"WinUSB Device" implementation for Tivaware

Another modification that you have suggested is as follows

USB_VID_TI_1CBE, // <--- ex, 0xFF00
USB_PID_BULK, // <--- ex, 0x1234

Are these values fixed?

And if a failed instance of the driver has been already executed, then would the new method still work?

Also on a slightly different note, the TivaWare USB drivers do not seem to work on Win10. Is this issue of TivaWare drivers not being recognized on Win10 machines also from the same cause.

Hi Amit,

The ICDI and CDC fail install on Win 10 machines.

     dvi:           Rank         - 0x80ff0001
     dvi:           Signer Score - Not digitally signed

On the x64 platforms, installation failed.

Double clicking on the .cat files, you'll see the status of the certification by the .cat file.
All of them are expired.

- The major certificate
 Publisher: <StellarisWare Test Certificate> - just for test on development

- Sub certificate
 Publisher: VeriSign Time Stamping Services Signer - G2
 valid in: 2007/06/15 - 2012/06/15

Tsuneo

Amit,

I believe you have trouble of version control on TI server.

1) The digital signing for .cat files are out of date on all of the ICDI drivers, distributed in this web page.
www.ti.com/.../stellaris_icdi_drivers

2) All of catalog (.cat) files in windows_drivers folder doesn't have digital sign yet, in Recent TivaWare releases.
- TivaWare_C_Series-2.1.2.111  - not signed yet
- TivaWare_C_Series-2.1.1.71   - not signed yet

On the other hand, these former releases have validly-signed .cat files.
- TivaWare_C_Series-2.1.0.12573 - OK
- TivaWare_C_Series-2.0.1.11577 - OK

The status of digital sign is displayed by clicking on the .cat file on Windows PC.
Please check them.


The trouble on Windows10 should be touched after fixing this trouble first.
Unless we would examine the same version, our discussion should diverge.

Tsuneo

Hi Tsuneo,

First, THANK YOU for sharing your wonderful code and expertise -- this has been fantastic.  

I was able to get this working on my device, but there was a small issue I ran into -- namely, my device showed up in device manager with the proper drivers, but my client program that I wrote to communicate with the device could not find it.  After digging into it a bit, I found a very helpful note on this page () that does a good job of explaining what was going on.  When returning the DeviceInterfaceGUID request, LibUsbDotNet (and several other libraries?) seem hardcoded to look ONLY for DeviceInterfaceGUIDs.  

Because of this fault in those libraries, when your patch returned the DeviceInterfaceGUID property, it wasn't being enumerated by my libraries.  

I (clumsily) modified your code to return a DeviceInterfaceGUIDs response instead (using USB_EX_PROPERTY_REG_MULTI_SZ instead of USB_EX_PROPERTY_REG_SZ), and that seems to have done the trick -- the device shows up and is enumerated perfectly by LibUsbDotNet.  

In case you (or anyone else) is curious, I'm attaching my patched files.usbdMSdesc.h

160a161
>     uint16_t wPropertyNameDummy;    // Dummy property name to be at the end of the list for use by REG_MULTI_SZ
162a164
>     uint16_t wPropertyDataDummy;    // Dummy property data to be at the end of the list for use by REG_MULTI_SZ
164a167,171
> 
> // NOTE: Switching this from REG_SZ to REG_MULTI_SZ because LibUsbDotNet is hardcoded to look for DeviceInterfaceGUIDs as part of locating WinUSB devices.
> //  As such, it won't identify a WinUSB device that sends DeviceInterfaceGUID.
> //  For more information, see the extended note on this topic here: https://github.com/BrandonLWhite/Stellaris-LaunchPad-UsbDevBulk-AutoWinusbInstall
> // HACK: To do this, we add a dummy property with null bytes to terminate the list expected by REG_MULTI_SZ
167,171c174,180
<     .dwPropertyDataType   = USB_EX_PROPERTY_REG_SZ, \
<     .wPropertyNameLength  = USB_EX_PROPERTY_NAME_LENGTH_IFGUID, \
<     .bPropertyName        = L"DeviceInterfaceGUID", \
<     .dwPropertyDataLength = USB_EX_PROPERTY_DATA_LEN_IFGUID, \
<     .bPropertyData        = guid \
---
>     .dwPropertyDataType   = USB_EX_PROPERTY_REG_MULTI_SZ, \
>     .wPropertyNameLength  = USB_EX_PROPERTY_NAME_LENGTH_IFGUID + 0x02, \
>     .bPropertyName        = L"DeviceInterfaceGUIDs", \
> 	.wPropertyNameDummy   = 0, \
>     .dwPropertyDataLength = USB_EX_PROPERTY_DATA_LEN_IFGUID + 0x02, \
>     .bPropertyData        = guid, \
> 	.wPropertyDataDummy   = 0 \

Thank you so very much for your work!  I too hope that this can get rolled into the the main TivaWare repository, as not having to deal with signing drivers GREATLY simplifies the development of small USB peripheral projects.  

Much appreciated!

--clint