<?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 Illegal Opcode IRQ in CodeWarrior for MCU</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Illegal-Opcode-IRQ/m-p/196858#M7308</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I wonder if anyone can help me. I am using the MC9S12XDT512 processor and something is causing the unimplemented opcode IRQ to execute.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;How can I go about finding what part of my code caused this to happen?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Stuart&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Oct 2008 22:29:59 GMT</pubDate>
    <dc:creator>Yellowfish</dc:creator>
    <dc:date>2008-10-23T22:29:59Z</dc:date>
    <item>
      <title>Illegal Opcode IRQ</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Illegal-Opcode-IRQ/m-p/196858#M7308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I wonder if anyone can help me. I am using the MC9S12XDT512 processor and something is causing the unimplemented opcode IRQ to execute.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;How can I go about finding what part of my code caused this to happen?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Stuart&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Oct 2008 22:29:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Illegal-Opcode-IRQ/m-p/196858#M7308</guid>
      <dc:creator>Yellowfish</dc:creator>
      <dc:date>2008-10-23T22:29:59Z</dc:date>
    </item>
    <item>
      <title>Re: Illegal Opcode IRQ</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Illegal-Opcode-IRQ/m-p/196859#M7309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;In your trap handler you could inspect the stack.&amp;nbsp;Illegal instruction trap&amp;nbsp;ISR return address (and I think the address of illegal instruction +2, must check)&amp;nbsp; should be stored at SP+8.&lt;/DIV&gt;&lt;DIV&gt;I think you should try using onchip trace buffer. I'm not familiar with it. But I would try to enable trace buffer, put breakpoint in trap ISR, and when breakpoint is hit&amp;nbsp;trying to trace it.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Oct 2008 14:32:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Illegal-Opcode-IRQ/m-p/196859#M7309</guid>
      <dc:creator>kef</dc:creator>
      <dc:date>2008-10-24T14:32:59Z</dc:date>
    </item>
    <item>
      <title>Re: Illegal Opcode IRQ</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Illegal-Opcode-IRQ/m-p/196860#M7310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Most common cause is indeed stack overflow.&lt;BR /&gt;&lt;BR /&gt;The quick &amp;amp; dirty way to find stack errors is to download the code through the debugger, then in the memory map, set every byte in the whole stack area to a certain value, like 0xAA.&lt;BR /&gt;&lt;BR /&gt;After that, start the program and let it run. When it catches the breakpoint for illegal instruction, pick up the memory map and check the stack. You should be able to see how much of the 0xAA on the stack that the program has munched away at. If it is all the way to the top, or close, then the cause is stack overflow.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Oct 2008 18:07:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Illegal-Opcode-IRQ/m-p/196860#M7310</guid>
      <dc:creator>Lundin</dc:creator>
      <dc:date>2008-10-24T18:07:49Z</dc:date>
    </item>
  </channel>
</rss>

