|
|
5 months ago | |
|---|---|---|
| .. | ||
| keymaps | f8596b40a4 Normalise mouse keycodes (#23975) | 2 years ago |
| config.h | f20a05440e Remove unused `MATRIX_HAS_GHOST` from config.h (#19726) | 3 years ago |
| dichotomy.c | d09a06a1b3 Update GPIO API usage in keyboard code (#23361) | 2 years ago |
| dichotomy.h | d09a06a1b3 Update GPIO API usage in keyboard code (#23361) | 2 years ago |
| keyboard.json | 960c4969a5 Remove empty `url` fields (#25181) | 1 year ago |
| matrix.c | db4d8823d6 Migrate ROW_SHIFTER to core MATRIX_ROW_SHIFTER (#25977) | 5 months ago |
| readme.md | 57678238a9 Keyboard: Fixing spelling, updating code, finalizing keymap for Dichotomy (#4539) | 7 years ago |
| rules.mk | 8ad3a36fb6 Data-Driven Keyboard Conversions: D (#23461) | 2 years ago |
These configuration files were based off the Mitosis keyboard. 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 - it also receives mouse pointer information from the keyboard halves, which is implemented through a new feature, "Pointing Device". The matrix.c file contains the code to poll the external microcontroller for the key matrix, and the keymap.c file contains similar code to obtain the mouse report. As long as the relavant functions in these files are not changed, all other QMK features are supported.
Build log of the keyboard can be found here
Hardware design files can be found here
Firmware for the nordic MCUs can be found here
For the full Quantum feature list, see the parent readme.
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.
To build with the default keymap, simply run make default.
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.