commit | ebd05033480cce8002381ecd4105e3965d5a59bd | [log] [tgz] |
---|---|---|
author | Sigvart Hovland <sigvart.m@gmail.com> | Thu Mar 21 10:47:32 2019 +0100 |
committer | Fabio Utzig <utzig@utzig.org> | Mon Mar 25 07:12:34 2019 -0300 |
tree | 70f6207ecd56ee7bf782a890a14d7de5fd1db029 | |
parent | 25ec74669854b7cae6de71f5fcaea377f32a88ce [diff] |
boot: Add cc310 options to CMakeLists, Kconfig and mcuboot config Adds `CC310` define which wraps the generic CC310 interface adds includes for using `NRF_CC310_BL` to CMakeLists. This requires `nrfxlib` to be located outside of the mcuboot folder by 1 directory level. Also add the Kconfig defines needed for this to build while trying to make it generic enough to be used by other vendors that have implemented `CC310`. Signed-off-by: Sigvart Hovland <sigvart.m@gmail.com>
This is mcuboot, version 1.3.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 easy software upgrade.
MCUboot is operating system and hardware independent and relies on hardware porting layers from the operating system it works with. 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!