I have built gdb as a cross compiler
GNU gdb 20000502
This GDB was configured as "--host=i686-pc-linux-gnu --target=mips64vr4300-elf".
I am trying to load my program to the target. I have issued the following
commands:
set remotebaud 9600
set mips saved-gpreg-size 32
target remote /dev/ttyS0
set debug remote 1
set remote memory-write-packet-size 34
set remote memory-write-packet-size limit
set remote X-packet disable
load
Things go along nicely until ...
Sending packet: $M800001c8,4:00000000#2b...Ack
Packet received: OK
Sending packet: $M800001cc,4:0080023c#96...Ack
Packet received: OK
Sending packet: $M800001d0,5:dc01426408#05...Ack
Packet received: OK
Sending packet: $M800001d5,5:0040000000#8e...Ack
Packet received: OK
Sending packet: $M800001da,2:0000#93...Ack
Packet received: OK
Loading section .text, size 0x9010 lma 0x800001dc
Sending packet: $M800001dc,4:00688040#71...Ack
Packet received: OK
Question:
Since I forced the packet size so that I would get exactly 4 bytes in
a transfer, why did gdb decide to send 5 bytes, 5 bytes, 2 bytes instead of
4, 4 and 4?
I am running eCos on the other side, with gdb-stub monitor. For some reason,
odd byte memory requests corrupt things. (different bug list)
Is there a better way to download an elf file to my target for
debugging? I tried using X-packets, but they were too large, and
overflowed by input buffer. (No Xon/Xoff or flow control in gdb-stub).
Thanks for any help or advice or how I can fix this bug.
-- Warren
Warren J. Jasper
[EMAIL PROTECTED]
