<?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 Best practice for K8x QSPI Dual-Quad Address Ranges in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Best-practice-for-K8x-QSPI-Dual-Quad-Address-Ranges/m-p/1508985#M63858</link>
    <description>&lt;P&gt;Though I'd share...&lt;/P&gt;&lt;P&gt;The K8x QSPI peripheral can accept one or two QSPI flash devices, or a dual-die device (which is really only two identical flash dies and one chip).&amp;nbsp; Each can have a maximum size of 64MB.&lt;/P&gt;&lt;P&gt;In some NXP K8x QSPI peripheral examples the second die address range starts where the first ends. So for example:&lt;BR /&gt;&lt;BR /&gt;2x 32MB dies would have:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-A: 0x68000000-0x69FFFFFF&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-B: 0x6A000000-0x6BFFFFFF&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;and 2x 16MB dies would have:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-A: 0x68000000-0x68FFFFFF&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-B: 0x69000000-0x69FFFFFF&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;&lt;EM&gt;This arrangement is no longer ideal with the latest Segger Flasher-ARM/J-Flash&lt;/EM&gt;&lt;/STRONG&gt;&lt;/FONT&gt;.&lt;/P&gt;&lt;P&gt;In earlier J-Flash versions (many moons ago) I recall the ability to change these addresses, but this is no longer allowed. Instead, the full 64MB is always allocated for each bank, and it cannot be changed.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="deniscollis_0-1660937994824.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/190752iAA6CF32E87495B14/image-size/medium?v=v2&amp;amp;px=400" role="button" title="deniscollis_0-1660937994824.png" alt="deniscollis_0-1660937994824.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Bank-A now always starts at &lt;FONT face="courier new,courier"&gt;0x68000000&amp;nbsp;&lt;/FONT&gt;and&amp;nbsp;Bank-B always starts at &lt;FONT face="courier new,courier"&gt;0x6C000000&amp;nbsp;&lt;/FONT&gt;and it then follows that in the examples above:&lt;/P&gt;&lt;P&gt;2x 32MB dies should have:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Bank-A: 0x68000000-0x69FFFFFF&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-B: 0x6C000000-0x6DFFFFFF&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;and 2x 16MB dies should have:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Bank-A: 0x68000000-0x68FFFFFF&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-B: 0x6C000000-0x6CFFFFFF&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;...which seems to be the best-practice is you want successful production programming of your products.&lt;/P&gt;&lt;P&gt;Cheers!&lt;BR /&gt;Denis&lt;/P&gt;</description>
    <pubDate>Fri, 19 Aug 2022 20:00:28 GMT</pubDate>
    <dc:creator>deniscollis</dc:creator>
    <dc:date>2022-08-19T20:00:28Z</dc:date>
    <item>
      <title>Best practice for K8x QSPI Dual-Quad Address Ranges</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Best-practice-for-K8x-QSPI-Dual-Quad-Address-Ranges/m-p/1508985#M63858</link>
      <description>&lt;P&gt;Though I'd share...&lt;/P&gt;&lt;P&gt;The K8x QSPI peripheral can accept one or two QSPI flash devices, or a dual-die device (which is really only two identical flash dies and one chip).&amp;nbsp; Each can have a maximum size of 64MB.&lt;/P&gt;&lt;P&gt;In some NXP K8x QSPI peripheral examples the second die address range starts where the first ends. So for example:&lt;BR /&gt;&lt;BR /&gt;2x 32MB dies would have:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-A: 0x68000000-0x69FFFFFF&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-B: 0x6A000000-0x6BFFFFFF&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;and 2x 16MB dies would have:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-A: 0x68000000-0x68FFFFFF&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-B: 0x69000000-0x69FFFFFF&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;&lt;EM&gt;This arrangement is no longer ideal with the latest Segger Flasher-ARM/J-Flash&lt;/EM&gt;&lt;/STRONG&gt;&lt;/FONT&gt;.&lt;/P&gt;&lt;P&gt;In earlier J-Flash versions (many moons ago) I recall the ability to change these addresses, but this is no longer allowed. Instead, the full 64MB is always allocated for each bank, and it cannot be changed.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="deniscollis_0-1660937994824.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/190752iAA6CF32E87495B14/image-size/medium?v=v2&amp;amp;px=400" role="button" title="deniscollis_0-1660937994824.png" alt="deniscollis_0-1660937994824.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Bank-A now always starts at &lt;FONT face="courier new,courier"&gt;0x68000000&amp;nbsp;&lt;/FONT&gt;and&amp;nbsp;Bank-B always starts at &lt;FONT face="courier new,courier"&gt;0x6C000000&amp;nbsp;&lt;/FONT&gt;and it then follows that in the examples above:&lt;/P&gt;&lt;P&gt;2x 32MB dies should have:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Bank-A: 0x68000000-0x69FFFFFF&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-B: 0x6C000000-0x6DFFFFFF&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;and 2x 16MB dies should have:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;Bank-A: 0x68000000-0x68FFFFFF&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Bank-B: 0x6C000000-0x6CFFFFFF&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;...which seems to be the best-practice is you want successful production programming of your products.&lt;/P&gt;&lt;P&gt;Cheers!&lt;BR /&gt;Denis&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2022 20:00:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Best-practice-for-K8x-QSPI-Dual-Quad-Address-Ranges/m-p/1508985#M63858</guid>
      <dc:creator>deniscollis</dc:creator>
      <dc:date>2022-08-19T20:00:28Z</dc:date>
    </item>
  </channel>
</rss>

