embox VS stm32-bootloader

Embox is a configurable RTOS designed for resource constrained and embedded systems. Embox main idea is using Linux software without Linux. (https://embox.github.io/ ) If you want use complex Linux Software and Linux is huge for your goals. Embox is the best idea, as I think. For example Embox is the only RTOS that allows to use OpenCV on Cortex-m MCUs https://www.embedded.com/benchmarking-opencv-on-stm32-mcus/

Look at Embox (https://github.com/embox/embox). It can run on EFM32ZG with 32kB ROM 4kB RAM

Take a look at Embox - https://github.com/embox/embox

As for Linux, it allows easy and fast creating a device with reach features, but it requires more powerful and expensive hardware platforms, it has some questions with hard real-time, and it is less secure after all it is a general-purpose OS. We try to solve these cons of Linux in Embox. It combines prop RTOSes and Linux and allows run Linux software everywhere including MCUs

We try to solve these Linux disadvantages in our way in Embox project. The project allows run Linux software everywhere including MCUs.

Here's a bootloader "library" that might be useful. You need to add your own code to get the actual firmware image from somewhere (UART, an SD card, or whatever), and then you just pass it off to the "library" for flashing.

Yes, unless you have something like an STM32 with a built-in bootloader. This can be used to update the regular bootloader. For example, this bootloader is capable of jumping to the built-in bootloader from software (as opposed to the "regular" method of pulling certain pins high or low at reset to cause the processor to run the built-in bootloader from ROM rather than the regular bootloader from flash).