<?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 Qspi_Ip_Example Qspi_Ip_Init timeout in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1643576#M22564</link>
    <description>&lt;P&gt;I will try to test it on my side. In the meanwhile I would like to ask whether you have tried newer version of S32DS or RTD?&lt;/P&gt;
&lt;P&gt;Described behavior is interesting, I am not sure if consider it rather as HW or SW issue.&lt;/P&gt;</description>
    <pubDate>Wed, 03 May 2023 11:17:35 GMT</pubDate>
    <dc:creator>davidtosenovjan</dc:creator>
    <dc:date>2023-05-03T11:17:35Z</dc:date>
    <item>
      <title>S32K344 Qspi_Ip_Example Qspi_Ip_Init timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1637428#M22282</link>
      <description>&lt;P&gt;I'm working on the&amp;nbsp;S32K344 Qspi_Ip_Example for&amp;nbsp;S32K3XXEVB-Q172 51972 PCB RevA SCH RevA board.&amp;nbsp;Qspi_Ip_Example_S32K344_Debug_FLASH_PNE is used as debug configuration. After running,&lt;/P&gt;&lt;P&gt;&lt;FONT color="#0000FF"&gt;Qspi_Ip_Init(instance, &amp;amp;QspiConfigSet_VS_0_paFlashCfg[0], &amp;amp;QspiConfigSet_VS_0_paFlashConnectionCfg[0]); &lt;FONT color="#000000"&gt;in the main file&amp;nbsp;gets timeout.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;I'm using S32 DS 3.4 and RTD SW version&amp;nbsp;2.0.0, build vresion S32K3_RTD_2_0_0_D2203_ASR_REL_4_4_REV_0000_20220331&lt;/P&gt;</description>
      <pubDate>Thu, 20 Apr 2023 16:46:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1637428#M22282</guid>
      <dc:creator>Li_Chen</dc:creator>
      <dc:date>2023-04-20T16:46:31Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 Qspi_Ip_Example Qspi_Ip_Init timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1638052#M22306</link>
      <description>&lt;P&gt;Could you provide example code showing the issue, letting us to the debug it? Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2023 12:38:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1638052#M22306</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-04-21T12:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 Qspi_Ip_Example Qspi_Ip_Init timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1638167#M22313</link>
      <description>&lt;P&gt;It's generated by IDE. I attached the main file here. Here are my further progress, I tested three S32K3x4EVB-Q172 boards, only one could pass the test. The others are stuck in the&amp;nbsp; Qspi_Ip_Init function and eventually timeout&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2023 16:04:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1638167#M22313</guid>
      <dc:creator>Li_Chen</dc:creator>
      <dc:date>2023-04-21T16:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 Qspi_Ip_Example Qspi_Ip_Init timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1640462#M22399</link>
      <description>&lt;P&gt;Are all these used board of same revision?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 10:00:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1640462#M22399</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-04-26T10:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 Qspi_Ip_Example Qspi_Ip_Init timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1640761#M22414</link>
      <description>&lt;P&gt;They are the same revision: 700-51972 REV A.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 16:35:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1640761#M22414</guid>
      <dc:creator>Li_Chen</dc:creator>
      <dc:date>2023-04-26T16:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 Qspi_Ip_Example Qspi_Ip_Init timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1643576#M22564</link>
      <description>&lt;P&gt;I will try to test it on my side. In the meanwhile I would like to ask whether you have tried newer version of S32DS or RTD?&lt;/P&gt;
&lt;P&gt;Described behavior is interesting, I am not sure if consider it rather as HW or SW issue.&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2023 11:17:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1643576#M22564</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-05-03T11:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 Qspi_Ip_Example Qspi_Ip_Init timeout</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1643656#M22571</link>
      <description>&lt;P&gt;On my side it runs normally. I will try to ask whether they are known issues with this board or this SW example configuration.&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2023 14:13:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-Qspi-Ip-Example-Qspi-Ip-Init-timeout/m-p/1643656#M22571</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-05-03T14:13:10Z</dc:date>
    </item>
  </channel>
</rss>

