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.

CDCEL9XXPROGEVM: Board not recognized by ClockPro - Device driver error

Part Number: CDCEL9XXPROGEVM
Other Parts Discussed in Thread: CDCE913, CLOCKPRO, , TUSB3410

Tool/software:

Hi There

Just got a CDCEL9xxprogevm for programming CDCE913 chips but I cannot get it to communicate with ClockPro under windows 11.

I did reload the latest version of Clockpro, dated Feb 2025 to no effect.

The board is recognized by the Device Manager but shows a driver error, cannot verify digital signature.

I did find out a previous thread recommending to update the TUSB3410 driver but the link provided to the new driver does not work.

Other threads I looked at seem pretty useless in the circumstances.

Obviously, the progevm is pretty useless if there is no way to communicate with it and I am getting frustrated.  This puts a project on hold.

How can I get that programmer to work?  Where can I find the right driver?

Thanks

  • Robert,

    I suspect that this may be an issue specifically with Windows 11. I have used this board with a Windows 10 machine with no issues. I have requested for a few boards to be shipped my way so that I may check with my Windows 11 machine as well. These should arrive in a week or so.

    Have you tried following the steps detailed by Derek here: https://e2e.ti.com/support/clock-timing-group/clock-and-timing/f/clock-timing-forum/1169622/cdcel9xxprogevm-driver-installation-problem?tisearch=e2e-sitesearch&keymatch=cdcel9xxprogevm%252520driver# ? This seems to have worked for Windows 7 machines in the past.

    Thanks,

    Kadeem

  • Hi Kadeem

    I had a look at Derek link already.  The problem is that the link to the new driver set does not work.  I do not know where to find the new set of drivers.

    I also had a look at the gpedit way of removing driver signing.  This is not supposed to work with newer releases of Windows.  And, as I am not a Windows expert, I am reluctant to risk creating worse problems playing with those things.

    I do presume the programming board is up to date.  Just got it from Mouser a few days ago.  Presumably the same as you will get.

    I will wait for your own testing before taking further steps.

    But in the meantime, would you have any documentation about the format of CLOCKPRO output files?  I would like to check things and may be look at alternative ways of doing things.  Clockpro documentation is quite sparse to say the least.  Or maybe I just did not find it.

    Have a nice day

    Robert

  • Robert,

    There are a couple of different output file types. The most straightforward to use is the TXT file input/output. This will give the values in the register space as a text file. Being connected to a physical device is not necessary for creating the configuration file, only for testing. The Configuration Code Release Sheet is mostly for internal usage, when we need to mass produce a configuration and save additional information about it. The CSV file is similar to the TXT file, and exists for automation purposes more than anything else.

    For your use case, using just the TXT file (or load and save setup) is sufficient.

    Thanks,
    Kadeem

  • Thanks again

    I did look at a .txt output file and this is clear enough.  It looks like it would be simple enough to design my own in-circuit programmer.  Something we will consider in the future.

    I also found some updated drivers in a Microsoft repository.  This is version 6.7.5.6 while the one that gives problem is 6.5.9018.1.  However I am a bit lost with the Microsoft package.  Not sure which of the driver files must be installed and when I tried a likely one, I got nasty warning messages from Windows.  I felt better to suspend operations until I get a bit more information.  If you do have a driver set that is known to be working, I would appreciate it.  I still would like to run the programmer.  That will make my prototyping work so much easier.  

  • Robert,

    I am still waiting to receive a programming EVM. I am escalating this so that I can get the board in my hands ASAP.

    Thanks,

    Kadeem

  • Thank you very much

    And no panic, I still have other things to deal with on this prototype.

    Have a nice week end

    Robert

  • Robert,

    Sending an update - the programming EVM has shipped and I should receive it in a few days.

    Thanks,

    Kadeem

  • Thanks for the update

    And I tried a few other things in the meantime, without success.

    1.  I tried a slightly modified version of the Derek suggestion:  I did replace the driver files in //ClockPro/ProgrammingEVM/Drivers by the equivalent files from version 6.7.5.6 drivers from Microsoft.  Exactly the same behavior:  will not recognize the programming board.

    2.  Just this morning, I got my hands on an older laptop running Windows 10, which is supposed to work.  Installed ClockPro.  But again, exactly the same behavior as on my main Win11 computer.  ClockPro works but will not connect to the programming board.

    I hope this will help you make sense of the issue.

    But, just in case, I also got myself an FTDI MPSSE cable and will look at writing some code to make myself an in-circuit programmer using this cable.  The idea would be to get the register values from ClockPro and then program them with the cable.  I still will wait a bit to get news from you before I get into that.

    Hopefully, you will be more successful than me in communicating with the programming board

    Have a nice day

    Robert

  • Robert,

    Understood. I will keep you updated when I receive the board.

    Thanks,

    Kadeem

  • Robert,

    I followed the exact steps from this thread (the first response from Shawn Han), and had no issue getting the board up and running. Please follow his proceure in the pdf: https://e2e.ti.com/support/clock-timing-group/clock-and-timing/f/clock-timing-forum/904979/cdcel9xxprogevm-using-the-clockpro-software.

    Thanks,
    Kadeem

  • Thanks Kadeem, that helps

    There is some progress.  The board is now recognized This windows now appears and if I click the power button, the two first indicators come on.

    But the connection light does not get green in the main window.  All devices show as local.

    It looks like I am still missing/misunderstanding something.

    I do have a CDCE913PWR in the socket, starting at pin 1.  Could it be due to a misplaced jumper? J2, J3, J4 are in the bottom position, J5 in the top.  Correct?

    Any other thing I may be missing?

  • One further note:  it looks like I had jumpers wrong.  I fixed that:  J4 now in the UP position (3V3).  J3 also in the UP position( Vccout to 3v3).

    Unfortunately, I still do not communicate with the chip.

    Another thing doubtful:  the drawing of the socket in Fig 5 of the EVM manual, right side, is reversed from what I see on the board.  I used the pin 1 marking on the board itself to locate the chip.  OK?

    I do guess that I am doing something wrong but I still cannot find out what.

    Robert

  • Robert,

    In this software, the programming EVM is ONLY usable with the programmer. It is not available with the main GUI for creating configurations. For this, a CDCE913 evaluation module is required.

    In general, the programming evaluation module is only usable for programming quantities of loose devices. For testing a configuration, the performance evaluation module (CDCE913EVM) is required.

    Thanks,

    Kadeem

  • Thanks Kareem.  Your support is much appreciated.

    I am happy now.  I finally got the programmer working.  I did not realize that the file had to be loaded from the menu.  I was trying to enter it directly in the file path.

    I am quite fine with the restrictions of the programming EVM, once I understand them.  The idea is to use that only for initial development.  If things work well, I definitely will want an in-circuit programmer and while this will not be very difficult to develop, I still prefer to put that as a later task to do.  It will be somewhat useless if we find out that the CDCE913 is not suitable after all.

    My only beef is that the programmer interface documentation is virtually inexistant.  It was not that intuitive to me.  But, after installing the right drivers that you provided and finally understanding how to use it, the thing works well.

    Again, thank you very much for your help and we can now consider the case closed.  Things now work as I would like.

    Have a great day

    Robert