• Support
  • VS Code shows "no boards" in in build configuration dialog for nRF9151 Feather

Hi

We’ve been through the procedure to install the tool chain as shown here: https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html

It seemed to work properly, but when we load any example, we have no boards listed in the Add Build Configuration dialog.

We’ve used VS Code with the nRF Connect tools successfully before, and are a bit stuck. Versions listed below.

Name: nRF Connect for VS Code
Id: nordic-semiconductor.nrf-connect
Description: Develop applications based on nRF Connect SDK with ease!
Version: 2025.5.92
Publisher: Nordic Semiconductor
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=nordic-semiconductor.nrf-connect


Name: nRF Connect for VS Code Extension Pack
Id: nordic-semiconductor.nrf-connect-extension-pack
Description: Recommended extensions for development with the nRF Connect SDK
Version: 2025.4.4
Publisher: Nordic Semiconductor
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=nordic-semiconductor.nrf-connect-extension-pack
```

Hmm. I have seen this before where it doesn’t want to show up under Nordic IC’s

Try clicking the ‘All’ option and start typing circuitdojo and see what you get.

Also, your project should look something like this:

You may have to re-open one level higher to include the .west folder in order to parse the sub-directories correctly. (All board files for the nRF9151 are located in nfed/boards and the nfed/zephyr/module.yml tells Zephyr to look there in order for it to show up and be a buildable target

NFED is short for nRF9160-feather-examples-and-drivers 😃

Try opening the parent folder in VSCode instead. If you didn’t make a parent folder (For example I put my stuff in ~/Git/ I would suggest making one then cloning the file structure there. If you haven’t done an init yet you should be able to move whole folder right over. Then run the west init function and west update commands via nRF Connect.

5 days later

Hi Jared

I work with tc531 and I am having the same problem he had where there are No Boards Found no matter what I do.

I have tried using v3.0.1 and I have tried cloning in a parent folder and opening the parent folder but it made no difference.

The Initialize West and Update West in VS Code appeared to complete without error. I can see the circuitdojo boards in the boards folder

@jcd no boards whatsoever? Do you get anything when you click the “All” option? What OS are you on? It may be good to jump on a screen share and see where things are going wrong so I can fix the documentation. Send me an email jared@circuitdojo.com

It’s probably related to having multiple toolchains/SDKs installed.

Try this command and make sure the folder you did your init and update in is targeted:

As you can see I had multiple entries.

Also make sure you have the base directory open in VSCode. So if everything is in C:\dojo\ make sure VSCode is open in that directory. (It should be the same directory as the .west folder)

Sorry - I must be doing something wrong and repeating the same mistake every time 🙁 These are the exact steps I am doing

Install the 3.0.1 Toolchain from nRF Connect : Manage Toolchains

Create the folder C:\nfed

Run nRF Connect: West Init selecting C:\nfed as the destination folder, selecting Custom Repository and entering the URL https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git and selecting the tag v3.0.x

Open the folder C:\nfed in VS Code

Run nRF Connect: West Update

Once that completes after a few mins then with C:\nfed open in VS Code then select Open an existing application in NRF CONNECT and select any of the sample folders. Adding a Build Configuration is always saying No boards found

Going to nRF Connect: Set Active West Manifest, C:\nfed\nfed\west.yml is already selected and selecting it has no effect. Selecting C:\nfed\external\nrf\west.yml causes boards to appear in the list but that is wrong and causes the directory structure to be incorrect

My directory structure is

C:\nfed.vscode
C:\nfed.west
C:\nfed\external
C:\nfed\nfed
C:\nfed\nfed\samples\ etc
C:\nfed\pcf85063a

Thanks!

I’m starting a fresh setup again here on a completely different machine. I’ll get back you you @jcd

@jcd i’m sorry this seems like a bug/edge case with Nordic’s plugin. I was able to reproduce this and it appears to have to do with the directory structure. If you delete the external folder, and edit your west.yml to remove:

        path-prefix: external

Under the nrf entry and run the nRF Connect: West Update. Then select an application (I tried blinky) and create a configuration that should 🤞 do the trick.

That was it! All sorted now - boards appear and managed to Add Build Configuration and build Blinky sample. Flashed it using probe-rs. So all up and running now 🙂 Thanks again

Terms and Conditions | Privacy Policy