<?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: Flash vs RAM build configuration in CodeWarrior for MCU</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Flash-vs-RAM-build-configuration/m-p/724695#M14261</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Egoitz,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Normally, those options represent the target where your code will be loaded by a loader (either RAM or Flash).&lt;/P&gt;&lt;P&gt;RAM target is used in general for fast debugging and when you cannot write or you do not have a flash memory(ROM only). Once your code was loaded in RAM, you need to load the code each time when a reset occurrs (RAM loses its content being a volatile memory).&lt;/P&gt;&lt;P&gt;Flash target on the other side, is used to keep your code for a long time even after a reset will occur.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a summary, loading your code in RAM and executing it from there is faster than executing it from Flash.&lt;/P&gt;&lt;P&gt;You need to pay attention here, because your code must be linked as position independent or linked in RAM's address space.&lt;/P&gt;&lt;P&gt;For instance, if you wrote a scatter file or a loader file and linked some code to a fixed address, executing from RAM and referencing from Flash will crash.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 Apr 2018 18:28:46 GMT</pubDate>
    <dc:creator>briceagbebe-cos</dc:creator>
    <dc:date>2018-04-12T18:28:46Z</dc:date>
    <item>
      <title>Flash vs RAM build configuration</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Flash-vs-RAM-build-configuration/m-p/724694#M14260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everybody,&lt;/P&gt;&lt;P&gt;I just downloaded Codewarrior V11.0 and making some trial projects I’ve seen that there is the option to choose RAM or FLASH.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/7894i14CA00CC29FCB893/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.jpg" alt="pastedImage_1.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I’ve been looking information about this but I couldn’t find anything, so I wonder if someone could help me explaining what is this option for and what is the difference between choosing one or the other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you and regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Apr 2018 09:00:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Flash-vs-RAM-build-configuration/m-p/724694#M14260</guid>
      <dc:creator>egoitztoledo</dc:creator>
      <dc:date>2018-04-12T09:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: Flash vs RAM build configuration</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Flash-vs-RAM-build-configuration/m-p/724695#M14261</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Egoitz,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Normally, those options represent the target where your code will be loaded by a loader (either RAM or Flash).&lt;/P&gt;&lt;P&gt;RAM target is used in general for fast debugging and when you cannot write or you do not have a flash memory(ROM only). Once your code was loaded in RAM, you need to load the code each time when a reset occurrs (RAM loses its content being a volatile memory).&lt;/P&gt;&lt;P&gt;Flash target on the other side, is used to keep your code for a long time even after a reset will occur.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a summary, loading your code in RAM and executing it from there is faster than executing it from Flash.&lt;/P&gt;&lt;P&gt;You need to pay attention here, because your code must be linked as position independent or linked in RAM's address space.&lt;/P&gt;&lt;P&gt;For instance, if you wrote a scatter file or a loader file and linked some code to a fixed address, executing from RAM and referencing from Flash will crash.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Apr 2018 18:28:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Flash-vs-RAM-build-configuration/m-p/724695#M14261</guid>
      <dc:creator>briceagbebe-cos</dc:creator>
      <dc:date>2018-04-12T18:28:46Z</dc:date>
    </item>
    <item>
      <title>Re: Flash vs RAM build configuration</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Flash-vs-RAM-build-configuration/m-p/724696#M14262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Briceag Bebe-Cosmin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Understood!!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Just for try out, I debugged a very simple blinking LED program with both configurations Flash and RAM and it occurred as you say when ressetting.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If I’m not wrong, the Flash memory has a limited amount of write cycles rather smaller than the RAM, so taking this into account, I think that debugging the programs in the RAM until having them finished (or almost) and make the last checks at the Flash would be a good practice that I’m going to adopt, mostly for complex projects where having no code errors from the beginning is not easy job.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;It's been a very clarifying and useful answer!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thank you and regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Apr 2018 06:58:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Flash-vs-RAM-build-configuration/m-p/724696#M14262</guid>
      <dc:creator>egoitztoledo</dc:creator>
      <dc:date>2018-04-13T06:58:26Z</dc:date>
    </item>
  </channel>
</rss>

