public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] uboot MPC5200B DDR memsize hangs
Date: Thu, 15 Oct 2009 10:14:32 +0200	[thread overview]
Message-ID: <m2ws2xcbvb.fsf@ohwell.denx.de> (raw)
In-Reply-To: <7900617ABF254270BD3ECA161C278A70@kos> (Chris Alfred's message of "Thu, 15 Oct 2009 10:38:38 +1100")

Hi Chris,

>> 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

Stable tarballs can be found on our ftp server[1] - git access to the
very latest and greatest is available here[2].

>> See also the FAQ at
>> http://www.denx.de/wiki/view/DULG/UBootCrashAfterRelocation
>
> Does the relocation occur before checking the DDR size?

For PowerPC we relocate to the highest possible RAM address, so no we
need to probe RAM before we can relocate.  Also I would think that we do
not even get to the relocation but hang in the probing phase.  You
should really hook up a JTAG debugger and find out what's wrong.

Best wishes
  Detlev

[1] ftp://ftp.denx.de/pub/u-boot/
[2] http://git.denx.de/?p=u-boot.git;a=summary

-- 
If we knew what it was we were doing, we wouldn't call it research.
                                            -- Einstein
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  reply	other threads:[~2009-10-15  8:14 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   ` [U-Boot] uboot MPC5200B DDR memsize hangs Chris Alfred
2009-10-15  8:14     ` Detlev Zundel [this message]
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=m2ws2xcbvb.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --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