• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 79 subscribers
  • Views 235 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Problem with FET Debugger

nick name
Intellectual 545 points
Other Parts Discussed in Thread: TUSB3410

Hai,

i am working on TI-MSP430F5438A EXP board from last one year onwards.

Now we open new MSP-FET430UIF Debugger. When i pluged in to the USB, FET debugger was not detected (no LED is glowing or ON) but at Device manager it is detected as TUSB3410 device.

When i pluged old USB FET debugger(The power LED was ON) and at device menager it is detected as MSP-FET430UIF-CDC.

What wrong in my New FET Debugger..???

Why it is detected as TUSB3410 device.??\

any one can help me greatly appriciated.

ThankYou.

  • 0
    Guru 227245 points

    Apparently, the TUSB3410 cannot read its firmware form the FET-internal I2C EEPROM. This may have several reasons. Maybe the MSP in the FET (not your target MSP!) somehow lost its firmware/crashed and is blocking I2C access. Or the checksum of the firmware in the I2C EEPROM was somehow damaged.
    However, the with the TUSB default firmware (uploaded by the TUSB PC driver), the TUSB does more or less the same as with its specific firmware: providing a serial connection to the MSP in the FET. Through this link, you can upload a new firmware to the MSP by using the proper tool (see WIKI or do a forum search for links). Then you can instruct the MSP to upload a new TUSB firmware in the I2C EEPROM. At this point, the TUSB will enumerate again as FET in device manager.

**Attention** This is a public forum