When I try WinUSB (v6.1.7600.16385) driver, sigrok shows ASIX Sigma on scan, but sampling doesn't work: sigrok-cli --driver asix-sigma --samples 5 --channels=1-3 sr: asix-sigma: ftdi_usb_open failed: usb_open() failed sr: asix-sigma: ftdi_write_data failed: usb bulk write failed sr: asix-sigma: ftdi_write_data failed: usb bulk write failed ... It works fine with libusbK (v3.0.7.0). Setup: ASIX Sigma 2 LA Windows 7 Pro Zadig 2.2 Latest nightly build of sigrok (both PulsView and sigrok-cli)
Hi, it's possible that there is an issue with the special libusb branch we're using (only on Windows), that contains changes which have not yet been merged into mainline libusb: https://github.com/dickens/libusb/commits/event-abstraction-v4 Maybe one of those changes affects the Sigma use-case, not sure. Might be worth investigating. I personally don't have a Sigma so I cannot debug this easily, unfortunately.
Hi, is this still reproducible with the current nightly installers? Either with WinUSB or libusbK Zadig drivers? If yes, please provide an updated "-l 5" log.
Is it related to previous driver versions' opening the USB device multiple times perhaps? Which got fixed in 2017-06 when bug 471 got resolved. Closing the report due to reporter's inactivity. Applied fixes since then and lack of feedback suggest the device is usable. A workaround was available at the time of the initial report already. Feel free to re-open when recent versions still are affected.
(In reply to Uwe Hermann from comment #1) > Hi, it's possible that there is an issue with the special libusb branch > we're using (only on Windows), that contains changes which have not yet been > merged into mainline libusb: > > https://github.com/dickens/libusb/commits/event-abstraction-v4 > > Maybe one of those changes affects the Sigma use-case, not sure. Might be > worth investigating. I personally don't have a Sigma so I cannot debug this > easily, unfortunately. Hi Uwe, It seems the mxe patch is still trying to fetch https://github.com/dickens/libusb/archive/event-abstraction-v4.zip But is 404 now.
(In reply to iamseer from comment #4) > (In reply to Uwe Hermann from comment #1) > > Hi, it's possible that there is an issue with the special libusb branch > > we're using (only on Windows), that contains changes which have not yet been > > merged into mainline libusb: > > > > https://github.com/dickens/libusb/commits/event-abstraction-v4 > > > > Maybe one of those changes affects the Sigma use-case, not sure. Might be > > worth investigating. I personally don't have a Sigma so I cannot debug this > > easily, unfortunately. > > Hi Uwe, > It seems the mxe patch is still trying to fetch > https://github.com/dickens/libusb/archive/event-abstraction-v4.zip > But is 404 now. It seems event-abstraction-v4 branch was removed. When I change link in libusb1.mk to master. libusb1 seems passed $(PKG)_CHECKSUM := bea7a412d61468e5e4eedcca0abb63e9c762d83c0fae58b54421b25f4c293d97 $(PKG)_SUBDIR := libusb-master $(PKG)_FILE := libusb-master.zip $(PKG)_URL := https://github.com/dickens/libusb/archive/master.zip