qmk-firmware/keyboards/hineybush/h87a
Xelus22 b73a29aaea
[Bug] Develop - Change uint32_t to layer_state_t (#13596)
* fix sat75

* update uint32_t to layer_state
2021-07-19 09:50:55 -07:00
..
keymaps [Bug] Develop - Change uint32_t to layer_state_t (#13596) 2021-07-19 09:50:55 -07:00
config.h Remove DESCRIPTION, H-J (#11616) 2021-01-20 00:38:12 +11:00
h87a.c Hineybush h87a lock indicators (#8237) 2020-02-24 12:04:40 -08:00
h87a.h
info.json
readme.md
rules.mk Remove FAUXCLICKY feature (deprecated) (#11829) 2021-02-09 09:49:05 -08:00

h87a

A QMK-powered replacement PCB for custom TKL keyboards. This PCB has the same size of the b.87 PCB, while using the USB port placement and spacebar stabilizer orientation as the a.87 PCB.

Keyboard Maintainer: hineybush
Hardware Supported: h87a ver. 1.5, ver. 1.6 (normal and thin), h87alps
Hardware Availability: hineybush.com

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

 make hineybush/h87a:default

See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.

h87a hardware information

Controller: Atmega32u4

/* Column pin configuration
* col: 0   1   2   3   4   5   6   7   8   
* pin: F0  F1  F4  F5  F6  F7  C7  C6  D2
*/
 
/* Row pin configuration
* row: 0   1   2   3   4   5   6   7   8   9   10  11
* pin: B0  B1  B2  B3  D0  D1  B5  B6  D7  B4  D6  D4  (Rev 1)
*/

The H87a PCB utilizes duplex matrix organization.

Caps Lock LED: D5
Scroll Lock LED: E6
Num Lock LED: not supported
Backlight Pin: B7
RGB Data Pin: D3

For ver 1.5 in-switch indicators: To connect the Caps Lock LED to the main backlight matrix, jump the middle pad and the left pad on J1. To use the Caps Lock LED as an indicator, jump the middle pad and the right pad on J1.

To connect the Scroll Lock LED to the main backlight matrix, jump the middle pad and the right pad on J2. To use the Scroll Lock LED as an indicator, jump the middle pad and the left pad on J2.

Note: The different orientations of J1 and J2 was fixed with ver. 1.6.