On Thu, Mar 4, 2010 at 1:08 PM, Mark Rages <markrages@gmail.com> wrote:
> The problem with the TI's USB programmer / debugger is the usb->serial
> chip they use, the tusb3410.

I have a TI ADC evaluation board (with the MMB3 base board and various
ADC/DAC daughter boards) in front of me which is also using
the TUSB3410 together with a MSP430F449.

> A problem with the MSP430 is a general supply shortage right now. It
> doesn't seem like a good time to introduce a high-volume, low-cost
> version when they have difficulty keeping up with the supply now. =A0Or
> maybe MSPs without analog peripherals can be produced at a different
> fab.

TI seems to suffer the supply shortages right now. So companies
like ADI is promoting their parts to replace TI parts. Even Microchip
is looking at replacing certain TI parts due to supply shortage issues
with TI.

But nowadays, a lot of vendors are having delivery issues. I
do not think the economy is really getting that good. But the
delivery issues are really there.

> There is a GCC4 port of the mspgcc toolchain at
> http://mspgcc4.sourceforge.net/. =A0Development of mspgcc is rather
> fragmented. =A0 From reading the generated code, I would say that mspgcc
> does a better job then SDCC does for PICs.

GCC for MSP430 is of course better than SDCC for PIC. ;-)

It would be good that MSPGCC is integrated into the main
gcc line. But I think that would not happen for a while.

-- =

Xiaofan http://mcuee.blogspot.com

-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist