History

Gabriel Young 4a97ef6c48 start to define keymap; annoying because rows and columns are swapped from schematic		2017-03-19 19:55:55 -07:00
..
keymaps/default	start to define keymap; annoying because rows and columns are swapped from schematic	2017-03-19 19:55:55 -07:00
Makefile	boilerplate project created with new_project.sh	2017-03-18 15:38:03 -07:00
config.h	successfully read data from the matrix	2017-03-19 15:59:21 -07:00
frosty_flake.c	boilerplate project created with new_project.sh	2017-03-18 15:38:03 -07:00
frosty_flake.h	start to define keymap; annoying because rows and columns are swapped from schematic	2017-03-19 19:55:55 -07:00
matrix.c	start to define keymap; annoying because rows and columns are swapped from schematic	2017-03-19 19:55:55 -07:00
readme.md	boilerplate project created with new_project.sh	2017-03-18 15:38:03 -07:00
rules.mk	sketch out frosty flake matrix using custom matrix.c based on kitten paw	2017-03-18 16:19:10 -07:00

readme.md

frosty_flake keyboard firmware

Quantum MK Firmware

For the full Quantum feature list, see the parent readme.

Building

Download or clone the whole firmware and navigate to the keyboards/frosty_flake 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 default.

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 a keymap like this:

$ make [default|jack|<name>]

Keymaps follow the format <name>.c and are stored in the keymaps folder.