Ryan 12d42cedd2 Move `FORCE_NKRO` to data driven (#20604) 3 years ago
..
keymaps 99b35940bc Remove unnecessary backslash-escapes in default keymaps (#15472) 4 years ago
config.h 12d42cedd2 Move `FORCE_NKRO` to data driven (#20604) 3 years ago
info.json 12d42cedd2 Move `FORCE_NKRO` to data driven (#20604) 3 years ago
matrix.c 4869b8061c Move ortho & numpad layouts to data driven (#20183) 3 years ago
readme.md c8cbee5d71 Modified URLs to point to new locations 7 years ago
rules.mk f9aeea64c1 Migrate `MCU` and `BOOTLOADER` to data-driven (#19529) 3 years ago
sixkeyboard.c 4869b8061c Move ortho & numpad layouts to data driven (#20183) 3 years ago

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.