From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Alfred (Internode) Date: Thu, 15 Oct 2009 10:38:38 +1100 Subject: [U-Boot] uboot MPC5200B DDR memsize hangs References: <20091014120031.A7FEEE84EBC@gemini.denx.de> Message-ID: <7900617ABF254270BD3ECA161C278A70@kos> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > Hm... U-Boot 1.2.0 is very old. Please consider it obsolelte and > unsupported. Is there any special reason for not using current code? No reason, UBoot 1.2.0 is in ELDK4.1. Will seek and download latest uboot >> UBoot starts and we see serial output; but UBoot hangs on the very >> first read from DDR which is done in memsize.c:get_ram_size(). >> >> The serial output is: >> CPU: MPC5200 v2.2, Core v1.4 at 462 MHz >> Bus 132 MHz, IPB 66 MHz, PCI 33 MHz >> Board: JKC5200N7 >> I2C: 85 kHz, ready >> DRAM: >> >> We are pretty sure the DDR configuration is correct, but we would >> have thought this would not cause get_ram_size() to hang - merely >> return 0 or incorrect memory size. > > You are almost certainly wron - either your hardware or your DDR > initialization is broken. Can bad DDR configuration really hang the processor? I thought there was no acknowledgement system for DDR. > See also the FAQ at > http://www.denx.de/wiki/view/DULG/UBootCrashAfterRelocation Does the relocation occur before checking the DDR size? Chris