<?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>NRF7002DK basic button example interrupts seem to fire at the opposite edge/level.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/100829/nrf7002dk-basic-button-example-interrupts-seem-to-fire-at-the-opposite-edge-level</link><description>github.com/.../main.c 
 This example was used to test the button interrupt. 
 For the example, the interrupt seems to be setup to fire when the button goes to logic high i.e. when the button is RELEASED, based on the schematic. 
 
 I assumed this meant</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 15 Jun 2023 13:46:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/100829/nrf7002dk-basic-button-example-interrupts-seem-to-fire-at-the-opposite-edge-level" /><item><title>RE: NRF7002DK basic button example interrupts seem to fire at the opposite edge/level.</title><link>https://devzone.nordicsemi.com/thread/431294?ContentTypeID=1</link><pubDate>Thu, 15 Jun 2023 13:46:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:038e56bd-0d4c-4502-b36c-f024ef053842</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;You welcome, glad I could help &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF7002DK basic button example interrupts seem to fire at the opposite edge/level.</title><link>https://devzone.nordicsemi.com/thread/431253?ContentTypeID=1</link><pubDate>Thu, 15 Jun 2023 12:34:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b9f3eed7-677d-4792-9e4a-2b9d871879d2</guid><dc:creator>leo_nam</dc:creator><description>&lt;p&gt;Ah I see, knew I was missing something,&amp;nbsp;&lt;br /&gt;Thank You&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF7002DK basic button example interrupts seem to fire at the opposite edge/level.</title><link>https://devzone.nordicsemi.com/thread/431239?ContentTypeID=1</link><pubDate>Thu, 15 Jun 2023 12:07:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c8c28e7-56dd-472f-8385-c7cc960d9bcf</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;The button pins are defined as active low in the board file, which means that active is defined as logical 0.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You can change this in the board file or in your overlay file by modifying the GPIO_ACTIVE_LOW field to GPIO_ACTIVE_HIGH, in case you want to design your own hardware:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;buttons {
	compatible = &amp;quot;gpio-keys&amp;quot;;
	button0: button_0 {
		gpios = &amp;lt;&amp;amp;gpio0 23 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)&amp;gt;;
		label = &amp;quot;Push button 1&amp;quot;;
	};
	button1: button_1 {
		gpios = &amp;lt;&amp;amp;gpio0 24 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)&amp;gt;;
		label = &amp;quot;Push button 2&amp;quot;;
	};
	button2: button_2 {
		gpios = &amp;lt;&amp;amp;gpio0 8 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)&amp;gt;;
		label = &amp;quot;Push button 3&amp;quot;;
	};
	button3: button_3 {
		gpios = &amp;lt;&amp;amp;gpio0 9 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)&amp;gt;;
		label = &amp;quot;Push button 4&amp;quot;;
	};
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>