commit | a0e1cce57ab782d23f267235e3915fd61d20f885 | [log] [tgz] |
---|---|---|
author | Fabio Utzig <utzig@apache.org> | Thu Nov 23 20:04:01 2017 -0200 |
committer | David Brown <davidb@davidb.org> | Thu Dec 21 13:36:34 2017 -0700 |
tree | 87449668185df1c1a3694f47ead91b9d28d789ba | |
parent | eb95a580b47a0ecc560234b4025581ba03424329 [diff] |
Enable ignoring write failures to status area The rationale behind this change is that while performing a swap operation, writes to the status area are not important enough to abort the operation. If the swap is not interrupted, status writes are ignored. If the swap is interrupted, failures to write status area are detected during the next boot and an appropriate measure is taken. If MCUBOOT_VALIDATE_SLOT0 is set we ignore the status write fail and allow slot0 to be validated by its hash/signature. Otherwise, the old behavior is maintained, which is to abort on any write failures. Signed-off-by: Fabio Utzig <utzig@apache.org>
This is mcuboot, version 1.0.0
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.
The issues being planned and worked on are tracked on Jira. To participate 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!