History

dankm 19a1fbaca2 Better non-Linux support (#2524 ) * grep -> $(GREP) Some UNIXy systems (FreeBSD for example) don't use GNU grep by default. Allow the user to specify which grep implementation to use so that GNU grep can be specified. * Allow using versioned avr-gcc command Don't hardcode "avr-gcc", and allow strings such as "avr-gcc8", or "avr-gcc-7.3.0" to match checks for "avr-gcc".		2018-03-26 16:08:08 -04:00
..
keymaps	Update to drashna files (#2587 )	2018-03-25 13:01:15 -07:00
config.h	Updates bootloader settings, adds file size check (#2029 )	2017-11-27 23:08:21 -05:00
readme.md	updated drashna's keymaps (#1769 )	2017-09-29 11:52:37 -10:00
rules.mk	Better non-Linux support (#2524 )	2018-03-26 16:08:08 -04:00
woodpad.c	updated drashna's keymaps (#1769 )	2017-09-29 11:52:37 -10:00
woodpad.h	updated drashna's keymaps (#1769 )	2017-09-29 11:52:37 -10:00

readme.md

woodpad keyboard firmware

Quantum MK Firmware

For the full Quantum feature list, see the parent readme.

Building

Download or clone the whole firmware and navigate to the keyboards/woodpad 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 default.

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 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.

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.