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:

[Priyanka]

Hi,

When you look at the peripheral_bms sample, it is mentioned which devices support this sample and the nrf52840gmouse that you try with, doesn't support it. This might be the reason.

Best Regards,

Priyanka

[Arthur_Melkumov]

That's what I'm trying to do. Maybe it will be helpfully to realize what's wrong:

[Priyanka]

Could you try selecting the "Create a new application" and entering the details accordingly ?

After that, you can create the build configuration for the added application.

Also, when building using west, you can give "west build -b nrf52840dk_nrf52840" and after that "west flash" to flash the sample.

You can take a look at the nRF Connect SDK Tutorial for more information too.

-Priyanka

[Arthur_Melkumov]

Tried to create new application, but it doesn't work also. The same error (west build invalid choice..) and build is not creates

[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.