<?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>what&amp;#39;s timing requirement of GPIOE detect rising/fall edge?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7048/what-s-timing-requirement-of-gpioe-detect-rising-fall-edge</link><description>we now using GPIO as input. when it rise then start timer. but it seem failed. No GPIOE IN event happened. 
 what&amp;#39;s timing need for rising/fall edge detecting? &amp;lt; XX (us)? How sharp it need be?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 19 May 2015 00:52:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7048/what-s-timing-requirement-of-gpioe-detect-rising-fall-edge" /><item><title>RE: what's timing requirement of GPIOE detect rising/fall edge?</title><link>https://devzone.nordicsemi.com/thread/24904?ContentTypeID=1</link><pubDate>Tue, 19 May 2015 00:52:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d58f80d0-b771-4d9b-91a5-b85558cc6a75</guid><dc:creator>wen jin zhang</dc:creator><description>&lt;p&gt;sorry! I did not remember how much changes in NRF_GPIO-&amp;gt;PIN_CNF[]. but this config working for our board. detect the RISE Event.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;NRF_GPIO-&amp;gt;PIN_CNF[zx] = (GPIO_PIN_CNF_SENSE_Disabled &amp;lt;&amp;lt; GPIO_PIN_CNF_SENSE_Pos)
                        | (GPIO_PIN_CNF_DRIVE_S0S1 &amp;lt;&amp;lt; GPIO_PIN_CNF_DRIVE_Pos)
                        | (GPIO_PIN_CNF_PULL_Disabled &amp;lt;&amp;lt; GPIO_PIN_CNF_PULL_Pos)
                        | (GPIO_PIN_CNF_INPUT_Disconnect &amp;lt;&amp;lt; GPIO_PIN_CNF_INPUT_Pos)
                        | (GPIO_PIN_CNF_DIR_Input &amp;lt;&amp;lt; GPIO_PIN_CNF_DIR_Pos);

NRF_GPIOTE-&amp;gt;CONFIG[2] = (GPIOTE_CONFIG_MODE_Event &amp;lt;&amp;lt; GPIOTE_CONFIG_MODE_Pos)
                        | ((uint32_t)zx    &amp;lt;&amp;lt; GPIOTE_CONFIG_PSEL_Pos)
                        | ((uint32_t)GPIOTE_CONFIG_POLARITY_LoToHi &amp;lt;&amp;lt; GPIOTE_CONFIG_POLARITY_Pos)
                        | ((uint32_t)GPIOTE_CONFIG_OUTINIT_Low &amp;lt;&amp;lt; GPIOTE_CONFIG_OUTINIT_Pos);
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;appreciate  your help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: what's timing requirement of GPIOE detect rising/fall edge?</title><link>https://devzone.nordicsemi.com/thread/24899?ContentTypeID=1</link><pubDate>Mon, 18 May 2015 09:55:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ed20cb7-459e-4ad0-8d38-e1b9890c4d79</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;does the Sense enable cause problem with the pin when you connected it with GPIOTE?
This setting must have been ignored, why didn&amp;#39;t it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: what's timing requirement of GPIOE detect rising/fall edge?</title><link>https://devzone.nordicsemi.com/thread/24900?ContentTypeID=1</link><pubDate>Mon, 18 May 2015 09:05:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74a6aa74-df6d-4403-a004-32e38a42e9e5</guid><dc:creator>wen jin zhang</dc:creator><description>&lt;p&gt;Thank for your  help!  solved the problem by set the GPIO_PIN_CNF_SENSE_Disabled in
NRF_GPIO-&amp;gt;PIN_CNF[].&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: what's timing requirement of GPIOE detect rising/fall edge?</title><link>https://devzone.nordicsemi.com/thread/24902?ContentTypeID=1</link><pubDate>Mon, 18 May 2015 07:08:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bc2a7d5e-b8dc-424e-822d-0a30960273cb</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Yes, that is true, my apologies, only input connect settings from GPIO settings will still be in effect and others ignored. Ignore my comment about the Sense mechanism from GPIO pin setting but my comment on sampling is still valid that it should happen fast enough. What is the rising and falling time for your signal?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: what's timing requirement of GPIOE detect rising/fall edge?</title><link>https://devzone.nordicsemi.com/thread/24903?ContentTypeID=1</link><pubDate>Sun, 17 May 2015 23:57:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d79723e6-69e9-4f14-8deb-6aadf0f30306</guid><dc:creator>wen jin zhang</dc:creator><description>&lt;p&gt;Thanks! But why the NRF_GPIOTE-&amp;gt;CONFIG[] did not take over the NRF_GPIO-&amp;gt;PIN_CNF[] configuration? the document said:
When an OUT[n] task or an IN[n] event has been configured to operate on a pin, the pin can only be written
from the GPIOTE module. Attempting to write a pin as a normal GPIO pin will have no effect.
As long as an OUT[n] task or an IN[n] event is configured to control a pin n, the pin&amp;#39;s output value will only
be updated by the GPIOTE module. The pin&amp;#39;s output value as specified in the GPIO will therefore be ignored
as long as the pin is controlled by GPIOTE.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: what's timing requirement of GPIOE detect rising/fall edge?</title><link>https://devzone.nordicsemi.com/thread/24901?ContentTypeID=1</link><pubDate>Fri, 15 May 2015 09:38:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41286a04-309c-4719-93fa-48cfe07f5260</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;There is nothing in the GPIO to generate events.
When you have enabled the &amp;quot;Sense&amp;quot; mechanism on your input pin through the GPIO configuration, It will generate a detect signal which in turn will generate a PORT event inside GPIOTE.&lt;/p&gt;
&lt;p&gt;This detection sampling should happen atleast at the speed of internal clock, so 0.06us. I am pretty confident that the chip won&amp;#39;t miss it if it happens.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>