The text below is accurate except that the patches have been modified to be more consistent with TI naming conventions (specifically the names of the include files), and the repository has been removed and replaced by a git repository at:
git://oshan.git.sourceforge.net/gitroot/oshan/msp430-libc Baselined stable releases of the msp430-libc are hosted at https://sourceforge.net/projects/oshan/files/ in the msp430-libc directory. I believe this version will be an option in future mspgcc4 builds. The binutils and gcc patches have also been integrated into mspgcc4. I'd like to make one last plea for fork-avoidance in the library. The mspgcc4 project, which I've moved to entirely, uses subversion. The mspgcc project has both Bazaar and CVS repositories, and it appears the CVS one has recently seen activity in the msp430-libc area. I had not been tracking those changes, but I'll start trying to do so. But wouldn't it be nice if there was just one version somewhere? Heck, I'll even volunteer to maintain msp430-libc hosted from this project if somebody adds me as a developer and I can use git. There's no reason why the standalone library shouldn't work with mspgcc as well as mspgcc4; up to two weeks ago that's what I was using. Peter On Wed, Jan 13, 2010 at 11:43 AM, Peter Bigot <p...@peoplepowerco.com> wrote: > In support of OSHAN <http://sourceforge.net/projects/oshan/>, an open > source home area network targeted to embedded devices, I've implemented > CC430 support in MSPGCC. It is currently available for download from the > OSHAN project page on SourceForge, in a Bazaar repository based on the > MSPGCC one at http://sourceforge.net/projects/mspgcc/develop. You can get > a copy using: > > bzr checkout bzr://oshan.bzr.sourceforge.net/bzrroot/mspgcc-core.cc430 > > For convenience of those who don't want to deal with Bazaar, I've also made > available a tar file with the current contents, and a patch relative to the > trunk at the time I started, at: > > http://sourceforge.net/projects/oshan/files/ > > A set of examples that work on the TI EM430 developer board are also > available from the OSHAN project on > SourceForge<http://sourceforge.net/projects/oshan/files/> > . > > I apologize for the lack of convenience, but I'm not building releases of > this: it's been tested on Linux (Fedora 9), and you can build it with the > buildgcc.sh script that comes as part of the mspgcc-core branch. The > binutils patch is for 2.19.1, and the gcc changes are for 3.2.3, but the > bulk of the work was in msp430-libc, so supporting the port in other > versions of gcc should be pretty easy. > > My hope is the current MSPGCC maintainers will have a chance to look over > the changes and incorporate them into the mainline; I don't want yet another > forked MSPGCC. However, I'll maintain the repository that's hosted in the > OSHAN project until the changes are integrated somewhere more official. If > you have problems, please mail mspgcc-us...@lists.sourceforge.net. > > Notes on the changes are below. > > CC430 Support in MSPGCC > ======================= > > This directory contains patches to support the TI CC430 System-on-Chip > family. These chips incorporate a MSP430-5xx microcontroller with a CC1101 > radio. > > Only the gcc/gcc-3.2 compiler patches have been updated for CC430 support, > but the bulk of the effort is in msp430-libc, so adapting this for a > working > version of a different compiler should be trivial. See the diffs for the > necessary steps. > > Relative to the baseline MSPGCC system, the patches in this directory > incorporate: > > * Updates to binutils-2.19.1.patch to handle the eight defined CC430 chips > > * Updates to the gcc/gcc-3.2 configuration files to handle the CC430 chips > > * Addition of a <cc430.h> include file for mspgcc-libc. > > * Additional MSP430-5xx module support from JMGross <msp...@grossibaer.de > >, > including new support for: > - CRC16 > - Power Management Module > > * Additional MSP430-5xx/CC430 module support from Peter Bigot > <p...@peoplepowerco.com>, including new support for: > - Port Mapping Control > - Special Functions > - Advanced Encryption Standard > - RF1A CC1101 Radio Module > > * Addition of mnemonic defines matching TI headers (e.g., TASSEL__TACLK > mapping to TASSEL_0). > > * Assorted fixes for watchdog support on processors that do not map WDTCTL > to 0x0120. > > Build and install in the normal way. > >
