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

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

Daniel DSouza — Mon, 09 Feb 2026 10:57:45 GMT

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.

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

mlampacher — Mon, 15 Dec 2025 13:17:50 GMT

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

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

Einar Thorsrud — Mon, 15 Dec 2025 13:05:47 GMT

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.