Bug 960 - FX2 device not found when attached to certain USB-Hubs
Summary: FX2 device not found when attached to certain USB-Hubs
Status: CONFIRMED
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Driver: fx2lafw (show other bugs)
Version: 0.3.0
Hardware: x86 Windows
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-27 20:01 CEST by evil_medi
Modified: 2018-10-02 18:15 CEST (History)
1 user (show)



Attachments
Zip of Snapshot and CLI printouts (6.07 KB, application/x-zip-compressed)
2017-05-27 20:01 CEST, evil_medi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description evil_medi 2017-05-27 20:01:24 CEST
Created attachment 308 [details]
Zip of Snapshot and CLI printouts

fyi: This issue was discussed on IRC (27.05.17) with user "uwe_".

Bug: When connecting an FX2 type device to the USB 2.0 Hub integrated into my screen, sigrok encounters errors when enumerating the device.

This issue does not appear when repeating the same process, while attaching the device directly to the motherboard.

Attached you will find the output from the two scenarios with the following command:

> set LIBUSB_DEBUG=1
> sigrok-cli.exe --driver fx2lafw --samples 1 -l 5

Also attached is print screen from the device enumeration from windows "Device Manager". The device has been installed with Zadig/WinUSB on both ports (direct/USB-Hub).
Comment 1 Uwe Hermann 2018-10-02 18:15:36 CEST
Can't reproduce this with a "standard" USB hub (not integrated into a monitor) on Windows 10 64bit with the current installer as of today. It probably only happens with *some* hubs and/or with "special" stuff integrated into monitors (?) Not really sure.

Your logs look a bit strange, though. The non_working.txt log suggests that run *did* work fine, the device is found and one sample has been gathered successfully.

Either way, it looks like there's not much we can do about this, it looks very much like a hardware and/or libusb issue to me, nothing we can fix in libsigrok per se.

Can you retry with the latest installer and "set LIBUSB_DEBUG=5" this time please? Maybe there's some useful hint in those logs.