Stanley Lai
3302258abd
* Added WS2812 support for KC60 * Reorganized WS2812 support into its own keymap * Fixed relative link in README * Moved WS2812 mention in README to the bottom * Fixed titling in WS2812 README * Reverted KC60 Makefile and default keymap back * Moved RGB specific config.h to ws2812 keymap folder |
9 years ago | |
---|---|---|
.. | ||
keymaps | Added WS2812 support for KC60 (#419) | 9 years ago |
Makefile | Added WS2812 support for KC60 (#419) | 9 years ago |
README.md | Added WS2812 support for KC60 (#419) | 9 years ago |
config.h | Added WS2812 support for KC60 (#419) | 9 years ago |
kc60.c | Added WS2812 support for KC60 (#419) | 9 years ago |
kc60.h | Cleans up quantum/keymap situation, removes extra lufa folders (#416) | 9 years ago |
README.md
KC60 (version 2.0) 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 keyboard/kc60 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 file named <name>.c
in the keymaps folder, and see keymap document (you can find in top README.md) and existent 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 <name>.c and are stored in the keymaps
folder.
WS2812 Support
Build with WS2812 Support by running make KEYMAP=ws2812
.