Using the nrf-kconfig and nrf-devicetree extensions without nrf-connect

[mlampacher]

Hi,

I wanted to use the `nordic-semiconductor.nrf-kconfig` and the `nordic-semiconductor.nrf-devicetree` without the nRF Connect extension in `vscode`, but they don't seem to play nice without it since the build context etc. is directly taken from the (not installed) `nordic-semiconductor.nrf-connect`.

The `nrf-devicetree` extension is somewhat usable since at least it provides the proper syntax highlighting, though I also have `kylemicallefbonnici.dts-lsp` installed. Could you please allow configuring the build context using `vscode` settings? I could then point the extensions to wherever my build folder is located.

Cheers.M

[Einar Thorsrud]

Hi,

Thank you for the request. I have forwarded it internally, but there are no plans for supporting nrf-kconfig and nrf-devicetree without nrf-connect for now.

[mlampacher]

That's a pity, especially since your Kconfig extension is listed as a replacement for `trond-snekvik.kconfig-lang`.

[Daniel DSouza]

At the moment, both nrf-kconfig and nrf-devicetree are tightly coupled to the nRF Connect extension because they rely on its build context (CMake, Kconfig, DTS paths). Without nRF Connect, syntax highlighting works, but context-aware features won’t, unless Nordic exposes a manual build-folder override via VS Code settings.

A common workaround is to keep nRF Connect installed but disabled, just to provide the build context, while using your own toolchain/workflow. That way the extensions can still resolve symbols correctly.

For reference, I’m working with nRF52-based hardware, (e.g. nRF52840) so having accurate devicetree/Kconfig context without full nRF Connect would be very useful.