<?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 iMX DDR Stress Tool source code in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/iMX-DDR-Stress-Tool-source-code/m-p/678008#M104601</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px;"&gt;My customer is accidentally overclocking their iMX6 system LPDDR2. it oddly functions up 30-75MHz over what we're already clocking at. &amp;nbsp;The stress tester is able to change the DDR clock frequencies and by doing that, he can qualify where different parts eventually fail at. &lt;BR /&gt; &lt;BR /&gt;Customer wishes to change nothing in his design.&amp;nbsp; He is trying to figure out how to run the LPDDR2 clock at 333MHz instead of 400MHz, and cannot figure out how to do that.&amp;nbsp; He is looking for the DDR Stress Tool source code as a template as it's apparently able to change the frequencies in 13MHz steps.. &amp;nbsp;I guess simply providing the source to the piece of the stress tester that changes the MMDC clocks is all we need to use as a template&lt;BR /&gt; &lt;BR /&gt; Essentially we need to figure out how to change to make the MMDC output to 333MHz clocking (or close to that) without drastically slowing down the rest of the imx. &amp;nbsp;We do not use the VPU, GPU...etc, just the core and EIM. &amp;nbsp;We'd prefer to not reduce EIM speed if that's possible. &amp;nbsp;Everything seems to be cross dependent on clocks.&lt;/SPAN&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px;"&gt;Gordy Carlson&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px;"&gt;Avnet FAE&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px;"&gt;Upstate NY&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Jun 2017 20:26:08 GMT</pubDate>
    <dc:creator>gcarlson</dc:creator>
    <dc:date>2017-06-07T20:26:08Z</dc:date>
    <item>
      <title>iMX DDR Stress Tool source code</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX-DDR-Stress-Tool-source-code/m-p/678008#M104601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px;"&gt;My customer is accidentally overclocking their iMX6 system LPDDR2. it oddly functions up 30-75MHz over what we're already clocking at. &amp;nbsp;The stress tester is able to change the DDR clock frequencies and by doing that, he can qualify where different parts eventually fail at. &lt;BR /&gt; &lt;BR /&gt;Customer wishes to change nothing in his design.&amp;nbsp; He is trying to figure out how to run the LPDDR2 clock at 333MHz instead of 400MHz, and cannot figure out how to do that.&amp;nbsp; He is looking for the DDR Stress Tool source code as a template as it's apparently able to change the frequencies in 13MHz steps.. &amp;nbsp;I guess simply providing the source to the piece of the stress tester that changes the MMDC clocks is all we need to use as a template&lt;BR /&gt; &lt;BR /&gt; Essentially we need to figure out how to change to make the MMDC output to 333MHz clocking (or close to that) without drastically slowing down the rest of the imx. &amp;nbsp;We do not use the VPU, GPU...etc, just the core and EIM. &amp;nbsp;We'd prefer to not reduce EIM speed if that's possible. &amp;nbsp;Everything seems to be cross dependent on clocks.&lt;/SPAN&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px;"&gt;Gordy Carlson&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px;"&gt;Avnet FAE&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13px;"&gt;Upstate NY&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jun 2017 20:26:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX-DDR-Stress-Tool-source-code/m-p/678008#M104601</guid>
      <dc:creator>gcarlson</dc:creator>
      <dc:date>2017-06-07T20:26:08Z</dc:date>
    </item>
    <item>
      <title>Re: iMX DDR Stress Tool source code</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX-DDR-Stress-Tool-source-code/m-p/678009#M104602</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;&amp;nbsp; DDR Stress Test sources are not provided. You may use&amp;nbsp; Linux codes,&lt;/P&gt;&lt;P&gt;supporting CPUFREQ feature and Dynamic Bus Frequency driver.&lt;/P&gt;&lt;P&gt;Please refer to i.MX Linux® Reference Manual for more details.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Yuri&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jun 2017 02:44:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX-DDR-Stress-Tool-source-code/m-p/678009#M104602</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2017-06-08T02:44:57Z</dc:date>
    </item>
  </channel>
</rss>

