Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add reset instructions for boards that use Command to the Zadig driver installation guide #6770

Merged
merged 3 commits into from
Sep 20, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
-> → →
  • Loading branch information
vomindoraan committed Sep 19, 2019
commit 4dd2958bef7cab2e77adc11d226b389d7a70f5f6
4 changes: 2 additions & 2 deletions docs/driver_installation_zadig.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ We recommend the use of the [Zadig](https://zadig.akeo.ie/) utility. If you have
Put your keyboard into bootloader mode, either by hitting the `RESET` keycode (which may be on a different layer), or by pressing the reset switch that's usually located on the underside of the board. If your keyboard has neither, try holding Esc or Space+B as you plug it in (see the [Bootmagic](feature_bootmagic.md) docs for more details). Some boards use [Command](feature_command.md) instead of Bootmagic; in this case, you can enter bootloader mode by hitting LShift+RShift+B or LShift+RShift+Esc at any point while the keyboard is plugged in.
vomindoraan marked this conversation as resolved.
Show resolved Hide resolved
Some keyboards may have specific instructions for entering the bootloader. For example, the [Bootmagic Lite](feature_bootmagic.md#bootmagic-lite) key (default: Esc) might be on a different key, e.g. LCtrl; or the magic combination for Command (default: LShift+RShift) might require you to hold something else, e.g. LCtrl+RCtrl. Refer to the board's README file if you are unsure.
vomindoraan marked this conversation as resolved.
Show resolved Hide resolved

Zadig will automatically detect the bootloader device. You may sometimes need to check **Options -> List All Devices**.
Zadig will automatically detect the bootloader device. You may sometimes need to check **Options List All Devices**.
- For keyboards with Atmel AVR MCUs, the bootloader will be named something similar to `ATm32U4DFU`, and have a Vendor ID of `03EB`.
- USBasp bootloaders will appear as `USBasp`, with a VID/PID of `16C0:05DC`.
- AVR keyboards flashed with the QMK-DFU bootloader will be named `<keyboard name> Bootloader` and will also have the VID `03EB`.
Expand Down Expand Up @@ -39,4 +39,4 @@ Right-click it and hit **Uninstall device**. Make sure to tick **Delete the driv

![The Device Uninstall dialog, with the "delete driver" checkbox ticked](https://i.imgur.com/aEs2RuA.png)

Click **Action -> Scan for hardware changes**. At this point, you should be able to type again. Double check in Zadig that the keyboard device(s) are using the `HidUsb` driver. If so, you're all done, and your board should be functional again!
Click **Action Scan for hardware changes**. At this point, you should be able to type again. Double check in Zadig that the keyboard device(s) are using the `HidUsb` driver. If so, you're all done, and your board should be functional again!