diff options
| author | Jack Humbert <jack.humb@gmail.com> | 2016-06-06 21:54:21 -0400 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2016-06-06 21:54:21 -0400 |
| commit | 2222621b55768702ab7f0eb9c0276357f8eaa6bc (patch) | |
| tree | 4f84fc67854b2257fbb2ffad21bc37dfa5ed528f /doc | |
| parent | 219e4a3012baeeb301b57b97c1b274458f124ac2 (diff) | |
| download | qmk_firmware-2222621b55768702ab7f0eb9c0276357f8eaa6bc.tar.gz qmk_firmware-2222621b55768702ab7f0eb9c0276357f8eaa6bc.zip | |
Update HAND_WIRE.md
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/HAND_WIRE.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/HAND_WIRE.md b/doc/HAND_WIRE.md index f5dfc0753..073dbf447 100644 --- a/doc/HAND_WIRE.md +++ b/doc/HAND_WIRE.md | |||
| @@ -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 | ||
| 285 | After 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. | 285 | After 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](/doc/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 | ||
| 287 | Once 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. | 287 | Once 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 | ||
