summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Fertser <fercerpav@gmail.com>2015-01-27 13:37:51 +0300
committerPaul Fertser <fercerpav@gmail.com>2015-05-17 21:15:13 +0100
commit1583379fb91e0040b08e7ac365fa0919ace4e391 (patch)
tree2a2465e3d6a497005144d2b6542036a1da855200
parent805604058be368c1b44defb03ecc5e3e1b616fb9 (diff)
downloadopenocd-1583379fb91e0040b08e7ac365fa0919ace4e391.tar.gz
openocd-1583379fb91e0040b08e7ac365fa0919ace4e391.tar.xz
README.Windows: clarify the kernel drivers installation
HID and composite devices need to be mentioned explicitly due to windows oddities. Change-Id: I7cdbaa50c60ceb1950c934e0249986d46c875cff Signed-off-by: Paul Fertser <fercerpav@gmail.com> Reviewed-on: http://openocd.zylin.com/2506 Tested-by: jenkins Reviewed-by: Xiaofan <xiaofanc@gmail.com> Reviewed-by: Andreas Fritiofson <andreas.fritiofson@gmail.com>
-rw-r--r--README.Windows19
1 files changed, 15 insertions, 4 deletions
diff --git a/README.Windows b/README.Windows
index 9cdd55c5..6c616f38 100644
--- a/README.Windows
+++ b/README.Windows
@@ -7,6 +7,9 @@ recommended as it doesn't provide enough C99 compatibility).
Alternatively, one can cross-compile it using MinGW-w64 on a *nix
host. See README for the generic instructions.
+Also, the MSYS2 project provides both ready-made binaries and an easy
+way to self-compile from their software repository out of the box.
+
Native MinGW-w64/MSYS compilation
-----------------------------
@@ -22,13 +25,21 @@ installation.
USB adapters
------------
-You usually need to have WinUSB.sys (or libusbK.sys) driver installed
-for a USB-based adapter. Some vendor software (e.g. for ST-LINKv2)
-does it on its own. For the other cases the easiest way to assign
-WinUSB to a device is to use the latest Zadig installer:
+For the adapters that use a HID-based protocol, e.g. CMSIS-DAP, you do
+not need to perform any additional configuration.
+
+For all the others you usually need to have WinUSB.sys (or
+libusbK.sys) driver installed. Some vendor software (e.g. for
+ST-LINKv2) does it on its own. For the other cases the easiest way to
+assign WinUSB to a device is to use the latest Zadig installer:
http://zadig.akeo.ie
+When using a composite USB device, it's often necessary to assign
+WinUSB.sys to the composite parent instead of the specific
+interface. To do that one needs to activate an advanced option in the
+Zadig installer.
+
For the old drivers that use libusb-0.1 API you might need to link
against libusb-win32 headers and install the corresponding driver with
Zadig.