<?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>NRF51822 sd_softdevice_enable freeze SDK 12.3 SD130 v2.0.1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50488/nrf51822-sd_softdevice_enable-freeze-sdk-12-3-sd130-v2-0-1</link><description>My app runs the following code, that is supposed to init the SoftDevice: 
 
 nrf_clock_lf_cfg_t clock_lf_cfg = { .source = NRF_CLOCK_LF_SRC_XTAL, .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM, }; 
 // Initialize the SoftDevice handler module. SOFTDEVICE_HANDLER_INIT</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Aug 2019 07:33:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50488/nrf51822-sd_softdevice_enable-freeze-sdk-12-3-sd130-v2-0-1" /><item><title>RE: NRF51822 sd_softdevice_enable freeze SDK 12.3 SD130 v2.0.1</title><link>https://devzone.nordicsemi.com/thread/202320?ContentTypeID=1</link><pubDate>Mon, 05 Aug 2019 07:33:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:25f931fa-0abb-4b3c-9166-ea604dfac396</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;The disadvantage is slightly increased current consumption as the Softdevice need to increase RX windows account for the lower clock tolerance and perform periodic calibration of the oscillator. But the app_timer will work as before, just not as accurate (20 ppm vs 250 ppm)&lt;/p&gt;
&lt;p&gt;Softdevice setting to use internal RC oscillator:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;    nrf_clock_lf_cfg_t clock_lf_cfg = { .source  = NRF_CLOCK_LF_SRC_RC,
                                        .rc_ctiv = 4,
                                        .rc_temp_ctiv = 1 };&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF51822 sd_softdevice_enable freeze SDK 12.3 SD130 v2.0.1</title><link>https://devzone.nordicsemi.com/thread/201974?ContentTypeID=1</link><pubDate>Thu, 01 Aug 2019 16:29:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6ec3cf75-a5ce-4935-9ba5-e30c4fe52c34</guid><dc:creator>Daniel Dakhno</dc:creator><description>&lt;p&gt;&lt;span&gt;Does that have any disadvantages? How do i get app_timer to work?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF51822 sd_softdevice_enable freeze SDK 12.3 SD130 v2.0.1</title><link>https://devzone.nordicsemi.com/thread/201798?ContentTypeID=1</link><pubDate>Thu, 01 Aug 2019 09:58:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e75b2b5-6f6f-4a50-9f04-36967cc3293b</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Yes, it looks like it only has the footprint for&amp;nbsp;a LF crystal unfortunately.&amp;nbsp; In that case you need to select the internal RC oscillator when you enable the Softdevice.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF51822 sd_softdevice_enable freeze SDK 12.3 SD130 v2.0.1</title><link>https://devzone.nordicsemi.com/thread/201794?ContentTypeID=1</link><pubDate>Thu, 01 Aug 2019 09:48:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aa5876a0-9ac8-4a86-938f-8e94d618a90f</guid><dc:creator>Daniel Dakhno</dc:creator><description>&lt;p&gt;You are right, that is what i initially wanted to do, but failed through brainless copy-pasting.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;With the XTAL it gets stuck in the loop, indeed.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I am using this board:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " height="200" src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1564652820577v2.jpeg" width="200" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;although in reality it looks like this:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " height="194" src="https://sc01.alicdn.com/kf/HTB11GAHSXXXXXaiXpXXq6xXFXXXo/MS49SF1-Bluetooth-4-0-low-cost-board.jpg" width="194" /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Is it possible that the difference between the pictures is indeed the missing Crystal?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Also, using app_timer and System on mode, are there any advantages to an external crystal?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF51822 sd_softdevice_enable freeze SDK 12.3 SD130 v2.0.1</title><link>https://devzone.nordicsemi.com/thread/201745?ContentTypeID=1</link><pubDate>Thu, 01 Aug 2019 06:59:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7a73672-948a-49a3-88df-c43ee31f7361</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Are you sure the&amp;nbsp;new board supposed to have a 32 KHz LF crystal mounted? As you may have seen from other posts, the&amp;nbsp;Softdevice enable function&amp;nbsp;can&amp;nbsp;get stuck in a loop and never return if you select the wrong clock source or have a bad clock circuit.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I suggest to try starting the clock manually like you did, but with the clock source set to xtal. Then see if you get the started event.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;//NRF_CLOCK-&amp;gt;LFCLKSRC = (CLOCK_LFCLKSRC_SRC_RC &amp;lt;&amp;lt; CLOCK_LFCLKSRC_SRC_Pos);
NRF_CLOCK-&amp;gt;LFCLKSRC = 1; //XTAL
NRF_CLOCK-&amp;gt;EVENTS_LFCLKSTARTED = 0;
NRF_CLOCK-&amp;gt;TASKS_LFCLKSTART = 1;

while (NRF_CLOCK-&amp;gt;EVENTS_LFCLKSTARTED == 0)
{
// Do nothing.
}&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>