summaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorDaveHodder67 <dave.hodder@focusrite.com>2015-08-13 18:19:29 +0100
committerDaveHodder67 <dave.hodder@focusrite.com>2015-08-13 18:19:29 +0100
commit8504fff60d88ed1205c7c1f9df6018cdaee771a4 (patch)
tree056ce4b862ffee84e04aff081a833edcd7495061 /README.md
parentd43a3275cccbdbb578866ab117118712bc612dc6 (diff)
downloadlaunchpad-polymaker-8504fff60d88ed1205c7c1f9df6018cdaee771a4.tar.gz
launchpad-polymaker-8504fff60d88ed1205c7c1f9df6018cdaee771a4.zip
improved debugging docs for OS X and a factory Launchpad Pro
Diffstat (limited to 'README.md')
-rw-r--r--README.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/README.md b/README.md
index 322fef1..c22b331 100644
--- a/README.md
+++ b/README.md
@@ -99,9 +99,10 @@ If do you want to debug interactively (and of course you do), you can use the in
991. Build the Xcode project located in `/tools/osx` 991. Build the Xcode project located in `/tools/osx`
1002. Connect your Launchpad Pro 1002. Connect your Launchpad Pro
1013. Install the factory firmware on your Launchpad Pro 1013. Install the factory firmware on your Launchpad Pro
1024. Debug away! 1024. Put the Launchpad Pro into "Programmer" mode using the Setup button (you'll get odd behaviour otherwise)
1035. Start debugging in Xcode!
103 104
104Currently it only supports button presses and LED messages - there's no virtual MIDI IO or aftertouch (yet). It has a really awful busywaiting timer for the 1kHz tick. However, it does allow you to debug your application logic using Xcode! 105Currently it only supports button presses and LED messages - there's no virtual MIDI IO, setup button or aftertouch (yet). It has a really awful busywaiting timer for the 1kHz tick. However, it does allow you to debug your application logic using Xcode!
105 106
106You can also use the simple command-line simulator located in the `/tools` directory. It is compiled and ran as part of the build process, so it serves as a very basic test of your app before it is baked into a sysex dump - more of a test harness. 107You can also use the simple command-line simulator located in the `/tools` directory. It is compiled and ran as part of the build process, so it serves as a very basic test of your app before it is baked into a sysex dump - more of a test harness.
107 108