Agentic AI Designs an Analog Synthesizer · Tim, hardware and microcontroller blogger (cpldcpu) · Tim's Blog, November 14, 2026
An agent designs and brings up an analog synthesizer board from a parts list
Tim started from a blank folder and a fresh git repo, running Claude Code with Opus 5.5. He pointed it at JLCPCB's free parts list and named the microcontroller (CH32V00x); the agent proposed a subtractive synthesizer with a Juno-style oscillator, a Moog-style transistor ladder filter and a voltage-controlled amplifier. It then ran seven ngspice test benches, built a Python behavioral model calibrated against the SPICE results, generated KiCad schematics, and wrote the firmware and ordering files. By his logs, the design took 19 hours from first prompt to order, most of it unattended autorouting runs. PCB layout was where he intervened most. He had to ask for a floorplan that followed the functional blocks, two-layer routing never completed, and the four-layer board cleared only after he pointed out where to move blocks to make room for routing.
His working rule is the useful part. "My observation is that it is much easier for the models to generate the next abstraction layer from a complete specification in one go, instead of doing it step by step," he writes, and he has the agent write a design report in parallel. He also had the agent add an audio feedback path into the microcontroller's ADC so bring-up could be automated. When the boards arrived, Claude Code drove the lab PC over SSH and calibrated the board through that loopback and an oscilloscope. He reports an excellent match between simulation and hardware, with one hardware fix needed: a solder bridge he had made by hand. The design files, the AI-written report and audio samples are published.
Why it matters: This is a first-person account of agent work outside software that follows the same discipline as a software factory: full spec per abstraction layer, a simulator as the check before anything physical, and a test path designed in so the agent can verify its own output. The 19 hours and the hardware match are his figures; the published repo is there for anyone who wants to check the design.