From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: aminayev@yahoo.com
Cc: gdb@sources.redhat.com
Subject: Re: gdb-h8-stub... please help.
Date: Mon, 15 Jul 2002 07:20:00 -0000 [thread overview]
Message-ID: <200207151420.g6FEKTq23706@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <20020714055803.62733.qmail@web13505.mail.yahoo.com> (message from Alexei Minayev on Sat, 13 Jul 2002 22:58:03 -0700 (PDT))
>(gdb) cont
>Continuing.
>Sending packet: $m18,2#34...Ack
>Packet received: 0000
>binary downloading NOT suppported by target
>Sending packet: $M18,2:5730#1d...Ack
>Packet received: OK
>Sending packet: $Hc0#db...Ack
>Packet received:
>Sending packet: $c#63...putpkt: Junk: @
>Timed out.
>Packet received: S05
>Sending packet: $c#63...putpkt: Junk:
>Timed out.
>
>end quote.
>I would appreciate any light that you can shine on this. Do I need to patch
>GDB? Do I need to process binary downloading (I don't do it now)? Add extra
>cases to my command switch?
>
GDB tried the binary download('m'), and when that failed, fell back to
hex download('M'). So you don't need to add binary download.
To me it looks like the problem is in the stub since the communication
between the host and stub is not working correctly. If you have a
spare serial port on the target, add code to the stub to dump each
packet that is recieved and sent. Run through the sequence again, and
then decode the packets in the debug output and compare it against the
documentation. I'm sure you'll eventually find what's wrong in your
stub...
--
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax)
next prev parent reply other threads:[~2002-07-15 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 22:58 Alexei Minayev
2002-07-15 7:20 ` Peter Barada [this message]
2002-07-15 7:35 ` Daniel Jacobowitz
2002-07-15 9:26 ` Andrew Cagney
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=200207151420.g6FEKTq23706@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=aminayev@yahoo.com \
--cc=gdb@sources.redhat.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