Well, I still don't have this playing correctly. But it is closer. gdbproxy will connect and find the device... although sometimes I have to diconnect the FET tool while it is trying at the beginning.
I get msp430-gdb to connect with msp430-gdbproxy. I get all notice, debug and info messages up until I try to erase memory (monitor erase all).. in gdb i get Erasing taget flash - all ...MSP430 error: Could not preserve/resotre device memory (12) Protocol error with Rcmd gdbproxy gives: debug: msp430: msp430_remcmd() debug: msp430: msp430_rcmd_erase() error: msp430:Could not perserve/restore device memory (12) additional visual info. the FET tool has the blinky led program in it. Note this is anecdotal and not perfectly repeating. If i forget to disable cupsd, it stops blinking ... then restarts when I select a different window than where I started gdbproxy. If i kill cupsd and run gdbproxy with the --debug option... it often does not restart blinking until after the rcmd_erase failure. what else could be interfering with the parallel port? any other ideas? jim
