ahoneybun/qmk_firmware
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

QMK Configurator support for Maxipad keypad (#3307)

Browse source
This commit is contained in:
MechMerlin 2018-07-04 18:04:22 -07:00 • committed by Drashna Jaelre
parent 876377e945
commit 7eeb8932a1
4 changed files with 21 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

12
keyboards/maxipad/info.json Normal file
View file

@ -0,0 +1,12 @@
{
"keyboard_name": "maxipad",
"url": "",
"maintainer": "qmk",
"width": 6,
"height": 5,
"layouts": {
"LAYOUT": {
"layout": [{"x":0, "y":0}, {"x":1, "y":0}, {"x":2, "y":0}, {"x":3, "y":0}, {"x":4, "y":0}, {"x":5, "y":0}, {"x":0, "y":1}, {"x":1, "y":1}, {"x":2, "y":1}, {"x":3, "y":1}, {"x":4, "y":1}, {"x":5, "y":1}, {"x":0, "y":2}, {"x":1, "y":2}, {"x":2, "y":2}, {"x":3, "y":2}, {"x":4, "y":2}, {"x":5, "y":2}, {"x":0, "y":3}, {"x":1, "y":3}, {"x":2, "y":3}, {"x":3, "y":3}, {"x":4, "y":3}, {"x":5, "y":3}, {"x":0, "y":4}, {"x":1, "y":4}, {"x":2, "y":4}, {"x":3, "y":4}, {"x":4, "y":4}, {"x":5, "y":4}]
}
}
}

4
keyboards/maxipad/keymaps/default/keymap.c
View file

@ -1,14 +1,14 @@
#include "maxipad.h" #include "maxipad.h"
const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = { const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
[0] = KEYMAP( /* Base */ [0] = LAYOUT( /* Base */
KC_ESC, KC_1, KC_2, KC_3, KC_4, KC_5, \ KC_ESC, KC_1, KC_2, KC_3, KC_4, KC_5, \
KC_TAB, KC_Q, KC_W, KC_E, KC_R, KC_T, \ KC_TAB, KC_Q, KC_W, KC_E, KC_R, KC_T, \
MO(1), KC_A, KC_S, KC_D, KC_F, KC_G, \ MO(1), KC_A, KC_S, KC_D, KC_F, KC_G, \
KC_LSFT, KC_Z, KC_X, KC_C, KC_V, KC_B, \ KC_LSFT, KC_Z, KC_X, KC_C, KC_V, KC_B, \
KC_LCTL, KC_LALT, MO(1), KC_ENT,KC_GRV,KC_SPC \ KC_LCTL, KC_LALT, MO(1), KC_ENT,KC_GRV,KC_SPC \
), ),
[1] = KEYMAP( [1] = LAYOUT(
KC_GRV, KC_F1, KC_F2, KC_F3, KC_F4, KC_F5, \ KC_GRV, KC_F1, KC_F2, KC_F3, KC_F4, KC_F5, \
KC_TRNS, KC_TRNS, KC_UP, KC_TRNS, KC_TRNS, KC_TRNS, \ KC_TRNS, KC_TRNS, KC_UP, KC_TRNS, KC_TRNS, KC_TRNS, \
KC_TRNS, KC_LEFT, KC_DOWN, KC_RIGHT, KC_TRNS, KC_TRNS, \ KC_TRNS, KC_LEFT, KC_DOWN, KC_RIGHT, KC_TRNS, KC_TRNS, \

2
keyboards/maxipad/maxipad.h
View file

@ -7,7 +7,7 @@
// The following is an example using the Planck MIT layout // The following is an example using the Planck MIT layout
// The first section contains all of the arguements // The first section contains all of the arguements
// The second converts the arguments into a two-dimensional array // The second converts the arguments into a two-dimensional array
#define KEYMAP( \ #define LAYOUT( \
k00, k01, k02, k03, k04, k05, \ k00, k01, k02, k03, k04, k05, \
k10, k11, k12, k13, k14, k15, \ k10, k11, k12, k13, k14, k15, \
k20, k21, k22, k23, k24, k25, \ k20, k21, k22, k23, k24, k25, \

16
keyboards/maxipad/readme.md
View file

@ -1,4 +1,4 @@
Maxipad keyboard firmware # Maxipad
## Quantum MK Firmware ## Quantum MK Firmware
@ -7,23 +7,11 @@ For the full Quantum feature list, see [the parent readme.md](/readme.md).
If you are using a pro micro then make sure to enable USE_PRO_MICRO in the makefile 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!! 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. Depending on which keymap you would like to use, you will have to compile slightly differently.
### Default ### Default
To build with the default keymap, simply run `make`. To build with the default keymap, simply run `make maxipad:default`.
### Other Keymaps ### 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. 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.