VSCode Connected Devices sees the dev board, but not the target

RE: VSCode Connected Devices sees the dev board, but not the target

Menon — Thu, 23 May 2024 08:44:24 GMT

Hello,

I am glad to hear that it worked for you.

Kind Regards,

Abhijith

RE: VSCode Connected Devices sees the dev board, but not the target

brianh — Wed, 22 May 2024 13:56:21 GMT

OK, good news. I followed the instructions given in the "Incorrect J-Link USB Driver Installed" link that you provided. And this has fixed the problem.

It was slightly more complicated though, because in the first step where it says:

"Locate the J-Link USB device that has just been added when J-Link was connected"

there was no such J-Link device enumerated in device manager. All I had was the COM port, and there was also this device - which I believe is related to the J-Link in some way and was showing up as a warning:

The only way I was able to follow the instructions was to plug in a proper J-Link plus debugger (not the dev board) and then I did indeed see a J-Link device appear:

From there I was able to follow the rest of the instructions to update the driver. And, having done that, when I connect the dev board the BULK interface warning entry has gone, and I am able to see the target appear in "Connected Devices" in VSCode.

Thanks for your assistance and I hope that someone else who stumbles across this issue will also find the dialogue useful.

RE: VSCode Connected Devices sees the dev board, but not the target

Menon — Wed, 22 May 2024 11:04:19 GMT

Hello,

I am not sure why this is happening; the message from the programmer does not give much idea.

But I doubt this might be an issue because of the installed USB driver. So please go through the Incorrect J-Link USB Driver Installed page from Segger and follow the steps mentioned. I also recommend following this page explaining why J-Link cannot connect to the CPU. Were you able to recover the device? Try nrfprog --recover --log.

Kind Regards,

Abhijith

RE: VSCode Connected Devices sees the dev board, but not the target

brianh — Wed, 22 May 2024 09:44:34 GMT

Thanks for the response Abhijith,

When I connect my dev board to the work PC, it enumerates as a COM port in device manager as expected.

I have installed the nRF Connect programmer app. When I launch it and click "connect device", it sees the board but then fails with a complaint "NO_EMULATOR_CONNECTED". See full log below.

2024-05-22T09:41:05.960Z INFO Initialising nrfutil module: device
2024-05-22T09:41:05.988Z DEBUG Application data folder: C:\Users\brihos\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2024-05-22T09:41:06.019Z DEBUG Sending event "programmer: running nrfutil device"
2024-05-22T09:41:06.020Z DEBUG App pc-nrfconnect-programmer v4.3.0 (official)
2024-05-22T09:41:06.020Z DEBUG App path: C:\Users\brihos\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2024-05-22T09:41:06.020Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2024-05-22T09:41:06.020Z DEBUG nRFConnect path: C:\Users\brihos\AppData\Local\Programs\nrfconnect\resources\app.asar
2024-05-22T09:41:06.020Z DEBUG HomeDir: C:\Users\brihos
2024-05-22T09:41:06.020Z DEBUG TmpDir: C:\Users\brihos\AppData\Local\Temp
2024-05-22T09:41:06.723Z DEBUG Sending event "programmer: running nrfutil device"
2024-05-22T09:41:07.693Z DEBUG Sending event "programmer: running nrfutil device"
2024-05-22T09:41:07.693Z DEBUG Sending event "programmer: running nrfutil device"
2024-05-22T09:41:07.714Z DEBUG Sending event "programmer: running nrfutil device"
2024-05-22T09:41:07.804Z INFO Using nrfutil-device core version: 7.7.1
2024-05-22T09:41:08.395Z INFO Using nrfutil-device version: 2.1.1
2024-05-22T09:41:08.395Z INFO Using nrf-device-lib version: 0.17.5
2024-05-22T09:41:08.395Z INFO Using nrfjprog DLL version: 10.24.0
2024-05-22T09:41:08.395Z INFO Using JLink version: JLink_V7.94e
2024-05-22T09:41:08.762Z INFO Getting serialport options from persistent store 000683307548.pc-nrfconnect-programmer
2024-05-22T09:41:08.762Z DEBUG Sending event "programmer: device connected"
2024-05-22T09:41:15.263Z DEBUG Sending event "programmer: running nrfutil device"
2024-05-22T09:41:16.613Z ERROR Error: Failed with exit code 1.
Failed to device info one or more devices:
* 683307548: [jlink] NO_EMULATOR_CONNECTED, code: Nrfjlink.
Message: Operation device-info failed, [jlink] NO_EMULATOR_CONNECTED.
2024-05-22T09:41:16.613Z INFO Using nrfutil device to communicate with target via JLink
2024-05-22T09:41:16.633Z DEBUG Sending event "programmer: device selected"
2024-05-22T09:41:16.633Z DEBUG Sending event "programmer: running nrfutil device"
2024-05-22T09:41:16.946Z DEBUG Sending event "programmer: running nrfutil device"
2024-05-22T09:41:19.854Z INFO Reading readback protection status for Application core
2024-05-22T09:41:19.855Z ERROR Failed to reading readback protection status for application core core. Error: [object Object], message: Batch task protection-get failed, [jlink] NO_EMULATOR_CONNECTED
2024-05-22T09:41:20.046Z ERROR Error: Failed with exit code 1.
One or more batch tasks failed:
- [jlink] NO_EMULATOR_CONNECTED, code: Nrfjlink.
Message: Batch task protection-get failed, [jlink] NO_EMULATOR_CONNECTED.
2024-05-22T09:41:20.046Z ERROR Error: Failed with exit code 1.
One or more batch tasks failed:
- [jlink] NO_EMULATOR_CONNECTED, code: Nrfjlink.
Message: Batch task protection-get failed, [jlink] NO_EMULATOR_CONNECTED.

RE: VSCode Connected Devices sees the dev board, but not the target

Menon — Tue, 21 May 2024 12:32:28 GMT

Hello,

Since it is working fine with another PC, I guess it is not an issue with the nRF52840DK or the VScode extension. See if your device is detected properly inside the PC device manager (see the Ports section inside the device manager). How the nRF Connect programmer app works when you try to read the device. See if the programmer's app is throwing any errors. Also, try to recover your device once and see if this resolves your issue.

Kind Regards,

Abhijith