Re: [Mspgcc-users] msp430-elf-gcc upcoming release

[DJ D. <dj...@re...>]

> > It uses the TI CIO interface.
> 
> Interesting; is there any public documentation on how to use that?

Not that I know of.

> An option to build MSP430 newlib with the standard system interface
> would be even better.

I don't know of a "standard" interface.  Each chip I've done has done
something a little different, depending on what the architecture
provided that could be hooked.

> It's not clear to me why a TI-specific interface is desirable to
> anybody other than TI.  Part of the point of using a GNU-based
> toolchain is portability across processors (even if vendors would
> prefer that we be locked to their offerings).

They use the CIO interface across all their processors, and it lets
you debug gcc-produced executables in their IDE/simulator/hardware.

As for reverse-engineering it... the sources are in libgloss and the
simulator ;-)

> I saw that, but it only mentioned two specific flags, compared with
> the nine that are used by gcc-arm-embedded (though they're using a
> forked newlib).  However if nobody actually uses newlib for
> applications on MSP430 yet, perhaps the community will come up with a
> set of flags that work.

There are far more than nine flags available, too.  Users almost need
to check them all and decide which features they're using in their app
and which they aren't.