<?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 gpiote interrupt faults out</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12099/nrf52-gpiote-interrupt-faults-out</link><description>currently, i connected the nrf52(spi master) with ads1292 (spi slave) which is a ECG sensor. For the ads1292 chips, there is a output pin generating the signal called DRDY to indicate the spi data is ready. just like the following picture shown, when</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Feb 2016 10:35:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12099/nrf52-gpiote-interrupt-faults-out" /><item><title>RE: nrf52 gpiote interrupt faults out</title><link>https://devzone.nordicsemi.com/thread/45788?ContentTypeID=1</link><pubDate>Wed, 24 Feb 2016 10:35:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aab84e94-0034-428c-a6f3-7af11e9b6031</guid><dc:creator>oliverhu</dc:creator><description>&lt;p&gt;thank you very much, I delete the existing GPIOTE handler and it works. really learn from it, thank you again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52 gpiote interrupt faults out</title><link>https://devzone.nordicsemi.com/thread/45787?ContentTypeID=1</link><pubDate>Wed, 24 Feb 2016 10:30:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f82ed38a-ea26-4ca1-ab4f-e1ba91b207ca</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Well you can&amp;#39;t just change the name of the GPIOTE handler to something incorrect and then expect it to work can you? The GPIOTE IRQ has a specific name requirement. So your problem is you already have a GPIOTE handler, probably because you&amp;#39;re using the button module or something which uses the GPIOTE module. So if you want to use GPIOTE for your interrupt then you have to either not use the button module, or &amp;#39;pretend&amp;#39; the interrupt line you&amp;#39;re using is a button and use a button-style callback for it or find a function in the GPIOTE module which allows you to work alongside it and add your own interrupts. Just ignoring the compilation error by changing the name really wasn&amp;#39;t going to work.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52 gpiote interrupt faults out</title><link>https://devzone.nordicsemi.com/thread/45786?ContentTypeID=1</link><pubDate>Wed, 24 Feb 2016 10:25:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2261b84-2df1-4b44-a794-37556ac4b438</guid><dc:creator>oliverhu</dc:creator><description>&lt;p&gt;Hi RK, thanks for your reply.  sorry ,maybe what i described is a little bit confusing. actually the data is ready when the signal is low, the data is to be sent when the signal is high).&lt;br /&gt;
and if i use void GPIOTE_IRQHandler(void), the error will occur (._build\nrf52832_xxaa.axf: Error: L6200E: Symbol GPIOTE_IRQHandler multiply defined (by nrf_drv_gpiote.o and main.o).).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52 gpiote interrupt faults out</title><link>https://devzone.nordicsemi.com/thread/45789?ContentTypeID=1</link><pubDate>Wed, 24 Feb 2016 09:48:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f80a292-a025-453c-8274-1fa0dc6ee523</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;&lt;code&gt;void GPIOTE_IRQHandler1(void)&lt;/code&gt; is not the right name for the IRQ Handler. And you have the configuration possibly backwards, you have HiToLo instead of LoToHi (you say the data is ready when the signal is high).&lt;/p&gt;
&lt;p&gt;So most likely you&amp;#39;ve enabled the interrupt, it&amp;#39;s fired instantly, you&amp;#39;ve gone to the GPIOTE_IRQHandler which you haven&amp;#39;t defined and hence is probably therefore the default tight do-nothing loop and there it will stay forever.&lt;/p&gt;
&lt;p&gt;When code &amp;#39;sticks&amp;#39;, try pressing the break button the debugger and find out where you are.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>