<?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 FlexSPI layout guidelines  in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/FlexSPI-layout-guidelines/m-p/1060614#M155956</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;HI NXP Team,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;We are using i.MX8DualXPLUS processor in our custom platform development based on the MEK.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Please recommend some good reference document/link for the FlexSPI Octal interface layout guidelines.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Aug 2020 11:52:48 GMT</pubDate>
    <dc:creator>harsh_mistry</dc:creator>
    <dc:date>2020-08-04T11:52:48Z</dc:date>
    <item>
      <title>FlexSPI layout guidelines</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/FlexSPI-layout-guidelines/m-p/1060614#M155956</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;HI NXP Team,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;We are using i.MX8DualXPLUS processor in our custom platform development based on the MEK.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Please recommend some good reference document/link for the FlexSPI Octal interface layout guidelines.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2020 11:52:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/FlexSPI-layout-guidelines/m-p/1060614#M155956</guid>
      <dc:creator>harsh_mistry</dc:creator>
      <dc:date>2020-08-04T11:52:48Z</dc:date>
    </item>
    <item>
      <title>Re: FlexSPI layout guidelines</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/FlexSPI-layout-guidelines/m-p/1060615#M155957</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The complete Guidelines for the i.MX8X are available in the following link:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/webapp/Download?colCode=IMX8HWDG" title="https://www.nxp.com/webapp/Download?colCode=IMX8HWDG"&gt;https://www.nxp.com/webapp/Download?colCode=IMX8HWDG&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the FlexSPI module,&amp;nbsp; I would said the basic guideline it is to have the data lines and clock in differential pair, to obtain a maximum performance and distance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2020 22:17:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/FlexSPI-layout-guidelines/m-p/1060615#M155957</guid>
      <dc:creator>jamesbone</dc:creator>
      <dc:date>2020-08-04T22:17:25Z</dc:date>
    </item>
  </channel>
</rss>

