FTDI devices visible with UsbDkController, but not to libusbx #39
Comments
|
Did it work with UsbDk 1.0.16? |
|
Could you please post log of libusbx for the problematic case? |
|
1.0.16 works |
[timestamp] [threadID] facility level [function call][ 0.000000] [00000d44] libusb: debug [libusb_init] created default context |
|
Another trace [timestamp] [threadID] facility level [function call][ 0.000000] [00002820] libusb: debug [libusb_init] created default context |
|
Hmmm, that is interesting. Could you please also provide UsbDk traces for case when devices appear in the list and cases when they don't. It is important to have UsbDk device trace from device plug and until libusb_get_device_list return. (As usually see this for instructions on trace collection) Thanks in advance, |
|
Non-working case |
|
Working... |
|
any news? |
|
Hi, Not yet. Sorry for the delay, we are busy with Win10 support and a bunch of other tasks. ~Dmitry |
|
any news? |
|
We do not reproduce any problem with similar FTDI device. Something is definitely going wrong as FTDIBUS... device shall not be listed under UsbDk controller.
Thanks |
|
|
|
Are these screenshots for USB\VID_0403&PID_6010&MI_00 and USB\VID_0403&PID_6010&MI_01? |
|
Yes. I did some further experiments, it seems to be timing sensitive. A delay of about 300ms between enumerating and connecting seems to make it work |
|
https://drive.google.com/file/d/0B9gp3tZmgMhdMmVtX3pRZ1pYQlE/view?usp=sharing Please try this private build of UsbDk. It requires test signing to be enabled on the machine (see readme.txt inside). If it does not fix the problem, please do the record as was done earlier. |
|
I don't see any change in behaviour... |
|
Without delay |
|
With 300ms delay |
|
Can you please verify that installed UsbDk is this one. Due to some reason one of records dated March 1. |
|
Additionally: please provide the result of "usbdkcontroller.exe -n" |
|
I'm quite sure the latest logs provided are done with UsbDk driver 1.0-17 and not with private version. Please recheck. |
|
Timestamp: Created: Yesterday, 28. März 2017, 13:03:36 So it looks to me like it was indeed the test version. This is Win7 x64 ./UsbDkController.exe -n
|
|
Now, it seems OK and FTDIBUS device is not enumerated (as it should be). If the functional problem still happens (as it was with 1.0-17), please make a record when redirection does not work and (if possible) when it does. Previous records were done with 1.0-17 (I can see it by trace events that are different in test version). |
|
usbdkworking.zip and usbdknotworking.zip are identical, the file contains inside zip with logs from UsbDk-1.0-17 dated March 1 |
|
I would suggest to keep old ETL files aside and then delete them before making record. |
|
Another try... |
|
Can you please attach the image of this specific model of FTDI device? |
|
With private build of UsbDk is it still happens the FTDI device is enumerated in UsbDkController and not visible in lubusb list? Can you please describe exactly what you do via libusb? |
|
I'm experiencing the same problem. Listing devices with libusb using UsbDk as a driver sometimes misses some device. It's very erratic. |
|
@dmitryfleytman That seems like a very good explanation. Several thins:
Would that mean that this issue (#39) is just another manifestation of the same root cause as #43? |
|
We are not sure yet. Waiting for answers from @tsailer... |
|
@dmitryfleytman Ooops sorry, I edited my comment while you were replying. Please see udpated version above. |
|
|
Hi @tsailer Did you have a chance to check the private build provided by Yuri (#39 (comment)). Thanks, |
|
Hi @dmitryfleytman, please see the logs in the comment from March 29 Thanks, |
|
This issue is the same as #43 |
With UsbDk 1.0.17:
./UsbDkController.exe -n
Enumerate USB devices
Found 6 USB devices:
0. FilterID: 1, Port: 1, ID: 8087:8001, Configs: 1, Speed: 3
USB\VID_8087&PID_8001 1
Descriptor for configuration #0: size 25
USB\VID_8087&PID_0A2A 3
Descriptor for configuration #0: size 177
USB\VID_1BCF&PID_2B8D 6
Descriptor for configuration #0: size 737
USB\VID_0A5C&PID_5804 0123456789ABCD
Descriptor for configuration #0: size 269
USB\VID_0403&PID_6010 AX00000003
Descriptor for configuration #0: size 55
FTDIBUS\VID_0403+PID_6010+AX00000003B 0000
Descriptor for configuration #0: size 32
Output from libusb_get_device_list:
index 0 vendor 0x8087 product 0x8001
index 1 vendor 0x8087 product 0x0a2a
index 2 vendor 0x1bcf product 0x2b8d
index 3 vendor 0x0a5c product 0x5804
This is with the fedora mingw libusbx.
Name : mingw64-libusbx
Version : 1.0.21
Release : 1.fc25
Architecture: noarch
Install Date: Mon 27 Feb 2017 02:35:09 PM CET
Group : Unspecified
Size : 333790
License : LGPLv2+
Signature : RSA/SHA256, Sat 29 Oct 2016 03:58:53 PM CEST, Key ID 4089d8f2fdb19c98
Source RPM : mingw-libusbx-1.0.21-1.fc25.src.rpm
Build Date : Sat 29 Oct 2016 03:56:47 PM CEST
Build Host : buildvm-22.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http://libusbx.org/
Summary : MinGW library which allows userspace access to USB devices
Description :
This package contains the header files and libraries needed to develop
applications that use libusbx.
This is on Windows 7. It is somewhat erratic, sometimes the ftdi devices are there, more often however not.
The text was updated successfully, but these errors were encountered: