<?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>Any issues without external crystal besides power ?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/21192/any-issues-without-external-crystal-besides-power</link><description>If you dont have an external 32Khz crystal for the nRF52832, besides the higher power consumption, are there any other issues ? e.g. CPU starvation affecting my app during recalibration, how does recalibration affect longer running operations like DFU</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 11 Apr 2017 16:30:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/21192/any-issues-without-external-crystal-besides-power" /><item><title>RE: Any issues without external crystal besides power ?</title><link>https://devzone.nordicsemi.com/thread/82926?ContentTypeID=1</link><pubDate>Tue, 11 Apr 2017 16:30:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:403f2aa2-97be-4e8e-8b0d-2fc51764d5cc</guid><dc:creator>ShannonPahl</dc:creator><description>&lt;p&gt;great, thanks for the help&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Any issues without external crystal besides power ?</title><link>https://devzone.nordicsemi.com/thread/82925?ContentTypeID=1</link><pubDate>Mon, 10 Apr 2017 15:04:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c76214ab-8026-43b5-9337-f61f5b56b714</guid><dc:creator>Stian R&amp;#248;ed Hafskjold</dc:creator><description>&lt;p&gt;The calibration is not blocking, so it can run while the CPU is doing other stuff. You can use PPI with the calibration timer to start calibration without any CPU interaction. This is handled by the SoftDevice btw. As long as the accuracy (ppm) of the LFRC is given to the SoftDevice while you enable it, the stability is as good as when you use LFXO, since the SD will increase the window widening on the RX event corresponding to the accuracy given.&lt;/p&gt;
&lt;p&gt;Regarding current consumption using the LFRC vs the LFXO, you can have a look at &lt;a href="https://devzone.nordicsemi.com/question/81847/how-much-current-consumption-when-we-use-internal-32k-rc/"&gt;this post&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For the nRF51 you had the choice to only calibrate if the temperature had changed. For nRF52 the SD will calibrate the clock even though the temp is stable. Please see the notes in the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v4.0.2/structnrf__clock__lf__cfg__t.html"&gt;SD spec here&lt;/a&gt;.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;For nRF52, the application must ensure
calibration at least once every 8
seconds to ensure +/-250 ppm clock
stability. The recommended
configuration for NRF_CLOCK_LF_SRC_RC
on nRF52 is rc_ctiv=16 and
rc_temp_ctiv=2. This will ensure
calibration at least once every 8
seconds and for temperature changes of
0.5 degrees Celsius every 4 seconds.&lt;/p&gt;
&lt;/blockquote&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>