commit | 84ede5893ffd781e8dcc01900f2383601bda382f | [log] [tgz] |
---|---|---|
author | Carles Cufi <carles.cufi@nordicsemi.no> | Mon Jan 29 15:12:00 2018 +0100 |
committer | David Brown <davidb@davidb.org> | Mon Jan 29 12:22:48 2018 -0700 |
tree | bbecb7d77536a53b98a2a64d60c2a09fa2cb7106 | |
parent | 51a09210063f5f09831a71f05923589a8695ac96 [diff] |
kconfig: Add new MCUboot device settings Add a new MCUboot device settings option that enables or configures features that are specific to a particular device. Additionally enable software vector relay in Cortex-M0 CPUs that do not have a hardware mechanism to relay or forward interrupts. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
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!