2

We have an application which uses an off-the-shelf Bluetooth USB dongle (CSR8510-A10). Unfortunately, our app needs better control over the BLE hardware than Windows generic driver can provide. Our solution was to write our own BLE-HCI code, which works great, but requires the user manually replace the generic BLE driver with WinUSB (e.g. by using Zadig).

Our next step is to streamline the user experience to something like: 1. install our application, which can run some WinUSB driver installer 2. plug-in the dongle 3. --> Windows 7/8/10 should recognize it and use the WinUSB driver supplied in step 1

The dongle comes pre-loaded with firmware, which I cannot modify. It is possible, however, to change many attributes, including VendorId, ProductId, WCID etc, which we have - the VID/PID are now our own.

Questions: - Is it possible to install a inf file, such that Windows ignores the WCID provided by the dongle's firmware? - If not, is there another way to achieve this functionality, without modifying the dongle's firmware?

bavaza
  • 10,319
  • 10
  • 64
  • 103
  • If it's just for your computer, then [Zadig](https://zadig.akeo.ie/) should do the trick. If you want to create a device that will use WinUSB on all computers, then the USB descriptor should contain a Microsoft WCID feature descriptor. – Codo Aug 11 '19 at 17:36
  • I'm not aware of any other solution. What's the goal anyway? What do you want your Bluetooth dongle to become eventually? – Codo Aug 12 '19 at 11:25
  • What is a "HCI dri"? – Codo Aug 12 '19 at 18:38
  • We wrote an BLE HCI controller, which works with the dongle, when we replace the default driver with WinUSB using Zadig. We are looking for a way to achieve this without the need for Zadig. – bavaza Aug 12 '19 at 18:47
  • @Codo - do you know if it is possible (other than using Zadig), to make Windows ignore the WCID, and use my driver instead (we can create a cab/inf file with the appropriate VID/PID). Thanks! – bavaza Aug 13 '19 at 13:32
  • It might be possible with .inf files. But it's not my turf. You have hardly provided any information about the product you're using, why you can change the product class but not make other changes. If you provided more information, other people might direct you to solutions you'd never have thought of. – Codo Aug 13 '19 at 17:40
  • @Codo - thanks for your help. The dongle is a CSR8510 A10 Bluetooth controller. I can only change some properties of its existing descriptors, using a utility program, but I do not have, (and AFAIK, cannot obtain), the source code. – bavaza Aug 18 '19 at 06:56

0 Answers0