|
|
9 лет назад | |
|---|---|---|
| .. | ||
| keymaps | 9 лет назад | |
| Makefile | 9 лет назад | |
| config.h | 9 лет назад | |
| maxipad.c | 9 лет назад | |
| maxipad.h | 9 лет назад | |
| readme.md | 9 лет назад | |
| rules.mk | 9 лет назад | |
<<<<<<< HEAD
For the full Quantum feature list, see the parent readme.
If you are using a pro micro then make sure to enable USE_PRO_MICRO in the makefile
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.
<<<<<<< HEAD
make default.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 file named <name>.c and see keymap document (you can find in top readme.md) and existent keymap files.
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.
a06115df19To build the firmware binary hex file with a keymap just domakewith a keymap like this:
$ make [default|jack|<name>]
<<<<<<< HEAD
keymaps folder.Keymaps follow the format <name>.c and are stored in the keymaps folder.