commit | 4e8d838d3648fb0a7f335f16d2e05f89613879af | [log] [tgz] |
---|---|---|
author | Tamas Ban <tamas.ban@arm.com> | Wed Sep 30 08:01:58 2020 +0100 |
committer | Fabio Utzig <utzig@utzig.org> | Fri Oct 02 07:31:11 2020 -0300 |
tree | 576a90f8b0799bbe3b37b0246b9a5a469311dc68 | |
parent | 76177e1b8e914bee0018044b982aea65a76676fe [diff] |
cypress: Add fault injection mitigation Add software countermeasures against fault injection attacks. Change-Id: I35ae95a3387a0231f81782e22728bf8a3f9b6005 Signed-off-by: Tamas Ban <tamas.ban@arm.com> Signed-off-by: Fabio Utzig <fabio.utzig@nordicsemi.no> Signed-off-by: Roman Okhrimenko <roman.okhrimenko@cypress.com>
This is mcuboot version 1.6.0
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!