<?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: Re: Re: MX6Q+LPDDR2(32bit) boot issue in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/MX6Q-LPDDR2-32bit-boot-issue/m-p/315528#M41649</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ofer,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Darn. I really thought I had a break through for you.&lt;/P&gt;&lt;P&gt;I am running my board rock solid at 556 MHz. It will then work with intermittent errors up to 571 MHz before it won't pass data at all at 576 MHz.&lt;/P&gt;&lt;P&gt;The board I am using is an internal Freescale validation board we used for validating the LPDDR2 interface. It is not available to the general public.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am atttaching the *inc file I am using to get these results. The Micron chip listed in the file is the one I am using.&lt;/P&gt;&lt;P&gt;If you send back the script you are using, I can take another look to see if there is anything else I can think of.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem at this point is trying to find that one parameter that is hanging things up. Unfortunately I don't have any secret recipe for making that easier. It just has to be brute force at this point, adjusting things one at a time.&lt;/P&gt;&lt;P&gt;If you have JTAG capability, you can take a look at the DRAM memory directly. This might help you determine if the problem is with a Write or a Read, or might help you zero in on a particular byte lane. If you need the .elf file for use with a JTAG debugger, I can send you that file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One other general insight: The tricky thing with LPDDR2 is that the CA traces ared strobed on both the rising and falling edges of the clock, so there is a certain amount of alignment of the clock signals to the CA traces required. The traces lengths need to be matched pretty well, and the clock signal must be aligned to transition in the middle of the valid CA signal (which is the purpose of the CA ABS Delay field setting). Unfortunately, there is no calibration routine for aligning this clock edge. It was the registers that adjust this alignment that I was trying to change with my recommendations.&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Nov 2014 21:14:51 GMT</pubDate>
    <dc:creator>TheAdmiral</dc:creator>
    <dc:date>2014-11-24T21:14:51Z</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>

