Hi All- I've done some assorted MSP430 development under IAR in the past (circa 2005), and yesterday I attended TI's 430-Day promotion. Seeing all the new devices and capabilities has got me interested in working with the '430 again, not to mention the free EZ430 tool at least whets my appetite to tinker!
However, since my last '430 project closed, I've switched to 100% Linux (Ubuntu 6.06LTS) for my day-to-day and development work. I'm writing to ask, generally speaking regarding the Linux toolchain, "How's it going?" As I enter the processor downselect phase of my next project - one that may end up becoming my bread-and-butter as early as next year - I'm definitely including "Linux toolchain availability and maturity" in the mix. This leaves me with a few questions: 1) Where can I go for a definitive list of supported target processors? The official documentation only lists older targets from the 1xx and 3xx families, but a quick Google search shows embedded systems blogs announcing 2006 releases supporting some newer 2xx chips. Skimming the release notes and readme files in CVS doesn't net me any answers either. Is there a master list somewhere? 2) How difficult is it to add new target support? I've always been firmly rooted in the class of "compiler user", but since I'll be using mspgcc for a commercial project (which in turn will be paying my mortgage) I'm interested in the possibility of contributing. Can someone give me a bird's eye primer on the general steps that are involved in adding a new target processor? [depending on the answer to Q#1, there may be no target processors awaiting implementation...in this case, I'm still interested, since it appears there are a lot of new processors slated for release by TI in 2008.] 3) Cruising through the recent archives of this list, it seems there are a handful of people who are using mspgcc successfully for active development of mainstream products. From these folks, I'm interested in hearing your take on the maturity of the toolchain... What % of your seat time do you spend coding for the target vs. troubleshooting toolchain issues? If you've got experience with both mspgcc and a commercial package, how do they compare? _Every_ toolchain has its issues, and I have no expectation that mspgcc should be any exception to this, so I think this is a reasonable question. That said, if I'm out of line asking that in this setting, feel free to put me in my place! 4) Finally, what is the appropriate scope for this list? Are threads restricted to strictly mspgcc-related issues, or are target behavior/coding questions also entertained? I _do_ hope to use mspgcc in some capacity, so I figured I'd ask this now rather than embarass myself later! :) Thanks in advance to all who reply, Cheers, Dave (Rochester, NY) -- "I am sir Oregano, Duke of Chutney!"
