I'm working to update the mspgcc-based tool chain to support the CC430F5137 and related chips on TinyOS. Since the CC430 family doesn't have more than 32KB of memory, I'm ignoring the MSP430X branch. Similarly, I'm leaving aside the mspgcc4 fork, though I plan to go back to that. However, I am having to add some of the missing MSP430 5xx peripheral modules, including (first off) the power management module.
Of course, I'll make the patches available to whoever wants them as soon as I'm convinced they produce working code. For now, I had a couple questions: * On mspgcc's sourceforge page, the git repository appears to be identical to the cvs repository except for some rearrangment. I'm based on the trunk cvs repository. Is that a problem? * Has anybody done significant work on 5xx peripherals that has not been checked into the CVS repository? I notice the MSP430X branch has outdated files in msp430-libc/include (e.g., msp430/timera.h), which is one of the reasons I'm not using it. * If there's a gatekeeper or other developers active in this area who would like to coordinate efforts, please let me know. * Also, if anybody's had any luck with gdb talking to the MSP-FET430UIF with TI's firmware revision 20401004 I'd appreciate some pointers. Right now, neither mspdebug nor fetproxy seem to know the right dialect, and as I understand it msp430-gdbproxy is a non-starter for newer chips on Linux. Any other suggestions to help speed this to success, including a pointer to a pre-existing solution, would be most welcome. Peter
