<?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>Timeslot interrupt latency</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20500/timeslot-interrupt-latency</link><description>Hello, 
 Is there any way to mitigate delay of redirecting interrupts from softdevice to application? Using nRF51 with S130 there is ~2us delay even with SoftDevice disabled (as stated in SD documentation). 
 Regards</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 16 Mar 2017 14:31:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20500/timeslot-interrupt-latency" /><item><title>RE: Timeslot interrupt latency</title><link>https://devzone.nordicsemi.com/thread/79924?ContentTypeID=1</link><pubDate>Thu, 16 Mar 2017 14:31:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:675e0114-9064-4722-98fc-948a7123bcdc</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Wizath,&lt;/p&gt;
&lt;p&gt;If your application requires lower latency, you can think of setting up your application to work as a bootloader. This mean your application/bootloader will receive the interrupt forwarding directly from the MBR, which save you some time because for normal application it will be
MBR -&amp;gt; softdevice -&amp;gt; Application.&lt;/p&gt;
&lt;p&gt;Please refer to our DFU bootloader to see how it works and how you can forward back the interrupt to the softdevice by initializing it using SD_MBR_COMMAND_INIT_SD MBR command.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>