Skip to content

target: nrf54l: fix reprogramming of locked devices - #2047

Open
jsiverskog wants to merge 1 commit into
pyocd:mainfrom
jsiverskog:fix_nrf54l_reprogramming
Open

jsiverskog wants to merge 1 commit into
pyocd:mainfrom
jsiverskog:fix_nrf54l_reprogramming

Conversation

@jsiverskog

Copy link
Copy Markdown
Contributor

once an nrf54l15 has been programmed with firmware that leaves APPROTECT enabled, connecting triggers the auto-unlock mass erase. the AHB-AP object was created while the device was locked though, so the first memory access afterwards (the FICR read in check_part_info) fails with:

Memory transfer fault (SWD/JTAG communication failure (FAULT ACK))
@ 0x00ffc31c-0x00ffc31f

re-create the AHB-AP after a successful mass erase (and re-apply the rom base fixup), as the nrf52 target does. also bail out if the mass erase fails instead of continuing with a locked device.

once an nrf54l15 has been programmed with firmware that leaves
APPROTECT enabled, connecting triggers the auto-unlock mass erase.
the AHB-AP object was created while the device was locked though,
so the first memory access afterwards (the FICR read in
check_part_info) fails with:

  Memory transfer fault (SWD/JTAG communication failure (FAULT ACK))
  @ 0x00ffc31c-0x00ffc31f

re-create the AHB-AP after a successful mass erase (and re-apply
the rom base fixup), as the nrf52 target does. also bail out if
the mass erase fails instead of continuing with a locked device.

Signed-off-by: Jacob Siverskog <jacob@teenage.engineering>

This branch has not been deployed

No deployments
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.

1 participant