qmk_firmware/keyboard/planck
2016-02-07 10:39:01 -05:00
..
keymaps Remove obsolete comments 2016-02-03 16:54:38 -05:00
old_keymap_files making the extended keymap the default - no more 'common' 2015-08-22 11:10:57 -04:00
backlight.c ok 2015-08-16 17:52:49 -04:00
config.h Integrate WS2812 code into quantum core 2016-01-24 17:05:47 -08:00
flash-pcb.sh ok 2015-08-16 17:52:03 -04:00
Makefile no message 2016-01-24 18:16:40 -08:00
PCB_GUIDE.md Update PCB_GUIDE.md 2016-02-05 19:06:25 -05:00
planck.c Add support for WS2812 LEDs 2016-01-24 13:14:50 -08:00
planck.h Add support for WS2812 LEDs 2016-01-24 13:14:50 -08:00
planck_pcb.hex pcb hex 2015-09-26 00:39:48 -04:00
planck_with_bootloader.hex bluetooth 2015-10-22 13:37:45 -04:00
README.md Merge branch 'master' of https://github.com/jackhumbert/tmk_keyboard 2016-02-07 10:39:01 -05:00

Planck keyboard firmware

DIY/Assembled compact ortholinear 40% keyboard by Ortholinear Keyboards.

Quantum MK Firmware

Building

Download or clone the whole firmware and navigate to the keyboard/planck folder. Once your dev env is setup, you'll be able to type make to generate your .hex - you can then use make dfu to program your PCB once you hit the reset button.

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.

Safety Considerations

You probably don't want to "brick" your keyboard, making it impossible to rewrite firmware onto it. Here are some of the parameters to show what things are (and likely aren't) too risky.

  • If a keyboard map does not include RESET, then, to get into DFU mode, you will need to press the reset button on the PCB, which requires unscrewing some bits.
  • Messing with tmk_core / common files might make the keyboard inoperable
  • Too large a .hex file is trouble; make dfu will erase the block, test the size (oops, wrong order!), which errors out, failing to flash the keyboard
  • DFU tools do /not/ allow you to write into the bootloader (unless you throw in extra fruitsalad of options), so there is little risk there.
  • EEPROM has around a 100000 write cycle. You shouldn't rewrite the firmware repeatedly and continually; that'll burn the EEPROM eventually.

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.

To build the firmware binary hex file with a keymap just do make with KEYMAP option like:

$ make KEYMAP=[default|jack|<name>]

Keymaps follow the format <name>.c and are stored in the keymaps folder.

Notable forks (which some of the keymap files are from)