Difference between revisions of "Windows"

From sigrok
Jump to navigation Jump to search
Line 19: Line 19:
In order to use [[libsigrok]] (via a sigrok frontend) on Windows, you need to install the proper driver for the respective device.  
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 ===
=== COM/serial/RS232 driver ===


If your device is connected through a (virtual) COM port, libsigrok don'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.
If your device is connected through a (virtual) COM port, libsigrok don'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 ===
=== Device specific USB driver ===

Revision as of 18:03, 6 January 2014

PulseView on Windows

Windows installers

We provide experimental Windows installers for sigrok-cli and PulseView. Please test and report any issues you encounter.

Download: http://sigrok.org/download/binary/

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 don'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.

For installing the drivers 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).

Devices where libsigrok uses libftdi (asix-sigma, chronovu-la8, ikalogic-scanaplus) will need the libusb-win32 driver, devices where libsigrok uses libusb-1.0 will need the WinUSB driver (all other USB devices).

If you already installed the vendor driver previously, you need to run Zadig and switch to the libusb-win32 or WinUSB driver (see above). There's no need to uninstall or deactivate the vendor driver manually, Zadig will handle all of this.

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.

Limitations and TODOs

We intend to fully support all major operating systems in sigrok, including Windows. However, we're not quite there, yet. Various portability issues and TODOs need to be addressed still. The table below lists some of the known remaining issues.

Driver/device Windows status
ikalogic-scanalogic2 HID-based, we need to use HIDAPI.
openbench-logic-sniffer Serial port portability fixes required (partially implemented, but unfinished).
link-mso19‎ Doesn't compile due to libudev dependency (Linux-only). TODO: Make libudev optional.
rigol-ds USB connection not supported yet (it's Linux-only), serial connection partially working.
uni-t-dmm HID-based, we need to use HIDAPI.
victor-dmm HID-based, we need to use HIDAPI.

Building from source

See Windows/Building.