commit | cd07ed3b979d30f9b3feea38c382067655cd6710 | [log] [tgz] |
---|---|---|
author | Dominik Ermel <dominik.ermel@nordicsemi.no> | Wed Feb 17 15:18:01 2021 +0000 |
committer | Fabio Utzig <utzig@utzig.org> | Fri Feb 19 08:23:00 2021 -0300 |
tree | 69c5665c3fb15262e7cfbb43c657b5c1de63c36f | |
parent | 8a5e49876eae4f2d9bc8ced2fa2e2be0d24ddd68 [diff] |
boot/zephyr: Fix Direct-XIP boot messages The commit changes banner message to indicate that bootloader has been built for Direct-XIP mode. It also removes, in Direct-XIP compiled code, information on jumping into first slot: that information is not always correct for Direct-XIP and other messages correctly point slot that will be used. Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
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!