diff options
| author | DaveHodder67 <dave.hodder@focusrite.com> | 2015-08-13 13:54:26 +0100 |
|---|---|---|
| committer | DaveHodder67 <dave.hodder@focusrite.com> | 2015-08-13 13:54:26 +0100 |
| commit | bd1f984b05ed156fc5c64fea5416b4fe48c3d491 (patch) | |
| tree | 484c52503daf45d2eec1b6138f2acd15de8c9fca /README.md | |
| parent | 04e2b3c71bec78ccbc8732d24de86a3f37372c28 (diff) | |
| download | launchpad-polymaker-bd1f984b05ed156fc5c64fea5416b4fe48c3d491.tar.gz launchpad-polymaker-bd1f984b05ed156fc5c64fea5416b4fe48c3d491.zip | |
improved formatting
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 7 |
1 files changed, 4 insertions, 3 deletions
| @@ -70,7 +70,7 @@ I won't describe how to use these tools, I'm sure you already know - and if you | |||
| 70 | Tip - set the delay between sysex messages to as low a value as possible, so you're not waiting about for ages while the firmware uploads! | 70 | Tip - set the delay between sysex messages to as low a value as possible, so you're not waiting about for ages while the firmware uploads! |
| 71 | 71 | ||
| 72 | # Bricked it! | 72 | # Bricked it! |
| 73 | Don't worry - even if you upload toxic nonsense to the device, you cannot brick it - the bootloader is stored in a protected area of flash. If your new firmware doesn't boot, you'll get stuck at step (3) above, or with a crashed unit. Simply repeat the above process with the shipping firmware image (resources/Launchpad Pro-1.0.154.syx) to restore your unit to the factory defaults. Better yet, fix the bugs :) | 73 | Don't worry - even if you upload toxic nonsense to the device, you cannot brick it - the bootloader is stored in a protected area of flash. If your new firmware doesn't boot, you'll get stuck at step (3) above, or with a crashed unit. Simply repeat the above process with the shipping firmware image (`resources/Launchpad Pro-1.0.154.syx`) to restore your unit to the factory defaults. Better yet, fix the bugs :) |
| 74 | 74 | ||
| 75 | # The API | 75 | # The API |
| 76 | The API works in two directions - from the HAL (hardware abstraction layer) to the app, and from the app to the HAL. The HAL calls into your app to: | 76 | The API works in two directions - from the HAL (hardware abstraction layer) to the app, and from the app to the HAL. The HAL calls into your app to: |
| @@ -78,13 +78,14 @@ The API works in two directions - from the HAL (hardware abstraction layer) to t | |||
| 78 | - Receive user events from the pads and buttons | 78 | - Receive user events from the pads and buttons |
| 79 | - Receive messages from the MIDI/USB ports | 79 | - Receive messages from the MIDI/USB ports |
| 80 | - Receive a tick message to drive timer based code | 80 | - Receive a tick message to drive timer based code |
| 81 | - Be notified when someone connects or disconnects a MIDI cable | ||
| 81 | 82 | ||
| 82 | By calling into the HAL, your app can | 83 | By calling into the HAL, your app can: |
| 83 | 84 | ||
| 84 | - Write colours to the LEDs | 85 | - Write colours to the LEDs |
| 85 | - Send messages to the MIDI/USB ports | 86 | - Send messages to the MIDI/USB ports |
| 86 | 87 | ||
| 87 | The best way to learn about these is to read the documentation in app.h, and to study the (very basic) example code! | 88 | The best way to learn about these is to read the documentation in `app.h`, and to study the (very basic) example code! |
| 88 | 89 | ||
| 89 | Currently the HAL/app interface does not support reading or writing the flash memory. | 90 | Currently the HAL/app interface does not support reading or writing the flash memory. |
| 90 | 91 | ||