Firmware for hardware startups heading to production
Some firmware decisions cost an afternoon before your first production run and a recall after it. We help you make those first, then build the rest with you.
Key characteristics
- Stage
- Working prototype to first production run
- Decide early
- Update path, signing keys and flash layout
- First step
- A firmware review with a written plan
- Ends with
- Your own team able to ship a release
Most seed and Series A hardware teams reach the same point. The prototype works on the bench, the demo went well, and a contract manufacturer wants a date. The firmware that got you here was written to prove the idea. It often has no bootloader that can accept an update, no signing key, a flash map nobody planned, and one person who knows how to build it.
None of that is a failure. It is what prototypes look like. The question is which parts to fix before the first production run, because every unit you ship carries those choices with it for the rest of its life.
Cheap now, expensive later
Three decisions are close to free on a prototype and very hard to change once devices are in customers’ hands.
The update path
A device can only accept an update if the firmware it shipped with knows how. That takes a bootloader that checks signatures, room in flash for a second image, and an application that confirms a new image works before the old one is given up. Built before production, it is a bounded piece of engineering. Skipped, every bug fix after launch becomes a recall, a site visit or a customer plugging in a cable. Our over-the-air updates page explains how the path works and how we test it by cutting power in the middle of an update.
The signing keys
The bootloader in every unit trusts one public key, written at the factory. Whoever holds the matching private key decides what your devices will run for as long as they exist. Decide now where that key lives (a cloud key service, a hardware security module or an offline procedure), who can use it, and what you would do if it leaked or was lost. We set this up so the key is created in your own account and Fumbar never holds the only copy. See firmware security and our security practices.
The flash layout
The flash map divides memory between the bootloader, two image slots, settings and logs. Make the slots too small and next year’s firmware will not fit. Change the layout later and units already in the field cannot follow, because their bootloader expects the old one. Check your own numbers with the flash budget calculator.
Example (fictional). Loamwick, a two-founder Denver startup, builds the LW-1 soil probe on a microcontroller with 1 MB of internal flash: a 48 KB bootloader, two 448 KB image slots, 32 KB of settings and 48 KB of logs. Its 412 KB application already fills 92.8% of a slot, so 25% growth would not fit. Because the first firmware review caught this, the team plans to move the second slot to external flash on the Rev E board instead of finding the limit in the field. The full story is on the example project page.
A few more choices are worth settling while they are still cheap:
- A version scheme that records the hardware revision, so a device refuses an image built for a different board. The version scheme builder drafts one.
- An RTOS release with enough support left. Zephyr long-term support releases are maintained for about five years; FreeRTOS long-term support libraries get security and critical fixes for two years, and the current FreeRTOS 202604 LTS runs to April 30, 2028. The RTOS selection worksheet helps you compare.
- Device identity and factory programming. Each unit needs a unique identity and the right bootloader, key and starting version written at the factory. See manufacturing firmware.
From prototype to a production run
Most teams move through engineering, design and production validation builds (EVT, DVT and PVT) on the way to volume. Each build is a chance to freeze something. Our production readiness checklist lists the firmware gates for each one.
In our method, a typical path looks like this. Review: we read your schematics, code, flash layout and update plan and write down the risks. Bring-up: new board revisions are powered up and tested with your hardware engineer (board bring-up). Build: the application firmware is written or rebuilt with tests. Ship: signed releases, the update pipeline, factory programming and the first rollout. Sustain: maintenance releases and handover.
Hiring or contracting firmware
This is a real decision, and the honest answer is often both.
| Hire a firmware engineer | Contract the work | |
|---|---|---|
| Fits best when | Firmware is core to the product for years | Specific work has to be done before a date |
| Knowledge lives | With that person, inside your company | In code and documents, if handover is planned |
| Main risk | One person holds everything | The contractor leaves and takes the context |
| What to ask for | Time to document as well as build | Source code, build instructions, signing setup and docs |
Many startups contract the work with a deadline (the update pipeline, the first production release) and hire for the long run. If you plan to hire, tell us at the start. We then write the documentation and runbooks with that person in mind, and a team handover ends with your engineer cutting and shipping a release while we watch. You receive the source code, build instructions, signing setup and documentation; ownership and licensing terms are set out in each agreement. The handover checklist shows what changes hands.
While we work together, one technical lead writes you a short status every week in plain English: what was done, what was measured, what is blocked and what is next. Founders who are not firmware engineers can read it and forward it to the board.
Where to start
If your prototype works and production is on the calendar, request a firmware review. We read your schematics, current code, flash layout and update plan, and you get a written plan with the risks ranked and the order of work. More on this stage 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.
Or email sales@fumbar.com, or call (720) 675-4202.