nrfjprog --ids not finding board

[bluetooth_mdw]

I'm trying to flash a Nordic Thingy. I have it connected to the debug port of a nRF52840-DK, nrfjprog --ids lists no boards, however.

C:\workspaces\zephyr_source\zephyr\samples\hello_world>nrfjprog --ids

C:\workspaces\zephyr_source\zephyr\samples\hello_world>pyocd list

However pyocd produces:

C:\workspaces\zephyr_source\zephyr\samples\hello_world>pyocd list
## => Board Name | Unique ID
-- -- ----------------------
 0 => nRF52840-DK [nrf52840] | 110200005020312032413650313034313031303897969903

And yes, I have switched the Thingy on when testing :-)

[Jørgen Holmefjord]

Hello!

Is it possible that you flashed the interface MCU chip on the DK with a DAPLink FW? I tested PyOCD on one of my DK, and it did not list any devices (while nrfjprog did). After flashing this firmware, the nRF52840 DK is listed in PyOCD, but not by nrfjprog.

You can find the default J-Link OB Interface MCU firmware on nRF52840 DK download page. Hold "IF BOOT/RESET" while powering the board, and drag the downloaded BIN file to removable drive named "BOOTLOADER", to flash the firmware.

Best regards,
Jørgen

[bluetooth_mdw]

Hi Jorgen.... anything's possible! Although I don't remember doing that. Anyway, I flashed J-Link OB-SAM3U128-V2-NordicSemi 170724.bin to the board just now but unfortunately nrfjprog -i still does not list the board. pyocd list now says "No available debug probes are connected".

However! I unplugged from USB, connected again and... now nrfjprog -i works :-)

Thanks for your help

Martin

[Jørgen Holmefjord]

Great that you got it working again!

I forgot to mention that you need to power cycle the board after updating the FW, to continue normal operation :-)

[bluetooth_mdw]

All good. If I'd got half a working brain this morning, I'd have known to do that anyway :-)