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

I am quite new to the nRF SDK.  When setting up an nRF project in VSCode, I can build my project but I cannot flash the target.

My target in this case is an nRF52840-DK.

I checked the "Connected Devices" tab, and I can see that the dev board is recognised.  But I don't see any target CPU:

If I open a terminal, JLink is not seeing the target:


I tried another laptop and here everything is better.  I can build and flash the target.  In connected devices, I see the target:

And in the terminal, JLink is seeing the target:

Version of nrfjprog is identical between these two systems.

Unfortunately, the non-working system also happens to be my work laptop Blush my question is, how can I troubleshoot this issue?

Parents
  • 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

  • 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.

Reply
  • 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.

Children
No Data
Related