<?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: DDR3 calibration failed in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486187#M77781</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case how can we booting Linux kernel or even Freescale SDK?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Apr 2016 08:53:23 GMT</pubDate>
    <dc:creator>letan</dc:creator>
    <dc:date>2016-04-07T08:53:23Z</dc:date>
    <item>
      <title>DDR3 calibration failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486185#M77779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We designed our custom board which is using i.MX6Dual(&lt;SPAN style="color: #ff0000;"&gt;MCIMX6D5EYM10AD) &lt;SPAN style="color: #000000;"&gt;with only ONE DDR3(&lt;SPAN style="color: #ff0000;"&gt;MT41K512M16HA) &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="1" cellpadding="2" cellspacing="2" height="112" width="1287"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;STRONG&gt;Steps&lt;/STRONG&gt;&lt;BR /&gt; &lt;/TD&gt;&lt;TD valign="top"&gt;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;BR /&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;STRONG&gt;1. 32bit read/write&lt;/STRONG&gt;&lt;BR /&gt; &lt;/TD&gt;&lt;TD valign="top"&gt;I can write then read the data into any random address on DDR3 exactly&lt;BR /&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;STRONG&gt;2. Calibration&lt;BR /&gt; &lt;/STRONG&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;But when I calibrate with &lt;STRONG&gt;528MHz&lt;/STRONG&gt;, even &lt;STRONG&gt;297MHz&lt;/STRONG&gt;. It failed as the attached log&lt;BR /&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD valign="top"&gt;&lt;STRONG&gt;3. Calibration&lt;BR /&gt; &lt;/STRONG&gt;&lt;/TD&gt;&lt;TD valign="top"&gt;Then I changed the DSE value to 34/40/48 but it failed as the same log&lt;BR /&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the log shows FAILED&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;Calibration will run at DDR frequency 528MHz. Type 'y' to continue.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;If you want to run at other DDR frequency. Type 'n'&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;&amp;nbsp; DDR Freq: 528 MHz&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;Would you like to run the write leveling calibration? (y/n)&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;&amp;nbsp; Please enter the MR1 value on the initilization script&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;&amp;nbsp; This will be re-programmed into MR1 after write leveling calibration&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;&amp;nbsp; Enter as a 4-digit HEX value, example 0004, then hit enter&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;0004 You have entered: 0x0004&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;Start write leveling calibration&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;Write leveling calibration completed&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;MMDC_MPWLDECTRL0 ch0 after write level cal: 0x001F001F&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;MMDC_MPWLDECTRL1 ch0 after write level cal: 0x001F001F&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;Would you like to run the DQS gating, read/write delay calibration? (y/n)&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;Starting DQS gating calibration...&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;. . . . . . . . . . . . . . ERROR FOUND, we can't get suitable value !!!!&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;&lt;STRONG&gt;dram test fails for all values.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 07:00:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486185#M77779</guid>
      <dc:creator>letan</dc:creator>
      <dc:date>2016-04-07T07:00:48Z</dc:date>
    </item>
    <item>
      <title>Re: DDR3 calibration failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486186#M77780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Le&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if all other tests passed, one can skip dqs gating calibration.&lt;/P&gt;&lt;P&gt;This may be caused by the hardware layout causing much noise between traces. &lt;/P&gt;&lt;P&gt;Background can be found on&lt;/P&gt;&lt;P&gt;p.22 Application Note AN4467 (Rev. 0, 10/2012) "i.MX 6 Series DDR Calibration"&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.freescale.com%2Ffiles%2F32bit%2Fdoc%2Fapp_note%2FAN4467.pdf" rel="nofollow" target="_blank"&gt;http://www.freescale.com/files/32bit/doc/app_note/AN4467.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"..as a proper DQS gating delay result. For i.MX 6 Series, however, the too-early&lt;/P&gt;&lt;P&gt;boundary detection was occasionally found to return wrong values (of 0 or 1 delay unit) using the hardware&lt;/P&gt;&lt;P&gt;calibration method. In these cases, the average value automatically placed in MMDC0/1_MPDGCTRLx&lt;/P&gt;&lt;P&gt;is thus also wrong. If using the hardware DQS Gating calibration sequence, it is the user’s responsibility&lt;/P&gt;&lt;P&gt;then to take the too-late boundary value, subtract a 3/4 cycle delay value, and write it to&lt;/P&gt;&lt;P&gt;MMDC0/1_MPDGCTRLx."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 08:03:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486186#M77780</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-04-07T08:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: DDR3 calibration failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486187#M77781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case how can we booting Linux kernel or even Freescale SDK?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 08:53:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486187#M77781</guid>
      <dc:creator>letan</dc:creator>
      <dc:date>2016-04-07T08:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: DDR3 calibration failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486188#M77782</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Le&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 09:41:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/486188#M77782</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-04-07T09:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: DDR3 calibration failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/1170642#M163766</link>
      <description>&lt;P&gt;I have the same problem with the same DDR3 chip but the imx6 solo CPU. If pre-defined pattern is used, the hardware read&amp;nbsp; DQS gating calibration return a hardware error, if predefined value is used, the hardware automatic calibration never stoped, that is, the HW_DG_EN bit is always 1 "1".&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2020 02:55:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/DDR3-calibration-failed/m-p/1170642#M163766</guid>
      <dc:creator>hailiu</dc:creator>
      <dc:date>2020-10-21T02:55:21Z</dc:date>
    </item>
  </channel>
</rss>

