commit | 7e377ab17b79dd1b6e1dc376af4659df0f793cf3 | [log] [tgz] |
---|---|---|
author | David Brown <david.brown@linaro.org> | Wed May 26 16:33:39 2021 -0600 |
committer | David Brown <davidb@davidb.org> | Mon Jul 19 11:22:13 2021 -0600 |
tree | cf9e621555efbc1467ae90b436b236bba0943c82 | |
parent | 4b82c671cf54015b15b20c5bd1d8f205bb9c84f5 [diff] |
sim: Enable sim building with ram-load Allow the sim to test configurations with MCUBOOT_RAM_LOAD defined. This does not define any tests for this mode. This adds definitions for simulated RAM offsets to the simulator. This will define the offset (from `IMAGE_RAM_BASE`) to where the simulated RAM will be located. For now, just give these somewhat reasonable values so that we are able to at least compile the RAM_LOADING code in the simulator. Signed-off-by: David Brown <david.brown@linaro.org>
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!