<?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 Question on SRAM size / availability in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Question-on-SRAM-size-availability/m-p/767101#M46669</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using &lt;STRONG&gt;K65&lt;/STRONG&gt; MCU for my application. This has 256 KBytes of RAM ( &amp;nbsp;&amp;nbsp;&amp;nbsp;SRAM_UPPER : 192 KB and SRAM_LOWER : 64 KB) and the access rule is as defined below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4.12 SRAM accesses&lt;BR /&gt;The SRAM is split into two logical arrays that are 32-bits wide.&lt;BR /&gt;• SRAM_L — Accessible by the code bus of the Cortex-M4 core and by the backdoor&lt;BR /&gt;port.&lt;BR /&gt;• SRAM_U — Accessible by the system bus of the Cortex-M4 core and by the&lt;/P&gt;&lt;P&gt;backdoor port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, can my application use both these portions of the SRAM seamlessly? In other words, both the sections are available for application to use (total 256 KB) ? Are there any constraints for the use?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Jan 2018 12:18:31 GMT</pubDate>
    <dc:creator>hegdepraveen</dc:creator>
    <dc:date>2018-01-29T12:18:31Z</dc:date>
    <item>
      <title>Question on SRAM size / availability</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Question-on-SRAM-size-availability/m-p/767101#M46669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using &lt;STRONG&gt;K65&lt;/STRONG&gt; MCU for my application. This has 256 KBytes of RAM ( &amp;nbsp;&amp;nbsp;&amp;nbsp;SRAM_UPPER : 192 KB and SRAM_LOWER : 64 KB) and the access rule is as defined below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4.12 SRAM accesses&lt;BR /&gt;The SRAM is split into two logical arrays that are 32-bits wide.&lt;BR /&gt;• SRAM_L — Accessible by the code bus of the Cortex-M4 core and by the backdoor&lt;BR /&gt;port.&lt;BR /&gt;• SRAM_U — Accessible by the system bus of the Cortex-M4 core and by the&lt;/P&gt;&lt;P&gt;backdoor port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, can my application use both these portions of the SRAM seamlessly? In other words, both the sections are available for application to use (total 256 KB) ? Are there any constraints for the use?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Jan 2018 12:18:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Question-on-SRAM-size-availability/m-p/767101#M46669</guid>
      <dc:creator>hegdepraveen</dc:creator>
      <dc:date>2018-01-29T12:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: Question on SRAM size / availability</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Question-on-SRAM-size-availability/m-p/767102#M46670</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi Praveen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally the SRAM can be considered as a linear 256k block of memory as long as a couple of things are considered:&lt;BR /&gt;1. Mis-aligned accesses across the boundary are not supported; this is generally not an issue since one should "generally" avoid misaligned accesses for compatibility (eg. the same code would "generally" fail on Cortex M0+ parts)&lt;BR /&gt;2. DMA burst across the boundary are not supported. It is quite unlikely that this will ever take place but if there is a chance you need to ensure that memory taking part in burst operations are restricted to being completely in one of the two sectors.&lt;BR /&gt;3. In &lt;EM&gt;some&lt;/EM&gt; low leakage only one of the memory sectors &lt;EM&gt;may&lt;/EM&gt; be retained. This depends on the mode and the device so consult the manual for specific details.&lt;BR /&gt;4. If you use bit banding on variables, only variables in the upper area can be operated on. If no bit banding on variables is used, there is no problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;Kinetis: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.utasker.com%2Fkinetis.html" rel="nofollow" target="_blank"&gt;http://www.utasker.com/kinetis.html&lt;/A&gt;&lt;BR /&gt;Kinetis K65/K66:&lt;BR /&gt;&lt;SPAN&gt;- &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.utasker.com%2Fkinetis%2FTWR-K65F180M.html" rel="nofollow" target="_blank"&gt;http://www.utasker.com/kinetis/TWR-K65F180M.html&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;- &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.utasker.com%2Fkinetis%2FFRDM-K66F.html" rel="nofollow" target="_blank"&gt;http://www.utasker.com/kinetis/FRDM-K66F.html&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;- &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.utasker.com%2Fkinetis%2FTEENSY_3.6.html" rel="nofollow" target="_blank"&gt;http://www.utasker.com/kinetis/TEENSY_3.6.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Free Open Source solution: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fgithub.com%2FuTasker%2FuTasker-Kinetis" rel="nofollow" target="_blank"&gt;https://github.com/uTasker/uTasker-Kinetis&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;Working project in 15 minutes video: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fyoutu.be%2FK8ScSgpgQ6M" rel="nofollow" target="_blank"&gt;https://youtu.be/K8ScSgpgQ6M&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For better, faster, cheaper product developments consider the uTasker developer's version, professional Kinetis support, one-on-one training and complete fast-track project solutions to set you apart from the herd : &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.utasker.com%2Fsupport.html" rel="nofollow" target="_blank"&gt;http://www.utasker.com/support.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Jan 2018 17:02:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Question-on-SRAM-size-availability/m-p/767102#M46670</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2018-01-29T17:02:57Z</dc:date>
    </item>
  </channel>
</rss>

