* Remove unnecessary IS_COMMAND definition in clueboard/66/rev4 * Replace keyboard_report->mods with get_mods() in IS_COMMAND definitions * Update docs to use get_mods() instead of keyboard_report->mods * Replace keyboard_report->mods with get_mods() in tmk_core/protocol/usb_hid/test For some reason, this occurrence used KB_LSHIFT and KB_RSHIFT, which don't exist * Replace keyboard_report->mods with get_mods() in Massdrop keyboards (as per @patrickmt) |
||
|---|---|---|
| .. | ||
| config.h | ||
| i2c.c | ||
| i2c.h | ||
| matrix.c | ||
| readme.md | ||
| rules.mk | ||
| template.c | ||
| usbconfig.h | ||
%KEYBOARD%

A short description of the keyboard/project
Keyboard Maintainer: You
Hardware Supported: The PCBs, controllers supported
Hardware Availability: links to where you can find this hardware
Make example for this keyboard (after setting up your build environment):
make %KEYBOARD%:default
Flashing
ps2avr(GB) boards use an atmega32a microcontroller and a different bootloader. It is not flashable using the regular QMK methods.
Windows:
- Download HIDBootFlash.
- Place your keyboard into reset.
- Press the
Find Devicebutton and ensure that your keyboard is found. - Press the
Open .hex Filebutton and locate the.hexfile you created. - Press the
Flash Devicebutton and wait for the process to complete.
macOS:
-
Install homebrew by typing the following:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" -
Install
crosspack-avr.brew cask install crosspack-avr -
Install the following packages:
brew install python brew install pyusb brew install --HEAD`https://raw.githubusercontent.com/robertgzr/homebrew-tap/master/bootloadhid.rb -
Place your keyboard into reset.
-
Flash the board by typing
bootloadHID -rfollowed by the path to your.hexfile.
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.