recover nrf52 DK

RE: recover nrf52 DK

AHaug — Mon, 10 Jul 2023 11:53:23 GMT

Hi,

Håkon is out of office now on vacation for the next weeks. Based on what I can see and what Håkon states it looks like this latest issue is a new issue. I recommend you to create a new case and we will assign it to an available engineer to look into it over the summer. Do however note that we're in the main summer vacation period here in Norway, so responses will be slower than usual until mid August.

Kind regards,
Andreas

RE: recover nrf52 DK

Neum_d — Thu, 06 Jul 2023 15:38:54 GMT

Yes. If I switch back to the old MDK 8.24.1, I can write into internal flash, but no more, if I use 8.53.1. Then, fds.c::record_header_write_begin() does not return and the whole system hangs (until watchdog causes reboot), even if fds_record_update() is called in the context of app_scheduler.

RE: recover nrf52 DK

Håkon Alseth — Thu, 06 Jul 2023 14:35:28 GMT

The handling of approtect is done in the startup files, so no need to add anything in your application when using MDK v8.40.2 or newer.

[quote user="Neum_d"]MDK 8.53.1 prevents me to use FDS to store data into flash.[/quote]

How do you mean? You're not able to write to internal flash from the mcu anymore? This sounds like a different issue.

Kind regards,

Håkon

RE: recover nrf52 DK

Neum_d — Thu, 06 Jul 2023 12:05:31 GMT

I just saw that updating to MDK 8.53.1 prevents me to use FDS to store data into flash. I assume I have to take additional steps to re-enable it. I opened with NRF_UICR->APPROTECT = APPROTECT_DISABLE_DISABLE_SwDisable, but no success. I assume, I have to change some other things too, is there a porting guide for the MDKs?

RE: recover nrf52 DK

Neum_d — Wed, 28 Jun 2023 12:42:55 GMT

Thanks. I updated MDK and nrfjprog and now it seems to work. I have to check, if my program does the things still correct.

BTW: The connectivity firmware which comes with nrfutil 6.1.7 seems to use a MDK which is too old...

RE: recover nrf52 DK

Håkon Alseth — Wed, 28 Jun 2023 08:02:51 GMT

Hi,

[quote user="Neum_d"]

If I understand the linked explanation correct, I just add NRF_UICR->APPROTECT=0xFF; to my main() ?

[/quote]

That will lock down the device, so that you'll need to recover each time you reprogram.

Set it to 0x5AUL; to open it up.

It is strongly recommended that you update to MDK version 8.40.2 or later:

https://www.nordicsemi.com/Products/Development-tools/nRF-MDK

[quote user="Neum_d"]I use nrfjprog version 10.12.2:[/quote]

Could you try to update nrf-command-line-tools to a newer version?

Kind regards,

Håkon

RE: recover nrf52 DK

Neum_d — Tue, 27 Jun 2023 13:13:32 GMT

If I understand the linked explanation correct, I just add NRF_UICR->APPROTECT=0xFF; to my main() ?

I use nrfjprog version 10.12.2:

$ nrfjprog -v
nrfjprog version: 10.12.2 
JLinkARM.dll version: 6.88a

RE: recover nrf52 DK

Håkon Alseth — Tue, 27 Jun 2023 12:24:50 GMT

Hi,

With newer revisions of the nRF52 SoC family, a hardened approtect is added, which requires handling in the firmware to open up the debugger session:

https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev3/ERR/nRF52832/Rev3/latest/config_832_249.html?cp=5_2_1_0_2_0

Is your firmware compiled with newer startup files (MDK)?

[quote user=""]So I run nrfjprog --recover -f nrf52.
After that, I try to flash my FW, but nrfjprog returns[/quote]

which version of nrfjprog are you using? Could you share the output of "nrfjprog -v"?

Kind regards,

Håkon