commit | 2ae1f1651649f7dd4066cdd15fbae765267a6d89 | [log] [tgz] |
---|---|---|
author | Dominik Ermel <dominik.ermel@nordicsemi.no> | Fri Jul 09 10:59:23 2021 +0000 |
committer | Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no> | Wed Jul 21 09:33:45 2021 +0200 |
tree | 2de4c971dd6e1cc70588f88c032ad1da622595d4 | |
parent | 3d4e55d5825bf09d783a0c28292d7a45d4cb2bd3 [diff] |
zephyr: Relocate BOOT_ERASE_PROGRESSIVELY option The Kconfig option is applied only when MCUBOOT_SERIAL is enabled so it has been moved into MUCBOOT_SERIAL dependent section of Kconfig. 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!