History

Richard f4febd2cf7 Fix other KC60 Keymap Makefiles so they compile properly		2016-07-03 13:49:10 +12:00
..
keymaps	Fix other KC60 Keymap Makefiles so they compile properly	2016-07-03 13:49:10 +12:00
config.h	Backlight abstraction and other changes (#439 )	2016-06-23 22:18:20 -04:00
kc60.c	Backlight abstraction and other changes (#439 )	2016-06-23 22:18:20 -04:00
kc60.h	Backlight abstraction and other changes (#439 )	2016-06-23 22:18:20 -04:00
Makefile	Renames keyboard folder to keyboards, adds couple of tmk's fixes (#432 )	2016-06-21 22:39:54 -04:00
readme.md	Backlight abstraction and other changes (#439 )	2016-06-23 22:18:20 -04:00

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 keyboards/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.