<?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 (Reset) on M5223X / M5213 in ColdFire/68K Microcontrollers and Processors</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134899#M1523</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;Unfortunatly, you can only do a soft Reset (MCF_CIM_RCR_SOFTRST), and I if you program is blocked in a critical section, the cpu core will never be reinitialized and the program is definitely deadlocked, so you have to avoid loops in critical regions.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Emmanuel,&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 31 Oct 2006 16:09:26 GMT</pubDate>
    <dc:creator>Nouchi</dc:creator>
    <dc:date>2006-10-31T16:09:26Z</dc:date>
    <item>
      <title>Watchdog (Reset) on M5223X / M5213</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134898#M1522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I would like to know a little more about the software watchdog in the above processors - this is taking on from the previous (but now quite old) posting &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://forums.freescale.com/freescale/board/message?board.id=CFCOMM&amp;amp;message.id=776&amp;amp;query.id=13063#M776" target="_blank"&gt;http://forums.freescale.com/freescale/board/message?board.id=CFCOMM&amp;amp;message.id=776&amp;amp;query.id=13063#M776&lt;/A&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The present understanding is that it is not possible to program the core software watchdog in these devices to cause a reset in order to recover from a problem (software runaway). It is necessary to activate the corresponding interrupt routine and to command a soft reset from it.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have just programmed this and also set the priority of this interrupt as the highest in the system.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There remains one question. What happens when a problem exists in a section of code which disables all interrupts? Wouldn't it mean that the core sw watchdog timer will timeout but its interrupt never handled? Is this not quite a risk??&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mark Butcher&lt;BR /&gt;&lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.mjbc.ch%2F" rel="nofollow" target="_blank"&gt;www.mjbc.ch&lt;/A&gt; / &lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.uTasker.com%2F" rel="nofollow" target="_blank"&gt;www.uTasker.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Oct 2006 08:09:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134898#M1522</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2006-10-31T08:09:41Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog (Reset) on M5223X / M5213</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134899#M1523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;Unfortunatly, you can only do a soft Reset (MCF_CIM_RCR_SOFTRST), and I if you program is blocked in a critical section, the cpu core will never be reinitialized and the program is definitely deadlocked, so you have to avoid loops in critical regions.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Emmanuel,&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Oct 2006 16:09:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134899#M1523</guid>
      <dc:creator>Nouchi</dc:creator>
      <dc:date>2006-10-31T16:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog (Reset) on M5223X / M5213</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134900#M1524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;If you have the option, an external watchdog, or watchdog/voltage regulator IC can be a great solution to this problem. Depending on your requirements for the power supply, this can be close to cost neutral.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Dec 2006 06:10:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134900#M1524</guid>
      <dc:creator>jvantol</dc:creator>
      <dc:date>2006-12-07T06:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog (Reset) on M5223X / M5213</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134901#M1525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Why not use level 7 for the watchdog interrupt? It should be non-maskable.&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 15:47:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134901#M1525</guid>
      <dc:creator>Petter_fupp</dc:creator>
      <dc:date>2007-06-29T15:47:11Z</dc:date>
    </item>
    <item>
      <title>Re: Watchdog (Reset) on M5223X / M5213</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134902#M1526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi Petter&lt;BR /&gt;&lt;BR /&gt;You are correct, the Interrupt level 7 assigned to an interrupt gives it NMI qualities and so this is a solution which has been adopted in the meantime.&lt;BR /&gt;&lt;BR /&gt;There is still a small risk involved since if the interrupt vector is in SRAM and this gets corrupted by a runaway program the NMI interrupt will fire but fail itself - so there is still no 100% secure method of recovering from a fatal program error through a reset. i.e. if the runaway program writes something to the watchdog interrupt vector it will result in the board hanging forever with no automatic reset recovery (apart from when an external supervisor is utilised...)&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Mark&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.uTasker.com" rel="nofollow" target="_blank"&gt;www.uTasker.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 16:24:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Watchdog-Reset-on-M5223X-M5213/m-p/134902#M1526</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2007-06-29T16:24:53Z</dc:date>
    </item>
  </channel>
</rss>

