Cannot use NRF4340-DK as external debug probe for Thingy 53

[Wladymir Brborich]

Hi! I'm currently trying to flash custom firmware in the Thingy53. As suggested here I'm using the NRF5340-DK as an external debug probe. When I try to flash it with the programmer I get the following error:



I Have tried to run:

nrfjprog -v
nrfjprog version: 10.24.2 external
JLinkARM.dll version: 7.96t

nrfjprog --log --memrd 0x00FF0204 --n 8

[error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 412 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.

With no luck.

I have also tried to update Jlink to the latest version, and some intermediate versions as well with no luck.

I'm running macOS Sonoma 14.6.1

Here is a picture of my setup:

Any advice or help will be really apperciated!

[Priyanka]

Hi,

Could you tell me your nRF Connect for Desktop and Programmer versions?

Please make sure that you have connected the JTAG cable properly and not inverted.

Did you try with the pre-compiled application firmware? Were you able to flash this?

Have you used the DK or the Thingy before?

Regards,

Priyanka

[Wladymir Brborich]

Hi,

Thanks for the reply, Here is a screenshot of the nRF Connect and Programmer apps. I downloaded the latest ones.

The JTAG cable is keyed so I think is connected properly. (Just in case I connected it with the opposite orientation and I get the same error)

I have been able to flash the Thingy with the pre-compiled firmware via USB with MCUBoot, but not using the DK as a debug probe.

Both the Thingy and DK are brand new, out of the box.

[Priyanka]

Hi,

Could you try to recover both cores?

nrfjprog --recover --coprocessor CP_NETWORK && --recover
nrfjprog --recover

-Priyanka

[Wladymir Brborich]

Hi,

I can do it without the Jtag cable connected, If I connect the cable to the debug out port it does not let me run the command

This is with the cable connected

nrfjprog --recover --coprocessor CP_NETWORK && nrfjprog --recover
[error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 483 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.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

This is without the cable

 nrfjprog --recover --coprocessor CP_NETWORK && nrfjprog --recover
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.

After recovering it the same error persists:

nrfjprog --log --memrd 0x00FF0204 --n 8
[error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 488 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.

Maybe I'm using the wrong cable? Could you recommend the exact one that I need?

[Priyanka]

Hi,

From the picture it looks like you are using the correct JTAG cable. Do you have another one of the same, just to verify that it's not this particular cable's fault?

[Wladymir Brborich]

HI,

Sure I'm going to try and get another cable over the weekend. Thanks a lot!

[Wladymir Brborich]

Hi,

Ok, another cable seems to work. Now I don't get the error, but I can't write to the thingy using VSCode when I flash a simple hello world program it seems to do it to the DK.

Best regards.

[Priyanka]

Hi,

Do you mean that when you try to write to the Thingy, it gets written to the DK? 

-Priyanka