Windows
Windows installers
We provide nightly Windows installers for sigrok-cli and PulseView. Please test and report any issues you encounter.
Downloads:
Drivers
In order to use libsigrok (via a sigrok frontend) on Windows, you need to install the proper driver for the respective device.
COM/serial/RS232 driver
If your device is connected through a (virtual) COM port, libsigrok doesn't need a special driver. Please install the driver as provided by the manufacturer. If you are unsure, you can check if your device appears at the "Ports (COM&LPT)" section of the Windows Device Manager.
Device specific USB driver
The device specific USB driver shipped with the vendor software is not going to work in almost all cases. You will need to install the WinUSB driver.
For installing the WinUSB driver you can use the zadig executable from the libwdi project. There are two versions, one for Windows XP (zadig_xp.exe), and another one for all other (Vista or higher) supported Windows versions (zadig.exe). Both 32 and 64 bit Windows versions are supported. The sigrok-cli and PulseView installers ship with both zadig executable files for convenience (they're located in the installation directory of the respective application).
If you already installed the vendor driver previously, you need to run Zadig and switch to the WinUSB driver (see above). There's no need to uninstall or deactivate the vendor driver manually, Zadig will handle all of this.
See also the Zadig wiki page for more information.
Firmware
The Windows installers ship with all firmware files that are either open-source or where we have permission from the vendor to distribute them. Some devices will need other firmware which we cannot redistribute though. See the wiki page for the respective device on how you can extract those firmware files from the vendor's software.
You'll need to copy the extracted files into the firmware subfolder of the respective installation directory of sigrok-cli or Pulseview, e.g. C:\Program Files\sigrok\sigrok-cli\firmware or C:\Program Files\sigrok\PulseView\firmware.
Example files
The Windows installers ship with example dump files (from our sigrok-dumps repository), which are located in the examples subdirectory of the install directory of sigrok-cli and PulseView.
These files can be used to conveniently test various frontend features and protocol decoders, and so on.
Limitations and TODOs
The table below lists some of the known remaining issues.
| Driver/component | Windows status |
|---|---|
| fx2lafw | There seems to be some issue causing frontend hangs (bug #343). Needs to be investigated (could be a libsigrok driver issue, or libusb issue, or USB/thread code issue, or something entirely different). |
| openbench-logic-sniffer | The OLS (and other compatible devices such as Buspirate) are not detected. |
| serial port code | There may be an issue still in the serial port handling on Windows (bug #341). Needs to be investigated. |
| sysclk-lwla | Acquisition "hangs" on Windows (bug #328). May or may not be related to (or have the same cause as) bug #343. |
FAQ
I cannot start sigrok-cli or PulseView: error Oxc0150002
This happens if you don't have the Microsoft Visual C++ 2008 Redistributable Package installed. Usually this is already installed on most machines since various other software packages also need this. If you didn't yet install it (or no other software package automatically installed it for you) you will see the Oxc0150002 error and sigrok-cli and/or PulseView will not start.
The root cause for this is that the above download will install the otherwise missing file msvcr90.dll (and possibly others) which is required for running sigrok frontends. The requirement is imposed by python32.dll to be more specific, which we use/need for running protocol decoders.
Please download the Microsoft Visual C++ 2008 Redistributable Package and install it, that should fix the issue and allow you to start sigrok-cli and/or PulseView.
Building from source
Note: This should generally not be necessary for users, please just use the provided nightly installers (see above).
Cross-compile using MXE
If you really want to build from source, we recommend you use the sigrok-cross-mingw script from the sigrok-util repository (that uses MXE) to cross-compile the Windows binaries on a Linux system.
Native builds are generally not supported by us! Yes, they can work in theory (see below), but it means a lot of hassle compared to a cross-compile using the above script, and native builds are not really well-tested by us.
Native build using MSYS2
If you do want to build the sigrok subprojects natively on a Windows system (instead of using the cross-compile method, see above) we recommend you use MSYS2.
After you've run the MSYS2 installer (use msys2-x86_64-*.exe. i.e. the 64bit MSYS2) you can install the sigrok requirements like this:
$ pacman -Sy $ pacman -S git autoconf automake libtool make pkg-config wget patch mingw-w64-i686-toolchain \ mingw-w64-i686-glib2 mingw-w64-i686-glibmm mingw-w64-i686-libusb mingw-w64-i686-check mingw-w64-i686-boost \ mingw-w64-i686-libzip mingw-w64-i686-doxygen mingw-w64-i686-python3 mingw-w64-i686-python3-numpy \ mingw-w64-i686-python3-gobject mingw-w64-i686-python3-setuptools mingw-w64-i686-swig mingw-w64-i686-qt4 mingw-w64-i686-cmake
Afterwards, you can open a new MSYS2 MinGW32 shell and build the sigrok subprojects pretty much like on any Linux system.
TODO:
- This is still work in progress, not all parts are fully working, tested, or supported yet!
- MSYS2 currently doesn't ship with all packages we want. E.g. the following are missing: autoconf-archive, libftdi1, librevisa.
- There may be a few bugs that need to be fixed in sigrok subprojects first. Examples: #533.