The MSP-FET430UIF is a powerful flash emulation tool to quickly begin application development on the MSP430 MCU. It includes USB debugging interface used to program and debug the MSP430 in-system through the JTAG interface or the pin saving Spy Bi-Wire (2-wire JTAG) protocol. The flash memory can be erased and programmed in seconds with only a few keystrokes, and since the MSP430 flash is ultra-low power, no external power supply is required.
The debugging tool interfaces the MSP430 to the included integrated software environment and includes code to start your design immediately. The MSP-FET430UIF development tool supports all MSP430 flash devices.
- 1 Features
- 2 Documentation
- 3 MSP-FET430UIF Troubleshooting
- USB debugging interface (MSP-FET430UIF) connects a flash-based MSP430 MCU to a PC for real-time, in-system programming and debugging
- Technical specifications:
- Software configurable supply voltage between 1.8 and 3.6 volts at 100mA
- Supports JTAG Security Fuse blow to protect code
- Supports all MSP430 boards with JTAG header
- Supports both JTAG and Spy-Bi-Wire (2-wire JTAG) debug protocols
- MSP430 Hardware Tools User's Guide
- Flash Emulation Tool (FET) (for Use With CCE/CCS) User's Guide
- Flash Emulation Tool (FET) (for Use With IAR v3+) User's Guide
What version of the software tool are you using?
It is recommended that only the latest version be installed for proper functionality.
Updating to the latest version fixes bugs in previous releases and provides support for the latest MSP430 devices. Using the latest version will eliminate software variables as a cause of your issue.
IAR EW430 5.40 has various problems with v3 FET protocol, such as getting message "Could not find device (or device not supported)" during download. See this article for more information and a workaround.
IAR EW430 Firmware upgrade
If your MSP-FET430UIF is successfully recognized by your OS but within your IAR EW430 the only entry under "FET Debugger->USB Selection" is "Automatic", be sure to read the following article: FET-firmware upgrade and downgrade.
- EW430 version 5.40+ and firmware downgrade
- "After upgrading to EW430 version 5.40, there might be problems using the FET debugger with older EW430 releases. It is possible to replace the old msp430.dll with the new DLL from EW430 5.40, to get it working. If this does not work, you can use the downgrade utility, V32V2.bat, located in the 430/bin directory to do a firmware downgrade. See the 5.40 Release Notes for more info[...]".
In other words: If you e.g. worked with IAR EW430 v5.10 and installed parallel an evaluation version >= 5.40 that requested a firmware upgrade, your v5.10 does not longer recognize your MSP-FET430UIF! In this case you have to copy the msp430.dll located in 430\bin\msp430.dll to your older IAR EW430 version and replace the old one as described above.
Are you using a valid OS?
The USB FET (MSP-FET430UIF) drivers included with the latest IAR Kickstart and the TI Code Composer Studio IDEs support Windows XP, Vista, and Windows 7, both 32-bit and 64-bit versions. All drivers are Microsoft WHQL certified.
The linux version of CCS5 does not support auto-update (or manual update) of DLL V3 (CDC-based) driver. Without installing a CCS5 or IAR on Windows, the MSP430-Flasher tool can be used for a quick firmware update. See MSP430_Flasher_-_Command_Line_Programmer
Hardware Self Test
When your device is plugged in do the LEDs blink? The pattern should be RED-RED-RED-GREEN and then the green should stay on. This indicates that the device is receiving power.
If the above does not happen: Sometimes updating the firmware will fix this problem, but if not the hardware could be damaged.
Note: The blinking pattern only applies on FET firmware v2. Newer firmware just lights the GREEN led when connected to PC.
2nd PC Test
Have you tried to install the same questionable USB FET on other PCs (using the installation guide steps in appendix C) of the Hardware User's Guide
If your FET works on a second PC the issue probably is a PC driver conflict with your first PC.
Was the tool in question ever recognized by any PC? If so were able to successfully program and debug with this tool at any time in the past?
If the tool used to work but no longer responds it could be damaged, or the drivers could have a conflict with newly installed 3rd party software.
Custom Board Comparison
Are you using a TI target board or a custom board design?
Hardware considerations can be ruled out by using a TI target board, available for order at www.MSP430.com
If you are using your own board, does your JTAG connections differ in any way from the recommendations we give in the Hardware User's Guide, page 23 (4-wire) or page 24 (2-wire/Spy-Bi-Wire)?
If there are significant differences this could very well be the source of your problem. See the Custom Board Comparison topic above.
New Project Test
After the above steps have been performed please do the following: If you create a new project using the steps in the attached word document (IAR , CCE V3 , CCS V4) and attempt to load a simple TI code example, do you see the same issue? This should rule out software considerations.
Device Manager Comparison
You should have a virtual com port (VCP) entry like the image below under PORTS (COM & LPT) If it does not then right-click and reinstall.
Update: the VCP-stuff is related to DLL V2. For DLL V3 (which add features), the CDC driver must be notified instead of VCP. Both types of drivers create a virtual COM port.
Still having problems?
Please open a new request at TI Support & reply to the Service Request bounce-back email with:
- Comments/Answers to the above questions
- Screen image of the device manager & error message
- the newly created workspace and files using the steps above, back to us in a zip file so we may take a look at it. Please also send the answers to the above questions.
Once the above questions are answered we can identify and rule out any issues regarding:
- Driver Errors
- Operating System Incompatibilities
- Software Tool Updates
- Software Setup/Project Option Issues