Request a firmware review
Menu
Hardware startups planning their first production run

Firmware gates for EVT, DVT and PVT builds

What firmware has to show at each hardware build stage before the next one starts, ending with the checks before the first units ship.

Key characteristics

Items
18 in four gates
Gates
EVT, DVT, PVT, ready to ship
Output
Ticks on screen, CSV download, print
Runs
In your browser with nothing sent

Checklist: Firmware gates for EVT, DVT and PVT builds

Tick items as you confirm them. Ticks stay on this page only; download the list when you are done.

EVT: does the design work
DVT: does it work everywhere it must
PVT: can the factory build it
Ready to ship

0 of 18 items confirmed

Hardware startups usually reach production through three build stages. EVT (engineering validation test) asks whether the design works. DVT (design validation test) asks whether it works everywhere it must: across temperature, battery levels and radio conditions, and through the tests a certification lab will run. PVT (production validation test) asks whether the factory can build it, the same way every time. Teams draw the lines slightly differently, but the questions hold. This checklist lists what firmware must show at each gate, so the firmware is never the reason a build slips, or the reason a weak one goes ahead.

How to use it

Review the next gate well before the build, not after it: several items take weeks to prepare. At the gate meeting, tick what is confirmed and download the CSV as the record. Anything unticked either becomes a named risk with an owner, or the gate waits. Ticks are not saved if you leave the page.

The four gates

EVT: does the design work

All peripherals brought up and tested on EVT boards, the power budget measured on real hardware, the bootloader, signing and update path working from a signed image to a confirmed update on the device, and known hardware issues listed with any firmware workarounds. The update path sits here on purpose. If it waits for DVT, the units in your field trial may go out without a safe way to fix them.

DVT: does it work everywhere it must

Firmware feature-complete for the first release; temperature, battery and radio range tests passed; pre-certification radio tests run with the test firmware the lab needs; a security review of debug access, keys and update signing; and field trial units updated over the air at least twice. Labs usually need firmware that holds the radio in fixed test modes, so build it before the lab date, not during it. Two real field updates prove more than any bench test that the path works where the devices live.

PVT: can the factory build it

A factory programming procedure written and timed; factory test firmware that checks every part a customer depends on; a unique device identity and keys provisioned and recorded for each unit; the debug port locked on production units; and a defined path for failed units: rework, retest or scrap. Unique identity is also a regulatory theme. The UK’s product security regime, for example, requires passwords on consumer connectable products to be unique per product or set by the user. NIST IR 8259 Rev. 1 describes the wider set of cybersecurity activities a manufacturer should consider before an IoT product is sold.

Ready to ship

The shipping firmware version frozen and signed, the first over-the-air update already planned for after launch, a way for support to read the version and health of a returned unit, and named owners for releases, updates and incidents. Planning the first update before launch is the safe assumption, not a pessimistic one: the path should be exercised before the day it is needed.

Reading the example

Example (fictional). Loamwick’s 40 trial probes on Rev D boards were updated over the air twice, to 1.0.2 and then 1.1.0, which is the evidence the last DVT item asks for. The flash budget check showed the 412 KB image would not fit its slot with 25% growth, so Rev E moves the second slot to external flash. Because the flash layout changes, the EVT item for the bootloader, signing and update path has to be shown again on Rev E before the PVT build.

Limits

  • Firmware only. Mechanical, electrical, supply-chain and certification work have their own gates.
  • Not a certification checklist. A ticked pre-certification item does not mean a product will pass; it means you looked for problems early. This page is not legal or regulatory advice.
  • Gates are decisions. A startup may ship DVT units to a pilot customer on purpose. The checklist makes that a decision with an owner, not an accident.

What to do next

The PVT items are the core of our manufacturing firmware work: factory programming, test firmware and device identity. Firmware security covers the lockdown and key items, with more detail in the secure boot checklist. For the earliest stage, start with the board bring-up checklist. Startups planning a first production run can read more on the hardware startups page and in the prototype to production section of Field Update.

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.