| commit | 94f3f91ca77fe46ad605e32715d98b4cb3aa2cb5 | [log] [tgz] |
|---|---|---|
| author | Marti Bolivar <marti.bolivar@linaro.org> | Fri Mar 17 15:13:32 2017 -0400 |
| committer | Marti Bolivar <marti.bolivar@linaro.org> | Tue Mar 21 15:39:53 2017 -0400 |
| tree | 7ddf1b35ffa00e0d0659e88d93046ae86bf76d6e | |
| parent | 51181cf34ff7abedd6a09eb1675c260e3e4d00be [diff] |
zephyr: 96b_nitrogen: increase scratch space The current configuration only allows ~170 updates before we can expect wear on the flash device (per product spec that the flash device supports 10,000 erase cycles). Increase the scratch size to make this better by removing some application space, to allow for ~2500 application updates or rollbacks. The new configuration is 52 KiB (13 sectors) for scratch, and 208 KiB (52 sectors) for each application image. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
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: