<?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>Classic/Legacy CodeWarrior中的主题 Re: CW SC - SC100 - How to analyse performance of the code on simulator</title>
    <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/CW-SC-SC100-How-to-analyse-performance-of-the-code-on-simulator/m-p/147879#M1887</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hello&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;You can use the Runsim command line simulator to collect profiling information in simulation.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Please refer to {Install}\Help\PDF\Targeting StarCore.pdf, chapter "Debugger Communication Protocols", section "RUNSIM Command-Line Tool" -&amp;gt; "RUNSIM Profiling" for more info.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;CrasyCat&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Sep 2007 17:51:12 GMT</pubDate>
    <dc:creator>CrasyCat</dc:creator>
    <dc:date>2007-09-20T17:51:12Z</dc:date>
    <item>
      <title>CW SC - SC100 - How to analyse performance of the code on simulator</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/CW-SC-SC100-How-to-analyse-performance-of-the-code-on-simulator/m-p/147878#M1886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Hi&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I want to analyse my code in terms of memory usages, cycle count, etc. I am using CodeWarrior IDE for StarCore V5.7.0 (Trial Version).&lt;/DIV&gt;&lt;DIV&gt;I don't have a hardware and I am using SC100 simulator. The profiler is not working on the simulator.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Please suggest a solution.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;--&lt;BR /&gt;Alban Edit: Please always include FSL Part Number in Message Subject line.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Message Edited by Alban on &lt;/SPAN&gt;&lt;SPAN class="date_text"&gt;2007-09-20&lt;/SPAN&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;SPAN class="time_text"&gt;10:18 AM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2007 15:43:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/CW-SC-SC100-How-to-analyse-performance-of-the-code-on-simulator/m-p/147878#M1886</guid>
      <dc:creator>amol</dc:creator>
      <dc:date>2007-09-20T15:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: CW SC - SC100 - How to analyse performance of the code on simulator</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/CW-SC-SC100-How-to-analyse-performance-of-the-code-on-simulator/m-p/147879#M1887</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hello&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;You can use the Runsim command line simulator to collect profiling information in simulation.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Please refer to {Install}\Help\PDF\Targeting StarCore.pdf, chapter "Debugger Communication Protocols", section "RUNSIM Command-Line Tool" -&amp;gt; "RUNSIM Profiling" for more info.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;CrasyCat&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2007 17:51:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/CW-SC-SC100-How-to-analyse-performance-of-the-code-on-simulator/m-p/147879#M1887</guid>
      <dc:creator>CrasyCat</dc:creator>
      <dc:date>2007-09-20T17:51:12Z</dc:date>
    </item>
  </channel>
</rss>

