First time install today of latest Pulseview nightly and out-the-box VKTech Saleae clone hardware on Win7 and Win10 machines. The LA is supported (https://sigrok.org/wiki/VKTECH_saleae_clone) and the hardware is virgin - I have not fiddled with it yet but have inspected the solder quality for loose balls. I cant get PV to recognise it no matter what options I try under device selection dropdown. I also tried all driver options under Zadiq. I would expect to see Saleae 8 appear in the selection box in PV when I select fx2lafw device option, but nothing appears, the box is blank. Same result on 3 machines Win10 (x1) and Win7 (x2). Common denominators are Pulseview and the LA hardware (I changed the USB cable) - unfortunately I only have 1x LA so it may be hardware as rootcause, but this report just in case its firmware or app related or you are picking up other chatter around this topic, altho I have not seen any recent similar reports on Bugzilla.
Do you know how to use the Windows command line? If so, please download the debug build of PulseView (it's on the same download page) and execute "pulseview -l 5" to show the debug messages. Then, please copy the output to a pastebin and put the URL here do so we can have a look. Maybe the debug output gives you an idea already, too.
Update: I ran Cypress EZ-USB Interface and that downloads successfully to the LA onboard MCU, and I can read and write to the EPROM eg, change VID:PID so that rules out hardware, no?
Thanks Soeren, I didnt see yr comment before posting mine, I will run the debug and report back.
Created attachment 400 [details] Pulseview debug traces - success and fail cases
Created attachment 401 [details] Pulseview debug traces - success and fail cases
Ok - some success and failure. Many trials and different combinations of events - see the two attached .txt files for debug output from PV. One case is PASS and the other case is FAIL. Summary: Running the debug version of PV I get success. going back to the release version I get failure as described in this original report. Observations: I noticed that in debug version, when selecting fx2lafw device in menu, a 2nd USB instance is created with a serial number = Saleae (text). From thereon the process works and I am able to capture trace data. In release version no such 2nd USB is created and no device listed when clicking on fx2lafw. In Win7 you get the system sounds when a USB device is plugged/unplugged if it was enumerated successfully - with debug version you get a device unplugged followed immediately by device plugged sound. Also, I use the excellent Nirsoft USBDeview and in there you can see the 2nd device created, actually seems to be a new instance of the same device but with "Saleae" in the serial number field. It has the same .inf file as 1st device. The 1st device is created when using Zadiq to add the WinUSB driver. When switching between versions of PV, I do a complete uninstall of PV, removal of USB driver in device manager including delete .inf file in windows/inf folder, then reboot before installing other version of PV.
Hm, "resource: Attempt to open 'C:\Program Files (x86)\sigrok\PulseView\share\sigrok-firmware' failed: Permission denied" and "Failed to locate 'fx2lafw-saleae-logic.fw'." sounds like #1140 which was fixed recently. Please retry everything with a fresh installer of PulseView, if possible. Also, please try different USB cables, just to be sure. Many of the cables that come with FX2 devices are utterly shitty and can cause all kinds of issues.
Fixed, well done.