qmk_firmware/keyboards/lfkeyboards/lfkpad
fauxpark e96cac0814 Cleanup rules.mk for 32U4 keyboards, L-M (#7120)
* Cleanup rules.mk for 32U4 keyboards, L-M

* Move some stuff to keyboard level
2019-10-24 13:50:13 -07:00
..
keymaps/default Remove/migrate action_get_macro()s from default keymaps (#5625) 2019-07-15 23:04:02 -07:00
config.h Replace DEBOUNCING_DELAY (deprecated) with DEBOUNCE (#5997) 2019-06-06 12:09:56 -07:00
info.json Keyboard: LFKPad refactor and Configurator support (#3439) 2018-07-18 20:03:40 -07:00
lfkpad.c Keyboard: LFKPad refactor and Configurator support (#3439) 2018-07-18 20:03:40 -07:00
lfkpad.h Keyboard: LFKPad refactor and Configurator support (#3439) 2018-07-18 20:03:40 -07:00
readme.md
rules.mk Cleanup rules.mk for 32U4 keyboards, L-M (#7120) 2019-10-24 13:50:13 -07:00

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/