g1smo
/
qmk_firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
qmk_firmware/keyboards/yushakobo/navpad/10
History
Ryan 1e05bad1ba
Move `TAPPING_TERM` to data driven (#21296) 
Co-authored-by: Nick Brassel <nick@tzarc.org>
 		2023-06-24 17:44:21 +10:00
..
keymaps Remove `RGB_DI_PIN` ifdefs (#20218) 2023-03-23 21:38:01 +11:00
rev0 Move single `LAYOUT`s to data driven (#20365) 2023-04-12 13:42:51 +10:00
rev1 Move `RGBLIGHT_LED_MAP` to data driven (#21095) 2023-06-14 22:01:13 +10:00
config.h Move `TAPPING_TERM` to data driven (#21296) 2023-06-24 17:44:21 +10:00
info.json Move `TAPPING_TERM` to data driven (#21296) 2023-06-24 17:44:21 +10:00
readme.md
…
rules.mk Migrate `MCU` and `BOOTLOADER` to data-driven (#19529) 2023-02-08 18:41:46 +11:00

readme.md

navpad 1.0

navpad_10

Useful and easy to build numpad with nav-cluster

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

make yushakobo/navpad/10:default

Flashing example for this keyboard:

make yushakobo/navpad/10: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 key at (0,0) in the matrix (usually the top left key or Escape) and plug in the keyboard
  • Physical reset button: Briefly press the button on the back of the PCB - some may have pads you must short instead
  • Keycode in layout: Press the key mapped to QK_BOOT if it is available