tudattr
/
qmk_firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
qmk_firmware/keyboards/ergodox
History
Gergely Nagy 8a9bf1f165 Update some obsolete references 
Some links were still pointing to `/keyboards/ergodox_ez`, while the
directory is `/keyboards/erdogox` now.

Not all references have been updated, and some of the text here and
there may need updating to mention the ErgoDox Infinity too, but that's
out of the scope for this quick fix.

Signed-off-by: Gergely Nagy <algernon@madhouse-project.org>
 		2016-07-30 08:37:30 +02:00
..
ez Move Ergodox readme from ez subfolder to parent 2016-07-29 21:09:37 +03:00
infinity Small fix for infinity include guard 2016-07-29 21:09:42 +03:00
keymaps Update some obsolete references 2016-07-30 08:37:30 +02:00
Makefile
…
config.h
…
ergodox.c
…
ergodox.h
…
readme.md Fix typo in the readme. 2016-07-29 21:09:41 +03:00

readme.md

Getting started

There are two main ways you could customize the ErgoDox (EZ and Infinity)

The Easy Way: Use an existing firmware file and just flash it

This does not work for Infinity ErgoDox yet, you need to compile the firmware according to the instructions below

  1. Download and install the Teensy Loader. Some Linux distributions already provide a binary (may be called teensy-loader-cli), so you may prefer to use this.
  2. Find a firmware file you like. You can find a few of these in the keymaps subdirectory right here. The file you need ends with .hex, and you can look at its .c counterpart (or its PNG image) to see what you'll be getting. You can also use the Massdrop configurator to create a firmware Hex file you like.
  3. Download the firmware file
  4. Connect the keyboard, press its Reset button (gently insert a paperclip into the hole in the top-right corner) and flash it using the Teensy loader you installed on step 1 and the firmware you downloaded.

More technical: compile an existing keymap, or create your own totally custom firmware by editing the source files.

This requires a little bit of familiarity with coding. If you are just compiling an existing keymap and don't want to create your own, you can skip step 4, 5 and 8.

  1. Go to https://github.com/jackhumbert/qmk_firmware and read the readme at the base of this repository, top to bottom. Then come back here :)

  2. Clone the repository (download it)

  3. Set up a build environment as per the build guide

    • Using a Mac and have homebrew? just run brew tap osx-cross/avr && brew install avr-libc

  4. Copy keyboards/ergodox/keymaps/default/keymap.c into keymaps/your_name/keymap.c (for example, keymaps/german/keymap.c)

  5. Edit this file, changing keycodes to your liking (see "Finding the keycodes you need" below). Try to edit the comments as well, so the "text graphics" represent your layout correctly. See below for more tips on sharing your work.

  6. Compile your firmware by running make keymap=keymap_name. For example, make keymap=german. This will result in a hex file, which will be called ergodox_ez_keymap_name.hex, e.g. ergodox_ez_german.hex. For Infinity ErgoDox you need to add subproject=infinity to the make command.

  7. ErgoDox EZ - Flash this hex file using the Teensy loader as described in step 4 in the "Easy Way" above. If you prefer you can automatically flash the hex file after successful build by running make teensy keymap=keymap_name.

    Infinity ErgoDox - Flash the firmware by running make dfu-util keymap=keymap_name subproject=infinity

  8. Submit your work as a pull request to this repository, so others can also use it. :) See below on specifics.

Good luck! :)

Contributing your keymap

The ErgoDox firmware is open-source, so it would be wonderful to have your contribution! Within a very short time after launching we already amassed almost 20 user-contributed keymaps, with all sorts of creative improvements and tweaks. This is very valuable for people who aren't comfortable coding, but do want to customize their ErgoDox. To make it easy for these people to use your layout, I recommend submitting your PR in the following format.

  1. All work goes inside your keymap subdirectory (keymaps/german in this example).
  2. keymap.c - this is your actual keymap file; please update the ASCII comments in the file so they correspond with what you did.
  3. readme.md - a readme file, which GitHub would display by default when people go to your directory. Explain what's different about your keymap, what you tweaked or how it works. No specific format to follow, just communicate what you did. :)
  4. Any graphics you wish to add. This is absolutely not a must. If you feel like it, you can use Keyboard Layout Editor to make something and grab a screenshot, but it's really not a must. If you do have graphics, your readme can just embed the graphic as a link, just like I did with the default layout.

Finding the keycodes you need

Let's say you want a certain key in your layout to send a colon; to figure out what keycode to use to make it do that, you're going to need quantum/keymap_common.h.

That file contains a big list of all of the special, fancy keys (like, being able to send % on its own and whatnot).

If you want to send a plain vanilla key, you can look up its code under doc/keycode.txt. That's where all the boring keys hang out.