jlj-qmk/keyboards/maxipad/readme.md

52 lines
1.9 KiB
Markdown
Raw Normal View History

<<<<<<< HEAD
2016-11-19 04:40:34 +00:00
Maxipad keyboard firmware
2016-11-17 00:18:54 +00:00
======================
## Quantum MK Firmware
2016-11-19 04:40:34 +00:00
For the full Quantum feature list, see [the parent readme.md](/readme.md).
=======
2016-11-17 00:18:54 +00:00
## Quantum MK Firmware
For the full Quantum feature list, see [the parent readme](/).
2016-11-17 01:44:49 +00:00
>>>>>>> a06115df19a74d39b08758472b221e630c3680d3
2016-11-17 00:18:54 +00:00
## Building
2016-11-19 04:40:34 +00:00
If you are using a pro micro then make sure to enable USE_PRO_MICRO in the makefile
2016-11-17 00:18:54 +00:00
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
<<<<<<< HEAD
2016-11-17 00:18:54 +00:00
To build with the default keymap, simply run `make default`.
=======
2016-11-17 00:18:54 +00:00
To build with the default keymap, simply run `make`.
2016-11-17 01:44:49 +00:00
>>>>>>> a06115df19a74d39b08758472b221e630c3680d3
2016-11-17 00:18:54 +00:00
### Other Keymaps
2016-11-19 04:40:34 +00:00
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.
2016-11-17 00:18:54 +00:00
<<<<<<< HEAD
=======
2016-11-17 00:18:54 +00:00
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.
>>>>>>> a06115df19a74d39b08758472b221e630c3680d3
2016-11-17 00:18:54 +00:00
To build the firmware binary hex file with a keymap just do `make` with a keymap like this:
```
$ make [default|jack|<name>]
```
<<<<<<< HEAD
Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder.
=======
2016-11-17 00:18:54 +00:00
Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder.
>>>>>>> a06115df19a74d39b08758472b221e630c3680d3