<?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>Inside GPIOTE interrupt handler the SPI transaction never ends</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/79793/inside-gpiote-interrupt-handler-the-spi-transaction-never-ends</link><description>Hi, 
 
 I am sensing interrupts on a pin using GPIOTE. I can see the interrupts coming on the oscilloscope. The firmware also detects the interrupts. However once I am inside the interrupt function, if I want to do a SPI transaction (in my case it is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 20 Sep 2021 07:42:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/79793/inside-gpiote-interrupt-handler-the-spi-transaction-never-ends" /><item><title>RE: Inside GPIOTE interrupt handler the SPI transaction never ends</title><link>https://devzone.nordicsemi.com/thread/330176?ContentTypeID=1</link><pubDate>Mon, 20 Sep 2021 07:42:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90c73484-ebd3-4440-af72-ccc0ba89ed1a</guid><dc:creator>alexislong73</dc:creator><description>&lt;p&gt;I see, thus I was overwriting it before to a priority above the SPI. Alright, thanks this solves my issue.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Kind regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inside GPIOTE interrupt handler the SPI transaction never ends</title><link>https://devzone.nordicsemi.com/thread/330168?ContentTypeID=1</link><pubDate>Mon, 20 Sep 2021 07:31:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f0d33c4-300e-4cab-9f84-a6c66a91dfcb</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Unless specified, the default configuration will read the interrupt priority from the sdk_config.h file.&lt;/p&gt;
&lt;p&gt;To override this, you need to change the input member .irq_priority provided to the nrf_&amp;lt;driver&amp;gt;_init() function.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Inside GPIOTE interrupt handler the SPI transaction never ends</title><link>https://devzone.nordicsemi.com/thread/330130?ContentTypeID=1</link><pubDate>Sat, 18 Sep 2021 17:08:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3ba555d-15e8-4be9-b3ee-c74c1e963e35</guid><dc:creator>alexislong73</dc:creator><description>&lt;p&gt;I found a solution. I have set .irq_priority in the SPI configuration to 1 instead of 6.&lt;/p&gt;
&lt;p&gt;But then what&amp;#39;s the difference between the peripheral priority in the sdk_config.h and the priority of theSPI1 configuration (.irq_priority)?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>