|
|
9 years ago | |
|---|---|---|
| .. | ||
| keymaps | 936a26d04f Added pin support for A0-A7 | 9 years ago |
| Makefile | fb8365a378 Split vision_division into Makefile/rules.mk | 9 years ago |
| Potential Layouts.txt | 705c775a4a Nightly | 9 years ago |
| config.h | 936a26d04f Added pin support for A0-A7 | 9 years ago |
| matrix_types.h | 705c775a4a Nightly | 9 years ago |
| readme.md | 5febdb0a3c Initial Commmit | 9 years ago |
| rules.mk | fb8365a378 Split vision_division into Makefile/rules.mk | 9 years ago |
| vision_division.c | 5febdb0a3c Initial Commmit | 9 years ago |
| vision_division.h | 705c775a4a Nightly | 9 years ago |
For the full Quantum feature list, see the parent readme.md.
Download or clone the whole firmware and navigate to the keyboards/vision_division 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.
To build with the default keymap, simply run make.
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 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/