MSP-FET 430UIF is not working

Nandish H S said:

in elptronic it says com port issue

In the last case, you might have a mouse driver or smartphone syncing program that hijacks the com port

HI Jens,

thanks for the reply, please find the snap shots of elptronic and device manager , i have tried to change the comport but nothing works out.

The FETs used to use a VCP (Virtual COM Port) driver, but newer drivers use a CDC structure that forwards to a VCP. After the update, the PC will assign a different COM port for the new VCP and somehow this has been messed-up. In fact, sometimes, Windows will assign the same COM number to multiple devices (of course this won't work properly) or fail to report the available COMs (especially if they have number >15) to the applications. This is because of multiple APIs to access COM ports, starting with old DOS.

YOu can try to manually assign a COM port in device manager and then restart the software and re-configure the COM port to use (or leave the setting to auto, if available)

Hi jens,

i tried this but it didnt work it out can please help me  to manual reflashing of the FET tool firmware.

regards

Nandish

Hi Jens,

i followed below link but after removing EEProm i dont kow how to flassh the IC.

http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/244991.aspx

please help me to resolve this 

Regards

Nandish

After removing the I2C EEprom (shorting its SCL and SDA pins would have been sufficient), the TUSB acts as a plain vanilla USB/SER bridge. The EEprom contains the special firmware for the TUSB bridge chip, not for the 1612. It is CRC protected, and if CRC is not correct or EEProm doesn’t answer, the TUSB goes into standard mode.
Now you can directly access the FET’s 1612 through BSL (with BSL-Demo or similar BSL software).
Likely, the I2C EEProm still has a correct firmware for the TUSB (), so it can be soldered again (or the short can be removed).