summaryrefslogtreecommitdiffstats
path: root/keyboards/jj40
diff options
context:
space:
mode:
authorEiji Onchi <onchi.eiji@gmail.com>2017-11-26 07:26:03 +0100
committerJack Humbert <jack.humb@gmail.com>2017-11-26 08:22:23 +0100
commit5fd400faa999bdb15240966f6246c4788c438568 (patch)
tree1de062fe0b6c4730befb735b21528cf7f9d4b217 /keyboards/jj40
parentf2a0b0ee20619d2634d7e18ae662768d91402961 (diff)
downloadqmk_firmware-5fd400faa999bdb15240966f6246c4788c438568.tar.gz
qmk_firmware-5fd400faa999bdb15240966f6246c4788c438568.tar.xz
Fixed bootloader access key
Diffstat (limited to 'keyboards/jj40')
-rw-r--r--keyboards/jj40/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/keyboards/jj40/README.md b/keyboards/jj40/README.md
index 0720366ad..563f5788e 100644
--- a/keyboards/jj40/README.md
+++ b/keyboards/jj40/README.md
@@ -33,7 +33,7 @@ $ pip install pyusb
```
If you prefer, you can just build it and flash the firmware directly with
-`bootloadHID` if you boot the board while holding down `L_Ctrl` to keep it
+`bootloadHID` if you boot the board while holding down `Backspace` (`Top Right Key`) to keep it
in the bootloader:
```
@@ -43,7 +43,7 @@ $ bootloadHID -r jj40_default.hex
## Troubleshooting
-1. Try plugging the board in while pressing `L_Ctrl`. This will force it
+1. Try plugging the board in while pressing `Backspace` (`Top Right Key`). This will force it
to boot only the bootloader without loading the firmware. Once this is
done, just reflash the board with the original firmware.
2. Sometimes USB hubs can act weird, so try connecting the board directly