An implementation of the MSP430.dll software interface that supports the TI MSP-FET430UIF is provided in CrossWorks for MSP430. The Windows implementation is provided by TI. The Linux, MacOS and Solaris implementations are provided by Rowley Associates.

For the Windows and Linux implementations the Port Name property should refer to the USB VCP (virtual COM port) that is created when the MSP430-FET430UIF is plugged in. If the default Port Name value USB is specified on Windows the first MSP430-FET430UIF device found is used and on Linux the serial port /dev/ttyUSB0 is used.

On Windows implementations you can right click on the target in the targets window and select the virtual COM port to use if there is more than one MSP-FET430UIF connected to the PC.

For the MacOS and Solaris implementations the Port Name is ignored, the first MSP430-FET430UIF device that is found is used i.e there is no way to use more than one MSP430-FET430UIF.

On Windows and Linux device drivers are provided by TI to create a VCP when the FET430UIF is plugged in. On MacOS and Solaris there are no VCP drivers provided by TI. The MSP430-FET430UIF uses a TI TUSB3410 as a USB interface chip which needs to have a program loaded onto it when it is plugged in (this is done by the device drivers on Windows and Linux). For MacOS this process is handled by CrossWorks For MSP430 when you connect to the target. For Solaris you will need to load the TUSB3410 each time that you plug in the MSP430-FET430UIF by running the program ~/.rowley_associates_limited/crossworks_for_msp430/packages/targets/msp430/loadtusb3410 from a command shell and then following the instructions that are output.

The Windows implementation supports upgrading the firmware of the MSP-FET430UIF. The Linux, MacOS and Solaris implementations do not support firmware upgrade i.e. you will need access to a windows machine to upgrade the firmware of the MSP430-FET430UIF.