History

Fred Sundvik 523dff3005 Merge branch 'master' into makefile_overhaul		2016-08-25 23:26:02 +03:00
..
keymaps	Nightly	2016-08-23 23:05:35 -05:00
atomic.c	Backlight abstraction and other changes (#439 )	2016-06-23 22:18:20 -04:00
atomic.h	Backlight abstraction and other changes (#439 )	2016-06-23 22:18:20 -04:00
config.h	Backlight abstraction and other changes (#439 )	2016-06-23 22:18:20 -04:00
Makefile	Split keyboard makefiles into rules and Makefile	2016-08-20 03:56:08 +03:00
readme.md	Update keyboard readme files with new makefile instructions	2016-08-20 03:56:48 +03:00
rules.mk	Split keyboard makefiles into rules and Makefile	2016-08-20 03:56:08 +03:00

readme.md

Atomic keyboard firmware

DIY/Assembled ortholinear 60% 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 keyboards/atomic 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 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 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 a keymap like this:

$ make [default|jack|<name>]

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