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.
Comments
4 comments
Hi Paul,
I've already tried all you said but i'm still having problems, when i work with the msp430.dll the write operation failed message appears, and when i work with the msp430_ti.dll the can't identify target device: no error appears, i already tried what you say and the solution for the write operation message, but i'm still having problems.
We had this issue with new boards. kept getting can't Id target message. We had not connected the test pin to the TIMSP-430UIF. Reading the documentation, I interpret it to say that if you tie this high, the pins should always be in JTAG mode. For some reason this does not work. The processor does not reply to a query for the device type. If we tie to the UIF test pin I see the reset and Test go high together. Then the test pin drops momentarily and the processor replies after it goes back high. From then on in a debug session both reset and test remain high.
Anyway I hope this helps someone. If anyone has information on why the test pin cannot be tied to Vcc. I would love to know. The descriptions in the data sheet and the user guide imply to me that it could be tied high unless you need to use the pins for something other than JTAG.
I have the same problem, however I have a method that works for me.
I used to use Cross Studio for MSP430 Ver 1.3, TI MSP-430FETUIF with target devices MSP430F1611, 169, etc. everything worked fine on one PC. I then upgraded to Cross Studio 2.0.9 on the same PC and switched to MSP430F2618 - still everything worked ok
I'm now using Cross Studio 2.0.9 and/or 2.1 on a 2nd PC. When I first plugged in my FET, it asked to Upgrade my FET firmware - done. I then got the "Can't identify target device: no error" message. I can, however, connect to a MSP430F1611 target.
If I now connect the TI FET to the original PC and run Cross Studio for MSP430 ver 2.0.9, it will re-download firmware to the FET and detect the MSP430F2618 target. After this I connect the FET to the new PC and DECLINE the FET firmware Upgrade, and voila - it connects to the MSP430F2619, as well as the 1611, etc. Cross Studio contionues to ask about Upgrading the FET firmware every time I connect to the FET, but I continue to decline it and all works well.
Hope this helps troubleshoot this problem - or is it possible to obtain the original FET firmware for 2.0.9/2.1 in order to prevent Cross Studio from requesting the Upgrade?
hi Paul,
i'm using msp430 usb debug interface msp-fet430uif and during firmware update i plug up usb from laptop now msp-fet430uif don't work. please help me what can i do .....
is there any Hard reset option in msp430 usb debug interface msp-fet430uif.
Please sign in to leave a comment.