1
0
Fork 0
qmk_firmware/keyboards/meira
Graham P Heath 10c636a1ee Keyboard: add Telophase board (and Graham's keymaps) (#3244)
* add my config

* fix backlight, clean up that code

* group background code, restore static var

* qwerty is supposed to be in the middle

* wrap layer change backlight in ifdef

* backlight levels and some more 'emojis'.

* Restructure to make it possible to press cmd ent on the right side of the board with one hand.

* Expose the period through the number layer. Add Hyper keys to mouse layer

* reduce mouse speed

* add a : -P  key

* Thumbs up and down, remove some keys that are duplicated via function keys, clean up

* fix build issues

* add various emoji

* duplicate default Meira keymaps

* Miera updates

* add documented but unmapped emoji

* Sound for the Meira, was stumped by a file size! Thanks drashna!

* add docs

* docs

* revert lib changes...

* clean up

* clean up

* remove make file

* Fixes missing key

* clean up

* add my lets split

* add more emoji

* add the telophase board (unofficially, I guess...)

* add missing files

* add/reset files

* Review feedback implementation: Not needed. Add #define FLIP_HALF to your config.h file instead.

* Review feedback implementation: All of these includes should be replaced with #include QMK_KEYBOARD_H.

* Review feedback implementation: [FAILING] You may want to use LAYOUT_ortho_4x12 instead, and move this to /layouts/community/ortho_4x12/ instead. That way, you can use the same keymap for all of the boards.

* clean up

* add a key for command tilde (osx loves it)

* at least its building again

* remove adjusts and migrate layer switching to MO(_LAYER)

* update the telophase readme

* update the telophase readme

* grahampheaths -> grahampheath

* ONEHAND_ENABLE -> SWAP_HANDS_ENABLE

* convert lets split to use ortho_4x12

* Move lets split keyboard layout into community/ortho_4x12

* make telophase use LAYOUT()

* I did it?!

* Add clap and grin

* swap tabs and back and forward

* whitespace
2018-08-19 13:29:11 -07:00
..
featherble Meira updates for bluetooth and audio (#2731) 2018-04-19 00:57:24 -04:00
keymaps Keyboard: add Telophase board (and Graham's keymaps) (#3244) 2018-08-19 13:29:11 -07:00
promicro Meira updates for bluetooth and audio (#2731) 2018-04-19 00:57:24 -04:00
config.h Meira updates for bluetooth and audio (#2731) 2018-04-19 00:57:24 -04:00
issi.c Add support for Meira 2017-12-09 00:05:35 -05:00
issi.h Add support for Meira 2017-12-09 00:05:35 -05:00
lighting.c Update Meira for revision 1.1 to enable backlighting by default (#2468) 2018-03-07 17:06:41 -05:00
lighting.h Add support for Meira 2017-12-09 00:05:35 -05:00
matrix.c Remove _quantum functions from custom matrix.c code 2018-02-06 12:25:30 -05:00
meira.c Meira updates for bluetooth and audio (#2731) 2018-04-19 00:57:24 -04:00
meira.h Meira updates for bluetooth and audio (#2731) 2018-04-19 00:57:24 -04:00
readme.md Update Meira readme 2017-12-09 00:05:35 -05:00
rules.mk Meira updates for bluetooth and audio (#2731) 2018-04-19 00:57:24 -04:00
TWIlib.c Add support for Meira 2017-12-09 00:05:35 -05:00
TWIlib.h Add support for Meira 2017-12-09 00:05:35 -05:00

Meira

Miera

A 4x12 ortholinear low-profile keyboard.

Keyboard Maintainer: Cole Markham
Hardware Supported: Meira/ProMicro, Meira/FeatherBLE
Hardware Availability: WoodKeys.click

Two controllers are support: the Pro Micro, and the Adafruit Feather BLE 32u4. Support for each is defined as a hardware revision subfolder in QMK. Main differences include processor frequencies and matrix pinouts.

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

make meira/promicro:default

or

make meira/featherble:default

See build environment setup then the make instructions for more information on generic QMK configuration and setup.

Both the Pro Micro and the Feather BLE use the Catalina bootloader, which is typically programmed using avrdude.

Matrix

In order to have enough pins for the matrix and other functions, a custom matrix is implemented using a demultiplexer to scan the columns. Since the demux is active low, the diodes must be oriented with the cathode connected to the demux pin. When looking at the bottom of the board with the controller at the top right, the cathode mark on the diode should be toward the left.

LED Controller

The in-switch LEDs are driven by an ISSI LED controller (IS31FL3731). The micro controller communicates with this chip using I2C. Individual LED control is possible, but currently only general backlighting support is implemented. This functionality is located in lighting.c, issi.c, and TWILib.c.