The "Flash" action from the nRF Connect for VS Code has stopped working.

[tylerh]

Hi,

I just reinstalled a fresh version of VS Code 1.96.2, and I'm using v2024.12.55 of the nRF Connect for VS Code extension. I'm also using nRF SDK v2.1.1.

In the past couple months, my "Flash" action has stopped working. I get this error.

However, if I use the "Start New Terminal in the sources of this build" and put "west flash -d c:\repos\master\src\top\mission_mode\build --skip-rebuild --dev-id 52005670", then it works.

I'm not sure why this has stopped working, but I suspect that it was an update to nRF Connect for VS Code.

[Kenneth]

Reported it, will update when I learn more.

Kenneth

[Kenneth]

One question that came up from our devs now was whether you could upload the support log from VS Code, as that can give an indication to what's wrong here. This can be done by going to the nRF Connect extension in VS Code, and press the small headset symbol in the top right of the nRF Connect sidebar:

Please upload the file generated here and our devs will take a look.

Kenneth

[tylerh]

Certainly, here you are.

By the way, I discovered that if I use "Manage SDKs -> Manage West Workspace... -> Set West Manifest Repository -> nRF Connect SDK v2.1.1 -> zephyr (c:\ncs\v2.1.1\zephyr\west.yml)", then the Flash action works again. However, my Build action will now fail.

If I do the above, but replace "zephyr ..." with "nrf (c:\ncs\v2.1.1\nrf\west.yml)", then Build works, but Flash does not, as in the ticket.

I tried setting ZEPHYR_BASE=C:\ncs\v2.1.1\zephyr in my system environment variables, but that didn't work unfortunately.

[Kenneth]

Hi again,

We suspect some "incorrect" clone of the v2.1.1. SDK. Something to try:

Make sure when the manifest is changed, west update is done. 

If that doesn't help, then we would like you to check:

1. the contents of C:\ncs\v2.1.1\zephyr\scripts\west_commands
2. a confirmation that the PATH and ZEPHYR_BASE points to the correct toolchain and SDK in the terminal that he opens by "Start New Terminal in the sources of this build".

Kenneth

[tylerh]

Hi Kenneth,

You were right. There seemed to be something wrong with the v2.1.1 SDK. I uninstalled it with the toolchain manager, reinstalled, and now everything seems to work as suggested. Thank you!