<?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 MCF5475 - How do I know if the CPU is halted? in ColdFire/68K Microcontrollers and Processors</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5475-How-do-I-know-if-the-CPU-is-halted/m-p/161763#M5196</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I'm working with an MCF5475 running Linux v2.6.10 from the Freescale BSP.&amp;nbsp; I recently ran across information in the Coldfire Family Programmer's Reference Manual, Rev 3&amp;nbsp;in section 11.1.3 that states:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;"Note that if a Coldfire processor encounters any fault while processing another fault, it immediately halts execution with a catastrophic fault-on-fault condition.&amp;nbsp; A reset is required to force the processor to exit this halted state."&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I'm suspicious that we maybe encountering this catastrophic fault-on-fault condition but I am having trouble proving this.&amp;nbsp; I suspect this because&amp;nbsp;on a very intermmitent basis, while I have my BDI2000 debugging tool plugged into the BDM port and when the system locks up, I halt the CPU using the debugger to investigate the registers and find that the registers have invalid values and that the BDI2000 loses communication with the CPU.&amp;nbsp; Under normal circumstances, I halt and resume the CPU without issue using the BDI2000.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Is there a way to determine that the CPU experienced a catastrophic fault-on-fault condition by sticking a probe on one of the CPU pins or something along that line?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;Tony.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Nov 2007 08:12:56 GMT</pubDate>
    <dc:creator>TonyM</dc:creator>
    <dc:date>2007-11-08T08:12:56Z</dc:date>
    <item>
      <title>MCF5475 - How do I know if the CPU is halted?</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5475-How-do-I-know-if-the-CPU-is-halted/m-p/161763#M5196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I'm working with an MCF5475 running Linux v2.6.10 from the Freescale BSP.&amp;nbsp; I recently ran across information in the Coldfire Family Programmer's Reference Manual, Rev 3&amp;nbsp;in section 11.1.3 that states:&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;"Note that if a Coldfire processor encounters any fault while processing another fault, it immediately halts execution with a catastrophic fault-on-fault condition.&amp;nbsp; A reset is required to force the processor to exit this halted state."&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I'm suspicious that we maybe encountering this catastrophic fault-on-fault condition but I am having trouble proving this.&amp;nbsp; I suspect this because&amp;nbsp;on a very intermmitent basis, while I have my BDI2000 debugging tool plugged into the BDM port and when the system locks up, I halt the CPU using the debugger to investigate the registers and find that the registers have invalid values and that the BDI2000 loses communication with the CPU.&amp;nbsp; Under normal circumstances, I halt and resume the CPU without issue using the BDI2000.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Is there a way to determine that the CPU experienced a catastrophic fault-on-fault condition by sticking a probe on one of the CPU pins or something along that line?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;Tony.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2007 08:12:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5475-How-do-I-know-if-the-CPU-is-halted/m-p/161763#M5196</guid>
      <dc:creator>TonyM</dc:creator>
      <dc:date>2007-11-08T08:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: MCF5475 - How do I know if the CPU is halted?</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5475-How-do-I-know-if-the-CPU-is-halted/m-p/161764#M5197</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;From what I understand the Coldfire core will output 0x0F on the four PST lines to debug interface continusly&amp;nbsp;when this condition occurs.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Nov 2007 09:12:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5475-How-do-I-know-if-the-CPU-is-halted/m-p/161764#M5197</guid>
      <dc:creator>Technoman64</dc:creator>
      <dc:date>2007-11-13T09:12:20Z</dc:date>
    </item>
  </channel>
</rss>

