<?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>nRF52 DK improper GPIOTE --&amp;gt; PPI configuration (no interrupts being raised on input toggle)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46152/nrf52-dk-improper-gpiote----ppi-configuration-no-interrupts-being-raised-on-input-toggle</link><description>Above is my code. I am using Keil uVision5 IDE on Windows 10. I am flashing s132 and then application hex to device using nRFGo. 
 
 My goal is to take a square wave as input to the nRF52 DK and measure the duration of each high and low in the signal</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 15 Apr 2019 06:03:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46152/nrf52-dk-improper-gpiote----ppi-configuration-no-interrupts-being-raised-on-input-toggle" /><item><title>RE: nRF52 DK improper GPIOTE --&gt; PPI configuration (no interrupts being raised on input toggle)</title><link>https://devzone.nordicsemi.com/thread/181977?ContentTypeID=1</link><pubDate>Mon, 15 Apr 2019 06:03:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8608bd45-665b-4156-bbbb-5b5d73c14ebf</guid><dc:creator>Dmitry</dc:creator><description>&lt;p&gt;You&amp;#39;re trying to receive analog signal on digital input. It shouldn&amp;#39;t be done such way. GPIO expects digital signal in range 0...VDD. For analog signal, configure pin as analog input and use COMP instead of GPIO. In any case input level should be in range 0...VDD, otherwise you need external schematic to ensure that.&lt;/p&gt;
&lt;p&gt;Try to connect your pin to GND then VDD, if there&amp;#39;s no change in read value, your chip rather didn&amp;#39;t withstand 6.6v input.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK improper GPIOTE --&gt; PPI configuration (no interrupts being raised on input toggle)</title><link>https://devzone.nordicsemi.com/thread/181970?ContentTypeID=1</link><pubDate>Sun, 14 Apr 2019 21:47:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e5f88809-6b9f-4a1c-9c4e-aa9f843ff611</guid><dc:creator>r_malito</dc:creator><description>&lt;p&gt;In main.c for loop: NRF_LOG_INFO(&amp;quot;PIN_IN value: %i&amp;quot;,nrf_gpio_pin_read(PIN_IN))&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Pin read on PIN_IN is always 1 if configured as&amp;nbsp;&lt;strong&gt;nrf_gpio_cfg_input(PIN_IN, NRF_GPIO_PIN_PULLUP);&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Pin read on PIN_IN is always 0 if configured as&amp;nbsp;&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;strong&gt;nrf_gpio_cfg_input(PIN_IN, NRF_GPIO_PIN_PULLDOWN);&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Pin read on PIN_IN is always 0 if configured as&amp;nbsp;&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;strong&gt;nrf_gpio_cfg_input(PIN_IN, NRF_GPIO_PIN_NOPULL);&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This seems to point to me having my waveform generator input signal incorrectly configured???&lt;/p&gt;
&lt;p&gt;I&amp;#39;m also printing my queue size in main as well to see if anything ever gets queued. Its always 0 as well.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK improper GPIOTE --&gt; PPI configuration (no interrupts being raised on input toggle)</title><link>https://devzone.nordicsemi.com/thread/181968?ContentTypeID=1</link><pubDate>Sun, 14 Apr 2019 20:06:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88868616-60a6-4ec9-9b44-a38a34eaa659</guid><dc:creator>Dmitry</dc:creator><description>&lt;p&gt;I don&amp;#39;t think supplying pin with 6.6v is a good idea :)&lt;/p&gt;
&lt;p&gt;Can you also print input value (nrf_gpio_pin_read(PIN_IN)) with RTT?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK improper GPIOTE --&gt; PPI configuration (no interrupts being raised on input toggle)</title><link>https://devzone.nordicsemi.com/thread/181953?ContentTypeID=1</link><pubDate>Sun, 14 Apr 2019 01:30:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9107d955-6a76-4008-bd6c-e150113e9a06</guid><dc:creator>r_malito</dc:creator><description>&lt;p&gt;I do not believe my GPIOTE_IRQHandler function is ever being called. My RTT log never contains the line from the handler:&lt;/p&gt;
&lt;p&gt;NRF_LOG_INFO(&amp;quot;in GPIOTE_IRQHandler...&amp;quot;);&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;When I was first building the project, the function definition for &lt;strong&gt;GPIOTE_IRQHandler()&lt;/strong&gt; was getting an error because it was claiming to be already defined in &lt;em&gt;nrfx_gpiote.c&lt;/em&gt;&amp;nbsp;(line 668) as&amp;nbsp;&lt;strong&gt;void nrfx_gpiote_irq_handler(void).&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I commented this function out as that is what I saw people saying to do in DevZone question answers.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not sure if that could be causing my handler to not be called every polarity toggle on the input pin.&lt;/p&gt;
&lt;p&gt;I have tried various input signal settings with a function generator. None seem to trigger the handler:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Frequencies Tested: 1 Hz to 1000 Hz&lt;/p&gt;
&lt;p&gt;Polarities tested: normal &amp;amp; inverted&lt;/p&gt;
&lt;p&gt;----------------------&lt;/p&gt;
&lt;p&gt;Specific Setting Combinations tried to trigger event:&lt;/p&gt;
&lt;p&gt;----------------------&lt;/p&gt;
&lt;p&gt;Amplitude (6.6v pk-pk)&lt;/p&gt;
&lt;p&gt;Load type: Hi-Z (High Impedance)&lt;/p&gt;
&lt;p&gt;----------------------&lt;/p&gt;
&lt;p&gt;Amplitude (3.3v pk-pk)&lt;/p&gt;
&lt;p&gt;Load type:&amp;nbsp;50 Ohm resistance&lt;/p&gt;
&lt;p&gt;---------------------&lt;/p&gt;
&lt;p&gt;Amplitude (3.3v pk-pk)&lt;/p&gt;
&lt;p&gt;Offset: 1.65v (in effort to get clear distinction between high and low)&lt;/p&gt;
&lt;p&gt;Load type:&amp;nbsp;50 Ohm resistance&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK improper GPIOTE --&gt; PPI configuration (no interrupts being raised on input toggle)</title><link>https://devzone.nordicsemi.com/thread/181951?ContentTypeID=1</link><pubDate>Sat, 13 Apr 2019 23:27:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2ec56972-2247-4782-9394-3ca7c723b939</guid><dc:creator>Dmitry</dc:creator><description>&lt;p&gt;You&amp;#39;re clearing EVENTS_IN[1] in interrupt handler, so you will always see 0 in main thread. In general your code is correct. Does your&amp;nbsp;GPIOTE_IRQHandler get called?&lt;/p&gt;
&lt;p&gt;What input signal do you have - push-pull or open-drain?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK improper GPIOTE --&gt; PPI configuration (no interrupts being raised on input toggle)</title><link>https://devzone.nordicsemi.com/thread/181924?ContentTypeID=1</link><pubDate>Sat, 13 Apr 2019 04:49:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a7cb9586-3c1f-4431-aa93-fc0a45522897</guid><dc:creator>r_malito</dc:creator><description>&lt;p&gt;&lt;span&gt;NRF_GPIOTE-&amp;gt;EVENTS_IN[1] is always 0&amp;nbsp; (pardon my typo) (I can answer any other intermediate questions that viewers of this post have as well in order to facilitate&amp;nbsp;a solution!)&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>