<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Config impacts in prj.config</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116499/config-impacts-in-prj-config</link><description>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</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 26 Nov 2024 10:44:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116499/config-impacts-in-prj-config" /><item><title>RE: Config impacts in prj.config</title><link>https://devzone.nordicsemi.com/thread/512073?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2024 10:44:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75482107-327a-4a37-9fe3-6c21a4b0077b</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I see that the defconfig file for the board that you are using is setting CONFIG_SERIAL=y.&lt;/p&gt;
&lt;p&gt;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&amp;nbsp;&lt;span&gt;CONFIG_UART_INTERRUPT_DRIVEN=y.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;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?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1732617712588v1.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If you can share a minimal sample that would reproduce the issue then that would be great!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;regards&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Jared&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Config impacts in prj.config</title><link>https://devzone.nordicsemi.com/thread/511582?ContentTypeID=1</link><pubDate>Thu, 21 Nov 2024 23:45:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:888eb445-adab-440d-8f11-74e407809473</guid><dc:creator>MontanaEE</dc:creator><description>&lt;p&gt;Yes I can change some configurations just these few for uart interrupt are not changing.&amp;nbsp; Where would they have &amp;quot;locked&amp;quot; these configs?&amp;nbsp; I cannot find reference to anywhere that would be taking place.&lt;/p&gt;
&lt;p&gt;Stephen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Config impacts in prj.config</title><link>https://devzone.nordicsemi.com/thread/511399?ContentTypeID=1</link><pubDate>Thu, 21 Nov 2024 04:16:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e16b4bcd-26fc-4afc-8625-4c22ce0ecf96</guid><dc:creator>MontanaEE</dc:creator><description>&lt;p&gt;Thanks Elfving,&lt;/p&gt;
&lt;p&gt;UART_0 interrupt is turned off, but I cannot get UART interrupt to be disabled.&lt;/p&gt;
&lt;p&gt;This is what I have in proj.conf:&lt;/p&gt;
&lt;p&gt;CONFIG_UART_INTERRUPT_DRIVEN=n&lt;br /&gt;CONFIG_UART_0_INTERRUPT_DRIVEN=n &lt;br /&gt;CONFIG_NRFX_UARTE0=n&amp;nbsp;&lt;br /&gt;CONFIG_SERIAL=n&amp;nbsp;&lt;br /&gt;CONFIG_UART_ASYNC_API=y&lt;br /&gt;CONFIG_UART_0_ASYNC=y&lt;br /&gt;CONFIG_UART_0_NRF_HW_ASYNC=y&lt;br /&gt;CONFIG_UART_0_NRF_HW_ASYNC_TIMER=0&lt;br /&gt;CONFIG_UART_USE_RUNTIME_CONFIGURE=y&lt;/p&gt;
&lt;p&gt;This is what is in the resulting .config output:&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_INTERRUPT_DRIVEN&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_SERIAL&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_SERIAL_HAS_DRIVER&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_SERIAL_SUPPORT_ASYNC&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_SERIAL_SUPPORT_INTERRUPT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_LOG_LEVEL_OFF is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_LOG_LEVEL_ERR is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_LOG_LEVEL_WRN is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_LOG_LEVEL_INF is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_LOG_LEVEL_DBG is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_LOG_LEVEL_DEFAULT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_LOG_LEVEL&lt;/span&gt;&lt;span&gt;=3&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_USE_RUNTIME_CONFIGURE&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_ASYNC_API&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_LINE_CTRL is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_DRV_CMD is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_WIDE_DATA is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_PIPE is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;#&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# Serial Drivers&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;#&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_NRFX&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_ASYNC_TX_CACHE_SIZE&lt;/span&gt;&lt;span&gt;=8&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_0_NRF_UARTE&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_0_ENHANCED_POLL_OUT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_0_INTERRUPT_DRIVEN is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_0_ASYNC&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_0_NRF_PARITY_BIT is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_0_NRF_TX_BUFFER_SIZE&lt;/span&gt;&lt;span&gt;=32&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_0_NRF_HW_ASYNC&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_UART_0_NRF_ASYNC_LOW_POWER is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_0_NRF_HW_ASYNC_TIMER&lt;/span&gt;&lt;span&gt;=0&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Config impacts in prj.config</title><link>https://devzone.nordicsemi.com/thread/511305?ContentTypeID=1</link><pubDate>Wed, 20 Nov 2024 13:30:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a36084bb-130a-4f65-9edf-edeea21c01cb</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;Hello Stephen,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am not used to out of tree builds like these, but I wonder if it might be locked that way.&lt;/p&gt;
&lt;p&gt;Could you try setting these configurations:&amp;nbsp;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_ASYNC_API=y&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_UART_0_ASYNC=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;CONFIG_UART_0_INTERRUPT_DRIVEN=n&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;Are you able to enable any configuration for this build?&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;div&gt;Regards,&lt;/div&gt;
&lt;div&gt;Elfving&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Config impacts in prj.config</title><link>https://devzone.nordicsemi.com/thread/511214?ContentTypeID=1</link><pubDate>Wed, 20 Nov 2024 05:50:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9213e705-d171-4a32-8f38-6402ac7747fc</guid><dc:creator>MontanaEE</dc:creator><description>&lt;p&gt;From the build:&lt;/p&gt;
&lt;p&gt;warning: UART_INTERRUPT_DRIVEN (defined at boards/shields\sparkfun_sara_r4\Kconfig.defconfig:24,&lt;br /&gt;boards/shields\wnc_m14a2a\Kconfig.defconfig:17, soc/arm\quicklogic_eos_s3\Kconfig.defconfig:17,&lt;br /&gt;drivers/serial/Kconfig:72) was assigned the value &amp;#39;n&amp;#39; but got the value &amp;#39;y&amp;#39;. See&lt;br /&gt;&lt;a href="http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UART_INTERRUPT_DRIVEN"&gt;docs.zephyrproject.org/.../kconfig.html&lt;/a&gt; and/or look up&lt;br /&gt;UART_INTERRUPT_DRIVEN in the menuconfig/guiconfig interface. The Application Development Primer,&lt;br /&gt;Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be&lt;br /&gt;helpful too.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;warning: SERIAL (defined at soc/arm/nxp_lpc/lpc55xxx\Kconfig.defconfig.lpc55S69_cpu1:14,&lt;br /&gt;drivers/serial/Kconfig:6) was assigned the value &amp;#39;n&amp;#39; but got the value &amp;#39;y&amp;#39;. See&lt;br /&gt;&lt;a href="http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_SERIAL"&gt;docs.zephyrproject.org/.../kconfig.html&lt;/a&gt; and/or look up SERIAL in the&lt;br /&gt;menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,&lt;br /&gt;and Kconfig - Tips and Best Practices sections of the manual might be helpful too.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;warning: MODEM_RECEIVER (defined at drivers/modem/Kconfig:17) was assigned the value &amp;#39;n&amp;#39; but got the&lt;br /&gt;value &amp;#39;y&amp;#39;. See &lt;a href="http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MODEM_RECEIVER"&gt;docs.zephyrproject.org/.../kconfig.html&lt;/a&gt; and/or look&lt;br /&gt;up MODEM_RECEIVER in the menuconfig/guiconfig interface. The Application Development Primer, Setting&lt;br /&gt;Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful&lt;br /&gt;too.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Config impacts in prj.config</title><link>https://devzone.nordicsemi.com/thread/511199?ContentTypeID=1</link><pubDate>Wed, 20 Nov 2024 01:29:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a21b9700-bde1-4408-a0f8-a64cb5cccc00</guid><dc:creator>MontanaEE</dc:creator><description>&lt;p&gt;Went through all of the configs that were listed as selectors for the interrupt driven option. Made sure they were set to &amp;quot;n&amp;quot; to disable, still interrupts are set to &amp;quot;yes&amp;quot; in the config.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>