<?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 RAM initalization in Classic/Legacy CodeWarrior</title>
    <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/RAM-initalization/m-p/204372#M5637</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;SPAN&gt;I have external RAM on my system. It is being automaticaly intialized when the system starts up. It is battery backed.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I whish it not to be altered. I are assuming there is a setting to stop this from happening. But where is it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The memory is decleared as such&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;c file&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#pragma DATA_SEG __GPAGE_SEG BATTERY_RAM&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; volatile Prog_Layout&amp;nbsp;&amp;nbsp; Program[MAX_PROGRAMS + 2];&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;prm file&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; BATTERY_RAM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; INTO&amp;nbsp; NO_INIT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x200000'G TO 0x3FFFFF'G;&amp;nbsp;&amp;nbsp; // CS1 BatteryRAM;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;yet when the system is rebooted it has 64 in every byte.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;anyone got any surgestions.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Mar 2008 05:42:54 GMT</pubDate>
    <dc:creator>NZ_Design</dc:creator>
    <dc:date>2008-03-19T05:42:54Z</dc:date>
    <item>
      <title>RAM initalization</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/RAM-initalization/m-p/204372#M5637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;SPAN&gt;I have external RAM on my system. It is being automaticaly intialized when the system starts up. It is battery backed.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I whish it not to be altered. I are assuming there is a setting to stop this from happening. But where is it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The memory is decleared as such&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;c file&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#pragma DATA_SEG __GPAGE_SEG BATTERY_RAM&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; volatile Prog_Layout&amp;nbsp;&amp;nbsp; Program[MAX_PROGRAMS + 2];&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;prm file&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; BATTERY_RAM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; INTO&amp;nbsp; NO_INIT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x200000'G TO 0x3FFFFF'G;&amp;nbsp;&amp;nbsp; // CS1 BatteryRAM;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;yet when the system is rebooted it has 64 in every byte.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;anyone got any surgestions.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 05:42:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/RAM-initalization/m-p/204372#M5637</guid>
      <dc:creator>NZ_Design</dc:creator>
      <dc:date>2008-03-19T05:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: RAM initalization</title>
      <link>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/RAM-initalization/m-p/204373#M5638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Are you sure it the compiler startup code which inits your RAM?&lt;BR /&gt;I would guess it is something else, the NO_INIT should stop the linker from init your data, and also the startup code would 0-init it, and not write 0x40.&lt;BR /&gt;So I would guess that something in your battery backed RAM setup is not working properly and look in that direction.&lt;BR /&gt;&lt;BR /&gt;Daniel&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2008 10:42:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Classic-Legacy-CodeWarrior/RAM-initalization/m-p/204373#M5638</guid>
      <dc:creator>CompilerGuru</dc:creator>
      <dc:date>2008-03-19T10:42:28Z</dc:date>
    </item>
  </channel>
</rss>

