Bug 650 - PulseView cannot find my Saleae Logic16 clone (KingST KQS3506-LA16100)
Summary: PulseView cannot find my Saleae Logic16 clone (KingST KQS3506-LA16100)
Status: CONFIRMED
Alias: None
Product: PulseView
Classification: Unclassified
Component: Other (show other bugs)
Version: unreleased development snapshot
Hardware: x86 Windows
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-08 12:25 CEST by rol.dob
Modified: 2019-08-10 10:14 CEST (History)
8 users (show)



Attachments
Images for zadig and PulseView (94.30 KB, application/x-7z-compressed)
2015-09-08 12:25 CEST, rol.dob
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rol.dob 2015-09-08 12:25:49 CEST
Created attachment 156 [details]
Images for zadig and PulseView

Hello,

I've tried the latest Windows nightly build on Windows7 (and around one year ago). I can see my "Saleae Logic16" in te decive combo box and when I select it the PulseView pops up an error message (see attached zadig.png).
(generic/unspecified error, Failed to select device)

I tried reinstall/replace driver with zadig. I tred all three drivers:
WinUSB (v6.1.7600.16385)
libusbK (v3.0.7.0)
libusb-win32 (v1.2.6.0)

I replaced the usb cable with shorter and longer... 

Please give advice what should I to do.

Best regards.

DR
Comment 1 Uwe Hermann 2015-09-08 16:26:24 CEST
Hi,

I guess you're missing the correct firmware and FPGA bitstream files (we cannot ship those as part of the installer, you have to extract them from the Saleae software).

http://sigrok.org/wiki/Windows#Firmware
http://sigrok.org/wiki/Saleae_Logic16#Firmware

Please report back if that fixes your issue so that we can close the bug report.
Comment 2 rol.dob 2015-09-08 18:04:00 CEST
(In reply to comment #1)
> Hi,
> 
> I guess you're missing the correct firmware and FPGA bitstream files (we
> cannot ship those as part of the installer, you have to extract them from
> the Saleae software).
> 
> http://sigrok.org/wiki/Windows#Firmware
> http://sigrok.org/wiki/Saleae_Logic16#Firmware
> 
> Please report back if that fixes your issue so that we can close the bug
> report.

Hi,

I have exactly same as http://sigrok.org/wiki/KingST_KQS3506-LA16100.
The revision 6.0. This is marked as supported device so I've thought it should work with PulseView and it's firmwares. Or not?

It has FX2LP and I have read that here:
http://sigrok.org/wiki/Saleae_Logic16#Firmware

"The firmware for the FX2LP is embedded in the vendor application as a set of Intel HEX lines. Each line is uploaded individually with a separate control transfer. The firmware currently occupies the address range [0x0000-0x145d], but is uploaded out of order. "

I've a Logic.exe. Should I disassemble the EXE for firmware?

Please help me what should I do.

Thank you.

Best regards.
Comment 3 Uwe Hermann 2015-09-09 16:13:18 CEST
Hi,

