Hi Kevin, I have also this Kingst LA2016 device and it doesn't work with sigrok on Windows. The interface number should be changed in protocol.h line 37, and be used in the line 505 you cited.
But this change is not sufficient. The communication with the device stucks later when the IN transfer should be read. I don't have a solution, sorry. Regards, Helge Am 09.12.2020 um 14:46 schrieb Kevin Grant: > > Hello, > > Log: > > sr: kingst-la2016: Found a LA2016 device. > sr: kingst-la2016: device at 'usb/1-5' has no firmware loaded! > sr: ezusb: uploading firmware to device on 1.7 > *ezusb: Unable to set configuration: LIBUSB_ERROR_INVALID_PARAM* > sr: kingst-la2016: uC firmware upload failed! > > I think this is because the USB device descriptors show the > configuration index as 0x01 (in USB Tree View[1]) but PulseView tries > to set configuration 0x00. > src/hardware/kingst-la2016/protocol.c > <https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/kingst-la2016/protocol.c;h=0b4a8bf36019d0a18d97c2412e8af7790c81e162;hb=HEAD> > 505 return ezusb_upload_firmware(sr_ctx, dev, 0, fw_file); > > By contrast, the little saleae clone I have works, it also shows > configuration index as 0x01 and PulseView sets configuration 0x01 for that > src/hardware/fx2lafw/protocol.h > <https://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/fx2lafw/protocol.h;h=3f240c590eb1bb765b991796a2c8619d45aa03f8;hb=HEAD> > 35 #define USB_CONFIGURATION 1 > > If anyone has LA2016 working on Windows, please let me know. > > Regards, > > Kevin > > [1] https://www.uwe-sieber.de/usbtreeview_e.html > > > > _______________________________________________ > sigrok-devel mailing list > sigrok-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sigrok-devel
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
