Xds100v2 Driver Windows 10 Download
Jacque Finister
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.
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.
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).
I attempted to install the latest CCS emulation tools to 6.0.228.0 and now the XDS100v1/v2 devices are no longer detected by windows. I can manually install the drivers using "Have Disk" -> Point them to "C:\ti\ccsv6\ccs_base\emulation\windows\xds100_drivers\ftdi" but the device is only recognizes as TI XDS100 Channel A. I cannot seem to get the device to load both channels. So far I have:
Have you ever used OpenOCD that required installing libFTDI? Perhaps Windows is getting confused by the mix and match of libraries - I remember having this issue in the past, where a nifty utility called Zadig helped me with the constant switch of drivers. The usual "symptom" is the presence of the following entry on Control Panel:
If you don't want to use the utility, simply right-click on the "Texas Instruments Inc.XDS100 Ver 2.0" and select "Update Driver Software". Then, click on "Browse my computer for driver software" and select "Let me pick from a list of device drivers on my computer". Then they must select the entry that starts with TI XDS100 as shown below:
We have a remote manufacturing production plant which is equipped with XDS100V2 USB Debug Probe programmer and a Window 7 PC with Uniflash programming software utility provied by TI installed. It seems the Uniflash is unable to detect the XS100v2 USB Debug Probe programmer device as it requires the necessary drivers. When I looked on the TI website to download the windows 7 drivers for this regards just before christmas, I realised that TI have removed the support page for XDS100v2 and this means I am unable to download the required drivers. I have also tried downloading the drivers directly from FTDI website but even that has not resolved the issue. Can you please provide me with the correct drivers for XDS100V2 USB Debug Probe programmer. Without this, several XDS100v2 programmer devices procured by us for production plant have been rendered useless. We also feel that TI have taken down the support for this device without any notice to us.
I have also explored using the new programmer device XDS200 USB Debug Probe and have also realised that TI webpage recommends downloading the entire Code Composer Suite on Windows 7 machine for it to work. We feel that the entire Code Composer Suite is too complex and huge for installation and definately not required in the manufacturing production plant environment. Can you therefore provide us with only drivers for XDS200 USB Debug Probe so that it can work with the Uniflash utility provided by TI.
I have developed code for the TMS320F28035PNT using Code Composer and the XDS100 v2 interface. We have now asked our board manufacturer to start production and they would like to programme these blank device. I have tried C2Prog from Codeskin and this seems fine. However our suppliers are now asking me for the drivers. The only option I have is to get them to download and install Code Composer which seems a little excessive. I have been in contact with FTDI but they could not assist as TI has customised the driver. Does anyone know where I can obtain the drivers?
The JTAG Emulator Driver download page inlcudes drivers for Code Composer Studio and Windows. The Windows device drivers are included with each driver packge for Code Composer Studio. These device driver installs are being supplied for other non-Code Composer Studio uses, such as BHFlashBurn or BhLoader.
There was some recent discussion about this on the OpenOCD mailing list, but it looks like licensing issues prevent the team from including direct support for the XDS100v2. I also found a Git commit made around the same time as the discussion that appears to include code for supporting the XDS100v2, but I don't know if this is official or not. I can't really test it, either, because the XDS100v2 doesn't actually install correctly. I have to install CCSv4 to get the drivers, but I refuse to do this on my other machine because I don't want it to get cluttered like the first one. The discussion mentions that the XDS100v2 is actually just a FTDI device, so I tried using a generic FTDI driver, but Windows didn't recognize it.
I guess what I'm asking is this: Is there some way that I can easily get OpenOCD to support the XDS100v2 by somehow using a generic FTDI driver or another method? I spent $80 on this JTAG emulator and I really hate to let it go to waste.
Getting OpenOCD to work with this will be tricky...
First you need to add the USB IDs of you XDS100v2 to the driver inf file. Please note thatyou have to choose between the FTDI drivers and libusb drivers depending how you compiled OpenOCD. If you downloaded a binary OpenOCD version, you should use the drivers shipped with it. Once you added the correct USB Vendor and Product ID to inf file, the driver will install (you have to tell windows the correct path). This step is only needed on Windows platforms.
The device manager will tell you the ID numbers on its "Details" page as "Hardware IDs" Property. Is VID_xxxx and PID_yyyy where xxxx is the Vendor id (VID) and yyyy is the Product id (PID).
As noted in the BeagleBone documents, the FTDI FT2232H used for USB to JTAG and Serial ports currently uses the USB Vendor ID of 0x0403 and Product ID of 0xA6D0. Device driver installers are available on the Bone; however, for Windows they have an incorrect setting in the INF files and will not load the drivers. In short, the INF files provided were for a single-port FTDI device like the FT232R and not the FT2232H.
This can easily be corrected by downloading the FTDI drivers from and editing the ftdibus.inf file. These instructions are on the TI BeagleBone Wiki page ( -Android-DevKit_Guide#Hardware_setup), but the information presented also has a couple errors by assigning the same VID and PID to lines for 1-, 2- and 4-port devices. Only the 2-port device lines are needed in the [FtdiHw], [FtdiHw.NTamd64] and [Strings] sections:
All FTDI default VID/PID lines should be removed from any customized INF file. If this is not done, when FTDI releases a new WHQL driver version, it may overwrite and break the edits for this custom PID.
Here is my theory of why I was able to do this successfully. I have previously installed Code Composer Studio, which installed the XDS100v2 drivers onto my system. It so happens that these are the drivers with the correct VID/PID for the FTDI chip on the Beaglebone. When I connect the Bone, the XDS100v2 drivers are the ones that load, followed by a USB-serial driver.
This section will detail how to install drivers for the USB/Serial connection (and the other USB devices) from the Bone onto your Windows computer. We'll try to have more documentation on using the Bone with a Mac & Linux at some point but since so many people use Windows and its tougher to install the drives on Win than other OS's we'll start here!
Installation of USB drivers for TI XDS debugger probes
During the installation of the Embedded Workbench for ARM (EWARM) you have the possibility to install the TI USB drivers.
But in case you need to install any driver manually following steps are done:
- If you are using TI XDS100/110/200 emulator, you must have the version of the TI emupack provided with this release of EWARM installed in the suggested directory C:\ti.
The TI emupack installer is located in the arm\drivers\ti-xds directory of the EWARM installation.
Note: To install the TI emupack you must have full administrative rights on your computer. To achive this you have to do Run as administrator when starting the installer.
The following USB drivers are included in the TI emupack installation, and will be installed in your system as part of the installation procedure:
- For TI XDS110, USB drivers are found in the C:\ti\ccs_base\emulation\windows\xds110_drivers directory.
- For TI XDS100, USB drivers are found in the C:\ti\ccs_base\emulation\windows\xds100_drivers directory.
- For TI XDS200, USB drivers are found in the C:\ti\ccs_base\emulation\windows\xds2xx_drivers directory.
- For some TI XDS110 boards, you need to explicitly install the USB driver in the arm\drivers\StellarisICDI directory of the EWARM installation. This USB driver is also possible to install during the installation of the EWARM.
When reading the FIQ register group in the XDS100 debugger driver, incorrect values are recorded. The actual behavior depends on the current cpu mode. This will cause the stack checking to give false warnings in the log window. A workaround is to turn off the stack checking from the menu Tools>Options>Stack and disable all stack options.
[EW22839]
Support for Texas Instruments XDS100v2
The Texas Instruments debug probe XDS100v2 is now supported for TI TMS570 devices. To use XDS100v2, select TI XDS100 in the Driver drop-down list on the Debugger>Setup options page. The XDS100v2 debug driver requires the Texas Instruments emulator package to be installed. To install the emulator package, start ...\arm\drivers\ti-xds\ti_emupack_setup.exe and follow the installation procedure. Make sure to install the emulator package in the suggested default location. This will allow the debugger to find the emulator package automatically. If for some reason the package is installed in a custom location, the option --xds_rootdir=path must be specified on the options page Debugger>Extra Options.