I've noticed that gdbproxy is chatty but it hasn't really bothered me. There are some things that can be done to speed up the gdb connection to the MSP. I have a gdb.ini file which is automatically run when gdb/Insight first comes up. It is below. I also have a Win-XP shortcut which erases and reprograms the MSP. Together the interface is both pretty easy and fast.
Regards -Bill Knight R O SoftWare PS - A few lines are commented out either for this processor (endian) or for this phase of the project (b main), etc. Some of this was borrowed from my ARM development efforts. ============== contents of gdb.ini =============================== echo Setting up the environment for debugging gdb.\n set complaints 1 #set output-radix 16 #set input-radix 16 # GDB must be set to big endian mode first if needed. #set endian big dir . set prompt (msp-gdb) # Set the filename so we can show MIXED C & assembly. # Must be done before connecting to the target. file test.elf # Connect to msp430-gdbproxy on port 1000 of localhost. target remote localhost:1000 # Reset the chip to get to a known state. monitor reset set remoteaddresssize 16 set remotetimeout 999999 # Increase the packet size to improve upload speed. # Wish this didn't cause an "Are you sure?" popup. set remote memory-read-packet-size 1024 set remote memory-read-packet-size fixed # Load the symbols for the program. symbol-file test.elf # Set a breakpoint at main(). #b main # Run to the breakpoint. #c
