• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 390 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.

CDCE72010 EVM USB firmware

Douglas Keenan
Prodigy 30 points

I have a CDCE72010EVM that I have been working with, and I seem to have accidentally wiped the USB EEPROM so the EVM no longer shows up to the control GUI. 

Is there a way to recover from this?

Thanks,

Doug

  • 0
    Prodigy 30 points

    Actually, figured it out - ApLoader to load the TUSB2136.bin provided with the control GUI install, then "upload FW" from the GUI.

    The hangup I was having was that the ApLoader INF was not installing. 

    Not being in any way familiar with INF files, after a bit of stabbing blindly at it, I found that adding a "ClassGUID" field to the [Version] block of the ApLoader.INF file allowed the INF to install (I borrowed "ClassGUID={36FC9E60-C465-11CF-8056-444553540000}" from the TiHera.INF in the GUI install). 

    I was having the same problem with the EEPROM Burner tool, the INF will not install if it does not have a "ClassGUID" field.  Is this a bug?

    -Doug

  • 0 in reply to Douglas Keenan
    TI__Guru* 81035 points

    Hi Doug,

    When the firmware gets corrupted for the TUSB chip, it makes it difficult to communicate with the device from the PC. The firmware contains device ID information (VID/PID) that the driver uses to recognize the device. The easiest way to work around this is to wipe the firmware clean, but unfortunately the EVM does not provide a good way to do this. It looks like you found another work-around by modifying the INF file itself which I have seen other users successfully do before.

    I will try to put together a robust procedure to address this in the future.

    Best regards,

    Matt