summaryrefslogtreecommitdiff
path: root/keyboards/ps2avrGB
diff options
context:
space:
mode:
authorSebastian Kaim <32064878+sebastian-kaim@users.noreply.github.com>2017-10-27 17:25:02 +0200
committerJack Humbert <jack.humb@gmail.com>2017-10-29 19:59:16 -0400
commit688343f218d6ce9ac10a7fd27177478841d7c1a0 (patch)
tree9e806887d0cafba3f43205d7eed0242d8876ad56 /keyboards/ps2avrGB
parent4d421ee31c0003290bb4b083bcde8a7e607c082d (diff)
Added a better description for the bootloader key
Diffstat (limited to 'keyboards/ps2avrGB')
-rw-r--r--keyboards/ps2avrGB/README.md17
1 files changed, 15 insertions, 2 deletions
diff --git a/keyboards/ps2avrGB/README.md b/keyboards/ps2avrGB/README.md
index 8fd2af00f4..886e3aea89 100644
--- a/keyboards/ps2avrGB/README.md
+++ b/keyboards/ps2avrGB/README.md
@@ -49,13 +49,26 @@ $ make ps2avrGB
$ bootloadHID -r ps2avrGB_default.hex
```
+## Setting the board to bootloader mode
+
+If you're lucky, the programming script does this automagically for you. If
+however this doesn't work for you, you need to enter the bootloader mode manually
+by plugging the keyboard in while holding the bootloader key. If you did this
+correctly the LEDs will blink and you'll be able to flash your firmware.
+
+The bootloader key is the top left key of your matrix. For a standard board
+from winkeyless.kr this is `L_Ctrl`, but for some custom boards running ps2avrGB
+this might be different. For the Pearl it's `Esc`, for a b.fake it is `q`. If
+you're unsure you should be able to see the key in the bootmapper client.
+
+
## Troubleshooting
From my experience, it's really hard to brick these boards. But these
tricks have been useful when it got stuck in a weird scenario.
-1. Try plugging the board in while pressing `L_Ctrl`. This will force it
- to boot only the bootloader without loading the firmware. Once this is
+1. Try plugging the board in while holding the bootloader 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
to your computer or plugging/unplugging the USB hub.