<?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>NRF51 Timer 2 accuracy</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/17294/nrf51-timer-2-accuracy</link><description>I&amp;#39;m using PPI to trigger a gpio high after a given delay from 4.00 ms to 8.00 ms. I need to be accurate up to .01 ms but i&amp;#39;m seeing some jitter in the actual delay vs given delay. Is there any way I can ensure I can be accurate to .01 ms?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 Oct 2016 19:34:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/17294/nrf51-timer-2-accuracy" /><item><title>RE: NRF51 Timer 2 accuracy</title><link>https://devzone.nordicsemi.com/thread/66460?ContentTypeID=1</link><pubDate>Wed, 26 Oct 2016 19:34:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:120c0174-290c-4a1b-972f-e8dfe63addff</guid><dc:creator>Ron</dc:creator><description>&lt;p&gt;I managed a way to verify the timer value on my event trigger and those seem to be consistent. That leads me to believe that the jitter is the ppi failing to be accurate in setting the gpio signal to high.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF51 Timer 2 accuracy</title><link>https://devzone.nordicsemi.com/thread/66459?ContentTypeID=1</link><pubDate>Wed, 26 Oct 2016 06:55:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b570a0e2-f121-4469-8c65-3646e3d19dac</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;You can that anytime after enabling softdevice (SD) since you are coordinating well with SD by using its API. remember to release it before going to low power and request again on wakeup else your sleep current will be high.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF51 Timer 2 accuracy</title><link>https://devzone.nordicsemi.com/thread/66458?ContentTypeID=1</link><pubDate>Tue, 25 Oct 2016 14:30:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:36da1c29-113f-4a86-9129-b3fac439faeb</guid><dc:creator>Ron</dc:creator><description>&lt;p&gt;At what point would be best to start this? I am using bluetooth as well. I have the following before i start advertising and start my application loop.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;sd_clock_hfclk_is_running(&amp;amp;err_code);

if (!err_code) {
    sd_clock_hfclk_request();
}
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF51 Timer 2 accuracy</title><link>https://devzone.nordicsemi.com/thread/66457?ContentTypeID=1</link><pubDate>Tue, 25 Oct 2016 07:33:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93bb9b32-48bf-4725-9cb9-7eb0e0752520</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;start the HF Crystal oscillator. If you are using internal RC for HFCLK, it will be less accurate.
Do this by&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;NRF_CLOCK-&amp;gt;TASKS_HFCLKSTART = 1;
while(0 == NRF_CLOCK-&amp;gt;EVENTS_HFCLKSTARTED);
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>