<?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>Problem after restarting SAADC</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/90827/problem-after-restarting-saadc</link><description>Hi, 
 today I faced a rather strange problem when trying to restart the SAADC. 
 Bit of context: a requirement for the product I&amp;#39;m developing changed and the device now must advertise in its idle mode instead of entering the system off mode. To save energy</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 11 Aug 2022 07:41:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/90827/problem-after-restarting-saadc" /><item><title>RE: Problem after restarting SAADC</title><link>https://devzone.nordicsemi.com/thread/381108?ContentTypeID=1</link><pubDate>Thu, 11 Aug 2022 07:41:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b496c905-78f2-4916-bb40-39d0ea846e53</guid><dc:creator>JoEi</dc:creator><description>&lt;p&gt;Hi Einar,&lt;/p&gt;
&lt;p&gt;thanks the workaround works like a charm. =)&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Johannes&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem after restarting SAADC</title><link>https://devzone.nordicsemi.com/thread/381102?ContentTypeID=1</link><pubDate>Thu, 11 Aug 2022 07:25:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f8f3771-5a43-41a3-bcc4-4096ef15b6f7</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I cannot say exactly why this is, but there are a few issues with the SAADC that could potentially play a part. You could try to look at&amp;nbsp;saadc_anomaly_212_workaround_apply() from&amp;nbsp;modules/hal/nordic/nrfx/drivers/src/nrfx_saadc.c in SDK 17.1.0 and consider doing something like this&amp;nbsp;when uniniting the SAADC driver. That will effectively reset the SAADC peripheral.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem after restarting SAADC</title><link>https://devzone.nordicsemi.com/thread/381021?ContentTypeID=1</link><pubDate>Wed, 10 Aug 2022 12:53:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:96cd0712-6b85-4aea-b7f9-508aa85d359c</guid><dc:creator>JoEi</dc:creator><description>&lt;p&gt;Ok in newer SDK versions this problem is fixed within the nrf_drv_saadc_init function.&lt;/p&gt;
&lt;p&gt;Anyhow after some testing I made a peculiar discovery regarding unitialising the SAADC.&lt;br /&gt;So far I&amp;#39;ve configured the SAADC with NRF_SAADC_OVERSAMLE_4X and 2 channels with burst mode active.&lt;br /&gt;After unitialising the SAADC I have a power consumption somewhere of the neighbourhood of 790&amp;micro;A.&lt;br /&gt;If I&amp;nbsp;configure the SAADC without oversampling and the channels without burst mode after unitialising the SAADC I get a power consumption around 150&amp;micro;A.&lt;/p&gt;
&lt;p&gt;Does anyone have an idea why there is such a difference?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>