you should use the "sigrok-fwextract-saleae-logic16" script mentioned in the wiki to extract the three firmware/bitstream files from the Saleae software (it's a Python script that we usually use on Linux, but I guess it should also work on Windows if you have Python installed).

Then, place those three files (as mentioned in the wiki) into the directory where the other firmware files are located. On Windows this is e.g. C:\Program Files\sigrok\PulseView\firmware (or similar, depends where you installed PulseView).
Comment 4 rol.dob 2015-09-10 08:24:53 CEST
Hi,

I've downloaded and installed Python and your script. I tried it and I always get "Error: ELF signature not found" message. I tried with three Logic.exes. No results....
Comment 5 Uwe Hermann 2015-09-10 14:40:43 CEST
You need to download the Linux Saleae software and run the script against the "Logic" Linux executable (you can run the script itself on Windows, but the "Logic" executable has to be the one from the Saleae Linux software).
Comment 6 rol.dob 2015-09-10 19:42:45 CEST
Thank you for your help. 
Now, it works, but for only one capturing and on 500kHz. Higher capturing frequency does not provide any result on display. I always need to go to "connect to device" and scan/select Saleae logic 16... and it works again once on 500kHz.

Have you got any idea/solution?

(Should I have a cracked linux Logic as windows Logic.exe?)
Comment 7 rol.dob 2015-09-16 18:50:21 CEST
I have tried everything but it can capture only once and only on 500kHz.
So does Sigrok PulseView support with KingST KQ3506-LA16100 or not?

It seems to me it does not or is this a bug?
Comment 8 Soeren Apel 2016-04-17 22:52:54 CEST
If you're still interested in solving this issue and have access to a computer running linux, I'd be interested in the debug output ("pulseview -l 5") showing what pulseview does when you try aquiring data at more than 500kHz. Unfortunately, debug output isn't available on Windows unless you use a special build.

That said, wacky USB connections have always caused problems and I can see how you may be affected by this here. Please try a different USB cable (the clones usually come with very cheap ones that violate the USB specs), a different USB port (esp. USB2 vs. USB3) and if you use a USB hub, try a direct connection to the PC.
Comment 9 Rudolf 2016-09-12 11:09:18 CEST
Hello,

I've tried the latest Windows nightly build on Windows7-64,
and Windows 10-64. Unfortunately the same error.
I have tried 2 different proven USB cables.

This Saleae Logic16 clone works on Ubuntu 14.04-32,
and on Mac OS El Capitan 10.11.6 (with Homebrew).
See also http://www.rudiswiki.de/wiki9/SigrokDecoder

The Logic16 clone is seen, the firmware is uploaded, but then an error:
    Failed to receive reply to EP1 command 0x7d: LIBUSB_ERROR_IO.

What can I do from my side to help fixing the problem?
Regards, Rudolf

Use of zadig.exe:
Menu Options->List all devices
Logic S/16
Driver: WinUSB (v6.1.7600.16385)
USB ID: 21A9  1001

Use of sigrok-cli, with log level 5:
C:\Program Files (x86)\sigrok\sigrok-cli>sigrok-cli -d saleae-logic16 --samples
100 -l 5
sr: [00:00.000000] log: libsigrok loglevel set to 5.
sr: [00:00.000000] backend: libsigrok 0.5.0-git-d5794ad/3:0:0 (rt: 0.5.0-git-d57
94ad/3:0:0).
sr: [00:00.000000] backend: Libs: glib 2.44.1 (rt: 2.44.1/4401:1), libzip 0.11.2
, libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1), libusb-1.0 1.0.20.11003-rc3, libf
tdi 1.2.
sr: [00:00.000000] backend: Host: i686-w64-mingw32.static.posix, little-endian.
sr: [00:00.000000] backend: SCPI backends: TCP, serial, USBTMC.
sr: [00:00.000000] backend: Sanity-checking all drivers.
sr: [00:00.000000] backend: Sanity-checking all input modules.
sr: [00:00.000000] backend: Sanity-checking all output modules.
sr: [00:00.000000] backend: Sanity-checking all transform modules.
srd: libsigrokdecode loglevel set to 5.
sr: [00:00.000000] hwdriver: Initializing driver 'saleae-logic16'.
sr: [00:00.078000] ezusb: uploading firmware to device on 6.2
sr: [00:00.078000] ezusb: setting CPU reset mode on...
sr: [00:00.093000] resource: Attempt to open 'C:\Users\klaus\AppData\Local\sigrok-firmware\saleae-logic16-fx2.fw' failed: No such file or directory
sr: [00:00.093000] resource: Attempt to open 'C:\ProgramData\sigrok-firmware\saleae-logic16-fx2.fw' failed: No such file or directory
sr: [00:00.093000] resource: Attempt to open 'C:\Users\Public\Documents\sigrok-f
irmware\saleae-logic16-fx2.fw' failed: No such file or directory
sr: [00:00.093000] resource: Opened 'C:\Program Files (x86)\sigrok\sigrok-cli\sh
are\sigrok-firmware\saleae-logic16-fx2.fw'.
sr: [00:00.093000] ezusb: Uploading firmware 'saleae-logic16-fx2.fw'.
sr: [00:00.093000] ezusb: Uploaded 4096 bytes.
sr: [00:00.093000] ezusb: Uploaded 1121 bytes.
sr: [00:00.093000] ezusb: Firmware upload done.
sr: [00:00.109000] ezusb: setting CPU reset mode off...
sr: [00:00.109000] hwdriver: Scan of 'saleae-logic16' found 1 devices.
sr: [00:00.109000] saleae-logic16: Waiting for device to reset.
sr: [00:00.576000] saleae-logic16: Waited 467ms.
sr: [00:00.736000] saleae-logic16: Waited 627ms.
sr: [00:00.895000] saleae-logic16: Waited 786ms.
sr: [00:01.051000] saleae-logic16: Waited 942ms.
sr: [00:01.222000] saleae-logic16: Waited 1113ms.
sr: [00:01.378000] saleae-logic16: Waited 1269ms.
sr: [00:01.534000] saleae-logic16: Waited 1425ms.
sr: [00:01.690000] saleae-logic16: Waited 1581ms.
sr: [00:01.862000] saleae-logic16: Waited 1753ms.
sr: [00:02.034000] saleae-logic16: Waited 1925ms.
sr: [00:02.205000] saleae-logic16: Waited 2096ms.
sr: [00:02.274000] saleae-logic16: Failed to receive reply to EP1 command 0x7d:
LIBUSB_ERROR_IO.
sr: [00:02.274000] saleae-logic16: Failed to init device.
sr: [00:02.374000] saleae-logic16: Waited 2265ms.
sr: [00:02.434000] saleae-logic16: Failed to receive reply to EP1 command 0x7d:
LIBUSB_ERROR_IO.
sr: [00:02.434000] saleae-logic16: Failed to init device.
sr: [00:02.534000] saleae-logic16: Waited 2425ms.
sr: [00:02.594000] saleae-logic16: Failed to receive reply to EP1 command 0x7d:
LIBUSB_ERROR_IO.
sr: [00:02.594000] saleae-logic16: Failed to init device.
sr: [00:02.694000] saleae-logic16: Waited 2585ms.
sr: [00:02.754000] saleae-logic16: Failed to receive reply to EP1 command 0x7d:
LIBUSB_ERROR_IO.
sr: [00:02.754000] saleae-logic16: Failed to init device.
sr: [00:02.860000] saleae-logic16: Waited 2751ms.
sr: [00:02.922000] saleae-logic16: Failed to receive reply to EP1 command 0x7d:
LIBUSB_ERROR_IO.
sr: [00:02.922000] saleae-logic16: Failed to init device.
sr: [00:03.031000] saleae-logic16: Waited 2922ms.
sr: [00:03.094000] saleae-logic16: Failed to receive reply to EP1 command 0x7d:
LIBUSB_ERROR_IO.
sr: [00:03.094000] saleae-logic16: Failed to init device.
sr: [00:03.203000] saleae-logic16: Waited 3094ms.
sr: [00:03.203000] saleae-logic16: Device failed to renumerate.
Comment 10 Rudolf 2016-09-13 10:55:56 CEST
Hello,

