mcuboot
mcuboot copied to clipboard
Secure boot for 32-bit Microcontrollers!
Adds a warning if one of the default signing/encryption key files is used
BOOT_SERIAL_IMG_GRP_SLOT_INFO should be not available for direct-xip and ram-load modes.
The version of `imgtool` distributed through [PyPi](https://pypi.org/project/imgtool/#history) is out of date. Specifically, it does not contain the fixes contained in #1973.
Bootstrapping is currently not allowed for more than one image. But that seems to be unintentional according to https://github.com/mcu-tools/mcuboot/pull/826#issuecomment-707939624 I ran into the same issue trying to boot two images...
I am creating an application, for nRF chip on Zephyr environment. Using watchdog here is "must have". Also the idea is that the watchdog has to be enabled when doing...
This PR adds support for signing and verifying images with multiple signatures of the same type (e.g., multiple EC256 signatures), enhancing flexibility in secure boot scenarios. It also introduces Key...
The new stack comes with a higher demand for flash. We need to adapt the overlay file for the platform used for testing. The legacy stack is in the process...
Align the project security policy with the Trusted Firmware security policy at: https://www.trustedfirmware.org/.well-known/security.txt
Directly load an image to RAM and see if that works.
This PR adds support for Booting on a Cortex-R core. It has been tested with the following branch which also includes some instructions what Kconfig options need to be set:...