598cb82655
- a keyboard already in bootloader mode will now be detected - if setting the keyboard to bootloader mode doesn't work, a hint will be printed on how to do so - instead of failing instantly when no keyboard is found, the script will now wait up to 60 seconds (it retries every 5 seconds, up to 12 times) |
||
|---|---|---|
| .. | ||
| keymaps/default | ||
| config.h | ||
| i2c.c | ||
| i2c.h | ||
| matrix.c | ||
| program | ||
| ps2avrGB.c | ||
| ps2avrGB.h | ||
| README.md | ||
| rules.mk | ||
| usbconfig.h | ||
ps2avrGB keyboard firmware
This is a port of the QMK firmware for boards that are based on the ps2avrGB firmware, like the ps2avrGB keyboard or the ones sold by Winkeyless.
Note that this is a complete replacement for the firmware, so you won't be using Bootmapper Client to change any keyboard settings, since not all the USB report options are supported.
Supported Boards
Only the B.mini X2 has been tested so far (since it's the only one I own). But other boards that use the ps2avrGB firmware should work as well.
Installing
First, install the requirements. These commands are for OSX, but all you
need is the AVR toolchain and bootloadHID for flashing:
$ brew cask install crosspack-avr
$ brew install --HEAD https://raw.githubusercontent.com/robertgzr/homebrew-tap/master/bootloadhid.rb
In order to use the ./program script, which can reboot the board into
the bootloader, you'll need Python 2 with PyUSB installed:
$ pip install pyusb
Then, with the keyboard plugged in, simply run this command from the
qmk_firmware directory:
$ make ps2avrGB-program
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
in the bootloader:
$ make ps2avrGB
$ bootloadHID -r ps2avrGB_default.hex
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.
- 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 done, just reflash the board with the original firmware. - Sometimes USB hubs can act weird, so try connecting the board directly to your computer or plugging/unplugging the USB hub.