From: Michael Snyder <msnyder@vmware.com>
To: "jeremy.bennett@embecosm.com" <jeremy.bennett@embecosm.com>
Cc: "gdb@sources.redhat.com" <gdb@sources.redhat.com>
Subject: Re: Generic Proxy RSP Server
Date: Tue, 30 Jun 2009 19:02:00 -0000 [thread overview]
Message-ID: <4A4A60AE.4090709@vmware.com> (raw)
In-Reply-To: <1246386344.2490.42.camel@thomas>
Jeremy Bennett wrote:
> I recently had to port GDB to a new embedded DSP architecture before the
> chip was available either in Silicon or model. All I had was the ABI
> specification, a GCC compiler and a promise of a cycle accurate model in
> a few weeks.
>
> In the absence of any target, I created a simple proxy for RSP, which
> was capable of modeling blocks of memory and registers, initialized
> according to the ABI specification. This allowed me to test the
> architecture definition in the GDB client against the ABI before the
> target was ready.
>
> When the target became available (as a model), I was able to quickly
> write an RSP server, with some confidence that the GDB client would be
> working reasonably accurately.
>
> I'm sure I'm not the first person to do this, but thinking it could be
> useful to others, I've packaged up the code and written a user guide for
> it (all GPL). It should be configurable to act as a proxy for any "bare
> metal" embedded target.
>
> http://www.embecosm.com/download/esp7.html
>
> I'm very happy to donate the code to GDB if people think it would be a
> useful addition.
>
> Feedback and comments welcome.
I've had to do something similar, so I recognize the utilitity.
But by the way "RSP"? Is that remote serial port, route/switch
processor, or revolutionary socialist party? 1/2 ;-)
prev parent reply other threads:[~2009-06-30 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 18:26 Jeremy Bennett
2009-06-30 19:02 ` Michael Snyder [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=4A4A60AE.4090709@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sources.redhat.com \
--cc=jeremy.bennett@embecosm.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