|
5 年之前 | |
---|---|---|
.. | ||
keymaps | 0072fdd799 Cleanup Default Keymaps (#5442) | 6 年之前 |
config.h | b05c0e46c6 Adds a default value for IS_COMMAND for COMMAND feature (#4301) | 6 年之前 |
dichotomy.c | 57678238a9 Keyboard: Fixing spelling, updating code, finalizing keymap for Dichotomy (#4539) | 6 年之前 |
dichotomy.h | ad3e4d6c13 Tidy up backlight header use to avoid build issues (#6714) | 5 年之前 |
info.json | b1ed855871 Dichotomy: fix info.json mismatch (#4771) | 6 年之前 |
matrix.c | 6d2071ad6e Fix `1<col` instead of `1<<col` typo in matrix_is_on() | 6 年之前 |
readme.md | 57678238a9 Keyboard: Fixing spelling, updating code, finalizing keymap for Dichotomy (#4539) | 6 年之前 |
rules.mk | 66fe3001e4 Trim firmware sizes from default rules.mk, part 1 (#8027) | 5 年之前 |
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.