In my desperation I have installed sigrok in Ubuntu 16.04 LTS xenial via synaptic.

When I tested with:
$ sigrok-cli -d saleae-logic16 --samples 100 -l 5

I got the error message:
sr: saleae-logic16: Invalid FPGA bitstream version: 0x40 != 0x10

I found File: libsigrok-03.0/hardware/saleae-logic16/protocol.c
In line 295 you could see:
	if (version != 0x10) {
		sr_err("Invalid FPGA bitstream version: 0x%02x != 0x10.", version);
		return SR_ERR;
	}

In a newer version of protocol.c I found:
         if (version != 0x10 && version != 0x13 && version != 0x40 && version != 0x41) {

Then I tried to compile myself a new libsigrok, with one changed line.
It does not made me happy:
1. pathes have been changed - solvable
   new path:
   /usr/local/share/sigrok-firmware/saleae-logic16-fpga-18.bitstream.
   old path:
   /usr/share/sigrok-firmware/saleae-logic16-fpga-18.bitstream

2. not solvable:
$ sigrok-cli -d saleae-logic16 --samples 100 -l 5
sr: libsigrok loglevel set to 5.
sr: backend: Sanity-checking all drivers.
sr: backend: Sanity-checking all input modules.
sr: backend: Sanity-checking all output modules.
srd: libsigrokdecode loglevel set to 5.
sr: hwdriver: Initializing driver 'saleae-logic16'.
sr: saleae-logic16: Found a Logic16 device.
sr: hwdriver: Scan of 'saleae-logic16' found 1 devices.
sr: saleae-logic16: Firmware upload was not needed.
sr: saleae-logic16: Uploading FPGA bitstream at /usr/local/share/sigrok-firmware/saleae-logic16-fpga-18.bitstream.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 15872 bytes.
sr: saleae-logic16: Uploaded 6668 bytes.
sr: saleae-logic16: FPGA bitstream upload done.
sr: saleae-logic16: Opened device 0 on 1.4, interface 0.
sr: session: Starting.
sr: saleae-logic16: Invalid state at acquisition setup: 0x15 != 0x08.
sr: session: sr_session_start: could not start an acquisition (generic/unspecified error)
Failed to start session.

That is above my knowledge.
I would very much appreciate, if a maintainer could solve that problem.

Regards, Rudolf

p.s.
In web page http://sigrok.org/wiki/Linux
it would be nice to mention, that "./autogen.sh" is no longer needed.
After a long pause of Linux compilation it was just confusing for me.
Comment 11 Uwe Hermann 2016-09-13 11:50:29 CEST
Hi, thanks for looking into this!

The "./autogen.sh" step is required, the wiki docs explain the build steps when building from git ("./autogen.sh" is not required for tarball builds).

Which Logic16 device *exactly* do you have? There are many clones of the Saleae Logic16, and some of them have different hardware and FPGAs and bitstreams etc.

We have info about these so far. Do you own one of those? Or another model? If yes, which?

http://sigrok.org/wiki/Saleae_Logic16
http://sigrok.org/wiki/KingST_KQS3506-LA16100
http://sigrok.org/wiki/Mcupro_Logic16_clone
http://sigrok.org/wiki/WayEngineer_Saleae16
http://sigrok.org/wiki/Mcupro_Logic16_clone
http://sigrok.org/wiki/Noname_XL-LOGIC16-100M
etc.

It would be nice if you could try your device with a fresh build of everything from git. You can use our tool "sigrok-cross-linux" from the sigrok-util repository, which will build everything into $HOME/sr (but you have to install all build requirements first):

  http://sigrok.org/gitweb/?p=sigrok-util.git;a=tree;f=cross-compile/linux
  http://sigrok.org/wiki/Building#Build_requirements

You can then run:

  LD_LIBRARY_PATH=$HOME/sr/lib $HOME/sr/bin/pulseview -l 5

More info here:

  http://sigrok.org/wiki/Building#Installing_to_a_non-standard_directory_using_LD_LIBRARY_PATH

Which firmware and bitstream files do you use and where did you get them from? From saleae.com or from a CD-ROM that came with your device? The latter could have a modified software and/or modified firmware + bitstreams on it.

You can extract the files with this script:

  http://sigrok.org/gitweb/?p=sigrok-util.git;a=tree;f=firmware/saleae-logic16

The latest ones that can be extracted from the official Saleae software from saleae.com should work for most devices, and have these MD5 sums:

96df76444afc5c28748f03d7e4280c2d  saleae-logic16-fpga-18.bitstream
c97db523c2d54fe07fc6d8588fd9d77b  saleae-logic16-fpga-33.bitstream
80af10cd7c0d0cd8ba69d3bc60baa9f8  saleae-logic16-fx2.fw
Comment 12 Rudolf 2016-09-13 15:40:17 CEST
Hello Uwe,

Thank you very much for taking care about my subject.
In am not so fluent in programming, sorry for leaving out important details.

> Which Logic16 device *exactly* do you have?
It looks like http://sigrok.org/wiki/Noname_XL-LOGIC16-100M

> The latest ones that can be extracted from the official Saleae software from saleae.com should work for most devices, and have these MD5 sums:
> 96df76444afc5c28748f03d7e4280c2d  saleae-logic16-fpga-18.bitstream
> c97db523c2d54fe07fc6d8588fd9d77b  saleae-logic16-fpga-33.bitstream
> 80af10cd7c0d0cd8ba69d3bc60baa9f8  saleae-logic16-fx2.fw

My download was from: 
https://www.saleae.com/downloads - Logic Linux 32 Bit, version 1.2.10
MD5 (saleae-logic16-fpga-18.bitstream) = 96df76444afc5c28748f03d7e4280c2d
MD5 (saleae-logic16-fpga-33.bitstream) = c97db523c2d54fe07fc6d8588fd9d77b
MD5 (saleae-logic16-fx2.fw) = 80af10cd7c0d0cd8ba69d3bc60baa9f8

I have already 3 working "sigrok" installations on different platforms.
1st working  sigrok installation on Ubuntu 14.04-32 LTS, with PPA
2nd working  sigrok installation on Mac OSX 10.11.6 El Capitan. 
3rd working  sigrok installation on Windows 7-64 -> !VirtualBox 5.1.4 -> Ubuntu 14.04-32 LTS with PPA.
Please see for more details http://www.rudiswiki.de/wiki9/SigrokDecoder

But when it comes to long term use, it would be useful to have it 
also working von Windows7 nativly, and the actual Ubuntu 16.04 LTS. 
There I am still struggeling, and hope on the help of you.

> It would be nice if you could try your device with a fresh build of everything from git. You can use our tool "sigrok-cross-linux" from the sigrok-util repository, which will build everything into $HOME/sr (but you have to install all build requirements first):

I will do so, and give you feed back.

Regards, Rudolf
Comment 13 Rudolf 2016-09-13 17:08:54 CEST
Hello Uwe,

I made the compile Test for sigrok under Ubuntu 16.04-32:
$ ./cross-compile_linux_sigrok-cross-linux.sh 

The log is in my wiki, please see:
http://www.rudiswiki.de/wiki9/SigrokDecoder#Links #13
    sigrok_Ubuntu1604-32_git-test.txt
If you click on the link, you can read the text, or can download it.

Unfortunately no binaries are build.
The folder home/rudi/sr exists with some contents.
I can not find, what was the error.

Are you please so kind and route me to a possible fix?

Regards, Rudolf
Comment 14 Soeren Apel 2016-09-13 17:16:39 CEST
Hi Rudolf,

libsigrok didn't complete because the test suite didn't succeed. Can you please also upload test-suite.log?

Not sure why the unit tests are required for building but that's why the process stops. If it didn't, the script would continue building the rest of the sigrok suite.
Comment 15 Rudolf 2016-09-13 20:17:39 CEST
(In reply to comment #14)
> Hi Rudolf,
> 
> libsigrok didn't complete because the test suite didn't succeed. Can you
> please also upload test-suite.log?
> 
> Not sure why the unit tests are required for building but that's why the
> process stops. If it didn't, the script would continue building the rest of
> the sigrok suite.

Hello Soeren,

Thank you for your help.
In the text file
http://www.rudiswiki.de/wiki9/SigrokDecoder#Links #13
    sigrok_Ubuntu1604-32_git-test.txt
short before the end it tells:

Makefile:3174: die Regel für Ziel "test-suite.log" scheiterte
               the rule for target "test-suite.log" failed

So, no file "test-suite.log" was generated.
I searched for it also:
$ sudo updatedb
$ locate test-suite.log
- no result

searching for the rule, I found:

Path: build/libsigrok/build/Makefile

$(TEST_SUITE_LOG): $(TEST_LOGS)
3174	@$(am__set_TESTS_bases); \
	am__f_ok () { test -f "$$1" && test -r "$$1"; }; \
	redo_bases=`for i in $$bases; do \
	              am__f_ok $$i.trs && am__f_ok $$i.log || echo $$i; \
	            done`; \
	if test -n "$$redo_bases"; then \
	  redo_logs=`for i in $$redo_bases; do echo $$i.log; done`; \
	  redo_results=`for i in $$redo_bases; do echo $$i.trs; done`; \
	  if $(am__make_dryrun); then :; else \
	    rm -f $$redo_logs && rm -f $$redo_results || exit 1; \
	  fi; \
	fi; \
	if test -n "$$am__remaking_logs"; then \
	  echo "fatal: making $(TEST_SUITE_LOG): possible infinite" \
	       "recursion detected" >&2; \
	elif test -n "$$redo_logs"; then \
	  am__remaking_logs=yes $(MAKE) $(AM_MAKEFLAGS) $$redo_logs; \
	fi; \
	if $(am__make_dryrun); then :; else \
	  st=0;  \
	  errmsg="fatal: making $(TEST_SUITE_LOG): failed to create"; \
	  for i in $$redo_bases; do \
	    test -f $$i.trs && test -r $$i.trs \
	      || { echo "$$errmsg $$i.trs" >&2; st=1; }; \
	    test -f $$i.log && test -r $$i.log \
	      || { echo "$$errmsg $$i.log" >&2; st=1; }; \
	  done; \
	  test $$st -eq 0 || exit 1; \
	fi
/* is that REALLY one statement? */

For me, this is not understandable why it fails.

Regards, Rudolf
Comment 16 Uwe Hermann 2016-09-13 20:53:18 CEST
The logfile for the failed checks should be here:

  sigrok-util/cross-compile/linux/build/libsigrok/build/test-suite.log

Anyway, this is an unrelated issue, you can just comment out the "make check" in the script (for libsigrok) to get the build to continue for now.


As for the Logic16 issue, I could indeed reproduce it today on two different Win 10 64bit boxes, I'm getting the

  saleae-logic16: Failed to receive reply to EP1 command 0x7d: LIBUSB_ERROR_IO.

error as well (tested all Logic16 clones I own as well, happens on all of them)

The errors happen during firmware upload, i.e. the device never renumerates.

I'll investigate this further.


Seems to be Windows-specific indeed btw, this does not happen on Linux with the same device, USB cable, and firmware/bitstream combinations.
Comment 17 Rudolf 2016-09-13 21:51:09 CEST
Hello Uwe,

Thank you very much taking care about the Logic16 topic.
This is a Logic Analyzer frontend with a very good 
price/performance ratio.

Regarding Ubuntu 16.04 LTS Xenial it would be really nice to
bring the updated saleae-logic16 driver into 
the Ubuntu 16.06 repository. This is the easiest
for the not so programming familiar user, like me ;-)

Second option would be the PPA from David Elstner:
https://launchpad.net/~daniel-elstner/+archive/ubuntu/sigrok
which does not have a 16.04 Xenial binary version of sigrok.

In the meanwhile I am struggeling at a GPIB decoder, with
the use of the Logic16. In pulseview it shows alread good results:
http://www.rudiswiki.de/wiki9/SigrokDecoderGPIB
The problem with the "last byte not showing" is alread solved,
but not yet documented.

Regards, Rudolf
Comment 18 Uwe Hermann 2016-09-15 16:28:29 CEST
Alright, I was able to bisect this, the change that "broke" the previously working version was this:

http://sigrok.org/gitweb/?p=libsigrok.git;a=commitdiff;h=1f61c22ff5e0d1d169894ad606831b44fde19468

Alas, there are no saleae-logic16 specific changes in there, and I also checked that none of the compiler or linker flags changed. The *order* of some entries changed though, and I think that leads to the change in behaviour.

In the working version the libsigrok "-l 5" output says that it's using libusb 1.0.19 (as built by MXE), in the non-working one it seems to be 1.0.20-rc3 (which is the custom libusb branch we're currently using until those changes are merged upstream).

