TUSB3410: TUSB3410 - Driver for Windows 10

Orlando Simpson

Part Number: TUSB3410

Previously, I had gained Brian's assistance with personalizing the “INF” file of the TI TUSB3410 USB for our company. Now because the driver has changed (new INF file), we need to driver signed again. I was just wondering if you have any background knowledge of getting a driver digitally signed or could point me in the right direction? I was following a tutorial from Microsoft but not getting the desired outcome as the steps are not clearly defined. I have tried calling Microsoft but the customer service is not much help.

over 6 years ago

0 Brian Zhou over 6 years ago

TI__Guru*** 131275 points

someone will help you soon

0 Orlando Simpson over 6 years ago in reply to Brian Zhou

Prodigy 245 points

Ok thank you very much. I need help asap. Any help is much appreciated.

0 Nicholaus_Malone over 6 years ago in reply to Orlando Simpson

TI__Mastermind 27220 points

Hi Orlando,

I am currently working on this issue. I reached out to Brian for advice, and he pointed me to a Microsoft tutorial as well. Is this the tutorial you were referring to?

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/kernel-mode-code-signing-policy--windows-vista-and-later-

Regards,

0 Orlando Simpson over 6 years ago in reply to Nicholaus_Malone

Prodigy 245 points

Hi Nicholaus, thank you for responding. I have been going through some Microsoft tutorials regarding driver signing for windows 10. However, they seem to be general and some of the steps appear to be missing. I have also try calling them but their customer service (Microsoft) keeping sending me to different departments and so I am in a circle. I tried following the Microsoft tutorial of creating the ".hlkx" file that needs to be submitted and the test are failing on the modified driver (INF file modified only) provided by Brian. I have attached the screenshot where 47/50 test failed. Any help would be much appreciated. I was thinking since TI went through the process thereby having more experience and knowledge.

No one at our company has any experience with driving signing and we have a lot of products in the field with the customized TI driver (meaning INF file changed to match our VID and PID). Since Windows 10, some of our customers do not like that our version of the driver is not signed. Thanks much

0 Orlando Simpson over 6 years ago in reply to Orlando Simpson

Prodigy 245 points

Hi Nicholaus, I installed the original driver signed for Windows 10 and tried the HLK test on it. I tried the "DF- InfVerif INF Verification" but it failed. Please see error below. I am also getting error in the modified TI installer as well. Maybe I am not testing it correctly. Do you know the process to get driver signed? Thanks in advance.

0 Nicholaus_Malone over 6 years ago in reply to Orlando Simpson

TI__Mastermind 27220 points

Hi Orlando,

The Windows driver issue is something that has recently been brought to our team's attention since signed drivers are now required by Microsoft. I am not familiar with the driver signing process, but our team is currently discussing the best way to support it. It's possible that the TUSB3410 Virtual COM Port Windows Driver (Rev. B) is not signed. I expect to have more information for you next week.

0 Orlando Simpson over 6 years ago in reply to Nicholaus_Malone

Prodigy 245 points

Hi Nicholaus, is it possible you (TI) could sign a driver for us with our custom PID and VID ? We have hundreds of units in the field with this PID and VID. We have the .exe of the modified TI driver from Brian. As such, I am not sure if we could get the driver signed with just the "exe" or are we allowed to sign our modify version of TI's driver by our self? We would pay for any expenses. We are open to any suggestions. Thanks much.

0 Nicholaus_Malone over 6 years ago in reply to Orlando Simpson

TI__Mastermind 27220 points

Orlando,

We decided that we will use this driver as a test-case, and I will be attempt to take our official TUSB3410 Windows 10 Virtual COM Port driver through the Microsoft driver signing process. I will update you as I make progress. Once that is complete, I'll have a better idea of what we can do for your modified driver.

Regards,

0 Orlando Simpson over 6 years ago in reply to Nicholaus_Malone

Prodigy 245 points

Hi Nicholaus, Thank you very much for your help. Please do provide updates as we need to provide updates to other companies that are using our products.

0 Orlando Simpson over 6 years ago in reply to Orlando Simpson

Prodigy 245 points

Hi Nicholaus, any update ? There is an internal management meeting where they require an update every Friday. Any update would be helpful. Thank you

0 Nicholaus_Malone over 6 years ago in reply to Orlando Simpson

TI__Mastermind 27220 points

Orlando,

No update yet. I was out of office yesterday. I will be looking into this today and give you an update before tomorrow.

Regards,

0 Orlando Simpson over 6 years ago in reply to Nicholaus_Malone

Prodigy 245 points

Hi Nicholaus, thank you. Looking forward to it.

0 Nicholaus_Malone over 6 years ago in reply to Orlando Simpson

TI__Mastermind 27220 points

Hi Orlando,

I will be following the instructions here in order to get this driver signed. I have generated a .CAB file, and I'm trying to track down the EV Certificate in order to sign it.

Items remaining:

Sign the CAB file submission with your EV Cert
Submit the EV signed Cab file using the Hardware Dev Center dashboard
Validate that the driver was properly signed
Test your driver on Windows 10 for Desktop

Regards,

0 Orlando Simpson over 6 years ago in reply to Nicholaus_Malone

Prodigy 245 points

Hi Nicholaus, thank you very much for the update. Good progress. I appreciate you responding in a timely manner. Kindly, let me know as soon as you get your driver signed. Thanks in advance

0 Orlando Simpson over 6 years ago in reply to Orlando Simpson

Prodigy 245 points

Hi Nicholaus, did you manage to recover the EV Code Certificate ? or any progress ? Thanks

0 Nicholaus_Malone over 6 years ago in reply to Orlando Simpson

TI__Mastermind 27220 points

Hi Orlando,

I have found our EV Certificate, I'm in the process of learning how to apply and submit it.

0 Orlando Simpson over 6 years ago in reply to Nicholaus_Malone

Prodigy 245 points

Hi Nicholaus, thank you for the update.

Reference URL: https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/attestation-signing-a-kernel-driver-for-public-release

Sign the submission CAB file with your EV certificate

Use the process recommended by the EV cert provider to sign the cab file with your EV cert. For example, you might use the signtool and if you are using Verisign, you might specify their timestamp server. Please remember to timestamp. Most EV provides allow you to time stamp. The command below calls the Verisign timestamp. Timestamping ensures that the signature does not expire once the EV certificate expires. Each EV provider have instructions to sign .cab files etc.

Sign tool location on Windows 10

C:\Program Files (x86)\Windows Kits\10\bin\10.0.16299.0\x64

C:\Program Files (x86)\Windows Kits\10\App Certification Kit

Signing Cab files with EV code cert using Windows Signtool.exe

C:\Echo> SignTool sign /v /ac "C:\MyEVCert.cer" /s MY /n "Company Name" /t timestamp.verisign.com/.../timstamp.dll "C:\Echo\Disk1\Echo.cab"

How to get USB token ready for use:
https://www.youtube.com/watch?v=5jX7ZqEdQGs

Using sign tool

www.youtube.com/watch