Firmware services, arranged around the release
Eleven services that follow one method, from the first written review to releases your own team can run. Most work starts with a firmware review.
Key characteristics
- Method
- Review, Bring-up, Build, Ship, Sustain
- First step
- A fixed-scope firmware review and a written plan
- Every release
- Signed, staged and reversible
- Status
- A weekly written status from one technical lead
Firmware work at a hardware startup rarely arrives in a tidy order. Boards come back from assembly before the code is ready, a field trial gets booked before anyone has decided how devices will be updated, and a customer’s security questionnaire lands in the same week. We arrange every service around one method so the pieces land in an order that holds up: Review, Bring-up, Build, Ship and Sustain. Each stage is described on how we work.
Most work starts with a firmware review
A firmware review is a short, fixed-scope first engagement. We read your schematics, your current code if you have any, your flash layout and your update plan, and we deliver a written plan with the risks we found and the order we would tackle them in. It is useful on its own, and it tells both of us which of the services below you actually need. Request a firmware review when you are ready.
How the services fit the method
| Stage | What happens | Services |
|---|---|---|
| Review | We read what exists and write the plan | Firmware review; documentation and onboarding closes the loop at the end |
| Bring-up | First boards power on, debug works, every part is checked | Board bring-up |
| Build | Application firmware, radios, power and tests | Firmware development, embedded Linux, connectivity, low-power design, test automation |
| Ship | Signed releases, the update pipeline, factory programming and the first rollout | Over-the-air updates, firmware security, manufacturing firmware |
| Sustain | Maintenance releases, release reports and handover | Sustaining releases |
Documentation and onboarding is listed with the review because it is the other bookend of an engagement: the review is how we learn your product, and the handover is how your team learns our work.
What stays the same in every service
- One technical lead. Every client has one named lead who writes a short weekly status in plain English (what was done, what was measured, what is blocked, what is next) and a release report after every release.
- Measured results. We report things you can check: sleep current, update success and rollback counts, test results, release reports. We do not promise outcomes we cannot measure.
- Your code, your keys. You receive the source code, build instructions, signing setup and documentation. Ownership and licensing terms are set out in each agreement.
- Built to be updated. Whatever we build, the update path is planned from the first commit, so later fixes can reach devices in the field.
The services combine into six engagement types, from a firmware review to a team handover. To see how they fit together on one product, follow the fictional example project, or try the free tools and checklists we use in our own work.
Review and handover
Build
Ship
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.