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.

Sign up for GitHub

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

Jump to bottom

[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
Open

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

wants to merge 2 commits into from
+21 −2

Commits on Oct 21, 2024

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

    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]>
    @MarkusLassila
    MarkusLassila committed Oct 21, 2024
    Configuration menu
    Copy the full SHA
    0a58adb View commit details
    Browse the repository at this point in the history

  2. [nrf noup] boot/../loader: Fix MCUboot update with NRF53 

    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 committed Oct 21, 2024
    Configuration menu
    Copy the full SHA
    396120f View commit details
    Browse the repository at this point in the history