commit | ccaf7f881462cc9a5ebf2981e465920128010658 | [log] [tgz] |
---|---|---|
author | Mark Horvath <mark.horvath@arm.com> | Mon Jan 04 18:16:42 2021 +0100 |
committer | Fabio Utzig <utzig@utzig.org> | Tue Jun 08 07:37:43 2021 -0300 |
tree | 7814976c978bc1dc7b4da9a5084a0fd5e6646846 | |
parent | f04aa54409063a492b393ac8ae4449c48ce0371c [diff] |
boot: Multi-image boot for direct-xip and ram-load Multiple image boot support is implemented for direct-xip and ram-load strategies. Dependency checking is also added, and for ram-load more executable ram regions can be set. Wrapper functions are intoduced to all boot strategies. Change-Id: I59b346277dcb2c17cef4800f1e556b4ea9144845 Signed-off-by: Mark Horvath <mark.horvath@arm.com>
This is mcuboot version 1.8.0-dev
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 simple software upgrades.
MCUboot is operating system and hardware independent and relies on hardware porting layers from the operating. 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 using GitHub issues. To participate please visit:
Issues were previously tracked on MCUboot JIRA , but it is now deprecated.
Information and documentation on the bootloader are stored within the source.
It was previously also documented on confluence: MCUBoot Confluence however, it is now deprecated and not currently maintained
For more information in the source, here are some pointers:
Developers welcome!