diff options
author | Stick <nstickney@gmail.com> | 2017-04-03 16:59:27 -0500 |
---|---|---|
committer | Stick <nstickney@gmail.com> | 2017-04-03 16:59:27 -0500 |
commit | bee9183e7fae7c739b9c42dd4dc759783ac80e46 (patch) | |
tree | 690f17486c2e57175bbd36152d685ebedc7c9439 /keyboards/frosty_flake/readme.md | |
parent | b6280d0cac59c741db62a63072efd5de4887fc01 (diff) | |
parent | 3ac9259742bfd428f71c31dbf2bfedace2a7f91b (diff) |
Merge remote-tracking branch 'upstream/master'
Diffstat (limited to 'keyboards/frosty_flake/readme.md')
-rw-r--r-- | keyboards/frosty_flake/readme.md | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/keyboards/frosty_flake/readme.md b/keyboards/frosty_flake/readme.md new file mode 100644 index 0000000000..ff440e33b6 --- /dev/null +++ b/keyboards/frosty_flake/readme.md @@ -0,0 +1,32 @@ +frosty_flake keyboard firmware +====================== + +This is the firmware for Rev. 20140521 of the Frosty Flake controller by [Bathroom Epiphanies](http://bathroomepiphanies.com/controllers/), a replacement controller for the [Cooler Master Quick Fire Rapid](http://www.coolermaster.com/peripheral/keyboards/quickfirerapid/). + +The code was adapted from the [BathroomEpiphanies TMK Firmware](https://github.com/BathroomEpiphanies/epiphanies_tmk_keyboard/tree/master/be_controllers), but has been cleaned up to match the [schematic](https://deskthority.net/wiki/File:Frosty_Flake_Schematics.pdf) and gone through some minor refactoring for QMK. + +## 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. |