d2ff66a985
* include variables and .h files as pp directives * start layout compilation * split ergodoxes up * don't compile all layouts for everything * might seg fault * reset layouts variable * actually reset layouts * include rules.mk instead * remove includes from rules.mk * update variable setting * load visualizer from path * adds some more examples * adds more layouts * more boards added * more boards added * adds documentation for layouts * use lowercase names for LAYOUT_ * add layout.json files for each layout * add community folder, default keymaps for layouts * touch-up default layouts * touch-up layouts, some keyboard rules.mk * update documentation for layouts * fix up serial/i2c switches |
||
|---|---|---|
| .. | ||
| keymaps/default | ||
| Makefile | ||
| README.md | ||
| config.h | ||
| fivethirteen.c | ||
| fivethirteen.h | ||
| rules.mk | ||
README.md
fivethirteen 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/handwired/fivethirteen 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
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 keymap.c and are stored in folders in the keymaps folder, eg keymaps/my_keymap/