commit | aefbd4663146bf561a530f9235527f9094146fb6 | [log] [tgz] |
---|---|---|
author | Marti Bolivar <marti@opensourcefoundries.com> | Fri Dec 15 03:43:46 2017 -0500 |
committer | David Brown <davidb@davidb.org> | Tue Jan 30 16:17:52 2018 -0700 |
tree | ba9513e6b90b2305b705c47e0ab37e6f210b86f3 | |
parent | 388454880f1313c10cd0a31614c54d234ae2480c [diff] |
zephyr: try to mass erase when flashing It's recommended practice to mass erase the flash chip before reflashing mcuboot. Add a configuration option for Zephyr which does this by default on some Zephyr runner backends which can support this (pyOCD and dfu-util). Additional runners can be added as needed. Signed-off-by: Marti Bolivar <marti@opensourcefoundries.com>
This is mcuboot, version 1.1.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.
Instructions for different operating systems can be found here:
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!