localhots
/
qmk_firmware
1
0
Fork 0
Code Releases Activity
qmk_firmware/keyboard/preonic
History
Jack Humbert b36e532b5e cleans up folder structure 
* consolidates docs
* deletes converter/
* updates .md references (most)
 		2016-06-04 00:10:47 -04:00
..
keymaps adds KC_NUBS, KC_NUHS and shifted versions to default keymaps 2016-05-17 22:17:23 -04:00
Makefile moves backlight functionality to keyboard files and updates template makefile 2016-04-29 22:19:40 -04:00
README.md Fixed minor issues with Preonic readme 2016-03-30 09:17:06 -04:00
config.h Optimize matrix scanning (#343) 2016-05-23 23:42:21 -04:00
preonic.c Leader key implementation (#326) 2016-05-15 00:27:32 -04:00
preonic.h cleans up default keymaps (olkb) 2016-05-15 01:07:48 -04:00
preonic_pcb_r1.hex removes extra voices, updates .hex files 2016-04-29 12:42:55 -04:00
preonic_pcb_r1_w_bootloader.hex removes extra voices, updates .hex files 2016-04-29 12:42:55 -04:00

README.md

Preonic keyboard firmware

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

Quantum MK Firmware

For the full Quantum feature list, see the parent README.md.

Building

Download or clone the whole firmware and navigate to the keyboard/preonic 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.

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 file in the keymaps folder 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.