My Stellaris Launchpad is not recognized by Windows 7 64

José,

Is it possible that the other two drivers have already been installed?  With the device plugged through the Device USB port, you do not see any Stellaris or unknown devices under Ports, Stellaris In-Circuit Debug Interface, Stellaris Device Firmware Upgrade, or Other Devices in the Windows Device Manager?  Just the one yellow exclamation mark In-Circuit Debug Interface under Other Devices?

What happens when you install the driver for the one "In-Circuit Debug Interface"?  Follow the instructions for Windows 7 driver installation in this document.  The driver installation is a little different between Windows XP and Windows 7.  I have been successful in installing all three of the Stellaris ICDI and virtual COM port drivers on a Windows 7 64 machine, so I don't think it's an issue with Windows 7 in particular.

-Rebecca

Hi Rebeca,

I have two boards, one which works fine and another which doesn't work. 

For the one that works I can only see one device, under "Other Devices",  that is called "In-Circuit Debug Interface". I have tried to remove the installed drivers and connect the non-working board without any luck, if I connect the working board the drivers install without any problem.

I also tried to install the drivers manually (from here) but it failed reporting that the folder contained no drivers for the device.

I had already tried the steps in the document you indicate.

My guess is that something is incorrectly programmed in the FTDI or other USB serial interface, and it is reporting the incorrect Vendor ID, Product ID, etc...

In attachment I put two files of the information obtained using the UsbView tool from Microsoft.

2625.stellaris-not-working.txt

8267.stellaris-working.txt

José,

You may be on to something with the incorrect VID and PID on the Stellaris ICDI device.

With the non-working LaunchPad connected through Windows 7, can you go to the Device Manager, right click the one device, go to properties->"Details" tab->under "Property" select "Hardware IDs" and report back exactly what you see there.  Can you also do this when it's connect through Windows XP with the virtual machine and for Windows 7 with your working LaunchPad.

Can you please provide a picture of the bottom of your non-working LaunchPad (in particular, if there are any white stickers)?  Was the RGB quickstart application running on the device when you first applied power?

-Rebecca

Hi Rebecca,

Regarding the RGB quickstart application it is running and the buttons work correctly.

In attachment the pictures you have requested.

José,

Your VID and PID appear to be correct.  Something is preventing the configuration over USB from happening.  Have you tried connecting your LaunchPad to a different computer running Windows 7 64-bit to see if this issue still occurs?

-Rebecca

Jose,

Ignore what I just posted :).  That's great news!  Have fun with your LaunchPad!

-Rebecca

