@TGMM I'm very skeptical that you could get a boot time sub 10secs, however as @luz pointed out you can reduce boot time by disabling init scripts. There are a lot of drivers that load during the boot process, many of which probe hardware so there may be some time to be saved there. Also reduce to a minimum the services/daemons you run, basically what @luz was saying. Stock firmware loads a lot of stuff you may not need. Connecting/scanning for WiFI takes some time so if you don't need it, disable it.

@György-Farkas Thanks again for replying! About the 3 seconds... it is desired and acceptable, having to hold the momentary switch down for 3 seconds to turn on/off the device ensures that it is not turned on or off accidentally. (This project is being run from a battery) I'm just a little annoyed that it takes LONGER than 3 seconds (10-13) to boot up the MCU. I agree your suggestions would work, but I would like to avoid having to make hardware changes to the board... in case this project happens to be manufactured in any considerable number. (The arduino dock is mounted on a pcb, so I was kind of hoping there would be a hardware fix that I could make to MY pcb to fix this... without resorting to altering the Arduino Dock board) I wonder if anything could be done in the Omegas boot code to pull pin 19 low sooner in the boot sequence or if is something that can't be avoided due to the Omegas internals.

@marco-rigoni NO! sysupgrade is not what you want. Try the uimage u = micro, iirc, and should provide you bare minimum booting times off the bat (though probably without all the stuff you need listed above). I think, though, uart is a deferred, with wifi + webserver as an immediate. That would mean that, if you set up your webserver correctly, you can get to minimum boot while you are awaiting the dhcp software and uart to boot. If you make a wifi connection as an initial setup (read: the user is expected to wait for a while on the first initial setup of internet access, with immediate boots thereafter), then your wifi and server can get online fairly quickly I would think. Unless of course, I'm misunderstanding your application. The reason this approach would work is that minimum response time for a webserver is the key. People/users expect the loading of data to take a while. And, the 'retrieving data log' portion can be a pinwheel to buy you time to load the first time, right? So there is actually a lot you can do to get a product that have nothing to do with overall boot times. . .