Bug 1332 - windows driver of DSLogic Plus hangs up
Summary: windows driver of DSLogic Plus hangs up
Alias: None
Product: PulseView
Classification: Unclassified
Component: Other (show other bugs)
Version: 0.4.1
Hardware: x86 Windows
: Normal normal
Target Milestone: ---
Assignee: Nobody
Depends on:
Reported: 2018-11-20 14:19 CET by Jochen Berg
Modified: 2019-11-16 14:53 CET (History)
3 users (show)

DSLogic Basic Plus Pro Firmwarefiles .FW (deleted)
2018-11-21 00:39 CET, Jochen Berg

Note You need to log in before you can comment on or make changes to this bug.
Description Jochen Berg 2018-11-20 14:19:16 CET

OS: Windows 7 64
Device: DreamSourceLab DSLogic Plus
Pulseview 0.4.1 and nighlybuilds 

when I device "Connect to Device" in pulseview than dslogic plus is found.
I see in Step 4: Select Device
"DreamSourceLab DSLogic Plus with 16 channels"

Im click "OK" then view a Message:
"Failed to open device"
"generic/unspecified error"

Than hangs up the device(driver). To scan again must i disconnect and reconnect the device.

I tested it in Win7 64 and 32 and WinXP. It is the same self problem.

Sigrok-cli --scan is the same problem, first the device is found, then only after a reconnect.

sr: dreamsourcelab-device: Failed to open potential device with VID:PID 2a0e:0020: LIBUSB_ERROR_ACCESS.

Best regards,
Jochen Berg
Comment 1 Uwe Hermann 2018-11-20 23:00:27 CET
Hi, did you assign the WinUSB driver to this device via Zadig and did you extract the correct version of the firmware files for this device from the vendor software?

Comment 2 Jochen Berg 2018-11-21 00:39:21 CET
Created attachment 491 [details]
DSLogic Basic Plus Pro Firmwarefiles  .FW
Comment 3 Jochen Berg 2018-11-21 00:56:48 CET

thank you. 

zadig was my first idea. that was not it.

I solved the problem!

in the windows registry string:

HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet000 \ Control \ usbflags \ 2A0E00200001

was the set osvc 01 88

i have changed to osvc 01 20

then I compiled the firmware under linux and copied on

->  C:\Program Files (x86)\sigrok\pulseview\share\sigrok-firmware


-> C:\Program Files (x86)\sigrok\sigrok-cli\share\sigrok-firmware

I have packed the *.fw firmware files with 7zip for other users with the same problem. see in previous message my attachment.

can you install the * .fw in the Sigrok installation package for Windows?
these files for DSLogic are missing in the installation package of pulseview and sigrok-cli. other users may have the same problem with the DSLogic analyzer. 

best regards,
jochen berg
Comment 4 bobdabiulder 2019-02-23 17:51:59 CET
Thank you Jochen!  I've been struggling with this one for a long time, you figured it out for me :)

FYI for other people from Google: I used Zadig, and made sure that it would REPLACE the driver with WinUSB.  Then, I made the registry edit, and put all of the .fw files into C:\Programs Files (x86)\PulseView\share\sigrok-firmware.  This really should be included in the next stable release of PulseView, which is what I am using.
Comment 5 Soeren Apel 2019-11-16 10:09:21 CET
Hello, which actions do you want us to perform exactly?
Comment 6 Uwe Hermann 2019-11-16 14:44:34 CET
The content of attachment 491 [details] has been deleted for the following reason:

Removing the attached firmware files, we have no permission to distribute them.
Comment 7 Uwe Hermann 2019-11-16 14:53:42 CET
Unfortunately we don't own the copyright on the firmware and FPGA files and we don't have permission to distribute them, so we can't make them available for download and we can't ship them directly with sigrok-cli or PulseView.

(for the same reason I've deleted the attached files from this bug report, sorry)

I've expanded the wiki description a bit to make it more convenient to get the files if you can't or don't want to use the bash script we provide:


(that page is also linked from all other DreamSourceLab pages in the wiki)

I've (re-)tested this on a Windows 10 box with PulseView 0.4.1 and the nightly build. After manual download, renaming and placing the files in the correct directory, the DSLogic devices work fine for me here.

I'm boldly closing the bug for now. I'm not entirely sure what exactly the registry changes in comment 3 are supposed to do and why, I personally never needed to do that on any of the various Windows boxes where I've used DSLogic devices on. If that's still an issue if the correct firmware files are placed in the correct directory, and something that might affect other users (i.e. not a local issue), please open another bug for that with more info and/or patches ideally (if we can do something about it in code at all). Thanks!