VS Code Connected Devices

[Bryan]

NCS: 2.3.0

OS: Windows 10

VS Code: 1.77.3

My Dell Windows 10 system forced me to reboot to do an update and now VS code does recognize any Segger JLink devices.

nrfjprog is still working, but it would be really nice to be able debug.  I have also done the classic Windows reboot with no change.

[Marte Myrvold]

Hi,

Please provide support information from the VS Code extension:

1. Open the command palette (Ctrl + Shift + P or View > Command Palette).
2. Write "nRF Connect: Generate support information" and press enter.
3. Copy the entire support information output.
4. Upload it here using Insert > Code or upload a .txt file with Insert > Image/video/file.

Make sure to remove confidential information you do not want to be shared in a public case.

If the issue came after updating the nRF Connect for VS Code extension to the latest version, then the issue might be due to nrfutil being used as device provider. You can change this in settings by going to settings > extension > nRF Connect and changing the following to nrfjprog:

Are you using an external debugger, or only the DKs?

Best regards,
Marte

[Dominik]

I think I had the same issue. I changed the device provider and it works for me.

Cheers

[Marte Myrvold]

Hi,

Are you using an external debugger?

Can you provide support information from the VS Code extension by following the steps in my previous reply?

Best regards,
Marte

[Bryan]

Only external Segger JLink debuggers seem to be affected.  If I plug in a Nordic DK, it recognize the device.

I followed your suggestion.  "nrfutil" was selected as the nRF-connect: Device Provider.  Changing it to "nrfjprog" immediately fixed the issue!

Thanks everyone for the help!

[Marte Myrvold]

Hi,

The developers have released a fix for the issue. Please update the extension, and let me know if you still experience issues with the latest version.

Best regards,
Marte

[Bryan]

Looks good - Thanks.