<?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>S12 / MagniV MicrocontrollersのトピックS12 XGATE Debugging</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12-XGATE-Debugging/m-p/200409#M8094</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 am trying to choose a processor for my next project. My previouse project used a S12 device, and worked very well, the only problem I had towards the end was a bit of a squeeze on RAM resources. A good code trim seemed to sort it out!!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;So I am thinking of going towards an S12XE device for my new project - they seem cheaper (I guess Freescale want to puch their new devices) and I am thinking that some of my driver code could be re-used, or at least&amp;nbsp;retain the same style. As a bonus, I can also re-use the Metrowerks license I have!!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Debugging on the particular S12 device we chose previously was quite bad - the silicon had a bug that meant the trace facility in Metrowerks would not function, and only 2 breakpoints - felt like the 1980's...&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;So, my question is - is the debugging on the S12X devices any better?&lt;/DIV&gt;&lt;DIV&gt;Especially with the trace support - is this a useful feature - I'm thinking that with the additional XGATE accelaration there's a good chance the Trace module can get confused, or that debugging without Trace is a nightmare?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Any experiences, general gut feelings, recommendations gratefully received.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks,&lt;/DIV&gt;&lt;DIV&gt;Mike&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Nov 2008 18:48:02 GMT</pubDate>
    <dc:creator>EmbeddedCoder</dc:creator>
    <dc:date>2008-11-07T18:48:02Z</dc:date>
    <item>
      <title>S12 XGATE Debugging</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12-XGATE-Debugging/m-p/200409#M8094</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 am trying to choose a processor for my next project. My previouse project used a S12 device, and worked very well, the only problem I had towards the end was a bit of a squeeze on RAM resources. A good code trim seemed to sort it out!!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;So I am thinking of going towards an S12XE device for my new project - they seem cheaper (I guess Freescale want to puch their new devices) and I am thinking that some of my driver code could be re-used, or at least&amp;nbsp;retain the same style. As a bonus, I can also re-use the Metrowerks license I have!!&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Debugging on the particular S12 device we chose previously was quite bad - the silicon had a bug that meant the trace facility in Metrowerks would not function, and only 2 breakpoints - felt like the 1980's...&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;So, my question is - is the debugging on the S12X devices any better?&lt;/DIV&gt;&lt;DIV&gt;Especially with the trace support - is this a useful feature - I'm thinking that with the additional XGATE accelaration there's a good chance the Trace module can get confused, or that debugging without Trace is a nightmare?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Any experiences, general gut feelings, recommendations gratefully received.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks,&lt;/DIV&gt;&lt;DIV&gt;Mike&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Nov 2008 18:48:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12-XGATE-Debugging/m-p/200409#M8094</guid>
      <dc:creator>EmbeddedCoder</dc:creator>
      <dc:date>2008-11-07T18:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: S12 XGATE Debugging</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12-XGATE-Debugging/m-p/200410#M8095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hello Mike&lt;BR /&gt;&lt;BR /&gt;The on chip debug support for the S12X devices is enhanced with respect to the S12 devices.&lt;BR /&gt;The S12X DBG module offers 4 comparator channels with associated breakpoints that can be mapped to either CPU or XGATE and provide for breakpoints on PC addresses or data accesses.&lt;BR /&gt;&lt;BR /&gt;Triggers for tracing use a state sequencer for more flexible control of trace begin or trace end.&lt;BR /&gt;&lt;BR /&gt;Tracing of CPU and/or XGATE is supported by the DBG module. This does not confuse the DBG, but it can be slightly confusing trying to interpret the contents without a suitable debugging tool. For this reason it is recommended to use a debugger such as Codewarrior V4.6 or later. Codewarrior compiles a listing of the code flow from the trace buffer contents automatically.&lt;BR /&gt;&lt;BR /&gt;The BDM and DBG modules are described in detail in chapters 7 &amp;amp; 8 of the S12XE- reference manual...&lt;BR /&gt;&lt;A href="http://www.freescale.com/files/microcontrollers/doc/data_sheet/MC9S12XEP100RMV1.pdf?fpsp=1" target="test_blank"&gt;http://www.freescale.com/files/microcontrollers/doc/data_sheet/MC9S12XEP100RMV1.pdf?fpsp=1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;DPB&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Nov 2008 19:59:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12-XGATE-Debugging/m-p/200410#M8095</guid>
      <dc:creator>DPB</dc:creator>
      <dc:date>2008-11-07T19:59:08Z</dc:date>
    </item>
  </channel>
</rss>

