History

Joel Challis dcb7ca3f79 Move some common matrix code to a common location (#7699 ) * Move some common matrix code to a common location * Refactor some 'custom_matrix_helper' logic to use custom matrix lite * Fix build for kinesis/stapelberg - abuse of vpath was picking up matrix.c from core when custom matrix was enabled * Add validation for CUSTOM_MATRIX		2020-01-04 20:29:44 +00:00
..
docs	remove .hex, .PNG, .jpg	2017-06-11 22:16:42 -04:00
alvicstep.c	kinesis remap	2017-01-08 22:02:01 -08:00
alvicstep.h	Kinesis refactor and Configurator update (#3245 )	2018-06-27 19:24:08 -07:00
config.h	kinesis remap	2017-01-08 22:02:01 -08:00
matrix.c	Remove _quantum functions from custom matrix.c code	2018-02-06 12:25:30 -05:00
readme.md	Fixed dead links (#2451 )	2018-03-01 07:45:47 -08:00
rules.mk	Move some common matrix code to a common location (#7699 )	2020-01-04 20:29:44 +00:00

readme.md

kinesis-advantage keyboard firmware

This directory is called alvicstep because https://github.com/alvicstep did the heavy work and took the photos in the doc directory. alvicstep did NOT do anything related to the QMK implementation, so don't bug him/her.

There are other ways of replacing the CPU in the kinesis, this one uses jumper wires from the Teensy to the original DIP socket

Kinesis specific information

This is a port of https://github.com/alvicstep/tmk_keyboard, which is a fork of https://github.com/wjanssens/tmk_keyboard, which is based on work from https://github.com/chrisandreae/keyboard-firmware

If you replace the kinesis CPU as described in the doc folder, then this code should allow you to use QMK. I've tested with a Teensy 2++, remember to change the CPU if you use a 32u4 instead.

Not yet implemented:

Kinesis EEProm reading or writing
Audio - this should be simple if we remove hardcoded pins from audio.h and switch to E7

Quantum MK Firmware

For the full Quantum feature list, see the parent readme.md.

Building

Download or clone the whole firmware and navigate to the keyboards/kinesis-advantage folder. Once your dev env is setup, you'll be able to type make to generate your .hex - you can then use the Teensy Loader to program your .hex file.

Depending on which keymap you would like to use, you will have to compile slightly differently.

Default

To build with the default keymap, simply run make.

Other Keymaps

Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create a folder with the name of your keymap in the keymaps folder, and see keymap documentation (you can find in top readme.md) and existant keymap files.

To build the firmware binary hex file with a keymap just do make with keymap option like:

$ make keymap=[default|jack|]

Keymaps follow the format keymap.c and are stored in folders in the keymaps folder, eg keymaps/my_keymap/