forked from forks/qmk_firmware
Updates ErgoDox readme
This commit is contained in:
parent
f422f442cf
commit
56aa51664e
|
@ -2,12 +2,10 @@
|
||||||
|
|
||||||
There are two main ways you could customize the ErgoDox (EZ and Infinity)
|
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
|
## The Easy Way: Use an existing firmware file and just flash it (ErgoDox EZ only)
|
||||||
|
|
||||||
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](https://www.pjrc.com/teensy/loader.html). Some Linux distributions already provide a binary (may be called `teensy-loader-cli`), so you may prefer to use this.
|
1. Download and install the [Teensy Loader](https://www.pjrc.com/teensy/loader.html). 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](https://keyboard-configurator.massdrop.com/ext/ergodox) to create a firmware Hex file you like.
|
2. Find a firmware file you like. There are [dozens of community-contributed keymaps](http://qmk.fm/keyboards/ergodox/) you can browse and download. You can also use the [Massdrop configurator](https://keyboard-configurator.massdrop.com/ext/ergodox) to create a firmware Hex file you like.
|
||||||
3. Download the firmware file
|
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.
|
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.
|
||||||
|
|
||||||
|
@ -18,8 +16,7 @@ If you are just compiling an existing keymap and don't want to create your own,
|
||||||
|
|
||||||
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 :)
|
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)
|
2. Clone the repository (download it)
|
||||||
3. Set up a build environment as per [the build guide](/doc/BUILD_GUIDE.md)
|
3. Set up a build environment as per the readme.
|
||||||
- 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`)
|
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.
|
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.
|
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.
|
||||||
|
@ -32,7 +29,7 @@ Good luck! :)
|
||||||
|
|
||||||
## Contributing your keymap
|
## 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.
|
The QMK firmware is open-source, so it would be wonderful to have your contribution! Within a very short time after launching we already amassed dozens of 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).
|
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.
|
2. `keymap.c` - this is your actual keymap file; please update the ASCII comments in the file so they correspond with what you did.
|
||||||
|
|
Loading…
Reference in a new issue