summaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorDaveHodder67 <dave.hodder@focusrite.com>2015-07-03 17:20:57 +0100
committerDaveHodder67 <dave.hodder@focusrite.com>2015-07-03 17:20:57 +0100
commit038b8dd27c08a6998ee93859820d642c0667df94 (patch)
tree18c6c41c810184575e5b87879ed9672cccdcbf93 /README.md
parent0490d1460a3c45d02090e59e6498471b68987f2c (diff)
downloadlaunchpad-polymaker-038b8dd27c08a6998ee93859820d642c0667df94.tar.gz
launchpad-polymaker-038b8dd27c08a6998ee93859820d642c0667df94.zip
more readme tips
Diffstat (limited to 'README.md')
-rw-r--r--README.md7
1 files changed, 3 insertions, 4 deletions
diff --git a/README.md b/README.md
index 15f3ac6..f23a6cc 100644
--- a/README.md
+++ b/README.md
@@ -29,7 +29,7 @@ This project uses [Vagrant](https://www.vagrantup.com/) to manage the build envi
294. Open a command prompt, and navigate to the project directory 294. Open a command prompt, and navigate to the project directory
305. Type `vagrant up`, hit enter and grab a beverage of your choice. Maybe two - it is building a lovely fresh development machine just for you! 305. Type `vagrant up`, hit enter and grab a beverage of your choice. Maybe two - it is building a lovely fresh development machine just for you!
31 31
32Note that it does take quite a while to download everything. If you have a poor internet connection, ummm, find a better one :) 32If you have a poor internet connection, ummm, find a better one :)
33 33
34# Building 34# Building
35Once your new "box" is up and running, you can build the app in one of two ways. In the spirit of experimentation, we've created a full Eclipse development environment for you to use. However, you might prefer to do things on the command line. 35Once your new "box" is up and running, you can build the app in one of two ways. In the spirit of experimentation, we've created a full Eclipse development environment for you to use. However, you might prefer to do things on the command line.
@@ -54,7 +54,7 @@ Make sure you wait until the `vagrant up` command has completed before logging i
5410. Select your project by clicking on it. 5410. Select your project by clicking on it.
5511. Click the hammer icon at the top, and wait while the project builds. 5511. Click the hammer icon at the top, and wait while the project builds.
56 56
57Either of the above methods will generate the firmware image, `launchpad_pro.syx`, in the project /build directory. You can then upload this to your Launchpad Pro from the host! 57Either of the above methods will generate the firmware image, `launchpad_pro.syx`, in the project `build` directory. You can then upload this to your Launchpad Pro from the host!
58 58
59# Uploading to a Launchpad Pro 59# Uploading to a Launchpad Pro
60Now you've got some nice new code to run! To upload it to your Launchpad Pro, you'll need a sysex tool for your host platform (I'd love to get it working from the virtual machine, but that's for later). I recommend [Sysex Librarian](http://www.snoize.com/SysExLibrarian/) on OS X, and [MIDI OX](http://www.midiox.com/) on Windows. On Linux, I'll bet you already have a tool in mind. 60Now you've got some nice new code to run! To upload it to your Launchpad Pro, you'll need a sysex tool for your host platform (I'd love to get it working from the virtual machine, but that's for later). I recommend [Sysex Librarian](http://www.snoize.com/SysExLibrarian/) on OS X, and [MIDI OX](http://www.midiox.com/) on Windows. On Linux, I'll bet you already have a tool in mind.
@@ -100,7 +100,6 @@ If you only want to build using the command line, you might want to run your Vag
100 100
101If prefer, you can install the gcc-arm toolchain on your local machine, or you might already have it. You can find all you need [here](http://gnuarmeclipse.livius.net/). 101If prefer, you can install the gcc-arm toolchain on your local machine, or you might already have it. You can find all you need [here](http://gnuarmeclipse.livius.net/).
102 102
103
104
105It appears that VirtualBox does not yet work on Windows 10. 103It appears that VirtualBox does not yet work on Windows 10.
106 104
105If your connection drops out while updating the Vagrant box, you can get stuck, unable to `vagrant up`. To resolve, you need to delete the temp file - `~/vagrant.d/tmp`. \ No newline at end of file