2.7 KiB
MCUboot
Overview
MCUBoot is a secure bootloader for 32-bit MCUs. The goal of MCUBoot is to define a common infrastructure for the bootloader, system flash layout on microcontroller systems, and to provide a secure bootloader that enables easy software upgrade.
MCUboot is operating system and hardware independent, and relies on hardware porting layers from the operating system it works with. Currently MCUboot works with both the Apache Mynewt, and Zephyr operating systems, but more ports are planned in the future. RIOT is currently supported as a boot target with a complete port planned.
Contents
- General: this document
- [design]({% link design.txt %}): for the design
- [imgtool]({% link imgtool.md %}): The image signing and key management tool.
- [Patch submission]({% link SubmittingPatches.md %}) for information on how to contribute to mcuboot.
- The [internal design]({% link design.txt %}) documentation.
- Testing
- The [Zephyr]({% link testplan-zephyr.md %}) test plan.
- The [mynewt]({% link testplan-mynewt.md %}) test plan.
There is also a document about [signed images]({% link
signed_images.md %}) that is out of date. You should use imgtool.py
instead of these documents.
Roadmap
The issues being planned and worked on are tracked on Jira. To participate please visit:
Browsing
Information and documentation on the bootloader is stored within the source, and on confluence:
For more information in the source, here are some pointers:
- boot/bootutil: The core of the bootloader itself.
- boot/boot_serial: Support for serial upgrade within the bootloader itself.
- boot/zephyr: Port of the bootloader to Zephyr
- boot/mynewt: Mynewt bootloader app
- imgtool: A tool to securely sign firmware images for booting by MCUboot.
- sim: A bootloader simulator for testing and regression
Joining
Developers welcome!
- Our developer mailing list
- Our Slack channel
Get your invite here! - Our IRC channel, channel #mcuboot (IRC link