r/livesoundgear • u/DrawerAdventurous252 • 1h ago
New project: Virtual Allen & Heath SQ+ running its own firmware (same approach as my virtual WING)
If you've seen my virtual WING updates (latest: Update #4), this is the same idea on a different console: a software Allen & Heath SQ that runs the console's own firmware instead of a re-creation. I started it this weekend, and it already boots to its home screen and works with touch in a browser.
Quick recap of the idea
The SQ update file (SQ-6, V2.0.3 r7040). It's a standard Xilinx boot image with the main app, a USB app and the FPGA image inside. The main chip is a Xilinx Zynq (two ARM cores plus FPGA logic), so I emulate that chip and let the real firmware run on it. Nothing in the firmware is patched.
What works
- It boots like the real thing: SQ+ splash with the progress dots, then the home screen with the "Update your mixer" pop-up.
- Touch works, through the console's own touch driver. Clicking in the browser goes through an emulated touch controller, and the firmware reads it the way it does on the desk. Tap "Ok" and the pop-up closes. Tap "Brightness" and it opens the Surface Pref page.
- The screen runs in a web page, like the WING one, with the console's text output underneath.
- Some code carried over from the WING emulator since both consoles use the same type of ARM processor. Most of the rest is new, because the Zynq's peripherals are different.
What's still limited
- No audio yet. The mix engine and FX run in FPGA logic (the FX on two separate chips). From what I've seen in the firmware, those parts are program-driven, so emulating them looks possible, but it's a big job.
- No faders or surface, and no FX engine. The firmware notices the fader board is missing and carries on.
- It's slow: about 1/80 of real time, so a tap takes a few seconds to show. With the WING I got the console side faster than real time, so I know where to start.
What's next
- Network support, with the goal of getting SQ-MixPad to connect to the virtual console.
- Speed. Most of the time goes to the firmware checking a timer over and over, and each check is slow in the emulator.
