Using the signed CYUSB3 driver from the development kit in an end product. | Cypress Semiconductor
Using the signed CYUSB3 driver from the development kit in an end product.
Now that the CyUSB3 driver has been released for the FX3 development kit as WHQL certified and signed by Microsoft, it is possible to set the VID/PID in the firmware of any FX2/FX3 device to 0x04B4/0x00F0, and the device will enumerate quite happily under Windows 7 x64 as a "Cypress USB BulkloopExample" with the unmodified driver.
In theory lots of different products from lots of different manufacturers could exist with this VID/PID pair and all come up as a "Cypress USB BulkloopExample" under Windows device manager.
It could then be up to their application software to decide what kind of device each of them really is, based on, for example, the vendor and product strings from the USB descriptor.
If a company doesn't mind that:
Their product will appear as a "Cypress USB BulkloopExample" in device manager.
Their application software will have to identify what such a device really is using another method, e.g. the USB descriptor vendor/product strings.
Their product probably won't be compatible with software from other providers, unless this idea catches on.
What reasons are there for a company not to sell such a product? (Technical or legal)
The motivation for doing so being the very significant amount of time and money saved in avoiding obtaining a VID and code-signing certificate. An additional benefit being that since the driver is already signed by Microsoft, no warning whatsoever appears when the device is installed. (A regular code-signing certificate will produce a “Do you trust this publisher?” type warning, which can only be avoided by installing the certificate into the trustedpublisher store.)