I've spent fifteen-plus years watching makers wrestle wild ideas into boards that actually ship. Few projects capture that spirit better than JurassicVader's (Spencer's) custom video interface. Watching his YouTube video "I made a Custom Video Interface (Watch out NVidia)" felt like sitting in the lab with a determined engineer who refused to quit until pixels appeared on a real monitor.
Spencer wanted a true video output for the custom computer he is building from scratch—something capable of displaying readable text and eventually graphics, not just blinkenlights. He targeted a clean black-and-white 400×300 resolution driven entirely by discrete logic. No FPGA, no microcontroller video core—just counters, gates, RAM, and careful timing. That ambition makes solid PCB design and manufacturing non-negotiable. Breadboards teach you the concept; reliable PCBs turn the concept into something you can trust when the pixel clock starts ticking.
Watching "Hello World" Appear After Months of Rebuilding
Spencer began in October 2025. He rebuilt the circuit on breadboards multiple times—by his own count, the video interface had already been assembled about five times before the design phase shown in the video. The first working attempt used only three breadboards and roughly thirteen ICs: two for horizontal and vertical timing, one for data input. It looked clean. It almost worked.
Figure: Breadboards rebuilding in 2025
Then the real engineering started. He moved the entire design into Logisim so he could simulate every timing edge before soldering another wire. The new version grew to twenty-seven ICs—more than double the original count—but now the logic was intentional.
Two cascaded counter chains handled the timing. The horizontal counter ran to 528 (ten bits out of a twelve-bit capability) and clocked the vertical counter, which counted to 628. Together they generated the horizontal and vertical sync and blanking windows needed for a monitor to lock.
Figure: The horizontal counter ran to 528 and vertical counter to 628
Pixel data lived in RAM. Spencer serialized sixteen bits at a time into a one-bit stream—zero for black, one for white—so the interface could paint each line left to right, then step down. When the second physical build finally came together and the testing section began, the monitor showed words. "Hello world" (or something very close) appeared. It wasn't perfect—extra pixels and slight artifacts remained—but for a fully discrete, home-designed video system it was a genuine "watch out NVIDIA" moment. Viewers in the comments immediately recognized the achievement; one even recalled building similar CRTC-style hardware with wire-wrap tools in 1982.
Figure: RAM & Video Data
The user experience is pure maker joy: a custom computer that can finally talk to a real display. That single success validates months of iteration and sets the stage for the custom CPU still to come.
What the Circuit Actually Needed on a Real Board
Although the video itself still lives on breadboards, the logical next step—and the clear trajectory of the project—is a proper PCB. Based on the circuit complexity (dozens of 74-series counters, NAND gates, shift registers or multiplexers, and static RAM) a practical first production board would look something like this:
|
Parameter |
Typical Value for this Design |
|---|---|
|
Layers |
4-layer (signal–gnd–power–signal) |
|
Material |
FR-4, Tg 150 °C or higher |
|
Board thickness |
1.6 mm |
|
Copper weight |
1 oz outer / 1 oz inner |
|
Surface finish |
ENIG or HASL lead-free |
|
Via type |
Through-hole, 0.3 mm drill min |
|
Impedance control |
Not critical at ~10–25 MHz pixel rates, but controlled 50 Ω digital preferred |
|
Decoupling |
100 nF ceramic per IC, bulk 10 µF near power entry |
|
Trace/space |
0.15 mm / 0.15 mm minimum |
Layout priorities are short, direct routes from the cascaded 74x161 counters to the address bus, tight clustering of the serialization logic, and a solid ground plane under the entire digital section. Power and ground pins on every IC get their own local decoupling—something breadboards never provide cleanly.
Figure: Horizontal & Vertical Timing Assembly
The Half-Pixel Ghosts That Kept Coming Back
Anyone who has chased video timing on discrete logic knows the pain points Spencer hit.
● Cascade delay in the counters. Each 74x161 adds roughly 14 ns of propagation. Three stages in series create 28–42 ns of skew at the critical count transitions (15→16, 255→256). The result? Brief windows where the RAM address is invalid and the display shows half-pixel glitches or "glitched bits."
● Data serialization instability. Moving from parallel RAM words to a serial pixel stream introduced timing skew. Spencer had to rework that section completely after the first tests produced unreadable or inverted output.
● Breadboard parasitics at speed. Capacitance and intermittent contacts turned already-marginal timing into intermittent artifacts. Higher-quality boards helped, but the fundamental problem remained: long jumper wires and poor ground return paths.
● Sync and blanking edge accuracy. Small errors in the NAND-decode logic for front-porch, sync, and back-porch windows caused the monitor to lose lock or display extra pixels.
These are classic discrete-logic video problems. Simulation in Logisim caught the functional bugs; the physical builds revealed the analog realities of delay, noise, and parasitics.
Why the Next Step Had to Be a Properly Manufactured Board
Here is where the story shifts from heroic breadboard wrestling to manufacturable hardware. Spencer's design is already proven in simulation and on the bench. The missing piece is a clean, repeatable physical implementation that eliminates the very variables that caused the artifacts.
A professional 4-layer PCB from a responsive partner changes everything. Solid continuous ground and power planes slash the return-path inductance that amplifies counter-cascade glitches. Matched-length address and data routes keep the RAM interface clean. Local decoupling right at each IC pin becomes trivial instead of a wiring nightmare. The same twenty-seven ICs that sprawled across three breadboards fit onto a compact, rigid board with consistent inter-trace capacitance.
AIVON's role was never to redesign the logic—that credit belongs entirely to Spencer. AIVON simply removed the manufacturing friction that stops so many ambitious discrete projects. Quick-turn prototypes with welcome credits let a maker iterate the physical board the same way he iterated the Logisim model. DFM feedback on via sizes, copper balance, and silkscreen clarity catches the small issues that turn a "working on the bench" design into a board that works every time it powers up. Precise fabrication tolerances mean the 14 ns counter delays stay consistent from board to board instead of drifting with every new breadboard contact.
The result is a video interface that can move from "Hello world with a few extra pixels" to a stable, camera-ready display ready for the custom CPU. Reliability goes up, assembly time drops, and the project gains the mechanical integrity needed for further expansion—color modules, higher resolution, or integration into a multi-board backplane. That is the quiet power of a trusted manufacturing partner: it lets the creator's vision survive contact with the real world.
Quick DFM Reality Check for Discrete Video Timing
|
Checkpoint |
Why It Matters for This Project |
Pass Criterion |
|---|---|---|
|
Counter cascade routing |
Minimize cumulative delay skew |
Trace length delta < 5 mm between stages |
|
Local decoupling per IC |
Kill high-frequency noise on pixel clock |
100 nF within 5 mm of every VCC pin |
|
Continuous ground plane |
Clean return path for fast edges |
No long slots under digital section |
|
RAM address/data length matching |
Prevent half-pixel glitches |
Matched within 2 mm |
|
Power entry & bulk capacitance |
Stable rails during full-frame bursts |
10–47 µF near connector + ferrite |
|
Via stitching around high-speed nets |
Reduce EMI and improve SI |
Stitch every 5–8 mm near counters |
|
Silkscreen clarity for debug |
Easy probing of H/V sync and blanking |
Clear labels on all test points |
The Monitor Is Finally Listening
Spencer took a stubborn idea—full video output from pure discrete logic—and pushed it until a monitor displayed real words. The breadboard scars, the Logisim late nights, and the cascade-delay lessons are now part of the design DNA. With a properly manufactured PCB the same circuit becomes something you can hand to a friend, mount in a case, or expand without fear of the next intermittent glitch.
That is the journey I love watching. If you have a custom computer, a retro display controller, or any discrete-logic project sitting on a tangle of wires, the path from prototype to reliable hardware is clearer than ever. Professional manufacturing support turns the struggle into a finished product you can be proud of. Go build the next "watch out NVIDIA" moment—your monitor is waiting.
FAQ
Q1: Why stick with discrete 74-series logic instead of an FPGA for a custom video interface?
A1: Educational clarity and absolute control. Every gate and every nanosecond of delay is visible and intentional. For a from-scratch computer series it is the purest way to learn. The trade-off is size and power; a PCB makes that trade-off acceptable.
Q2: How do you mitigate the 14 ns cascade delay of 74x161 counters on a real board?
A2: Keep the cascade chain short and tightly routed, use synchronous enable rather than ripple where possible, and latch the final count with a register clocked on the opposite edge. A solid ground plane further reduces the effective skew that breadboards exaggerate.
Q3: Is 400×300 a practical resolution for discrete designs?
A3: Yes. It keeps the counter widths and RAM size manageable while still delivering readable text and simple graphics. Many classic discrete VGA projects settle in the 200–400 pixel range for exactly this reason.
Q4: What PCB material and layer count are realistic for a first video-timing board?
A4: Standard FR-4, 4 layers. At these clock rates you do not need exotic low-loss materials, but you do need continuous planes and decent decoupling. That combination solves most of the artifacts Spencer still saw on breadboards.
Q5: Should I add impedance control for the pixel or address buses?
A5: Helpful but not mandatory below ~50 MHz. Controlled 50 Ω digital traces plus good termination practice give cleaner edges; for a first prototype the planes and length matching matter more.
Q6: How many prototype spins should I budget when moving a video interface from breadboard to PCB?
A6: Plan for two. The first catches layout-induced timing or noise issues; the second incorporates the DFM and SI tweaks. Quick-turn services with engineering feedback make those spins fast and affordable.