History

Ryan 12d42cedd2 Move `FORCE_NKRO` to data driven (#20604 )		2023-05-01 13:33:10 +10:00
..
keymaps
config.h	Move `FORCE_NKRO` to data driven (#20604 )	2023-05-01 13:33:10 +10:00
info.json	Move `FORCE_NKRO` to data driven (#20604 )	2023-05-01 13:33:10 +10:00
matrix.c	Move ortho & numpad layouts to data driven (#20183 )	2023-03-29 15:54:34 +11:00
readme.md
rules.mk	Migrate `MCU` and `BOOTLOADER` to data-driven (#19529 )	2023-02-08 18:41:46 +11:00
sixkeyboard.c	Move ortho & numpad layouts to data driven (#20183 )	2023-03-29 15:54:34 +11:00

readme.md

Techkeys SixKeyBoard

Keyboard Maintainer: QMK Community
Hardware Supported: Techkeys SixKeyBoard PCB
Hardware Availability: Techkeys

Make example for this keyboard (after setting up your build environment):

make sixkeyboard:default

See build environment setup then the make instructions for more information.

Hardware Info

The schematic is like this:

 switches       leds
,--+--+--.   ,--+--+--.
|C7|B7|B5|   |C6|B6|B4|
+--+--+--+   +--+--+--+
|D6|D1|D4|   |D5|D2|D3|
`--+--+--'   `--+--+--'

The LED on the bottom is C4. All 7 of the leds are turned on when the keyboard boots-up in the sixkeyboard.c file - backlight_enable is not required. The MCU is an Atmega16u2, so the flash memory is limited to 0x3000 bytes - the current setup uses just about all of that! I'm sure things can be opitimised a bit.

There is a jumper on the bottom of the board (next to the USB port) that serves as a reset button - I drilled a hole in my case to allow for quick access via a screwdriver/metal object.