<?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>i.MX RT Crossover MCUs中的主题 Re: Using QSPI Flash for MIMXRT555 developement</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-QSPI-Flash-for-MIMXRT555-developement/m-p/1879389#M30703</link>
    <description>&lt;P&gt;Thank you for your response &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/203261"&gt;@Gavin_Jia&lt;/a&gt;!&lt;/P&gt;&lt;P&gt;One of our &lt;EM&gt;RT595_EVK&lt;/EM&gt; boards is already configured to be used with QSPI Flash. Hardware modifications and boot setup were also applied and tested with &lt;EM&gt;MCUxpresso&lt;/EM&gt; hello world sample running from the QSPI.&lt;/P&gt;&lt;P&gt;I cannot find any DTS node in the Zephyr source code for the QSPI Flash installed on the evaluation kit (&lt;EM&gt;IS25WP064AJBLE&lt;/EM&gt;), and the driver (&lt;EM&gt;flash_mcux_flexspi_nor.c&lt;/EM&gt;) seems to only enable quad mode for MX25 family of Flash chips base on runtime detection: &lt;A href="https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/flash/flash_mcux_flexspi_nor.c#L890C23-L890C24" target="_blank" rel="noopener"&gt;https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/flash/flash_mcux_flexspi_nor.c#L890C23-L890C24.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Even if boot-related configuration would be enough for the code to run in the XIP mode, any feature requiring access to Flash memory in our application (e.g. storage and DFU, or not using XIP mode) seems to be impossible without adding DTS node, and performance would be impacted without modifying the driver.&lt;/P&gt;&lt;P&gt;Is there anything that we are missing? Right now we're looking into replacing the QSPI Flash on the evaluation kit with one of the &lt;EM&gt;Macronix &lt;/EM&gt;Flash memories, that seem to be supported, as this is the memory that we are going to use on our custom PCB.&lt;/P&gt;&lt;P&gt;With regards&lt;/P&gt;</description>
    <pubDate>Mon, 03 Jun 2024 04:02:42 GMT</pubDate>
    <dc:creator>GR-Grinn</dc:creator>
    <dc:date>2024-06-03T04:02:42Z</dc:date>
    <item>
      <title>Using QSPI Flash for MIMXRT555 developement</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-QSPI-Flash-for-MIMXRT555-developement/m-p/1876284#M30618</link>
      <description>&lt;P&gt;Hi!&lt;BR /&gt;&lt;BR /&gt;We want to use&lt;EM&gt; MIMXRT555SFAWCR&lt;/EM&gt; in a product based on Zephyr RTOS. To start development we're using &lt;LI-PRODUCT title="MIMXRT595-EVK" id="MIMXRT595-EVK"&gt;&lt;/LI-PRODUCT&gt;.&lt;/P&gt;&lt;P&gt;Given the lack of all OSPI signals in the selected MCU we're forced to use QSPI Flash memory. Even if we switch the EVK to QSPI Flash there seem to be no support for it in the Zephyr. &lt;EM&gt;MCUXpresso &lt;/EM&gt;also does not seem to have a lot of support for this use case.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;What is the suggested way of developing application for &lt;EM&gt;MIMXRT555SFAWCR&lt;/EM&gt; using the only available MIMXRT500 family development kit: &lt;LI-PRODUCT title="MIMXRT595-EVK" id="MIMXRT595-EVK"&gt;&lt;/LI-PRODUCT&gt;?&lt;/LI&gt;&lt;LI&gt;Is it even possible to use QSPI Flash memory under Zephyr?&lt;/LI&gt;&lt;LI&gt;Are there any additional materials that we can reference during development regarding QSPI usage and configuration?&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Tue, 28 May 2024 11:24:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-QSPI-Flash-for-MIMXRT555-developement/m-p/1876284#M30618</guid>
      <dc:creator>GR-Grinn</dc:creator>
      <dc:date>2024-05-28T11:24:43Z</dc:date>
    </item>
    <item>
      <title>回复： Using QSPI Flash for MIMXRT555 developement</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-QSPI-Flash-for-MIMXRT555-developement/m-p/1877164#M30642</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/234197"&gt;@GR-Grinn&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;First of all, although there is no more information available, it is possible to develop using QSPI Flash in Zephyr. For more information on how to use QSPI Flash on the RT595_EVK, NXP provides this document for reference:&amp;nbsp;&lt;A href="https://www.nxp.com/docs/en/application-note/AN13304.pdf" target="_blank"&gt;Boot from QSPI Flash on MIMXRT595-EVK (nxp.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If your board runs according to this documentation, then it's time to try the Zephyr project. It hasn't been verified, but my guess is that the required changes on the software side are essentially the same.（FDCB header\FlexSPI frequency\Flash Driver）&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Gavin&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 09:48:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-QSPI-Flash-for-MIMXRT555-developement/m-p/1877164#M30642</guid>
      <dc:creator>Gavin_Jia</dc:creator>
      <dc:date>2024-05-29T09:48:17Z</dc:date>
    </item>
    <item>
      <title>Re: Using QSPI Flash for MIMXRT555 developement</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-QSPI-Flash-for-MIMXRT555-developement/m-p/1879389#M30703</link>
      <description>&lt;P&gt;Thank you for your response &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/203261"&gt;@Gavin_Jia&lt;/a&gt;!&lt;/P&gt;&lt;P&gt;One of our &lt;EM&gt;RT595_EVK&lt;/EM&gt; boards is already configured to be used with QSPI Flash. Hardware modifications and boot setup were also applied and tested with &lt;EM&gt;MCUxpresso&lt;/EM&gt; hello world sample running from the QSPI.&lt;/P&gt;&lt;P&gt;I cannot find any DTS node in the Zephyr source code for the QSPI Flash installed on the evaluation kit (&lt;EM&gt;IS25WP064AJBLE&lt;/EM&gt;), and the driver (&lt;EM&gt;flash_mcux_flexspi_nor.c&lt;/EM&gt;) seems to only enable quad mode for MX25 family of Flash chips base on runtime detection: &lt;A href="https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/flash/flash_mcux_flexspi_nor.c#L890C23-L890C24" target="_blank" rel="noopener"&gt;https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/flash/flash_mcux_flexspi_nor.c#L890C23-L890C24.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Even if boot-related configuration would be enough for the code to run in the XIP mode, any feature requiring access to Flash memory in our application (e.g. storage and DFU, or not using XIP mode) seems to be impossible without adding DTS node, and performance would be impacted without modifying the driver.&lt;/P&gt;&lt;P&gt;Is there anything that we are missing? Right now we're looking into replacing the QSPI Flash on the evaluation kit with one of the &lt;EM&gt;Macronix &lt;/EM&gt;Flash memories, that seem to be supported, as this is the memory that we are going to use on our custom PCB.&lt;/P&gt;&lt;P&gt;With regards&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2024 04:02:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Using-QSPI-Flash-for-MIMXRT555-developement/m-p/1879389#M30703</guid>
      <dc:creator>GR-Grinn</dc:creator>
      <dc:date>2024-06-03T04:02:42Z</dc:date>
    </item>
  </channel>
</rss>

