From: Daniel Jacobowitz <drow@mvista.com>
To: msarasa@fh-konstanz.de
Cc: gdb@sources.redhat.com
Subject: Re: command targe child question , help needed!!
Date: Mon, 03 Mar 2003 14:02:00 -0000 [thread overview]
Message-ID: <20030303140224.GA13554@nevyn.them.org> (raw)
In-Reply-To: <1046699703.3e635eb73833a@webmail.fh-konstanz.de>
On Mon, Mar 03, 2003 at 02:55:03PM +0100, msarasa@fh-konstanz.de wrote:
> Zitat von Daniel Jacobowitz <drow@mvista.com>:
>
> > On Mon, Mar 03, 2003 at 11:02:00AM +0100, msarasa@fh-konstanz.de wrote:
> > >
> > > I think this is the right command I have to use in order to connect gdb
> > with
> > > an external proccess. As said in the help.
> > > But , this is my case:
> > > I've made a simulator of a whole board with it's processor. I can run it as
> > a
> > > process , and I want to know a little bit more about how to connect that
> > with
> > > gdb. In the documentation there's no more said about how does target child
> >
> > > work , and I would like to know, if it's possible , the way this command
> > > works.
> > > The format of the packets in this communication, the way I have to use it,
> > and
> > > how exactly should I modify a program that reads from a simulated UART, to
> >
> > > take the outputs from the gnu.
> > > It's REALLY important for me a little help with this. If I should explain
> > more
> > > about the simulator or the problem , please tell me!! but answer me
> > anyway!!
> > >
> > > I'm totally stopped at this point.
> >
> > Target child is what you would use to debug the simulator. If you
> > want to debug the simulated processor, then you probably want to
> > support the remote protocol in the simulator and use "target
> > remote".
> >
> > --
> > Daniel Jacobowitz
> > MontaVista Software Debian GNU/Linux Developer
> >
>
> This is what I have:
> A gnu development that debugs an architecture. That is , gnu that communicates
> with a physical external board with a hyperstone E1 chip , via serial link.
> I have too a simulator that acts exactly as this board. It reads/writes its
> input/output in a simulated UART. I can chage this to reading/writing
> elsewhere, but, i don't know exactly how to connect this with the gdb serial
> protocol. Should I modify gdb code, or should I use a specific command. I
> thought I could use the target child command to tell the gnu to communicate
> not to the board but to the board simulator process. But maybe I din't
> understand that properly as English is not my languange.
> I think , there are two functions called send_pkt and read_pakt (or similar)
> that I could modify too to force gnu to read/write in a virtual UART.
> But if it's possible I would like to use an option from this target command to
> communicate my simulator program with the gdb.
>
> Sorry for my english , I'll hope you could understand all. Thank you very much
> for your answer!!!
> Best regards! miguel
See my previous answer. Your simulator must support a GDB "remote"
protocol in order to do this (or RDI, etc.).
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-03-03 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 10:01 msarasa
2003-03-03 13:34 ` Daniel Jacobowitz
2003-03-03 13:54 ` msarasa
2003-03-03 14:02 ` Daniel Jacobowitz [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=20030303140224.GA13554@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=msarasa@fh-konstanz.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).