4 ms·
At that point, why not just get rid of the OS? That's what small embedded systems basically are --- there's not bootloader or any other extraneous complexity,
by userbinator 5y ago
At that point, why not just get rid of the OS?
That's what small embedded systems basically are --- there's not bootloader or any other extraneous complexity, the MCU starts up from the reset vector directly into the "application code".
Using Linux or some other full-blown OS is why a lot of newer embedded stuff like "smart" TVs, set-top boxes, etc. need to "boot" before they're usable. Regardless of how much you try to optimise the process, it won't beat a simple MCU or the "old school" non-computerised systems from power-on until usable.
- fouric 5y agoBecause the thing I described is still more flexible than having no OS at all. If you bundle some of the userspace into the kernel image, then you trade-off some security, and needing to have to rebuild this large image periodically, for much faster startup times, and (optionally) load times for some userspace applications - but you can still install and load other userspace tools, they'll just start up "normally".