<?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: SRAM segment in MCUXpresso IDE</title>
    <link>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808355#M2913</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jorge,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any document on why the memory is split into 2, and how MCU works if there is data in both parts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Oct 2019 05:11:53 GMT</pubDate>
    <dc:creator>hedj</dc:creator>
    <dc:date>2019-10-22T05:11:53Z</dc:date>
    <item>
      <title>SRAM segment</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808351#M2909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;K22 SRAM is split into 2 64K segments.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently the linker is only using SRAM_UPPER.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="2018-09-28.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/73809iAC71FAF82A371B1E/image-size/large?v=v2&amp;amp;px=999" role="button" title="2018-09-28.png" alt="2018-09-28.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;How should i change the MCUXpresso settings to:&lt;/P&gt;&lt;P&gt;a) merge the SRAM into 1 128K.&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;b) evenly distribute across both segments?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="2018-09-28 (2).png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/73856i4FEAC7ACB75239A4/image-size/large?v=v2&amp;amp;px=999" role="button" title="2018-09-28 (2).png" alt="2018-09-28 (2).png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Sep 2018 22:05:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808351#M2909</guid>
      <dc:creator>anbui</dc:creator>
      <dc:date>2018-09-28T22:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: SRAM segment</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808352#M2910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi An Bui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This means your RAM memory has overflowed. You cannot mearge this two RAM into one because it could cause you bus problems. My recomendation is that you place some data memory in the lower ram manually with a Macro definition in #include "cr_section_macros.h" for example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;__BSS(SRAM_LOWER)&lt;/STRONG&gt; uint8_t s_currSendBuf2[]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Jorge Alcala&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Oct 2018 17:11:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808352#M2910</guid>
      <dc:creator>jorge_a_vazquez</dc:creator>
      <dc:date>2018-10-09T17:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: SRAM segment</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808353#M2911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jorge,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Initially the linker put all my data into SRAM_UPPER, which causes it to overflow.&lt;/P&gt;&lt;P&gt;So I did what you suggested, I put&amp;nbsp;&lt;STRONG style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: bold;"&gt;__BSS(SRAM_LOWER) &lt;/STRONG&gt;in front of a big float array about 28k size; after compiling I found linker put all data into SRAM_LOWER, which definitely causes another overflow.&lt;/P&gt;&lt;P&gt;How to make the linker to put the rest data in upper RAM without manually adding &lt;STRONG style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: bold;"&gt;__BSS(SRAM_UPPER)&amp;nbsp;&lt;/STRONG&gt;for rest data? I have a few dozens of them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Oct 2019 09:11:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808353#M2911</guid>
      <dc:creator>hedj</dc:creator>
      <dc:date>2019-10-03T09:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: SRAM segment</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808354#M2912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think I made a calculation error: the data put into SRAM_LOWER by linker is exactly the size of that big array. That means __BSS() works as expected.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Oct 2019 06:14:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808354#M2912</guid>
      <dc:creator>hedj</dc:creator>
      <dc:date>2019-10-07T06:14:01Z</dc:date>
    </item>
    <item>
      <title>Re: SRAM segment</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808355#M2913</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jorge,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any document on why the memory is split into 2, and how MCU works if there is data in both parts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Oct 2019 05:11:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/SRAM-segment/m-p/808355#M2913</guid>
      <dc:creator>hedj</dc:creator>
      <dc:date>2019-10-22T05:11:53Z</dc:date>
    </item>
  </channel>
</rss>

