Hi, I am running into problems keeping msp430-gdbproxy connected to the target while using msp430-insight (msp430-gdb.exe) under win32. I am using the TI spy-bi-wire FET (the USB side of the eZ430-RF2500 development kit) as the programmer/debug interface to a msp430f2013, which is working reliably for flashing and running new code on the target via msp430-jtag.
But when running gdbproxy with Insight to debug, the connection between gdbproxy and the FET appears to bomb out when msp430-insight closes and re-opens the connection to gdbproxy, as it seems to do routinely in the course of its business. E.g. attempting to download and run an executable fails; with gdbproxy output: --- P:\project>msp430-gdbproxy --debug --port=2000 msp430 USBFET Remote proxy for GDB, v0.7.1, Copyright (C) 1999 Quality Quorum Inc. MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood GDBproxy comes with ABSOLUTELY NO WARRANTY; for details use `--warranty' option. This is Open Source software. You are welcome to redistribute it under certain conditions. Use the '--copying' option for details. debug: msp430: msp430_open() debug: MSP430_Initialize() debug: MSP430_Configure() debug: MSP430_VCC(3000) debug: MSP430_Identify() info: msp430: Target device is a 'MSP430F20x3' (type 52) debug: MSP430_Configure() notice: msp430-gdbproxy: waiting on TCP port 2000 notice: msp430-gdbproxy: connected debug: msp430: msp430_connect() debug: MSP430_Registers(READ) debug: msp430: msp430_current_thread_query() debug: msp430: msp430_offsets_query() debug: msp430: msp430_set_gen_thread() debug: msp430: msp430_read_registers() debug: MSP430_Registers(READ) debug: msp430: msp430_write_mem(0xF800, ptr, 0) debug: msp430: msp430_write_mem(0xF800, ptr, 0) debug: MSP430_Memory(WRITE) debug: msp430: msp430_write_mem(0xF824, ptr, 0) ...etc... debug: msp430: msp430_read_mem(0xFA24, ptr, 0, ptr) debug: MSP430_Memory(READ) debug: msp430: msp430_kill() debug: MSP430_Reset(ALL) debug: msp430: msp430_close() debug: MSP430_Reset(ALL) debug: MSP430_Close() info: msp430-gdbproxy: session killed. Will wait for a new connection debug: msp430: msp430_open() debug: MSP430_Initialize() debug: MSP430_Configure() debug: MSP430_VCC(3000) debug: MSP430_Identify() error: msp430: Could not read device Register (33) debug: MSP430_VCC(0) error: msp430: Not supported by selected Interface or Interface is not initialized (34) debug: MSP430_VCC(3000) error: msp430: Not supported by selected Interface or Interface is not initialized (34) debug: MSP430_Reset(ALL_RESETS) error: msp430: Not supported by selected Interface or Interface is not initialized (34) debug: MSP430_Close() error: msp430: Not supported by selected Interface or Interface is not initialized (34) Assertion failed: !msp430_status.is_open, file target_msp430.c, line 745 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. --- The 'global variable workaround' (http://www.nabble.com/gdb-problem%3A-sect_index_data-not-initialized-td9076831.html) already is present in the .elf. As seen in other random forums posts scattered around the web, I created a gdb.ini file (does msp430-gdb.exe honor this?) and populated it with: set remoteaddresssize 64 set remotetimeout 999999 target remote localhost:2000 monitor erase all ...with no improvement to the problem at hand. Has anyone seen this problem before, or better yet can suggest a fix? Thanks, Tim / Drmn4ea -- View this message in context: http://www.nabble.com/Connection-failure-during-close-and-re-open-msp430-gdbproxy-by-msp430-insight-tp22129473p22129473.html Sent from the MSP430 gcc - Users mailing list archive at Nabble.com.
