b05c0e46c6
* Add default value for IS_COMMAND for COMMAND feature * Cleanup and consistency * Update Templates to reflect change * Fix IS_COMMAND in template * Fix IS_COMMAND define * Use consistent IS_COMMAND block in templates * Remove unnecessary `#undef IS_COMMAND` directives * Fix compile issue on orthodox * Reomve IS_COMMAND option for newer boards * Remove all existing definitions of IS_COMMAND if they use default LSHIFT and RSHIFT setting * Remove a couple of additional IS_COMMAND defines * Remove remaining redundant IS_COMMAND definitions * Remove #undef IS_COMMAND from orthodox:drashna and whitefox:konstantin * Remove multiple empty lines in modified config.h files * Update additional boards * Reomve IS_COMMAND from newer boards * Update Alice keyboard * Remove IS_COMMAND from additional boards Jan 24th edition |
||
|---|---|---|
| .. | ||
| keymaps | ||
| tools | ||
| backlight_custom.h | ||
| backlight.c | ||
| breathing_custom.h | ||
| config.h | ||
| i2c.c | ||
| i2c.h | ||
| matrix.c | ||
| program | ||
| README.md | ||
| rules.mk | ||
| usbconfig.h | ||
| ymd96.c | ||
| ymd96.h | ||
YMD96
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.
A very big thanks to @krusli for making the RGB underglow, Backlight, CapsLock and NumLock LEDs working correctly.
Finding your specific matrix
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:
- Follow the guide here to get Bootmapper Client setup. While you won't need it after you get qmk working, you need to use Bootmapper Client to figure out how the matrix is laid out. In the end, here's an example of what it should look like:
- Next is the tricky part: editing the
ymd96.hfile. 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. - First, you need to define the codes that are actually used in the brackets. KC_NO is used whenever a cell isn't used, such as col 1 row 4-6 in BMC.
- Once you have all those set up, you need to put the keycodes where they physically are in the KEYMAP( area. Since the columns aren't all uniform (e.g. col2row6 is B, but col2row7 is the numpad 1), the keycodes will be all over the place.
- Finally! Hard part is pretty much done. Next, you simply have to edit the
keymap.cfile 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!
Installing and Building
Since the YMD96 uses an ATmega32a chip instead of the 32u4, you need to download HIDBootFlash v.1.0 for Windows. For Linux you can use the bootloadHID utility (which will require building). Arch Linux users can alternatively install this from the AUR. On Windows, I use MINGw to compile the keymaps. On Linux, you can simply use the terminal.
Once you have those two pieces of software: Build the keyboard by navigating to the root folder of the QMK repo and running
$ make ymd96:default
If you make your own layout, change the default word to whatever your layout is.
To flash the compiled hex file, simply put the board in flashing mode by plugging it in while holding control.
In HIDBootFlash first click find device, then you can specify the .hex file and flash it to the device.
For bootloadHID, from a terminal that is in the same folder as your firmware file, run
$ sudo bootloadHID ymd96_default.hex
Again replacing default with your custom keymap name if required.
Troubleshooting
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.
- Try plugging the board in while pressing
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. - Sometimes USB hubs can act weird, so try connecting the board directly to your computer or plugging/unplugging the USB hub.
Lastly, if you still need help, you can add me on Discord and I'll be happy to help.