<?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>S110 src\soc_clock.c line 258 assert</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/111636/s110-src-soc_clock-c-line-258-assert</link><description>Hi, We are currently developing a embedded system utilizing timeslots. When the device gets awoken from deepsleep we want to get a timeslot as soon as possible in order to conserve battery. After the SVCALL sd_softdevice_enable we have to delay roughly</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 03 Jun 2024 08:09:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/111636/s110-src-soc_clock-c-line-258-assert" /><item><title>RE: S110 src\soc_clock.c line 258 assert</title><link>https://devzone.nordicsemi.com/thread/487047?ContentTypeID=1</link><pubDate>Mon, 03 Jun 2024 08:09:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:312155c4-df40-445f-ab17-6d8787a0b1ca</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Good to hear. I will close the ticket then &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 src\soc_clock.c line 258 assert</title><link>https://devzone.nordicsemi.com/thread/486920?ContentTypeID=1</link><pubDate>Fri, 31 May 2024 13:14:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aace0ac2-53e9-414e-87d4-2c8b681ad64b</guid><dc:creator>Marcus_P</dc:creator><description>&lt;p&gt;I failed to mention that this is a FW-update for an older product. We are well aware of BT SIG and have since moved new developments to S130&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 src\soc_clock.c line 258 assert</title><link>https://devzone.nordicsemi.com/thread/486879?ContentTypeID=1</link><pubDate>Fri, 31 May 2024 11:28:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:273bd80c-e8d2-44fc-a362-76b2d651f615</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi again&lt;/p&gt;
&lt;p&gt;Just to elaborate on my earlier comment, the reason the S110 shouldn&amp;#39;t be used for new designs is that the Bluetooth version it uses is deprecated by the BT SIG. Fore more information please have a look &lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/what-impact-does-the-deprecation-and-withdrawal-of-bluetooth-core-specification-v4-0-and-v4-1-have-on-your-current-and-future-products"&gt;here&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 src\soc_clock.c line 258 assert</title><link>https://devzone.nordicsemi.com/thread/486821?ContentTypeID=1</link><pubDate>Fri, 31 May 2024 08:51:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ae25771f-0d89-4984-9a6c-8bd8cbaead9f</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;That&amp;#39;s great news Marcus, I will close the ticket then.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;And as a side note,&amp;nbsp;I would not recommend staring&amp;nbsp;new projects using the S110 and the nRF51 series.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 src\soc_clock.c line 258 assert</title><link>https://devzone.nordicsemi.com/thread/486702?ContentTypeID=1</link><pubDate>Thu, 30 May 2024 13:44:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:91330595-bc51-404c-9d0d-dc208008756f</guid><dc:creator>Marcus_P</dc:creator><description>&lt;p&gt;Hi Torbj&amp;oslash;rn,&lt;br /&gt;&lt;br /&gt;We found the issue.&lt;br /&gt;If you request a timeslot with&amp;nbsp;NRF_RADIO_HFCLK_CFG_FORCE_XTAL before SD has gotten the chance to enable XTAL it will give the assert.&lt;br /&gt;&lt;br /&gt;The workaround we implemented:&lt;br /&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_TEMP_4000MS_CALIBRATION, NULL);

while((NRF_CLOCK-&amp;gt;HFCLKSTAT &amp;amp; CLOCK_HFCLKSTAT_SRC_Msk) != (CLOCK_HFCLKSTAT_SRC_Xtal &amp;lt;&amp;lt; CLOCK_HFCLKSTAT_SRC_Pos)) {
    nrf_delay_us(10);
}

// Continue to request timeslot and, when granted, make use of radio and timer0&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;This as far as we know only an issue on S110 and not on S130&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 src\soc_clock.c line 258 assert</title><link>https://devzone.nordicsemi.com/thread/486695?ContentTypeID=1</link><pubDate>Thu, 30 May 2024 13:33:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:796b63ea-0f63-4cf6-8e46-1a0ecdd3e7b1</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Which version of the S110 and the nRF5 SDK are you using?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you considered simply delaying the SoftDevice enable call, then you should be able to access SoftDevice resources right away without needing to use timeslots.&amp;nbsp;The question is whether or not this activity needs to go on continuously, or if you could halt it later to give you time to enable the SoftDevice once you need to use it.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>