public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: #HE XUZHOU# <xuzhouhe@pmail.ntu.edu.sg>
Cc: gdb@sources.redhat.com
Subject: Re: Problem on JTAG debug for ARM920T when mmu/cache is turned on
Date: Fri, 07 Oct 2005 12:56:00 -0000	[thread overview]
Message-ID: <20051007125555.GA19002@nevyn.them.org> (raw)
In-Reply-To: <052033A55521254893A4E2041957E1D0013393C3@mail03.student.main.ntu.edu.sg>

On Fri, Oct 07, 2005 at 01:26:02PM +0800, #HE XUZHOU# wrote:
> I am writing a program for JTAG debug. My target board is ARM920T. I found a single stepping problem when the MMU/CACHE is turn on. If the cache is turn on, single stepping doesn't work. If the cache is turn off, single stepping then works well.I guess this is casued by data/instruction cache. So, I am wandering what I should handle the MMU/CACHE when ARM920T enters debug state with mmu/cache is turned on? I have TWO questions and hope I can get some suggestions here. Thank you!
> 
> 1. Should I turn off the MMU after ARM920T enter debug state and turn
> it on before ARM920T is restarted? 2. Should I turn off the cache
> after ARM920T enter debug state and turn it on before ARM920T is
> restarted? Or just flush the cahce?

This depends on your target and debug stub; it is a problem with your
stub.  You probably want to flush the cache when writing to memory,
which includes for single step breakpoints.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

      reply	other threads:[~2005-10-07 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07  5:26 #HE XUZHOU#
2005-10-07 12:56 ` Daniel Jacobowitz [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=20051007125555.GA19002@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=xuzhouhe@pmail.ntu.edu.sg \
    /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).