nRF53 Device is Protected after programming and I cannot debug

RE: nRF53 Device is Protected after programming and I cannot debug

Sigurd — Mon, 07 Jun 2021 11:22:15 GMT

Try uninstall Segger J-link, and then run the nRF Command Line Tools installer again,

https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download#infotabs

RE: nRF53 Device is Protected after programming and I cannot debug

emag nioj — Mon, 07 Jun 2021 11:17:47 GMT

hello thank you!

about nrfjprog

i have this error ERROR: JLinkARM DLL not found. Please reinstall latest JLinkARM.

how to reinstall?

this errr after the update.

RE: nRF53 Device is Protected after programming and I cannot debug

Sigurd — Mon, 07 Jun 2021 10:12:28 GMT

This is handled by the start-up code:

https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/mdk/system_nrf53_approtect.h

https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/mdk/system_nrf5340_application.c#L233

https://github.com/zephyrproject-rtos/hal_nordic/blob/574493fe29c79140df4827ab5d4a23df79d03681/nrfx/mdk/system_nrf5340_network.c#L87

If you have a nRF5340 revision D, I recommend using NCS v.1.5.0, or higher, and make sure to use the latest version of nrfjprog.

RE: nRF53 Device is Protected after programming and I cannot debug

emag nioj — Tue, 01 Jun 2021 13:18:39 GMT

here i haven't hard fault i can check just because the uploaded firmware seems to work

but the flash in net core when updated programmatically seems to be erased after, but i haven't a way to verify.

i m thinking to not continue i have other projects delayed

RE: nRF53 Device is Protected after programming and I cannot debug

nsga333 — Tue, 01 Jun 2021 11:22:52 GMT

Hi emag nioj

How did you manage to get that to run - i got a hard failt as soonas i tried to set NRF_CTRLAP_NS->APPROTECT.DISABLE and NRF_CTRLAP_S->APPROTECT.DISABLE

Thanks

RE: nRF53 Device is Protected after programming and I cannot debug

emag nioj — Tue, 01 Jun 2021 10:08:06 GMT

But in nrf5340 revision A it was working all very good. Debugging Net Core was very simple.

Now with revision D i m wasting lot of time.

i have added this

NRF_NVMC_NS->CONFIG = (NVMC_CONFIG_WEN_Wen << NVMC_CONFIG_WEN_Pos);
while (NRF_NVMC_NS->READY == NVMC_READY_READY_Busy) {};
NRF_UICR_NS->APPROTECT=0x50fa50fa;
while (NRF_NVMC_NS->READY == NVMC_READY_READY_Busy) {}
NRF_NVMC_NS->CONFIG = (NVMC_CONFIG_WEN_Ren << NVMC_CONFIG_WEN_Pos);
while (NRF_NVMC_NS->READY == NVMC_READY_READY_Busy){};
NRF_CTRLAP_NS->APPROTECT.DISABLE=0x50fa50fa;

in NET core at main function

and this in APP main

NRF_NVMC_S->CONFIG = (NVMC_CONFIG_WEN_Wen << NVMC_CONFIG_WEN_Pos);
while (NRF_NVMC_S->READY == NVMC_READY_READY_Busy) {};
NRF_UICR_S->APPROTECT=0x50fa50fa;
while (NRF_NVMC_S->READY == NVMC_READY_READY_Busy) {}
NRF_NVMC_S->CONFIG = (NVMC_CONFIG_WEN_Ren << NVMC_CONFIG_WEN_Pos);
while (NRF_NVMC_S->READY == NVMC_READY_READY_Busy){};
NRF_CTRLAP_S->APPROTECT.DISABLE=0x50fa50fa;
NRF_CTRLAP_S->SECUREAPPROTECT.DISABLE=1;

so i m expecting to attach the debug without problems but not.

So HOW TO DO?

Thank you!

RE: nRF53 Device is Protected after programming and I cannot debug

emag nioj — Tue, 01 Jun 2021 09:59:49 GMT

every time there is a reset the protection goes on erasing all automatically.

It's a lot disturbing, now i need to update the NET core but i m not able to debug.

I enable FLASH ERASE then writing 0xFFFFFFFF on 0xFFFFF000 boundaries then the page is erased ready to write the code. In APP it's ok in NET no but how to debug????

RE: nRF53 Device is Protected after programming and I cannot debug

nsga333 — Tue, 01 Jun 2021 09:55:45 GMT

Not I am using the Programmer built into nRF Connect and just drag the images in so I wouldn't expect an issue.

As soon as i program the device the nRF Connect programmer reports it as protected

RE: nRF53 Device is Protected after programming and I cannot debug

nsga333 — Tue, 01 Jun 2021 09:50:42 GMT

I am using nRFProg to write the image through a Segger j-link ( I have upgraded to the latest Segger as well). This works fine with the older nRF52 boards. and also when i program a PDK. But as soon as I program our target the nRFProg reports that the device is locked.

Next time i wish to program the device i have to do an erase all to unlock it. I have seen it work for an hour or a few hours such that i can program it and it comes back unlocked so that i am able to debug it but after a period, maybe the next day it wil revert to programming as locked

RE: nRF53 Device is Protected after programming and I cannot debug

emag nioj — Tue, 01 Jun 2021 09:35:47 GMT

I m stuck i try to attach the debug the flash erases. Sometime it works other not.

I have the NET core that needs to update the firmware flash and it's impossible to debug it.

problems:

- it's not clear if it's possible to write the NET core from the APP core in case of yes it makes firmware update simpler.

- it's not clear how to disable protection from firmware to let debug to attach in NET core

- the info in the datasheet are not clear about lot of protect and disable protect and flash uicr bah!!!!

I'll abandon nr5340 to many time wasted in problems not related to the development of the code

bye

RE: nRF53 Device is Protected after programming and I cannot debug

Sigurd — Fri, 28 May 2021 16:02:34 GMT

Hi,

How are you flashing the device? With nrfjprog or west?

Take a look at the commands on this page on how to flash the image:

http://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/nrf/ug_nrf5340.html#programming-from-the-command-line

RE: nRF53 Device is Protected after programming and I cannot debug

nsga333 — Thu, 27 May 2021 15:35:46 GMT

I have subsequently gone back into the situation where the segger reports the following:

Any suggestions?