<?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: Memory mapping on MC9S12DG128 in S12 / MagniV Microcontrollers</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175792#M6144</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;1) 8k RAM can't be mapped to any 2k boundary. Irrelevant INITRM bits (bit4 to bit0)&amp;nbsp;are ignored. So 8k RAM can be mapped to any 8k boundary, only 0-1FFF, 2000-3FFF, 4000-5FFF and so on.&lt;/DIV&gt;&lt;DIV&gt;2) By default 8k RAM is mapped to 0-1FFF. By default&amp;nbsp;registers block is mapped to 0-3FF. Registers block takes precedence over flash, EEPROM and RAM, so by default only 7k out of 8k RAM are&amp;nbsp;accessible at 400-1FFF.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 26 Jul 2008 02:10:53 GMT</pubDate>
    <dc:creator>kef</dc:creator>
    <dc:date>2008-07-26T02:10:53Z</dc:date>
    <item>
      <title>Memory mapping on MC9S12DG128</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175791#M6143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;HI, everyone.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm working with Freescale uCs only a few days and I have some problems with understanding of memory mapping.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I'll try to describe my problems:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) this uC has 8k RAM and in user guide written that this memory can be mapped to any 8k boundary. But INITRM register defines the upper 5 bits of RAM address. So RAM can be mapped to any 2k boundary.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) After reset RAM memory mapped to 0x0000-0x1FFF. But the INITRM reset value is 0x09 (hex). So RAM should be mapped to 0x0800-0x2800.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can you explain me this contradictions?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jul 2008 22:49:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175791#M6143</guid>
      <dc:creator>condor</dc:creator>
      <dc:date>2008-07-25T22:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: Memory mapping on MC9S12DG128</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175792#M6144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;1) 8k RAM can't be mapped to any 2k boundary. Irrelevant INITRM bits (bit4 to bit0)&amp;nbsp;are ignored. So 8k RAM can be mapped to any 8k boundary, only 0-1FFF, 2000-3FFF, 4000-5FFF and so on.&lt;/DIV&gt;&lt;DIV&gt;2) By default 8k RAM is mapped to 0-1FFF. By default&amp;nbsp;registers block is mapped to 0-3FF. Registers block takes precedence over flash, EEPROM and RAM, so by default only 7k out of 8k RAM are&amp;nbsp;accessible at 400-1FFF.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Jul 2008 02:10:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175792#M6144</guid>
      <dc:creator>kef</dc:creator>
      <dc:date>2008-07-26T02:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: Memory mapping on MC9S12DG128</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175793#M6145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Thanks for the answer:&lt;BR /&gt;1) Can you give me the link to the document where 4-0 bits are ignored? In User guide INITRM is defined like this:&lt;BR /&gt;bit7 - RAM15&lt;BR /&gt;bit6 - RAM14&lt;BR /&gt;bit5 - RAM13&lt;BR /&gt;bit4 - RAM12&lt;BR /&gt;bit3 - RAM11&lt;BR /&gt;bit2 - ignored&lt;BR /&gt;bit1 - ignored&lt;BR /&gt;bit0 - RAMHAL&lt;BR /&gt;&lt;BR /&gt;So only 2-0 bits are ignored in address and therefore boundary is 2k. Is this a mistake in user guide?&lt;BR /&gt;&lt;BR /&gt;2) The INITRM reset value is 0x09, so bit3 is 1 and base RAM address should be 0x0800. If bit4 and bit3 are really ignored then everything is ok and the base address 0x0000.&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Jul 2008 04:11:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175793#M6145</guid>
      <dc:creator>condor</dc:creator>
      <dc:date>2008-07-26T04:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: Memory mapping on MC9S12DG128</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175794#M6146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;The RAMHAL is not ignored,&lt;BR /&gt;I searched for RAMHAL in this forum and found&lt;BR /&gt;&lt;A href="http://forums.freescale.com/freescale/board/message?board.id=16BITCOMM&amp;amp;message.id=976" target="_blank"&gt;http://forums.freescale.com/freescale/board/message?board.id=16BITCOMM&amp;amp;message.id=976&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;which also contains a reference to this:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.freescale.com/files/microcontrollers/doc/eng_bulletin/EB386.pdf?srch=1" rel="nofollow" target="_blank"&gt;http://www.freescale.com/files/microcontrollers/doc/eng_bulletin/EB386.pdf?srch=1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;which also mentions in which cases the lower bits of INITRM are ignored.&lt;BR /&gt;&lt;BR /&gt;hope it helps :smileyhappy:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Daniel&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Jul 2008 13:01:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175794#M6146</guid>
      <dc:creator>CompilerGuru</dc:creator>
      <dc:date>2008-07-26T13:01:43Z</dc:date>
    </item>
    <item>
      <title>Re: Memory mapping on MC9S12DG128</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175795#M6147</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Thanks!&lt;BR /&gt;Now everything is clear.&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Jul 2008 19:13:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Memory-mapping-on-MC9S12DG128/m-p/175795#M6147</guid>
      <dc:creator>condor</dc:creator>
      <dc:date>2008-07-26T19:13:15Z</dc:date>
    </item>
  </channel>
</rss>

