6baaf5e5d4
- Remove the concept of "mcus". With only one target platform (CircuitPython), it no longer makes a bunch of sense and has been kept around for "what if" reasons, complicating our import chains and eating up RAM for pointless subclasses. If you're a `board`, you derive from `KeyboardConfig`. If you're a handwire, the user will derive from `KeyboardConfig`. The end. As part of this, `kmk.hid` was refactored heavily to emphasize that CircuitPython is our only supported HID stack, with stubs for future HID implementations (`USB_HID` becomes `AbstractHID`, probably only usable for testing purposes, `CircuitPython_USB_HID` becomes `USBHID`, and `BLEHID` is added with an immediate `NotImplementedError` on instantiation) - `KeyboardConfig` can now take a HID type at runtime. The NRF52840 boards will happily run in either configuration once CircuitPython support is in place, and a completely separate `mcu` subclass for each mode made no sense. This also potentially allows runtime *swaps* of HID driver down the line, but no code has been added to this effect. The default, and only functional value, for this is `HIDModes.USB` - Most consts have been moved to more logical homes - often, the main or, often only, component that uses them. `DiodeOrientation` moved to `kmk.matrix`, and anything HID-related moved to `kmk.hid`
44 lines
1.7 KiB
Python
44 lines
1.7 KiB
Python
import board
|
|
|
|
from kmk.matrix import DiodeOrientation
|
|
from kmk.matrix import intify_coordinate as ic
|
|
from kmk.keyboard_config import KeyboardConfig as _KeyboardConfig
|
|
|
|
|
|
class KeyboardConfig(_KeyboardConfig):
|
|
# Pin mappings for converter board found at hardware/README.md
|
|
# QMK: MATRIX_COL_PINS { F6, F7, B1, B3, B2, B6 }
|
|
# QMK: MATRIX_ROW_PINS { D7, E6, B4, D2, D4 }
|
|
col_pins = (board.A2, board.A3, board.A4, board.A5, board.SCK, board.MOSI)
|
|
row_pins = (board.D11, board.D10, board.D9, board.RX, board.D13)
|
|
diode_orientation = DiodeOrientation.COLUMNS
|
|
|
|
split_flip = True
|
|
split_offsets = (6, 6, 6, 6, 6)
|
|
split_type = 'UART'
|
|
uart_pin = board.SCL
|
|
extra_data_pin = board.SDA
|
|
rgb_pixel_pin = board.TX
|
|
led_pin = board.D7
|
|
|
|
coord_mapping = []
|
|
coord_mapping.extend(ic(0, x) for x in range(12))
|
|
coord_mapping.extend(ic(1, x) for x in range(12))
|
|
coord_mapping.extend(ic(2, x) for x in range(12))
|
|
|
|
# Buckle up friends, the bottom row of this keyboard is wild, and making
|
|
# our layouts match, visually, what the keyboard looks like, requires some
|
|
# surgery on the bottom two rows of coords
|
|
|
|
# Row index 3 is actually perfectly sane and we _could_ expose it
|
|
# just like the above three rows, however, visually speaking, the
|
|
# top-right thumb cluster button (when looking at the left-half PCB)
|
|
# is more inline with R3, so we'll jam that key (and its mirror) in here
|
|
coord_mapping.extend(ic(3, x) for x in range(6))
|
|
coord_mapping.append(ic(4, 2))
|
|
coord_mapping.append(ic(4, 9))
|
|
coord_mapping.extend(ic(3, x) for x in range(6, 12)) # Now, the rest of R3
|
|
|
|
# And now, to handle R4, which at this point is down to just six keys
|
|
coord_mapping.extend(ic(4, x) for x in range(3, 9))
|