JLink loading into a secured nRF54 device

[bios-bob]

i'm working "bare-metal" with the nRF54-DK, loading from the command-line by directly calling JLink....

often (but not always) i receive the following message from JLink:

clicking through this, my image loads just fine....

is there something i should do in my target firmware to "unsecure" the device???

at this stage, i'm in development and am constantly re-flashing my HW

[hmolesworth]

Not sure if this will help, but this is what I use:

// nrf54L15 UICR Arm Cortex-M33
// ============================
// To program a hex file:
// In .\nRF5_SDK_17.1.0_ddde560\examples\peripheral\blinky\pca10156\blank\iar\_build
//  nrfjprog -v
//    nrfjprog version: 10.24.2 external
//    JLinkARM.dll version: 7.94e
//  nrfjprog --recover
//  nrfjprog --memwr 0x00FFD080 --val 0x00000003
//  nrfjprog --program blinky_pca10156.hex --chiperase --verify -r --log
// Example:
//    .\nRF5_SDK_17.1.0_ddde560\examples\peripheral\blinky\pca10156\blank\iar\_build>nrfjprog --recover
//    Recovering device. This operation might take 30s.
//    Erasing user code and UICR flash areas.
//    .\nRF5_SDK_17.1.0_ddde560\examples\peripheral\blinky\pca10156\blank\iar\_build>nrfjprog --memwr 0x00FFD080 --val 0x00000003
//    Parsing parameters.
//    Writing.
//    .\nRF5_SDK_17.1.0_ddde560\examples\peripheral\blinky\pca10156\blank\iar\_build>nrfjprog --program blinky_pca10156.hex --chiperase --verify -r --log
//    [ #################### ]   0.263s | Erase file - Done erasing
//    [ #################### ]   0.197s | Program file - Done programming
//    [ #################### ]   0.072s | Verify file - Done verifying
//    Applying system reset.
//    Run.

[bios-bob]

long story, but i'm using the jlink CLI directly and not `nrfjprog`....  any hint as to what i need to do???  sounds like a mass-erase is required???

[Emil Lenngren]

Make sure this line is called in your code at application start: github.com/.../system_nrf54l.c. It opens up the debugger.