hi Bob,

I didn't find the xds200 driver neither on TI site nor Spectrum Digital site. But when I update Code Composer Studio from v5.2 to v5.3, I found the xds200 driver had been installed. CCSV5.3 could be downloaded from the following URL.

http://processors.wiki.ti.com/index.php/Code_Composer_Studio_Beta_Downloads

best regards

Bai

Thanks Bai,

Doesn't work for me.  I've installed CCS5v3.0.00067 but the driver install still fails.  Looks like it finds the driver, but driver won't install.  Error message is: "The filename, directory name, or volume label syntax is incorrect."  I'm on a 64-bit Windows Vista machine.  I will open a ticket with TI.  Will also check beta releases.

Bob

Bob,

I will split this thread and it can be your ticket.

Regards,

John

Thanks John.

I don't see anything in 5.4 release notes that address XDS2xx issues, but I'll download it anyway just in case.  This will take awhile...

Bob

I just noticed that the ccs5.3 version I retried off the web was a beta release (3.0.00067).  I'm downloading 3.0.00090 now.  Will uninstall the beta and install the release to see if that one fixes the problem.

I've now installed ccs 5.3.0.00090 and still get the same driver installation issues.  I'm down now and can make no further progress.  My application is a TMDSEVM6657LS evaluation kit.  I'm downloading the 5.4.0.00048_win32 beta version, but I'm not optimistic after reading the release notes.

Bob,

A few comments:

- Is the emulator properly recognized by the Windows Control Panel? Or does it show an error as in the previous discussion?

- If not, the XDS200 windows device drivers are usually installed under C:\ti\ccsv5\ccs_base\emulation\windows\xds2xx_drivers

