Aaron Peterson wrote:
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.
i use msp430-jtag to download and execute if i'm not debuggig.
when i debug, i use the ini files that come with the plugin (see eclipse
help->mspgcc) these ini files contain the lines to erase the target and
download the data, along with some options to optimize the messages
between gdbproxy and gdb.
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 dont use the GDB server. i didn't work for me, or i did not try hard
enough...
i use the normal debugger that is available under then name "mspgcc ..."
and connect in the gdb.ini file. (in eclipse 2.x / cdt 1.x there is not
a "mspgcc" debugger but rather the cygwin (win32) and normal debugger
are enabled for all targets)
> 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 never implemented anything into these plugins that would restrict them
to a certain platform, nor are they designed to run a only on one
platform ;-)
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)
but the "gdb server" option tries to connect to a target that already
contains the software. which is usualy not the case in the embedded world.
also, gdb has no support for targets that need to be erased before they
can be loaded.
reasons to use the normal debugger with an ini file to connect, erase
and download.
chris
