This seemingly strange error message deserves an explanation. The error message is quite right in that when attempting to identify the MSP430 attached, the FET430UIF couldn't identify it. What's more, the response is authoratative, there was no procedural error whilst trying to identify the device.
To try to rectify this, there are a few things to try:
- Make sure you have only a single FET430UIF plugged in to the USB ports of your PC. If the target interface's Port setting is USB then the TI MSP430 DLL tries to match the device name in Windows' Device Manager to the format that it thinks the VCP name should be in. If there is more than one FET430UIF plugged in, the MSP430 DLL will pick one of them, but it's not guaranteed to pick the one with the numerically lowest COM port assigned. So, just to be sure, check you have only one FET430UIF plugged in and it shows up as a FET430UIF virtual COM port in Device Manager.
- Make sure the FET430UIF is plugged in and that it's connected to a target board. Silly, I know, but just do it.
- Make sure that you have enabled the regulator and powered the MSP430, if you intend to power the MSP430 from the FET430UIF. You should check the Vcc setting in the Connection group of the FET430UIF target interface's properties. The default for this is 3.3V, but you may have changed it.
- Make sure that you are attempting to connect using the correct protocol. In CrossWorks V2 there are two FET430UIF target interfaces, one named TI MSP-FET430UIF (JTAG) and one named TI MSP-FET430UIF (SBW). If your board is set up for Spy-bi-Wire, use the SBW interface, and if it's JTAG then use the JTAG interface. There is nothing special about these two interfaces, they just have their properties set correctly for JTAG and SBW interfaces.
- Make sure that the FET430UIF DLL path is correctly set. The default for this is $(PackagesDir)/targets/msp430/MSP430$(HostDLL) which specifies the MSP430 DLL delivered in the latest MSP430 package. When TI deliver new DLLs, you might be able to change this to a "patch" DLL. Just put it back to the default and try again.
- Note that the DLL and the FET430UIF firmware must be synchronized. CrossStudio will automatically upgrade the firmware for you. If you use an out-of-sync DLL and firmware combination, all manner of strange things can happen.
- Make sure the target that you have is supported by CrossStudio. There are some devices that customers are privileged to receive before we do. If you're trying one of those and we don't have support for it, that can be a problem. This usually requires a new DLL from TI and a rev of the MSP430 CPU support package.
If you're still having problems, turn off Caps Lock and submit a ticket so we can go through it with you and update this article.