<?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>CodeWarrior for MCUのトピックRe: CW 10.6 TAD K64 Ram usage</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/CW-10-6-TAD-K64-Ram-usage/m-p/323148#M11024</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found the issue was in the K64 Linker file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; /* kernel space starts after RAM variables (Location of MQX Kernel data + MQX heap) */&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; end_of_kd&amp;nbsp;&amp;nbsp; (RW): ORIGIN = 0x2000FFF0, LENGTH = 0x00000000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;needed to be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; /* kernel space starts after RAM variables (Location of MQX Kernel data + MQX heap) */&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; end_of_kd&amp;nbsp;&amp;nbsp; (RW): ORIGIN = 0x2002FFF0, LENGTH = 0x00000000&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Jun 2014 19:39:06 GMT</pubDate>
    <dc:creator>leepenn</dc:creator>
    <dc:date>2014-06-26T19:39:06Z</dc:date>
    <item>
      <title>CW 10.6 TAD K64 Ram usage</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/CW-10-6-TAD-K64-Ram-usage/m-p/323147#M11023</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am evaluating the advantages of the K64 over the K60, the first thing I notice is that when the projects for the K64 do not show that the 256k ram is available in TAD just 126K is available. Is this a CW 10.6 limitation?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jun 2014 19:13:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/CW-10-6-TAD-K64-Ram-usage/m-p/323147#M11023</guid>
      <dc:creator>leepenn</dc:creator>
      <dc:date>2014-06-23T19:13:50Z</dc:date>
    </item>
    <item>
      <title>Re: CW 10.6 TAD K64 Ram usage</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/CW-10-6-TAD-K64-Ram-usage/m-p/323148#M11024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found the issue was in the K64 Linker file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; /* kernel space starts after RAM variables (Location of MQX Kernel data + MQX heap) */&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; end_of_kd&amp;nbsp;&amp;nbsp; (RW): ORIGIN = 0x2000FFF0, LENGTH = 0x00000000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;needed to be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; /* kernel space starts after RAM variables (Location of MQX Kernel data + MQX heap) */&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; end_of_kd&amp;nbsp;&amp;nbsp; (RW): ORIGIN = 0x2002FFF0, LENGTH = 0x00000000&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2014 19:39:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/CW-10-6-TAD-K64-Ram-usage/m-p/323148#M11024</guid>
      <dc:creator>leepenn</dc:creator>
      <dc:date>2014-06-26T19:39:06Z</dc:date>
    </item>
  </channel>
</rss>

