From: Daniel Jacobowitz <dan@debian.org>
To: Mark and Janice Juszczec <juszczec@hotmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: cross debugging r3912 cpu with gdb
Date: Sun, 7 Dec 2003 22:10:39 -0500 [thread overview]
Message-ID: <20031208031039.GA17991@nevyn.them.org> (raw)
In-Reply-To: <Law10-F80XN3su1U6s400015b8a@hotmail.com>
On Mon, Dec 08, 2003 at 12:02:14AM +0000, Mark and Janice Juszczec wrote:
>
> Daniel
>
> you wrote:
> >
> >You left out lots of details.
> >
>
> Oops. My bad.
>
> >What operating system is the r3900 running?
>
> Yes its linux. kernel v2.4.0-test1-acc22
>
> >From the list name, I assume it's Linux/MIPS. So why did you configure
> >for mips-idt-ecoff?
> >
> Hmmmmm. Good question. The gdb docs say I have to if I want to use the
> MIPS remote debugging protocol.
>
> I did try --target=mipsel-elf-linux and --target-mipsel-linux. I got the
> following targets:
>
> (gdb) help target
> Connect to a target machine or process.
> The first argument is the type or protocol of the target machine.
> Remaining arguments are interpreted by the target protocol. For more
> information on the arguments for a particular protocol, type
> `help target ' followed by the protocol name.
>
> List of target subcommands:
>
> target async -- Use a remote computer via a serial line
> target cisco -- Use a remote machine via TCP
> target core -- Use a core file as a target
> target exec -- Use an executable file as a target
> target extended-async -- Use a remote computer via a serial line
> target extended-remote -- Use a remote computer via a serial line
> target remote -- Use a remote computer via a serial line
> target sim -- Use the compiled-in simulator
>
> I figured mips should show up, so I guessed they were incorrect. Even so,
> I tried connecting with both and got the same results:
>
> (gdb) target async /dev/ttyUSB0
> Remote debugging using /dev/ttyUSB0
> Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet:
> $Hc-1#09...Sending packet: $Hc-1#09...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Sending packet: $qC#b4...Sending packet: $qC#b4...Sending packet:
> $qC#b4...Sending packet: $qC#b4...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Sending
> packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Timed out.
> Timed out.
> Timed out.
> Ignoring packet error, continuing...
> Couldn't establish connection to remote target
> Malformed response to offset query, timeout
>
> Any idea what that all means?
>
> >If you're using gdbserver, then you want target=mips-linux and "target
> >remote", not "target mips".
> >
>
> I'm not using gdbserver. It won't fit on my pda if I include kaffe and
> its associated files.
Then what ARE you using on the target?
You have to connect to some particular debug stub. That determines
what protocol to use.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-08 3:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 0:02 cross debugging r3912 cpu with gdb Mark and Janice Juszczec
2003-12-08 0:02 ` Mark and Janice Juszczec
2003-12-08 3:10 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 12:48 Mark and Janice Juszczec
2003-12-08 15:39 ` Daniel Jacobowitz
2003-12-07 22:28 Mark and Janice Juszczec
2003-12-07 22:54 ` Daniel Jacobowitz
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=20031208031039.GA17991@nevyn.them.org \
--to=dan@debian.org \
--cc=juszczec@hotmail.com \
--cc=linux-mips@linux-mips.org \
/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