From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] after a sw reset, u-boot hangs in relocate_code
Date: Fri, 4 Mar 2005 12:14:26 -0500 [thread overview]
Message-ID: <42289772.6000705@smiths-aerospace.com> (raw)
In-Reply-To: <1109953466.32294.11.camel@x.at.lan>
Jaka Mo?nik wrote:
> hello!
>
> I've ported U-Boot (1.1.2) 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
Welcome to the u-boot email list ;-)
In our previous exchange on the Linuxppc-embedded list, you disagreed
with my suggestion (FAQ on u-boot hanging after relocation), and I tend
to agree (I skipped over the _restart_ statement previous).
Given that it is a problem on restart, I would speculate you have a
peripheral (ethernet is your #1 suspect) that isn't being shut down
before you reset/reboot. As a result, a packet comes in after you
reboot and your peripheral (ethernet) DMAs the packet into memory in the
middle of somewhere it doesn't belong. Kabango.
gvb
prev parent reply other threads:[~2005-03-04 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 16:24 [U-Boot-Users] after a sw reset, u-boot hangs in relocate_code Jaka Močnik
2005-03-04 17:14 ` Jerry Van Baren [this message]
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=42289772.6000705@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--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