<?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>BLE Blocking Interrupts</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7076/ble-blocking-interrupts</link><description>Hi, 
 I am using the nRF51822 with an external chip. The nRF51822 has interrupts which trigger when one of the signals from the external chip goes low. When using BLE and the CPU is blocked during transmission of the radio, the interrupts are not triggered</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 16 May 2015 14:08:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7076/ble-blocking-interrupts" /><item><title>RE: BLE Blocking Interrupts</title><link>https://devzone.nordicsemi.com/thread/25006?ContentTypeID=1</link><pubDate>Sat, 16 May 2015 14:08:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:705b9b91-83ab-49b6-9168-b5b4e4039812</guid><dc:creator>Jack</dc:creator><description>&lt;p&gt;Many thanks for your help, RK!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Blocking Interrupts</title><link>https://devzone.nordicsemi.com/thread/25005?ContentTypeID=1</link><pubDate>Sat, 16 May 2015 01:03:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dec10d68-e547-4c42-aa34-03c18cce7bd9</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;No there isn&amp;#39;t. The BLE stack has precise timing requirements and so it runs at a higher priority than everything else.&lt;/p&gt;
&lt;p&gt;If you search you will find dozens of threads about this which tell you about how the newer versions of chip/softdevice tie up the processor for less time, how the multiprotocol timeslot API can give you short intervals you can work in etc. However the BTLE stack will always take precedence and if your interrupts are at random times, you will not always get serviced until the stack has finished its work.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>