diff options
| author | DaveHodder67 <dave.hodder@focusrite.com> | 2015-07-06 14:35:55 +0100 |
|---|---|---|
| committer | DaveHodder67 <dave.hodder@focusrite.com> | 2015-07-06 14:35:55 +0100 |
| commit | 010601571f334328f6f08625857df8444fb65d1c (patch) | |
| tree | 2f63a0c7bd5bee91f0b24f56d9b516c52d49e409 /README.md | |
| parent | 038b8dd27c08a6998ee93859820d642c0667df94 (diff) | |
| download | launchpad-polymaker-010601571f334328f6f08625857df8444fb65d1c.tar.gz launchpad-polymaker-010601571f334328f6f08625857df8444fb65d1c.zip | |
improved readme
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 9 |
1 files changed, 7 insertions, 2 deletions
| @@ -64,9 +64,11 @@ I won't describe how to use these tools, I'm sure you already know - and if you | |||
| 64 | 1. Unplug your Launchpad Pro | 64 | 1. Unplug your Launchpad Pro |
| 65 | 2. Hold the "Setup" button down while connecting it to your host via USB (ensure it's connected to the host, and not to a virtual machine!) | 65 | 2. Hold the "Setup" button down while connecting it to your host via USB (ensure it's connected to the host, and not to a virtual machine!) |
| 66 | 3. The unit will start up in "bootloader" mode | 66 | 3. The unit will start up in "bootloader" mode |
| 67 | 4. Send your launchpad_pro.syx file to the device MIDI port - it should briefly scroll "updating..." across the grid. | 67 | 4. Send your launchpad_pro.syx file to the device MIDI port - it will briefly scroll "upgrading..." across the grid. |
| 68 | 5. Wait for the update to complete, and for the device to reboot! | 68 | 5. Wait for the update to complete, and for the device to reboot! |
| 69 | 69 | ||
| 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 | |||
| 70 | # Bricked it! | 72 | # Bricked it! |
| 71 | 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 :) |
| 72 | 74 | ||
| @@ -102,4 +104,7 @@ If prefer, you can install the gcc-arm toolchain on your local machine, or you m | |||
| 102 | 104 | ||
| 103 | It appears that VirtualBox does not yet work on Windows 10. | 105 | It appears that VirtualBox does not yet work on Windows 10. |
| 104 | 106 | ||
| 105 | If 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 | 107 | If 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`. |
| 108 | |||
| 109 | # Firmware development tips | ||
| 110 | OK - we're not going to need to use the MISRA rules, but there are a few things to avoid. Dynamic memory allocation is a no (well it will work, but it's best avoided). Floating point will work, but it's implemented in software and will be slooooow. C++ ought to work, but you'll definitely want to avoid exceptions and RTTI! \ No newline at end of file | ||