Skip to contentSkip to conversation

after a sw reset, u-boot hangs in relocate_code

U-Boot-Users Jaka Močnik 2 participants 2 messages Mar 4, 2005

lore
Share & tools
lore
#0 lore raw

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

Signature · 2 lines
w3: http://fish.homeunix.org/people/jaka
email: jaka at activetools.si
#1 lore raw
Quoted 9 lines · Jaka Mo?nik

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

Quoted 8 lines

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