summaryrefslogtreecommitdiffstats
path: root/doc/HAND_WIRE.md
diff options
context:
space:
mode:
authorJack Humbert <jack.humb@gmail.com>2016-06-22 04:39:54 +0200
committerGitHub <noreply@github.com>2016-06-22 04:39:54 +0200
commit649b33d7783cf3021928534b7ae127e0a89e8807 (patch)
treec2b5e0cf8ff4aa2918e3b88ab75dbdb071cc0a1d /doc/HAND_WIRE.md
parent464c8e274f993d3571fe5ea5e836fe55a3912ffe (diff)
downloadqmk_firmware-649b33d7783cf3021928534b7ae127e0a89e8807.tar.gz
qmk_firmware-649b33d7783cf3021928534b7ae127e0a89e8807.tar.xz
Renames keyboard folder to keyboards, adds couple of tmk's fixes (#432)
* fixes from tmk's repo * rename keyboard to keyboards
Diffstat (limited to 'doc/HAND_WIRE.md')
-rw-r--r--doc/HAND_WIRE.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/HAND_WIRE.md b/doc/HAND_WIRE.md
index 073dbf447..bb3683cb9 100644
--- a/doc/HAND_WIRE.md
+++ b/doc/HAND_WIRE.md
@@ -185,13 +185,13 @@ From here, you should have a working keyboard with the correct firmware. Before
To start out, download [the firmware](https://github.com/jackhumbert/qmk_firmware/) - we'll be using my (Jack's) fork of TMK called QMK/Quantum. We'll be doing a lot from the Terminal/command prompt, so get that open, along with a decent text editor like [Sublime Text](http://www.sublimetext.com/).
-The first thing we're going to do is create a new project using the script in the root directory of the firmware. In your terminal, run this command with `<project_name>` replaced by the name of your project - it'll need to be different from any other project in the `keyboard/` folder:
+The first thing we're going to do is create a new project using the script in the root directory of the firmware. In your terminal, run this command with `<project_name>` replaced by the name of your project - it'll need to be different from any other project in the `keyboards/` folder:
util/new_project.sh <project_name>
-You'll want to navigate to the `keyboard/<project_name>/` folder by typing, like the print-out from the script specifies:
+You'll want to navigate to the `keyboards/<project_name>/` folder by typing, like the print-out from the script specifies:
- cd keyboard/<project_name>
+ cd keyboards/<project_name>
#### config.h
@@ -286,7 +286,7 @@ After you've written out your entire keymap, you're ready to get the firmware co
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.
-Once you have your `<project_name>.hex` file, open up the Teensy loader application, and click the file icon. From here, navigate to your `QMK/keyboard/<project_name>/` folder, and select the `<project_name>.hex` file. Plug in your keyboard and press the button on the Teensy - you should see the LED on the device turn off once you do. The Teensy Loader app will change a little, and the buttons should be clickable - click the download button (down arrow), and then the reset button (right arrow), and your keyboard should be ready to go!
+Once you have your `<project_name>.hex` file, open up the Teensy loader application, and click the file icon. From here, navigate to your `QMK/keyboards/<project_name>/` folder, and select the `<project_name>.hex` file. Plug in your keyboard and press the button on the Teensy - you should see the LED on the device turn off once you do. The Teensy Loader app will change a little, and the buttons should be clickable - click the download button (down arrow), and then the reset button (right arrow), and your keyboard should be ready to go!
#### Testing your firmware