ARMmbed
/
mbed-os
mirror of https://github.com/ARMmbed/mbed-os.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
mbed-os/tools/targets/musca_b1-root-rsa-3072.md

12 lines
445 B
Markdown
Raw Normal View History

Add ARM_MUSCA_B1 as a new target platform Musca-B1 is a Cortex-M33 based target with security extension enabled. - ARM_MUSCA_B1 is the non-secure target running mbed-os. - ARM_MUSCA_B1_S is the secure target running TF-M. - TF-M sources were imported and patched in previous commits. - TF-M secure bootloader (McuBoot) for MUSCA_B1 is submitted by a pre-built binary. - A post-build hook concatenates The secure and non-secure binaries, signs it and then concatenates the bootloader with the signed binary. Change-Id: I4b36290941b5f0bb7aa7c12dda2f38b5c1e39ae2 Signed-off-by: Tamas Kaman <tamas.kaman@arm.com> Signed-off-by: Gabor Abonyi <gabor.abonyi@arm.com>
2020-01-08 20:08:12 +00:00
# Musca-B1 RSA keypair
A default RSA key pair is given to the Musca-B1 target.
psa: Remove v8-M S targets Remove PSA v8-M S target binaries will be built outside of Mbed OS and added in as binaries which NS targets consume. Mbed OS no longer implements PSA for v8-M targets, so there is no reason for it to build PSA S targets. Signed-off-by: Jaeden Amero <jaeden.amero@arm.com>
2020-03-12 16:04:49 +00:00
Public key was pre-compiled to `targets/TARGET_ARM_SSG/TARGET_MUSCA_B1/prebuilt/mcuboot.bin` and private key is in `musca_b1-root-rsa-3072.pem`.
Add ARM_MUSCA_B1 as a new target platform Musca-B1 is a Cortex-M33 based target with security extension enabled. - ARM_MUSCA_B1 is the non-secure target running mbed-os. - ARM_MUSCA_B1_S is the secure target running TF-M. - TF-M sources were imported and patched in previous commits. - TF-M secure bootloader (McuBoot) for MUSCA_B1 is submitted by a pre-built binary. - A post-build hook concatenates The secure and non-secure binaries, signs it and then concatenates the bootloader with the signed binary. Change-Id: I4b36290941b5f0bb7aa7c12dda2f38b5c1e39ae2 Signed-off-by: Tamas Kaman <tamas.kaman@arm.com> Signed-off-by: Gabor Abonyi <gabor.abonyi@arm.com>
2020-01-08 20:08:12 +00:00
DO NOT use them in production code, they are exclusively for testing!
Private key must be stored in a safe place outside of the repository.
`tools/psa/tfm/bin_utils/imgtool.py` can be used to generate new key pairs.