Visual studio nRF Connect extension debug does not work

[sokui]

When I clicked the debug action for my app, the following error window popped up.

I followed the below steps to create the app:

1. check my default directory of nRF Connect Toolchain, which is E:\lab\ncs

2. create my app under this folder

3. After I build my firstApp, I clicked debug. Then a window as below popped up:

4. Then I clicked the "Open 'launch.json' button. It said the file is not found, and let me choose which folder to add this file to. I selected firstApp folder. Then it asked me which environment I should use. And I chose nRF Connect. After this, the launch.json is created under this folder:

5. After this, I clicked the debug again. the above error window still popped up.

Does any one know what's the problem? Many thanks

I asked this question in the other thread (devzone.nordicsemi.com/.../questions-for-visual-studio-code-at-sdk-connect-v1-7-0), but have not got the reply. So I create a new one. 

[Marte Myrvold]

Hi,

Where did you install the nRF Command Line Tools, and did you install the 32 bit or 64 bit version?

There is a bug in the VS Code extension making it unable to find the JLink executable because it is not looking in the correct folder if you have installed a 64 bit version of nRF Command Line Tools. The error you are getting might be related to this bug.

Best regards,

Marte

[sokui]

Thanks for replying. How can I check which version I installed? I think I just followed some tutorial from official website for nRF SDK (not NCS). And I guess I downloaded the command line tools from https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download#infotabs. I suspect I installed the 64 bit version.

So could you pls let me know how can I check the installed version? And my windows 10 is 64 bits, should I install the 32 bit version of the command line tools? Thanks

[Marte Myrvold]

Hi,

You can find multiple ways of checking this by searching online, but one of the simplest ways is to inspect the properties of the program or executable. Right click on the file or program -> Properties -> Compatibility. If you check "Run this program in compatibility mode for" you can look at the content of the dropdown menu. If the earliest Windows version is Windows Vista, then the application is 64-bit, while if it is Windows 95, then it is 32 bit. Since your Windows is 64 bit, you should use the 64 bit version. You can also use the 32 bit version, but the 64 bit is recommended.

If you installed the 64 bit version and did not change the installation folder, you should find the JLink executable in C:\Program Files\SEGGER\JLink. Is this where your installation is located?

Best regards,

Marte

[sokui]

Hi, Marte,

Thanks for helping here. I checked, my JLink is 64 bit version. It is installed under E:\Program Files\SEGGER\JLink. Could you please let me know if the installation path causes the visual studio extension to be confused? How can I resolve this?

[Marte Myrvold]

Hi,

The fix for this will be included in the next release of the VS Code extension. In the meantime, you can fix this manually by creating a symlink between the two directories:

mklink /d "C:\Program Files (x86)\SEGGER\JLink" "C:\Program Files\SEGGER\JLink"

Best regards,

Marte

[Marte Myrvold]

Hi,

The version with this fix was released today, and it is available on the VS Code marketplace now.

Best regards,

Marte