From: Andrew Batchelor <A.C.Batchelor-99@student.lboro.ac.uk>
To: ramana.radhakrishnan@codito.com
Cc: GDB Newsgroup <gdb@sources.redhat.com>
Subject: Re: GDB --> Ethernet --> RV-ICE
Date: Mon, 27 Oct 2003 21:40:00 -0000 [thread overview]
Message-ID: <1067290805.1086.15.camel@And.Linux> (raw)
In-Reply-To: <1065.219.65.83.113.1067284661.squirrel@webmail.codito.com>
Hi Ramana,
Thanks a lot for your reply.
On Mon, 2003-10-27 at 19:57, Ramana Radhakrishnan wrote:
> You would need to add a new target that would talk to your RVICE in the
> format that it understands. Just as you have target remote , you also have
> target rdi / target angel etc. in gdb by which you can connect to other
> remote boards. So you would need to implement your own target structure.
[.....]
> The stub files would be used only if the board does not have any on chip
> debug support.In your case I dont see any reason for having any stub files
> because the work of the stub in your case would be done by the JTAG
> onboard.
[.....]
> As I see it your implementation is going to be simpler than any of the
> jtag implementations.You would essentially have to change the protocol
> packets in remote.c to send your protocol packets and I would guess you
> would be done.
Yeah, I figured as much. Seems to be pretty straight-forward then.
(famous last words.....) :o)
> You would have to implement each of the functions in the target
> structure.There is a provision for this. A reference implementation for
> this functionality would be the BDM patch to gdb for the coldfire . That
> would have provisions for all the above mentioned stuff.
Thanks - I'll go away and have a look at that.
Andy
prev parent reply other threads:[~2003-10-27 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 18:33 Andrew Batchelor
2003-10-27 19:47 ` Ramana Radhakrishnan
2003-10-27 21:40 ` Andrew Batchelor [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=1067290805.1086.15.camel@And.Linux \
--to=a.c.batchelor-99@student.lboro.ac.uk \
--cc=gdb@sources.redhat.com \
--cc=ramana.radhakrishnan@codito.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