<?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 Re: CW: defining C  code memory address in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201505#M16522</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Thanks CrazyCat&lt;BR /&gt;. I now have the C code compiling at a higher memory address, likewise&lt;BR /&gt;its ram useage.&lt;BR /&gt;My next problem is how to send the compiled C code to the debugger, along with&lt;BR /&gt;an independant CW assembler code.&lt;BR /&gt;The C code will not change, but I need to be able to modify and assemble the assembler code&lt;BR /&gt;and send it the the debugger/flasher with the C code output.&lt;BR /&gt;Is there a way to tell the linker(?) or downloader to combine the two output files?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Nov 2008 07:16:25 GMT</pubDate>
    <dc:creator>donw</dc:creator>
    <dc:date>2008-11-14T07:16:25Z</dc:date>
    <item>
      <title>CW: defining C  code memory address</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201503#M16520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;CW experts please!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I want to 'intergrate' some C code with assembler code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have some C code (for JM60) and I want to have it complied starting at a certain&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;address. (I want to place it higher up in the flash memory address).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I also want to define the starting RAM address of the variables. (again to move them up in higher ram)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Also I want to be able to send this C complied output to the debugger for flashing, along with&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;a pure assembler file.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I will need to edit/assemble the assembler code, but not the C code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Nov 2008 17:28:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201503#M16520</guid>
      <dc:creator>donw</dc:creator>
      <dc:date>2008-11-12T17:28:45Z</dc:date>
    </item>
    <item>
      <title>Re: CW: defining C  code memory address</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201504#M16521</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 need to place your C code in a user defined section (using #pragma CODE_SEG) and place this section accordingly in your .PRM file.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;For your variable I would also recommend defining them in a user defined data section (using #pragma DATA_SEG) and placing the section appropriately in the .prm file.&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>Wed, 12 Nov 2008 20:41:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201504#M16521</guid>
      <dc:creator>CrasyCat</dc:creator>
      <dc:date>2008-11-12T20:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: CW: defining C  code memory address</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201505#M16522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Thanks CrazyCat&lt;BR /&gt;. I now have the C code compiling at a higher memory address, likewise&lt;BR /&gt;its ram useage.&lt;BR /&gt;My next problem is how to send the compiled C code to the debugger, along with&lt;BR /&gt;an independant CW assembler code.&lt;BR /&gt;The C code will not change, but I need to be able to modify and assemble the assembler code&lt;BR /&gt;and send it the the debugger/flasher with the C code output.&lt;BR /&gt;Is there a way to tell the linker(?) or downloader to combine the two output files?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Nov 2008 07:16:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201505#M16522</guid>
      <dc:creator>donw</dc:creator>
      <dc:date>2008-11-14T07:16:25Z</dc:date>
    </item>
    <item>
      <title>Re: CW: defining C  code memory address</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201506#M16523</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;Which version of CodeWarrior are you using?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;If you are using CodeWarrior for MCU V6.1 or higher, this can be done from the debugger command line using command LOAD with option ADD_SYMBOLS.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The attached technical note explains how to achieve that.&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>Mon, 24 Nov 2008 18:41:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201506#M16523</guid>
      <dc:creator>CrasyCat</dc:creator>
      <dc:date>2008-11-24T18:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: CW: defining C  code memory address</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201507#M16524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;thanks. That should solve this problem&lt;BR /&gt;- don&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Nov 2008 06:08:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/CW-defining-C-code-memory-address/m-p/201507#M16524</guid>
      <dc:creator>donw</dc:creator>
      <dc:date>2008-11-25T06:08:31Z</dc:date>
    </item>
  </channel>
</rss>

