commit | db543e502617a54c1ff62d39655d4aac914b5dc0 | [log] [tgz] |
---|---|---|
author | Hugo L'Hostis <hugo.lhostis@arm.com> | Tue Mar 09 18:00:31 2021 +0000 |
committer | Fabio Utzig <utzig@utzig.org> | Thu Oct 07 14:23:51 2021 -0300 |
tree | 7fc31cf8287b7d66a6e7694800b7b26cb41f0f6d | |
parent | 8fcdfc5c67312f3d9630976f2d522f5c290a9e37 [diff] |
boot : Adding encrypted ram-load support This patch adds the possibility to boot using ram-load with an encrypted image. This is enabled when both the flags MCUBOOT_RAM_LOAD and MCUBOOT_ENC_IMAGES are defined. Signed-off-by: Fabio Utzig <utzig@apache.org> Signed-off-by: Hugo L'Hostis <hugo.lhostis@arm.com> Signed-off-by: Salome Thirot <salome.thirot@arm.com> Change-Id: I7756c2c634d90a2e726117d6cfc5650653cf1b51
This is mcuboot version 1.8.0-rc2
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!