Have I Bricked my Omega 2?
@ccs-hello thanks ccs. I measured the current this morning as 180mA and the board remained cool until it connected to the wifi. Seems to match the findings in the link you posted.
I have 4 Omega2+ and all behave the same.
@Sergey-Suyazov We strongly recommend using a Dock to provide power to your Omega. Improvised power supplies usually can't keep up with the Omega's sudden changes in current requirement caused by the WiFi radio. This would explain the instability you're seeing with networking.
Thank you for the suggestion with the power supply.
This morning I have tried a number of different power supply units (including the official rPi3 plug and cable) and this allowed me to get the device setup and SD card expanded as per the guides.
Issue now is the wifi looses connection to my home internet? The AP is still up but the 'second connection' to the router fails?
If it helps, I use apple airport router and a number of AP. The wifi failed on both router/ap AND also failed when tethering to my mobile phone wifi hotspot?
Now if I boot the device up with the ethernet expansion board connected (I use the expansion dock with my Omega2+) I can get network address/connectivity from my router/network. But again, remove the ethernet module and I am back to only having the ability to SSH/WebConsole via the Omega AP.
Could this be power related?, The Omega is using the latest firmware available from the Onion repos and flashed using the onion guides.
Please read this topic Omega2+ Not working out of box! (and its forerunner).
If you want a nicer (ie. can read more easily) text please edit your post.
Put a line with ``` (three backticks) before and put a line with ``` (three backticks) after your terminal log.
Why won't my Omega stop blinking?
Yes, if your script includes an infinite loop or never stops for other reasons the boot process will not end and the led kepps blinking.
You can tell the rc.local file that this script will not end by attaching an & behind the command.
Added some more pictures as requested in ticket 16582.
When omega failed, it was connected like this – nothing more was connected.
omega2 plus not boot sd ???
Omega2 after frimware reflash, clearing all files on restart.
Could you please tell whatyou meant by re-flashed, as I am also getiing the similar issue. Does that re-flashed meant U flashed the firmware again?
Scratch the "anywhere" part. Double checked just now and it works everywhere BUT the terminal application.
I'd like to point out the "breadboard psu" link in the first post is a really bad one.
It only has one (probably low capacitance and very cheap) capacitor in the circuit design.
This is not good for AMS1117 (or friends) linear regulator.
That regulator needs both input and output capacitor in a normal design.
you really cannot cut corner in this front in power supply department.
I not understand. My omega is not dead?
All that can be said is that your current measurement does not by itself indicate much.
If you could log instantaneous current over time and compare to the startup of a functioning board it might be possible to learn something. And that other person who measured more than an amp had in their measurement a clear indication of a problem, but your measurement is not outside the expected range, at least until its trend over time is considered in detail.
Note that it is not out of the question that connection of an unspecified ammeter inline could prevent the system from properly functioning.
I received the replacement mini dock yesterday ( March 9) and now I'll try to put it to use.
Nevermind, I moved a little the cables and started! so exited to try it!
Relatively unlikely to make a difference, by now that you've done the upgrade you might try booting it without the USB stick plugged in - it represents some additional load on the power circuitry, and adds some complexity of software possibilities.
You could have installed a bad image, or at least one that's wrong for the board. Always failing in the same place in the boot sequence would be a hint of this, but it would seemingly not occur with a different image especially one that previously worked.
You could theoretically have a badly soldered board or one with bad components, not so bad that memory detection fails right away in U-Boot as has happened in a small number of cases, but more "flaky". However if a boad-level issue this would seem likely to cause more random failures than specific ones. An actual bad memory cell could cause a consistent failure but seems yet less likely.
@Chris-Stratton The problem is, that it does not reboot. It stucks with that message!
There's a chance the CPU did reset, but was unable to read the flash chip because on boot it would be sending 3-byte addresses while the flash chip may still be expecting 4-byte ones from the settings in use before the crash.
and what can I do now?