From: Dan Malek <dan@embeddededge.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Enabling 8xx debug mode
Date: Tue, 23 Aug 2005 00:58:21 -0400 [thread overview]
Message-ID: <f45653d49c79423af587cff97181ac74@embeddededge.com> (raw)
In-Reply-To: <20050823022011.GE9667@dmt.cnet>
On Aug 22, 2005, at 10:20 PM, Marcelo Tosatti wrote:
> I know now that the BDI automatically enables debug mode by asserting
> the DSCK signal (available through the JTAG port). Is there any way
> to enable debugging mode purely via software?
I'm not sure I really understand the question, but I'll give some
answers anyway :-) The 8xx has the development/debug support,
which is a bunch of registers that allow setting instruction/data
breakpoints and so on. These are accessible from software, along
with other standard PowerPC debug (like single step).
The DSCK is a BDM/JTAG clock signal, and along with the other
signals allow the clocking of instructions and data through the BDM
pins. One of the things you can do is strobe in instructions that will
set these same breakpoint or other debug registers as are accessible
from software running on the part.
So, if you have software running on the processor, you can do the
same things. Obviously, if you are stuck someplace you need to
get the attention of the processor. You can do this with some interrupt
like kgdb does, then use the debug interface to help.
Does this make sense?
Thanks.
-- Dan
next prev parent reply other threads:[~2005-08-23 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 2:20 Enabling 8xx debug mode Marcelo Tosatti
2005-08-23 4:58 ` Dan Malek [this message]
2005-08-23 5:31 ` Marcelo Tosatti
2005-08-23 6:09 ` Dan Malek
2005-08-23 7:34 ` client and server implementation Saini Narendra
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=f45653d49c79423af587cff97181ac74@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=marcelo.tosatti@cyclades.com \
/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).