<?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>Use SAADC Limit to clear GPIO via PPI</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/30824/use-saadc-limit-to-clear-gpio-via-ppi</link><description>Hello, 
 I&amp;#39;m attempting to use a high-limit reached event from the SAADC to trigger the clearing of a GPIO. My wish is to disable this GPIO with the lowest possible latency, avoiding the need for the CPU to manually clear the pin. However, my current</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 22 Jun 2018 17:04:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/30824/use-saadc-limit-to-clear-gpio-via-ppi" /><item><title>RE: Use SAADC Limit to clear GPIO via PPI</title><link>https://devzone.nordicsemi.com/thread/137270?ContentTypeID=1</link><pubDate>Fri, 22 Jun 2018 17:04:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a51d1b9-78b4-494c-8268-4eda1774aa50</guid><dc:creator>juliantbrown</dc:creator><description>&lt;p&gt;That was an oversight on my part. We were also logging values from the SAADC for debug purposes, but for a release solution, the COMP/LPCOMP is the right call. This worked perfectly. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Use SAADC Limit to clear GPIO via PPI</title><link>https://devzone.nordicsemi.com/thread/122252?ContentTypeID=1</link><pubDate>Wed, 28 Feb 2018 10:14:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bdd4ddfd-c777-45f1-9e6b-4f9cb2175697</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;I do not see any particular reason why this should not work, what SDK version are you using and can it be that the SAADC event is already set?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Use SAADC Limit to clear GPIO via PPI</title><link>https://devzone.nordicsemi.com/thread/121855?ContentTypeID=1</link><pubDate>Sat, 24 Feb 2018 10:31:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:008713c4-a50a-48c6-b037-8bcc7ae1630e</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Why do you want to use the SAADC instead of the COMP or LPCOMP peripherial? The SAADC must be kept running &lt;strong&gt;and&lt;/strong&gt; sampling all the time, which implies significant current consumtion.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>