Dieter, your info is definetely helpful and explains some of the behavior that i have been seeing. however, does the same principles hold under linux? thus far i have received replies from people who are using the windows environment. one of the first diffs i saw between windows and linux was the msp430-jtag executable. i dont use this under linux (or maybe its being run in the background) and im not sure if this is strictly used in windows.
> Now when you use the new Eclipse > with the old ini file, you are really trying to connect to > msp430-gdbproxy TWICE and an error results. this behavior seems to fit my case. in my experimentation, i have come across the following. after issuing msp430-gdbproxy --port=2000 msp430, i go to RUN->Debug... (in eclipse) and to the Debuger tab. here i choose the Debugger GDB Server. i installed the mspgcc GDB Debugger plugin from Chris Liechti's website which i think was intended for windows but "seems" to work under linux. i say seems because the option to choose that debugger shows up under the picklist of Debuggers. but when i use this Debugger to run the program, it connects to the gdbproxy (by the "notice: msp430-gdbproxy: connected" message), but am unable to issue any commands like monitor erase, load, etc... on the other hand, if i choose GDB Server for the Debugger, it then gives me the options i am used to seeing ie: Conncetion->TCP; Host name or ip address->localhost; Port number->2000. when i try and connect with these settings and click the Debug button i get the following message inside the console window (elclipse) info threads warning: RMT ERROR : failed to get remote thread list the msp430-gdbproxy gives me the connected message but i am unable to issue any commands ie. it hangs. BUT if i kill the proxy , the error message Watchdog has expired. Target detached. info threads No stack. info threads No stack. info threads No stack. info threads No stack. info threads No stack. appears in the console window(eclipse). from here, i restart the proxy. in the console window (eclipse) i type the command "target remote localhost:2000" and the proxy then gives me the message of being connected. it is here where i have been able to issue two commands that appear to work. monitor reset and monitor erase. the first indication is the output in the console window (eclipse) is in blue font whereas other commands that does nothing (except for target remote localhost:2000) is red. the other indication is by testing to see if the program in the flash has actually been erased. i am running the tcpip stack written by addreas dannenburg so i am able to ping the chip. after the erase under eclispe and a power down/up of the MCU, the chip does not respond to a ping verifying the flash has been erased. so i know that eclipse is communicating with the msp430. but after issuing a monitor erase or monitor reset, it seems like there is a communcation error or eclipse is waiting for a response because issuing another command does absolutely nothing. now with that being said (and i know it was a ton) i want to become clear on a couple of things. to run the program, to i go to Run->Run... or can i also run/debug the program by Run->Debug...? i started working with MCU's about 4 months ago so i am somewhat new. however, my knowledge has grown tremendously and i understand the big picture. details are constantly being filled in as i go. so hopefully my questions are not the "did you search the message board because we already answered this question". and yes, i did without finding anything on linux for this topic. thanks for the help and hopefully this issue can be resolved. aaron
