Nikolaus Wittenstein
8ddbf7f59f
Fixes #1201. |
8 years ago | |
---|---|---|
.. | ||
keymaps | Fix spelling of "persistent" | 8 years ago |
Makefile | Split keyboard makefiles into rules and Makefile | 8 years ago |
atomic.c | Backlight abstraction and other changes (#439) | 9 years ago |
atomic.h | Backlight abstraction and other changes (#439) | 9 years ago |
config.h | Backlight abstraction and other changes (#439) | 9 years ago |
readme.md | Update keyboard readme files with new makefile instructions | 8 years ago |
rules.mk | Split keyboard makefiles into rules and Makefile | 8 years ago |
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.