All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <kenneth.johansson@inn.ericsson.se>
To: Mark Powell <medp@primagraphics.co.uk>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Compiling/debugging 405GP and RISCWatch
Date: Wed, 21 Mar 2001 16:43:27 +0100	[thread overview]
Message-ID: <3AB8CC1F.C1F418AA@inn.ericsson.se> (raw)
In-Reply-To: 03ee01c0b206$c4878ea0$3000a8c0@primag


Mark Powell wrote:
>
>
> Is it possible to use the RISCWatch/JTAG interface as a backend to gdb?

No target exist now that Iam aware of.
The thing that prevent one from beeing written is that the help on the commands that the
riscwatch probe can do is to poor.

for ex. the help for dump is
---
help dump

  dump - upload processor memory in absolute file format

    dump -h <addr>..<addr> - upload hp format (requires transfer protocol)
    dump -b <addr>..<addr> - send data in binary (valid with -h option)
    dump -n <addr>..<addr> - send data in fast binary format
---

This dose not actually work if you trace a dump from the rwppc program you see that
a @<memory_type> is also needed.

On the other hand nobody has tried to make the interface difficult so its probably
quite easy to reverse engineer it.

What you need for gdb is a way to start/stop the cpu and to read/write registers and memory.

Its only the command for writing that is not obvious from the ascii trace that I did.



--
Kenneth Johansson
Ericsson Business Innovation AB   Tel: +46 8 404 71 83
Viderögatan 3                     Fax: +46 8 404 72 72
164 80 Stockholm                  kenneth.johansson@inn.ericsson.se

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2001-03-21 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 12:59 Compiling/debugging 405GP and RISCWatch Mark Powell
2001-03-21 13:12 ` Ralph Blach
2001-03-21 13:24 ` Wolfgang Denk
2001-03-21 15:43 ` Kenneth Johansson [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=3AB8CC1F.C1F418AA@inn.ericsson.se \
    --to=kenneth.johansson@inn.ericsson.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=medp@primagraphics.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.