5f4c2dfd84
* change diverge 3 KC_KEYMAP to LAYOUT * Change KEYMAP to LAYOUT for handwired arrow pad * change M10A to LAYOUT for m10-a * Change KC_KEYMAP to LAYOUT_kc and KEYMAP to LAYOUT for mf68 * change KC_KEYMAP to LAYOUT for nano * Refactor to LAYOUT * refactor to LAYOUT-ansi and LAYOUT_iso for s65 * LAYOUT conversions for lfkkeyboards * missed a few renames * mini1800 for lfkeyobards support of LAYOUT |
||
|---|---|---|
| .. | ||
| keymaps/default | ||
| config.h | ||
| lfkpad.c | ||
| lfkpad.h | ||
| readme.md | ||
| rules.mk | ||
readme.md
bluepad keyboard firmware
Quantum MK Firmware
For the full Quantum feature list, see the parent readme.md.
Building
Download or clone the whole firmware and navigate to the keyboards/bluepad folder. Once your dev env is setup, you'll be able to type make to generate your .hex - you can then use the Teensy Loader to program your .hex file.
Depending on which keymap you would like to use, you will have to compile slightly differently.
Default
To build with the default keymap, simply run make.
Other Keymaps
Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create a folder with the name of your keymap in the keymaps folder, and see keymap documentation (you can find in top readme.md) and existant keymap files.
To build the firmware binary hex file with a keymap just do make with keymap option like:
$ make keymap=[default|jack|<name>]
Keymaps follow the format keymap.c and are stored in folders in the keymaps folder, eg keymaps/my_keymap/