Skip to content

Board bring-up and schematic review

I do the hardware-side work that makes an FPGA board real: schematic design and review before the board is ordered, first power-on when it arrives, clock trees, and high-speed links tuned and validated with real patterns on real hardware. I've been bringing boards up since 2008, from palm-sized SDR modules to multi-board quantum network equipment.

Schematic review · PCB review First power-on Clock trees SERDES · JESD204B · PRBS

What I do

Schematic design and review

Power architecture, reference clocking, decoupling, reset strategy and pinout reviews before the board goes to fab. I reviewed six boards for one quantum network product, catching problems while they were still cheap to fix.

First power-on

A bring-up plan written before the board exists: what to measure at each rail, what order to enable things in, and what a safe first bitstream looks like. Then the real power-on, with the scopes on it.

Clock trees and data converters

Reference and sample clocks distributed and verified: jitter budgeting, PLL configuration, synchronization across channels, and converters that still line up after every power cycle.

High-speed link bring-up

SERDES and JESD204B links tuned and validated with PRBS, eye scans and error counters until they stay up under load, with the register access over SPI or your bus of choice to prove it.

For the RTL and timing closure side of a design, see FPGA design. For the tests that catch problems before hardware exists, see FPGA verification.

Typical problems I'm brought in for

  • A board came back from fab and it won't come up, and nobody can tell whether it's the hardware, the bitstream or the software.
  • The schematic is nearly done and you want a second set of eyes on it before it goes to fab.
  • The contract manufacturer's review covered assembly, not the FPGA's needs: power sequencing, banking, clocking.
  • A high-speed link trains on the bench and then drops errors under load.
  • Channels that should line up don't, and the alignment changes after every power cycle.
  • The next revision has to work, because a third spin isn't in the budget.

How engagements work

Design review

$2,500

fixed price · delivered in three days

A schematic you want checked or a board that won't come up. 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 link fix or a schematic revision, 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

Can you review a schematic before we commit it to fab?

Yes. A schematic review before fab is the cheapest point to catch the problems that cost weeks later: power sequencing, reference clock placement, decoupling, reset strategy and connector pinouts. It fits inside a design review.

Do you work remotely?

Yes. I'm based in West Milford, NJ and work remotely with teams anywhere. Ship me a board and the bring-up happens on my bench, as if I were in the next room. I travel on site when it makes sense.

Will you sign an NDA?

Yes. I'm happy to sign your NDA before we get into the details of your system.

Who owns the deliverables?

You do. Everything I deliver is yours outright on payment: the repo, the scripted builds, the tests and the docs.

Board not coming up?

Tell me what you're building and where you're stuck. I'll reply within one business day.

Start a project