Request a firmware review
Menu
Hardware startups between working prototypes and a first production run

From first boards to first shipment

What firmware has to get right between the first board that powers up and the first box that ships.

The road from a prototype to a product runs through a series of builds, and the firmware has a job at each one. This section of Field Update covers that road: bringing up a new board revision, sorting hardware faults from firmware faults, testing on real hardware, the engineering, design and production validation builds (EVT, DVT and PVT), and the factory programming that gives each unit its bootloader, keys, identity and starting version.

Most of what goes wrong here is ordinary. A debug header left off a board revision. A part substituted by the contract manufacturer. Tests that pass on a desk and fail on a production line. A factory station that writes the wrong image, or leaves a debug port open. The articles explain how to catch these early, what to measure, and what to write down so the next board revision goes faster than the last.

Testing gets particular attention. A firmware team that runs unit tests on every commit and hardware-in-the-loop tests before every release catches many regressions before they reach the field. This section looks at how a small team can set that up without a large lab.

Our free checklists follow the same path: the board bring-up checklist for first power-on, the production readiness checklist for the EVT, DVT and PVT gates, and the firmware release checklist for every release after that. When you want help with the work itself, see board bring-up, test automation and manufacturing firmware, or read how we work with hardware startups heading for a first production run.

The articles in this section are listed below with their issue dates.

Articles in this section, with issue dates
IssueArticle and the question it answers
RF certification test firmware: what the lab will ask forWhat test firmware and radio test modes will the FCC or EU test lab need from us, and does using a pre-certified module remove that work?
Outsource firmware or hire: how hardware startups decideShould our startup hire its first firmware engineer, use a contractor or firm, or combine both, and what must we own whichever route we take?
Firmware testing for startups: unit tests, CI and a HIL rigWhat automated firmware testing should a small team set up first, and when is a hardware-in-the-loop rig worth building?
Factory provisioning: giving every device a unique identityHow should each device get its unique keys and certificates during manufacturing when a contract manufacturer builds our boards, and what has to be locked before units ship?
From prototype code to production firmware: keep or rewrite?Our prototype runs on Arduino or vendor example code: what can we keep, what must change, and in what order, before the first production run?

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.