<?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 System hangs with simultaneous QSPI file access and XiP execution  in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/System-hangs-with-simultaneous-QSPI-file-access-and-XiP/m-p/881270#M52266</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a K8x with a single-die 16MB QSPI flash module.&amp;nbsp; The QSPI memory layout is arranged with a section for XiP code, and another section for a file system.&amp;nbsp; If a function in internal flash accesses the file system, then everything works fine. Functions on external flash that do not access the file system also run without a problem.&amp;nbsp; However, if a function on QSPI flash attempts to access the file system, also on QSPI flash, then the system hangs.&amp;nbsp; In the debugger I see that the QSPI busy bit (BOARD_QSPI_BASE-&amp;gt;SR &amp;amp; QuadSPI_SR_BUSY_MASK) remains set, forever.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can this be overcome?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Apr 2019 01:10:51 GMT</pubDate>
    <dc:creator>deniscollis</dc:creator>
    <dc:date>2019-04-05T01:10:51Z</dc:date>
    <item>
      <title>System hangs with simultaneous QSPI file access and XiP execution</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/System-hangs-with-simultaneous-QSPI-file-access-and-XiP/m-p/881270#M52266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a K8x with a single-die 16MB QSPI flash module.&amp;nbsp; The QSPI memory layout is arranged with a section for XiP code, and another section for a file system.&amp;nbsp; If a function in internal flash accesses the file system, then everything works fine. Functions on external flash that do not access the file system also run without a problem.&amp;nbsp; However, if a function on QSPI flash attempts to access the file system, also on QSPI flash, then the system hangs.&amp;nbsp; In the debugger I see that the QSPI busy bit (BOARD_QSPI_BASE-&amp;gt;SR &amp;amp; QuadSPI_SR_BUSY_MASK) remains set, forever.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can this be overcome?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Apr 2019 01:10:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/System-hangs-with-simultaneous-QSPI-file-access-and-XiP/m-p/881270#M52266</guid>
      <dc:creator>deniscollis</dc:creator>
      <dc:date>2019-04-05T01:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: System hangs with simultaneous QSPI file access and XiP execution</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/System-hangs-with-simultaneous-QSPI-file-access-and-XiP/m-p/881271#M52267</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Denis,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately, what you are trying to do is not possible. Accessing the file system at the same time the code is running from the QSPI memory it is a limitation of XiP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For implementing this you will have to execute the function from internal flash or either copy the function to ram and execute it from there.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Felipe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Apr 2019 17:00:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/System-hangs-with-simultaneous-QSPI-file-access-and-XiP/m-p/881271#M52267</guid>
      <dc:creator>FelipeGarcia</dc:creator>
      <dc:date>2019-04-08T17:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: System hangs with simultaneous QSPI file access and XiP execution</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/System-hangs-with-simultaneous-QSPI-file-access-and-XiP/m-p/881272#M52268</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;Felipe,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found a similar discussion -&amp;nbsp;&lt;A _jive_internal="true" href="https://community.nxp.com/thread/464926"&gt;RT1050 QSPI Flash Limitations&lt;/A&gt;&amp;nbsp;-&amp;nbsp;which confirms your answer.&amp;nbsp; I'm assuming that memory-mapped reads from the file-system will be okay, and it's just the functions that control erase- and write-cycles that must be located in RAM or internal flash.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Denis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Apr 2019 17:36:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/System-hangs-with-simultaneous-QSPI-file-access-and-XiP/m-p/881272#M52268</guid>
      <dc:creator>deniscollis</dc:creator>
      <dc:date>2019-04-08T17:36:35Z</dc:date>
    </item>
  </channel>
</rss>

