X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=README.Windows;h=9cdd55c5c2236b53de19bbc2384fd7fe3a893a9f;hp=011ba54223d720719ff4f41c6aa5ecd72c4d2185;hb=1a9cec020ee71b804db21ba85ccc7393336a88ce;hpb=06fb3bf8cd3e14d8e1f32f6b6b5f586ef5d1857d diff --git a/README.Windows b/README.Windows index 011ba54223..9cdd55c5c2 100644 --- a/README.Windows +++ b/README.Windows @@ -25,10 +25,25 @@ 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 Zadig installer: +WinUSB to a device is to use the latest Zadig installer: - http://sourceforge.net/projects/libwdi/files/zadig/ + http://zadig.akeo.ie 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. + +If you need to use the same adapter with other applications that may +require another driver, a solution for Windows Vista and above is to +activate the IgnoreHWSerNum registry setting for the USB device. + +That setting forces Windows to associate the driver per port instead of +per serial number, the same behaviour as when the device does not contain +a serial number. So different drivers can be installed for the adapter on +different ports and you just need to plug the adapter into the correct +port depending on which application to use. + +For more information, see: + + http://msdn.microsoft.com/en-us/library/windows/hardware/jj649944(v=vs.85).aspx + http://www.ftdichip.com/Support/Knowledgebase/index.html?ignorehardwareserialnumber.htm