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.

Noel Fung offered his TI3410 driver labeled 6825.zip

Other Parts Discussed in Thread: CLOCKPRO, CDCE925, 4213, TUSB3410

That installation failed with the message "Unable to Launch usbinst"

When I install ClockPro from SCAC119d I get the same message.

Earlier I received SCAC131.zip   Among the unzipped files in a file TI3410Inst.exe  That file completes.

However when this is done I need to install the com port software manually by pointing to files in c:\TI Instruments Inc


The com port number comes out high like com11 or greater.


The problem is still not solved.

Thanks,

archieb

  • Hi Archieb,

    We will get back to you on this issue shortly.

    Regards

    Arvind Sridhar

  • Hello Archie,

    please try the installation routine from the last post at http://e2e.ti.com/support/clocks/f/48/p/317745/1114468.aspx#1114468

    best regards,

    Julian

  • I have an XP SP3.  I followed the instructions but have the same result.  In the window "TI ClockPro Programmer" having selected the CDCE925, Find Boards does not return a board that was found.


    I had downloaded the file 4213.Driver_ProgrammingEVM_Windows7 and extracted it to a new directory.  during the installation above, I directed the browse to ProgrammingEVM\i386 for the file umpusbvista.sys and then to

    ProgrammingEVM for file umpf3410.i51

    with the results mentioned above.


    It is my impression that there is TI ClockPro the application, A driver below that, and the driver that shows up in Device Manager.  The first and last appear to install.  The middle one is the piece that is apparently not working.

    Thanks,

    archieb

  • Hello Archie,


    Could you please let me know, if you see this device in your device manager, if the CDCE(L)9xx Programming EVM is connected to your PC?

    "TI CDCE(L)9xx Programming Evaluation Module (COMx)"

    if this is the case, maybe the standalone (labview needed) version could work: http://www.ti.com/litv/zip/scac120.

    If this is not the case, the EEPROM for the TUSB3410 might not be programmed correctly.

    This could be resolved by this instructions (only works with Win XP):

    8836.HOW TO program EEPOROM on EVM.zip

    Julian

  • In device manager I see;

    TI CDCE(L)9xx Programming Evaluation Module (COM11)

    I do not have labview  Does your installer provide the necessary NI files for this to work.

    My first EVM did work at one time but did not work after I went back to it, and has not worked since.

    A new one fresh out of the box did not work either.

    archieb

  • Following the instructions in the zip file I searched for other drivers.  There were none.  So I uninstalled the one in Ports.

    While I was searching for drivers I found a C:\windows\tiisnt\TUSB3410 folder and moved that to a network drive.

    Then I directed the installer to Drivers and it did its thing.

    In the TUSB3410EEProm etc directory there was no inf file so clicked on that which said it was installing.  It happened quickly so I did it from a command window to read what was happening.

    In this same directory there is an eepromburnter.exe so I clicked on that according to the README.txt file.  I followed that down until it told me to choose a USB bus device.  I had pointed to the one in Ports but it did not accept it.  I am shutting down to reboot and to move the tiinst directory back to c:\windows.

    More in a bit.

    archieb

  • I am back again. after copying tiinst directory back to c:\windows

    There is a 9xx Family EVM USB Adpator in the Device Manager MultiPort group, as well

    as an EVM-Serial Port (COM11) driver in ports.

    So I started eepromburner.exe again and worked through the questions.

    The USB device offered is the one from MultiPort.

    When I click on Program EEProm it comes back with

    Coose a TIUSBdevice to Program and blanks the USB chooser window.

    This is the where I was before.  The drivers in device Manager look OK but a program will not run.

    So, I have facility to drive the CDCE925 i2c port with in order to program it.

    I have been working on that between answering these emails.  However even using the output from

    ClockPro dot CSV file sending data over one byte at a time does not produce the desire results.  I have programmed the bytes from 1 to 6 and 10 to 1f.


    Can you give me pointers on how to achieve operation using my i2c master device?  Do I need to program 20 to 2f before it will work?

    Thanks,

    archieb

  • Hi Archie,

    if the windows device manager shows "TI CDCE(L)9xx Programming Evaluation Module (COM11)", the programming should work.

    - Do you have a device in the socket? -> the Programming EVM will be recognized only if there is a device in the socket.

    - Is the device in the right position and orientation in the socket?

    - Are the jumper settings correct?

    - Did you tried a different CDCE925 unit?

    Please check everything above in the UserGuide. http://www.ti.com/lit/ug/scau026a/scau026a.pdf

    Note: the silkscreen description of J5 on older EVMs might be wrong. For CDCE(L)9xx, the jumper has to be placed next to J2 (upper two pins).

    If you use another I2C master, please make sure the Slave address is correct, as well as that your are sending MSB first. Sending bytes from 1 to 6 and 10 to 1f should be sufficient to program PLL1. if  this doesn't work, you might want to check if the I2C address is correct. Do you have the option to read back the register values, that you wrote to the device?

    Best regards,

    julian

  • Such a struggle.

    I had missed the part about having a device in the socket.  I am using a cable from gnd, SDA, SCL to my board.  When I connected that It worked.

    Something is wrong with my i2c setup.  In some instances the address and command are correct and in another they are wrong.  I had not checked the second instance assuming that the first inferred that the second would work as well.


    Thank you for your patience with me,

    archieb