Ouch, I missed to attach the log. -----Original Message----- From: Helge Kruse [mailto:helge.kr...@gmx.net] Sent: Sunday, October 18, 2020 11:47 AM To: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016
Hi Paul, > I think you're supposed to run --scan for any detection attempts to take place. I agree. But I expected the device in the hardware list even if it is not connected as the other devices. > it looks like you're using 0.5.1 which seems to predate that commit. I use the latest version https://sigrok.org/download/binary/sigrok-cli/sigrok-cli-0.7.1-x86_64-instal ler.exe Unfortunately I failed to find any tag in the repository git://sigrok.org/sigrok-cli. So I can't see what has been used to build the version 0.7.1 of the software. The last entry in the file NEWS in the current repository is dated with 2017-06-12 for version 0.7.0. So there is also no information. I downloaded the nightly build (debug). It's also version 0.7.1. That's confusing me. Anyway, the nightly build should support the LA2016. The --scan result is attached. The essential lines are probably: sr: [00:01.403000] kingst-la2016: Found a LA2016 device. sr: [00:01.403000] kingst-la2016: device at 'usb/2-8' has no firmware loaded! sr: [00:01.404000] ezusb: uploading firmware to device on 2.11 sr: [00:01.405000] ezusb: Unable to set configuration: LIBUSB_ERROR_INVALID_PARAM sr: [00:01.405000] kingst-la2016: uC firmware upload failed! The firmware search path includes the directory C:\ProgramData\sigrok-firmware. Therefore I added the directory listing for it. Is there any other option than "-l 5" to get more information? -----Original Message----- From: Paul Fertser [mailto:fercer...@gmail.com] Sent: Sunday, October 18, 2020 10:47 AM To: Helge Kruse Cc: sigrok-devel@lists.sourceforge.net Subject: Re: [sigrok-devel] Getting firmware for Kingston LA2016 On Sun, Oct 18, 2020 at 10:32:31AM +0200, Helge Kruse wrote: > I started "sigrok-cli -L -l5 > sigrok-cli.log 2>&1". The output is attached, I think you're supposed to run --scan for any detection attempts to take place. Also, the support was added with https://sigrok.org/gitweb/?p=libsigrok.git;a=commitdiff;h=f2cd2debf9dcbf0e83 ec70d8ea41d8421a400dfd , in June this year, are you sure your libsigrok is new enough? To me it looks like you're using 0.5.1 which seems to predate that commit. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
sigrok-cli-scan.log
Description: Binary data
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
