From: Xiaofan C. <xia...@gm...> - 2018-06-28 11:51:46
|
On Thu, Jun 28, 2018 at 10:08 AM, Chengda Guo <che...@ca...> wrote: > > Hi Xiaofan, > > My WCID device's descriptor like below shows: > That is not really the descriptor. You should have something like this. http://janaxelson.com/files/ms_os_10_descriptors.c More explanation here. https://github.com/pbatard/libwdi/wiki/WCID-Devices > And when I use xusb.exe to check the device's descriptor, it can't open the > device like below shows: Then I think your FW has an issue. Read the above libwdi wiki page and see if you can learn something there. > And then I debug into the source code of LibUsbk's example "open-device", in the > function l_EnumKey_Instances() at lusbk_device_list.c file. When enum > DeviceInterface, got an error code 259(No more data is available) like below shows: As mentioned in the previous email, libusbK has a problem -- it will not work for your use case unfortunately even if you fix your FW. You may want to try out libusb Windows -- still you need to fix your FW. > So I guess maybe my FW is missing DeviceInterfaceGUID handling like your > previous mail said. But I'm not the expert of device FW, so I'm not sure about this. > Do you agree with me or have some other advice? > -- Xiaofan |