commit | 2473ac0e5b6020109eb45387022031fbd0382a98 | [log] [tgz] |
---|---|---|
author | Fabio Utzig <utzig@utzig.org> | Tue May 02 12:45:02 2017 -0300 |
committer | Fabio Utzig <utzig@utzig.org> | Wed May 24 08:58:59 2017 -0400 |
tree | 834ff2856845f0dfc53240885b46b6f9ec3ac5a6 | |
parent | 7ebb7c23d90fba468c73951c66bd5f1bae11a2d8 [diff] |
Add support for swapping only fw sectors in use Before this patch, the swapping would process all sectors in a slot not matter what the size of the binary firmware was. This changes the swap process to swap only sectors that are in use by firmware. Also, if the last slot sector, which stores the trailer, is actually not in use by the binary firmware, now trailer is never written to scratch. `use_scratch` temp variable was added to boot_status struct to control this (this var is never written to disk). Random other small refactorings were applied.
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