Jack Humbert 9fdc276260 | 6 years ago | |
---|---|---|
.. | ||
keymaps/default | 6 years ago | |
README.md | 6 years ago | |
config.h | 6 years ago | |
i2c.c | 6 years ago | |
i2c.h | 6 years ago | |
matrix.c | 6 years ago | |
program | 6 years ago | |
rules.mk | 6 years ago | |
usbconfig.h | 6 years ago | |
ymd96.c | 6 years ago | |
ymd96.h | 6 years ago |
This is a port of the QMK firmware for boards that are based on the ps2avrGB firmware, like the ps2avrGB keyboard, for use on the YMD96.
Note that this is a complete replacement for the firmware, so you won't be using Bootmapper Client to change any keyboard settings, since not all the USB report options are supported.
Here is the default layout, it is fairly simple with a few function keys:
If you have a different layout (since there were many options during the GB), please feel free to contribute!
Keyboard maintainer: Andrew
Hardware Supported: YMD96 with the ATmega32a chip.
Hardware Availability: The GB was run June 2017, in this thread. The vendor has stated that they plan on selling more rounds.
This firmware was modified from ps2avrGB, also found on this qmk repo, to work with the YMD96 keyboard. However, I only have one board to test with, which might have a different layout than yours. To get qmk working with your specific layout, you'll need to follow these steps:
ymd96.h
file. Here, you have to figure out how the keys are laid out physically and assign each key the right keycode. Study how the codes in brackets correspond to the BMC columns. Consider the first column: K000 corresponds to Col 1 Row 1, and K100 corresponds to Col 2 Row 1. K111 = Col 2 Row 10.keymap.c
file to actually assign the keycodes to do something. You essentially replace the keycodes (e.g. K000) with actual codes that do something, e.g. KC_ENTER. Modify these to your hearts content, and of course this is where all the extra functionality of QMK shines. I won't get into it here, but hopefully you've made it this far!First, install the requirements. These commands are for OSX, but all you
need is the AVR toolchain and bootloadHID
for flashing:
$ brew cask install crosspack-avr
$ brew install --HEAD https://raw.githubusercontent.com/robertgzr/homebrew-tap/master/bootloadhid.rb
In order to use the ./program
script, which can reboot the board into
the bootloader, you'll need Python 2 with PyUSB installed:
$ pip install pyusb
Build the keyboard with
$ make ymd96:default
If you make your own layout, change the default
word to whatever your layout is.
From my experience, it's really hard to brick these boards. But these tricks have been useful when it got stuck in a weird scenario.
L_Ctrl
. This will force it
to boot only the bootloader without loading the firmware. Once this is
done, just reflash the board with the original firmware.