Config impacts in prj.config

[MontanaEE]

Trying to set up UART/UART0 for async.  I cannot get the uart interrupt config to shut off.

CONFIG_UART_INTERRUPT_DRIVEN=n  is set in the prj.conf 

In config output, this field is still set:

CONFIG_UART_INTERRUPT_DRIVEN=y

I do not have access to Kconfig as this is being set up on the Laird/Ezurio Pinnacle 100 DVK which uses and out of tree build.

How can I see which config is locking the Uart Interrupt Driven on?

Thanks

[Jared]

Hi there,

I see that the defconfig file for the board that you are using is setting CONFIG_SERIAL=y.

But the prj.config file should have precedence over this, so I assume that there is something else in your application build that is forcing CONFIG_SERIAL=y and CONFIG_UART_INTERRUPT_DRIVEN=y.

Can you try to open up the kConfig menu in VS Code and then go through all of the kConfigs dependencies and see if any of them are forcing it to be enabled?

If you can share a minimal sample that would reproduce the issue then that would be great!

regards

Jared