1 arrow_pad keyboard firmware
6 The ArrowPad is a wired conversion that can be made to any stand-alone keypad. It uses two main layers - a standard numpad, and a more advanced arrow cluster navigator.
8 The first 24-key ArrowPad was handwired, but the PCB was wired as listed below.
11 <Chip Ref Des> pin <Pin #>
12 <Keycap Name> (Silkscreen Name if different) - <Switch Pin #>
16 U2 pin 2 is the Num Lock LED and is active low.
34 Delete (BACK SPACE) - 2
52 Delete (BACK SPACE) - 1
92 More info can be found on [GeekHack](https://geekhack.org/index.php?topic=73632.msg1802497#msg1802497)
94 The second ArrowPad was a conversion from a 21-key Genovation keypad. It used a 2 row x 11 column matrix.
98 KM_ESC, KM_TAB, KM_BSL, KM_ARR, \
99 KM_NUM, KM_FSL, KM_AST, KM_MIN, \
100 KM___7, KM___8, KM___9, ___PLS, \
101 KM___4, KM___5, KM___6, KM_PLS, \
102 KM___1, KM___2, KM___3, ___ENT, \
103 KM___0, _____0, KM_DOT, KM_ENT \
105 { KM_ESC, KM_TAB, KM_BSL, KM_ARR, KM___7, KM___8, KM___9, KM_PLS, KM___1, KM___2, KM___3, }, \
106 { KM_NUM, KM_FSL, KM_AST, KM_MIN, KM___4, KM___5, KM___6, KM_ENT, KC_NO, KM___0, KM_DOT, }, \
111 ## Quantum MK Firmware
113 For the full Quantum feature list, see [the parent readme.md](/readme.md).
117 Download or clone the whole firmware and navigate to the keyboards/arrow_pad 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.
119 Depending on which keymap you would like to use, you will have to compile slightly differently.
122 To build with the default keymap, simply run `make default`.
125 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` in the keymaps folder, and see keymap document (you can find in top readme.md) and existent keymap files.
127 To build the firmware binary hex file with a keymap just do `make` with a keymap like this:
130 $ make [default|pad_21|pad_24|<name>]
133 Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder.