- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software: Code Composer Studio
I am running Windows 10 64-Bit, installed CCS 8 successfully. XDS100v2 Driver will not install.
In my Device Manager I do not have the Channel A and Channel B drivers listed. (as other posts show it should look when it is installed properly. I have tried the both online and offline installs. Both ways installs CCS and I can build the blinky test but neither one will install the driver.
The main error i get is: "sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider."
Here is the error when trying to install the driver manually:
sto: {DRIVERSTORE IMPORT VALIDATE} 10:57:16.122
sig: {_VERIFY_FILE_SIGNATURE} 10:57:16.200
sig: Key = xds100bus.inf
sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp\{6d328034-067f-2f48-92f7-80ba41d47a5b}\xds100bus.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp\{6d328034-067f-2f48-92f7-80ba41d47a5b}\xds100bus.cat
! sig: Verifying file against specific (valid) catalog failed.
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 10:57:16.231
sig: {_VERIFY_FILE_SIGNATURE} 10:57:16.231
sig: Key = xds100bus.inf
sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp\{6d328034-067f-2f48-92f7-80ba41d47a5b}\xds100bus.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp\{6d328034-067f-2f48-92f7-80ba41d47a5b}\xds100bus.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 10:57:16.293
sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 10:57:16.324
sig: Signer Score = 0x0F000000
sig: Signer Name = Texas Instruments Incorporated
sto: {DRIVERSTORE IMPORT BEGIN} 10:57:16.324
sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 10:57:16.324
cpy: {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{6d328034-067f-2f48-92f7-80ba41d47a5b}} 10:57:16.324
cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\xds100bus.inf_amd64_619be3210695622f
cpy: {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{6d328034-067f-2f48-92f7-80ba41d47a5b}\amd64} 10:57:16.340
cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\xds100bus.inf_amd64_619be3210695622f\amd64
cpy: {Copy Directory: exit(0x00000000)} 10:57:16.356
cpy: {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{6d328034-067f-2f48-92f7-80ba41d47a5b}\i386} 10:57:16.356
cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\xds100bus.inf_amd64_619be3210695622f\i386
cpy: {Copy Directory: exit(0x00000000)} 10:57:16.356
cpy: {Copy Directory: exit(0x00000000)} 10:57:16.371
idb: {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\xds100bus.inf_amd64_619be3210695622f\xds100bus.inf} 10:57:16.371
idb: Created driver package object 'xds100bus.inf_amd64_619be3210695622f' in DRIVERS database node.
idb: Created driver INF file object 'oem107.inf' in DRIVERS database node.
idb: Registered driver package 'xds100bus.inf_amd64_619be3210695622f' with 'oem107.inf'.
idb: {Register Driver Package: exit(0x00000000)} 10:57:16.387
idb: {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\xds100bus.inf_amd64_619be3210695622f\xds100bus.inf} 10:57:16.387
idb: Activating driver package 'xds100bus.inf_amd64_619be3210695622f'.
cpy: Published 'xds100bus.inf_amd64_619be3210695622f\xds100bus.inf' to 'oem107.inf'.
idb: Indexed 5 device IDs for 'xds100bus.inf_amd64_619be3210695622f'.
sto: Flushed driver database node 'DRIVERS'. Time = 0 ms
sto: Flushed driver database node 'SYSTEM'. Time = 15 ms
idb: {Publish Driver Package: exit(0x00000000)} 10:57:16.437
sto: {DRIVERSTORE IMPORT END} 10:57:16.442
dvi: Flushed all driver package files to disk. Time = 0 ms
!!! sig: Failed to install catalog 'xds100bus.cat' as 'oem107.cat'. Error = 0x8E5E0408
sto: {DRIVERSTORE IMPORT END: exit(0x8e5e0408)} 10:57:36.608
sto: Flushed driver database node 'DRIVERS'. Time = 16 ms
sto: Flushed driver database node 'SYSTEM'. Time = 0 ms
sto: Rolled back driver package publishing.
sto: Rolled back driver package registration.
sto: Rolled back driver package import.
!!! sto: Failed to import driver package into Driver Store. Error = 0x8E5E0408
sto: {Stage Driver Package: exit(0x8e5e0408)} 10:57:36.677
sto: {Setup Import Driver Package - exit (0x8e5e0408)} 10:57:36.693
!!! ndv: Driver package import failed for device.
ndv: Installing NULL driver.
dvi: {Plug and Play Service: Device Install for USB\VID_0403&PID_A6D0&MI_01\6&167B77B0&0&0001}
! dvi: Installing NULL driver!
dvi: {DIF_ALLOW_INSTALL} 10:57:37.317
dvi: Default installer: Enter 10:57:37.317
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 10:57:37.334
dvi: {DIF_REGISTER_COINSTALLERS} 10:57:37.338
dvi: Default installer: Enter 10:57:37.339
dvi: Default installer: Exit
dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 10:57:37.339
dvi: {DIF_INSTALLDEVICE} 10:57:37.339
dvi: Default installer: Enter 10:57:37.339
! dvi: Installing NULL driver!
dvi: Install Null Driver: Removing device sub-tree. 10:57:37.354
dvi: Install Null Driver: Removing device sub-tree completed. 10:57:37.354
dvi: Install Null Driver: Restarting device. 10:57:37.370
dvi: Install Null Driver: Restarting device completed. 10:57:37.385
dvi: Device Status: 0x01802400, Problem: 0x1c (0x00000000)
dvi: Install Device: Starting device 'USB\VID_0403&PID_A6D0&MI_01\6&167B77B0&0&0001'. 10:57:37.385
dvi: Install Device: Starting device completed. 10:57:37.494
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 10:57:37.494
ump: {Plug and Play Service: Device Install exit(00000000)}
How do i get this driver to install?
Hi,
What is the exact version of Windows 10 (1709, 1804, 1809)? Each new version can potentially change a few things with the trusted certificates.
Also, is this a new setup and was CCS ever installed in this host? If this worked before, then there is a chance of corruption on the installer and you could always try to install the drivers manually by following the instructions at the page below.
http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package
You could also check if the certificates exist or are valid - several references on the web mention methods to verify this, and the screnshot shows what I have here (the highlighted entries are for the FTDI device drivers used by the XDS100v2 Debug Probe).
Procedure to check if a certificate is installed in your system:
Checking a certificate using Microsoft's Signtool utility:
https://www.codeproject.com/Questions/875907/How-to-sing-a-driver-package
My system:
Regards,
Rafael
