> That doesn't really help the rest of us, though. Yup, I've complained to TI about that. I'll bring it up again.
> I'm interfacing with other external hardware including LCDs and FAT > file systems, and I want to re-use the standard libc interface at > the application layer. Could you elaborate on this? Are you talking about real hardware talking to real peripherals, or is there a host involved? > Like Mark, one of my needs is for input as well as output. For ARM, I > can take a binary toolchain from launchpad with a pre-built newlib and > substitute a new system interface that meets my requirements. As long > as I can do the same thing for the msp430 one, I'll have no issues > with the default solution being CIO. None of the CIO stuff interferes with the ANSI routines in newlib/libc. You still use printf() and fopen() etc. The CIO code is at the very bottom in libgloss, where it provides a CIO-specific write() call. If you have some other low-level I/O routines, like a serial port or lcd, just provide your own read() and write() functions and the rest of newlib will "just work". ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
