Jack Humbert
b476d65b9c
this may change some of the keyboards' default settings - if you experience anything odd, please check back to this commit |
8 years ago | |
---|---|---|
.. | ||
keymaps/default | just saving | 8 years ago |
Makefile | just saving | 8 years ago |
config.h | having trouble with conflicts | 8 years ago |
maxipad.c | just saving | 8 years ago |
maxipad.h | just saving | 8 years ago |
readme.md | having trouble with conflicts | 8 years ago |
rules.mk | Update keyboards' rules.mk/Makefiles (#1442) | 8 years ago |
readme.md
Maxipad keyboard firmware
Quantum MK Firmware
For the full Quantum feature list, see the parent readme.md.
If you are using a pro micro then make sure to enable USE_PRO_MICRO in the makefile Change the config.h pinout to match your mcu!!
Download or clone the whole firmware and navigate to the keyboards/maxipad 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
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 a keymap like this:
$ make [default|jack|<name>]
Keymaps follow the format <name>.c and are stored in the keymaps
folder.