• State Not Answered
  • Replies 2 replies
  • Subscribers 86 subscribers
  • Views 160 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 356854
Options

nRF Connect for VS Code stuck on "Validating toolchain..."

Gordon

Hi,

Having developed for the past several years with Nordic's legacy library, I'm attempting to get started porting my project to Nordic's Bare Metal SDK.

I managed to install it in VS Code and after a while managed to build the ble_uart example and ran it (although it appeared to spam the console with UART errors). However upon trying to create my own project, which I did by `Create a new application` and then copying that application over my project files, I'm unable to then click "Add build configuration" - the window pops up and shows `Validating toolchain...` and then it just sits there.

The output log for `nRF Connect` just shows `=========== Toolchain validation report for nRF Connect SDK Toolchain v3.2.0 ===========` and nothing else, and never returns.

I managed to get "Add build configuration" to work by doing it on a project I'd just created, but when I copy my source files back in (being sure not to overwrite/change anything), I can't even click edit as it's stuck on `Validating toolchain...` again.

Any ideas how I can get past this?

My project folder does have a bunch of source files for various SDKs in (as we have to target Nordic legacy SDKs 11/12/15 as well as some STM32 and ESP32) which it feels like could be to blame - but so far no manufacturer's SDKs (nor VS Code) have had any issues with this, so I'm surprised that the NRF Bare Metal SDK would be the first.

 

Parents
  • 0

    Hello,

    Not sure what the problem can be, but a few things to look into:

    Temporarily disable non‑Nordic extensions, then reload vs code.
    Given that your project folder contains multiple SDKs, try to remove some of them for test to try to narrow down the problematic one (e.g. in case there are multiple west , cmakelists that somehow cause it to seemingly "hang").
    Delete potential build folders that may already exist.
    Try to downgrade vs code extension to a older version.
    For test try to remove any of the old toolchains from toolchains.json.

    Kenneth

Reply
  • 0

    Hello,

    Not sure what the problem can be, but a few things to look into:

    Temporarily disable non‑Nordic extensions, then reload vs code.
    Given that your project folder contains multiple SDKs, try to remove some of them for test to try to narrow down the problematic one (e.g. in case there are multiple west , cmakelists that somehow cause it to seemingly "hang").
    Delete potential build folders that may already exist.
    Try to downgrade vs code extension to a older version.
    For test try to remove any of the old toolchains from toolchains.json.

    Kenneth

Children
  • 0 in reply to Kenneth

    Hi, Thanks for the suggestions. I'll give them a try.

    For now I have managed to succeed by creating the project in its own directory, and then having cmake include the other repository.

    It's not ideal, but it lets me start on the arduous process of trying to figure out what Nordic's SDK team has decided to randomly rename all the functions, structures and fields to in this SDK release :(

Related
Terms of service