commit | 17609d8a7e85e6863973fd8a909a47414ada6fb9 | [log] [tgz] |
---|---|---|
author | David Brown <david.brown@linaro.org> | Fri May 05 09:41:34 2017 -0600 |
committer | David Brown <david.brown@linaro.org> | Wed May 10 08:33:19 2017 -0600 |
tree | 55d2ac3b1d7d5a9757e9f4ece35ba5015aa5c7e4 | |
parent | 902d617687c0a1dc72ba2d5cda81cbaf2599cd01 [diff] |
Add "upgrade only" support Add a configuration option "BOOTUTIL_OVERWRITE_ONLY" that avoids using the image swap code. Instead, when an upgrade is detected in slot 1, it is copied directly onto slot 0. As long as the image in slot 1 is valid, this should work robustly (it will redo it if power is lost during the upgrade). This doesn't protect against the case of deploying an image that fails to boot on some devices. But, the behavior is similar to the swap upgrade approach when the slot 1 image is marked initially as "image ok", but without the complexity (or need of a swap partition) of the swap code.
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.
The MCUBoot project was originally taken from the Apache Mynewt operating system, which had secure boot and software upgrade functionality instrinsic to it. Currently development is heads down on a first release of MCUboot that works across both the Zephyr operating system and Apache Mynewt operating system.
For more information on what's being planned, and worked on, please visit:
https://runtimeco.atlassian.net/projects/MCUB/summary
Information and documentation on the bootloader is stored within the source, and on confluence:
https://runtimeco.atlassian.net/wiki/discover/all-updates
For more information in the source, here are some pointers:
Developers welcome! To join in the discussion, please join the developer mailing list:
http://lists.runtime.co/mailman/listinfo/dev-mcuboot_lists.runtime.co