• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 1016 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.

EK-TM4C123GXL: USB bulk example issues when connecting to PC

Colombo Carlo
Mastermind 24280 points
Part Number: EK-TM4C123GXL


Hello everybody , 

please  I m testing usb_dev_bulk example on the launchpad .  I am on latest TIVAWARE 

TivaWare_C_Series-2.1.4.178\examples\boards\ek-tm4c123gxl\usb_dev_bulk.
I can compiler and download  , no problem 

now when I connect to a WIN10 PC   thePC sees a new device connected and asks for proper driver . Using std win procedure  Windows, Device Manager, Update Driver Software...   and  using file from Tivaware _C_Series-2.1.4.178\windows_drivers\usb_dev_bulk.inf  I got the error as in attach .

check the certificate in the driver   TivaWare_C_Series-2.1.4.178\windows_drivers\usb_dev_bulk.cat  it looks  the signature has expired  see in attach 

please  where am I wrong ?  is it the signature epeiration the issue ?

thank you 

bye

Carlo

Carlo

  • 0
    TI__Guru 72500 points

    I find that strange. I am still on a Windows 7 machine, but I see the same file (C:\ti\TivaWare_C_Series-2.1.4.178\windows_drivers\usb_dev_bulk.cat) with an October 18, 2016 date

  • 0 in reply to Bob Crosby
    TI__Mastermind 24280 points

    Hi Bob ,

    please clcik   the "view certificate"  button and  you ll see the valid date   m referring to .

    did you try on a "new" machine my sema Tivaware version   ?

    where  I could be wrong ?

    thank you 

    bye

    Carlo

  • 0 in reply to Colombo Carlo
    TI__Guru 72500 points

    I used TivaWare version 2.1.4.178 downloaded from the WEB.

    I checked and I actually installed my TivaWare on 2/24/2017. I was lucky by one day. I will look into getting a new valid certificate.

  • 0 in reply to Bob Crosby
    TI__Mastermind 24280 points
    HI Bob ,
    OK thank you
    please keep me posted
    bye
    Carlo
  • 0 in reply to Colombo Carlo
    TI__Guru 72500 points
    The feedback I got is that when drivers are signed with a timestamp, the timestamp is used to validate that the certificate was legal at the time of the signing. So as long as there is a timestamp, the driver should continue to work fine because the OS checks the timestamp against the certificate dates.

    Also, that error isn’t the one you would get for an expired certificate. I’m not 100% sure though what could cause the error. Two possibilities are that one of the driver files is corrupt so that its hash doesn’t match the value stored in the .cat file. Or there is another driver already installed using the same .inf name. I’ve seen that error with drivers that have been changed to include different devices, but the original was still installed by the same .inf name. The driver files are stored by the .inf file name, and having multiple but different drivers using the name confuses Windows.