Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[nrf noup] boot: zephyr: Do not lock PCD region with TF-M #330

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

MarkusLassila
Copy link

@MarkusLassila MarkusLassila commented Aug 30, 2024

Previously PCD memory was locked as read-only, non-secure in MCUboot. Given that TF-M also needs write to PCD to communicate with b0n, the memory is left unlocked and locked to read-only, non-secure in TF-M.

Edit: Added fix to MCUboot upgrade image handling with CONFIG_NRF53_MULTI_IMAGE_UPDATE.

@MarkusLassila
Copy link
Author

@nvlsianpu: Could you take a look at this?

@MarkusLassila MarkusLassila requested a review from a team October 18, 2024 09:59
Previously PCD memory was locked as read-only, non-secure in
MCUboot. Given that TF-M also needs write to PCD to
communicate with b0n, the memory is left unlocked and
locked to read-only, non-secure in TF-M.

Signed-off-by: Markus Lassila <[email protected]>
Previously, when CONFIG_NRF53_MULTI_IMAGE_UPDATE was set and the
MCUboot upgrade image was uploaded, but not verified or confirmed,
booting the DK caused MCUboot to attempt to start the MCUboot upgrade
image as the application image.

This was only recoverable with: nrfjprog --family NRF53 --qspieraseall.

Signed-off-by: Markus Lassila <[email protected]>
@MarkusLassila MarkusLassila force-pushed the mcuboot-do-not-lock-pcd-with-tfm branch from 365d973 to 396120f Compare October 21, 2024 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants