• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 2016 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.

MSP-EXP430F5529: CCS Debug no USB FET found

Ralf Brandes
Prodigy 20 points
Other Parts Discussed in Thread: MSP430F5529, TUSB3410

Hi all,

when I try to connect in CCS (Version: 4.2.4.00033 )  to the MSP-EXP430F5529 onboard ez430 FET I get the error message: no USB FET found.

All jumpers are installed according to the quick start or user guide, power switch setting is eZ and no battery is connected.

The target config file used is:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<configurations XML_version="1.2" id="configurations_0">

 

<configuration XML_version="1.2" id="TI MSP430 USB1_0">

<instance XML_version="1.2" desc="TI MSP430 USB1_0" href="connections\TIMSP430-USB.xml" id="TI MSP430 USB1_0" xml="TIMSP430-USB.xml" xmlpath="connections"/>

<connection XML_version="1.2" id="TI MSP430 USB1_0">

<instance XML_version="1.2" href="drivers\msp430_emu.xml" id="drivers" xml="msp430_emu.xml" xmlpath="drivers"/>

<platform XML_version="1.2" id="platform_0">

<instance XML_version="1.2" desc="MSP430F5529_0" href="devices\MSP430F5529.xml" id="MSP430F5529_0" xml="MSP430F5529.xml" xmlpath="devices"/>

</platform>

</connection>

</configuration>

</configurations>

In CCS 'connect to target' menu item in the target menu is grayed out.

Thank you for any advice.

Ralf

  • 0
    Guru 227245 points

    If CCS doesn't find the FET then there is no FET answering on any COM port (including the virtual ones) that isn't in use by another application.

    So if the drivers are properly installed and the virtual COM port appears in teh device manager when you plug-in the board, then maybe a driver or applicaiton is hijacking it.

    There have been mouse drivers, PDA sanying software and other 'masterpieces'  grabbing the newly appearing COM port, so it was in use and unavailable for CCS.

  • 0 in reply to Jens-Michael Gross
    Genius 4925 points

    To find out if that is the case you can try to open the COM-port with a terminal program - if it cannot open it when no other obvious program is running (CCS not running) then you have some masterpiece running Jens-Michael mentioned.

    I think last time it was a camera software grabbing it...

  • 0 in reply to Bernhard Weller
    Prodigy 20 points

    Hi Jens-Michael, Bernhard,

    in the windows XPs device manager it is recognized as a TUSB3410 (COM6) device and declared ready to use.

    If I connect a eZ430-F2013 stick to the same USB port, it is recognized as a MSP-FET430UIF - VCP (COM3). This one can be used for debugging etc.

    I have also tried it on another computer - with the same result.

    regards

    Ralf

  • 0 in reply to Ralf Brandes
    Guru 227245 points

    Ralf Brandes said:
    in the windows XPs device manager it is recognized as a TUSB3410 (COM6) device and declared ready to use.

    So the eeprom containing the specialized firmware for the TUSB chip somehow got corrupted.

    The TUSB tries to read specific firmware from an external eeprom on power-up. In case of the FET it contains the VID/PID for the FET, adn in some cases externsions for a backchannel UART fonctionality (e.g. on the LaunchPad).

    If the eeprom content has been damaged, the TUSB will identify itself as generic TUSB and gets a default firmware form the PC driver through USB. (that's why it makes a double-dong when you plug it in - it answers as 'empty TUSB' first, gets its firmware and then re-enumerates as TUSB virtual COM port)

    In a different thread I read about a tool that allows changing the VID/PID (updating the eeprom). This is done by the FETs MSP (if it is still working) which can be accessed independently of the TUSBs VID/PID - if the software doesn't check for the proper FET-IDs and knows the right commands to be sent to the MSP.

    Sounds confusing? I agree :)

    However, it allows things that weren't possible if the TUSB were using a static ID and firmware. Like the backchannel UART, or having several FETs attached at the same time without mixing them up etc.

**Attention** This is a public forum