commit | ba1fbe607b3075910f9836fdab143ef081bdbf2a | [log] [tgz] |
---|---|---|
author | Fabio Utzig <utzig@apache.org> | Fri Jul 21 14:01:20 2017 -0300 |
committer | Fabio Utzig <utzig@utzig.org> | Fri Jul 21 15:58:44 2017 -0300 |
tree | 0deadfac31826222af6f89d231df60c5f4f12572 | |
parent | d0116731a9660539ea7f27a0e636fdd27f0c0982 [diff] |
Fix running newtmgr when building for mcuboot This enables mynewt to use mcuboot as a remote repository, which is only required when using newtmgr to manage images. Since mcuboot has slightly changed the trailer format, newtmgr built against the bundled mynewt bootloader writes the magic and flags to the wrong location. To build a mynewt app the wants to run with mcuboot as the bootloader and requires newtmgr one needs to change the app's pkg.yml dependencies as follows: - - boot/bootutil + - "@mcuboot/boot/bootutil" Signed-off-by: Fabio Utzig <utzig@apache.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. 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!