From: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
To: Dan Malek <dan@embeddededge.com>
Cc: fabidi@ultsol.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: TLB and CSSBAR problems with MPC8540 and BDI2000
Date: Fri, 09 Jan 2004 16:18:18 -0600 [thread overview]
Message-ID: <1073686698.3275.10.camel@chuck.arlut.utexas.edu> (raw)
In-Reply-To: <3FFF276C.4060003@embeddededge.com>
>
> 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.
That leaves me with one question. When I don't do anything in the init
section of the bdi2000 except one command which is to remove the L2SRAM
from the initial MMU page and then I proceed with booting the board
boots fine. If I halt the board examine the CCSRBAR it has moved from
the default location.
I must be missing something, any ideas?
Thanks
--
Matthew S. McClintock <mattsm@arlut.utexas.edu>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-09 22:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 5:41 [Q] question about using x86 gdb to debug the remote ppc target (kgdb) kotaeji
2004-01-09 5:50 ` John Zhou
2004-01-09 16:42 ` Christopher R. Johnson
2004-01-09 17:40 ` TLB and CSSBAR problems with MPC8540 and BDI2000 Fahd Abidi
2004-01-09 17:54 ` Dan Malek
2004-01-09 19:45 ` Matthew S. McClintock
2004-01-09 22:13 ` Dan Malek
2004-01-09 22:18 ` Matthew S. McClintock [this message]
2004-01-09 22:28 ` Dan Malek
2004-01-12 15:56 ` Dan Malek
2004-01-12 20:19 ` Matthew S. McClintock
2004-01-14 1:43 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 17:19 Milliorn Gary-rxcr80
2004-01-14 18:39 ` Dan Malek
2004-01-28 15:57 ` Matthew S. McClintock
2004-01-28 16:10 ` Kumar Gala
2004-01-28 16:47 ` Matthew S. McClintock
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=1073686698.3275.10.camel@chuck.arlut.utexas.edu \
--to=mattsm@arlut.utexas.edu \
--cc=dan@embeddededge.com \
--cc=fabidi@ultsol.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).