Hello Kevin, I think yes, your are wrong.
The problem is not the device. Although the EEPROM content is a bit different, the Kingst LA2016 works if it is connected to a Linux version of sigrok. Anyway, here is the non-FF content of the EEPROM: c0 a1 77 a2 01 00 00 00 08 f7 00 00 08 f7 10 ef da da d8 2b a7 bf 74 7c 34 a5 26 32 ff e8 a3 81 20 08 df f7 ff ff ff ff ff ff ff ff ff ff ff ff Running the same LA2016 with the Windows version fails. Florian made a lot of tries to diagnose problems and to find a necessary fix. But finally this didn't succeed. We should keep in mind that the Windows software is different. It is linked with the libusb built in the MXE cross compiler. The original MXE is built with the current libusb, that is similar to the Linux version. For building sigrok for Windows you have to apply a patch that contains this difference: https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob;f=cross-compile/mingw/mxe_fixes.patch;h=e0e2b6a10a018bdcc20ac0531cf4bfbacb9f2291;hb=HEAD#l189 Therefore the MXE, prepared for building sigrok, uses a libusb based on version 1.0.20-rc3. The current libusb version is 1.0.23. The LIB_API_VERSION changed from 0x01000104 to 0x01000108. Additionally there are the differences that has been implemented to make libusb compatible to sigrok on Windows. Best regards, Helge Am 11.12.2020 um 20:01 schrieb Kevin Grant: > > Hello, > > The EEPROM on the LA2016 can be read/written with the Python utility > called 'fx2tool'. > > On Windows I used Zadig to assign WinUSB as the driver, then; > > Read of the 24C02 256 byte EEPROM on Kingst LA2016 with v1.3.0 PCB: > > |pip install fx2 fx2tool -B -d 77a1:01a2 read_eeprom -W 1 0 256 c0 a1 > 77 a2 01 00 00 00 08 f7 00 00 08 f7 10 ef f2 9e 0e 1d f9 c4 40 86 34 > a5 26 32 ff e8 a3 81 20 11 df ee ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |It > would be good to confirm if this is the same as the "Jiankun" LA2016 EEPROM. > > Regards > > Kevin > > > On 2020-12-10 16:50, Kevin Grant wrote: > >> Hello, >> >> Apologies, I'm not sure whether to top post or bottom post in this >> mailing list. Please tell me if I got it wrong. >> >> It occurred to me that my unit and Helge's unit are Kingst brand, >> whereas the unit used by the developer may have been "Jiankun" >> (guessing because that unit is described on sigrok site). >> >> https://sigrok.org/wiki/Kingst_LA2016 >> <https://sigrok.org/wiki/Kingst_LA2016> >> >> Perhaps there are slight configuration differences (eeprom) between >> the two. Just a thought. I will try to read eeprom. >> >> Regards, >> >> Kevin >> >> >> On 2020-12-09 16:41, Helge Kruse wrote: >> >> 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 >> <https://www.uwe-sieber.de/usbtreeview_e.html> >> >> >> >> _______________________________________________ >> sigrok-devel mailing list >> sigrok-devel@lists.sourceforge.net >> <mailto:sigrok-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/sigrok-devel >> <https://lists.sourceforge.net/lists/listinfo/sigrok-devel> >> >> >> >> _______________________________________________ >> sigrok-devel mailing list >> sigrok-devel@lists.sourceforge.net >> <mailto:sigrok-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/sigrok-devel >> <https://lists.sourceforge.net/lists/listinfo/sigrok-devel> >> >> >> >> _______________________________________________ >> sigrok-devel mailing list >> sigrok-devel@lists.sourceforge.net >> <mailto:sigrok-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/sigrok-devel >> <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
