commit | f4d0e1adf2a1ee1711d9290f918e59b86dfcacbe | [log] [tgz] |
---|---|---|
author | Marti Bolivar <marti.bolivar@linaro.org> | Wed Aug 30 18:39:07 2017 -0400 |
committer | David Brown <davidb@davidb.org> | Thu Aug 31 08:29:53 2017 -0600 |
tree | 428711afa18ec9850f33c597915532dc77b0c9f2 | |
parent | 4094813181e0101081f08ff26c41eae525588306 [diff] |
zephyr: turn off I2C Upstream Zephyr is making a habit of enabling subsystems on any board that supports them. That's a potential security risk if any of those allow interference with the running bootloader, and is currently exceeding mcuboot's flash allowance on some STM32 targets, e.g. 96b_carbon. Turn off I2C to restore the build for those. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
This is mcuboot, version 0.9.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.
The issues being planned and worked on are tracked on Jira. To participate please visit:
https://runtimeco.atlassian.net/projects/MCUB/summary
Information and documentation on the bootloader is stored within the source, and on confluence:
https://runtimeco.atlassian.net/wiki/discover/all-updates
For more information in the source, here are some pointers:
Developers welcome!