The Add Build Configuration wizard on nRFConnect extension for VSCode does not show custom boards

[V.Lorz]

Dear All,

I'm trying to add a build configuration to a project based on my custom board and the wizard does not list the custom boards I've previously created.

I created the custom board using the "Create a new board" utility in the extension's welcome page, gave it PRD1J4 as a name and board Id, selected D:\workspace\PRD1J4 as target path, nrf52830-QFAA as the SoC, and MyCompany as vendor name.

The wizard creates the boards folder, as expected, and a set of files at D:\workspace\PRD1J4\boards\arm\prd1j4.

The ratio button for listing the custom boards is not displayed by the nRF Connect's Add Build Configuration.

I later checked the D:\workspace\PRD1J4 folder was listed in the workspace's board roots parameter, like described here in this post.

Also tried to create the board inside the project's root dir, the wizard created all the files and folders below a boards folder, but with same results.

I even restarted VSCode after modifying the Board Roots setting for the workspace.

Current version I use is nRF Connect SDK v2.3.0 + nRF Connect for VS Code v2023.4.179

What am I missing?

Thanks a lot in advance.

[runsiv]

Hi, 

I will investigate, however: I normally find my custom boards in the list of boards select boards in built configuration

Regards

Runar

[V.Lorz]

Hi Runar,

I tried uninstalling everything, also deleted all hidden vscode folders and files, and then reinstalled VSCode, nRF Connect, etc. again. Got same results.

Regards,
V.Lorz

[runsiv]

Hi V.Lorz

I have not yet been able to recreate what you are seeing.

Can you open the nRF Connect for VScode setings, select Workspace and verify if the board folder is still there after you reinstalled VScode? 

Also could you upload the custom board files so that I can see if I find them? I can set the case to private if you like

Regards

Runar

[V.Lorz]

Hi Runar,

I'll try to provide all details I can.

I uninstalled everything again, and tracked down and deleted all traces from VSCode and nRF Connect and all Nordic components and tools.

After starting VSCode, everything was clean, no application in the workspace, no folder, etc.

I opened the folder of a previously created project, the one I selected as target for creating a custom board with the wizard. The board files were just like the wizard created them, no change.

Trying then to create a build configuration did display the "Custom boards" radio button, and the board name was listed. The project compiled, west's command line included the expected -DBOARD_ROOT:STRING="d:/workspace/pcd/fw/proto1" argument.

I then went to Settings>>Workspace>>nRF Connect and added "D:\workspace\PRD1J4" to boards root. This is the folder where I created a custom board yesterday. Same as before, just the templates created by the wizard.

The add build configuration wizard did not show the "prd1j4" board, it only listed the "proto1".

Next I removed the project from the workspace and opened another arbitrary project, just a hello world I was playing with before on my nRF-DK.

When I opened the wizard to create the build configuration, the prd1j4 board did appear there in the custom boards.

The project compiled, and, surprisingly, west's command line included both board folders: -DBOARD_ROOT:STRING="d:/workspace/PRD1J4;d:/workspace/pcd/fw/proto1", yet the "proto1" board is not referenced anywhere in the workspace or user configuration, and the proto1 project (folder) was not open.

Just to check, I closed and reopened VS Code and made a pristine build, this time only the correct board folder was referenced in west: -DBOARD_ROOT:STRING="d:/workspace/PRD1J4".

Next I opened (APPLICATIONS + button) the project that included a board inside (pcd, previously mentioned), and.... this is totally annoying, the nRF Connect tools that display the boards, dts, build etc.... disappeared.

Went to the Explorer view (Ctrl+Shift+E), removed the project from the workspace, and the tools appeared again.

Well, I don't know if this is standard behaviour, but it looks a little bit bizarre for me.

My OS is Windows 10, two HDD, with Nordic tools installed on secondary HDD.

Regards,

V.Lorz

[runsiv]

Thanks for the explanation. I have contacted the developers in regards to what you are experiencing. 

When I created a custom board I had to "Developer reload Windows" command in vscode for the custom board to show during configure build project

Regards

Runar