This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP-FET430UIF not found

Expert 1030 points
Other Parts Discussed in Thread: MSP430F4132, TUSB3410, MSP-FET

I am trying to develop some code on an MSP430F4132. I am using my MSP-FET430UIF, but whenever I come to try and Debug the code the Debug window pops up an error dialog window whose caption reads:

TI MSP430 USB1_0/MSP430

and with the following error message:

Error initializing emulator: No USB FET found.

Looking in Windows Manager under devices, the device comes up as TUSB3410 Device (COM13)

Can anyone tell me what this is due to and how I can fix it? Thanks. Harry.

  • Unfortunately I only have the new black MSP-FET here at the moment and this is listed as "MSP Debug Interface" in the device manager. I can test it later at home with my older grey one if it only says "TUSB3410 Device" as well. Maybe it is not enumerated properly or maybe missing drivers.

    Or anyone else has one and can have a quick look inside his device manager?

    Dennis

  • If the device enumerates as TUSB4310, then the USB/SER converter chip on the FET is running on its default firmware and not the specific firmware used for FET operation.
    This means that the I2C EEPROM on the FET does not provide a proper firmware to the TUSB. Either the MSP in the FET (not your target MSP) is blocking access to the EEprom (due to damaged firmware) or the content in the EEProm has been damaged.
    There are tools available (sorry, you need to use the forum search yourself) to access the MSP int he FET and make it updating the I2C EEProm, so the TUSB can fetch its special firmware from there on next power-on.
    This process has been described in several older threads.
  • Hi Jens. The device enumerates as TUSB4310, but when I try to initiate a debug session an error message states: 'No USB FET was found'. I have tried reading the information at the following site:

    processors.wiki.ti.com/.../MSPDS_Debugger_Up-_and_Downgrade

    The relevant section of the above page is titled: 'Upgrade process to MSP430.DLLv3', since my debugger is version 1.4a. The first subsection seems to refer to new IDE updates and so is not relevant - I'm already on CCS ver 6.1. The second section addreses my situation and begins with: 'When a debug session is being opened, the IDE will ask you to perform a debugger update'. This does not, in fact, happen. Instead I get the error message described previously. My debugger, when it is connected, goes straight to green, not red-red-red-green, so I seem to have MSP430.DLLv3 already. Any suggestions? Thanks for any help you might offer.

  • When the device enumerates as TUSB4310, then the TUSB serial bridge chip doesn't find its special FET firmware anymore and enumerates in its default mode. This can have two reasons: First, the I2C Flash chip in the FET has corrupted content. This may happen due to voltage peaks or incomplete updates. Sometimes even by power-loss just the moment the TUSB reads the firmware.
    The other reason is that the MSP on the FET has lost its firmware or got an incomplete update, and now blocks the I2C bus.
    If you search the forum, you'll find information on how to flash a working firmware on the MSP through the default TUSB serial connection, then how to update/refresh the I2C flash chip content through the MSP. Afte rall, the default TUSB firmware is sufficient to access the MSP in BSL mode (for firmware update) and then to send it commands. It is just not enumerating as the expected device and does not offer the additional features needed for high-speed JTAG communication.
    btw: seeing a green LED at startup, it seems that the MSP firmware is still intact and it is just the I2C EEPROM that got its content damaged. Unfortunately, I don't remember the process for updating it, so please search the forum yourself.

**Attention** This is a public forum