doc: ap-protect: edit nrfjprog to nrfutil

[greg-fer]

Changed nrfjprog commands to nrfutil in the AP-Protect documentation. NCSDK-30148.

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 5

Inputs:

Sources:

more details

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (0)

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain
• ◻️ Build twister
• ◻️ Integration tests

Note: This message is automatically posted and updated by the CI

[NordicBuilder]

You can find the documentation preview for this PR at this link.

Note: This comment is automatically posted by the Documentation Publish GitHub Action.

[MarkusLassila]

To lock both the network core and application core in nrf53, you actually have to do both:
nrfutil device protection-set All --core Network
nrfutil device protection-set All

And in this order.

This is the same with nrfjprog, but I think that this should be updated in here.

[MarkusLassila]

With nrf54l15 (using my nRF54L15-PDK):

nrfutil device protection-set All

Fails with: [Probe] Device error: Unknown device: Unknown part number 0x0000001c and revision 0x00000001 , code: Generic

Debugger can be connected after this.

nrfjprog --rbp ALL also fails, but the debugger cannot be connected after that.

[bjorgan]

@MarkusLassila: Which version is this? (nrfutil device --version)

[MarkusLassila]

nrfutil-device 2.3.6 (20652ac 2024-05-30)
commit-hash: 20652ac7e517947958af060dcb956b9de5fe5456
commit-date: 2024-05-30
host: x86_64-unknown-linux-gnu
build-timestamp: 2024-05-30T11:22:59.088218653Z
classification: nrf-external

[greg-fer]

@evenl , @bjorgan , @Tiwalun , would you know what the issue might be? Could it be related to Markus using a PDK, not a DK?

[bjorgan]

Too old version, I think. The version (2.3.6) also sounds like the latest on the old package index, so needs an upgrade of nrfutil itself as well.

@MarkusLassila: Could you run nrfutil self-upgrade and nrfutil upgrade device and try again?

[MarkusLassila]

nrfutil device --version

nrfutil-device 2.7.11 (7005884 2025-01-15)
commit-hash: 70058847a6226212a758c274d19aa8f95dc23cdc
commit-date: 2025-01-15
host: x86_64-unknown-linux-gnu
build-timestamp: 2025-01-16T09:13:44.207691632Z
classification: nrf-external

Detected SEGGER J-Link version: JLink_V7.94i

nrfutil device protection-set All
❌ Failed to set protection on 1057792717, [Probe] Device error: Memory access error at 0x00ffd000. Probably a memory prot
Error: One or more set protection tasks failed:

• 1057792717: [Probe] Device error: Memory access error at 0x00ffd000. Probably a memory protection issue. Probe access is Secure, code: Generic

nrfutil device protection-set SecureRegions
✔️ Protection was set on 1057792717

[bjorgan]

Well, that was disappointing. Sounds like a bug, thanks for discovering this.

I'll contact Markus directly about this so that I don't spam down the PR review with debugging questions.

[juhaylinen]

I can reproduce the Memory access error at 0x00ffd000 error if I try to run nrfutil device protection-set All after flashing an application to the nRF54L15. The command works if nrfutil device recover is run before protection-set All

[MarkusLassila]

The failure seemed to be specific for TF-M builds (/NS) for regular builds, it seemed to work.