qmk_firmware/keyboards/meira
Zach White d02c4c5241
Add a <FEATURE>_SUPPORTED flag (#9058)
* Initial attempt at allowing keyboards to indicate what features they do not support

* try to use a for loop instead

* Update disable_features.mk

Co-authored-by: Drashna Jaelre <drashna@live.com>

* add a few more features

* remove my test fixture

* disable things that make all:all suggested"

Co-authored-by: Zach White <skullydazed@users.noreply.github.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
2021-01-30 13:08:58 -08:00
..
featherble Remove `MIDI_ENABLE_STRICT` from keyboards' config.h (#11679) 2021-01-27 17:26:26 +11:00
keymaps
promicro Add a <FEATURE>_SUPPORTED flag (#9058) 2021-01-30 13:08:58 -08:00
TWIlib.c Normalise include statements in keyboard code (#11185) 2020-12-16 14:27:23 +11:00
TWIlib.h Fix TWIlib compilation on avr-gcc 10 (#9273) 2020-09-17 10:45:07 +10:00
config.h Remove `DESCRIPTION`, K-M (#11619) 2021-01-20 09:56:41 +11:00
issi.c
issi.h
lighting.c Normalise include statements in keyboard code (#11185) 2020-12-16 14:27:23 +11:00
lighting.h
matrix.c
meira.c
meira.h
readme.md
rules.mk

readme.md

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.