fad5a57156
* Don't save the ctags file in the repo. * Initial support for the KC60 board. Only 5x5 working so far. * Rename because this isn't the same KC60 as others. * Add in some generic layout. Pins seem to be in the right order except the 6th column spews gibberish. * Don't need this for now. * Move this to some other folder. * Trying again to start over. * Don't need to start over because I figured out why the 'broken' stuff wasn't working. * Attempt to enable backlighting. It's on on pin B7 like other boards. * Fix last port changes and fix LED control in keymap. * Trying some other LED code. * Bootloader needs to be bigger. Disabling backlight for now. * Simplify LED code while I try to figure it out. * Turn back on backlighting. * Backlighting works now. Just need to get levels or breathing working. * Trying to allow for turning off the LEDs before I get to brightness levels. * The missing link: need to run the init_ports function for LEDs to work properly. * Removing breathing stuff since it bricks the board. * Clean up default layer. * Cleanup keymap, KC60 doesn't support a 5th right bottom-row button. * Add in the keymap I want for now. * Back to escape by default. * Move my personal keymap to the new place for keymaps. * Add the version number for clarity.
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
KC60 (version 2.0) keyboard firmware
|
|
======================
|
|
|
|
## Quantum MK Firmware
|
|
|
|
For the full Quantum feature list, see [the parent README.md](/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.
|