VS Code Not Finding Zephyr Include Paths

RE: VS Code Not Finding Zephyr Include Paths

dejans — Tue, 02 Dec 2025 18:02:59 GMT

Hi,

Do you see the same issue if you add NCS folder to your workspace?

Best regards,
Dejan

RE: VS Code Not Finding Zephyr Include Paths

viggyd-blur — Tue, 02 Dec 2025 17:46:30 GMT

This issue is present in other samples as well.

[quote userid="111786" url="~/f/nordic-q-a/125833/vs-code-not-finding-zephyr-include-paths/556046"]Can you elaborate on this? Is there an action on your side that you would want to do but cannot do due to these error squiggles?
[/quote]

I would like to view the source code of kernel function calls, but I cannot because VS Code Intellisense cannot find the headers/source files. For example, I want to see the code that is executed when the `gpio_is_ready_dt` function is called, but I cannot see the source code due to the error squiggles.

RE: VS Code Not Finding Zephyr Include Paths

dejans — Tue, 02 Dec 2025 17:41:53 GMT

Hi,

Have you tested any other sample? Is this issue also present with other samples?

[quote user="viggyd-blur"]I need to be able to look through the full source code when I'm debugging issues. I need to be able to see what these kernel function calls are doing if my program is not behaving as expected. Again, I don't have a problem right now, everything compiles and works fine, but I have always needed to look through files like this during the course of my work.[/quote]

Can you elaborate on this? Is there an action on your side that you would want to do but cannot do due to these error squiggles?

Best regards,
Dejan

RE: VS Code Not Finding Zephyr Include Paths

Stanley Jackson — Mon, 01 Dec 2025 21:42:51 GMT

Hi Dejan,

Im having a similar issue. My application builds and runs fine but the "red squiggles" dont go away.
SDK: v3.1.1
Toolchain: v3.1.1
nRF Connect VSCode extension: v2025.9.798

Something else of note, in the VSCode output window (nRF Connect selected in the dropdown), I see the following error:

[09:54:07] Stale build configuration (modbus_rtu_server_test - build): Unable to find the SDK at path: C:/ncs/v3.1.1/zephyr
[09:54:12] Failure (code 1).
[09:54:15] Stale build configuration (modbus_rtu_server_test - build): Unable to find the SDK at path: C:/ncs/v3.1.1/zephyr
[09:54:15] Stale build configuration (modbus_rtu_server_test - build/modbus_rtu_server_test): Unable to find the SDK at path: C:/ncs/v3.1.1/zephyr

I have checked that file path and there stuff there.

I have just recently moved from SDK v2.7.0 to v3.1.1 (to get support for the nRF54L15DK).
I did not have this issue with v2.7.0 (although that SDK does not support the nRF54)

I too noticed the lack of `compile_commands.json` in the build output directory (where previously with v2.7.0 it was there).

I hope this provides some more information and I look forward to hearing any other suggestions.

Cheers

RE: VS Code Not Finding Zephyr Include Paths

viggyd-blur — Mon, 01 Dec 2025 13:13:51 GMT

Here's the link to the lesson that I'm using: https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-1-nrf-connect-sdk-introduction/topic/exercise-2-1/

Specifically, this blurb says they should go away:

Here's a screenshot of my workspace:

[quote userid="111786" url="~/f/nordic-q-a/125833/vs-code-not-finding-zephyr-include-paths/555548"]Can you describe what you want to do in more detail?
[/quote]

It's not that I'm having a problem right now, but when working on projects, I need to be able to look through the full source code when I'm debugging issues. I need to be able to see what these kernel function calls are doing if my program is not behaving as expected. Again, I don't have a problem right now, everything compiles and works fine, but I have always needed to look through files like this during the course of my work.

RE: VS Code Not Finding Zephyr Include Paths

dejans — Wed, 26 Nov 2025 17:31:46 GMT

Hi,

Are you able to show your observations using some simple nrf sample?

Can you point to the lesson which says that errors should go away?

[quote user=""] It's very useful to be able to look through included header files[/quote]

Can you describe what you want to do in more detail?

Best regards,
Dejan