<?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: S32K344 MRCANHUBK344 QSPI Example Timeout in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2057901#M46582</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I tried the configurations you mentioned and successfully ran the example. Thank you.&lt;/P&gt;</description>
    <pubDate>Fri, 07 Mar 2025 13:15:53 GMT</pubDate>
    <dc:creator>oguzhan1857</dc:creator>
    <dc:date>2025-03-07T13:15:53Z</dc:date>
    <item>
      <title>S32K344 MRCANHUBK344 QSPI Example Timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2054546#M46368</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I’m currently testing the Qspi_Ip_Example_S32K344 on the MRCANHUBK344 developer board. The example project uses an MX25L6433FM2R-08G flash device, whereas the CANHUB board is equipped with an MX25L6433FM2I-08G. I believe there isn’t any major difference in configuration between these two flash models, and the QSPI pin definitions in the example also seem to match the MRCANHUBK344 QSPI interface.&lt;/P&gt;&lt;P&gt;However, I’m running into an issue where Qspi_Ip_Init returns STATUS_QSPI_IP_BUSY. Everything appears normal until Qspi_Ip_InitProtection is called inside Qspi_Ip_Init, at which point Qspi_Ip_WaitCommandComplete also returns STATUS_QSPI_IP_BUSY (as shown in the attached image).&lt;/P&gt;&lt;P&gt;I’ve come across a similar issue in this forum post:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/S32K/initial-QSPI-will-be-timeout-on-S32K344-EVB/td-p/1900127" target="_self"&gt;initial QSPI will be timeout on S32K344 EVB&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m using S32 Design Studio 3.6 and RTD R21-11 Version 5.0.0. Could anyone advise me on the steps to resolve or further diagnose this issue?&lt;/P&gt;&lt;P&gt;Thank you in advance for your help&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="qspi_timeout.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/326456i65E1868BA48BB526/image-size/medium?v=v2&amp;amp;px=400" role="button" title="qspi_timeout.png" alt="qspi_timeout.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Mar 2025 08:37:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2054546#M46368</guid>
      <dc:creator>oguzhan1857</dc:creator>
      <dc:date>2025-03-03T08:37:11Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 MRCANHUBK344 QSPI Example Timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2054697#M46377</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;devices are the same, there is just temp range difference.&lt;BR /&gt;Pins setting looks correct and matches with schematic, as you wrote. You can check in debugger if respective SIUL registers are written that way.&lt;/P&gt;
&lt;P&gt;Let me check this RTD demo in&amp;nbsp;&lt;SPAN&gt;MRCANHUBK344&amp;nbsp;as well.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;BR, Petr&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Mar 2025 11:55:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2054697#M46377</guid>
      <dc:creator>PetrS</dc:creator>
      <dc:date>2025-03-03T11:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 MRCANHUBK344 QSPI Example Timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2057825#M46572</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I was able to pass init and run code when lowering QSPI_SFCK&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 451px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/327179i866B3C0B8B8FA951/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Also slowing down signal edges helps with example default SFCK (80MHz)&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/327180i99C402D8C0F447DC/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Most probably there is some issue with HW design or similar.&lt;/P&gt;
&lt;P&gt;BR, Petr&lt;/P&gt;
&lt;DIV id="tinyMceEditorPetrS_0" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2025 11:56:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2057825#M46572</guid>
      <dc:creator>PetrS</dc:creator>
      <dc:date>2025-03-07T11:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 MRCANHUBK344 QSPI Example Timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2057901#M46582</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I tried the configurations you mentioned and successfully ran the example. Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2025 13:15:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-MRCANHUBK344-QSPI-Example-Timeout/m-p/2057901#M46582</guid>
      <dc:creator>oguzhan1857</dc:creator>
      <dc:date>2025-03-07T13:15:53Z</dc:date>
    </item>
  </channel>
</rss>

