#TI CONNECT UNKNOWN DEVICE WINDOWS#"One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it. "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In different situations, the error is followed by various messages: When Windows generates such an error, the USB will not show up on your computer, and you can't access your data. "USB device not recognized" is an error that usually occurs on Windows computers when you plug in a USB device. #TI CONNECT UNKNOWN DEVICE FULL#Full stepsĬhange USB settings and reinstall the USB. #TI CONNECT UNKNOWN DEVICE UPDATE#Full stepsĬhoose Update Device Driver in Device. Navigate to the Driver tab, choose Uninstall. Full stepsĬheck all the available USB cables and ports. Hope this helps troubleshoot this problem - or is it possible to obtain the original FET firmware for 2.0.9/2.Shut down the computer > Unplug power cable. 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. #TI CONNECT UNKNOWN DEVICE PC#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. 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. I can, however, connect to a MSP430F1611 target. I then got the "Can't identify target device: no error" message. #TI CONNECT UNKNOWN DEVICE UPGRADE#When I first plugged in my FET, it asked to Upgrade my FET firmware - done. I'm now using Cross Studio 2.0.9 and/or 2.1 on a 2nd PC. I then upgraded to Cross Studio 2.0.9 on the same PC and switched to MSP430F2618 - still everything worked ok I used to use Cross Studio for MSP430 Ver 1.3, TI MSP-430FETUIF with target devices MSP430F1611, 169, etc. I have the same problem, however I have a method that works for me. 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. This usually requires a new DLL from TI and a rev of the MSP430 CPU support package. If you're trying one of those and we don't have support for it, that can be a problem. There are some devices that customers are privileged to receive before we do. Make sure the target that you have is supported by CrossStudio.If you use an out-of-sync DLL and firmware combination, all manner of strange things can happen. CrossStudio will automatically upgrade the firmware for you. Note that the DLL and the FET430UIF firmware must be synchronized.Just put it back to the default and try again. When TI deliver new DLLs, you might be able to change this to a "patch" DLL. The default for this is $(PackagesDir)/targets/msp430/MSP430$(HostDLL) which specifies the MSP430 DLL delivered in the latest MSP430 package. Make sure that the FET430UIF DLL path is correctly set.There is nothing special about these two interfaces, they just have their properties set correctly for JTAG and SBW interfaces. If your board is set up for Spy-bi-Wire, use the SBW interface, and if it's JTAG then use the JTAG interface. In CrossWorks V2 there are two FET430UIF target interfaces, one named TI MSP-FET430UIF (JTAG) and one named TI MSP-FET430UIF (SBW). Make sure that you are attempting to connect using the correct protocol.The default for this is 3.3V, but you may have changed it. You should check the Vcc setting in the Connection group of the FET430UIF target interface's properties. Make sure that you have enabled the regulator and powered the MSP430, if you intend to power the MSP430 from the FET430UIF.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |