commit | b588907ab14aaea983d23d23dc3c3073801a78c1 | [log] [tgz] |
---|---|---|
author | Johan Öhman <johan.ohman@softube.com> | Fri Apr 01 09:10:28 2022 +0200 |
committer | David Brown <davidb@davidb.org> | Tue May 31 10:20:19 2022 -0600 |
tree | 37e2a0085041313786543abae5dc24288a50fd51 | |
parent | 6093cbb3dd38f6ebb7c144c72f8af9baec65dc48 [diff] |
zephyr: Wrapped the RAM loading mode in Zephyr configs. The RAM loading mode wasn't wrapped in Zephyr configs like the other boot modes. Added a config to enable RAM loading as well as two configs to set IMAGE_EXECUTABLE_RAM_START and IMAGE_EXECUTABLE_RAM_SIZE, respectively. These two values default to the values from the chosen node sram in the dts. Signed-off-by: Johan Öhman <johan.ohman@softube.com>
This is MCUboot version 1.10.0-dev
MCUboot is a secure bootloader for 32-bits microcontrollers. It defines a common infrastructure for the bootloader and the system flash layout on microcontroller systems, and provides a secure bootloader that enables easy software upgrade.
MCUboot is not dependent on any specific operating system and hardware and relies on hardware porting layers from the operating system it works with. Currently, MCUboot works with the following operating systems and SoCs:
RIOT is supported only as a boot target. We will accept any new port contributed by the community once it is good enough.
See the following pages for instructions on using MCUboot with different operating systems and SoCs:
There are also instructions for the Simulator.
The issues being planned and worked on are tracked using GitHub issues. To give your input, visit MCUboot GitHub Issues.
You can find additional documentation on the bootloader in the source files. For more information, use the following links:
Developers are welcome!
Use the following links to join or see more about the project: