public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Will Deacon" <will.deacon@arm.com>
To: "'xingxing pan'" <forandom@gmail.com>, "gdb" <gdb@sourceware.org>,
	  "Matthew Gretton-Dann" <Matthew.Gretton-Dann@arm.com>,
	<ks@nvidia.com>
Subject: RE: [Help] About the two debug modes of ARM
Date: Tue, 06 Jul 2010 14:48:00 -0000	[thread overview]
Message-ID: <005b01cb1d1a$366ab870$a3402950$@deacon@arm.com> (raw)
In-Reply-To: <AANLkTilmrQ67nz2_OR0Hz5ZFZovZLlLXoUGk2jZSf6IC@mail.gmail.com>

Hi,

> From the ARM11 reference manual, I know ARM11 has two debug modes, the
> Halting mode and the Monitor Mode.
> When we use debuggers to debug a program, often there are also two
> modes. The remote debugging, the debugger runs on the host, the
> debuggee runs on the target, and the debugger communicates with the
> core through something like JTAG. The native debugging, the debugger
> and debuggee run on the same computer.

Right, those are the usual two debugging scenarios.
 
> Here are my questions.
> (1)Dose the Halting mode and the Monitor mode correspond to Remote
> debugging and Native debugging respectively?

Halting Mode means that the core is being debugged by an external
JTAG debugger. Monitor mode means that the debugging is performed
natively via co-processor or memory-mapped debug registers and 
debug events are handled via exceptions.

> (2)Some cores like ARM920 don't have the Monitor mode. Dose it means
> that when we are in native debugging on that cores, we can not use the
> hardware breakpoints and watchpoints?

You will need an external debugger in order to use hardware watchpoints
or breakpoints on the ARM920. The 926 has monitor mode implemented using
the EmbeddedICE-RT logic, so you can use the hardware resources there [with
the relevant Kernel support].

Hope that helps,

Will


      reply	other threads:[~2010-07-06 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 14:25 xingxing pan
2010-07-06 14:48 ` Will Deacon [this message]

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='005b01cb1d1a$366ab870$a3402950$@deacon@arm.com' \
    --to=will.deacon@arm.com \
    --cc=Matthew.Gretton-Dann@arm.com \
    --cc=forandom@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=ks@nvidia.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 read-only IMAP folder(s) and NNTP newsgroup(s).