<?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: Using 32M flash in i.mxrt1062 in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-32M-flash-in-i-mxrt1062/m-p/2351884#M36492</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/254481"&gt;@AndrewChoi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks for your interest in NXP MIMXRT series!&lt;/P&gt;
&lt;P&gt;The FlexSPI address space of the i.MX RT1062 inherently supports QSPI NOR flash memory larger than 16 MB. However, the publicly available MCUXpresso component code is primarily tailored to the flash memory used on the official EVK. Therefore, no code specific to 4-byte addressing is provided. &lt;BR /&gt;Customers should perform joint adaptation and verification of the FCB, LUT, flashloader/download algorithms, and boundary access beyond 16 MB based on the specific Flash.&lt;/P&gt;
&lt;P&gt;Unfortunately, there are currently no plans to release an official SDK that supports this feature. We apologize for any inconvenience this may cause. You can also find more details provided by developers in this thread:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Add-4-byte-addressing-to-FLEXSPI-flash-driver/m-p/1093750" target="_blank"&gt;https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Add-4-byte-addressing-to-FLEXSPI-flash-driver/m-p/1093750&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Gavin&lt;/P&gt;</description>
    <pubDate>Thu, 16 Apr 2026 02:53:39 GMT</pubDate>
    <dc:creator>Gavin_Jia</dc:creator>
    <dc:date>2026-04-16T02:53:39Z</dc:date>
    <item>
      <title>Using 32M flash in i.mxrt1062</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-32M-flash-in-i-mxrt1062/m-p/2351179#M36488</link>
      <description>&lt;P&gt;Hello All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My customer is using 32M flash on i.mxrt1062.&lt;/P&gt;&lt;P&gt;I confirmed in a previous post that 32M support is available.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/QSPI-Flash-Size-MIMXRT1062/m-p/2193977#M35489" target="_blank"&gt;https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/QSPI-Flash-Size-MIMXRT1062/m-p/2193977#M35489&lt;/A&gt;&lt;/P&gt;&lt;P&gt;And,&lt;BR /&gt;&lt;A href="https://github.com/nxp-mcuxpresso/mcux-component/blob/release/26.03.00/flash/mflash/mimxrt1160/mflash_drv.c" target="_blank"&gt;https://github.com/nxp-mcuxpresso/mcux-component/blob/release/26.03.00/flash/mflash/mimxrt1160/mflash_drv.c&lt;/A&gt;&lt;/P&gt;&lt;P&gt;it was confirmed that the addressing is set to 3 bytes,&lt;/P&gt;&lt;P&gt;LEXSPI_LUT_SEQ(&lt;/P&gt;&lt;P&gt;kFLEXSPI_Command_SDR, kFLEXSPI_1PAD, 0x03,&lt;/P&gt;&lt;P&gt;kFLEXSPI_Command_RADDR_SDR, kFLEXSPI_1PAD, 0x18&lt;BR /&gt;)&lt;/P&gt;&lt;P&gt;so the customer is currently using a modified file.&lt;/P&gt;&lt;P&gt;Please let me know if NXP has any plans or schedules for officially supporting 4-byte addressing.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2026 06:39:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-32M-flash-in-i-mxrt1062/m-p/2351179#M36488</guid>
      <dc:creator>AndrewChoi</dc:creator>
      <dc:date>2026-04-15T06:39:02Z</dc:date>
    </item>
    <item>
      <title>Re: Using 32M flash in i.mxrt1062</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-32M-flash-in-i-mxrt1062/m-p/2351884#M36492</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/254481"&gt;@AndrewChoi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks for your interest in NXP MIMXRT series!&lt;/P&gt;
&lt;P&gt;The FlexSPI address space of the i.MX RT1062 inherently supports QSPI NOR flash memory larger than 16 MB. However, the publicly available MCUXpresso component code is primarily tailored to the flash memory used on the official EVK. Therefore, no code specific to 4-byte addressing is provided. &lt;BR /&gt;Customers should perform joint adaptation and verification of the FCB, LUT, flashloader/download algorithms, and boundary access beyond 16 MB based on the specific Flash.&lt;/P&gt;
&lt;P&gt;Unfortunately, there are currently no plans to release an official SDK that supports this feature. We apologize for any inconvenience this may cause. You can also find more details provided by developers in this thread:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Add-4-byte-addressing-to-FLEXSPI-flash-driver/m-p/1093750" target="_blank"&gt;https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Add-4-byte-addressing-to-FLEXSPI-flash-driver/m-p/1093750&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Gavin&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2026 02:53:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-32M-flash-in-i-mxrt1062/m-p/2351884#M36492</guid>
      <dc:creator>Gavin_Jia</dc:creator>
      <dc:date>2026-04-16T02:53:39Z</dc:date>
    </item>
  </channel>
</rss>

