Firmware your devices can safely update.
Embedded firmware and over-the-air updates for hardware startups, from first board to fleet.
Figure 1. Update sequence
A fictional soil probe with two image slots. Download an update, reboot into it, then confirm it or fail its self-test.
Ready. The probe runs v1.0.2 and checks with its gateway for updates.
1Features
- Application firmware on Zephyr, FreeRTOS or bare metal
- Signed updates, two image slots and rollback from the first release
- Staged rollouts with a written halt rule and a release report
- One technical lead who writes your weekly status in plain English
- Documentation and onboarding your next hire can learn from
2Applications
- Hardware startups before their first production run
- Connected consumer products
- Medical and health devices
- Climate and energy hardware
- Robotics and industrial sensors
3Description
Fumbar writes the firmware that runs on your boards and the update path that keeps it improving after units ship. Work starts with a firmware review and ends with source, signed releases and a team that can carry on.

4Functional block diagram
What you hand over, the five stages of the work, and what you receive. Each stage links to the service behind it.
You provide
Schematics and boards, requirements, any existing code, access to your cloud or gateway, and a person who can decide.
Fumbar works in five stages
One account lead writes a weekly status and a report after every release. How we work.
You receive
Source and build instructions, signed releases, an update pipeline with a rollout plan, test records, and documentation with onboarding.
5Ordering information
Six ways to engage. Most start with a firmware review. Compare engagements
| Engagement | Starts with | You receive |
|---|---|---|
| Firmware review | Schematics, any existing code, your flash layout and update plan | A written plan: risks, the order of work and how updates will reach the field |
| Bring-up sprint | First boards, a debug probe and the hardware engineer on call | Working drivers, a board support package and a bring-up log with measurements |
| Product firmware build | Requirements, target hardware and a person who can decide | Application firmware with tests, release builds and a weekly written status |
| Update pipeline setup | A device that boots and access to your cloud or gateway | Bootloader, signing, two image slots, rollback and a staged rollout plan |
| Sustaining releases | A product in the field and a list of what needs fixing | Scheduled maintenance releases, each with a release report |
| Team handover | Your firmware hire, or the team that will own the code | Documentation, recorded walkthroughs and a handover checklist worked through together |

6Typical application
Example (fictional). Loamwick, a two-founder Denver startup, has 40 prototype soil probes, four gateways and a field trial in eight weeks.
- Week 1: a firmware review of the Rev C boards and the flash layout.
- Weeks 1 to 6: bring-up, sensor and radio firmware, and the update path.
- Week 8: the trial starts on v1.0.0.
- Later: v1.1.0 fixes a sensor drift, rolled out in three waves.
7Design tools
Free calculators, builders and checklists that run in your browser. All tools
Calculators
Builders and worksheets
8Revision history, from Field Update
Long guides for founders and firmware engineers, checked against their sources. Read Field Update
| Issue | Article | Section |
|---|---|---|
| What it takes to ship firmware you can safely update | Updates and releases | |
| Matter over Thread or Wi-Fi: choosing the transport for a new device | Connectivity and power | |
| RF certification test firmware: what the lab will ask for | Prototype to production | |
| FDA cybersecurity for device startups: what your firmware must show | Security and regulation | |
| Field crash diagnostics: watchdogs, faults and coredumps | Firmware architecture | |
| LTE-M or NB-IoT in 2026: choosing cellular for US deployments | Connectivity and power |
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.