| commit | 4cb262357435bb83601132832797c05ba347ae89 | [log] [tgz] |
|---|---|---|
| author | David Brown <david.brown@linaro.org> | Tue Apr 11 08:15:18 2017 -0600 |
| committer | David Brown <david.brown@linaro.org> | Tue Apr 11 08:18:18 2017 -0600 |
| tree | 9d21e870bbfb9c6cb4bd0a3d276ddd796a789037 | |
| parent | a9c6661d80af20d9c2aee4c390fa8d38249d67e3 [diff] |
Back out unneeded part of random reset test
In change
commit bb5635e07439c809d055d3413844c394c0b1b4bc
Author: Fabio Utzig <utzig@utzig.org>
Date: Mon Apr 10 09:07:02 2017 -0300
Add test of multiple random resets while upgrading
in addition to adding the try_random_fails, it shuffled the order that
the initial interruption test ran. However, this test always clones
the flash device, so it doesn't matter what order the tests are run.
Revert this part of the change to avoid unnecessary complexity in the
code.
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.
The MCUBoot project was originally taken from the Apache Mynewt operating system, which had secure boot and software upgrade functionality instrinsic to it. Currently development is heads down on a first release of MCUboot that works across both the Zephyr operating system and Apache Mynewt operating system.
For more information on what's being planned, and worked on, 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! To join in the discussion, please join the developer mailing list:
http://lists.runtime.co/mailman/listinfo/dev-mcuboot_lists.runtime.co