diff options
| author | Sebastian Kaim <32064878+sebastian-kaim@users.noreply.github.com> | 2017-10-27 17:25:02 +0200 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2017-10-29 19:59:16 -0400 |
| commit | 688343f218d6ce9ac10a7fd27177478841d7c1a0 (patch) | |
| tree | 9e806887d0cafba3f43205d7eed0242d8876ad56 | |
| parent | 4d421ee31c0003290bb4b083bcde8a7e607c082d (diff) | |
| download | qmk_firmware-688343f218d6ce9ac10a7fd27177478841d7c1a0.tar.gz qmk_firmware-688343f218d6ce9ac10a7fd27177478841d7c1a0.zip | |
Added a better description for the bootloader key
| -rw-r--r-- | keyboards/ps2avrGB/README.md | 17 |
1 files changed, 15 insertions, 2 deletions
diff --git a/keyboards/ps2avrGB/README.md b/keyboards/ps2avrGB/README.md index 8fd2af00f..886e3aea8 100644 --- a/keyboards/ps2avrGB/README.md +++ b/keyboards/ps2avrGB/README.md | |||
| @@ -49,13 +49,26 @@ $ make ps2avrGB | |||
| 49 | $ bootloadHID -r ps2avrGB_default.hex | 49 | $ bootloadHID -r ps2avrGB_default.hex |
| 50 | ``` | 50 | ``` |
| 51 | 51 | ||
| 52 | ## Setting the board to bootloader mode | ||
| 53 | |||
| 54 | If you're lucky, the programming script does this automagically for you. If | ||
| 55 | however this doesn't work for you, you need to enter the bootloader mode manually | ||
| 56 | by plugging the keyboard in while holding the bootloader key. If you did this | ||
| 57 | correctly the LEDs will blink and you'll be able to flash your firmware. | ||
| 58 | |||
| 59 | The bootloader key is the top left key of your matrix. For a standard board | ||
| 60 | from winkeyless.kr this is `L_Ctrl`, but for some custom boards running ps2avrGB | ||
| 61 | this might be different. For the Pearl it's `Esc`, for a b.fake it is `q`. If | ||
| 62 | you're unsure you should be able to see the key in the bootmapper client. | ||
| 63 | |||
| 64 | |||
| 52 | ## Troubleshooting | 65 | ## Troubleshooting |
| 53 | 66 | ||
| 54 | From my experience, it's really hard to brick these boards. But these | 67 | From my experience, it's really hard to brick these boards. But these |
| 55 | tricks have been useful when it got stuck in a weird scenario. | 68 | tricks have been useful when it got stuck in a weird scenario. |
| 56 | 69 | ||
| 57 | 1. Try plugging the board in while pressing `L_Ctrl`. This will force it | 70 | 1. Try plugging the board in while holding the bootloader key. This will force |
| 58 | to boot only the bootloader without loading the firmware. Once this is | 71 | it to boot only the bootloader without loading the firmware. Once this is |
| 59 | done, just reflash the board with the original firmware. | 72 | done, just reflash the board with the original firmware. |
| 60 | 2. Sometimes USB hubs can act weird, so try connecting the board directly | 73 | 2. Sometimes USB hubs can act weird, so try connecting the board directly |
| 61 | to your computer or plugging/unplugging the USB hub. | 74 | to your computer or plugging/unplugging the USB hub. |
