qmk-firmware/keyboards/mitosis/readme.md

34 lines
1.9 KiB
Markdown
Raw Normal View History

2017-04-19 14:39:44 +02:00
Mitosis Keyboard Firmware
2017-04-19 12:27:49 +02:00
======================
These configuration files were based off the Atreus keyboard. It assumes a Pro Micro is being used, however retains the 'make upload' feature from the Atreus branch. This keyboard uses a completely different 'matrix scan' system to other keyboards, it relies on an external nRF51822 microcontroller maintaining a matrix of keystates received from the keyboard halves. The matrix.c file contains the code to poll the external microcontroller for the key matrix. As long as this file is not changed, all other QMK features are supported.
2017-04-19 14:39:44 +02:00
Build log of the keyboard can be found [here](https://www.reddit.com/r/MechanicalKeyboards/comments/66588f/wireless_split_qmk_mitosis/)
2017-04-19 12:27:49 +02:00
2017-04-19 14:39:44 +02:00
Hardware design files can be found [here](https://github.com/reversebias/mitosis-hardware)
2017-04-19 12:27:49 +02:00
2017-04-19 14:39:44 +02:00
Firmware for the nordic MCUs can be found [here](https://github.com/reversebias/mitosis)
2017-04-19 12:27:49 +02:00
2017-04-19 14:39:44 +02:00
## Quantum MK Firmware
2017-04-19 12:27:49 +02:00
2017-04-19 14:39:44 +02:00
For the full Quantum feature list, see [the parent readme](/).
2017-04-19 12:27:49 +02:00
## Building
Download or clone the whole firmware and navigate to the keyboards/atreus 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 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 a keymap like this:
```
$ make [default|jack|<name>]
```
Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder.