• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 3455 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.

Trouble installing ICDI Drivers on Windows Server 2012

Sasa Janjic
Prodigy 30 points


Hello,
I'm having issues installing the ICDI drivers on Windows Server 2012. Every time I try to install the ICDI drivers for use with my LM4F120XL they always fail as shown in the attached images. Any suggestions on how to fix this?

Regards

  • 0
    TI__Expert 3445 points

    Sasa,

    We do not test on or support Windows Server 2012. Have you followed as closely as possible the installation procedures in the driver install guide at http://www.ti.com/lit/ml/spmu287a/spmu287a.pdf?

  • 0 in reply to Stellaris John
    Prodigy 30 points

    I was able to fix the issue by modifying the driver.
    I got rid of the provided catalog files, changed the inf's a bit, used INF2CAT, and self-signed the new catalog files to get it to work.

    For anyone else that may have this issue, here's a very comprehensive and easy to follow guide:
    http://technet.microsoft.com/en-us/library/dd919238%28v=ws.10%29.aspx

  • 0 in reply to Sasa Janjic
    TI__Expert 3445 points

    Sasa,

    Most impressive. The drivers we provide are already signed, so I think the changes to the .inf files were what got it working. Did you change the .inf files beyond the steps detailed in the Technet article?

  • 0 in reply to Stellaris John
    Prodigy 30 points

    Yes, the provided drivers are signed, but after changing the inf's it's necessary to create new cat's since the changes cause a hash error when trying to install:
    "The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering."
    As it turns out no changed to the infs were needed, just had to rebuild the cats and sign. The Technet article covers more than what's needed for installing the drivers on Server 2012, so I made a quick guide:

    1) Download a fresh copy of the Stellaris ICDI Drivers: http://www.ti.com/tool/stellaris_icdi_drivers

    2) Extract the folder somewhere convenient, (for example to "C:\icdi")

    3) In Command Prompt, use: "INF2CAT /driver:C:\icdi /os:7_x86,7_x64" to create new cat files. Be sure to change the driver location to where you extracted them if you chose a different location.

    Note: It wasn't necessary to change anything in the inf files, but if you wanted to sign the driver for a newer operating system like Windows 8 or Server 2012 (8_x86, 8_x64, 8_ARM,Server8_x64) you will have to change the version date in each inf to a date after 4/27/2012. Signing the driver for Windows 7 works just as well and doesn't require any modification of the inf files. You only need to specify one of 7_x86 or 7_x64 depending on if your system is 32 or 64 bit respectively. Having both specified updates all cat files.

    4)  Now that we have the cat files, you can either sign the drivers or reboot and disable signature enforcement. Assuming you don't want to reboot, use SignTool to sign the drivers with your certificate:
    Use "cd C:\icdi" to set the current directory to the driver folder
    Use "SignTool sign /s YOURCERTIFICATE /n “NAME OF YOUR CERTIFICATE” /t http://timestamp.verisign.com/scripts/timestamp.dll *.cat" to sign all the cat files with your certificate.

    Note: To create your own certificate follow Steps 1-3 of the Technet article: http://technet.microsoft.com/en-us/library/dd919238%28v=ws.10%29.aspx

    5) Follow the official driver install guide at http://www.ti.com/lit/ml/spmu287a/spmu287a.pdf using the newly created and signed drivers.