Re: gdb-h8-stub... please help.

[Daniel Jacobowitz <drow at mvista dot com>]

On Mon, Jul 15, 2002 at 10:20:29AM -0400, Peter Barada wrote:
> 
> >(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.

For the record, 'm' is memory read, not binary download.  It looks like
binary download was already marked unsupported, or something like that.

> 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... 

At a guess, "Junk: @".  The stub is sending something out the serial
port, or the application is being allowed to write to the serial port
while GDB is waiting for a result.


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer