Repository navigation
Replies: 1 comment
I don't see what the purpose of using u-boot on a zephyr device would be. For a complex linux sbc then sure, it allows multiple boot locations including manufacturing, test and recovery if something happens over a multitude of interfaces. MCUboot on the other hand does not, it is a secure bootloader which only really allows loading (or updating) one of 2 images, it is fast and lightweight and is fully integrated in zephyr. The size of the SoC isn't really important in the decision, it is the best tool for the job |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I am working on Zephyr firmware intended to run on my embedded device, which is based on an ARMv7 32-bit architecture.
Zephyr OS has superb integration with MCUboot, and my first thought was to use this bootloader. However, after discussing bootloader strategies with others, I was told that MCUboot is meant for “small devices,” not “large SoCs,” and that I would be better off using other solutions like U-Boot.
This leads me to my question: what really prevents MCUboot from being compatible with modern SoC devices? As systems become more complex, they also become cheaper and more accessible. In the past, “embedded” often meant something like an STM32 chip, but now you can get an ARMv7 processor with a neural processing unit for less than a dollar. These chips seem like a great fit for small embedded devices using technologies like Zephyr and potentially MCUboot.
Could
mcubootstop to be a small 32-bit bootloader and become just a first-class bootloader for ZephyrOS apps?All reactions