> This seems to me to be a round-about method. If all you want to do is
> program the msp430 using C-spy, then just use hex files - objcopy will do
> elf-to-hex conversion, and C-spy will happily read and program it.
>
I wasn't aware of that route. However...
> If you are looking for a slightly more capable debugging system using C-Spy,
> then as far as I know the best method at the moment is to use objdump to
> generate a copy of the object code in iar assembler format, with the
> original C code embedded as comments. This can then be assembled and
> compiled using iar's free tools, and loaded into C-Spy.
>
I used to do exactly that. But, it required a good few steps that couldn't
be done by the makefile under linux (which was annoying), and certainly in the
early days the IAR assembler output of objdump was quite buggy (which yielded
some very inpenetrable bugs in running code). I contributed quite a few
disassembler fixes for such problems myself back in June/July last year.
However, none of these routes offered the possibility of letting C-SPY use
a symbol-table properly. That's what I'd hoped the direct creation of a
UBROF file would permit. Hence all the effort to that end. Of course I got
overtaken eventually by native linux support for JTAG downloads, but having
said that, I've not yet actually managed to get msp430-gdb/rproxy to work.
And the non-linux/non-i386 people never will until the JTAG interface software
goes open source.
--
Steve Hosgood |
st...@caederus.com | "A good plan today is better
Phone: +44 1792 203707 + ask for Steve | than a perfect plan tomorrow"
Fax: +44 70922 70944 | - Conrad Brean
--------------------------------------------+
http://tallyho.bc.nu/~steve | ( from the film "Wag the Dog" )
