aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEric Tang <e_l_tang@outlook.com>2016-06-06 18:53:37 -0700
committerJack Humbert <jack.humb@gmail.com>2016-06-06 21:53:37 -0400
commit219e4a3012baeeb301b57b97c1b274458f124ac2 (patch)
treefb3077a4c6e2e1e9f48a4849c8daee89a46622da /doc
parent408c9e159b88161f660886f9697ed4ddd8fdff00 (diff)
downloadqmk_firmware-219e4a3012baeeb301b57b97c1b274458f124ac2.tar.gz
qmk_firmware-219e4a3012baeeb301b57b97c1b274458f124ac2.zip
Fix hand wiring guide (#387)
* Fix broken link * Fix incoherent sentence
Diffstat (limited to 'doc')
-rw-r--r--doc/HAND_WIRE.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/HAND_WIRE.md b/doc/HAND_WIRE.md
index 704930a53..f5dfc0753 100644
--- a/doc/HAND_WIRE.md
+++ b/doc/HAND_WIRE.md
@@ -195,7 +195,7 @@ You'll want to navigate to the `keyboard/<project_name>/` folder by typing, like
195 195
196#### config.h 196#### config.h
197 197
198The first thing you're going to want to modify is the `config.h` file. Find `MATRIX_ROWS` and `MATRIX_COLS` and them to match the dimensions of your keyboard's matrix. 198The first thing you're going to want to modify is the `config.h` file. Find `MATRIX_ROWS` and `MATRIX_COLS` and change their definitions to match the dimensions of your keyboard's matrix.
199 199
200Farther down are `MATRIX_ROW_PINS` and `MATRIX_COL_PINS`. Change their definitions to match how you wired up your matrix (looking from the top of the keyboard, the rows run top-to-bottom and the columns run left-to-right). Likewise, change the definition of `UNUSED_PINS` to match the pins you did not use (this will save power). 200Farther down are `MATRIX_ROW_PINS` and `MATRIX_COL_PINS`. Change their definitions to match how you wired up your matrix (looking from the top of the keyboard, the rows run top-to-bottom and the columns run left-to-right). Likewise, change the definition of `UNUSED_PINS` to match the pins you did not use (this will save power).
201 201
@@ -282,7 +282,7 @@ It's also important to use the `KEYMAP` function we defined earlier - this is wh
282 282
283#### Compiling your firmware 283#### Compiling your firmware
284 284
285After you've written out your entire keymap, you're ready to get the firmware compiled and onto your Teensy. Before compiling, you'll need to get your [development environment set-up](https://github.com/jackhumbert/qmk_firmware/blob/master/keyboard/planck/PCB_GUIDE.md#setting-up-the-environment) - you can skip the dfu-programmer instructions, but you'll need to download and install the [Teensy Loader](https://www.pjrc.com/teensy/loader.html) to get the firmware on your Teensy. 285After you've written out your entire keymap, you're ready to get the firmware compiled and onto your Teensy. Before compiling, you'll need to get your [development environment set-up](./BUILD_GUIDE.md) - you can skip the dfu-programmer instructions, but you'll need to download and install the [Teensy Loader](https://www.pjrc.com/teensy/loader.html) to get the firmware on your Teensy.
286 286
287Once everything is installed, running `make` in the terminal should get you some output, and eventually a `<project_name>.hex` file in that folder. If you're having trouble with this step, see the end of the guide for the trouble-shooting section. 287Once everything is installed, running `make` in the terminal should get you some output, and eventually a `<project_name>.hex` file in that folder. If you're having trouble with this step, see the end of the guide for the trouble-shooting section.
288 288