Flash memory protection when debugging

[Tage Korsdal Nielsen]

Hi

I am moving an application to nRF54L15DK.

SDK is v3.2.2, single core only, no sysbuild.

Whenever I try to debug I get:

-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
-- runners.nrfutil: Flashing file: c:\dev\bluejay\ble\bluejay\b_0121_pd_ne_nrf54\zephyr\zephyr.hex
-- runners.nrfutil: Connecting to probe
-- runners.nrfutil: Programming image
Error: One or more batch tasks failed:
* 1057733518: Device error: Memory access error at 0x00000480. Probably a memory protection issue. Probe access is Secure (Generic)

I can program the flash using 'west flash --recover' - and the apps seems to be running (alrhough I don't get trace output).

But how do I debug? Do I need to add --recover to the debug command, and if so, how do I do that?

Rgds Tage

[Amanda Hsieh]

Hi Tage, 

Check out How to recover a device with readback protection. 

Regards,
Amanda H.

[Tage Korsdal Nielsen]

One follow-up question: I need to do a recover each time I start debugging my own application (ported from the nRF52), whereas that is not necessary for e.g. the peripheral_lbs sample.

There must be some config or overlay that can stop this?

rgds Tage

[Amanda Hsieh]

You can add the following configs to avoid needing a recover every time. 

CONFIG_NRF_APPROTECT_DISABLE=y
CONFIG_NRF_SECURE_APPROTECT_DISABLE=y
CONFIG_FPROTECT=n

[Tage Korsdal Nielsen]

Hi Amanda,

Thank you.

This does not seem to do it - the first recover from the old build was expected, but following attempts to debug all required recover.

Rgds Tage

[Amanda Hsieh]

Could you check the .config under build/app_name/zephyr to verify those configs?

See Configuration overview in the nRF Connect SDK. 

[Tage Korsdal Nielsen]

From autoconf.h:

#define CONFIG_NRF_APPROTECT_DISABLE 1

#define CONFIG_NRF_SECURE_APPROTECT_DISABLE 1

The CONFIG_FPROTECT is not found in autoconf.h - this one is:

#define CONFIG_FPROTECT_BLOCK_SIZE 0x1000

I guess the settings is ok in the build output?

[Amanda Hsieh]

yes. 

I have created a blank application (1727.test.7z) to test, and it can start to debug without requiring to recover every time. Could you run and check whether it works for you? If so, you can use it as the base for your application.