aboutsummaryrefslogtreecommitdiff
path: root/docs/faq_build.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/faq_build.md')
-rw-r--r--docs/faq_build.md14
1 files changed, 12 insertions, 2 deletions
diff --git a/docs/faq_build.md b/docs/faq_build.md
index 7d17df074..14c61a1e9 100644
--- a/docs/faq_build.md
+++ b/docs/faq_build.md
@@ -17,7 +17,7 @@ or just:
17 17
18Note that running `make` with `sudo` is generally *not* a good idea, and you should use one of the former methods, if possible. 18Note that running `make` with `sudo` is generally *not* a good idea, and you should use one of the former methods, if possible.
19 19
20## Linux `udev` Rules 20### Linux `udev` Rules
21On Linux, you'll need proper privileges to access the MCU. You can either use 21On Linux, you'll need proper privileges to access the MCU. You can either use
22`sudo` when flashing firmware, or place these files in `/etc/udev/rules.d/`. 22`sudo` when flashing firmware, or place these files in `/etc/udev/rules.d/`.
23 23
@@ -37,6 +37,14 @@ SUBSYSTEMS=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2ff0", MODE:="066
37SUBSYSTEMS=="usb", ATTRS{idVendor}=="feed", MODE:="0666" 37SUBSYSTEMS=="usb", ATTRS{idVendor}=="feed", MODE:="0666"
38``` 38```
39 39
40## Unknown Device for DFU Bootloader
41
42If you're using Windows to flash your keyboard, and you are running into issues, check the Device Manager. If you see an "Unknown Device" when the keyboard is in "bootloader mode", then you may have a driver issue.
43
44Re-running the installation script for MSYS2 may help (eg run `./util/qmk_install.sh` from MSYS2/WSL) or reinstalling the QMK Toolbox may fix the issue.
45
46If that doesn't work, then you may need to grab the [Zadig Utility](https://zadig.akeo.ie/). Download this, find the device in question, and select the `WinUS(libusb-1.0)` option, and hit "Reinstall driver". Once you've done that, try flashing your board, again.
47
40## WINAVR is Obsolete 48## WINAVR is Obsolete
41It is no longer recommended and may cause some problem. 49It is no longer recommended and may cause some problem.
42See [TMK Issue #99](https://github.com/tmk/tmk_keyboard/issues/99). 50See [TMK Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
@@ -97,10 +105,12 @@ The solution is to remove and reinstall all affected modules.
97``` 105```
98brew rm avr-gcc 106brew rm avr-gcc
99brew rm dfu-programmer 107brew rm dfu-programmer
108brew rm dfu-util
100brew rm gcc-arm-none-eabi 109brew rm gcc-arm-none-eabi
101brew rm avrdude 110brew rm avrdude
102brew install avr-gcc 111brew install avr-gcc
103brew install dfu-programmer 112brew install dfu-programmer
113brew install dfu-util
104brew install gcc-arm-none-eabi 114brew install gcc-arm-none-eabi
105brew install avrdude 115brew install avrdude
106``` 116```
@@ -116,5 +126,5 @@ For now, you need to rollback avr-gcc to 7 in brew.
116``` 126```
117brew uninstall --force avr-gcc 127brew uninstall --force avr-gcc
118brew install avr-gcc@7 128brew install avr-gcc@7
119brew link avr-gcc@7 129brew link --force avr-gcc@7
120``` 130```