<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: LPC1768 GPIO Interrupt Triggers when enabled in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521805#M4441</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by briching on Thu Oct 15 22:48:44 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Clearing any interrupt before enabling them for the first time is analogous to initializing it, and properly I might add.&amp;nbsp; If you don't initialize (just about everything) properly, you should expect undefined or undocumented behavior.&amp;nbsp; In your case with double edge interrupts, perhaps it is the fact that the chip defaults all of its pins to inputs with pull-up resistors on powerup, and that is generating a pending interrupt before you have made a call to enable the interrupt which immediately ends up firing the ISR?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 17:51:00 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T17:51:00Z</dc:date>
    <item>
      <title>LPC1768 GPIO Interrupt Triggers when enabled</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521802#M4438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by dev2. on Tue Oct 13 01:13:34 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a requirement where I need to turn on/off GPIO interrupts during certain events in my application. Requirement is to monitor both Falling/Rising edges when this interrupt is enabled. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Each time GPIO interrupt is enabled in IO0IntEnR/IO0InENF register, I get one Rising/Falling edge interrupt trigger even though there is no transition in the input. This happens only the first time, after which interrupt works as expected.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any pointers on what could be the reason for this behavior? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sam&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:50:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521802#M4438</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:50:58Z</dc:date>
    </item>
    <item>
      <title>Re: LPC1768 GPIO Interrupt Triggers when enabled</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521803#M4439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by R2D2 on Tue Oct 13 01:25:54 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: dev2.&lt;/STRONG&gt;&lt;BR /&gt;Any pointers on what could be the reason for this behavior?&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You don't clear the interrupts before you enable them... &lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:50:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521803#M4439</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:50:59Z</dc:date>
    </item>
    <item>
      <title>Re: LPC1768 GPIO Interrupt Triggers when enabled</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521804#M4440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by dev2. on Tue Oct 13 01:34:41 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks. It worked.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any logic why it has to be cleared before enabling it? &lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:51:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521804#M4440</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:51:00Z</dc:date>
    </item>
    <item>
      <title>Re: LPC1768 GPIO Interrupt Triggers when enabled</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521805#M4441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by briching on Thu Oct 15 22:48:44 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Clearing any interrupt before enabling them for the first time is analogous to initializing it, and properly I might add.&amp;nbsp; If you don't initialize (just about everything) properly, you should expect undefined or undocumented behavior.&amp;nbsp; In your case with double edge interrupts, perhaps it is the fact that the chip defaults all of its pins to inputs with pull-up resistors on powerup, and that is generating a pending interrupt before you have made a call to enable the interrupt which immediately ends up firing the ISR?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:51:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-GPIO-Interrupt-Triggers-when-enabled/m-p/521805#M4441</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:51:00Z</dc:date>
    </item>
  </channel>
</rss>

