<?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>ADC channel changes from NCS 3.1.1 to NCS 3.2.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127630/adc-channel-changes-from-ncs-3-1-1-to-ncs-3-2-0</link><description>Hi Nordic, 
 I&amp;#39;m using custom board based on nrf52840 SoC. After migrating the SDK, the original device tree configuration for ADC became unavailable, but I failed to find relevant explanations in the SDK migration guide. Through my own attempts, I modified</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Apr 2026 03:51:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127630/adc-channel-changes-from-ncs-3-1-1-to-ncs-3-2-0" /><item><title>RE: ADC channel changes from NCS 3.1.1 to NCS 3.2.0</title><link>https://devzone.nordicsemi.com/thread/564429?ContentTypeID=1</link><pubDate>Fri, 03 Apr 2026 03:51:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2754d481-6ed8-451d-bd30-dc5909ac87d6</guid><dc:creator>brave_niuniu</dc:creator><description>&lt;p&gt;Hi runar,&lt;/p&gt;
&lt;p&gt;Thanks for your reply, &lt;span&gt;I found that this problem was caused by setting the wrong channel in the adc_channel_setup() function in the application, not an issue with the device tree.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADC channel changes from NCS 3.1.1 to NCS 3.2.0</title><link>https://devzone.nordicsemi.com/thread/564363?ContentTypeID=1</link><pubDate>Wed, 01 Apr 2026 09:01:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:201d4b40-b052-440d-b1d8-24e902cb3891</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Update:&lt;/p&gt;
&lt;p&gt;So Zephyr has&amp;nbsp;made some changes in the ADC driver and you now need to configure each channel by themself compared to how it was before.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
[quote user=""]&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;1.This error occurs during ADC setup when using channel 7 in NCS 3.2.0: &amp;lt;err&amp;gt; adc_nrfx_saadc: Cannot configure channel 0: -22. Normally, all 8 channels should be usable properly. I don&amp;#39;t know why the error occurs in NCS 3.2.0.&lt;/span&gt;&lt;/p&gt;[/quote]
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Your overlay seems to be valid for me. Can you do a pristine build and compare your overlay.dts to the generated one after building?&amp;nbsp;&lt;/p&gt;
[quote user=""]2.If I do not use channel 6 but other channels such as channel 0 and channel 1, the voltage collected using adc_raw_to_millivolts(); will not be valid data. I do not see any other ADC channels being used in the final generated zephyr.dts, so I am not sure what exactly causes only channel 6 to be able to collect valid battery level data.[/quote]
&lt;p&gt;This makes sense as as i presume your battery divider is is connected to pin corresponding to AIN7. No other channel can see the signal if you don&amp;#39;t change the dts.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADC channel changes from NCS 3.1.1 to NCS 3.2.0</title><link>https://devzone.nordicsemi.com/thread/564313?ContentTypeID=1</link><pubDate>Tue, 31 Mar 2026 13:08:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2b0b487-c3d3-42f4-bf89-66566fc35dfb</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I will investigate this. It might be related to new nrfx version where they introduced a log of breaking changes ref&amp;nbsp;&lt;a href="https://github.com/NordicSemiconductor/nrfx/blob/master/doc/nrfx_4_0_migration_guide.md"&gt;https://github.com/NordicSemiconductor/nrfx/blob/master/doc/nrfx_4_0_migration_guide.md&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADC channel changes from NCS 3.1.1 to NCS 3.2.0</title><link>https://devzone.nordicsemi.com/thread/564275?ContentTypeID=1</link><pubDate>Tue, 31 Mar 2026 01:27:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c977435c-a848-401f-be1e-550119270b40</guid><dc:creator>brave_niuniu</dc:creator><description>&lt;p&gt;Thanks for your advice, but&amp;nbsp;&lt;span&gt;the same error occurs in NCS 3.2.4&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ADC channel changes from NCS 3.1.1 to NCS 3.2.0</title><link>https://devzone.nordicsemi.com/thread/564243?ContentTypeID=1</link><pubDate>Mon, 30 Mar 2026 10:03:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30ca6b4a-15fd-4bb3-9107-49ce4656c859</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Try NCS 3.2.4 version. Your problems sound very much like a known bug to me.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>