Set up your computer
Install the compilers and tools, build a firmware, flash it.
Write your own effect in plain C: your sound, your screen, your controls. Try it on your computer first, then flash it over USB.
| The simulator | the whole firmware on the computer: sound, screen, scripted controls |
| Parameters and presets | settings declared once, saved, and editable from a computer |
| The UI kit | a settings page, a menu, value text, messages |
| Text and fonts | the built-in pixel font, smooth text, your own font |
| Storage | keeping settings and files on the pedal |
| The audio link | sound on both processors |
| Performance | budgets, measuring, what’s fast where |
| Debugging | the log, the load report, symptoms and causes |
| Releasing your firmware | versions, release notes, getting listed |
| API reference | everything a firmware can use |
| Protocols | USB-MIDI, the firmware update, the image format, the processor link |
| Hardware | memory, pins and clocks of both processors |
| Known limits | what it can’t do yet |
| FAQ | common questions |
Install the compilers and tools, build a firmware, flash it.
The two processors, the platform, settings, storage, and what happens at power-on.
Build a tremolo step by step: settings, sound, screen and controls.
Start a firmware from the template: its own repository, built and tested on every push.
Run a whole firmware on the computer: sound, screen and scripted controls.
Declare settings once; the platform saves them, keeps presets and gives a computer an editor.
A settings page, a menu, value text, messages and knob pickup.
The built-in pixel font, smooth text in any font, and making your own.
Keeping settings and files on the pedal.
Sound on both processors.
Budgets, measuring, and what’s fast on each processor.
The log, the load report, symptoms and their causes.
Versions, release notes, and getting listed in Launchpad and the web flasher.
Everything a firmware can use: manifest, callbacks, platform calls, log, load.
USB-MIDI, the firmware update, the image format, and the link between the processors.
Memory, pins and clocks of both processors.
What OpenGP5 can’t do (yet).
Common questions about using OpenGP5 and writing firmware.