![]() |
mspgcc |
Make sure that the Binary Parser is set to Elf Parser
,
see the dialog in 'Project -> Properties'.
Now copy the gdb ini file sto the project folder. These files have to be edited so that they load the elf file of the current project.
gdb-target.ini: this files contains the commands to run it on a real target (using gdbproxy)
gdb-sim.ini: this files runs the program in the gdb simulator
Then create a new debug configuration:
Click on „New“ and update the settings as shown in the
images:
Name: (Project file name)
Project: (Project name)
C/C++
Application: (must be the name of the resulting ELF file, so that the
debug info is found)
GDB debugger: „msp430-gdb“
GDB command file: choose one of the ini files for the target or simulator
To speed up the debugging process, one can switch off the auto update features. Usualy it would upload lots of memory and registers when a breakpoint is hit. But in the single step mode it slows down a bit too much. But one has to rember to manualy refresh the views...
"Remove terminated launches when a new launch is
created"
in the dialog in the Window->Preferences
,
"Debug" Tab.
Activate: "Remove terminated launches when a new launch
is created"
in the dialog in the Window->Preferences
,
"Debug" Tab.