I experienced the exact same problem described in this thread (W7 x64, only a single "In-Circuit Debug Interface" device showing, drivers won't load, but board functioning on another computer). Re-installing Windows is a non-starter as a solution. Fortunately, I managed to get the ICDI drivers installed without re-installing Windows. For the benefit of any future searchers here is a quick summary of the situation and my solution, presented without warranty. Please use at your own risk.

The ICDI is a composite USB device. W7 should load a generic system driver (usbccgp.sys) to control the parent composite automatically when the hardware is detected, and subsequently enumerate the 3 child devices. My system has no issues with other composite devices, but for an unknown reason this driver was not loaded, leaving the composite device without a driver. From the device ids shown in the earlier screenshot it is apparent the original poster's system was in the same situation.

To resolve the issue (following clues from here http://msdn.microsoft.com/en-us/library/windows/hardware/ff537109%28v=vs.85%29.aspx and elsewhere), the solution is to build a .inf that explicitly installs the usbccgp.sys as the driver for the composite device. Subsequently the 3 child devices will appear and the provided drivers can be loaded per the provided instructions. Create a file called "parent.inf" in the "stellaris_icdi_drivers" directory and search that directory when installing a driver for the single unknown device.

This cost me quite a few hours, hopefully I can save someone else some time, effort and grief.

------- parent.inf begins below here ------

;
;   Stellaris USB ICDI driver installation file.
;
;   Copyright (c) 2010 Texas Instruments Incorporated.  All rights reserved.
;

[Version]
Signature = "$Windows NT$"
Class = StellarisICDIDeviceClass
ClassGuid={F5450C06-EB58-420e-8F98-A76C5D4AFB19}
Provider=%MFGNAME%
CatalogFile.NTx86=stellaris_icdi_debug_x86.cat
CatalogFile.NTamd64=stellaris_icdi_debug_amd64.cat
DriverVer=09/02/2011,2.0.7922

; ========== Manufacturer/Models sections ===========

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

[StellarisICDIDevice.NTamd64]
"Stellaris Parent Composite"=ParentInstall,USB\Vid_1CBE&Pid_00FD

; =================== Installation ===================

; Composite
[ParentInstall.NTamd64]
Include=usb.inf
Needs=Composite.Dev.NT

[ParentInstall.NTamd64.Services]
AddService = usbccgp, 0x00000002, ParentInstall.AddService
;Include=usb.inf
;Needs=CommonClassParent.AddService,Composite.Dev.NT.Services

[ParentInstall.AddService]
DisplayName    = %GenericParent.SvcDesc%
ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
StartType      = 3                  ; SERVICE_DEMAND_START
ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
ServiceBinary  = %12%\usbccgp.sys
LoadOrderGroup = Base

; Stellaris ICDI DFU Device
; ================= Source Media Section =====================

[SourceDisksNames]
1=%DISKNAME%,,,
2=%DISKNAME%,,,\i386
3=%DISKNAME%,,,\amd64

[SourceDisksFiles]
%12%\usbser.sys=1

[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll=2
WdfCoInstaller01009.dll=2
lmusbdll.dll=2
lmusbdll.lib=2
lmusbicdi.dll=2
lmusbicdi.lib=2
lmdfu.dll=2
lmdfu.lib=2

[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll=3
WdfCoInstaller01009.dll=3
lmusbdll.dll=2
lmusbdll.lib=2
lmusbicdi.dll=2
lmusbicdi.lib=2
lmdfu.dll=2
lmdfu.lib=2
lmusbdll64.dll=3
lmusbdll64.lib=3
lmusbicdi64.dll=3
lmusbicdi64.lib=3
lmdfu64.dll=3
lmdfu64.lib=3

; =================== Strings ===================

; Note: Replace these as appropriate to describe your device.
[Strings]
MFGNAME       = "Texas Instruments, Inc."
DISKNAME      = "Stellaris ICDI Device"
DESCRIPTION_1 = "Stellaris ICDI JTAG/SWD Interface"
DESCRIPTION_2 = "Stellaris ICDI DFU Device"
SERVICE       = "Stellaris ICDI"
WinUSB_SvcDesc="WinUSB"
ICDIClassDisplayName="Stellaris In-Circuit Debug Interface"

GenericParent.SvcDesc="Microsoft USB Generic Parent Driver"

Tom,

I am experiencing the same problem, and tried your fix.  It got me a bit closer as it looked as if something was being installed, but then it complained while trying to install the composite device  with "The install class is not present or invalid."

Any idea where I might be getting stuck?  I'm running win7 64bit.

Thnx!

Reza

Reza, I have not seen that error msg before. You can try the instructions from Peter Ryall at the link below. After posting the info above I continued to have issues with other composite devices and couldn't hack up an inf for all of them. Copying usb.inf from the cache as described in Peter's answer resolved them. 

http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/usb-composite-device-driver/a0cc4d40-1dd9-4c2c-9c24-7e5e9287b147

Best luck,

Tom

Tom,

I've been going nuts trying to figure this stuff out.  Your suggestion worked great!  I was indeed missing my usb.inf file.  Not sure how that happened.  Been posting to microsoft dev boards and that's not been helpful at all.  

Thanks again!

Reza

Thanks all for posting.

I followed your comments to:

http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/usb-composite-device-driver/a0cc4d40-1dd9-4c2c-9c24-7e5e9287b147

I unzipped the drivers files into a new folder "any name" and added the

C:\Windows\System32\DriverStore\FileRepository\usb.inf_amd64_neutral_269d7150439b3372

folder to the new "any name" driver folder.

Then updated my drivers using device manager from "any name" folder, issue solved.

Thanks again and hope this helps anyone else looking to solve this.