Matthew S. McClintock wrote:
> So more specifically, if the bdi2000 init section moves the CCSRBAR and
> maps a TLB to the location the CCSRBAR was moved too you can't just
> moved the CCSRBAR back to its default location?
No, because the BDI2000 doesn't know that _you_ have done that in
your code. If you do it in the BDI init secion, it will know.
> .... One would also need to
> remap the TLB entry to CCSRBAR?
Yes, but that isn't the problem.
> Could anyone familiar with that workaround listed below verify
> that
> this could be causing the CPU to freeze/crash?
I've been there and done it. The CCSRBAR can't be changing while you
are using the BDI2000 for debug. The debug registers the BDI2000 is
trying to access are in this space. If you move the space without the
BDI2000 knowing (i.e. in your code), the BDI2000 doesn't seem to be
able to track those changes and continues to try and access the
debug registers in the last known space.
So, what you have to do is (simply :-) ensure the CCSRBAR isn't
changing when you are debugging the software.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
