How to use Claude to build an EEPROM upload tool
Claude Code implemented a serial protocol for a homemade EEPROM programmer. Its maker wired the Arduino hardware and checked uploads in a real homebrew CPU.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Implement a serial upload protocol between my Python microcode generator and Arduino EEPROM programmer. Follow the supplied shift-register wiring and OE/WE/CE timing, start with a slow verified upload and use physical readback before improving page-write speed.
Reach people exploring AI agents
See placements →What happened
The homebrew programmer could accept generated microcode over serial and upload it to physical EEPROMs. Claude's contribution was the protocol; CPU hardware construction and verification remained human.
Reported by Will Warren — Personal blogHow the agent did it
- Warren assembled an Arduino and shift-register EEPROM programmer for three microcode ROMs.
- Claude Code designed and implemented its computer-to-programmer serial protocol.
- Warren tested slow uploads and then improved programming with page writes.
Where a person stepped in
Warren designed and assembled the programmer, connected physical control signals and tested uploads and CPU behavior.
Will Warren used Claude Code to design and implement the serial protocol for an EEPROM programmer in his homebrew CPU project. The immediate problem was getting generated microcode from a computer onto three physical ROM chips without making every revision a manual programming exercise.
The programmer used an Arduino Nano and shift registers to address and control the EEPROMs. Warren handled the circuit design, wiring and control-signal arrangement. Because the chip's output-enable, write-enable and chip-enable signals passed through the shift-register chain, sequencing those signals correctly mattered before faster writes could be attempted.
Claude's contribution connected the existing microcode workflow to the programmer over serial. The resulting toolchain generated binary ROM data in Python and uploaded it to the hardware. Warren reports that a slow programming mode worked on the first attempt, then describes improving the transfer with page writes instead of individual byte writes.
The larger article follows the CPU into working hardware, but does not attribute every schematic, soldering fix or timing correction to Claude. This is a specific interface-development use case: agent-written protocol code became part of a human-built programming tool, with actual uploads and physical CPU behavior providing the checks beyond compilation.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Personal blog · Will Warren
Frequently asked questions
What did Claude actually build?
The serial protocol linking the computer's microcode workflow to the EEPROM programmer.
Who handled the hardware?
Warren designed, assembled and tested the physical programmer.
What checked the result?
Actual EEPROM uploads and subsequent behavior of the homebrew CPU.
More details
About this account
Warren assembled an Arduino and shift-register EEPROM programmer for three microcode ROMs. Claude Code designed and implemented its computer-to-programmer serial protocol.
Original engineering account opened. Claude's explicit contribution is the serial protocol; the surrounding CPU, PCB and physical debugging are human work. The article discloses PCBWay sponsorship. Suggested prompt written by Agents In Use; no original task prompt was published in the verified account.
Credit: Will Warren — Personal blog
Source published 12 Mar 2026
Source checked 14 Oct 2026
Tools and topics
Claude Code · Arduino Nano · Python · EEPROM
Microcode · Serial protocol
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.