History

Migrate LOCKING_*_ENABLE to Data-Driven: A-C, Part 2 (#23746 )

Affects:

  - `chalice`
  - `charue/sunsetter_r2`
  - `checkerboards/axon40`
  - `checkerboards/candybar_ortho`
  - `checkerboards/g_idb60`
  - `checkerboards/nop60`
  - `checkerboards/phoenix45_ortho`
  - `checkerboards/plexus75`
  - `checkerboards/plexus75_he`
  - `checkerboards/pursuit40`
  - `checkerboards/quark`
  - `checkerboards/quark_lp`
  - `checkerboards/quark_plus`
  - `checkerboards/quark_squared`
  - `checkerboards/snop60`
  - `checkerboards/ud40_ortho_alt`
  - `cheshire/curiosity`
  - `chickenman/ciel`
  - `chlx/merro60`
  - `chlx/str_merro60`
  - `chosfox/cf81`
  - `citrus/erdnuss65`
  - `ckeys/handwire_101`
  - `ckeys/nakey`
  - `ckeys/obelus`
  - `ckeys/thedora`
  - `ckeys/washington`
  - `clueboard/2x1800/2018`
  - `clueboard/2x1800/2021`

2024-05-20 21:00:35 +01:00

keymaps/default

…

keyboard.json

Migrate LOCKING_*_ENABLE to Data-Driven: A-C, Part 2 (#23746 )

2024-05-20 21:00:35 +01:00

readme.md

…

readme.md

naKey

Firmware for custom keyboard

Keyboard Maintainer: James Underwood
Hardware Supported: naKey
Hardware Availability: ckeys.org

To build this keyboard, follow the build guide.

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

make ckeys/nakey:default

See build environment setup then the make instructions for more information.

Quantum MK Firmware

For the full Quantum feature list, see the parent readme.

Building

Download or clone the whole firmware and navigate to the root folder. Once your dev env is setup, you'll be able to type make ckeys/nakey:default to generate your .hex - you can then use the Teensy Loader to program your .hex file.

(Note: replace naKey with the name of your keyboard.)

Depending on which keymap you would like to use, you will have to compile slightly differently.

Default

To build with the default keymap, simply run make ckeys/nakey:default.

Other Keymaps

Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create a folder with the name of your keymap in the keymaps folder. Create a readme.md and a keymap.c file to complete your new keymap. When you are done your file tree should look like this:

qmk_firmware/
- keyboard/
  - keymaps/
    - config.h (optional)
    - keymap.c
    - readme.md
    - rules.mk (optional)

To build the firmware binary hex file with a keymap just do make with a keymap like this:

$ make naKey-[default|jack|<name>]