Topics created by Ilya Mordasov

@Ilya-Mordasov said in No wireless: yes, that seems to be the problem, because only the wireless is not working, I tried i2c and spidev, everything is fine. Yeah, only the wifi driver relies on the data in the factory partition. So it makes sense that everything else works. Do I only need to know the factory MAC address or do I need to have access to the whole chip? My guess is that you'll need a whole new copy of the factory partition - it looks like the wifi driver in openwrt 22.03 has a workaround for invalid MAC addresses but still crashes because of the rest of the invalid configuration. Do I need to connect wires to the chip? No need to connect wires, you can do it from Linux. And how can I extract the factory partition from the live chip? To copy the factory partition from one device to another, it's actually super similar to the steps in the post linked by @crispyoz: @Lazar-Demin said in Contradiction in Omega2 Device MAC Address Allocation: install the xxd package dump the factory partition to hex: xxd /dev/mtd2 > factory.hex create a backup just in case edit the two mac addresses (can use vi) convert the edited hex file to binary: xxd -r factory-new.hex > factory.bin write the binary file to the factory partition: mtd -r write factory.bin factory Do steps 1 to 5 on a working device, and step 6 on your current device. (You'll probably need to reinstall whichever firmware was successfully booting on your current device in order to get to Linux)

@Lazar-Demin Unfortunately, both ways you've suggested don't work to me, I don't have ethernet port, I use my custom shield, and I was trying to flash it via USB, but according to google I have old U-Boot 1.1.3 and Onion Omega2 UBoot Version: 4.3.0.3 and when I try to flash fw from the usb I get timeout error (found that it was solved in later versions) I use the next steps to flash my omega2: start command line tool attach usb and copy openwrt-initramfs image to 0x81000000 erase linux bootm 0x81000000 so when the device is running I connect to it via ssh and write omega2-0.3.3-b256 fw 5. cat omega2-v0.3.3-b256.bin | ssh root@192.168.1.1 mtd write - firmware These steps are ok for 0.1.10-b160 and openwrt-22.05.02 firmwares, but not for the latests openwrt is ok for general purposes (wifi connection, msc, etc), but it has a problems with interfaces, such as spi, i2c, gpio in general, so then omega2-0.1.10 is ok for that

@Pavel-Metrokhin какая-то странная ситуация, вы открещиваетесь от дальнейшей поддержки девелоперской платы, выпущенной вашей компанией как раз для разработки в случае, если дефолтное состояние было нарушено (в моем случае - стер загрузчик, причем стер средствами нативного кода, зашитым при покупке самой платы), при этом проблема не возникла из неоткуда, а наблюдалась с самого начала получения мной платы (наша ранняя беседа в хелпдеске) - и, с учетом, частоты вашей поддержки я искал пути решения проблемы, которая не позволяла мне пользоваться полноценно покупкой. Ваш бутлоадер мне помог стартовать плату, но bootcmd по умолчанию настроен на tftp инициализацию, при покупке не было указано, что для работы платы требуется ваш док, я использую свои макеты, не вижу смысла покупать новую плату из-за того, что ваша компания не дает компетентной поддержки

@Ilya-Mordasov i am also facing same issue if u solve that issue can u share me that working firmware please.

@Douglas-Kryder for what? Pine is just simple dev board, ok, raspberry shows the same error, should I go to raspberry forum? I use flashrom, pine64 is connected by spi, and is used for communication only upd: I resized uboot.bin up to required size and flashed it without errors, tomorrow I will solder it back to omega2 and test it

The flash is not a BGA - you can clearly see all 8 contacts in the picture, and if you hold the MT7688 in reset it will stay out of the way of your programmer. But you have to remove the shield. Unfortunately, JTAG does not seem to be available without removing the shield either. If you want to do low-level work you'd likely be better off with a Linkit Smart or an ACSIP module than an Omega2, in both cases where removing the shield is both less necessary, and substantially easier.

Thanks for your reply. I thought the same that 0.1.10 is more stable that previous, looked at changelog. But at first, I stucked in issue when I have to set internet connection via browser. Not always I see my ssid in the available networks list and usually type it manually. Even after that when I’m pressing configure it can freeze in this half-state. I’d prefer to set it using wifisetup over ssh or console. Also I tried to use lede repos instead of onion’s, but with it I got error relocating errors for wget and missed libencrypt.so Traceroute shows that I have access to the internet. But to be honest, I use my own extension board, but I’m not sure this is the reason. If I had the problem with it my o2 wouldn’t work. And o2 gets 3.3v of power and enough current Yep, I created ticket on onion’s helpdesk and sent them logs.

@Ghent-The-Slicer said in Using SD card on Omega2 not plus: It is not possible. In addition to the missing socket, there are other components missing, some are under the shield. Care to elaborate? Not much should be required, so this is a bit surprising, unless it's an intentional disabling. That said, USB-based storage could be another option - but it should be kept in mind that neither is robust in the face of unexpected shutdowns/reboots - one of the real strengths of these platforms over the computationally far more powerful and hardly more expensive raspberry pi, is that they don't depend on a fragile SD card. If you could boot a pi W from an SPI flash, it's questionable if there would be a market for MT7688 systems at all.

@Ilya-Mordasov There is no Vdd25 pin in Omega2.