Invalid Toolchain installation in VS code

[AntonyJ]

Hi,

I am trying to set up  nRF Connect for VS code in visual studio code using the documentation provided but I getting following error in VS code.

Installed Version is shown below.

Any fix on this?

[fhfs]

For windows you can use the "Toolchain Manager" in the "nRF Connect for Desktop" to install the SDK and Toolchain

Note that the "nRF Connect Toolchain"  is much more than the nrfjprog.

Here you can see the location for the toolchain and sdk

[AntonyJ]

Hi fhfs,

Thank you for your response. I tried directory showed in the Toolchain Manager still the same issue, Invalid toolchain installation.
I tried with different version but still the same error.

Thanks and regards
Antony

[Elfving]

After selecting where the toolchain is, does pressing the reset button change anything?

Could you also see if you have a path to JLink in your Path variables? If not, could you try adding it? I assume you'll find JLink.exe in Program Files/SEGGER/Jlink.

Regards,

Elfving

[AntonyJ]

Hi,

I tried reset button, after few seconds error pops up again.

I added the JLink to my path variables still same issue.

I also uninstalled the SDK and installed in default folder but still facing the issue.

Regards
Antony

[AntonyJ]

Hi Elfving,

Any update on this?

[fhfs]

For reference:

My path includes nRF-Command-line-tools, it does not include the path to SEGGER\JLink

No idea if this helps you though.

*Edit - reuploaded screenshot

[Elfving]

It would be great if everyone could let me know what OS and version they are using.

And could you please also generate support information for me?

Regards,

Elfving

[AntonyJ]

Hi Elfving,

I am using Windows 10 Pro, Version 10.0.19045 Build 19045

I have sent you support Information as private message.

Thanks
Antonyt

[AntonyJ]

Hi Elfving, Any update?
Thanks

[AntonyJ]

Hi Elfving,

Whenever I uninstall the JLink and check my VS Code I get following error message.

[Elfving]

Hello again, and sorry about the delay on this case.

Are you also seeing the issue being solved when downgrading the VSC extension to 2022.7.111, like what was suggested in the other thread? And which version are you currently using, and seeing this being an issue with? 2023.2.56?

I haven't been able to reproduce this yet.

Regards,

Elfving