Embedded firmware for Zynq, soft cores, RISC-V and ESP32
I write bare-metal and Linux firmware on soft and hard processors and microcontrollers, from Zynq ARM cores to ESP32 sensor nodes. Because I also design the FPGA, the firmware and the hardware it controls come from one person, which is where most integration bugs stop.
What I do
Zynq and hard processors
Bare-metal and Linux software on Zynq ARM cores: boot, drivers for your custom FPGA logic, and the control code that ties them together.
Soft cores and RISC-V
Soft-processor control stacks inside the FPGA, including RISC-V, for systems that need a small, deterministic controller next to the logic.
Microcontrollers and ESP32
ESP32 firmware for sensor nodes and connected devices. I build and sell my own: Hatchtrack, a sensor egg that alerts your phone when incubator conditions drift.
Register access and host control
Register maps, SPI command parsing, Linux drivers and Python control libraries your scientists and test engineers can use directly.
Firmware gets the same treatment as RTL: see verification and test automation. If the processor sits in a GPU host fed over PCIe, see PCIe and GPU streaming.
Typical problems I'm brought in for
- The FPGA works in simulation, but nobody has written the software to drive it on the board.
- The Zynq boots, but your custom logic doesn't show up or doesn't respond.
- Control firmware grew one feature at a time and nobody wants to change it now.
- A prototype sensor node works on the desk and fails in the field.
- Your scientists or test engineers need a clean Python interface instead of raw register pokes.
- The firmware and FPGA teams each blame the other for the same bug.
Related work
Quantum networking · 2022–2023
Control for a commercial quantum network
RTL, a soft-processor control stack and schematic review across six boards.
Edge AI · RF · 2025
RF straight into GPU memory
Transceiver streams into a GPU host over PCIe, with the register interface, interrupts and a custom Linux driver.
Quantum computing · 2024
Chip-to-chip control links
Control traffic over SERDES links, with register access over SPI and command parsing.
How engagements work
Design review
$2,500
fixed price · delivered in three days
A board that won't come up or firmware you want checked. A written assessment with next steps, credited in full toward a sprint.
Sprint
$15,000
fixed price · two weeks
An agreed scope and a working, tested deliverable: a bring-up, a driver or a control stack, with the repo, tests and docs.
Retainer
$25,000 / month
month to month
Ongoing development with priorities set week by week, for teams that need a senior engineer on it continuously.
Prices in US dollars. Tell me about your project and I'll suggest the right fit.
Questions
Do you take firmware-only projects with no FPGA?
Yes. Microcontroller and ESP32 work stands on its own, and Hatchtrack is a product I built end to end. The FPGA background helps most when firmware has to talk to custom hardware.
Bare-metal or Linux?
Both. I'll recommend whichever fits your timing, boot and maintenance needs, and explain the trade-off in the spec before any code is written.
Do you work remotely?
Yes. I'm based in West Milford, NJ and work remotely with teams anywhere. Bring-up happens on your board.
Who owns the firmware, and how is AI used?
AI agents working inside my rule sets draft code, tests and docs. Simulation in CI and hardware-in-the-loop tests catch what generation gets wrong, and I review and own everything that ships. You get the repo, scripted builds, tests and docs, so your team can carry it forward.
Hardware waiting on firmware?
Tell me what you're building and where you're stuck. I'll reply within one business day.
Start a project