Correct place to set Kconfig parameter CONFIG_GPIO=y using nRF Connect SDK v2.9.0?

[Ken58]

Hi,

What file or files should contain CONFIG_GPIO=y for a simple application developed with nRF Connect SDK v2.9.0 such that VS Code does not show squiggles under #include <zephyr/drivers/gpio.h>  indicating error:  The GPIO drivers must be enabled by CONFIG_GPIO to be included in build (missing_kconfig_param).

I have a similar problem with CONFIG_PWM.  I have tried setting it in prj.conf and also my custom_board_defconfig file without solving the problem.

Thanks,

Ken

[Sigurd Hellesvik]

Hi,

Do you see this with the Zephyr Blinky sample?

And you see the squiggles also after having built the project?

Regards,
Sigurd Hellesvik

[Ken58]

Hi Sigurd.  Happy Holidays!

I tried the Zephyr Blinky sample with similar results to my own application.  After having built the project, here is a screen shot showing Blinky, the squiggles, and the PROBLEMS warning message:

Thanks,

Ken

[Sigurd Hellesvik]

Ken58 said:

When I expand "build" and select "blinky", the warning is removed

This makes sense then. See Application Contexts docs. It is because the config for the project will be under "blinky", and if CONFIG_GPIO is for the project, this has to be selected for VS Code to understand.

Ken58 said:

where should I define CONFIG_GPIO and CONFIG_PWM?

If your project uses these, they should be in prj.conf for your project

[Ken58]

Thanks Sigurd.  I'm going to continue my work and will get back to you with any unusual observations, but I think I'm good to go for now.  Thanks again,

Ken

[AndersHedberg]

I also got this error now, and it's confusing. One error claims GPIO is set twice, another error that it must be enabled. And just by clicking on the files, it now have a CONFIG_UART_CONSOLE error as well... what is going on?!? and this is just the first lesson! Now Use sysbuild was marked... 

and yes, it builds and flashes and works, but why... 

[AndersHedberg]

It's stated here that the Academy course is not updated to the latest version of the tools and Problems should be ignored...
devzone.nordicsemi.com/.../tfm_version_manual-mismatches-to-actual-tf-m-version-please-update-nrf9160-dk

[Sigurd Hellesvik]

Hi Anders,

AndersHedberg said:

I also got this error now, and it's confusing. One error claims GPIO is set twice, another error that it must be enabled. And just by clicking on the files, it now have a CONFIG_UART_CONSOLE error as well... what is going on?!? and this is just the first lesson! Now Use sysbuild was marked... 

A new update to the VS Code Extension should be available soon (I can not say exactly when).
With that update, you should not longer get the warning that "GPIO is set twice".

Let me know if you still get this warning after your next VS Code Extension update