Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: linux-mips@linux-mips.org
Subject: Re: Debugging MIPS cpu with a probe, how?
Date: Thu, 7 Aug 2008 15:34:58 +0200	[thread overview]
Message-ID: <20080807133458.GA16456@linuxtv.org> (raw)
In-Reply-To: <18830812.post@talk.nabble.com>

On Tue, Aug 05, 2008, TriKri wrote:
> 
> I have an embedded system, a box, with a MIPS processor on it, which I need
> to debug (stop and start the processor, tell what instructions it has
> previously executed, etc.). I also have an EJTAG probe, which I have
> connected between the computer's usb and the box, and written software for
> it. The software can communicate with the probe, which in its own turn can
> communicate with the box through the tap (test access port), by giving the
> tap certain instructions. It can also, through the tap, feed the MIPS
> processor with instructions, and read/write data from processor registers.
> 
> The question is now, how can debug the processor? How do I stop it, do I
> have to send any certain instructions to it? How can I set a breakpoint
> (which I understand is a quite crucial point)? Can I use GDB with my
> software to help debug the processor and how do I do that?

I looked for Open Source EJTAG software a while ago and found
two projects which may be of interest to you:

http://svn.berlios.de/svnroot/repos/openocd/branches/mips/
http://www.totalembedded.com/open_source/jtag/mips32_ejtag/

But I didn't try to use any of it so far.


Johannes

      parent reply	other threads:[~2008-08-07 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 13:10 Debugging MIPS cpu with a probe, how? TriKri
2008-08-07 12:47 ` Markus Gothe
2008-08-07 13:34 ` Johannes Stezenbach [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=20080807133458.GA16456@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=linux-mips@linux-mips.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