nrfjprog -e does not erase nRF9160

RE: nrfjprog -e does not erase nRF9160

JONATHAN LL — Fri, 16 Oct 2020 07:04:34 GMT

Hi,

Update on issue:
A new release of nrfjprog v10.11.0 will fix the issue and its due to release within October.

regards,
Jonathan

RE: nrfjprog -e does not erase nRF9160

JONATHAN LL — Wed, 23 Sep 2020 13:48:08 GMT

I am able to reproduce the problem on both Windows and Linux. Where nrfjprog -e does not successfully erase when building a non-secure application.

Reverting to 10.5.0 fixed the issue with nrfjprog -e not working properly.
However the nrfjprog --recover worked on both 10.9.0 and 10.10.0.

Regards,
Jonathan

RE: nrfjprog -e does not erase nRF9160

Daniel Veilleux — Wed, 23 Sep 2020 00:09:41 GMT

I also see pynrfjprog 10.10.0 failing to erase all or sector erase with python 3.8. Using the recover operation or rolling pynrfjprog back to 10.5.0 are workarounds.

RE: nrfjprog -e does not erase nRF9160

JONATHAN LL — Mon, 21 Sep 2020 06:52:41 GMT

New version of nrfjprog, its now at 10.10.0, could try that.

Can you read the device memory using Programmer app before and after you have tried nrfjprog -e of --recover. Does it show if anything has changed?

nrfjprog --halt, could you try this and se if it actually halts the Feather board?

Do you have the same behavior if you test with another board? for example if you have another nrf9160DK that you can replace with your Feather board?

I will talk to my colleague about this and se if there is any known similar issues on OSX. The behaviour seems odd.

Regards,
Jonathan

RE: nrfjprog -e does not erase nRF9160

Jared — Fri, 18 Sep 2020 14:59:57 GMT

[quote userid="91187" url="~/f/nordic-q-a/65958/nrfjprog--e-does-not-erase-nrf9160/270353"]Do you get the same behavior if you use nrfjprog --recover ?
[/quote]

I thought it may have done it but I still have to erase using the Programmer app. Looking at the debug output, it appears to be using the same J-link library as nrfjprog.

RE: nrfjprog -e does not erase nRF9160

JONATHAN LL — Fri, 18 Sep 2020 13:46:19 GMT

Hi Jared,

Do you get the same behavior if you use nrfjprog --recover ?

Regards,
Jonathan

RE: nrfjprog -e does not erase nRF9160

Jared — Thu, 17 Sep 2020 16:29:14 GMT

Thanks for the suggestion Jeff.

Unfortunately, even after an upgrade, it's still exhibiting the same issue:

nrfjprog --version
nrfjprog version: 10.9.0 
JLinkARM.dll version: 6.84a

My best guess it's something to do with nrfjprog not the JLink library.

Jared

RE: nrfjprog -e does not erase nRF9160

Jeff4BLE — Wed, 16 Sep 2020 23:55:03 GMT

Hi Jared,

It's possible that nRF Connect for Desktop is using a different j-link driver than the command-line shell. So updating the JLINK driver is my first recommendation too.

Because the nRF Connect for Desktop programs the device, it can be assumed that the device selection switch (SW5) is in the correct position. However, when using the nRF9160-DK is a good idea to use the "family" flag to ensure the program is communication to the nRF9160 and not the nrf52 For example, >nrfjprog -f NFR91 -e

Cheers,

Jeff

RE: nrfjprog -e does not erase nRF9160

Jared — Wed, 16 Sep 2020 21:18:23 GMT

After some more playing, It seems to happen in a very certain instance during LWM2M bootstrapping. Only after being bootstrapped does it seem to fail to erase using the CLI. I'll try to figure out some type of reproducible test case.

RE: nrfjprog -e does not erase nRF9160

Jared — Wed, 16 Sep 2020 14:43:09 GMT

[quote userid="91187" url="~/f/nordic-q-a/65958/nrfjprog--e-does-not-erase-nrf9160/269900"]I am unsure what you meant by SB32. https://infocenter.nordicsemi.com/topic/ug_nrf91_dk/UG/nrf91_DK/solder_bridge_configuration.html
What version of the DK are you using?[/quote]

Ahh I misread it. It's SB37. I'm using 0.9.0.

[quote userid="91187" url="~/f/nordic-q-a/65958/nrfjprog--e-does-not-erase-nrf9160/269900"]if you do a nrfjprog -e and then connect the device to Programmer app and read the memory from the Feather device does it sow empty or show some partitions whit a application? [/quote]

I'll give it a shot and get back to you on this.

[quote userid="91187" url="~/f/nordic-q-a/65958/nrfjprog--e-does-not-erase-nrf9160/269900"]I currently do not have a Feather device so cant test this now, but if it is as you say I will see if I can get a hold of one and test it myself. [/quote]

Production is underway. I should have a handful if it comes to this. Here are all the files related to the design. Not much going on in there that could affect this (IMHO): docs.jaredwolff.com/nrf9160-downloads.html

RE: nrfjprog -e does not erase nRF9160

JONATHAN LL — Wed, 16 Sep 2020 13:41:13 GMT

Hi Jared,

I am unsure what you meant by SB32. https://infocenter.nordicsemi.com/topic/ug_nrf91_dk/UG/nrf91_DK/solder_bridge_configuration.html
What version of the DK are you using?

The programmer is open source and it uses nrfjprog if you want to take a look at how the GUI is built, and version 1.4.5 was released today and should be available.

if you do a nrfjprog -e and then connect the device to Programmer app and read the memory from the Feather device does it sow empty or show some partitions whit a application?

I currently do not have a Feather device so cant test this now, but if it is as you say I will see if I can get a hold of one and test it myself.

Regards,
Jonathan

RE: nrfjprog -e does not erase nRF9160

Jared — Wed, 16 Sep 2020 12:52:45 GMT

Hey Jonathan

Thanks or the answer. I actually jumped SB32 on the DK, so there never should be a case when the on-board device is being erased.

Curiously, the erase command in the nRF Desktop Programmer App *does* erase the device. So I'm not sure what the difference is between the CLI and the GUI are but there's something!

Thanks

Jared

RE: nrfjprog -e does not erase nRF9160

JONATHAN LL — Wed, 16 Sep 2020 10:41:07 GMT

Hi Jared,

I have had more success using the following routine:
nrfjprog -r
nrfjprog -e

and do a hard reset on both devices.

make sure that the 9160DK is not he one targeted. Load a application on the nrf9160Dk that has a blinking led or something that you can easily see is running on the device. Then when you run the nrfjprog -e you will quickly see that which device is being erased, if it is the DK or the Feather board.

Latest version of JLinkARM is 6.84 I think so maybe consider updating.

Regards,
Jonathan