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"
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.
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?
Created attachment 491 [details]
DSLogic Basic Plus Pro Firmwarefiles .FW
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.
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.