localhots
/
qmk_firmware
1
0
Fork 0
Code Releases Activity
qmk_firmware/keyboards/sixkeyboard
History
noroadsleft eccfb8d55e SixKeyBoard refactor (#3193) 
* Refactor: create matrix macro

* Readme changes

* Configurator support
 		2018-06-16 08:02:11 -07:00
..
keymaps/default SixKeyBoard refactor (#3193) 2018-06-16 08:02:11 -07:00
config.h adds debouncing to sixkeyboard 2017-06-30 16:33:49 -04:00
info.json SixKeyBoard refactor (#3193) 2018-06-16 08:02:11 -07:00
matrix.c remove warning 2017-06-30 16:33:49 -04:00
readme.md SixKeyBoard refactor (#3193) 2018-06-16 08:02:11 -07:00
rules.mk Update keyboards' rules.mk/Makefiles (#1442) 2017-06-30 16:09:52 -04:00
sixkeyboard.c
…
sixkeyboard.h SixKeyBoard refactor (#3193) 2018-06-16 08:02:11 -07: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.