I.e. there seem to be some weird libusb-version mixups, I'll see if I can find out some more details.

I might have a temporary workaround soonish, but this will need some proper analyzing to find out what *exactly* is happening and why.
Comment 19 Rudolf 2016-09-15 16:59:07 CEST
Hello Uwe,

Thank you for taking care about the topic.
That is far above my knowledge level.

In the meanwhile I got my GPIB decoder for saleae-logic16 ready, 
that way, that I like it.

Do you want to have a look at it at:
    http://www.rudiswiki.de/wiki9/SigrokDecoderGPIB
if it ready for publishing, or may I send it to the maillist?

Regards, Rudolf
Comment 20 Andy Moyo 2017-03-16 22:37:09 CET
Uwe Hermann,

Any info about the workaround to get http://sigrok.org/wiki/Noname_XL-LOGIC16-100M work on native Windows?

I have follows info from Rudolf, http://www.rudiswiki.de/wiki9/sigrokLogic16, it seem to work on Ubuntu 14 inside VMWARE.
Comment 21 Christopher Masto 2017-08-08 05:41:36 CEST
I have this same "Failed to receive reply to EP1 command 0x7d: LIBUSB_ERROR_IO" error trying to use my (Saleae brand) Logic16 on Windows. I'm not sure I follow all the details in this bug report, but as far as I can tell this has been broken since 2015? Perhaps it would make sense to remove logic16 from the list of supported devices so people will not go down the same dead end I did and spend several hours installing and reinstalling and extracting firmware and switching USB drivers etc.
Comment 22 Rudolf 2017-08-08 11:57:34 CEST
It works also on the actual Mac OS version 10.12.6 (Sierra), see:
http://www.rudiswiki.de/wiki9/sigrokLogic16#Logic16_in_Mac_OS_X

