public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chris Alfred (Internode) <chrisalfred@internode.on.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] uboot MPC5200B DDR memsize hangs
Date: Thu, 15 Oct 2009 10:38:38 +1100	[thread overview]
Message-ID: <7900617ABF254270BD3ECA161C278A70@kos> (raw)
In-Reply-To: 20091014120031.A7FEEE84EBC@gemini.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 

       reply	other threads:[~2009-10-14 23:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D3F8E34E64844A62822AD8FE290DB614@kos>
     [not found] ` <20091014120031.A7FEEE84EBC@gemini.denx.de>
2009-10-14 23:38   ` Chris Alfred [this message]
2009-10-15  8:14     ` [U-Boot] uboot MPC5200B DDR memsize hangs Detlev Zundel
2009-10-18  7:42       ` Chris Alfred

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7900617ABF254270BD3ECA161C278A70@kos \
    --to=chrisalfred@internode.on.net \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox