Hi Peter,
I only tested rproxy on Windows Me, Windows XP and RedHat. People are
using it successfully on Windows 2000, though.
You are doing the wrong thing with telnet, but it has highlighted a bug
in rproxy. When you get the record back from rproxy, you should respond
with "+" to acknowledge it. Anything else will result in the last packet
being repeated. The bug you hightlighted means the repeat is incorrect.
This is irrelevant in normal use, as packets are normally acknowledged
OK by gdb. This is not, therefore, your problem. It is fixed in CVS now,
though.
The source code for most of rproxy is in the mspgcc CVS, but it is now
called gdbproxy. This lacks the MSP430 specific bits of gdbproxy, as TI
do not allow the source for those to be distributed.
I have no idea what your problem is, but it sounds like either gdb or
your use of it is wrong. Did you build gdb yourself, or are you using
one of the tested binaries? What did you use to connect to rproxy? The
correct command would be:
target remote localhost:2000
if rproxy is running on the local host at port 2000.
I really should get around to distributing updated binaries for gdbproxy
this week. The version I have now has several little improvements. I
need to find time for the more major improvements too.....
Regards,
Steve
Peter Jansen wrote:
Hi,
I'm having trouble getting the rproxy debugging stub working. I assume
this is the only option at the moment to use the FET tool from TI?
I'm running the rproxy on a Win 2K box and get a connection to it with
telnet/nc (netcat) and gdb but gdb always time-out.
With a session from nc typing '$g#67' gets
'+$ffff7d8200000000fa69dfffffdb7bd15ff304dbffefdeafdbd8ffdbfffbfebc#46'
but typing '$g#67' again only gets '+$' and then I don't see any
response.
Connecting with gdb and setting 'set debug remote 1' and set
remotelogfile log, I find this in the log file,
w \x03
r <Timeout: 30 seconds>
c quit
the console which rproxy is running from shows this
Remote proxy for GDB, v0.71, Copyright (C) 1999 Quality Quorum Inc.
MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood
Remote Proxy comes with ABSOLUTELY NO WARRANTY; for details
use `--warranty' option. This is free software, and you are
welcome to redistribute it under certain conditions;
use `--copying' option for details.
info: msp430: Target device is a 'MSP430F149' (type 7)
notice: rproxy.exe: waiting on TCP port 2000
notice: rproxy.exe: connected
which all seems quite happy, but it does not seem to answer the gdb
commands propery, or at least the second one any way.
Has anyone got this working? or seen any of the same problems? where
is the source that was used to generate rproxy-0.71?
Thanks,
