From: Srinivas Murthy <codevana@gmail.com>
To: ramana.radhakrishnan@codito.com
Cc: gdb@sources.redhat.com
Subject: Re: GDB over a serial link (with no OS) for MIPS32
Date: Thu, 09 Jun 2005 02:22:00 -0000 [thread overview]
Message-ID: <7cb1293c05060819223c23de35@mail.gmail.com> (raw)
In-Reply-To: <3307.203.212.198.158.1118255507.squirrel@webmail.codito.com>
Thanks for the email.
I will need a little more hand-holding :(
Can you please give me some more pointers on how to get started?
More specifically,
1. What are the OS-dependent and OS-independent portions of the code?
2. Specifically using a serial port, what is transport dependent part
of the code?
3. What is the arch. dependent part?
Any pointers on how to get started (maybe something like a porting
guide, perhaps?).
Thanks much for your help.
Regards,
-Srinivas
On 6/8/05, Ramana Radhakrishnan <ramana.radhakrishnan@codito.com> wrote:
>
> Hi,
>
> You'd want to write a new target in GDB. Take a look at the target
> abstraction.
> Look at a sample target ... lets say remote.c .
>
> cheers
> Ramana
>
> > Hi,
> > We need to develop a gdb debug tool for a custom multi-processor MIPS
> > target running in an infinite loop (without an OS) over a serial link
> > with a UART. The host is an x86 machine with Linux OS.
> >
> > The single UART needs to provide connectivity to all the processors
> > on the target and the debug tool needs to do processor specific
> > commands (breakpoints, source-level debug, etc.).
> >
> > Can you guys please point me to any reference material,
> > implementations, etc. for me to get started with this?
> >
> > Thanks much for your help.
> >
> > Regards,
> > -Srinivas
> >
>
>
> ----
> Ramana Radhakrishnan
> Codito Technologies
>
>
prev parent reply other threads:[~2005-06-09 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 17:05 Srinivas Murthy
2005-06-08 18:33 ` Ramana Radhakrishnan
2005-06-09 2:22 ` Srinivas Murthy [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=7cb1293c05060819223c23de35@mail.gmail.com \
--to=codevana@gmail.com \
--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