Steve Hosgood wrote:
Nice to see a happy customer, Steve, but sadly I can't say the same. I've
got the rproxy version of the code from last week on a linux 2.4.20-pre2
machine. It loads up, spots the FET adapter, and correctly identifies the
MSP430-149F chip at the other end.
After is identified the target chip does it say "listening on port
4411"? If so it really should be. You can check with netstat -anp on a
Linux machine. I think "netstat -an" works on Windoze too.
Then I run msp430-gdb with the magic incantations:
set remoteaddresssize 64
set remotetimeout 999999
target remote localhost:4411
..but after this last command I get a 30 second wait followed by a "timed
out" message.
When you start gdb does rproxy say it has connected? If so, the initial
message exchange must be failing for some reason. What platform are you
using?
Any attempts to look at the code in the MSP430 result in various "code not
running" type of messages. Sadly I can't give you literal reports at the
moment as I don't have the kit plugged in temporarily.
This looks like great things are afoot, but I'm just not quite able to get
it working!
I know that feeling well :-)
Regards,
Steve
