<?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: Watchdog Timer Reset unexpected behaviour in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591596#M22248</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by starblue on Mon Nov 03 05:26:48 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: hangdog&lt;/STRONG&gt;&lt;BR /&gt;So, what startup code are you referring to&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No, just a generic assumption that the startup code in your software might do something different (e.g. count the number of watchdog resets to prevent a loop).&lt;/SPAN&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: hangdog&lt;/STRONG&gt;&lt;BR /&gt;the device ROM? Have you any notion that the behaviour of the ROM might be different following a WWDT reset?&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It seems they removed an erroneous mention in the boot flowchart that was in some earlier version of the UM, maybe I had that in the back of my mind.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I guess you have to work on developing your own super powers ...&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 19:20:27 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T19:20:27Z</dc:date>
    <item>
      <title>Watchdog Timer Reset unexpected behaviour</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591592#M22244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by hangdog on Wed Oct 01 05:11:53 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm trying to use the watchdog timer to reset an LPC4350 - the device stops running, but seems never to start again. When I hard reset using the reset button on the dev board (DIOLAN), it comes back as expected. What I don't get is... isn't using the WDT equivalent to pressing the reset button? Or did I miss something?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The only other information that might be pertinent is that various interrupts are enabled, so other code can potentially run whilst the WDT is counting down, but this is the only place in the code base that I touch the WDT, so I can't see why anything would get in its way.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers for any insight, my WDT reset code follows:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD bgcolor="#cacaca"&gt; &lt;PRE&gt;
WWDT_TC = 0xFFFF;
WWDT_MOD = BIT0 | BIT1;
WWDT_FEED = 0xAA;
WWDT_FEED = 0x55;
while (1)
{
}
&lt;/PRE&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:20:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591592#M22244</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:20:24Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog Timer Reset unexpected behaviour</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591593#M22245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by hangdog on Thu Oct 30 13:05:28 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Bump - on the off chance a super hero is passing by...&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:20:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591593#M22245</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:20:25Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog Timer Reset unexpected behaviour</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591594#M22246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by starblue on Fri Oct 31 04:15:01 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: hangdog&lt;/STRONG&gt;&lt;BR /&gt;isn't using the WDT equivalent to pressing the reset button?&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;SPAN&gt;That's not so easy, the startup code might check whether a watchdog reset occurred.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:20:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591594#M22246</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:20:26Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog Timer Reset unexpected behaviour</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591595#M22247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by hangdog on Fri Oct 31 06:37:09 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi starblue&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for your comment.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As someone previously suggested to me, I have read Ch14 of the user manual, and as far as I can see the relevant entry is Table 165, which describes a CORE_RST as being generated by either the external reset pin or by a WWDT timeout reset. That is, they're the same, aren't they? Fig 36 seems to indicate the same thing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I didn't state in my original post was that the reset does work most of the time, it just fails to come back occasionally. I can't see any pattern to when it does this.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So, what startup code are you referring to, the device ROM? Have you any notion that the behaviour of the ROM might be different following a WWDT reset?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:20:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591595#M22247</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:20:26Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog Timer Reset unexpected behaviour</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591596#M22248</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by starblue on Mon Nov 03 05:26:48 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: hangdog&lt;/STRONG&gt;&lt;BR /&gt;So, what startup code are you referring to&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No, just a generic assumption that the startup code in your software might do something different (e.g. count the number of watchdog resets to prevent a loop).&lt;/SPAN&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: hangdog&lt;/STRONG&gt;&lt;BR /&gt;the device ROM? Have you any notion that the behaviour of the ROM might be different following a WWDT reset?&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It seems they removed an erroneous mention in the boot flowchart that was in some earlier version of the UM, maybe I had that in the back of my mind.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I guess you have to work on developing your own super powers ...&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:20:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Watchdog-Timer-Reset-unexpected-behaviour/m-p/591596#M22248</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:20:27Z</dc:date>
    </item>
  </channel>
</rss>

