45fd373661
* fixup: update Vial keymaps per upstream reqs more keycodes renamed `rgb_matrix_indicators_user` return type switched to bool keymaps/encoder maps that exceeded DYNAMIC_KEYMAP_LAYER_COUNT had excess layers removed EOL spaces and backslashes removed from keymaps * fixup: DRIVER_LED_TOTAL --> RGB_MATRIX_LED_COUNT * fixup: Vial-exclusive keyboard configs * fixup: 42keebs rules * fixup: relocated Vial keymaps * fixup: cleanup post-keymap move Remove wavtype/p01_ultra keymaps that went into QMK under different names Fix handwired/misterdeck and 4pplet/waffling60/rev_c keymaps * fixup: Vial-exclusive default keymaps * fixup: remove broken via-only keymaps compiling VIA keymaps is not supported anyway * fixup: non-compiling Vial keymaps * refactor: changes from QMK PR, fix Vial keymap
Idobao x YMDK ID75
A 75-key, 5-row ortholinear keyboard with per-key and underglow RGB LEDs.
- Keyboard Maintainer: The QMK Community
- Hardware Supported: Idobao x YMDK ID75 PCB (APM32F103CBT6)
- This PCB uses an ARM Cortex-M3 MCU with 128kb flash. It is not the same as
idobao/id75orymdk/ymd75.
- This PCB uses an ARM Cortex-M3 MCU with 128kb flash. It is not the same as
- Hardware Availability: YMDK, AliExpress (YMDK Store), Amazon
Make example for this keyboard (after setting up your build environment):
make ymdk/id75:default
Flashing example for this keyboard:
make ymdk/id75:default:flash
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.
Bootloader
Enter the bootloader in 3 ways:
- Bootmagic reset: Hold down the top left key and plug in the keyboard. This will also clear the emulated EEPROM, so it is a good first step if the keyboard is misbehaving.
- Physical reset button: Press the button on the back of the PCB twice in quick succession.
- Keycode in layout: Press the key mapped to
QK_BOOT. In the pre-supplied keymaps it is on the second layer, in the bottom-right corner.
After entering the bootloader through one of the three methods above, the keyboard will appear as a USB mass storage device named MT.KEY. If the CLI is unable to find this device, the compiled .uf2 file can be manually copied to it. The keyboard will reboot on completion with the new firmware loaded.