RE: Remote communication error

Lan Zhang
2004-09-24T22:25:32Z

I can access this address:

(gdb-usb) x/i 0xec2d0
Sending packet: $mec2d0,4#5b...Ack
Packet received: 1500000a
target_xfer_memory (0xec2d0, xxx, 4, read, xxx) = 4, bytes = 15 00 00 0a
0xec2d0 <FirstMode+32>: beq 0xec32c <FirstMode+124>
(gdb-usb)

The stop address is randomly, it can stop at any address, and I can
access (read and write) any memory address before stopped. If I restart
over, it would pass the last stopped address and stopped at a different
place. That is why I think I didn't add my USB interface correctly into
the GDB, or on my target.

Thanks a lot.

Lan

-----Original Message-----
From: Andrew Cagney [mailto:cagney@gnu.org]
Sent: Friday, September 24, 2004 6:09 PM
To: Lan Zhang
Cc: gdb@sources.redhat.com
Subject: Re: Remote communication error

> w +
> c set debug serial 1
> c n
> w $mec2b0,4#59
> r +$04e02de5#29
> w +$mec2b4,4#5d
> ...
> ...
> ...
> w +$mec2cc,4#8d
> r +$000050e3#bd
> w +$mec2d0,4#5b
> r <Error: Connection timed out>

If this is deterministic then it looks like an attempt to read 0xec2d0
hangs your remote stub / machine :-(

Instead of a NEXT, try:
x/i 0xec2d0
after that, you've got a hardware problem.

Andrew

> r <Error: Connection timed out>