MCUboot: Multi-Image Support
summary
MCUboot implements a tiny (≈16KB) bootloader for constrained MCUs that uses a two‑slot flash layout (slot0, slot1, scratch), verifies images with RSA/ECDSA, and performs either overwrite or swap upgrades to allow reversion; it already handles execute‑in‑place devices and is being extended for multi‑image setups (secure vs non‑secure, multi‑CPU or TrustZone‑M) using per‑image TLV manifests or a detached manifest approach that moves to sign manifest semantics and aligns with SUIT/COSE/CBOR work.
AI-written summary · about
chapters (9)
- 0:00MCUboot introduction
- 4:21Current features
- 8:38Execute-in-place vs non-execute-in-place
- 13:00MCUboot manifests and TLV
- 19:23Multi-image challenges
- 23:17SUIT in firmware updates
- 27:59MCUboot future with SUIT
- 30:30Q&A
- 33:45Q&A
related talks
24mIntroduction to MCUboot: Secure Bootloader and Easy Firmware Updates
46mEnhancing System Security by Integrating Zephyr Bootloader and MCUboot
01h 03mTrusted Firmware M : Trusted Boot
21mSecure and Encrypted Boot in Zephyr RTOS
24mSecure and Encrypted Boot in Zephyr RTOS
42mApache Mynewt Bootloader for Reliable and Secure Firmware Upgrades
39mSecuring firmware: Secure and Trusted boot in OpenBMC
38mBoot to Cloud Security Considerations with IoT