<?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>APP High interrupt latency</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/4768/app-high-interrupt-latency</link><description>Hi, 
 I have application where I drive LEDs with shift registers. I need to send 14 bytes via SPI every 200us while I am in BLE connection. Timing should be exact as shift reg STROBE signal is taking place every 200us. I think to use Timer1 to generate</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 10 Dec 2014 13:04:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/4768/app-high-interrupt-latency" /><item><title>RE: APP High interrupt latency</title><link>https://devzone.nordicsemi.com/thread/16867?ContentTypeID=1</link><pubDate>Wed, 10 Dec 2014 13:04:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ed5348f-1837-4485-8345-66c2febb6c75</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;As specified in the S110 SDS, BLE connection event blocks the CPU from approximately 1ms-6ms, depending on the number of packets sent in each connection event. Even though you are not sending any payload data, BLE protocol will send empty packets to maintain the connection. A BLE connection event with no payload data will still block the CPU for ~800us.&lt;/p&gt;
&lt;p&gt;The above is true for the second revision nRF51 hardware. For the Third revision hardware and S110 v7.1.0, shorter blocking time is possible. How to unblock the CPU and enable the short CPU time is described on &lt;a href="https://devzone.nordicsemi.com/question/18751/how-to-unblock-the-cpu-during-connection-intervals-with-s110-v710/"&gt;this thead&lt;/a&gt;. To identify the nRF51 hardware revision is described on &lt;a href="https://devzone.nordicsemi.com/question/18925/nrf51822-revision/"&gt;this thread&lt;/a&gt;. &lt;a href="https://devzone.nordicsemi.com/question/21615/realtime-interrupt-with-50us-processing-possible-with-s110/"&gt;This thread&lt;/a&gt; might also be helpful.&lt;/p&gt;
&lt;p&gt;There will soon be released a new S110 SDS which will specify the CPU blocking times for 3rd revision nRF51 hardware.&lt;/p&gt;
&lt;p&gt;To know when BLE advertising/connection events take place, there are some pointers on &lt;a href="https://devzone.nordicsemi.com/question/22612/detect-if-code-has-been-interrupted-by-softdevice/?answer=22678#post-id-22678"&gt;this thread&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>