• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 376 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Driver installation problem

David Roberts
Prodigy 140 points
Part Number: CDCEL9XXPROGEVM
Other Parts Discussed in Thread: CLOCKPRO, TUSB3410

I am trying to setup my new CDCEL9XXPROGEVM

I am using a Windows 7 machine.

I ran the Clock Builder software, I get a message that I need a digitally signer driver.

Do you have one that I can use please?

Thanks

Dave R

  • +1
    TI__Mastermind 31660 points

    Dave,

    We've been unable to update ClockPro for some time, so the bundled driver software has gone out of date.

    I'll offer two possible suggestions:

    • Install the latest TUSB3410 driver stack. I've never tried this on a W7 machine, so I don't know if it will work. I did try this on my W10 machine and did not get any driver signature warnings, so I suspect it may have worked, but I also don't have a CDCEL9XXPROGEVM on hand to test.
      • The most up-to-date virtual COM port driver can be found at https://www.ti.com/product/TUSB3410#software-development.
      • Install the virtual COM port driver. It should install to C:\Program Files (x86)\Texas Instruments\TUSB3410 Driver.
      • ClockPro should be installed at C:\Program Files (x86)\Texas Instruments Inc\ClockPro by default. Copy (overwrite) the following files from the TUSB3410 Driver file into your ClockPro\Drivers\ProgrammingEVM path:
        • DIFxAPI.dll
        • Driver_Inst.exe
        • ump3410.cat
        • umpf3410.i51
        • umpusbvista.sys
        • usbuart3410.inf
        • WdfCoInstaller01009.dll
      • Delete the \i386 and \amd64 folders in the ClockPro\Drivers\ProgrammingEVM path.
      • The application should now function correctly.
    • If that doesn't work, the other option is to disable driver signature verification - I recommend only doing this for as long as the programmer application needs to be run, and only if the W7 machine can tolerate this configuration in its deployment environment. This also requires a significant degree of control over the W7 machine, so it may not be possible in a corporate deployment without administrator access or with restrictive group policies.
      • Open a command prompt, either while logged in as Administrator or by opening as Administrator.
      • In the command prompt, enter the following commands:
        • bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
        • bcdedit.exe -set TESTSIGNING ON
      • Next, go to Start -> Run -> GPEDIT.msc
        • Under User Configuration -> Administrative Templates -> System -> Driver Installation -> Code signing for drivers, click Disabled, then OK.

    If the first method works, please let me know - I've been trying to find a workaround to get ClockPro and CDCEL9XXPROGEVM working for a while.

    Regards,

    Derek Payne

  • 0
    Prodigy 140 points

    Thanks for your help!