One example for that is the 'ftdi-la' libsigrok driver. If you are unsure, you can check if your device appears at the 'Ports (COM&LPT)' section of the Windows Device Manager.Įxception: If the libsigrok driver uses the chip, for example an FTDI chip, in a special mode (i.e., not as a plain COM port), the Zadig steps outlined below will be required. Please install the driver as provided by the manufacturer. If your device is connected through a (virtual) COM port, libsigrok generally doesn't need a special driver. In order to use libsigrok (via a sigrok frontend) on Windows, you need to install the proper driver for the respective device. sigrok-cli-NIGHTLY-32bit-static-release-installer.exe ( debug build).pulseview-NIGHTLY-64bit-static-release-installer.exe ( debug build).pulseview-NIGHTLY-32bit-static-release-installer.exe ( debug build).

Please test and report any issues you encounter. We provide nightly Windows installers for sigrok-cli and PulseView (require Windows XP or higher). 7.6 Native build using Microsoft Visual Studio.7.5 Native build using Borland/Embarcadero C++ Builder.7.3 Native build using the old MinGW+MSYS.6.4 How do I see debug output from PulseView on Windows?.6.3 (FX2 based) logic analyzer terminates acquisition before the specified limit.6.2 My device is not found or usable (USB/driver/firmware/hardware issues).6.1 I cannot start sigrok-cli or PulseView: error Oxc0150002.

Zadig drivers for windows 10