nRF5340 Debug Probe to Nordic Thingy:53 - nRF Connect, nRF Programmer Error: Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.

[Droteer]

I am using Nordic Thingy:53 to build a Matter application using Matter Ecosystem. 

Flashing applications via Bluetooth on nRF Programmer mobile application works great.

But flashing via VS Code or via the nRF Programmer in nRF Connect on PC does not work as describe in this https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/working_with_nrf/nrf53/thingy53_gs.html at "Updating through external debug probe"

nRF5340-DK is connected with Data Usb-cable and has also been tested and is working fine. Programs have been flashed on the DK successfully and is working

JLink_V7.66a is installed as required by nRF Programmer and Nordic Thingy:53 is connected via the 2x5 Debug Out connector on the DK as shown in the picture in "Updating through external debug probe" section at the link above. 

In nRF Programmer the device shows up as J-Link 001050072180 in the dropdown bar as shown in the image below.

But when connecting to this device (which should be the Thingy:32 through the Debug Probe I recon) I get this error 

10:19:12.920

Using nrf-device-lib-js version: 0.5.0

10:19:12.921

Using nrf-device-lib version: 0.13.11

10:19:12.921

Using nrfjprog DLL version: 10.18.2

10:19:12.921

Using JLink version: JLink_V7.66a

10:19:19.133

Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.

I therefor cannot read, write or do anything with the Thingy:32 in the nRF Programmer. And in VS Code I get a similar error when trying to build the application similarly using the same Debug Probe connection and the method describe in https://nrfconnect.github.io/vscode-nrf-connect/get_started/build_app_ncs.html 

The error have been shown on two different Operating Systems using the same setup. Both on Windows 11 64 Bit and on Macbook Pro using macOS Ventura

Setup:

   nRF Connect SDK v2.2.99-dev3

   nRF Connect for Desktop v4.0.0

   nRF Programmer official, v3.0.7

   J-Flash V7.66a

   Nordic Thingy:53

   Nordic nRF5340-DK

   Usb Cable with Data on nRF USB outage on nRF5340 and Usb Cable without Data for the External Supply outage on nRF5340

  Operating System: Windows 11 64Bit and macOS Ventura

Tried Solutions:

   Downgrading nRF Connect to earlier versions as describe in previous similiar thread, here  Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device. 

   Used a different Nordic DK card

   Updated nRF Command Line Tools to latest version

   Tested software individually on both Thingy:32 and nRF5340-DK to ensure that they both work separately. 

   Searched around on similar errors and other similar issue's solutions did not work.

   Comments on this Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device. Seems to have the same issue but not received help for over a year, it seems

[Droteer]

Hey!

Switching the Power Source to VDD worked! 

I tried to flash the program on VS Code now, and it worked without any issues.

However, im not allowed to write anything using nRF Connect Programmer. The connection works now, but I am only allowed to read.

I clicked on "Add File", and choose the Zip file for the preCompiled Matter Weather Station and loaded it.

But I am not allowed to write.

Also, maybe not that it matters anymore. But this is what I get now from running the same "nrfjprog --memrd 0x00FF0204 --n 8" from earlier.

Do you know why that is with nRF Connect? Also, why were I not allowed to use the USB for the Power Source? Is it a bug in the hardware, or is it intentional?

[Einar Thorsrud]

Hi,

Droteer said:

I clicked on "Add File", and choose the Zip file for the preCompiled Matter Weather Station and loaded it.

But I am not allowed to write.

The Precompiled application firmware zip's contains upgrade image for use with DFU via a bootloader (via USB or BLE). You cannot program them via a debugger (and things like the bootloader is missing). For that, you need hex files you get when you build the project.

Droteer said:

Also, maybe not that it matters anymore. But this is what I get now from running the same "nrfjprog --memrd 0x00FF0204 --n 8" from earlier.

No, it is not relevant. The point was just to read a number that was unique for each device so that it would be easy to see if you were able to debug the Thingy and not accidentally were communicating with the nRF on the DK.

Droteer said:

Also, why were I not allowed to use the USB for the Power Source? Is it a bug in the hardware, or is it intentional?

When you supply via USB the high voltage regulator is used, and the VDD is lower. And you need to have the same VDD voltage on the DK and the Thingy in order to be able to debug it (so that the logical high levels on the SWD lines are the same seen from both devices).

[Droteer]

Hi

I see, thanks a lot! 

I view this thread as solved now. Thanks for the fast and efficient help. But I think that it could be beneficial if it was included in this Doc https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/working_with_nrf/nrf53/thingy53_gs.html at "Updating through external debug probe" section that the DK needs to be set to VDD for the connection to work. I could see this error being made quite easily and hard to realize

Thanks a lot for the help!

Cheers!

[JoseJavier]

Hello, I have a similar problem. I have the same set up:

Setup:

   nRF Connect SDK v2.3.0

   nRF Connect for Desktop v4.0.1

   nRF Programmer official, v3.0.8

   J-Flash V7.66a

   Nordic Thingy:53

   Nordic nRF5340-DK

   Usb Cable with Data on nRF USB outage on nRF5340 and Usb Cable without Data for the External Supply outage on nRF5340

  Operating System: Windows 11 64Bit

This is my connection:

This is from the Programmer view:

I run the command: nrfjprog --memrd 0x00FF0204 --n 8 and I got this:

$ nrfjprog --memrd 0x00FF0204 --n 8 --log
[error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 342 milliseconds with result -102
ERROR: Unable to connect to a debugger.
[error] [ Worker] - An unknown error.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

I tried to resert the thingy presing theSW2 and the switching on but I can't see it anymore on the Programmer. Could you help me?

[Einar Thorsrud]

Hi,

I don't see any obvious issues with your setup. Can you try to double-check the connections, and perhaps try another 10 pin cable if you have one? Also, if you have another DK or Thingy, see if you are able to debug that using the debug out port of the DK?