![]() * Cleanup Default Keymaps to conform to QMK Firmware standards * Minor fixes * Revert some changes |
6 years ago | |
---|---|---|
.. | ||
keymaps/default | Cleanup Default Keymaps (#5442) | 6 years ago |
config.h | Adds a default value for IS_COMMAND for COMMAND feature (#4301) | 6 years ago |
info.json | Keyboard: LFKPad refactor and Configurator support (#3439) | 6 years ago |
lfkpad.c | Keyboard: LFKPad refactor and Configurator support (#3439) | 6 years ago |
lfkpad.h | Keyboard: LFKPad refactor and Configurator support (#3439) | 6 years ago |
readme.md | Fixed dead links (#2451) | 7 years ago |
rules.mk | Fix the LFKeyboards so they work with the QMK Configurator (#4591) | 6 years ago |
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/