Factory Reset due to "invisible" Omega2
-
@Mark-B
Thank you for your answer.
For the power supply i'm using a MB102 (http://www.petervis.com/Raspberry_PI/Breadboard_Power_Supply/YwRobot_Breadboard_Power_Supply.html) which should supply stable 3.3 V. However I tried also to connect the Omega2 to the arduino 3.3V Out but nothing changed...
-
@WereCatf
Hi, I've just tried to connect to the Omega2 with serial connection. The problem is that the Omega seems to be in loop. I can see the booting process but after a few second, before finishing the boot, the board reboot.I need to reset the board, do you have any ideas ?
-
@Alessandro-Nichelini said in Factory Reset due to "invisible" Omega2:
@Mark-B
Thank you for your answer.
For the power supply i'm using a MB102 (http://www.petervis.com/Raspberry_PI/Breadboard_Power_Supply/YwRobot_Breadboard_Power_Supply.html) which should supply stable 3.3 V. However I tried also to connect the Omega2 to the arduino 3.3V Out but nothing changed...When I was seeing the boot loop I was using an MB102 with 10 cm Dupont connector wires as well.
You might try shortening your leads to the Omega2 as much as practical, use heavier gauge wire, and maybe put a capacitor on the Omega2 power pins, but I'm not convinced this is a stable setup.
I (and many others) had much the same problem with the ESP8266 boards with off-board power regulation which can be fixed in a similar manner.
Edit to add: From another current thread, I think the last boot line I saw on the serial port was "[ 18.882660] EEPROM:Read from [factory] offset 0x0,length 0x400." Then it started to exercise the WiFi stuff and immediately rebooted.
-
@Alessandro-Nichelini Well, like @Mark-B says, you might wanna try beefier power/cables, but if that doesn't work, you could post the boot-log here. Or see http://community.onion.io/topic/1154/omega-2-usb-firmware-install-after-brick-resolved for how to install new firmware from USB.
-
Thank you all for the help
0_1484254557174_log.txt
Here the log. I don't understand why lots of characters are missing in the console. (I'm working at the right baud amount).
-
@Alessandro-Nichelini That's a really messed-up log. You do have the serial-adapter's GND-pin connected to the Omega's GND-pin? And baudrate at 115200?
-
@WereCatf
Yes
-
@Alessandro-Nichelini The serial-port on the Omega2 can be quite fiddly. I have a whole bunch of USB serial-adapters and only one of them works right with it. The adapter in question is based on Prolific PL2303. I don't really know to suggest other than getting another adapter to try with or connecting via an Arduino or similar, if you got anything lying around. Can't really do recovery, if serial isn't working!
-
@WereCatf
I'll try with Arduino. This situation is upsetting: without the expansion dock i can't fix Omega2
-
@Alessandro-Nichelini yikes, that log looks awful, it definitely looks like a connection issue. When you do get the serial working correctly, you can get into the bootloader to reflash the firmware.
Without a dock, you'll have to apply a voltage to the reset pin while the Omega is booting to start the bootloader recovery.
Detailed 'using the bootloader' articles are in the pipeline, stay tuned!
-
@Alessandro-Nichelini try adding capacitor on the power line. I had similar setup using breadboard power supply and had the same boot loop problem. After I added a cap (I used 1000uF electrolytic capacitor) the boot process seems to be working fine and I could get into the console.
-
@fajran
Hi, I've just tried to use a different MB102 and short wires as suggested some days ago: Omega2 seems to work now, so the firmware was not corrupted and I don't need to flash the firmware. The problem was probably all about the power supply. I'll try with capacitor too. Thank you all
