<?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 Setting up an existing project for the simulator in CodeWarrior for StarCore</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-StarCore/Setting-up-an-existing-project-for-the-simulator/m-p/779925#M549</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using CodeWarrior for StarCore 10.7.2.&amp;nbsp; We have an existing project that we build and run on hardware.&amp;nbsp; The project was originally developed on the MSC8126, ported to MSC8144, and again to MSC8156.&amp;nbsp; We have no in-circuit emulation or JTAG probe capability on the hardware.&amp;nbsp; All we can do is look at global memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The project contains three "pieces": a vendor-supplied G.729AB codec in a library, a MELP codec in a library, and the actual application executable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We recently discovered that there is a serious problem in the G.729AB codec.&amp;nbsp; The codec came from DelCom 10 years ago.&amp;nbsp; DelCom is now apparently out of business and long gone.&amp;nbsp; By carefully reading the code and comparing intermediate results to the ITU-T reference implementation, I've already found and fixed a couple of problems.&amp;nbsp; I'm at the point where that is no longer sufficient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically, I need to set up the simulator, and debug interactively.&amp;nbsp; The documentation does not address the question of taking an existing project and adding simulator debug capability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone please provide a procedure, or at least some tips?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Jan 2018 17:17:59 GMT</pubDate>
    <dc:creator>johnstrohm</dc:creator>
    <dc:date>2018-01-11T17:17:59Z</dc:date>
    <item>
      <title>Setting up an existing project for the simulator</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-StarCore/Setting-up-an-existing-project-for-the-simulator/m-p/779925#M549</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using CodeWarrior for StarCore 10.7.2.&amp;nbsp; We have an existing project that we build and run on hardware.&amp;nbsp; The project was originally developed on the MSC8126, ported to MSC8144, and again to MSC8156.&amp;nbsp; We have no in-circuit emulation or JTAG probe capability on the hardware.&amp;nbsp; All we can do is look at global memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The project contains three "pieces": a vendor-supplied G.729AB codec in a library, a MELP codec in a library, and the actual application executable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We recently discovered that there is a serious problem in the G.729AB codec.&amp;nbsp; The codec came from DelCom 10 years ago.&amp;nbsp; DelCom is now apparently out of business and long gone.&amp;nbsp; By carefully reading the code and comparing intermediate results to the ITU-T reference implementation, I've already found and fixed a couple of problems.&amp;nbsp; I'm at the point where that is no longer sufficient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically, I need to set up the simulator, and debug interactively.&amp;nbsp; The documentation does not address the question of taking an existing project and adding simulator debug capability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone please provide a procedure, or at least some tips?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jan 2018 17:17:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-StarCore/Setting-up-an-existing-project-for-the-simulator/m-p/779925#M549</guid>
      <dc:creator>johnstrohm</dc:creator>
      <dc:date>2018-01-11T17:17:59Z</dc:date>
    </item>
  </channel>
</rss>

