On Sun, 12 Dec 2004 20:45:22 -0700
Chaz McGarvey <chaz@brokenzipper.com> wrote:

> 0 > .registers dev /memory .properties
> Client's Fix Pt Regs:
>   00 DEADBEEF 00E0EB00 DEADBEEF 00E0C840 00E0A864 00E0CAD0 00000004 
> 00000002
>   08 00E0F090 FF8099B8 00000000 00000000 00000000 DEADBEEF DEADBEEF 
> DEADBEEF
>   10 DEADBEEF DEADBEEF DEADBEEF DEADBEEF 000042F4 00000200 FF8099B8 
> 00000000
>   18 00000000 FF8D7C80 00010000 007E0000 000043BC 00000078 000043A0 
> FFFFFFFF

So r0, r3, r4, and r5 are in the 0xe0xxxx area

> Special Regs:
>      %SRR0: 006000D8   
>      %LR: 006000D8 

but the execution instructions were last at 0x600xxx. This looks a lot
like a mismatch between bootxx and ofwboot. bootxx 1.12 would have
loaded ofwboot to 0x600000 but ofwboot 1.10 (?) is linked to 0xe00000,
which is where you should have jumped to. After bootxx jumped to main()
in ofwboot, ofwboot passes parameters to printf statements. The address
of those parameters would be relative to ofwboot's link address, and
the r3, r4, and r5 registers look like they are at the end of ofwboot,
in the string area.

Let's try one more time, to be sure. At the catch, do

.registers
600000 dis
e00000 dis

thanks,
tim