darkkirb/qmk_firmware
1
0
Fork 0
forked from mirrors/qmk_firmware
Code Issues Pull requests Projects Releases Packages Wiki Activity

Added a better description for the bootloader key

Browse source
This commit is contained in:
Sebastian Kaim 2017-10-27 17:25:02 +02:00 committed by Jack Humbert
parent 4d421ee31c
commit 688343f218
1 changed files with 15 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
keyboards/ps2avrGB/README.md
View file

@ -49,13 +49,26 @@ $ make ps2avrGB
$ bootloadHID -r ps2avrGB_default.hex $ 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 ## Troubleshooting
From my experience, it's really hard to brick these boards. But these 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. 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 1. Try plugging the board in while holding the bootloader key. This will force
to boot only the bootloader without loading the firmware. Once this is it to boot only the bootloader without loading the firmware. Once this is
done, just reflash the board with the original firmware. done, just reflash the board with the original firmware.
2. Sometimes USB hubs can act weird, so try connecting the board directly 2. Sometimes USB hubs can act weird, so try connecting the board directly
to your computer or plugging/unplugging the USB hub. to your computer or plugging/unplugging the USB hub.