nrfjprog: --recover does not work

[kobi]

Hello,

I have a nrf5340 PDK .

The kit does not work right, because i got a several errors.

For example in nrf connect v.3.6.1 the PDK is shown as 000000123456 also in

C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog -i
123456

With JLink I also cannot connect to NRF5340_XXAA_NET (to NRF5340_XXAA_APP the connection is successful).

That happens, if i try to connect to NRF5340_XXAAA_NET:

SEGGER J-Link Commander V6.88a (Compiled Nov 18 2020 15:10:56)
DLL version V6.88a, compiled Nov 18 2020 15:09:23

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
Hardware version: V1.00
S/N: 960195344
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.300V

Type "connect" to establish a target connection, '?' for help
J-Link>con
Please specify device / core. <Default>: NRF5340_XXAA_NET
Type '?' for selection dialog
Device>M33
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  F) FINE
  I) ICSP
  C) C2
  T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>4000
Device "NRF5340_XXAA_NET" selected.


Connecting to target via SWD
ConfigTargetSettings() start
ConfigTargetSettings() end
InitTarget() start
CTRL-AP indicates that the device is secured.
For debugger connection the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash, SRAM and UICR of both the application and the network core.

Executing default behavior previously saved in the registry.
Device will be unsecured now.
InitTarget() end
ConfigTargetSettings() start
ConfigTargetSettings() end
InitTarget() start
CTRL-AP indicates that the device is secured.
For debugger connection the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash, SRAM and UICR of both the application and the network core.

Executing default behavior previously saved in the registry.
Device will be unsecured now.
InitTarget() end
ConfigTargetSettings() start
ConfigTargetSettings() end
InitTarget() start
CTRL-AP indicates that the device is secured.
For debugger connection the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash, SRAM and UICR of both the application and the network core.

Executing default behavior previously saved in the registry.
Device will be unsecured now.
InitTarget() end
ConfigTargetSettings() start
ConfigTargetSettings() end
InitTarget() start
CTRL-AP indicates that the device is secured.
For debugger connection the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash, SRAM and UICR of both the application and the network core.

Executing default behavior previously saved in the registry.
Device will be unsecured now.
InitTarget() end
Cannot connect to target.

I tried to recover the PDK with nrfjprog, for example:C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog --recover
ERROR: There is no debugger connected to the PC with the given serial number.

Or: C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog.exe --recover -f NRF53                                                                                                                                    C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog.exe --recover -f NRF53
Recovering device. This operation might take 30s.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.

Or: C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog.exe --coprocessor CP_NETWORK --recover
ERROR: There is no debugger connected to the PC with the given serial number.

Can sb. help?

Thank you!

[Einar Thorsrud]

Hi,

I do not immediately know what is happening, but I wonder which nrfjprog version do you have (nrfjprog --version), and which nRF5340 PDK version do you have (should be printed no the sticker on the large IC on the board)?

[kobi]

Hello,

nrfjprog --version:

nrfjprog version: 10.12.1
JLinkARM.dll version: 6.88a

And nRF5340 PDK version:

0.8.0 

2020.24

Thank you!

[kobi]

I tried it with another computer. The behaviour is still the same. On my second DK i have the same problems. The DK is also not shown in the explorer.

[Einar Thorsrud]

I see. I am not able to make sense of this, to be honest. I have found a few other reports with other DKs where there was an error "ERROR: There is no debugger connected to the PC with the given serial number." even if it was not specified. None of those were ever resolved, though.

Can you let me know more about your platform? It looks like you use Windows, but which version? And which exact PC models (particularly which chipset) have you used to test? It may not be relevant, but anything seems worth checking at this point. 

[kobi]

Yes I use windows.

My Laptop:

HP Elitebook 840 G6, x 64, Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz, 1896 MHz, 4 Core, 8 logische(r) Prozessor(en), Windows 10 Enterprise.

My PC:

Intel Core i7-4790 CPU @ 3,60GHz, 3601MHz, 4 Cores, 8 logische(r) Prozessor(en), Windows 10 Home.

[Einar Thorsrud]

Thanks for the details. I am currently not able to give an explanation for this or suggest a workaround, but I have asked the developers of nrfjprog to look into it. I will let you know as soon as I have some news.

[Einar Thorsrud]

Hi,

The reason for the "ERROR: There is no debugger connected to the PC with the given serial number." error is probably that nrfjprog is not able to properly read the ID of the debugger, and then Segger uses 123456 as the default ID when none is specified.

I assume you are using the onboard debugger on the DK? Or another official Segger debugger? If so, I wonder if the firmware could be corrupted. I suggest you do the following to see if it helps:

1. Start J-Link Configurator:

2. Right click probe in configurator and select "Reset config", then power cycle the board.

If the above doesn't work, you can try "Replace firmware", to reprogram the J-Link chip.

Please let me know if this fixes the issue or not.

[kobi]

Thank you, but it doesn´t work.

That´s the error:

I can´t reset, update or replace the firmware.

[Einar Thorsrud]

I see, that is strange. Did the kit ever work?

[kobi]

Yes, it worked in the beginning.

[Einar Thorsrud]

I see. Has anything particular happened between when it was working and when it stopped? Any SW updates or other changes to anything related to the DK or your computer in general?

[kobi]

I don´t know what happened. I have two other nrf5340pdk kits, which work fine.

After a lot of testing, ich can program the device via Segger Embedded Studios. I can erase and program the kit. But only the buttons, some blinky examples. If I want to work with bluetooth or something like that, it doesn´t work.