<?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: Re: MX6Q+LPDDR2(32bit) boot issue</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315535#M41656</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Asim,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I answered some of you questions, please see inline.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;asimzaidi wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hi Ofer&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Thanks for your responses. We still need to understand why your boards pass the FSL DDR stress test yet fail in your application. We had an internal meeting to discuss the issues you are encountering and came up with some further questions/experiments.&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Memory Testing&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The failure you posted below is strange stating that the complete background pattern word was incorrect. Is this indicating that DDR was reading all 0’s instead of all F’s&amp;nbsp; and vice versa, for multiple consecutive addresses. Is this consistently reproducible and what memory test (Bit Flip or other) is reporting this? &lt;/LI&gt;
&lt;/UL&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;o&amp;nbsp; If the Entire word is wrong or random this may indicate some issue with address and/or command signals.&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;&lt;STRONG&gt;YES, this type of failure is repeating (but not in every run). It happens when running "Solid Bits" and "Bit Flips".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;&lt;STRONG&gt;I also noticed that when it happens, it happens in a burst of 4 or 8 failures, for example:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;Loop 17/1000:&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Stuck Address&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Random Value&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;Compare XOR&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;Compare SUB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;Compare MUL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Compare DIV&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;Compare OR&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Compare AND&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Sequential Increment: ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;Solid Bits&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Block Sequential&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Checkerboard&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Bit Spread&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;Bit Flip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : testing 147FAILURE: 0xfffbffff != 0x00040000 at offset 0x00f8d440.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;FAILURE: 0x00040000 != 0xfffbffff at offset 0x00f8d444.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;FAILURE: 0xfffbffff != 0x00040000 at offset 0x00f8d448.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;FAILURE: 0x00040000 != 0xfffbffff at offset 0x00f8d44c.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Walking Ones&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;Walking Zeroes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; 8-bit Writes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; 16-bit Writes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;Loop 18/1000:&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Stuck Address&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Random Value&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Compare XOR&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;Compare SUB&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Compare MUL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Compare DIV&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Compare OR&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Compare AND&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Sequential Increment: ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Solid Bits&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : testing&amp;nbsp; 32FAILURE: 0x00000000 != 0xffffffff at offset 0x00b60f9c.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;FAILURE: 0xffffffff != 0x00000000 at offset 0x00b60fa0.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;FAILURE: 0x00000000 != 0xffffffff at offset 0x00b60fa4.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;FAILURE: 0xffffffff != 0x00000000 at offset 0x00b60fa8.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Block Sequential&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Checkerboard&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Bit Spread&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Bit Flip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Walking Ones&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; Walking Zeroes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&amp;nbsp; &lt;EM&gt;8-bit Writes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;&amp;nbsp; 16-bit Writes&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : ok&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 180px;"&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; padding: 0px 0px 0px 90px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You have previously confirmed the DDR settings in the stress test initialization and UBOOT are the same. Can you please read out the MMDC registers after your DDR initialization in UBOOT.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;Do you mean: dump the relevant registers from the u-boot prompt?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; What I did previously, was to dump the relevant registers after the system was up, from kernel using memtool. Isn't it even better?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (Because that rules out the possibility that the kernel does something wrong.)&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;o&amp;nbsp; We would like to confirm whether the registers you programmed are correctly and match the DDR stress test initialization ?&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px; padding-left: 60px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;o&amp;nbsp; Another similar experiment would be to run the FSL DDR stress test after UBOOT has initialized by attaching with JTAG.&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Byte wise failures are usually indicative of a problem with the DQS signals. Either the DQS signals have too slow a rise/fall time, or there is a glitch or over/under shoots (signal integrity issues).&lt;/LI&gt;
&lt;/UL&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;o&amp;nbsp; It will be helpful to test over temperature per above to assist in narrowing down the issue with the DQS signals&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px; padding-left: 60px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;o&amp;nbsp; Ideally we recommend using calibration values which are a mean of multiple boards and temperatures&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Do you see similar behavior/failures using both fixed and interleaved modes ?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;Since we understood that we can't use 64-bit for LPDDR2, we switched to Interleaving mode, and haven't tried Fixed mode.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Clocking&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Is your system changing the DDR frequency or does the system boot up and stay at 528 MHz?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;No, u-boot sets the DDR frequency, and the kernel doesn't modify MXC_CCM_CBCMR and MXC_CCM_CBCDR.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I used this patch in order to achieve that in 3.0.35 4.1.0:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;diff --git a/arch/arm/mach-mx6/clock.c b/arch/arm/mach-mx6/clock.c&lt;/P&gt;
&lt;P&gt;index 48d3999..9067bbe 100644&lt;/P&gt;
&lt;P&gt;--- a/arch/arm/mach-mx6/clock.c&lt;/P&gt;
&lt;P&gt;+++ b/arch/arm/mach-mx6/clock.c&lt;/P&gt;
&lt;P&gt;@@ -1390,12 +1390,12 @@ static int _clk_periph_set_parent(struct clk *clk, struct clk *parent)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reg = __raw_readl(MXC_CCM_CBCMR);&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reg &amp;amp;= ~MXC_CCM_CBCMR_PRE_PERIPH_CLK_SEL_MASK;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reg |= mux &amp;lt;&amp;lt; MXC_CCM_CBCMR_PRE_PERIPH_CLK_SEL_OFFSET;&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; __raw_writel(reg, MXC_CCM_CBCMR);&lt;/P&gt;
&lt;P&gt;+/*&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; __raw_writel(reg, MXC_CCM_CBCMR); */&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* Set the periph_clk_sel multiplexer. */&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reg = __raw_readl(MXC_CCM_CBCDR);&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reg &amp;amp;= ~MXC_CCM_CBCDR_PERIPH_CLK_SEL;&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; __raw_writel(reg, MXC_CCM_CBCDR);&lt;/P&gt;
&lt;P&gt;+/*&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; __raw_writel(reg, MXC_CCM_CBCDR); */&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; } else {&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reg = __raw_readl(MXC_CCM_CBCDR);&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* Set the periph_clk2_podf divider to divide by 1. */&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You had previously stated some issues in setting the DDR clock. Please refer to the following thread:&lt;/LI&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;A _jive_internal="true" data-containerid="2004" data-containertype="14" data-content-finding="Community" data-objectid="306143" data-objecttype="1" href="https://community.nxp.com/thread/306143" onclick=""&gt;https://community.freescale.com/thread/306143&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/UL&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If modifying the DDR clock are you changing any other system clocks ?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;No. I'm using this for 480MHz:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;MXC_DCD_ITEM(1, CCM_BASE_ADDR + 0x14, 0x2018D00) // 480MHz&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 90px;"&gt;&lt;EM&gt;MXC_DCD_ITEM(2, CCM_BASE_ADDR + 0x18, 0x20324)&amp;nbsp;&amp;nbsp; // 480MHz&lt;/EM&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp; And keep the default for 528MHz.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;HW Checks&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; To rule out any possible HW issues we would like to ensure that power supply and decoupling network on your board is correct . We are in the process of reviewing your provided design files as well.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Can you confirm if your board design meets the FSL decoupling requirements for the VDD_SOC and other domains as outlined in the i.MX6 HW users guide&lt;/LI&gt;
&lt;/UL&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 60px;"&gt;o&amp;nbsp; We have seen poor power delivery network can issues when stressing the part with higher instantaneous current requirements&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;YES, we reviewed our design, and it looks good. (&lt;A href="https://community.nxp.com/message/451283"&gt;Re: Re: ORCAM IPU/LPDDR2 Issues&lt;/A&gt;).&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Could you try increasing the VDD_SOC domain as well as the 1V8 and LPDDR_1V2_DDR to see if this has any impact.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;We increased the VDD_SOC to 1.375v and we noticed no influence. We didn't change 1V8 and LPDDR_1V2_DDR.&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;·&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Do you have any boards using a different memory vendor just to rule out any DDR memory issues ?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;Yes, we have some, but in the past we got poor results with them. We will try them again.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Errata Check&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Can you please confirm that the BSP/kernel you are using has the patch for the following issue:&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: Calibri, sans-serif; font-size: 14.4444446563721px;"&gt;ERR003740 ARM/PL310: 752271—Double linefill feature can cause data corruption: &lt;/SPAN&gt; only workaround to this erratum is to disable the double linefill feature.&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d; font-family: Calibri, sans-serif; font-size: 14.4444446563721px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;/*&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;120&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * The L2 cache controller(PL310) version on the i.MX6D/Q is r3p1-50rel0&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;121&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * The L2 cache controller(PL310) version on the i.MX6DL/SOLO/SL is r3p2&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;122&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * But according to ARM PL310 errata: 752271&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;123&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * ID: 752271: Double linefill feature can cause data corruption&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;124&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Fault Status: Present in: r3p0, r3p1, r3p1-50rel0. Fixed in r3p2&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;125&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Workaround: The only workaround to this erratum is to disable the&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;126&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * double linefill feature. This is the default behavior.&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;127&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; */&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;128&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; i&lt;STRONG&gt;f (!cpu_is_mx6q())&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;&lt;STRONG&gt;129&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; val |= 0x40800000;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;&lt;STRONG&gt;130&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; writel(val, IO_ADDRESS(L2_BASE_ADDR + L2X0_PREFETCH_CTRL));&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;131&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;132&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; val = readl(IO_ADDRESS(L2_BASE_ADDR + L2X0_POWER_CTRL));&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;133&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; val |= L2X0_DYNAMIC_CLK_GATING_EN;&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;134&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; val |= L2X0_STNDBY_MODE_EN;&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;135&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; writel(val, IO_ADDRESS(L2_BASE_ADDR + L2X0_POWER_CTRL));&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;136&lt;/P&gt;
&lt;P style="font-size: 13.3333339691162px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;137&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; l2x0_init(IO_ADDRESS(L2_BASE_ADDR), 0x0, ~0x00000000);&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;STRONG&gt;Confirmed - I found the marked code in arch/arm/mach-mx6/mm.c&lt;/STRONG&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P&gt;We realize that this is a slow and painful debug exercise but we are hopeful that we will discover the root cause of your instabilities.&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&lt;/P&gt;
&lt;P&gt;Asim&lt;/P&gt;

&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Ofer F.&lt;/P&gt;&lt;P&gt;ORCAM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 03 Dec 2014 17:08:09 GMT</pubDate>
    <dc:creator>oferfederovsky</dc:creator>
    <dc:date>2014-12-03T17:08:09Z</dc:date>
    <item>
      <title>MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315479#M41600</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I mentioned in some threads, we are trying on MX6Q+LPDDR2 combined design. but make no sense why boot failure in mfg bootimage.&lt;/P&gt;&lt;P&gt;We use Mx6DQSDL LPDDR2 Script Aid V0.04.xlsx to generate flashheader DCD part (attached file 6q_lpddr2_32.inc). The Samsung eMCP&lt;/P&gt;&lt;P&gt;DS attched,too.&lt;/P&gt;&lt;P&gt;Our DDR config:&lt;/P&gt;&lt;P&gt;Single Channel 32bit&lt;/P&gt;&lt;P&gt;2CS, each cs is 128Mx32 (totally 1GB)&lt;/P&gt;&lt;P&gt;With default DSE 40ohm (SI configuration in Mx6DQSDL LPDDR2 Script Aid V0.04.xlsx ), 400MHz DDR stress test failure, but it's okay change them&lt;/P&gt;&lt;P&gt;to 34ohm. But with this stress pass DCD, my uboot_mfg can't boot properly (no output in default console).&lt;/P&gt;&lt;P&gt;Please help us!&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-336254"&gt;6q_lpddr2_32.inc.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-336254"&gt;mx6q_tdh_lpddr2_400_v004.inc.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jun 2014 02:45:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315479#M41600</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-06T02:45:43Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2 boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315480#M41601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond&lt;/P&gt;&lt;P&gt;suggest to build just Uboot (not MFG) and try to boot it,&lt;/P&gt;&lt;P&gt;flash_header.S should be modified with new DCD settings.&lt;/P&gt;&lt;P&gt;Regarding MFG Tool, its firmware (initramfs.cpio.gz.uboot)&lt;/P&gt;&lt;P&gt;should be rebuilt with new DCD, please check&lt;/P&gt;&lt;P&gt;i.MX_6Dual6Quad_SABRE-SD_Linux_User's_Guide.pdf&lt;/P&gt;&lt;P&gt;sect.3.9 "Building Manufacturing Firmware".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.freescale.com/webapp/Download?colCode=L3.0.35_4.1.0_LINUX_DOCS&amp;amp;location=null&amp;amp;fasp=1&amp;amp;WT_TYPE=Supporting%20Information&amp;amp;WT_VENDOR=FREESCALE&amp;amp;WT_FILE_FORMAT=gz&amp;amp;WT_ASSET=Documentation"&gt;L3.0.35_4.1.0_LINUX_DOCS&lt;/A&gt; &lt;IMG alt="" class="jiveImage" src="http://www.freescale.com/files/graphic/SECURITYINFOIMAGE.gif" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually you can download just modified Uboot with MFG Tool,&lt;/P&gt;&lt;P&gt;modifiy ucl2.xml (also one can create new Profile, check with MFG2 Tool documentation).&lt;/P&gt;&lt;P&gt;u-boot-mx6q-sabresd_nopad.bin is Uboot image&amp;nbsp; without offset (0x400).&lt;/P&gt;&lt;P&gt;Note, for USB loading one needs the same images, but without offset.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Changed "SabreSD-SD" profile:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;LIST name="SabreSD-SD" desc="USB SDP"&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;CMD state="BootStrap" type="boot" body="BootStrap" file ="u-boot-mx6q-sabresd_nopad.bin" &amp;gt;Loading image&amp;lt;/CMD&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;CMD state="BootStrap" type="jump" &amp;gt; Jumping to image. &amp;lt;/CMD&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;CMD state="Updater" type="push" body="$ echo Load Complete!"&amp;gt;Done&amp;lt;/CMD&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/LIST&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On Windows platform for creating Uboot image without offset, "dd" &lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;utility may be used (&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.chrysocome.net/dd):"&gt;http://www.chrysocome.net/dd):&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;dd.exe if=u-boot-mx6q-sabresd.bin of=u-boot-mx6q-sabresd_nopad.bin&amp;nbsp; bs=1024 skip=1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jun 2014 10:25:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315480#M41601</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-06T10:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2 boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315481#M41602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/igorpadykov"&gt;igorpadykov&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.I use different profile to test my mfg uboot.&lt;/P&gt;&lt;P&gt;&amp;lt;LIST name="Android-TDH-eMMC" desc="Choose eMMC android as media"&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;CMD state="BootStrap" type="boot" body="BootStrap" file ="u-boot-mx6q-tdh-lpddr2_nopad.bin" &amp;gt;Loading U-boot&amp;lt;/CMD&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;CMD state="BootStrap" type="jump" &amp;gt; Jumping to OS image. &amp;lt;/CMD&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;&amp;nbsp; &amp;lt;CMD state="Updater" type="push" body="$ echo Load Complete!"&amp;gt;Done&amp;lt;/CMD&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/LIST&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 2.Following your instruction, I cut first 1k bytes of my mfg uboot&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;dd if=u-boot-mx6q-tdh-lpddr2.bin of=u-boot-mx6q-tdh-lpddr2_nopad.bin bs=1024 skip=1&lt;/P&gt;&lt;P&gt;142+1 records in&lt;/P&gt;&lt;P&gt;142+1 records out&lt;/P&gt;&lt;P&gt;146332 bytes (146 kB) copied, 0.00187831 s, 77.9 MB/s&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; Still there is no message output in uart console.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jun 2014 11:23:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315481#M41602</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-06T11:23:18Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2 boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315482#M41603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also have a double check on existed mfg u-boot-mx6q-sabresd.bin. It contains first 1k padding bytes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jun 2014 11:28:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315482#M41603</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-06T11:28:35Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2 boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315483#M41604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond&lt;/P&gt;&lt;P&gt;could you try to rebuild just Linux Uboot&lt;/P&gt;&lt;P&gt;(not Android) and try ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&amp;amp;nodeId=018rH3ZrDRB24A&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab"&gt;L3.0.35_4.1.0_ER_SOURCE_BSP&lt;/A&gt; &lt;IMG alt="" class="jiveImage" src="http://www.freescale.com/files/graphic/SECURITYINFOIMAGE.gif" /&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually does board output anything ?&lt;/P&gt;&lt;P&gt;Did you try SDK ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&amp;amp;nodeId=018rH3ZrDRB24A&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab"&gt;i.MX 6Series Platform SDK&lt;/A&gt; &lt;IMG alt="" class="jiveImage" src="http://www.freescale.com/files/graphic/SECURITYINFOIMAGE.gif" /&gt; :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jun 2014 11:31:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315483#M41604</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-06T11:31:38Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2 boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315484#M41605</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, there is nothing output in uart1 (1st uart). Are you sure that rebuild uboot source useful?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jun 2014 11:35:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315484#M41605</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-06T11:35:54Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2 boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315485#M41606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond&lt;/P&gt;&lt;P&gt;suggest to start with SDK and oscilloscope&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&amp;amp;nodeId=018rH3ZrDRB24A&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab"&gt;i.MX 6Series Platform SDK&lt;/A&gt; &lt;A href="http://www.freescale.com/files/graphic/SECURITYINFOIMAGE.gif"&gt;&lt;IMG alt="" class="jiveImage" src="http://www.freescale.com/files/graphic/SECURITYINFOIMAGE.gif" /&gt;&lt;/A&gt; :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jun 2014 14:53:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315485#M41606</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-07T14:53:15Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315486#M41607</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear chipexpert,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Thanks for your response! I checked iMX6 platform sdk, it does not contains LPDDR2 single channel DCD for MX6Q series boards.&lt;/P&gt;&lt;P&gt;MX6Q EVB -&amp;gt;2GB DDR3 @64bit single channel &lt;/P&gt;&lt;P&gt;MX6Q Sabre_ai -&amp;gt;DDR3&lt;/P&gt;&lt;P&gt;MX6Q Sabre_SmartDevice -&amp;gt;DDR3&lt;/P&gt;&lt;P&gt; I don't have JTAG tool,therefore I have to fix my DCD for DDR initialization issue. &lt;/P&gt;&lt;P&gt; BTW,my board DDR signal is routed in inner layer. Probably routing not good enough, we can't run memory stress test pass in 432MHz or &lt;/P&gt;&lt;P&gt;above.&lt;/P&gt;&lt;P&gt; My question is , DDR stress test pass in 400MHz, Why it fails to bringup LPDDR2 using same DCD config?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RaymondW&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 08 Jun 2014 06:50:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315486#M41607</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-08T06:50:01Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315487#M41608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond&lt;/P&gt;&lt;P&gt;you can add to DCD (and Uboot) code to set some GPIO,&lt;/P&gt;&lt;P&gt;then check where code hangs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 08 Jun 2014 15:40:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315487#M41608</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-08T15:40:12Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315488#M41609</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Chip&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I tried to enable 1 gpio to light on a LED, seems failure . I think this means cpu did not&lt;/P&gt;&lt;P&gt;run there.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; BTW, I found a DCD data to enable DDR 400MHz:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; setmem /32 0x020c4018 = 0x00060324&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Is it right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RaymondWang&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 01:40:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315488#M41609</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-09T01:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315489#M41610</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;Hi Raymond&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;suggest to verify that GPIO module clock is not&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;gated in CCM registers (CCM_CCGR).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;Best regards&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 03:55:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315489#M41610</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-09T03:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315490#M41611</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I Add the gpio code in uboot since DCD can't access gpio module directly.&lt;/P&gt;&lt;P&gt;I test my uboot with sabresd DDR3 config, it does work. &lt;/P&gt;&lt;P&gt;&amp;nbsp; Only one CCM register is set in DCD,&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt; setmem /32 0x020c4018 = 0x00060324&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt; I don't think it relevant to GPIO required clocks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;&amp;nbsp; I doubt DCD ccm register setting not enough to let LPDDR2 working at 400MHz. Our board&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;can't pass 528MHz DDR stress test.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 04:07:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315490#M41611</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-09T04:07:01Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2 boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315491#M41612</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond&lt;/P&gt;&lt;P&gt;you can try other settings as below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/312033"&gt;iMX6DQ LPDDR2 Initialization Issue&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;Best regards&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 08:07:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315491#M41612</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-09T08:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315492#M41613</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I tried ,same behavior as before. and that init script is 533MHz, running DDR stress test will fail. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 08:43:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315492#M41613</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-09T08:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315493#M41614</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond&lt;/P&gt;&lt;P&gt;what BSP are you using ?&lt;/P&gt;&lt;P&gt;What documents (if any) are you reading when&lt;/P&gt;&lt;P&gt;preparing images ?&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;Best regards&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 09:23:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315493#M41614</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-09T09:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315494#M41615</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;my bsp is Android4.2.2-1.1.0-GA And my board design is based on SabreSD ( but using different DDR and PMIC).&lt;/P&gt;&lt;P&gt;Mine is LPDD2 and PMIC is PF0100F1 (specially for LPDDR2 application)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 09:36:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315494#M41615</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-09T09:36:28Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315495#M41616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond&lt;/P&gt;&lt;P&gt;I would suggest to use Linux or even SDK&lt;/P&gt;&lt;P&gt;at bring-up phase. They are simpler, better documented,&lt;/P&gt;&lt;P&gt;easier for debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&amp;amp;nodeId=018rH3ZrDRB24A&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab"&gt;L3.0.35_4.1.0_ER_SOURCE_BSP&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&amp;amp;nodeId=018rH3ZrDRB24A&amp;amp;fpsp=1&amp;amp;tab=Design_Tools_Tab"&gt;i.MX 6Series Platform SDK&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;Best regards&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 09:45:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315495#M41616</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-09T09:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315496#M41617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am not familiar on linux or mx6 SDK. But I reviewed sdk source tree, no instinct difference between SDK and UBOOT stand for &lt;/P&gt;&lt;P&gt;board dcd configuration.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jun 2014 10:31:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315496#M41617</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-09T10:31:05Z</dc:date>
    </item>
    <item>
      <title>Re: Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315497#M41618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I rebuild sdk_unit_test_ALL.bin with replacing smart_device dcd.c to my LPDDR2.&lt;/P&gt;&lt;P&gt;And add it to mfg tool&lt;/P&gt;&lt;P&gt;&amp;lt;LIST name="DWLD_IN_SDP" desc="Download and execute a binary!"&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;CMD state="BootStrap"&amp;nbsp; type="find" body="Recovery" timeout="180"/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;CMD state="BootStrap" type="boot" body="Recovery" file="sdk_unit_test_ALL.bin"&amp;gt;Loading&lt;/P&gt;&lt;P&gt;SDK image&amp;lt;/CMD&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;CMD state="BootStrap" type="jump"&amp;gt;Jumping to SDK image.&amp;lt;/CMD&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/LIST&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The mfgtool hangs with display state in "Loading SDK image" about 75% over 5mins.&lt;/P&gt;&lt;P&gt;I enclosed my new dcd.c.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jun 2014 04:15:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315497#M41618</guid>
      <dc:creator>raymondwang</dc:creator>
      <dc:date>2014-06-10T04:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: Re: Re: MX6Q+LPDDR2(32bit) boot issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315498#M41619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raymond&lt;/P&gt;&lt;P&gt;I would suggest to start&lt;/P&gt;&lt;P&gt;with attached examples. One uses iRAM,&lt;/P&gt;&lt;P&gt;second DDR3 - you can modify it for LPDDR2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Optionally you can build SDK examples and run in iRAM using link below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-95853"&gt;iRAM (OCRAM) i.MX6 SDK Application&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;Best regards&lt;/P&gt;&lt;P style="font-weight: inherit; font-style: inherit; font-size: 13px; font-family: inherit;"&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jun 2014 07:33:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315498#M41619</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-06-10T07:33:08Z</dc:date>
    </item>
  </channel>
</rss>