$ pulseview -V
PulseView 0.4.0-git-fe934a9

$ pulseview -l 3
sr: saleae-logic16: Firmware upload was not needed.
sr: saleae-logic16: mcupro Saleae16 detected.
sr: saleae-logic16: Opened device on 20.11 (logical) / usb/20-2 (physical), interface 0

Regards, Rudolf
Comment 23 Christopher Masto 2017-08-08 15:21:58 CEST
Good point. This was specifically about the Windows version. I only have the one device to test with, so I don't know if the problem is:

* Windows version doesn't work with Logic16
or
* Windows version doesn't work at all

Either way, it doesn't look like it's getting fixed. The documentation is a Wiki, so I will see if I can annotate the page to explain that this is not a supported configuration.
Comment 24 davor 2017-10-10 17:42:01 CEST
Hi,

i had exactly the same Problem with my Logic16 Clone, but somehow i got it working on one, out of 3, Windows10 x64 PC´s with Pulseview and sigrok-cli.
The firmware directory in my case was "C:\Users\xxx\AppData\Local\sigrok-firmware\"
The driver i used is libusb0(v1.2.6.0)

https://ibb.co/cDVEwG
Comment 25 davor 2017-10-10 18:23:59 CEST
(In reply to davor from comment #24)
> Hi,
> 
> i had exactly the same Problem with my Logic16 Clone, but somehow i got it
> working on one, out of 3, Windows10 x64 PC´s with Pulseview and sigrok-cli.
> The firmware directory in my case was
> "C:\Users\xxx\AppData\Local\sigrok-firmware\"
> The driver i used is libusb0(v1.2.6.0)
> 
> https://ibb.co/cDVEwG

Finally got it working on all my Windows 7/10 Systems.
This is what i did, with Zadiag :
Install libusb-Driver, re-connect Device, install winUSB-Driver, re-connect Device, install libusbK, re-connect Device, then again installed libusb. 
And voila, started Pulsview and all OK.
Comment 26 jasonsmr 2019-08-10 10:14:03 CEST
Above solution by davor ; Comment 25 Works for me Date 08-10-2019.

Thanks