<?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: Too Much RAM ... really in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157200#M9133</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi Wingsy,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;It is very common, especially in the early days of a device to actually give the full memory (flash and ram) in what are supposed to be reduced memory devices such as the GB/GT range. This has occurred before with QY/QT devices.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The mask code you have quoted is shared between both GB and GT and both 32A and 60A. So it is quite possible this is the case here.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;P&amp;amp;E attempt to limit access to what is supposed to be there, so try telling P&amp;amp;E you have got a GT60A and give it a GT32A and see what happens.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 21 Oct 2007 08:47:21 GMT</pubDate>
    <dc:creator>peg</dc:creator>
    <dc:date>2007-10-21T08:47:21Z</dc:date>
    <item>
      <title>MC9S08GT32A Too Much RAM ... really</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157197#M9130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;P&gt;OK, I'm confused. I've been working with this 9S08GT32A for months now, and I've noticed random data in the memory region above the top of my stack, at $087F, the top of RAM for a GT32A. So just now I got curios and started poking around up there, and I can read and write to memory all the way up to $107F! So, why has this chip got 4K of RAM in it (like a GT60) when a GT32A is only supposed to have 2K?&lt;BR /&gt;&lt;BR /&gt;Markings on the chip are:&lt;BR /&gt;MC9S08&lt;BR /&gt;GT32ACFBE&lt;BR /&gt;3L11Y&lt;BR /&gt;CTAA0650&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Added p/n to subject.&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Message Edited by NLFSJ on &lt;/SPAN&gt;&lt;SPAN class="date_text"&gt;2007-10-20&lt;/SPAN&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;SPAN class="time_text"&gt;09:33 AM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Oct 2007 22:03:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157197#M9130</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2007-10-20T22:03:09Z</dc:date>
    </item>
    <item>
      <title>Re: Too Much RAM ... really</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157198#M9131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Wingsy,&lt;BR /&gt;&lt;BR /&gt;Are you sure it is really 4K and not the same 2K appearing twice?&lt;BR /&gt;&lt;BR /&gt;Peter House&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Oct 2007 22:09:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157198#M9131</guid>
      <dc:creator>PeterHouse</dc:creator>
      <dc:date>2007-10-20T22:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: Too Much RAM ... really</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157199#M9132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Yes, it's not that, but it may not be real RAM anyway. I just executed a routine to clear all memory up to $107F and locations above $087F did not clear. However, I'm still able to change any location up to $107F using P&amp;amp;E Multilink debugger. Maybe P&amp;amp;E is just making me think there is RAM there when really it's not. I've tried this on 3 different chips and I get the same results. I don't know what it is that's doing this but I'm pretty much convinced that I really don't have RAM up there.&lt;BR /&gt;&lt;BR /&gt;So, if I could I would remove "really" from my original subject line. &lt;IMG alt=":smileyhappy:" class="emoticon emoticon-smileyhappy" id="smileyhappy" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-happy.gif" title="Smiley Happy" /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Oct 2007 22:22:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157199#M9132</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2007-10-20T22:22:44Z</dc:date>
    </item>
    <item>
      <title>Re: Too Much RAM ... really</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157200#M9133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi Wingsy,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;It is very common, especially in the early days of a device to actually give the full memory (flash and ram) in what are supposed to be reduced memory devices such as the GB/GT range. This has occurred before with QY/QT devices.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The mask code you have quoted is shared between both GB and GT and both 32A and 60A. So it is quite possible this is the case here.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;P&amp;amp;E attempt to limit access to what is supposed to be there, so try telling P&amp;amp;E you have got a GT60A and give it a GT32A and see what happens.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 21 Oct 2007 08:47:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157200#M9133</guid>
      <dc:creator>peg</dc:creator>
      <dc:date>2007-10-21T08:47:21Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S08GT32A Too Much RAM ... really</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157201#M9134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;this is a very common thing that uC vendors do.&amp;nbsp; It's the same mask, many times the same memory and peripherals are there as in their common full up parts, but beware it's not tested nor guaranteed good.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;You may get lucky using it this time, but next time it might not work (or it can change in future parts).&lt;/DIV&gt;&lt;DIV&gt;And what would you complain about, "I know it's not supposed to be there, but...".&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;my two cents.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;uCTechnoGeek&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Oct 2007 10:03:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08GT32A-Too-Much-RAM-really/m-p/157201#M9134</guid>
      <dc:creator>UcTechnoGeek</dc:creator>
      <dc:date>2007-10-22T10:03:08Z</dc:date>
    </item>
  </channel>
</rss>

