summaryrefslogtreecommitdiffstats
path: root/keyboards/mitosis/readme.md
diff options
context:
space:
mode:
authorjpetermans <tibcmhhm@gmail.com>2017-05-08 15:24:50 -0700
committerjpetermans <tibcmhhm@gmail.com>2017-05-08 15:24:50 -0700
commit967cf0f6d43bd05c9951c7c31190971acd0799ea (patch)
tree34ff786a7e5177c6edc48e93b69ce71132cb3cbf /keyboards/mitosis/readme.md
parent5df74f3ba73f18f6bbd13b82a3a960c86fa592e1 (diff)
parent153eb95ab208cf5563ce2fae7ec68981b64d11ce (diff)
Merge remote-tracking branch 'upstream/master' into user_led_configuration
Diffstat (limited to 'keyboards/mitosis/readme.md')
-rw-r--r--keyboards/mitosis/readme.md33
1 files changed, 33 insertions, 0 deletions
diff --git a/keyboards/mitosis/readme.md b/keyboards/mitosis/readme.md
new file mode 100644
index 0000000000..70755e32ac
--- /dev/null
+++ b/keyboards/mitosis/readme.md
@@ -0,0 +1,33 @@
+Mitosis Keyboard Firmware
+======================
+
+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.
+
+Build log of the keyboard can be found [here](https://www.reddit.com/r/MechanicalKeyboards/comments/66588f/wireless_split_qmk_mitosis/)
+
+Hardware design files can be found [here](https://github.com/reversebias/mitosis-hardware)
+
+Firmware for the nordic MCUs can be found [here](https://github.com/reversebias/mitosis)
+
+## Quantum MK Firmware
+
+For the full Quantum feature list, see [the parent readme](/).
+
+## 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.