6d56cd8a5f
Instead of having to cd into the 'sim' directory, create a top-level Cargo.toml file that adds the sim as a workspace. For the most part, this doesn't change how the simulator works. It is still possible to run `cargo test ...` within the `sim` directory. However, the `target` directory will reside at the top-level of the tree instead of within the sim directory. One change is that running cargo commands at the top of the tree will run those commands on all of the packages found within the tree. Specific packages can be tested by either changing to the directory of that package, or passing `-p <dir>` to the cargo test command (i.e. `cargo test -p bootsim`). The other visible change from this commit is that the 'target' directory will always be at the top of the tree, rather than in particular directory where the test is run. Any scripts or tools that expect this to be in a certainly location, will have to be modified. Signed-off-by: David Brown <david.brown@linaro.org> |
||
|---|---|---|
| .github/workflows | ||
| boot | ||
| ci | ||
| docs | ||
| ext | ||
| ptest | ||
| samples | ||
| scripts | ||
| sim | ||
| testplan/mynewt | ||
| zephyr | ||
| .gitignore | ||
| .gitmodules | ||
| .mbedignore | ||
| .travis.yml-disabled | ||
| CODE_OF_CONDUCT.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE | ||
| NOTICE | ||
| README.md | ||
| enc-aes128kw.b64 | ||
| enc-aes256kw.b64 | ||
| enc-ec256-priv.pem | ||
| enc-ec256-pub.pem | ||
| enc-rsa2048-priv.pem | ||
| enc-rsa2048-pub.pem | ||
| enc-x25519-priv.pem | ||
| enc-x25519-pub.pem | ||
| go.mod | ||
| project.yml | ||
| repository.yml | ||
| root-ec-p256-pkcs8.pem | ||
| root-ec-p256.pem | ||
| root-ed25519.pem | ||
| root-rsa-2048.pem | ||
| root-rsa-3072.pem | ||
README.md
mcuboot
This is mcuboot version 1.8.0-rc1
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.
Using MCUboot
Instructions for different operating systems can be found here:
Roadmap
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.
Browsing
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:
- boot/bootutil: The core of the bootloader itself.
- boot/boot_serial: Support for serial upgrade within the bootloader itself.
- boot/zephyr: Port of the bootloader to Zephyr
- boot/mynewt: Mynewt bootloader app
- boot/nuttx: Bootloader application and port of MCUboot interfaces for NuttX.
- boot/espressif: Bootloader application and MCUboot port for Espressif SoCs.
- imgtool: A tool to securely sign firmware images for booting by mcuboot.
- sim: A bootloader simulator for testing and regression
Joining
Developers welcome!
- Our developer mailing list: https://groups.io/g/mcuboot
- Our Slack channel: https://mcuboot.slack.com/
Get your invite here! - Our IRC channel: http://irc.freenode.net, #mcuboot