Spurious Config Warnings

[d2sc]

in prj.conf 

I have several warnings in my application that look like this XXXXXXX set more that once. Old Value "x", new value "x". I am worried that this indicates I am not configuring the project correctly and / or have a miss understanding of the proper way to configure a project in zephyr/nrf connect sdk. What is the proper way to get these to go away.

This is the build configuration

 

[Sigurd Hellesvik]

Hi,

I have reported this to the devs and we are looking into it.
For now you will have to just ignore the warning, but it will be fixed in a future update.

I cannot give any timeline information, but feel free to ask again in a couple weeks or so if nothing has changed by then and I will give it a re-check at that point.

Regards,
Sigurd Hellesvik

[Joriam]

Hey Sigurd, I am not the original ticket author but I am running into the same issue. The warnings do not prevent the build from completing, but they do make it hard to spot actual warnings as the entire prj.conf is highlighted yellow. Do you have any updates on this yet?

[Sigurd Hellesvik]

Hi Joraim,

Which version of the VS Code extension do you have?

[Joriam]

Versions:
VS Code nRF Connect extension version: 2025.1.127 (auto-update turned on)
Latest version of VS Code itself
SDK Toolchain v2.9.0

I also turned my cmake tools extension off because the connect extension warned of possible problems.
If you prefer I can create my own ticket. I only replied here because the ticket tool suggested I visit this ticket first.

[Sigurd Hellesvik]

The warning system has been updated and will be part of an upcoming version of the VS Code extension.

Joriam said:

If you prefer I can create my own ticket. I only replied here because the ticket tool suggested I visit this ticket first.

Nah, it is fine to keep it in this ticket

[gterrell]

This is still an issue in the v3.0.0 SDK/Toolchain. I agree totally with Joriam, spurious warnings are not just an inconvenience, they hinder development of production level code.

[Sigurd Hellesvik]

Hi Greg,

Now, the "duplicate Kconfig" are info-symbols and not notes. They should be blue.
While this might not completely remove them, they are now different from warnings, which should help.

gterrell said:

they hinder development of production level code.

For production level code, you should not get these, right?
For example for CONFIG_CONSOLE: This should not be set in the board files, but just in the project files for the project that need it. You do not want your production device to have logs that are enabled by default, as this can increase current consumption.

[gterrell]

Agreed.