<?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>Using Simple Timer with SoftDevice</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/73243/using-simple-timer-with-softdevice</link><description>Device: nRF52840 
 SDK: 16.0. 
 Softdevice: 6.1.1 
 Hello, 
 I&amp;#39;m using Timer 2 peripheral using simple timer driver. It&amp;#39;s working fine but I have serious drift/accuracy issue. The timer drifts about 5s in 30mins. I don&amp;#39;t understand why so much drift is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 06 Apr 2021 13:40:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/73243/using-simple-timer-with-softdevice" /><item><title>RE: Using Simple Timer with SoftDevice</title><link>https://devzone.nordicsemi.com/thread/303195?ContentTypeID=1</link><pubDate>Tue, 06 Apr 2021 13:40:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d1608c5-822d-41f5-a9b6-a6ed36ca097b</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;I see.. Are you using custom HW? If so, can you let me know which crystal you are using and if more variants, which CL value the specific one you use have? Also please share your circuitry around the HF crystal and value of your load caps.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Simple Timer with SoftDevice</title><link>https://devzone.nordicsemi.com/thread/303106?ContentTypeID=1</link><pubDate>Tue, 06 Apr 2021 10:58:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8acab4e5-1121-4d3f-baf1-8a35551913a3</guid><dc:creator>Aftab</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I made sure that 16MHz clock source is being used by using the code you posted above.&lt;/p&gt;
&lt;p&gt;Still I see lot&amp;#39;s of variation, the clock source have no positive effect on it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using Simple Timer with SoftDevice</title><link>https://devzone.nordicsemi.com/thread/301923?ContentTypeID=1</link><pubDate>Thu, 25 Mar 2021 13:35:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b8358a87-f28d-4b6f-ba8b-ceaffdcd0d06</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Unless you explicitly start the HFXO (crystal oscillator) the HFINT (RC oscillator) is used, and that has a quite low accuracy. I suggest you start the HFXO and measure again. You can do that for instance using&amp;nbsp;&lt;code&gt;nrf_drv_clock_hfclk_request()&lt;/code&gt; or using this code snippet:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;    // Start 64 MHz crystal oscillator.
    NRF_CLOCK-&amp;gt;EVENTS_HFCLKSTARTED = 0;
    NRF_CLOCK-&amp;gt;TASKS_HFCLKSTART    = 1;

    // Wait for the external oscillator to start up.
    while (NRF_CLOCK-&amp;gt;EVENTS_HFCLKSTARTED == 0)
    {
        // Do nothing.
    }&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>