vscode nrf Connect no devices found

[Roedy]

I've been using my segger jlink base compact with vscode and the nrfconnect extension.  Everything was working fine, but suddenly, my board stopped showing in the connected devices.  

Normally I would suspect some driver or configuration error, but

• if I plug in a nrf5340 dev kit, it shows up in vscode nrfconnect panel.  
• I can still use nrfjprog to interact with my custom board (recover, erase, etc)
• I can still flash the board with the west utility
• the jlink shows up in nrf connect programmer and I can interact with my board using it.

I'm left to assume that all of the hardware is working correctly, but there is some sort of vscode config is broken.

Things I've tried:

• I updated my nrf command line tools to 10.21.0 Linux x86 64 according to this post  VSCode nRF Connect Extension: Connected Devices not Detecting Devices 
• restart vscode
• reboot computer
• delete my ${HOME}/.vscode folder and reinstall nrf connect extension
• updated all packages on my system to latest (I'm using debian bullseye)

Anyone have some insight on this?

[fabien-ch]

I have the same problem since yesterday too. I tested the SDK upgrade and downgrade nrfjprog but I can't get anything. nrfjprog does not detect anything but the jlink is detected.

[fabien-ch]

Can you see in nrf connect fort extension settings :

[Roedy]

Yes!  It took me a while to find those settings.  I got there from the welcome page 

[ErwinNoordhuis]

I had the same problem. suddenly after the lunchbreak VSCode didnt see my device anymore. this fixed it. Thanks

[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

[henning larsen]

thanks fabien-ch  the fix works nicely

- This is  second time I see this. but why does this problem keep popping up when doing an update of the tool - it appears.(Win11 latest vs-code and SDK2.4)?

Ought to be fixed by now.

[Marte Myrvold]

Hi henning larsen ,

This should have been fixed, but it might be a similar issue.

Can you create a new ticket for this issue where you add information about which board you are using (custom or DK), which external debugger if you are using any, and upload the support information?

To get support information from VS Code, do the following:

• Open the command palette (Ctrl + Shift + P or View > Command Palette).
• Write "nRF Connect: Generate support information" and press enter.
• Copy the entire support information output.
• Upload it in the new ticket 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.

Best regards,
Marte

[henning larsen]

Hi Marte,

Sure I could when/if I see it again. I assume it is when updating the tools.

Hint: It is likely the default value of the parameter (forgot what this parameter is called but you will know) which ought to be set to nrfjprog after update, but I notice that the default ("default" written in light gray) next to entry nrftools. So manually changing to nrfjprog solves the issue in both cases I have experienced. This was win11. First case was either win10 or ubuntu - sorry forgot which one.

But again - it is not something I would be able to reproduce - the fallback to the nonworking default, that is.

Changing parameter to nrftools is (obviously) easy once you know and it will fail with same error but that is not the problem.

br henning