MSP-FET430UIF firmware update causes a general recovery method

fish001

MSP-FET430UIF firmware update causes a general recovery method [Copy link]

I don't know if there is a problem with my emulator version or what the reason is. When IAR 5.5 prompted to upgrade the firmware, I clicked YES and the upgrade progress popped up. Halfway through, it prompted me to disconnect the USB connection, then plug it in again, and then click YES to continue. After clicking YES, the name of the emulator was no longer "MSP-FET430UIF - VCP", but "TUSB3410 Device". After searching a lot of information, I found out that after the prompt was inserted into the USB for the second time, the EEPROM data in the emulator's TUSB3410 was actually upgraded. This is also the case of upgrading from V2 to V3 mentioned in the forum, but that program corresponds to the successful upgrade. What if the upgrade fails? I tested that program, and it can't be used on mine at all, and it prompts that the emulator can't be found at all. Finally, I searched for multiple sources on GOOGLE, and BAIDU really couldn't find any valuable information. The result is: "TUSB3410 Device" corresponding to VID (company code) = 0451 PID (product code) = 3410 "MSP-FET430UIF - VCP" corresponding VID = 0451 PID = F430 That is, after the upgrade of IAR 5.5, the product code has been modified. The emulator I am currently using: If you have similar experiences, please refer to the following solutions: First, download the attached content Second, install the TI USB EEPROM Burner software (in the compressed package), if prompted to install the driver, etc., select Allow. Third, confirm in the device manager whether the TUSB3410 driver name has changed to "TI TUSB3410 EEPROMBurner", if not, customize the driver installation, and find the corresponding driver in the software installation directory. Until it is confirmed that the driver name has been changed. Fourth, start the "EEPROM Burner" software, select "TI TUSB3410 EEPROMBurner" in the serial port selection, select 128K in the capacity below, then click the "Erease EEPROM" button, and wait for about 10 minutes. Wait for the progress bar to reach the end and prompt a successful information window. Fifth, browse to another attachment you downloaded in the file selection, and select the "MSP-FET430UIF - VCP.bin" file, click the "Program EEPROM" button, wait for about 1 minute, wait for the progress bar to reach the end and prompt a successful information window. Sixth, unplug the USB cable, plug the USB cable again, reinstall the TUSB3410 driver, manually install the driver, select "C:\Program Files\IAR Systems\Embedded Workbench 6.0 Evaluation\430\drivers\TIUSBFET\XP32" or the corresponding location, and then it will prompt that the driver has been successfully installed. At this time, the driver name has been restored from "TUSB3410 Device" to "MSP-FET430UIF - VCP". At this point, the TUSB3410 chip has been fixed. --------------------- In addition, if the MSP430F1612 If the chip program is also updated, you need to re-flash the firmware. My emulator can use its own TUSB3410 chip and use the BSL function to burn the MSP430F612 firmware. First, download the attached content: Second, start "mspfet.exe", click "Tools" -> "Options" in the menu, select "BSL" in the current adapter on the right, select the COM port corresponding to TUSB3410 under the port, and click "OK" Third, click "File" -> "Open" in the menu, select "MSP430F1612 Firmware.txt". Fourth, click "Operation" -> "Automatic" in the menu, and wait for completion. Fifth, after completion, please unplug the USB interface and then plug it into the USB interface. At this point, the MSP430F1612 chip has been fixed---------------------After that, use the lower version of IAR to upgrade the firmware, and everything will return to normal use. I am currently using IAR5.3 version, If I still use IAR5.5 version, this problem will still occur on my emulator. I don't know why.