<?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>CodeWarrior for MCUのトピックRe: Erroneous break in Codewarrior 6.1 Running 68HCS12A512</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Erroneous-break-in-Codewarrior-6-1-Running-68HCS12A512/m-p/184743#M6395</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I seem to have solved this problem myself!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;It seems I have a dodgy BDM Pod. My other pod can be left connected overnight, and it does not break!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Feb 2008 16:56:42 GMT</pubDate>
    <dc:creator>EmbeddedCoder</dc:creator>
    <dc:date>2008-02-13T16:56:42Z</dc:date>
    <item>
      <title>Erroneous break in Codewarrior 6.1 Running 68HCS12A512</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Erroneous-break-in-Codewarrior-6-1-Running-68HCS12A512/m-p/184742#M6394</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi All,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I wonder if anyone else has seen the problems I have suddenly started to encounter and has any solutions?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I have been running Metrowerks debugger with a P&amp;amp;E BDM pod (Parallel not USB) on the HCS12A512 for over a year now and this is the first time I have seen this, which is suspicious in itself!!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I start my project, which does some initial checks and enters normal run mode - it seems to run like this for around 1 - 5minutes. During this time I can check internal memory, breakpoint etc as you would expect and all looks normal...&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;But then, I encounter an illegal breakpoint at the Clock Monitor Fail Vector, All the registers - PC, IP, D, A, B, IX, IY are populated with FFFF - which I think is consistent with the chip coming out of reset - although wierdly, having checked all the docs, I have disabled the clock monitor fail interrupt!?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;But, I have written debug software so I can interrogate the chip status through the SCI - and with the debugger showing the chip halted, I can still send and receive debug messages. Further - these messages indicate that the chip has not been reset, as internal message counters have not been cleared!!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;So, it seems that the metrowerks debugger has gotten confused somehow, indicating the chip has crashed when it has not&amp;nbsp;- I have read other posts that indicate running the debugger with PLL enabled can cause problems, and my project does use the PLL module, ramping the source 25Mhz crsytal&amp;nbsp;up to 50Mhz. However, I have run my project for at least 6 months with these PLL settings without apparent problems.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Has anyone else seen wierd effects like these, or have any workarounds?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks in advance,&lt;/DIV&gt;&lt;DIV&gt;Mike&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2008 18:08:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Erroneous-break-in-Codewarrior-6-1-Running-68HCS12A512/m-p/184742#M6394</guid>
      <dc:creator>EmbeddedCoder</dc:creator>
      <dc:date>2008-02-01T18:08:53Z</dc:date>
    </item>
    <item>
      <title>Re: Erroneous break in Codewarrior 6.1 Running 68HCS12A512</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Erroneous-break-in-Codewarrior-6-1-Running-68HCS12A512/m-p/184743#M6395</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I seem to have solved this problem myself!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;It seems I have a dodgy BDM Pod. My other pod can be left connected overnight, and it does not break!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2008 16:56:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Erroneous-break-in-Codewarrior-6-1-Running-68HCS12A512/m-p/184743#M6395</guid>
      <dc:creator>EmbeddedCoder</dc:creator>
      <dc:date>2008-02-13T16:56:42Z</dc:date>
    </item>
  </channel>
</rss>

