Sigrok - I cannot get my installed PulseView to connect to my VKTech clone Cypress FX2 logic analyzer inspite of 3 days of continuous attempts carefully following instructions on Sigrok pages or procedures in BugZilla posts and equally careful running of Zadig. After selecting lx2lafw in "Choose the driver" window, followed by "Scan for devices using the driver above", PulseView appears to stop and never shows connection to anything; nothing ever appears in the "Select the device" window. I have been totally unable to affect this behavior. My system: ASUS Z96Jm notebook OS Windows 7 Pro SP1 x64 Memory 2 GB The LA shows up in Device Manager/Universal Serial Bus devices/fx2lafw as: General Tab Logic Analyzer (name edited by me) Device Type Universal Serial Bus Devices Manufacturer Lakeview Research [what Jan Axelson is doing here I have no idea) Location Port_#0001.Hub_#0005 "This device is working properly" Driver Tab Logic Analyzer Driver Provider libwdi Driver Date 2/10/2017 Driver Version 6.1.7600.16385 Driver Signer USB\VID_0925&PID_3881 (libwdi autogenerated) Driver Details Button Driver files window C:\Windows\system32\Drivers\WinUSB.sys C:\Windows\system32\WdfCoInstaller01011.dll C:\Windows\system32\WinUSBCoInstaller2.dll Provider Microsoft Corporation File version 6.1.7601.17514 (win7sp1rtm101119-1850) Copyright @Microsoft Corporation All rights reserved Digital Signer Microsoft Windows Details Tab Logic Analyzer Property Window "Device Description" Value Window "Logic Analyzer" Any help would be sincerely appreciated; as of now I am completely stalled and have no idea what to do next. Mick H. 25 May 1 2019 7:31 PM PDT USA mhholl<at>comcast.net
Hello, first off, Windows support is generally working but there are edge cases where users simply cannot get the USB drivers to work. We don't know why and no user ever dug into the issue and apparently simply moved on. We're all Linux devs, so Windows support is something where we rely on the community to contribute. That said, you can get an idea of what's happening by downloading the debug build at https://sigrok.org/wiki/Downloads#Windows and starting PV from the console using "pulseview -l 5" or setting the log level to 5 in the settings and restarting PV. Then, detailed internal information will be printed to the debug console window, letting you see what PV is doing. It's possible that PV doesn't even see that there's an FX2 device connected. It's worth trying using the other drivers available in Zadig aside from WinUSB.
(In reply to Soeren Apel from comment #1) > Hello, > > first off, Windows support is generally working but there are edge cases > where users simply cannot get the USB drivers to work. We don't know why and > no user ever dug into the issue and apparently simply moved on. We're all > Linux devs, so Windows support is something where we rely on the community > to contribute. > > That said, you can get an idea of what's happening by downloading the debug > build at https://sigrok.org/wiki/Downloads#Windows and starting PV from the > console using "pulseview -l 5" or setting the log level to 5 in the settings > and restarting PV. Then, detailed internal information will be printed to > the debug console window, letting you see what PV is doing. > > It's possible that PV doesn't even see that there's an FX2 device connected. > It's worth trying using the other drivers available in Zadig aside from > WinUSB. Herr Apel - thanks for the prompt reply and the insights; I had already come to understand clearly that the Sigrok team is primarily a group of Linux geeks while I started with Microsoft DOS 2 (yes, I'm that old) and have lived in the Microsoft world ever since. I'll try the above suggestions ASAP, probably Monday 27 May, and report back with anything possibly useful. Mick H. 26 May 2019 1:04 PM PDT USA
(In reply to MickH from comment #2) > (In reply to Soeren Apel from comment #1) > > Hello, > > > > first off, Windows support is generally working but there are edge cases > > where users simply cannot get the USB drivers to work. We don't know why and > > no user ever dug into the issue and apparently simply moved on. We're all > > Linux devs, so Windows support is something where we rely on the community > > to contribute. > > > > That said, you can get an idea of what's happening by downloading the debug > > build at https://sigrok.org/wiki/Downloads#Windows and starting PV from the > > console using "pulseview -l 5" or setting the log level to 5 in the settings > > and restarting PV. Then, detailed internal information will be printed to > > the debug console window, letting you see what PV is doing. > > > > It's possible that PV doesn't even see that there's an FX2 device connected. > > It's worth trying using the other drivers available in Zadig aside from > > WinUSB. > > Herr Apel - thanks for the prompt reply and the insights; I had already come > to understand clearly that the Sigrok team is primarily a group of Linux > geeks while I started with Microsoft DOS 2 (yes, I'm that old) and have > lived in the Microsoft world ever since. I'll try the above suggestions > ASAP, probably Monday 27 May, and report back with anything possibly useful. > > Mick H. > 26 May 2019 > 1:04 PM PDT USA Herr Apel - PulseView is now working with my VKTech clone logic analyzer. I tried all applicable drivers (3 of 4) using Zadig; only the WinUSB driver will work. Condensing a lot of investigation down to two scenarios: 1. The LA is plugged in and fully enumerated on the USB - in this case, when PulseView is launched it immediately finds the LA, connects automatically, and is ready to go listed as Saleae Logic. 2. PulseView is launched and running before the LA is plugged in - in this case PulseView never finds the LA. Clicking the device selection button to launch the search window, selecting lx2lafw as driver, and clicking the "Scan for devices......" button never brings anything into the device selection window to be offered as a selection. I can certainly use the system but I have to remember to plug the LA into the USB first. Thanks for your help and advice with this. Now that the system works, I'll see what I can do with it Mick H. 28 May 19 503 pm PDT USA
Sounds like everything is working now, closing the bug. The unrelated issue of "start PV first, then attach device, then manually scan" is reprodicuble indeed, it might be fixed (or at least we're investigating it) over at bug #1399.