• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 21 subscribers
  • Views 743 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.

CDC Programming EVM Intstallation Problems

William Devine
Prodigy 70 points
Other Parts Discussed in Thread: TUSB3410

I have tried several times to install the Clock Pro Software.

Originally I could not even get the driver to load but resolved that and now it only shows

Ports (COM & LPT)->TUSB3410 Device (COM4).

I tried these instructions from another post

Please follow this instruction:6644.TUSB3410 EEPROM Burner Installer.zip

  • install driver from the attached zip file.
  • execute eepromburner.exe
  • select "TI TUSB3410 EEPROMBurner” and a eeprom size of 64kbits (this is important!!!)
  • click on browse and search for cdcproevm.bin from the zip file
  • click once on Programm EEPROM and wait a few seconds till a window pops up that says 'programming success full'
  • close eepromburner software and reconnect EVM
  • install driver from the previous post if needed

This did not work either it displays the following message

(eepromburnerDlg) (OnInitDialog) RegisterForDeviceNotification Fail (Error 13)

When I click OK a new pop-up comes up which has Select USB Device  and a drop down box with nothing in it.

I am running Windows 7

  • 0
    Prodigy 70 points

    Below is a capture of Device Manager using a driver that appears to work.  The problem is that the board does not boot meaning that it is possible that the internal rom is not configured.

    I attempted to use the program that is supposed to write to the EEProm but to no avail as stated previously and it appears the drivers in the files for the EEProm Burner are not compatible with Windows 7.  

    I was hoping someone from TI could shed some light on the issue but it appears that they are not really responding.

  • 0 in reply to William Devine
    TI__Expert 5325 points

    Hello William,

    I think a solution for an early issue got mixed now into your driver problem when you tried to flash a new firmware into the EEPROM.

     

    We now have two separate issues here:

    1) Win7 driver load issue of the TUSB3410 Virtual Com Port because of the driver signature.

    2) TUSB3410 does not recognize the firmware in the EEPROM properly and falls back to a generic mode.

     

    We need to start rolling back by putting the a clean EEPROM and inserting the correct firmware.

    Prerequisites

    a) keep the bin file from the zip ready

    b) clean all old driver left overs: 1) uninstall any clock pro software or EEPROM which you still might have installed by using the respective uninstallers. 2) go to the hardware device manager; top menu-> view-> show hidden devices; select any "TUSB3410" and "TI CDC..." devices you might find under "USB devices" and under "COM ports"; when you delete them, please enable the delete files option. 3) reboot 4) crosscheck in device manager that there are no devices left.

    c) get a Win7 compatible EEPROM burner tool

    install it. Please ensure that you write the bin file as a full binary image and that the EEPROM size is 64k. When the firmware should be somehow broken, it may be necessary to use a metal pincer and short the SCL or SDA line at power up as the TUSB3410 will automatically try to load a firmware from the EEPROM. The EEPROM burner software does not verify the actual EEPROM content after a write.

    After the next power cycle of the EVM. It should already show up as a device lacking a driver but in the device details the correct USB VID, PID (0x451, 0x16E0) should be visible.

    d) After re-installing the scac119e (clockpro1v21.exe) the EVM should properly come up. In case it shows a driver signature issue (depends a little bit on your windows security rights setup). It may be necessary to install the driver with a manual "update driver by INF" process, so that a warning dialog can be clicked.

    Best regards,

    Patrick

  • 0 in reply to Patrick Kammermayer
    Prodigy 70 points
    Hi Patrick, no luck I removed all and then reboot. Install the TUSBx10 EEPROM Burner short I2C_SCL and do not see any burner in the device manager on in the burner software.
  • 0 in reply to William Devine
    TI__Expert 5325 points
    Hello William,
    can you send me a private message/mail with your contact data. Then you can send me your device configuration. I can provide some samples with your config and get you going for your prototyping while we get your board working again.

    Best regards,
    Patrick