A repo of information for Zoom R8 firmware development
github.comI did some LLM-assisted firmware and hardware reverse engineering and I wanted to share the results to help other folks build on it. There's documentation, examples, and a Claude skill.
Interesting. I wonder how much of it applies also to Zoom R16.
I have no plan to brick it though, so no custom functions for me.
Just taking a quick look, the R16 uses the same firmware file format, so presumably it would be relatively straightforward to start modifying it.
However, it uses a different chip: the TI DaVinci DM644x, which is an ARM9 CPU paired with a C64x+ DSP. The R8 has a C6748 DSP and no ARM processor. It would be interesting to look at how the firmware splits duties between the DSP and the ARM; if nothing else the R16 can act as a USB host, which the R8 cannot do (at least not easily), which means you could probably get it to be USB MIDI host and start plugging in controllers.
I'm not sure I'm ready to drop a few hundred dollars on a R16 just yet, but if I do and I build anything with it I'll be sure to share it.
As an aside, I understand your concerns about bricking the device, but the bootloader and firmware installation process have some safeguards in place on the R8 that provide a good deal of safety. I don't want to overstate the case, but I think you'd be protected from anything bad if you stuck to firmware changes and left the bootloader alone.
Just the other day I was looking into resurrecting one of my pre-covid music projects and fetched my R8 from the storage. Went looking on the internet what's the current state of affairs regarding R8, and found your repo on github (maybe 10 hours after it was published!).
The project was pretty simple: the R8 as a recorder, a drum machine and a eurorack with midi. All sequenced with a ruby or nodejs script on a 2008-era netbook.
The one problem I could not solve back then was reliable sync - hitting play in time on both the R8 and the drum machine with the master clock became a chore very fast. The only other options were syncing to the metronome click over the headphone out or a SMPTE track, and that was a rabbit hole I didnt feel like diving into.
Now I'm looking into the possibility of adding midi clock, transport commands and position out over USB in recorder mode. If it works, this will turn the R8 into the ultimate portastudio.
Thank you for sharing your work! Without it I would not even think it was possible.
That sounds like a fun project.
If you get anything working I'd love to hear about it. There's USB MIDI in the stock firmware, but only when you have it in control surface mode, and I haven't taken the time to investigate that very far. It seems like the original firmware makes an effort to not try to do anything else while using USB, but it would be interesting to see if you could get it to turn on USB MIDI while it is in regular recorder mode so that it could process message.
Good luck!
For my use case, it only needs to send the midi clock at 24ppqn and start/stop. That's one byte every 20ms, can't be that taxing on the CPU.
And it does quite a lot in USB audio/control surface mode: stereo in/out, insert & send effects, midi control surface messages back and forth etc.
Earlier portastudios had DIN sockets and midi clock out, but then DIN sockets went away and midi sync dissapeared too. I don't think there was a technical reason for this, more like lack of imagination. Why would anybody need midi clock over usb when there was a daw on the other end? DAWless wasn't a thing back then yet.
Can you share why the R8, and what does custom firmware give you? Genuinely curious, thanks a lot!
As with many things, the answer to why I chose the R8 is that I happened to have one so it was easy to try out.
The R8 does have a few other things going for it: 1. the firmware is not encrypted 2. the I/O is considered pretty decent (low noise floor) 3. for a while you could get them for ~$150 4. 9 good sized faders on the front
So far I've added some features to the stock firmware: * a "reverse track" tool, which is the thing that started me down this path in the first place * a tool launcher that can run custom code inside the stock firmware, which lets me take advantage of the firmware's features and not have to restart * an app launcher that launches new firmware from the card, so that I can run new code without having to do a whole new firmware re-install
One of the first really useful things I made was a Forth firmware (and later a Forth app) so that I could run arbitrary code on the device and peek and poke memory. This really helped speed up the bootstraping process, because I didn't have to restart and reinstall firmware every time I wanted to try something new.
I've created some weird musical app/firmwares: * a pretty basic loop playing program * a Blippoo Box (feedback noisemaker) * a firmware based on the concepts from Musique Concrète that lets you do all kinds of weird sampling and sample manipulation
The first two are in the repo, the last one is something I'm developing separately as a way to test what I've found and see what else I should explore on the R8. I mostly wanted to share what I'd found so other folks could do R8 firmware development without having to completely reinvent the wheel.
Super interesting, thank you! I bought a Zoom LiveTrak L6 about a year ago, and have really like it. I wish I knew about the R8 which is cheaper and has bigger faders. And yeah - wow - all of this open firmware work!
Thanks a lot, I really appreciate your input and sharing your work. Cheers
looking good! how much of this do you think will apply to the Zoom R12?
Thanks!
The R12 is over a decade newer so I'd be surprised if there was much overlap, but it would be interesting to check out at some point.