cbabc8dbe6
* Replace Tapping Force Hold feature with Quick Tap Term * Replace keyboard level TAPPING_FORCE_HOLD with QUICK_TAP_TERM 0 * Deprecate force hold in info_config.json * Before and after quick tap term unit tests * Quick tap unit tests iteration * Keymap config.h correction * Remove TAPPING_FORCE_HOLD_PER_KEY macros that were missed * Add two more test cases for quick tap * Replace TAPPING_FORCE_HOLD with QUICK_TAP_TERM in configs #2 * Replace TAPPING_FORCE_HOLD_PER_KEY with QUICK_TAP_TERM_PER_KEY in configs #2 * Add function declaration for get_quick_tap_term Co-authored-by: Stefan Kerkmann <karlk90@pm.me> |
||
|---|---|---|
| .. | ||
| keymaps | ||
| rev1 | ||
| rev2 | ||
| config.h | ||
| info.json | ||
| kyria.c | ||
| kyria.h | ||
| readme.md | ||
| rules.mk | ||
readme.md
Kyria
An ergonomical 40% split keyboard
Keyboard Maintainer: splitkb.com
Hardware Supported: Pro Micro 5V/16MHz and compatible.
Hardware Availability: splitkb.com and partners.
Make example for this keyboard (after setting up your build environment):
make splitkb/kyria/rev2:default
make splitkb/kyria/rev2/proton_c:default
Example of flashing this keyboard:
make splitkb/kyria/rev2:default:flash
Replace "rev2" with "rev1" if you have a Kyria of revision 1.4 or below. Not sure what revision yours is? It is printed on the outer lower edge of the PCB! As a rule of thumb, all Kyrias sold after January 1st 2022 are revision 2.x.
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.
A build guide for the Kyria can be found at docs.splitkb.com.
Proton C Conversion Guide
If you're one of the lucky people to have Proton Cs to use with their Kyria, there are a couple of caveats to getting this working.
- You need to have 2x Proton Cs, as you cannot mix and match with Pro Micros or Elite C's. They both need to be Proton Cs.
- You'll need to do some modding to enable proper support with the Proton C.
By design, the Kyria uses every available pin on the Pro Micro footprint. This includes using D3 (RX) for RGB. This poses a challenge with using the Proton C, since it needs both the TX and RX pins. The Proton C needs both pins, especially if you plan on using Full Duplex Serial.
To fix this, you need to break off the last header position on the right-hand side on the footprint. This is the TX0/D3 pad. Leave this pad without a header connected to.
From the A9 pin on the Proton C, you want to run a wire from it to the SDA + Extra Data pad near the TRRS jack on the PCB. This will allow for proper, full duplex communication over the TRRS cable.
To get RGB working properly, as well, you want to run a wire from the A3 pin on the Proton C, next to the GND and DFU pin, right under the USB port. Run this to the TX0/D3 pad (the one you left without a header pin on the PCB).
Once you've done that, you can solder in the Proton C. and flash it.
