<?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>i.MX ProcessorsのトピックRe: 6sololite and Micron LPDDR2 EDB8132B4PM-1D-F issues</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/deleted/m-p/739980#M115155</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jaya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;except changing drive strength from i.MX side, it also can be changed&lt;/P&gt;&lt;P&gt;from EDB8132B4PM ddr: using MR3 (DS). May be useful to check temperature&lt;/P&gt;&lt;P&gt;dependency: if cooling down the part causes more failures, then it is likely the drive strength is &lt;BR /&gt;too high causing more overshoots and undershoots. Memtester differs from ddr test that&lt;/P&gt;&lt;P&gt;it also stresses power subsystem. One can pay attention to ripples: requirement for ripple noise&lt;/P&gt;&lt;P&gt;should be less than 5% Vp-p of supply voltage average value. Related power rails affected: all&lt;/P&gt;&lt;P&gt;VDD_xxx_IN and VDD_xxx_CAP and test with slightly increasing VDD_SOC_CAP.&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>Sun, 21 Jan 2018 22:55:54 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2018-01-21T22:55:54Z</dc:date>
    <item>
      <title>deleted</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/deleted/m-p/739979#M115154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;deleted&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Jan 2018 04:20:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/deleted/m-p/739979#M115154</guid>
      <dc:creator>jayakumar2</dc:creator>
      <dc:date>2018-01-20T04:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: 6sololite and Micron LPDDR2 EDB8132B4PM-1D-F issues</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/deleted/m-p/739980#M115155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jaya&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;except changing drive strength from i.MX side, it also can be changed&lt;/P&gt;&lt;P&gt;from EDB8132B4PM ddr: using MR3 (DS). May be useful to check temperature&lt;/P&gt;&lt;P&gt;dependency: if cooling down the part causes more failures, then it is likely the drive strength is &lt;BR /&gt;too high causing more overshoots and undershoots. Memtester differs from ddr test that&lt;/P&gt;&lt;P&gt;it also stresses power subsystem. One can pay attention to ripples: requirement for ripple noise&lt;/P&gt;&lt;P&gt;should be less than 5% Vp-p of supply voltage average value. Related power rails affected: all&lt;/P&gt;&lt;P&gt;VDD_xxx_IN and VDD_xxx_CAP and test with slightly increasing VDD_SOC_CAP.&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>Sun, 21 Jan 2018 22:55:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/deleted/m-p/739980#M115155</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-01-21T22:55:54Z</dc:date>
    </item>
  </channel>
</rss>

