<?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>Current consumption &amp;gt;1 mA changing LFCLKSRC</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5961/current-consumption-1-ma-changing-lfclksrc</link><description>Hello, 
 in my application i use a bootloader for S310 and S310 V2.1.0. 
 The Bootloader is configured to use NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION and the application use NRF_CLOCK_LFCLKSRC_XTAL_20_PPM. I could now observe the following</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Mar 2015 16:32:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5961/current-consumption-1-ma-changing-lfclksrc" /><item><title>RE: Current consumption &gt;1 mA changing LFCLKSRC</title><link>https://devzone.nordicsemi.com/thread/20778?ContentTypeID=1</link><pubDate>Wed, 11 Mar 2015 16:32:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81c6bbef-7756-435e-9412-e7e4c8f72650</guid><dc:creator>Frederic</dc:creator><description>&lt;p&gt;Thanks for help, works great :-)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Current consumption &gt;1 mA changing LFCLKSRC</title><link>https://devzone.nordicsemi.com/thread/20777?ContentTypeID=1</link><pubDate>Wed, 11 Mar 2015 15:23:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:abeba0d1-760c-4970-9a2f-392a22114bb4</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Frederic: No it&amp;#39;s not fixed on the S310. But the same workaround can be used for S310.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Current consumption &gt;1 mA changing LFCLKSRC</title><link>https://devzone.nordicsemi.com/thread/20776?ContentTypeID=1</link><pubDate>Tue, 10 Mar 2015 16:09:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:086bd1e6-1a2d-47c9-bbce-1011fc54eff3</guid><dc:creator>Frederic</dc:creator><description>&lt;p&gt;ok, thank you i will try this solution.
At the moment i use the lastest version from S310 V2.0.1. So i think there is no S310 availbale with bugfix.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Current consumption &gt;1 mA changing LFCLKSRC</title><link>https://devzone.nordicsemi.com/thread/20775?ContentTypeID=1</link><pubDate>Tue, 10 Mar 2015 15:55:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5756b866-e458-4964-8ed4-b2c40103f7fb</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Frederic,&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a bug we found in S110 v7.x and earlier. The bug is fixed and documented in our S110 v8.0 release note.&lt;/p&gt;
&lt;p&gt;If you want to continue to use S110 v7.x and earlier, the work around is to call&lt;/p&gt;
&lt;p&gt;NRF_POWER-&amp;gt;TASKS_LOWPWR = 1;&lt;/p&gt;
&lt;p&gt;after you disable the softdevice in the bootloader or before you start the softdevice in the application.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Current consumption &gt;1 mA changing LFCLKSRC</title><link>https://devzone.nordicsemi.com/thread/20774?ContentTypeID=1</link><pubDate>Tue, 10 Mar 2015 09:00:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ff99533-f886-4588-99a4-c2f3f10b3799</guid><dc:creator>Frederic</dc:creator><description>&lt;p&gt;In documentation i found the following description:&lt;/p&gt;
&lt;p&gt;@note Some care must be taken if a low frequency clock source is already running when calling this function: If the LF clock has a different source then the one currently running, it will be stopped. Then, the new clock source will be started.&lt;/p&gt;
&lt;p&gt;@param clock_source Low frequency clock source and accuracy. (Note: In the case of XTAL source, the PPM accuracy of the chosen clock source must be greater than or equal to the actual characteristics of your XTAL clock).&lt;/p&gt;
&lt;p&gt;But why the current consumption only increase if i do a power on cycle? Can i stop the LFCLK manually before call SOFTDEVICE_HANDLER_INIT(...)?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>