<?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>GPIOTE one input pin to few channels</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/45643/gpiote-one-input-pin-to-few-channels</link><description>Hello! 
 I want meashure pulse time via input capture. 
 I configured NRF_P0, NRF_GPIOTE, NRF_PPI and NRF_TIMER1. 
 
 
 It work fine, but in datasheet I found next text: 
 Only one GPIOTE channel can be assigned to one physical pin. Failing to do so may</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Apr 2019 19:32:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/45643/gpiote-one-input-pin-to-few-channels" /><item><title>RE: GPIOTE one input pin to few channels</title><link>https://devzone.nordicsemi.com/thread/181172?ContentTypeID=1</link><pubDate>Tue, 09 Apr 2019 19:32:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:73a0f3af-d687-4cfe-96af-972c4d2a5982</guid><dc:creator>Fred</dc:creator><description>&lt;p&gt;Were you able to work with the suggested answer below? If so, please accept it as such.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: GPIOTE one input pin to few channels</title><link>https://devzone.nordicsemi.com/thread/179667?ContentTypeID=1</link><pubDate>Tue, 02 Apr 2019 07:22:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d430e568-7f93-40f1-af5c-fb923e78bd4d</guid><dc:creator>Fred</dc:creator><description>&lt;p&gt;This is nice, just implemented something like this myself. So, let me tell you how I did this using PPI, a PORT event and COUNTER.&lt;/p&gt;
&lt;p&gt;First I configured the GPIO to trigger on both a rising and falling edge using:&lt;/p&gt;
&lt;p&gt;&lt;b&gt;nrf_drv_gpiote_in_config_t&lt;/b&gt;&lt;span style="font-weight:400;"&gt; config = GPIOTE_CONFIG_IN_SENSE_TOGGLE(&lt;/span&gt;&lt;span style="font-weight:400;"&gt;false&lt;/span&gt;&lt;span style="font-weight:400;"&gt;);&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-weight:400;"&gt;&lt;/span&gt;To be able to start and stop the counter, at least two PPI channels are to be created with the start-task and the stop-task of the&amp;nbsp;counter&amp;nbsp;respectively connected. However, only the start-channel needs to be enabled initially. When the event occurs, this start-channel needs to be disabled and the stop-channel enabled.&lt;/p&gt;
&lt;p&gt;However, the PPI does not have tasks to enable or disable channels directly. Instead PPI channel groups can be used to enable or disable a PPI channel. Adding the &amp;#39;start&amp;#39; channel to one channel group and the &amp;#39;stop&amp;#39; channel to the other now makes it possible to have a channel disable &amp;#39;itself&amp;#39; by attaching the fork of the channel to the disable task of the channel group.&lt;/p&gt;
&lt;p&gt;The tasks to enable a PPI channel group again I need two additional PPI channels, that are also added to the respective channel groups as illustrated in the final configuration below:&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/Screenshot-2019_2D00_04_2D00_02-at-09.12.54.png" /&gt;&lt;/p&gt;
&lt;p&gt;I hope this gives you inspiration ;-)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>