• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 1678 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.

GUI composer v5.5 runtime & XDS100v2 Windows XP USB driver INF

Genatco
Guru 56198 points

A functional XDS100v2 JTAG device is removed from Windows 7 computer and taken over to another computer in the building. This computer having Windows XP Sp1 and fresh GUI composer 5.5 runtime installation.

User then plugs in the XDS100v2 into a functional USB port. Win-XP plug and play wizard "Detected new hardware search windows update for drivers?" Sure "bla bla bla" no driver is found do you want to install the manufacturers driver or search for driver on local computer?

User traverses folder tree to find C:\ti\guicomposer\ccs_base\emulation\drivers\stellaris\icdi "Click next to continue", "No driver was found matching the installed device" do you want to search "Windows Update for the device" BANG!

Win-XP device manager shows two USB composite devices, one has properties XDS100v the other is blank. and shows 2 - ??UNKNOWN USB Device under "Unknown Hardware" BTW: USB mouse and Keyboard work great.

XDS100v2 device works ok on the Win7 computer with CCS-5.4 and GUI Composer 5.5 installed

Wiki support pages have no such scenario listed. User was sent from Black Hawk drivers page to Wiki support page after finding no Windows XP USB drivers for the XDS100V2. However the WIn-7 computer Programs and Features  clearly shows several CCS5 USB XDS100 software drivers installed.

Please advise how to fix this issue without installing CCS5.x on this XP computer???

 

  • 0
    Guru 56198 points

    Never have seen Windows XP device wizard give such problem. Seemingly the UNC path first chosen installing a device driver confuses Window add new hardware wizard.

    The folder tree opens long under Emulation folder pushing Windows directory far below the Drivers directory. Later discovered this and traversed to that Windows directory many times however the damage was done even though no driver had installed. UN-installed GCP5.5 and all TI emulators, CDM drivers and like. Restarted Win-XP installed GCP5.5 restarted Win-XP to freshen all registry keys and plugged in the XDS100v2 while watching in device manager (No more sneaky moves by him) and attempted install FTDI in Windows directory in this path below. Oddly the add new hardware wizard barked at this driver one time although did install both TI XDS100 USB A & B channels. 

    Proper UNC path C:\ti\guicomposer\ccs_base\emulation\windows\xds100_drivers\ftdi

     

     Manual install of the FTDI proceeded on first attempts to correct the driver fault but did not register the device class in the registry or the device manager oddly enough.