@Higor which uboot version are you using?

@crispyoz Thanks! That's an idea - I could probably just do a bunch of register level acces to initialise the display over i2c and put up something. I'll need to do a bit of learning on uboot

@huntc @Lazar-Demin pointed to the relevant description of the underlying issue (mismatched address modes) the issue is in the NOR flash not the Omega2, Onion have just activated the workaround via the DTS. Basically the CPU is in 4 bit mode while the NOR may not have reset properly and therefore remains in 3 bit mode --->>> CONFUSION! I recall a lot of discussion of this issue on the SUSE dev list a few years ago, if you want to know more perhaps check the mail archive on suse.org. Bu the short answer is there is nothing you can fix here.

@nsmith I suggest looking at this docs page as well: http://docs.onion.io/omega2-docs/running-a-command-on-boot.html

+1 on the need to boot directly from an sd card/emmc

@JeffZhou Thanks a lot, for your response! I think that the 2nd point (VCC current) was the root cause of my issues: I used an AWG30 wire for all VCC lines which was too thin to carry the current. Regarding the UART <-> USB-Bridge the issue still persists, it requires a little fiddling: opening the serial connection after counting to three after plugging in. Then it worked booted in 100% correctly so far. Best Regards!

@haythem The problem when you are trying to debug for hours is that you end up not seeing what you need to, and only seeing what you don't need to. So I am trying to help you work logically through the issues so they can be resolved. I've worked on hundreds of Omega2 so please follow what I ask you to do, provide the information I ask for and then I expect everything will be resolved. Let's start from scratch. Take a breath, forget what you think you know and just step through things as I asked. How did you perform a factory reset without a dock? I suspect your console issue is the handshaking, so please post the putty connect screen (as I asked) so I can take a look at it.

@defa85 My first step was to divide the boot time into two sections. 1) System is up. 2) Network is functional. If you start with section 1, issue the command service network disable and reboot (make sure you have a serial/usb connection). The system will start without loading the network, I expect this will be around 30 seconds. Depending on what services and kernel modules you load, you may be able to tweak this a bit by disabling a service and loading it after your app, or removing kernel modules you don't need. We're talking a second or less for most of this standard stuff. Network connection accounts for roughly 50% of the entire boot process so if you can optimise this you will notice an impact. An ethernet connection is faster and while you may think a static IP is faster, that is not necessarily the case on all routers. Disable ipv6, configure a specific channel if you are using wifi. dmesg will give you the timings, but for more detail you can enable more detailed debugging during boot up by watching for this prompt: Press the [f] key and hit [enter] to enter failsafe mode Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level press 4 and enter, then once boot is complete use the dmesg command to see the details and timing.

Updated an LTE board to 0.3.2 b244 just for the sake of it. I still get double entries (see my last post) but so far it doesn't show the increment behaviour but it isn't static either. I keep an eye on it.

Ok, seems like this appears to be my issue

@Anil-bhaskar did you try the example rc.local @György-Farkas posted above? It may be that rc.local is functioning correctly but that the commands you are executing are not. You can post your rc.local If you are trying to start a daemon you may need to background it using & so it doesn't exit. I personally thing procd is more appropriate in that case.

At a glance it looks like the mounting of /overlay didn't work. Suggest going over those steps again carefully.

@Angus-Ryan In that case, try Firmware Flashing from USB Storage.

Hello @Geoff-Tripoli. I got a pretty similar problem "blocksize write incorrect block#=0! ## Error: HTTP ugrade failed!" , did you find how to solve it?

@Ger-Buurman-0 Thanks for all of the info ERGO: You can't boot the Omega2+ via and USB Thanks

@Ankit-Rana I tried to reply for this "Omega 2 can't complete booting process!!!" and this "Omega continously Booting ..." statements. Later you wrote Omega 2 can't complete booting process!!! but still the LED is blinking for some time and again it continue, omega complete booting process. "Omega 2 can't complete booting" vs "omega complete booting" - this is some contradiction. And I don't fully understand what about the amber OMEGA LED. You have a USB-to-3.3V TTL serial converter module. You have already made a Serial Console connection (RX0, TX0, GND --- your module Tx, Rx, GND --- USB port of your host PC --- PuTTY). Omega continously Booting cant find access point Look at the output of the Serial Console to see what's going on.