Chris Liechti wrote:
> - .d43 cannot be converted to other formats by tools from mspgcc (it's a 
> proprietary format without documentation)
>

True, though there is my attempt at reverse engineering it somewhere
in the CVS on sourceforge. You could make a .d43 to Srecords converter using
that as a starting point in very little time.

I did once do a hack to 'objcopy' to write .d43 files in a convenient manner.
However, this worked the other way around in that it took the ELF output of
mspgcc and tried to make a .d43 that could (usually) be uploaded and run by
C-SPY.

I've totally ditched all this ever since Steve Underwood got gdbproxy working
early this year, and I've never looked back. I'm not sure if my .d43 writer
ever made it into offical binutils sources. It didn't translate the symbol
table anyway - just the code & data segments.

> - "Srecord" is not used in the MSP430 world (at least i havent heard 
> of). you probably mean "intel hex" format, also refrenced to as "ihex"
>

Srecord is effectively "motorola hex" format. Similar to "intel hex" but
different in detail. I'm sure binutils can generate it, though why anyone would
want to I'm not sure (in the msp430 world).

> - if you use the GCC toolchain, i.e. msp430-gcc you will get "elf" 
> files. those can be converted to "intel hex" with msp430-objcopy.
> our tools to debug and/or download understand both, elf and ihex (and 
> other formats as well, but no .d43)
>

Modulo my comments above about .d43. But you really don't want to generate
.d43, it's only possible use is to feed to C-SPY, and that's a complete crock
compared with gdb (or insight or whatever).



--

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" )



Reply via email to