Hi,
the file you asked for is the batch file that i am using to flash my
device after successful make and to start up msp430-gdbproxy.
f:
cd f:\programme\mspgcc\bin
msp430-jtag -e f:\programme\eclipse\workspace\[project]\[main].elf
msp430-gdbproxy --port=2000 msp430
Once the device has been programmed and msp430-gdbproxy has started, i can
start the debug session inside Eclipse. Eclipse will then start the msp430-gdb
and tell it how to connect to the msp430-gdbproxy, which elf-file to load and
where to find the ini-file. Eclipse will also tell msp430-gdb the options for
start address and so on that you defined in the Eclipse Debug Options panel.
Make is also automated by Eclipse, if you place the makefile inside the
workplace/project path. Example makefiles are in the mspgcc installation path
under /examples/[project]. By the way in my makefile i have all complete
absolute paths to the mspgcc binaries. Then you can use menu commands in
Eclipse to trigger make and i think Eclipse triggers make also before starting
a debug session. Eclipse will nicely locate errors in the source files!
If there is a problem with make, you can first try it by hand before doing it
under Eclipse.
I am no expert, neither for mspgcc nor for Eclipse. For me they are only tools.
I also tried the Insight debugger, but Eclipse works better. The combination of
Eclipse and mspgcc can fully replace a commercial solution, if you keep an eye
on mspgcc optimization artefacts.
Regards
Dieter Teuchert
