after sometime consuming experiments, i was finaly able to add the
msp430 target in an acceptable way to the Eclipse.org IDE.
the attached file goes into a folder "net.sf.mspgcc.cdt" in the existing
"exclipse/plugins" folder. it adds debugger settings for unknown
platforms as the msp430 target is unknown to eclipse...
then in your projects, add a debug configuration using msp430-gdb and a
gdb.ini file. i use the following two files for the sim or gdbproxy.
they have to be adapted for each project, so i'd keep them in the projects.
for the simulator:
---- gdb-sim.ini ------
target sim
load aout.elf
---- end gdb-sim.ini ------
or for a real target:
---- gdb-target.ini ------
ta re :3333
set remoteaddresssize 64
set download-write-size 512
set remotetimeout 999999
mon erase
load aout.elf
---- end gdb-target.ini ------
chris
<?xml version="1.0" encoding="UTF-8"?>
<fragment
id="net.sf.mspgcc.cdt"
name="net.sf.mspgcc.cdt"
version="1.0.0"
plugin-id="org.eclipse.cdt.debug.mi.core"
plugin-version="1.2.1"
match="greaterOrEqual">
<extension
point="org.eclipse.cdt.debug.core.CDebugger">
<debugger
platform="native"
name="%GDBDebugger.name"
modes="run,attach"
cpu="none,msp430"
class="org.eclipse.cdt.debug.mi.core.GDBDebugger"
id="org.eclipse.cdt.debug.mi.core.CDebugger">
</debugger>
<debugger
platform="win32"
name="%CygwinGDBDebugger.name"
modes="run,attach"
cpu="none,msp430"
class="org.eclipse.cdt.debug.mi.core.CygwinGDBDebugger"
id="org.eclipse.cdt.debug.mi.core.CygwinCDebugger">
</debugger>
<debugger
platform="native"
name="%GDBServer.name"
modes="run,attach"
cpu="none,msp430"
class="org.eclipse.cdt.debug.mi.core.GDBServerDebugger"
id="org.eclipse.cdt.debug.mi.core.GDBServerCDebugger">
</debugger>
</extension>
</fragment>
