nRF Connect for Desktop Bluetooth Low Energy Standalone v4.0.4 - freezing on "Found device type: unknown. J-Link firmware: J-Link OB-nRF5340-NordicSemi compiled Dec 3 2012 15:46:49

[jbeh444]

When using the software, the app freezes on - Found device type: unknown. J-Link firmware: J-Link OB-nRF5340-NordicSemi compiled Dec 3 2012 15:46:49.

If I first flash any program using vs code, then try the Bluetooth app again it no longer freezes and finishes the setup of the device. Has anyone experienced this or what other information do you need to help me resolve this issue.

[Øyvind]

Hello, 

unknown. J-Link firmware: J-Link OB-nRF5340-NordicSemi compiled Dec 3 2012 15:46:49.

What version of the JLink FW are you running? From the text attached it seems that you are on a fairly old version. Can you open a terminal or command prompt to run "nrfjprog --version", and provide the output here. 

What version of nRF Command Line Tools did you install with the nRF Connect for Desktop?

Kind regards,
Øyvind

[jbeh444]

Hello,

running "nrfjprog --version":

nrfjprog version: 10.19.0 external
JLinkARM.dll version: 7.80c

I am not sure what version of command line tools I downloaded.

I am currently installing 10.19.0 windows x86 64 to see if this may fix my issue.

Thank you very much for your prompt response.

[jbeh444]

After flashing with blinky program:

15:14:19.569

Device closed. --Flashed blinky onto board then retried--

15:15:48.249

Selected device with s/n 001050346905

15:15:55.062

Uploading image through JLink: 0%

15:15:57.243

Uploading image through JLink: 100%

15:15:57.449

Device programming completed.

15:15:58.764

Device setup completed

15:15:58.764

Getting information from J-Link debugger...

15:15:58.764

Found device type: unknown. J-Link firmware: J-Link OB-nRF5340-NordicSemi compiled Dec 3 2021 15:46:49.

15:16:00.172

Connectivity firmware version: 4.1.4. SoftDevice API version: 5.

15:16:00.172

Opening adapter connected to COM5

15:16:01.000

Successfully opened COM5. Baud rate: 1000000. Flow control: none. Parity: none.

15:16:01.003

Reset performed on adapter COM5

15:16:02.119

Adapter connected to COM5 opened

[Øyvind]

jbeh444 said:

After flashing with blinky program:

Does this mean that you fixed the issue? 

From the log in your other comment

jbeh444 said:

NRFDLException(9): async task failure for id: 715991010640 msg: NOT_AVAILABLE_BECAUSE_PROTECTION

This looks like your device was locked (APPROTECT). Running a nrfjprog --recover should fix this, it erases all user flash memory and disables the readback protection mechanism if enabled.

[jbeh444]

running nrfjprog --recover fixed the issue!! Thank you very much!

[jbeh444]

Was there any way to disable the read back protection? Every time I power off the unit it re-enables the read back protection.

[Øyvind]

Investigating. The SW might not be handling correctly, Reported internally. I will update as soon as I have an answer :)

[TomDavies]

Øyvind is there any feedback on this? We have a OTA jig using a DK that had been working great but the DK was switched out with a newer unit and it's causing issues where it's not being picked up due to programming failing - because it needs to go through the recovery step each time.
We can get this changed but it would be great to get an official response on whether this will be addressed or not.