<?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>TIMER2 running at 500us interval with ANT stack enabled</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6459/timer2-running-at-500us-interval-with-ant-stack-enabled</link><description>I have TIMER2 running at 500us interval. ANT is working as 100Hz master.
Understood softdevice will affect the timing and cause some latency.
I am guessing it is delaying the TIMER2_IRQHandler response by more than 500us which is enough to miss a TIMER2</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Apr 2015 13:15:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6459/timer2-running-at-500us-interval-with-ant-stack-enabled" /><item><title>RE: TIMER2 running at 500us interval with ANT stack enabled</title><link>https://devzone.nordicsemi.com/thread/22533?ContentTypeID=1</link><pubDate>Tue, 14 Apr 2015 13:15:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a81b5ed2-225d-44d3-a669-c82484562c99</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;Hi Paul&lt;/p&gt;
&lt;p&gt;I suspect you are correct, the ANT communication may be blocking the CPU for too long. Are you using S210 4.0.1? If so, look at the &lt;a href="https://www.nordicsemi.com/eng/nordic/Products/nRF51422/S210-SDS/20359"&gt;S210 SDS 2.0&lt;/a&gt; sections 11.2 and 11.3 for CPU availability. If your processing time for each TIMER2 interrupt is less than 100us, you could set the interrupt priority to APP_HIGH to see if that helps.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>