<?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 HyperRAM stability issue with 528MHz core in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/HyperRAM-stability-issue-with-528MHz-core/m-p/1540157#M22102</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We just changed our RT1064 part from the 600MHz variety to the 528MHz one.&lt;/P&gt;&lt;P&gt;On the 600MHz part we had HyperRAM running happily at 216MHz for the past year.&lt;/P&gt;&lt;P&gt;We've changed the clock setup to both the old a new (as we use the same binary) to 528MHz.&lt;/P&gt;&lt;P&gt;Now the HyperRAM isn't working at even 200MHz on old (600MHz, now clocked at 528) part. Core locks up as soon as the hyper RAM is accessed. We've had to back it off to 182MHz.&lt;/P&gt;&lt;P&gt;Is there some weird clock phasing issue between the core and FlexSPI peripheral?&lt;/P&gt;&lt;P&gt;To get 528MHz the ARM PLL was changed from *50 to *44.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the current (working) setting:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="p_shep_0-1666190392757.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/197303i82DCD0E5C8EF6E81/image-size/medium?v=v2&amp;amp;px=400" role="button" title="p_shep_0-1666190392757.png" alt="p_shep_0-1666190392757.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;p_shep_0-1666190392757.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Changing PLL2_PFD2 to /24 will cause the instability.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas as to what the problem my be?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 19 Oct 2022 14:41:49 GMT</pubDate>
    <dc:creator>p_shep</dc:creator>
    <dc:date>2022-10-19T14:41:49Z</dc:date>
    <item>
      <title>HyperRAM stability issue with 528MHz core</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/HyperRAM-stability-issue-with-528MHz-core/m-p/1540157#M22102</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We just changed our RT1064 part from the 600MHz variety to the 528MHz one.&lt;/P&gt;&lt;P&gt;On the 600MHz part we had HyperRAM running happily at 216MHz for the past year.&lt;/P&gt;&lt;P&gt;We've changed the clock setup to both the old a new (as we use the same binary) to 528MHz.&lt;/P&gt;&lt;P&gt;Now the HyperRAM isn't working at even 200MHz on old (600MHz, now clocked at 528) part. Core locks up as soon as the hyper RAM is accessed. We've had to back it off to 182MHz.&lt;/P&gt;&lt;P&gt;Is there some weird clock phasing issue between the core and FlexSPI peripheral?&lt;/P&gt;&lt;P&gt;To get 528MHz the ARM PLL was changed from *50 to *44.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the current (working) setting:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="p_shep_0-1666190392757.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/197303i82DCD0E5C8EF6E81/image-size/medium?v=v2&amp;amp;px=400" role="button" title="p_shep_0-1666190392757.png" alt="p_shep_0-1666190392757.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;p_shep_0-1666190392757.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Changing PLL2_PFD2 to /24 will cause the instability.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas as to what the problem my be?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Oct 2022 14:41:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/HyperRAM-stability-issue-with-528MHz-core/m-p/1540157#M22102</guid>
      <dc:creator>p_shep</dc:creator>
      <dc:date>2022-10-19T14:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: HyperRAM stability issue with 528MHz core</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/HyperRAM-stability-issue-with-528MHz-core/m-p/1541557#M22155</link>
      <description>&lt;P&gt;It is interesting finding.&lt;/P&gt;
&lt;P&gt;You use 'PLL2_PFD2 to /22' in 600MHz RT1064 variety, and 216MHz HyperRAM is working properly?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2022 03:09:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/HyperRAM-stability-issue-with-528MHz-core/m-p/1541557#M22155</guid>
      <dc:creator>jay_heng</dc:creator>
      <dc:date>2022-10-21T03:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: HyperRAM stability issue with 528MHz core</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/HyperRAM-stability-issue-with-528MHz-core/m-p/1541958#M22170</link>
      <description>&lt;P&gt;Correct, that the way we've been using the Cypress part for the last year - so overclocked a little.&lt;/P&gt;&lt;P&gt;Now with the changed core clock (from 600-&amp;gt;528), the HyperRAM doesn't even work at the rated 200MHz (well, 198MHz, as it works out).&lt;/P&gt;&lt;P&gt;Further curiosity is that after boot-looping for anywhere from a couple of times to 30 mins later, it'll eventually spring into life and work fine.&lt;/P&gt;&lt;P&gt;On our new devices, not only is the RT1064 changed, but so is the HyperRAM to a winbond part. Initially we thought it was less tolerant refusing to work at 216MHz. But after making the same software clock changes to the old devices, we found the same issues.&lt;/P&gt;&lt;P&gt;Very odd indeed.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Oct 2022 11:43:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/HyperRAM-stability-issue-with-528MHz-core/m-p/1541958#M22170</guid>
      <dc:creator>p_shep</dc:creator>
      <dc:date>2022-10-21T11:43:40Z</dc:date>
    </item>
  </channel>
</rss>

