VS Code+nRF Connect: "west invalid build choice" during sample project config

[Arthur_Melkumov]

Hello!

I am discovering a new approach to nRF52 development. I used to be quite happy with SDK+Segger Embedded Studio. But as I understand it, this is an outdated method. So I started evaluating VS Code + NRF Connect.

I have: 

- Installed fresh new Windows 11;
- Installed fresh new nRF Connect for Desktop (v3.11.1);
- Installed fresh new VS Code (v1.69.2);
- Installed fresh new nRF Command Line Tools (via nRF Toolchain Manager);
- Installed fresh new nRF Connect SDK (V2.0.0);
- Installed all required extensions for the VS Code (via nRF Toolchain Manager);

Then I have opened VS Code from nRF Toolchain Manager, and configured the toolchain and SDK as in the image:


I have opened the project from "peripherla_bms" samples and tried to add build configuration to it:



But when I press the "Build Configuration" button - I get an Error and the configuration is still empty:

[Arthur_Melkumov]

Hello

I've installed SDK nRF Connect v1.9.1 and made build configuration for peripheral_bms project successfully and simply. Nothing changed in my actions, just version of SDK. So with SDK v1.9.1 this step is OK and there is no any problems. But in case of v2.0.0 problem is still here.

Could you please check on your setup but with version of SDK v2.0.0?
It will be indication to know whether problem in my setup or in new SDK.

[Priyanka]

Which DK are you using? And have you tried flashing other samples? For eg, blinky, hello_world etc?

-Priyanka

[Arthur_Melkumov]

Hi, again

Seems like trouble was in incorect instalation of nRF Connect or SDK. I uninstalled nRF Connect and all the SDKs from PC and made a new clean instalation of nRF Connect, nRF Command Line Tools and SDK v2.0.0. And now everything is okay. The problem is gone.

And I realised that ncs folder is changed by number of folders (after reinstalling nRF Connect thay amount is increased. So I think that I has wring install before). On the screen is right installation. And it works properly.

Thank You!

[ezequielfalcon]

I have the same issue on MacOS. I had 2.0.2 working and tried to switch to 2.1.0. Now I can´t make it work in any version.
Already tried to reinstall the SDK and the CLI tools.