<?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: about RW data segment in K64 Linker script file in Kinetis Software Development Kit</title>
    <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/about-RW-data-segment-in-K64-Linker-script-file/m-p/553515#M5693</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi nine,&lt;/P&gt;&lt;P&gt;The reason is that the Kinetis K series has two memory controllers, one for each segment. So indeed there are two RAM ranges/segments, even if they are close together. You might face a hard fault if you place a variable/object over that 0x2000'0000 boundary depending on how you access it. More details about this you can find in &lt;A class="link-titled" href="https://mcuoneclipse.com/2013/07/10/freertos-heap-with-segmented-kinetis-k-sram/" title="https://mcuoneclipse.com/2013/07/10/freertos-heap-with-segmented-kinetis-k-sram/"&gt;https://mcuoneclipse.com/2013/07/10/freertos-heap-with-segmented-kinetis-k-sram/&lt;/A&gt;&amp;nbsp; (make sure you check the discussion area).&lt;/P&gt;&lt;P&gt;So you *could* have the two areas in one piece, but you need to be careful about what you do with your memory allocation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Aug 2016 05:33:23 GMT</pubDate>
    <dc:creator>BlackNight</dc:creator>
    <dc:date>2016-08-24T05:33:23Z</dc:date>
    <item>
      <title>about RW data segment in K64 Linker script file</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/about-RW-data-segment-in-K64-Linker-script-file/m-p/553514#M5692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; I have question about .bss segment in file&amp;nbsp;MK64FN1M0xxx12_flash.ld, The R/W memory data area was divided among m_data and m_data_2. &amp;nbsp;but these two segment is continuous. why not &amp;nbsp;not take it as whole segment? if it can be taken as union segment. Then all data are use such memory area. for example. the .bss segment in my program is&amp;nbsp;too large, i had to assign the .bss segment to m_data_2. Then some memory of m_data are to be wasted. Is there any reason to divided into two separated segment?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2016 01:36:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/about-RW-data-segment-in-K64-Linker-script-file/m-p/553514#M5692</guid>
      <dc:creator>ninesun</dc:creator>
      <dc:date>2016-08-24T01:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: about RW data segment in K64 Linker script file</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/about-RW-data-segment-in-K64-Linker-script-file/m-p/553515#M5693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi nine,&lt;/P&gt;&lt;P&gt;The reason is that the Kinetis K series has two memory controllers, one for each segment. So indeed there are two RAM ranges/segments, even if they are close together. You might face a hard fault if you place a variable/object over that 0x2000'0000 boundary depending on how you access it. More details about this you can find in &lt;A class="link-titled" href="https://mcuoneclipse.com/2013/07/10/freertos-heap-with-segmented-kinetis-k-sram/" title="https://mcuoneclipse.com/2013/07/10/freertos-heap-with-segmented-kinetis-k-sram/"&gt;https://mcuoneclipse.com/2013/07/10/freertos-heap-with-segmented-kinetis-k-sram/&lt;/A&gt;&amp;nbsp; (make sure you check the discussion area).&lt;/P&gt;&lt;P&gt;So you *could* have the two areas in one piece, but you need to be careful about what you do with your memory allocation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2016 05:33:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/about-RW-data-segment-in-K64-Linker-script-file/m-p/553515#M5693</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2016-08-24T05:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: about RW data segment in K64 Linker script file</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/about-RW-data-segment-in-K64-Linker-script-file/m-p/553516#M5694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok I see .Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2016 09:02:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/about-RW-data-segment-in-K64-Linker-script-file/m-p/553516#M5694</guid>
      <dc:creator>ninesun</dc:creator>
      <dc:date>2016-08-24T09:02:36Z</dc:date>
    </item>
  </channel>
</rss>

