<?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 signal when debugger crashes in Classic/Legacy CodeWarrior</title>
    <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/signal-when-debugger-crashes/m-p/135787#M867</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier; font-size: 2;"&gt;The debugger seems to crash randomly.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier; font-size: 2;"&gt;If it crashes while I have a motor in boost it burns out the board.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier; font-size: 2;"&gt;Is there a signal from the processor&amp;nbsp;that will let me know&amp;nbsp;when the debugger&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier; font-size: 2;"&gt;crashes? I am using codewarrior 7.3 on the 56f8357.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Nov 2006 01:45:05 GMT</pubDate>
    <dc:creator>mel</dc:creator>
    <dc:date>2006-11-09T01:45:05Z</dc:date>
    <item>
      <title>signal when debugger crashes</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/signal-when-debugger-crashes/m-p/135787#M867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier; font-size: 2;"&gt;The debugger seems to crash randomly.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier; font-size: 2;"&gt;If it crashes while I have a motor in boost it burns out the board.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier; font-size: 2;"&gt;Is there a signal from the processor&amp;nbsp;that will let me know&amp;nbsp;when the debugger&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier; font-size: 2;"&gt;crashes? I am using codewarrior 7.3 on the 56f8357.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Nov 2006 01:45:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/signal-when-debugger-crashes/m-p/135787#M867</guid>
      <dc:creator>mel</dc:creator>
      <dc:date>2006-11-09T01:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: signal when debugger crashes</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/signal-when-debugger-crashes/m-p/135788#M868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Let me expand on this.&lt;/DIV&gt;&lt;DIV&gt;There are some high power processes under control of the processor. When emulation stops, we need a graceful way to shut down the power processes so that the board does not burn up.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Is there some hardware method to flag when emulation stops on a breakpoint or emulation failure?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;codewarrior 7.3 on the 56f8357.&amp;nbsp;&amp;nbsp; Emulating through the parallel port using OCDemon 'wiggler' jtag converter.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;TIA&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Nov 2006 00:00:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/signal-when-debugger-crashes/m-p/135788#M868</guid>
      <dc:creator>Oppie</dc:creator>
      <dc:date>2006-11-10T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

