<?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>LPC MicrocontrollersのトピックRe: LPC2364 Reseting Randomly</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550765#M14072</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ABR15 on Wed Jul 15 04:02:06 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for answer dunno!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, I'm using about 7 types of interrupts. My interrupts remains enabled after the start up. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I could find the problem! I'm working with LIN communication and there is a break method where you change the baud rate to simulate a end of message. When I write U2DLL register, to change the baud rate, immediately occurs RX interrupt in the uart2 (LIN) and remains here forever. In the end of this interruption I clean the VICADDRESS for acknowledge, but the next step is the same interruption again, so the watchdog resets.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The solution was disable the RX interrupt when I change the baud rate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But, why does the firmware remain at this interrupt for ever, even clear the VICADDRESS ? I found an application note AN10414 about supirous interrupt and report about RDA UART interrupt, but is for UART0/1.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 19:52:03 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T19:52:03Z</dc:date>
    <item>
      <title>LPC2364 Reseting Randomly</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550763#M14070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ABR15 on Wed Jul 01 10:48:01 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi all. I have a case where the LPC2364 is reseting, but there isn't a visual reason for this, like an input event or communication event, and the time between the resets is about 3 or 4 days... so it's complicated to see this failure.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I've found in the user manual the RSIR register, that shows 4 reasons for the microcontroller reset (Powerup, WatchDog, Brownout and ExternalReset) and I've implemented a flash write for this register for me to see the reason and works fine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there another way for to investigate the reason? I've tried to get the PC value for write in the flash too but I couldn't..&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:52:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550763#M14070</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: LPC2364 Reseting Randomly</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550764#M14071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by dunno.. on Wed Jul 15 02:16:56 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;are you using interrupts? &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;do you disable interrupts on the run, or even change isr handlers in the vic on the fly?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-&amp;gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;i had the same problem as you, it looked like a restart, but in fact, it was only a spurious interrupt with jump to the default handler, which is simply starting to execute at line0..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;read the datasheet, search for spurious interrupts, make sure VICDefVectAddr is provided with an actual handler that acks the int and returns..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;also make sure to guard your changes to the vic on the fly by disabling global interrupts, these accesses are not interruptsave, either.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;to track this one down, do some debug prints or breakpoint in the VICDefVectAddr handler. &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:52:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550764#M14071</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:52:02Z</dc:date>
    </item>
    <item>
      <title>Re: LPC2364 Reseting Randomly</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550765#M14072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ABR15 on Wed Jul 15 04:02:06 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for answer dunno!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Yes, I'm using about 7 types of interrupts. My interrupts remains enabled after the start up. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I could find the problem! I'm working with LIN communication and there is a break method where you change the baud rate to simulate a end of message. When I write U2DLL register, to change the baud rate, immediately occurs RX interrupt in the uart2 (LIN) and remains here forever. In the end of this interruption I clean the VICADDRESS for acknowledge, but the next step is the same interruption again, so the watchdog resets.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The solution was disable the RX interrupt when I change the baud rate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But, why does the firmware remain at this interrupt for ever, even clear the VICADDRESS ? I found an application note AN10414 about supirous interrupt and report about RDA UART interrupt, but is for UART0/1.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:52:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550765#M14072</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: LPC2364 Reseting Randomly</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550766#M14073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by dunno.. on Wed Jul 15 04:54:02 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: ABR15&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;But, why does the firmware remain at this interrupt for ever, even clear the VICADDRESS ? I found an application note AN10414 about supirous interrupt and report about RDA UART interrupt, but is for UART0/1.&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sounds like you dont clear the source of the interrupt, so it gets fired right again after you ack it in the vic.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;some ints have to be cleared accessing some register in the peripheral.. i dont know your controller, though, so check the datasheet about how to reset interrupts in the uart... &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:52:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550766#M14073</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: LPC2364 Reseting Randomly</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550767#M14074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ABR15 on Thu Jul 16 03:54:49 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: dunno..&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sounds like you dont clear the source of the interrupt, so it gets fired right again after you ack it in the vic.&lt;BR /&gt;&lt;BR /&gt;some ints have to be cleared accessing some register in the peripheral.. i dont know your controller, though, so check the datasheet about how to reset interrupts in the uart...&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you for answer. You are right, but I already read the register that clear the interrupt. The fact is that this problem occurs rarely, so I think that there isn't a firmware problem.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:52:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC2364-Reseting-Randomly/m-p/550767#M14074</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:52:04Z</dc:date>
    </item>
  </channel>
</rss>

