diff options
| author | Ryan <fauxpark@gmail.com> | 2020-07-17 03:01:34 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-16 18:01:34 +0100 |
| commit | 19b70b2737517b08beebe28ad5b2d084c9f59bf3 (patch) | |
| tree | 43aaf61f0b6de6a1c4b23a6297ae4d7c94726628 /docs | |
| parent | 61b64bb82a93c6d1441f07655a5e20b59a15fd29 (diff) | |
MSYS2: Switch to bootloadHID package and bring back avrdude package (#9736)
* MSYS2: Switch to bootloadHID package and bring back avrdude package
* Update Zadig docs as well
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/driver_installation_zadig.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/driver_installation_zadig.md b/docs/driver_installation_zadig.md index b04a6fbef1..403b78da0c 100644 --- a/docs/driver_installation_zadig.md +++ b/docs/driver_installation_zadig.md @@ -23,7 +23,7 @@ Zadig will automatically detect the bootloader device. You may sometimes need to !> If Zadig lists one or more devices with the `HidUsb` driver, your keyboard is probably not in bootloader mode. The arrow will be colored orange and you will be asked to confirm modifying a system driver. **Do not** proceed if this is the case! -If the arrow appears green, select the driver, and click **Install Driver**. The `libusb-win32` driver will usually work for AVR, and `WinUSB` for ARM, but if you still cannot flash the board, try installing a different driver from the list. For flashing a USBaspLoader device via command line with msys2, the `libusbk` driver is recommended, otherwise `libusb-win32` will work fine if you are using QMK Toolbox for flashing. +If the arrow appears green, select the driver, and click **Install Driver**. The `libusb-win32` driver will usually work for AVR, and `WinUSB` for ARM, but if you still cannot flash the board, try installing a different driver from the list. USBAspLoader devices must use the `libusbK` driver.  |