Michael Korobov wrote:
Dear Sirs!
I have a question to you since I can't find answer to this one. I'm learning
to use the mspgcc compiler for the MSP430 microcontroller series and one of
most important things I think I have to do is debugging.
yeah, but a debugger is not always the best thing for embedded targets...
setting a breakpoint in your real time algorithm may not give you the
results you realy want (timer still running, interupts arriving and not
being processed etc.).
i often use toggling pins and an oscilloscope, then the next level are
debugging outputs over the serial port.
of course a debugger with single stepping etc may be nice in some rare
cases - the most useful feature is that you can stop the target and see
in which loop it hangs ;-)
> But msp430-insight
hasn't features I need (e.g. external pin stimuli etc.) IAR EWB instead has
these features
sure? not all features that you see in the menu are supported by the
msp430 backend, from what i read.
external pin stimuli are something for the simulator anyway, right?
but the object code generated by mspgcc allows only debugging
at the assembler level. Is it possible to convert the .elf format (or other
wrong. you just need to compile with the -g flag and you get full source
level debugging in gdb if you load the elf file.
if you mean that you cannot load an object file with debug info into
C-SPY, complain at IAR as they use a propietary, undocumented format and
do not load other formats than their own and ihex...
one generated by mspgcc) in the such way that allows debugging by IAR EWB at
the C-level? In examples I found the directory (leds) that contains (in the
makefile) the following strings:
iar: ${NAME}
msp430-objcopy -O msp430asm ${NAME} ${NAME}.s43
a430 -r ${NAME}.s43 -o ${NAME}.r43
xlink -cmsp430 -r $(NAME).r43 -o ${NAME}.d43
that is theoreticaly. i put it there but i never used it ;-)
people on this list used that feature some time ago and i put that what
i read in the makefile so that it written down somewhere.
As I understand the second line of this code produces the asm code from .elf
file. But when I trying to use this command binutil says to me that
msp430asm is the invalid BFD target. Supported BFD targets actually don't
contain this one (msp430asm). What am I doing incorrect?! You know, this
example contained in mspgcc and I didn't change it.
that feature is not in the official binutils build. it was an
experimental addon in the binutils patches from mspgcc.sf.net
from what i read it did not allow for real source level debugging
anyway. it was for debugging assembler but with the c code as comment in
the source files...
Thank you for any information you can give me.
Sincerely yourth,
Michael Korobov, National aerospace University, Kharkov, Ukraine
chris
