VSCode troubles with NCS 2.7.0 and hardware model 2 boards

RE: VSCode troubles with NCS 2.7.0 and hardware model 2 boards

Ben K — Tue, 19 Nov 2024 13:15:38 GMT

With NCS v2.8.0 and an update to the VSCode extension (v2024.11.75), the custom boards can be selected in the build configuration window, and I can use the usual workflow to build, flash and debug. The only problem I still have is that the boards cannot be loaded from the saved cmake presets, so every time I need to browse them from the list.

RE: VSCode troubles with NCS 2.7.0 and hardware model 2 boards

Edvin — Fri, 01 Nov 2024 08:57:46 GMT

Ok, I see. The reason it worked for me was that I didn't test with a custom board, like you.

I talked with some of the developers, and they said that, unfortunately, at this point custom hardware model v2 boards are not supported in the GUI in VS Code. This will be introduced in a later release. So for now, I am afraid that the only option is to build using the command line.

Best regards,
Edvin

RE: VSCode troubles with NCS 2.7.0 and hardware model 2 boards

Ben K — Thu, 31 Oct 2024 20:29:26 GMT

No, building from vscode's command line works, but the result is the same as rebuilding all configurations with the nRF Connect extension button, the extension detects them, but doesn't list them, so I cannot switch between my different boards. (see my last posted image)

RE: VSCode troubles with NCS 2.7.0 and hardware model 2 boards

Edvin — Wed, 30 Oct 2024 14:31:56 GMT

They are still working on the custom board support. I believe the recommended workaround is to create the build configuration using the command line to build the initial build:

west build -b <board name> -d <build_folder_name> -- -<DCMAKE_COMMANDS>

And then, at least in my case, the build appears in the build configuration list. Does that work in your case?

Best regards,

Edvin

RE: VSCode troubles with NCS 2.7.0 and hardware model 2 boards

Ben K — Mon, 28 Oct 2024 20:40:11 GMT

I would love to, but VSCode doesn't allow me to select the board in the build configuration. What I could do was to build successfully on 2.6.1, then switch to the 2.7.0 branch, where I can still re-run the same build configuration. I couldn't select any other build configurations, nor could I edit the current one. The build itself passes fine, also the west boards command is listing my out-of-tree boards.

Existing build configurations invisible after update to 2.7.0:

This bubble pops up when the build completes:

RE: VSCode troubles with NCS 2.7.0 and hardware model 2 boards

Edvin — Mon, 28 Oct 2024 14:53:32 GMT

Hello,

The support for custom boards in the VS Code extension is lagging behind a bit after the switch to Hardware model v2, introduced in 2.7.0.

Let me run your questions by our VS Code team, but first, can you please share some build logs and screenshots of the parts that aren't working in your exercise?

Best regards,

Edvin