<?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: FlexSPI Cache Issue</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310160#M15367</link>
    <description>&lt;P&gt;The FPGA is acting more like a RAM than a flash device. FlexSPI port B1 is configured to communicate with the FPGA, using custom LUT entries to match the bus characteristics that I'm expecting on the FPGA side. I am only using AHB-accesses, no IP comms.&lt;/P&gt;&lt;P&gt;The transactions work properly (all of the FlexSPI parameters are set-up properly for both write and read accesses). The issue is that I can't reliably cause a read on the QSPI. Even though I have cache disabled for the FPGA's memory region, and even if I completely disable D-Cache, a read in software doesn't cause a read on the FlexSPI.&lt;/P&gt;&lt;P&gt;I appreciate your help with this issue.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jul 2021 03:25:08 GMT</pubDate>
    <dc:creator>whermann</dc:creator>
    <dc:date>2021-07-20T03:25:08Z</dc:date>
    <item>
      <title>FlexSPI Cache Issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310069#M15358</link>
      <description>&lt;P&gt;I have an i.MXRT1011 connected to an FPGA via QSPI using the FlexSPI module. I have the entire FPGA memory region configured as non-cacheable in the MPU, as I want any access to that region to cause an SPI transaction:&lt;/P&gt;&lt;LI-CODE lang="c"&gt;ARM_MPU_SetRegionEx(0, 0x61000000, ARM_MPU_RASR(0, ARM_MPU_AP_FULL, 1, 0, 0, 0, 0, ARM_MPU_REGION_SIZE_64KB));&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When attempting to access this memory region, I find that writes do consistently cause SPI transactions, but reads do not:&lt;/P&gt;&lt;LI-CODE lang="c"&gt;volatile uint8_t *fpgaReg = (volatile uint8_t *)(FPGA_AHB_START_ADDRESS + 0x2000);
uint8_t rdVal = 0;

*fpgaReg = (uint8_t)(i);    // writes cause SPI transaction
rdVal = *fpgaReg;           // reads only cause an SPI transaction on first pass&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've tried both disabling the data cache, and invalidating the region I'm accessing before doing the read, but still no bus action. I figure I must be missing something about the CM7 cache but I'm not having any luck figuring it out.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jul 2021 22:08:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310069#M15358</guid>
      <dc:creator>whermann</dc:creator>
      <dc:date>2021-07-19T22:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: FlexSPI Cache Issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310136#M15364</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.&lt;BR /&gt;Actually, I'm a bit confused with your design, whether you use an FPGA to simulate the QSPI flash, if not, can you share the schematic of the custom board?&lt;BR /&gt;Looking forward to your reply.&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;
&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jul 2021 02:46:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310136#M15364</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2021-07-20T02:46:20Z</dc:date>
    </item>
    <item>
      <title>Re: FlexSPI Cache Issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310160#M15367</link>
      <description>&lt;P&gt;The FPGA is acting more like a RAM than a flash device. FlexSPI port B1 is configured to communicate with the FPGA, using custom LUT entries to match the bus characteristics that I'm expecting on the FPGA side. I am only using AHB-accesses, no IP comms.&lt;/P&gt;&lt;P&gt;The transactions work properly (all of the FlexSPI parameters are set-up properly for both write and read accesses). The issue is that I can't reliably cause a read on the QSPI. Even though I have cache disabled for the FPGA's memory region, and even if I completely disable D-Cache, a read in software doesn't cause a read on the FlexSPI.&lt;/P&gt;&lt;P&gt;I appreciate your help with this issue.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jul 2021 03:25:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310160#M15367</guid>
      <dc:creator>whermann</dc:creator>
      <dc:date>2021-07-20T03:25:08Z</dc:date>
    </item>
    <item>
      <title>Re: FlexSPI Cache Issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310384#M15372</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Thanks for your reply.&lt;BR /&gt;According to your reply, in your design, the FlexSPI port A connects the QSPI, meanwhile, the FlexSPI port B connects the FPGA.&lt;BR /&gt;In the application, you want to read and write the FPGA via AHB access mode, isn't my understanding right?&lt;BR /&gt;If yes, I was wondering if you can upload your demo code?&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;
&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jul 2021 10:23:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1310384#M15372</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2021-07-20T10:23:17Z</dc:date>
    </item>
    <item>
      <title>Re: FlexSPI Cache Issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1311516#M15410</link>
      <description>&lt;P&gt;I figured out the issue. The FlexSPI module has the ability to check its own TX buffer for a cache hit when doing a read. Clearing the AHBCR[CACHABLEEN] bit disables this feature, so every AHB read from the FlexSPI memory space will cause a SPI transaction.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jul 2021 21:20:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1311516#M15410</guid>
      <dc:creator>whermann</dc:creator>
      <dc:date>2021-07-21T21:20:19Z</dc:date>
    </item>
    <item>
      <title>Re: FlexSPI Cache Issue</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1477943#M20210</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Could you share your config on flexspi?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 07:45:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FlexSPI-Cache-Issue/m-p/1477943#M20210</guid>
      <dc:creator>jingyangxie</dc:creator>
      <dc:date>2022-06-22T07:45:10Z</dc:date>
    </item>
  </channel>
</rss>

