<?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: Internal LDO causes memtester failed in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287959#M34333</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;William,please click Correct Answer/Helpful Answer, if your question had been answered.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Yixing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Oct 2013 05:14:11 GMT</pubDate>
    <dc:creator>YixingKong</dc:creator>
    <dc:date>2013-10-31T05:14:11Z</dc:date>
    <item>
      <title>Internal LDO causes memtester failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287957#M34331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I saw random failure (CPU/System lockup) on memtester when I stressed the internal LDO. Below are my hardware and software settings.&lt;/P&gt;&lt;P&gt;Hardware:&lt;/P&gt;&lt;P&gt;iMX6D + 1GB x64 memory + uSD&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Software:&lt;/P&gt;&lt;P&gt;Linux Kernel 3.0.35_3.0.3 + ldo.sh + memtester&lt;/P&gt;&lt;P&gt;ldo.sh:&lt;/P&gt;&lt;P&gt;#!/bin/sh&lt;/P&gt;&lt;P&gt;## This script is to be used with memory_test. &lt;/P&gt;&lt;P&gt;## It will adjust the voltage to the LDO's as the &lt;/P&gt;&lt;P&gt;## memory test runs.&lt;/P&gt;&lt;P&gt;setspeed(){ echo $1 &amp;gt; /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed; }&lt;/P&gt;&lt;P&gt;vddsoc(){ if [ 0 -eq $# ]; then echo -n "vddsoc: " ; cat /sys/class/regulator/regulator.3/microvolts ; else echo $* &amp;gt; /sys/class/regulator/regulator.3/microvolts ; fi } &lt;/P&gt;&lt;P&gt;setspeed 396000 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;while :&lt;/P&gt;&lt;P&gt;do&lt;/P&gt;&lt;P&gt;&amp;nbsp; vddsoc 1250000 ;&lt;/P&gt;&lt;P&gt;&amp;nbsp; vddsoc 1175000 ;&lt;/P&gt;&lt;P&gt;done&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;memtester:&lt;/P&gt;&lt;P&gt;&lt;A href="http://pyropus.ca/software/memtester/" title="http://pyropus.ca/software/memtester/"&gt;memtester version 4&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 questions:&lt;/P&gt;&lt;P&gt;1. Can we stress internal LDO like this?&lt;/P&gt;&lt;P&gt;2. If answer to #1 is yes, how can we debug this since it's internal LDO?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Oct 2013 17:28:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287957#M34331</guid>
      <dc:creator>williamtung</dc:creator>
      <dc:date>2013-10-18T17:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: Internal LDO causes memtester failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287958#M34332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, William&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I do NOT understand what is your purpose of such test case, as the internal LDO's voltage will be changed according to CPUFreq change. Each CPU setpoint has its own setting of VDDARM and VDDSOC/PU, from your test case, I thought you try to make CPU running @396M, then do VDDSOC LDO output stress test. But I did NOT see you change the CPUFreq governor, as we use interactive governor by default, so CPUfreq will be changing according to CPU loading, so if you do want to do such test, please use powersave governor or userspace governor, then the CPU will be fixed at 396M. But I do NOT recommend you to do such test, as it is not making big sense, also, VDDPU should be always same as VDDSOC, not sure if you only adjust vddsoc would cause problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Please check you cpufreq governor first, if it is interactive, then your test case's failure is expected, as VDDSOC 1.175V is not enough for CPU running @1GHz.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Oct 2013 05:11:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287958#M34332</guid>
      <dc:creator>AnsonHuang</dc:creator>
      <dc:date>2013-10-25T05:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: Internal LDO causes memtester failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287959#M34333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;William,please click Correct Answer/Helpful Answer, if your question had been answered.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Yixing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Oct 2013 05:14:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287959#M34333</guid>
      <dc:creator>YixingKong</dc:creator>
      <dc:date>2013-10-31T05:14:11Z</dc:date>
    </item>
    <item>
      <title>Re: Internal LDO causes memtester failed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287960#M34334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;William, please click Correct Answer/Helpful Answer, if your question had been answered. Otherwise, we may close your discussion in 3 days.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Yixing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Nov 2013 07:11:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Internal-LDO-causes-memtester-failed/m-p/287960#M34334</guid>
      <dc:creator>YixingKong</dc:creator>
      <dc:date>2013-11-05T07:11:07Z</dc:date>
    </item>
  </channel>
</rss>

