<?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>Interrupt from timer2 at  0.5 ms using Softdevice</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8568/interrupt-from-timer2-at-0-5-ms-using-softdevice</link><description>Hi,I have need to set TIMER2 interrupt at high priority because I need a interrupt at 0.5ms.
This interrupt must comes while Softdevice is enable and my device(nrf51822 beacon) is connect with NRF51822 dongle.I set timer period right,and timer2 function</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 06 Aug 2015 08:34:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8568/interrupt-from-timer2-at-0-5-ms-using-softdevice" /><item><title>RE: Interrupt from timer2 at  0.5 ms using Softdevice</title><link>https://devzone.nordicsemi.com/thread/31323?ContentTypeID=1</link><pubDate>Thu, 06 Aug 2015 08:34:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:34a65c3c-55fe-4cfc-b1ac-3a52ec17b92b</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;I wonder how many times this question is going to be asked.&lt;/p&gt;
&lt;p&gt;You can&amp;#39;t do accurately timed interrupts with the softdevice running. Look at the softdevice spec for the softdevice you&amp;#39;re using (and which softdevice are you actually using, S110? which revision?)&lt;/p&gt;
&lt;p&gt;The softdevice is of higher priority while it&amp;#39;s communicating over bluetooth. The latest softdevice processes for less time than the older ones, but they all will beat any user interrupt and the older softdevices also suspend the CPU. There are tables in the spec which show you for how long interrupts can be delayed. For the latest softdevice that&amp;#39;s up to .5ms, for the older softdevice it&amp;#39;s several milliseconds.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>