bdi2000 debugging

Sylvain Munaut tnt at
Thu Feb 17 07:55:50 EST 2005


>Something is overwriting memory in kernel space I guess.
>Now, I have the BDI 2000 and I am trying to debug this, but until
>now I was unsuccessful :-(
>When I debug the kernel, the BDI prints this out in the telnet
>- Target MBAR is 0xF0000000
>- Target XLBA is 0x8000A366
>I know what MBAR is, but what the XLBA is?
>The problem is that while this value remains the same everything 
>is fine. But sometimes it is set to 0x00000000 and then I cannot
>use debugger anymore. I can make a few steps when this value 
>is set to 0x0, but the "stepping" is done in completely unrelated
>code. I first noticed this while stepping trough hc_found_ohci
>function when the return 0 is executed. When I disabled the USB
>support in my kernel I could use debugger to debug a kernel.
>But is still does not work all the time, because the XLBA still 
>gets set to 0!
The good news : I can explain you BDI2000 problem :)
The bad news : AFAIK you can't fix it :(

There is a bug in the rev <= 1.2 of the silicon of MPC5200 : When there
is another XLB Master active (like USB or any bestcomm activity), the XLB
arbiter can get confused during debugging and you can resume nor
can you access memory or do anything ... you can just reboot.

It's VERY frustrating since the BDI2000 is then kind of useless for debug
in the cases when you need those activated ...


More information about the Linuxppc-embedded mailing list