<?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>Something simple</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/148/something-simple</link><description>I&amp;#39;m trying without much success to write something fairly simple. Basically connect a signal to a pin, and run a function whenever that pin changes state. What&amp;#39;s confusing me is how do I tie everything up so that my function is triggered based on the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 10 Jun 2014 15:06:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/148/something-simple" /><item><title>RE: Something simple</title><link>https://devzone.nordicsemi.com/thread/819?ContentTypeID=1</link><pubDate>Tue, 10 Jun 2014 15:06:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f78c3cf5-ca10-4301-adb1-5ea67a9ddedf</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;The app_gpiote.c only uses the PORT event of the GPIOTE peripheral, so it will not cause any high current consumption. It is correct that it is the IN/OUT registers (set in NRF_GPIOTE-&amp;gt;CONFIG[] registers) that cause higher current consumption (due to them requiring the 16M clocktree, which gives you ~1mA added current consumption)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Something simple</title><link>https://devzone.nordicsemi.com/thread/818?ContentTypeID=1</link><pubDate>Sun, 08 Jun 2014 03:14:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e066e293-0b65-460b-be41-46abacd16c6c</guid><dc:creator>paul-b</dc:creator><description>&lt;p&gt;Hi Hakon, thanks for the quick response.  I&amp;#39;m still a little unsure about what particular setting causes the extra power to be consumed as in PAN-39.  Judging by this thread (&lt;a href="https://devzone.nordicsemi.com/question/2471/gpio-wakeup-low-power-workarounds/)"&gt;devzone.nordicsemi.com/.../)&lt;/a&gt;, it appears that the problematic power consumption during Sleep mode is specific to setting the NRF_GPIOTE-&amp;gt;CONFIG register.  Is that correct?  Would any of the APIs in app_gpiote.c,h trigger the problem?  Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Something simple</title><link>https://devzone.nordicsemi.com/thread/817?ContentTypeID=1</link><pubDate>Fri, 06 Jun 2014 09:35:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:56b1ca51-f3f0-46d2-bb81-c9b8498f1df7</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi Paul,&lt;/p&gt;
&lt;p&gt;We&amp;#39;re still working on restoring older links, sorry for the inconvenience.
The GPIOTE port event is available here:
&lt;a href="https://github.com/NordicSemiconductor/nrf51-powerdown-examples/tree/master/system-on-wakeup-on-gpio"&gt;github.com/.../system-on-wakeup-on-gpio&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;And the RTC trigger ADC example is available here:
&lt;a href="https://github.com/NordicSemiconductor/nrf51-ADC-examples/tree/master/rtc0-triggering-adc-sample"&gt;github.com/.../rtc0-triggering-adc-sample&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Something simple</title><link>https://devzone.nordicsemi.com/thread/816?ContentTypeID=1</link><pubDate>Thu, 05 Jun 2014 18:20:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d6ca8e7-76c8-4391-89a1-6f0204877065</guid><dc:creator>paul-b</dc:creator><description>&lt;p&gt;Hi Hakon, Nordic, I know this is a very old thread, but this example code could be very useful to workaround the GPIO power issue documented in the PAN.  Can you please restore the C and Zip file referenced here?  Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Something simple</title><link>https://devzone.nordicsemi.com/thread/815?ContentTypeID=1</link><pubDate>Wed, 24 Jul 2013 13:23:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a5f46f37-b88d-4750-8936-1af9b4618cc4</guid><dc:creator>sd</dc:creator><description>&lt;p&gt;OK, got it to work. Thanks for the help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Something simple</title><link>https://devzone.nordicsemi.com/thread/814?ContentTypeID=1</link><pubDate>Wed, 24 Jul 2013 08:34:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf033d05-83ab-4030-8bbf-50f3f7627dd0</guid><dc:creator>sd</dc:creator><description>&lt;p&gt;I suspect that with the framework in the HRS example doing what I want  should be very straight froward, but I&amp;#39;m not able to make it work yet.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Something simple</title><link>https://devzone.nordicsemi.com/thread/813?ContentTypeID=1</link><pubDate>Wed, 24 Jul 2013 08:25:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31c0738d-5027-4b5b-904c-332a284242e7</guid><dc:creator>sd</dc:creator><description>&lt;p&gt;Thanks! I think you&amp;#39;re right (looking at your example). Since I&amp;#39;m trying to integrate this into the heart rate monitor example, I&amp;#39;m now looking into getting this to work with the existing GPIOTE IRQHandler... it&amp;#39;s not that easy tracing all the events and calls ;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Something simple</title><link>https://devzone.nordicsemi.com/thread/812?ContentTypeID=1</link><pubDate>Wed, 24 Jul 2013 07:57:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:52d3faa7-d408-42b2-b15c-41983dec1828</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I think you are over-engineering your problem a bit.
Its not possible to have the GPIOTE/PPI to start a function call in such a &amp;quot;direct way&amp;quot;.
From your question, it seems like you want to generate an interrupt based on pin-change, and then run a function in code. This can be done using the GPIOTE PORT event. I am attaching an example on how to do this.&lt;/p&gt;
&lt;p&gt;However, if you&amp;#39;d like to trigger a &amp;quot;chain reaction&amp;quot;, for instance that pin change starts the ADC or similar, you can do this with PPI/GPIOTE. I am also attaching a example that triggers ADC each RTC TICK.&lt;/p&gt;
&lt;p&gt;BR
Håkon&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/rtc_5F00_trigger_5F00_adc.c"&gt;rtc_trigger_adc.c&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/GPIOTE_5F00_Port_5F00_event.zip"&gt;GPIOTE_Port_event.zip&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>