<?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: **bleep** PRAGMA in S12 / MagniV Microcontrollers</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130584#M1410</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;With small (and with no __FAR_SEG qualifier in the #pragma CODE_SEG)&lt;BR /&gt;the compiler will use a JSR to call those functions.&lt;BR /&gt;But appart that it may not work at runtime, this does not explain why the functions do not end up at the right address.&lt;BR /&gt;So the memory model matters if it works at runtime, but it does not matter for the allocation behaviour.&lt;BR /&gt;&lt;BR /&gt;Daniel&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Sep 2006 19:17:12 GMT</pubDate>
    <dc:creator>CompilerGuru</dc:creator>
    <dc:date>2006-09-19T19:17:12Z</dc:date>
    <item>
      <title>**bleep** PRAGMA</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130581#M1407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've got a very big problem...... I use this sentence "#pragma CODE_SEG PAG_1" so, the following code is in that page... But when I compile it, the code appears at the DEFAULT_ROM page.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;That's part of what's inside the prm file:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;PAGE_3C = READ_ONLY 0x3C8000 TO 0x3CBFFF;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;PAG_1 INTO PAGE_3C;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any idea of what's going on? Or maybe you know where I'm wrong at...&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks a lot. &lt;/SPAN&gt;&lt;A href="http://freescale.i.lithium.com/i/smilies/16x16_smiley-wink.gif"&gt;&lt;IMG alt=":smileywink:" class="emoticon emoticon-smileywink" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-wink.gif" title="Smiley Wink" /&gt;&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Sep 2006 00:10:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130581#M1407</guid>
      <dc:creator>SebaS</dc:creator>
      <dc:date>2006-09-19T00:10:22Z</dc:date>
    </item>
    <item>
      <title>Re: **bleep** PRAGMA</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130582#M1408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;strange, your syntax looks ok.&lt;BR /&gt;What I would check:&lt;BR /&gt;- how does the #pragma look like after preprocessing. #define's can cause many surprises...&lt;BR /&gt;- does it work if you use another name at those two places (#pragma &amp;amp; prm)? Same reason than for the first suggestion, just to check for some name collisions.&lt;BR /&gt;- the section containing the object refered to with INIT is special (default _Startup)&lt;BR /&gt;Is this here the case? The content of this section ends up in ".init".&lt;BR /&gt;- I would actually decode the object file, but its content may be hard to decipher if you are not familiar with ELF. With "-e -ed -d" decoder/importer options everything is displayed (usually too much...)&lt;BR /&gt;- this is about code, not constants, correct? (use #pragma CONST_SEG name for constants).&lt;BR /&gt;&lt;BR /&gt;Well, these are about all ideas I have. If they dont help, please show us a complete sample.&lt;BR /&gt;&lt;BR /&gt;Daniel&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Sep 2006 02:46:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130582#M1408</guid>
      <dc:creator>CompilerGuru</dc:creator>
      <dc:date>2006-09-19T02:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: **bleep** PRAGMA</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130583#M1409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;What would happen if not compiling with -Mb (banked memory)? Could be the cause of the problem.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Sep 2006 13:53:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130583#M1409</guid>
      <dc:creator>Lundin</dc:creator>
      <dc:date>2006-09-19T13:53:55Z</dc:date>
    </item>
    <item>
      <title>Re: **bleep** PRAGMA</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130584#M1410</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;With small (and with no __FAR_SEG qualifier in the #pragma CODE_SEG)&lt;BR /&gt;the compiler will use a JSR to call those functions.&lt;BR /&gt;But appart that it may not work at runtime, this does not explain why the functions do not end up at the right address.&lt;BR /&gt;So the memory model matters if it works at runtime, but it does not matter for the allocation behaviour.&lt;BR /&gt;&lt;BR /&gt;Daniel&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Sep 2006 19:17:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/bleep-PRAGMA/m-p/130584#M1410</guid>
      <dc:creator>CompilerGuru</dc:creator>
      <dc:date>2006-09-19T19:17:12Z</dc:date>
    </item>
  </channel>
</rss>