- If all else fails, try changing the USB port (sometimes restarting the PC helps, as Windows' handling of USB devices is sometimes a mystery to me)

- If this still does not help, I would test it in another PC to see if the issue is with the emulator itself...

Hope this helps,

Rafael

Rafael,

Thanks for looking into this problem.  The Windows Device Manager does show errors.  Tried switching USB port and switching USB cables.  No change.  Will try another PC.

Bob

I don't have another PC readily available.  Looking into my Windows>Control Panel>Administrative Tools>Event Viewer>Application logs and can see that I'm getting the following error:

The entry <C:\TI\CCSV5\ECLIPSE\P2\ORG.ECLIPSE.EQUINOX.P2.CORE\CACHE\BINARY\COM.BH.CCSTUDIO.EMULATION.WIN32_ROOT_5.2.0.205> in the hash map cannot be updated.

Context:  Application, SystemIndex Catalog

Details:
    A device attached to the system is not functioning.   (0x8007001f)

Another version of the error event is:

The entry <C:\TI\CCSV5\CCS_BASE\EMULATION\BOARDS\DSKTCI6482\GEL\DSKTCI6482_MEZZANINE.GEL> in the hash map cannot be updated.

Context:  Application, SystemIndex Catalog

Details:
    A device attached to the system is not functioning.   (0x8007001f)

Rafael,

I'm up and running on another PC so the EVM kit including emulator appear to be working.  This one's a 32-bit Windows XP machine.  I'm successfully running some of the MCSDK demo stuff.  The XDS200 drivers load fine on that machine.  I'm very interested in moving back to the 64-bit Windows Vista machine.  Please let me know when working drivers are available to support that configuration.

Thanks,

Bob

Bob,

Thanks for reporting this and I am glad you are somewhat back on track. The XDS200 emulators work just fine in Win7/64, therefore I am suspicious that Vista may be interfering with something (it shouldn't, but can't be 100% sure).

I will ask around and see if someone has a Vista/64 PC to test this, but I can't promise much (Vista was somewhat short lived). I'll let you know when I find something relevant on this issue, ok?

Cheers,

Rafael

Thanks Rafael.

I'm interested to know what you find.  I'm proceeding with evaluation on Windows XP, but this platform won't be acceptable long-term.

Bob

Bob,

I discussed this internally and found out the XDS2xx is based off industry standard CDC Serial Port driver. This driver is supported via Microsoft with <usbser.sys> (under the directory \windows\system32) and the emulation dlls make standard system calls to this driver. The XDS2xx inf file references <usbser.sys> and it must already be present for the HW installer to complete properly. Windows 7 and 8 come standard with <usbser.sys>, but pre-Windows 7 it is installed in some Service Pack or other driver update packages.

Thus it may be a matter of updating Vista to a specific Service Pack. However, I can't tell for sure as I couldn't install in my system either (it fails to install during the device driver instantiation) and several attempts to modify the .inf rendered fruitless.  

I am still investigating this, but it may or may not be a solution we (TI) are able to implement. I'll get back with additional findings.

Regards,

Rafael

Rafael,

Thanks for the continued investigation and info.  Our 64-bit Vista machines are updated frequently with all required software, and there are no outstanding Important or Recommended updates that have not been installed.  My last update occurred on 4/9 and I've duplicated the failure since.  I've also failed to find an optional Vista update that references the CDC Serial Port or usbser.sys driver.  Still interested in what you discover.

Thanks,

Bob

hi @all,

its an old thread....i know. but i was running over 1 year later into same problem. so it's still there.

but i can provide a solution:

microsoft changed something in the storage for the driver usbser.sys

this has to be taken into account for the inf file for this device. so i did some changes on the inf file from ti.

C:\ti\ccsv6\ccs_base\emulation\windows\xds2xx_drivers\xds2xx_usb_cmp.inf

;************************************************************
;  XDS2xx USB CDC (serial) composite driver installation file.

[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
LayoutFile=layout.inf
CatalogFile=%MFGFILENAME%.cat
DriverVer=04/21/2009,5.1.2600.0

[Manufacturer]
%MFGNAME%=DeviceList, NTx86, NTamd64

[DestinationDirs]
FakeModemCopyFileSection=12
DefaultDestDir=12

[SourceDisksFiles]

[SourceDisksNames]

;------------------------------------------------------------------------------
;  Windows 32-bit 2000/XP/Vista/Win7 Sections
;------------------------------------------------------------------------------

[DeviceList.NTx86]
%DESCRIPTION_0%=DriverInstall, USB\VID_0451&PID_BEF0&MI_00
%DESCRIPTION_1%=DriverInstall, USB\VID_0451&PID_BEF0&MI_02
%DESCRIPTION_0%=DriverInstall, USB\VID_0C55&PID_0220&MI_00
%DESCRIPTION_1%=DriverInstall, USB\VID_0C55&PID_0220&MI_02

[DriverInstall]
CopyFiles=DriverCopyFiles
AddReg=DriverInstall.AddReg

[DriverCopyFiles]
usbser.sys,,,0x20

[DriverInstall.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,usbser.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.Services]
AddService=usbser, 0x00000002, DriverService

[DriverService]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\usbser.sys


;------------------------------------------------------------------------------
;  Windows 64-bit Vista/Win7 Sections
;------------------------------------------------------------------------------

[DeviceList.NTamd64]
%DESCRIPTION_0%=DriverInstall, USB\VID_0451&PID_BEF0&MI_00
%DESCRIPTION_1%=DriverInstall, USB\VID_0451&PID_BEF0&MI_02
%DESCRIPTION_0%=DriverInstall, USB\VID_0C55&PID_0220&MI_00
%DESCRIPTION_1%=DriverInstall, USB\VID_0C55&PID_0220&MI_02

[DriverInstall.NTamd64]
;;;CopyFiles=DriverCopyFiles.NTamd64
CopyFiles = FakeModemCopyFileSection

AddReg=DriverInstall.NTamd64.AddReg

;;[DriverCopyFiles.NTamd64]
;;usbser.sys,,,0x20

[DriverInstall.NTamd64.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,usbser.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.NTamd64.Services]
AddService=usbser, 0x00000002, DriverService.NTamd64

[DriverService.NTamd64]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\usbser.sys

;------------------------------------------------------------------------------
;  String Definitions
;------------------------------------------------------------------------------

[Strings]
MFGFILENAME   = "xds2xx_usb_cmp"
MFGNAME       = "Texas Instruments Incorporated"
DESCRIPTION_0 = "XDS2xx Emulator CDC Serial Port"
DESCRIPTION_1 = "XDS2xx User CDC Serial Port"
SERVICE       = "XDS2xx Emulator CDC Serial Port"

you can find more details here:

http://www.microchip.com/forums/m488342.aspx

Why CDC Serial Device installation fails on Windows Vista and 7 ?

Hi,

I'm having the same problem with Windows 7 64-bit. Cannot use an XDS2xx emulator because Windows 7 does not install the drivers correctly. I have also tried the patch to the xds2xx_usb_cmp.inf file but the Windows device manager shows :

  The drivers for this device are not installed. (Code 28)

  There is no driver selected for the device information set or element.

  To find a driver for this device, click Update Driver.

Any other way to get these drivers installed correctly on a Windows 7 64-bit machine ?

Thanks in advance for any fixes or workarounds.

Mike

Hi,

looks like everythink is working out of the box on windows 7 64 Bit. I had to set up a new computer with windows 7 and 64Bit today. First I installed CCS v6 and afterwards I connected XDS200 and than XDS100. Both Connectors are getting there drivers from windows. And afterwards they are full functional with CCS. Everything is working fine.

Sorry, no useful information for people with trouble on this topic.

Best Regards,

Frank

Hi,

I have exactly the same problem as Mike. My OS is Windows 7 64-bit and I get the same error message in device manager.

Here is what I have tried already:

• Manually install driver from C:\ti\ccsv5\ccs_base\emulation\windows\xds2xx_drivers
• patch xds2xx_usb_cmp.inf as described above
• plug into different USB port
• update XDS emulation package to 5.1.641.0

Mike did you manage to get your XDS200 work in the meantime?

Any other suggestions, fixes or workarounds?

Thanks in advance

Benny