keychron_qmk_firmware/keyboards/0xcb/splaytoraid
2024-08-26 07:51:22 +10:00
..
32u4 0xcb/splaytoraid: remove CONVERT_TO at keyboard level (#23395) 2024-04-02 15:37:11 +01:00
keymaps/default Remove all via-enabled keymaps, including via. (#24322) 2024-08-26 07:51:22 +10:00
rp2040_ce 0xcb/splaytoraid: remove CONVERT_TO at keyboard level (#23395) 2024-04-02 15:37:11 +01:00
info.json 0xcb/splaytoraid: remove CONVERT_TO at keyboard level (#23395) 2024-04-02 15:37:11 +01:00
readme.md
rules.mk

splaytoraid

splaytoraid

A 40% ergonomic keyboard with a stacked acrylic case and RGB underglow.

  • Keyboard Maintainer: freya
  • Hardware Supported: PCB kit and Pro Micro compatible controller
  • Hardware Availability: here

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

make 0xcb/splaytoraid:default
make 0xcb/splaytoraid/32u4:default

Flashing example for this keyboard:

make 0xcb/splaytoraid:default:flash
make 0xcb/splaytoraid/32u4: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 left top 4. col key (usually Escape) and plug in the keyboard
  • Physical reset button: Press the button on the controller (Helios) for more than 500ms or just press it (Pluto)
  • Keycode in layout: Press the key mapped to QK_BOOT if it is available

Please note that the default bootloader for the 32u4 version is QMK DFU, for compatibility with 0xCB Pluto. Generic Pro Micros often use a different bootloader, such as caterina.

If the incorrect bootloader is specified, bootmagic reset and the QK_BOOT keycode will not work.

To avoid this problem, set the correct bootloader in your custom keymap's rules.mk file before compiling, or flash using an appropriate target (ex: make 0xcb/splaytoraid/32u4:default:avrdude). See flashing instructions and bootloader information for more details.