VS Code nrf-connect support custom boards under west workspace

[86s9f5w8]

Hello,

Currently the nrf-connect extension offers board targets under build configuration. These are categorized as "Nordic SoC", "Custom boards", "All".

As I have understood, it is not possible to have custom boards while using west workspace.
For example, I have the following import here, my custom boards under vscode workspace will get clumped under "All" boards.

manifest:
remotes:
- name: ncs
url-base: https://github.com/nrfconnect

projects:
- name: sdk-nrf
remote: ncs
path: nrf
revision: v2.4.2
import: true
clone-depth: 1
self:
path: project

If I take out the sdk here, and restart vscode my custom boards will show under "Custom boards".

It would be nice feature to have custom board roots under custom boards regardless of whether west workspace.

Similar discussion (also possible related topics "vscode not recognizing custom boards" in these forums)
devzone.nordicsemi.com/.../nrf-connect-boardroots-does-not-work-custom-board-are-not-picked-up

Thank you.

[Vidar Berg]

Hello,

86s9f5w8 said:

my custom boards under vscode workspace will get clumped under "All" boards

Are you boards not shown in any of the other lists like "Compatible" and "Nordic SoC"?

86s9f5w8 said:

If I take out the sdk here, and restart vscode my custom boards will show under "Custom boards".

Hitting "Refresh SDKs" should also do the trick:

Best regards,

Vidar

[86s9f5w8]

Vidar Berg said:

Are you boards not shown in any of the other lists like "Compatible" and "Nordic SoC"?

No, there are only "Nordic SoC" and "All". My custom boards are under "All" which also has all of the Zephyr supported boards, I just have to search them every time. Since I am using custom boards 99.99% when configuring build, I would like to have "Custom boards" option aswell.

[Vidar Berg]

Thanks for confirming. I forgot to ask, but could you also let me know the path to your board root? Is it in the 'project' directory?

[86s9f5w8]

Vidar Berg said:

Thanks for confirming. I forgot to ask, but could you also let me know the path to your board root? Is it in the 'project' directory?

Yes, here are the details.

.
├── bootloader
├── modules
├── nrf
├── nrfxlib
├── project
├── test
├── tools
└── zephyr

project/
├── CMakeLists.txt
├── Kconfig.project
├── README.md
├── app
├── boards
├── cmake
├── docs
├── drivers
├── dts
├── project.code-workspace
├── include
├── lib
├── test
├── tools
└── west.yml

[Vidar Berg]

I've discussed this with the team now.  Any boards that are *not* part of the west workspace are assumed to be "custom." The extension doesn't have a good way to determine whether a board was added to the workspace by the user or if it came from one of the SDK modules. A workaround could be to define a sample.yaml file in your project root to have your board appear in the "compatible" list.

[86s9f5w8]

I have just added a simple sample.yaml under the sample. It now automatically select the compatible board when navigating to the build configuration. This works for use nicely, thank you.