Use a different key to sign Non-secure image for ARM_MUSCA_B1 target #13285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
MCUBOOT has been upgraded to image 2, therefore the Non-secure image
needs to be signed with its own private key, which is validated during
boot.
MCUBOOT_REPO: 'UPSTREAM'
MCUBOOT_IMAGE_NUMBER: '2'
MCUBOOT_UPGRADE_STRATEGY: 'OVERWRITE_ONLY'
MCUBOOT_HW_KEY: 'On' (default)
The private key is been imported from - https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/bl2/ext/mcuboot/root-rsa-3072_1.pem
Impact of changes
These changes impact only the
ARM_MUSCA_B1
target.Migration actions required
Documentation
Pull request type
Test results
Reviewers