<?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>S120 interrupt latency</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5058/s120-interrupt-latency</link><description>We have an NRF51822 running S120 at 32MHz. 
 Our system has two removable batteries. If a battery is removed we need to switch to the other battery as fast as possible. We would like to do this in an interrupt service routine. ie detect battery fail</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 16 Jan 2015 16:27:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5058/s120-interrupt-latency" /><item><title>RE: S120 interrupt latency</title><link>https://devzone.nordicsemi.com/thread/17796?ContentTypeID=1</link><pubDate>Fri, 16 Jan 2015 16:27:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c7291365-0504-453e-97dd-cb19cf6d5338</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Charles,&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t think we can do anything to reduce the 1400usec maximum latency.&lt;/p&gt;
&lt;p&gt;However, the idea of using the PPI is not a bad idea. You can use the PPI to connect the GPIO task with the event from the LPCOMP to detect the drop in the input voltage compare to a reference voltage. Please have a look at chapter 32 in the RM.
But be aware that using PPI, GPIO task and LPCOMP will of course draw some extra current.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S120 interrupt latency</title><link>https://devzone.nordicsemi.com/thread/17795?ContentTypeID=1</link><pubDate>Thu, 08 Jan 2015 04:27:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:43c5b77d-705d-439d-ab9d-22078e443701</guid><dc:creator>Charles Manning</dc:creator><description>&lt;p&gt;I&amp;#39;m thinking of an alternative here:&lt;/p&gt;
&lt;p&gt;Perhaps I can use the GPIOTE engine and the PPI to use the change on one pin to trigger the other. Does that sound plausible?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>