<?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: Dependency of tCL and tCWL values on custom hardware performance ? in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Dependency-of-tCL-and-tCWL-values-on-custom-hardware-performance/m-p/788434#M122176</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Hello,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Look at my comments below.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;I. &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; From practical point of view&amp;nbsp; - it makes sense to modify / setup some MMDC registers &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;in initialization script after memory calibration, using its results. In Your case:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&amp;nbsp; MMDC registers updated from calibration &lt;BR /&gt;&amp;nbsp;&amp;nbsp; Write leveling calibration&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MMDC_MPWLDECTRL0 ch0 (0x021b080c) = 0x0018001E&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MMDC_MPWLDECTRL1 ch0 (0x021b0810) = 0x0028001A&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MMDC_MPWLDECTRL0 ch1 (0x021b480c) = 0x001A0025&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MMDC_MPWLDECTRL1 ch1 (0x021b4810) = 0x0014001E&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Read DQS Gating calibration&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPDGCTRL0 PHY0 (0x021b083c) = 0x02580258&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPDGCTRL1 PHY0 (0x021b0840) = 0x024C0250&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPDGCTRL0 PHY1 (0x021b483c) = 0x02600268&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPDGCTRL1 PHY1 (0x021b4840) = 0x02500230&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&amp;nbsp; Read calibration&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPRDDLCTL PHY0 (0x021b0848) = 0x423A3A3C&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPRDDLCTL PHY1 (0x021b4848) = 0x3A383842&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Write calibration&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPWRDLCTL PHY0 (0x021b0850) = 0x3A3A403C&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPWRDLCTL PHY1 (0x021b4850) = 0x403A403A&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;If overnight test with new initialization parameters is OK - the found parameters are good &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;candidates for final release. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;II.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; tCL&amp;nbsp; and tCWL should be the same for i.MX6 MMDC and DDR3 (AS4C256M16D3A). &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;III. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; Please verify PCB design, using Excel page named “MX6 DRAM Bus Length Check” in “HW Design &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Checking List&amp;nbsp;&amp;nbsp; for i.Mx6”. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;A href="https://community.nxp.com/docs/DOC-93819"&gt;https://community.nxp.com/docs/DOC-93819&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Have a great day,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Yuri&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Note: If this post answers your question, please click the Correct Answer &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;button. Thank you!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Sep 2018 06:35:49 GMT</pubDate>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2018-09-04T06:35:49Z</dc:date>
    <item>
      <title>Dependency of tCL and tCWL values on custom hardware performance ?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Dependency-of-tCL-and-tCWL-values-on-custom-hardware-performance/m-p/788432#M122174</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 All,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/Yuri"&gt;Yuri&lt;/A&gt;‌&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/igorpadykov"&gt;igorpadykov&lt;/A&gt;‌&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;A _jive_internal="true" data-containerid="-1" data-containertype="-1" data-content-finding="Community" data-objectid="206296" data-objecttype="3" href="https://community.nxp.com/people/igorpadykov" style="color: #3d9ce7; background-color: transparent; border: 0px; font-weight: inherit; padding: 1px 0px 1px calc(12px + 0.35ex);"&gt;igorpadykov&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;My custom hardware is based on i.MX6Q processor and 800MHz Alliance DDR3 memory&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: bold;"&gt;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;AS4C256M16D3A-12BCN.&lt;/STRONG&gt;&lt;/SPAN&gt;Design is most related to Nitrogen6_max design.&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;I set tCL = 6 and tCWL = 8 for the calibration and&amp;nbsp;ddr init script. Some boards are working for this values and for some boards I had to change tCWL = 7&amp;nbsp;for better performance. Otherwise getting segmentation faults.&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;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;1) How this could happen with the same ddr layout and same production line boards ?&amp;nbsp; What can we figure with this fine tuning of tCL and tCWL value of board to board ?&lt;/STRONG&gt;&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;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;A well as I could see following write DQS delays for my boards. You can see DQS 3 and DQS 4 are way off. It should be lover than 1/8 according to NXP user manual.&amp;nbsp;&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;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;2) What can we say from following DQS results ? Is it a impedance problem of those byte lanes ?&lt;/STRONG&gt;&amp;nbsp;&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;&lt;span class="lia-inline-image-display-wrapper" image-alt="t1.JPG"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/67983iA5A4E54A0D62D9DB/image-size/large?v=v2&amp;amp;px=999" role="button" title="t1.JPG" alt="t1.JPG" /&gt;&lt;/span&gt;&lt;IMG alt="" class="image-1 jive-image" height="122" style="border: 0px; font-weight: inherit; margin: 2px 20px 0px;" width="171" /&gt;&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;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;3) To optimize above values I used following method. But I couldn't see any impact for DQS 3 and DQS 4 with WALAT changes. Why is that ?&lt;/STRONG&gt;&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;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/68164iAAB6070A93483F41/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;IMG alt="" class="image-2 jive-image" height="356" style="border: 0px; font-weight: inherit; margin: 2px 20px 0px;" width="454" /&gt;&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;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;4) What are the other dependency which we can tolerate like tCWL and tCL for the memory performance ?&amp;nbsp;&lt;/STRONG&gt;&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;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;EM style="border: 0px; font-weight: inherit;"&gt;Here I have attached DDR3 memory data sheet and NXP calibration tool results.&amp;nbsp;&lt;/EM&gt;&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;I must be thankful to you if you will kindly reply me soon.&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;Regards,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Peter.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Sep 2018 05:57:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Dependency-of-tCL-and-tCWL-values-on-custom-hardware-performance/m-p/788432#M122174</guid>
      <dc:creator>peteramond</dc:creator>
      <dc:date>2018-09-04T05:57:25Z</dc:date>
    </item>
    <item>
      <title>Re: Dependency of tCL and tCWL values on custom hardware performance ?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Dependency-of-tCL-and-tCWL-values-on-custom-hardware-performance/m-p/788433#M122175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Peter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;unfortunately I am not aware of nxp documentation for optimization tCL and tCWL memory settings.&lt;/P&gt;&lt;P&gt;I believe such documentation should be provided by memory vendors.&lt;/P&gt;&lt;P&gt;NXP i.MX6 DDR Script Aid suggest to enter tCL and tCWL from datasheet mamories, without changes.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-333933"&gt;i.MX6ULL_LPDDR2_Script_Aid&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt;4) What are the other dependency which we can tolerate like tCWL and tCL for the memory performance ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;suggest to post this to memory vendor (Alliance) tech support&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WALAT is described on p.18 AN4467 i.MX 6 Series DDR Calibration&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note/AN4467.pdf" title="https://www.nxp.com/docs/en/application-note/AN4467.pdf"&gt;https://www.nxp.com/docs/en/application-note/AN4467.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general issues with improving performance and customer boards analysis may be provided with&lt;/P&gt;&lt;P&gt;extended support of Professional Services&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/support/support/nxp-professional-services:PROFESSIONAL-SERVICE" title="https://www.nxp.com/support/support/nxp-professional-services:PROFESSIONAL-SERVICE"&gt;NXP Professional Services|NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&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>Tue, 04 Sep 2018 06:34:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Dependency-of-tCL-and-tCWL-values-on-custom-hardware-performance/m-p/788433#M122175</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-09-04T06:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Dependency of tCL and tCWL values on custom hardware performance ?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Dependency-of-tCL-and-tCWL-values-on-custom-hardware-performance/m-p/788434#M122176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Hello,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Look at my comments below.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;I. &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; From practical point of view&amp;nbsp; - it makes sense to modify / setup some MMDC registers &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;in initialization script after memory calibration, using its results. In Your case:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&amp;nbsp; MMDC registers updated from calibration &lt;BR /&gt;&amp;nbsp;&amp;nbsp; Write leveling calibration&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MMDC_MPWLDECTRL0 ch0 (0x021b080c) = 0x0018001E&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MMDC_MPWLDECTRL1 ch0 (0x021b0810) = 0x0028001A&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MMDC_MPWLDECTRL0 ch1 (0x021b480c) = 0x001A0025&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MMDC_MPWLDECTRL1 ch1 (0x021b4810) = 0x0014001E&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Read DQS Gating calibration&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPDGCTRL0 PHY0 (0x021b083c) = 0x02580258&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPDGCTRL1 PHY0 (0x021b0840) = 0x024C0250&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPDGCTRL0 PHY1 (0x021b483c) = 0x02600268&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPDGCTRL1 PHY1 (0x021b4840) = 0x02500230&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&amp;nbsp; Read calibration&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPRDDLCTL PHY0 (0x021b0848) = 0x423A3A3C&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPRDDLCTL PHY1 (0x021b4848) = 0x3A383842&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Write calibration&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPWRDLCTL PHY0 (0x021b0850) = 0x3A3A403C&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MPWRDLCTL PHY1 (0x021b4850) = 0x403A403A&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;If overnight test with new initialization parameters is OK - the found parameters are good &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;candidates for final release. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;II.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; tCL&amp;nbsp; and tCWL should be the same for i.MX6 MMDC and DDR3 (AS4C256M16D3A). &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;III. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; Please verify PCB design, using Excel page named “MX6 DRAM Bus Length Check” in “HW Design &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Checking List&amp;nbsp;&amp;nbsp; for i.Mx6”. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;A href="https://community.nxp.com/docs/DOC-93819"&gt;https://community.nxp.com/docs/DOC-93819&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Have a great day,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Yuri&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;------------------------------------------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Note: If this post answers your question, please click the Correct Answer &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;button. Thank you!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Sep 2018 06:35:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Dependency-of-tCL-and-tCWL-values-on-custom-hardware-performance/m-p/788434#M122176</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2018-09-04T06:35:49Z</dc:date>
    </item>
  </channel>
</rss>

