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

[MontanaEE]

Went through all of the configs that were listed as selectors for the interrupt driven option. Made sure they were set to "n" to disable, still interrupts are set to "yes" in the config.

[MontanaEE]

From the build:

warning: UART_INTERRUPT_DRIVEN (defined at boards/shields\sparkfun_sara_r4\Kconfig.defconfig:24,
boards/shields\wnc_m14a2a\Kconfig.defconfig:17, soc/arm\quicklogic_eos_s3\Kconfig.defconfig:17,
drivers/serial/Kconfig:72) was assigned the value 'n' but got the value 'y'. See
docs.zephyrproject.org/.../kconfig.html and/or look up
UART_INTERRUPT_DRIVEN in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: SERIAL (defined at soc/arm/nxp_lpc/lpc55xxx\Kconfig.defconfig.lpc55S69_cpu1:14,
drivers/serial/Kconfig:6) was assigned the value 'n' but got the value 'y'. See
docs.zephyrproject.org/.../kconfig.html and/or look up SERIAL in the
menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.

warning: MODEM_RECEIVER (defined at drivers/modem/Kconfig:17) was assigned the value 'n' but got the
value 'y'. See docs.zephyrproject.org/.../kconfig.html and/or look
up MODEM_RECEIVER in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

[Elfving]

Hello Stephen, 

I am not used to out of tree builds like these, but I wonder if it might be locked that way.

Could you try setting these configurations: 

CONFIG_UART_ASYNC_API=y

CONFIG_UART_0_ASYNC=y

CONFIG_UART_0_INTERRUPT_DRIVEN=n

Are you able to enable any configuration for this build?

Regards,

Elfving

[MontanaEE]

Thanks Elfving,

UART_0 interrupt is turned off, but I cannot get UART interrupt to be disabled.

This is what I have in proj.conf:

CONFIG_UART_INTERRUPT_DRIVEN=n
CONFIG_UART_0_INTERRUPT_DRIVEN=n
CONFIG_NRFX_UARTE0=n 
CONFIG_SERIAL=n 
CONFIG_UART_ASYNC_API=y
CONFIG_UART_0_ASYNC=y
CONFIG_UART_0_NRF_HW_ASYNC=y
CONFIG_UART_0_NRF_HW_ASYNC_TIMER=0
CONFIG_UART_USE_RUNTIME_CONFIGURE=y

This is what is in the resulting .config output:

CONFIG_UART_INTERRUPT_DRIVEN=y

CONFIG_SERIAL=y

CONFIG_SERIAL_HAS_DRIVER=y

CONFIG_SERIAL_SUPPORT_ASYNC=y

CONFIG_SERIAL_SUPPORT_INTERRUPT=y

# CONFIG_UART_LOG_LEVEL_OFF is not set

# CONFIG_UART_LOG_LEVEL_ERR is not set

# CONFIG_UART_LOG_LEVEL_WRN is not set

# CONFIG_UART_LOG_LEVEL_INF is not set

# CONFIG_UART_LOG_LEVEL_DBG is not set

CONFIG_UART_LOG_LEVEL_DEFAULT=y

CONFIG_UART_LOG_LEVEL=3

CONFIG_UART_USE_RUNTIME_CONFIGURE=y

CONFIG_UART_ASYNC_API=y

# CONFIG_UART_LINE_CTRL is not set

# CONFIG_UART_DRV_CMD is not set

# CONFIG_UART_WIDE_DATA is not set

# CONFIG_UART_PIPE is not set

#

# Serial Drivers

#

CONFIG_UART_NRFX=y

CONFIG_UART_ASYNC_TX_CACHE_SIZE=8

CONFIG_UART_0_NRF_UARTE=y

CONFIG_UART_0_ENHANCED_POLL_OUT=y

# CONFIG_UART_0_INTERRUPT_DRIVEN is not set

CONFIG_UART_0_ASYNC=y

# CONFIG_UART_0_NRF_PARITY_BIT is not set

CONFIG_UART_0_NRF_TX_BUFFER_SIZE=32

CONFIG_UART_0_NRF_HW_ASYNC=y

# CONFIG_UART_0_NRF_ASYNC_LOW_POWER is not set

CONFIG_UART_0_NRF_HW_ASYNC_TIMER=0

[MontanaEE]

Yes I can change some configurations just these few for uart interrupt are not changing.  Where would they have "locked" these configs?  I cannot find reference to anywhere that would be taking place.

Stephen