From: "Jaka Močnik" <jaka@activetools.si>
To: Embedded PPC Linux Mailing List <Linuxppc-embedded@ozlabs.org>
Subject: U-Boot hangs in relocate_code after sw reboot
Date: Fri, 04 Mar 2005 16:53:13 +0100 [thread overview]
Message-ID: <1109951593.32294.5.camel@x.at.lan> (raw)
hello!
I don't really know if this mailing list is the proper place to direct
questions regarding U-Boot, but I've seen some preceding posts about it,
so I thought I'd ask...
I've ported U-Boot over to a custom MPC8560 (PQ3) based board - it works
well, except that after a sw reboot (from linux kernel or u-boot
itself), it only gets to the part where it relocates itself to RAM and
then hangs - the last debug output is
Relocating code to 07fd4000...
and the famous
Now running in RAM - U-Boot at: 07fd4000 never shows up.
has anyone experienced similar problems? any hints on what to look at?
regards,
jaKa
--
w3: http://fish.homeunix.org/people/jaka
email: jaka@activetools.si
next reply other threads:[~2005-03-04 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 15:53 Jaka Močnik [this message]
2005-03-04 16:06 ` U-Boot hangs in relocate_code after sw reboot Jon Loeliger
2005-03-04 16:11 ` Jerry Van Baren
2005-03-04 16:18 ` Kumar Gala
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=1109951593.32294.5.camel@x.at.lan \
--to=jaka@activetools.si \
--cc=Linuxppc-embedded@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).