summaryrefslogtreecommitdiff
path: root/keyboards
diff options
context:
space:
mode:
authorsgugler <sgugler@student.ethz.ch>2018-06-28 09:52:24 -0400
committerDrashna Jaelre <drashna@live.com>2018-06-28 06:52:24 -0700
commitf5f0e93230bbb40a37edf3adc4453bf4684fae56 (patch)
tree6c28d125dcf828050fbd611c08f9f23d2416b400 /keyboards
parent6590f3c81155f5d5cfb59c5b8a28610d6f3207d0 (diff)
added a description how to flash jj40 in windows (#3247)
Diffstat (limited to 'keyboards')
-rw-r--r--keyboards/jj40/README.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/keyboards/jj40/README.md b/keyboards/jj40/README.md
index 1b47ab8162..39e871d873 100644
--- a/keyboards/jj40/README.md
+++ b/keyboards/jj40/README.md
@@ -52,6 +52,13 @@ $ make jj40
$ bootloadHID -r jj40_default.hex
```
+For Windows 10:
+Windows sometimes doesn't recognize the jj40. The easiest way of flashing a new layout is probably using [HIDBootFlash](http://vusb.wikidot.com/project:hidbootflash).
+1. Go to Windows Device Manager and find the keyboard (plug it in while holding down `Backspace` (`Top Right Key`)). It can be found under Human Interface Devices or under Keyboards.
+2. Go to properties and the Details tab to find the hardware ID. You want the VID and the PID (code after the underscore). Plug them into HIDBootFlash and hit Find Device.
+3. Use `make jj40:<keymap-name>` to generate the .hex file in the qmk basis folder. Select the .hex file in HIDBootFlash and press Flash Device.
+
+
## Troubleshooting
1. Try plugging the board in while pressing `Backspace` (`Top Right Key`). This will force it