VS Code intellisense not finding kconfig options

RE: VS Code intellisense not finding kconfig options

Nick_RA — Wed, 08 Apr 2026 18:34:06 GMT

Okaaay thanks.. Yes I think I get something similar. My builds are sysbuild: if I click MYBUILD in the applications window then it doesn't work but if I click like so:

MYBUILD sysbuild <- click here not OK
|
|- myapp <- click here OK
|-mcuboot

then it works. That doesn't really explain why the copy of the project works though...?

I noticed also that I get this error in the status bar:

I may well have messed up my extensions anyway. I was experimenting disabling extensions because starting up was SLOW (>30 sec waiting). So maybe I have something wrong here?

RE: VS Code intellisense not finding kconfig options

Turbo J — Wed, 08 Apr 2026 16:52:30 GMT

Same problem here when using sysbuild.

Fix is relatively simple: Select the application build folder (example: MyProject/build/MyProject) in "Applications" tab. This allows the extension to read correct .config variables.

The bad thing here is that it breaks Segger Ozone debug support, which wants the "build" folder to be active in order to work correctly. Could be a problem with my very custom cmake scripts, though.

Note that I am still on the oldstable nrf connect extension version (2026.1.1327) so YMMV.

RE: VS Code intellisense not finding kconfig options

Nick_RA — Wed, 08 Apr 2026 14:23:41 GMT

No, it's also the same for other build configurations.

RE: VS Code intellisense not finding kconfig options

Kenneth — Wed, 08 Apr 2026 13:53:38 GMT

[quote user="Nick_RA"]I can only guess there is a cached file somewhere making it go wrong?[/quote]

Looks like it yes, does manually delete the build folder work?

Kenneth

RE: VS Code intellisense not finding kconfig options

Nick_RA — Wed, 08 Apr 2026 13:32:50 GMT

Probably not. The really weird thing is I recently made a copy of the entire project folder in order to do some hacking about to troubleshoot a subtle power consumption problem I had, and this copy works OK!

I have tried cleaning the build configuration and doing a pristine build but that makes no difference.

On the "good" copy I can hover over for example CONFIG_MY_CUSTOM_FOO and it looks up the value. On the "bad" copy it doesn't. Yet if I right-click and select "go to definition" on the bad copy it jumps to \include\generated\zephyr\autoconf.h and shows "1" if configured.

The contents of the ./vscode folder c_cpp_properties.json and settings.json match between the two.

I can only guess there is a cached file somewhere making it go wrong?

RE: VS Code intellisense not finding kconfig options

Kenneth — Tue, 07 Apr 2026 14:05:38 GMT

Hello,

Any way we can recreate it here?

Normally I would suggest that you do a pristine build and that you have the specific build active in the APPLICATIONS window in nRF Connect extension in VS code.

Kenneth