<?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>NRF_TIMER drifts consistently at 2850 ppm relative to the same code on a different DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/60024/nrf_timer-drifts-consistently-at-2850-ppm-relative-to-the-same-code-on-a-different-dk</link><description>I&amp;#39;m using two nRF52840 dev kits, both running with the same code. 
 
 I start the timer and every 20 ms, when the timer expires, I set a new 20ms timer, and in handler(), I increment a number. When that number reaches a multiple of 256, I drive a GPIO</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 Apr 2020 21:20:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/60024/nrf_timer-drifts-consistently-at-2850-ppm-relative-to-the-same-code-on-a-different-dk" /><item><title>RE: NRF_TIMER drifts consistently at 2850 ppm relative to the same code on a different DK</title><link>https://devzone.nordicsemi.com/thread/244195?ContentTypeID=1</link><pubDate>Thu, 09 Apr 2020 21:20:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:44ab2731-c564-48ac-9016-6b6701db99a8</guid><dc:creator>Collin</dc:creator><description>&lt;p&gt;Thanks! I added:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;NRF_CLOCK-&amp;gt;TASKS_HFCLKSTART = 1;&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;And I&amp;#39;m seeing much less drift now.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_TIMER drifts consistently at 2850 ppm relative to the same code on a different DK</title><link>https://devzone.nordicsemi.com/thread/244156?ContentTypeID=1</link><pubDate>Thu, 09 Apr 2020 07:38:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b7eab7d-0179-4b7b-85b9-e9049e9e0603</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;The HFINT clock source is an HF RC oscillator and it is not accurate at all with large variations from device-to-device. From&amp;nbsp;&lt;a title="64 MHz internal oscillator (HFINT)" href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/clock.html?cp=4_0_0_4_3_3_0#unique_707850542"&gt;64 MHz internal oscillator (HFINT)&lt;/a&gt;&amp;nbsp;specs:&amp;nbsp;&lt;/p&gt;
&lt;table border="1" cellpadding="4" cellspacing="0" frame="border" rules="all" summary=""&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td colspan="1" headers="d77729e19147" rowspan="1"&gt;f&lt;sub&gt;TOL_CAL_LFULP&lt;/sub&gt;&lt;/td&gt;
&lt;td colspan="1" headers="d77729e19150" rowspan="1"&gt;
&lt;p&gt;Frequency tolerance after calibration&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/clock.html?cp=4_0_0_4_3_3_0#fntarg_2" name="fnsrc_2"&gt;&lt;sup&gt;2&lt;/sup&gt;&lt;/a&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d77729e19153" rowspan="1"&gt;&lt;/td&gt;
&lt;td colspan="1" headers="d77729e19156" rowspan="1"&gt;&lt;/td&gt;
&lt;td colspan="1" headers="d77729e19159" rowspan="1"&gt;&lt;/td&gt;
&lt;td colspan="1" headers="d77729e19163" rowspan="1"&gt;&lt;span&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td colspan="1" headers="d77729e19166" rowspan="1"&gt;&lt;span&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td colspan="1" headers="d77729e19169" rowspan="1"&gt;&lt;span&gt;±2000&lt;/span&gt;&lt;/td&gt;
&lt;td colspan="1" headers="d77729e19172" rowspan="1"&gt;ppm&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Your findings are expected, I suggest you turn on the HFXO as it is&amp;nbsp;&amp;lt; +/-50ppm on the DKs.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>