Explanation: 1. The Bootloader handles the initial boot sequence on hardware before the operating system takes over. For example, U-boot is often used as the boot loader in embedded systems before starting embedded operating systems like Linux or FreeBSD. MCUBoot is also a bootloader, but it targets IoT, referring here to systems with limited memory and storage capacity of MCUs. 2. The early MCUBoot was part of the IoT system Apache Mynewt and is now independent. 3. Source code and documentation can be downloaded from:
https://github.com/runtimeco/mcuboot. 4. The last WeChat introduced Apache Mynewt to everyone:
Apache launched the IoT system Mynewt to compete with Mbed OS, Zephyr Project, and RIoT, supporting STM32.
5. Hopefully, it can be promoted in the future, and we can give a thumbs up to the original creators. ========================Introduction to MCUBoot: 1. MCUBoot is a secure bootloader for 32-bit MCUs. The goal of MCUBoot is to define a universal infrastructure for bootloaders, define the system flash layout on microcontroller systems, and provide a secure bootloader for easy software upgrades. 2. MCUboot is independent of the operating system and hardware, relying on the hardware abstraction layer of the operating system it works with. Currently, mcuboot works with Apache Mynewt and Zephyr operating systems, but plans to support more other RTOS in the future. 3. Due to resource constraints, the bootloader only needs a flash driver, single-threaded, and a cryptographic service. 4. The MCUBoot project aims to address security and field firmware updates. To achieve firmware updates, the Flash is divided into four parts: (1) Bootloader for system bootloading. (2) Slot0 for code execution, which should be the APP part. (3) Slot1 for firmware upgrades. (4) Scratch, a temporary storage area for swapping Slot during upgrades.
