Embedded firmware the next engineer can pick up and work on.
How this works
Firmware is where hardware problems show up first, so we start close to the board: power and clocks, then the debug connection, then drivers and protocols, and the application on top of those.
If your boards aren't ready yet, we get the code structure, drivers and a test harness running on a dev kit, then move onto your hardware once the first boards are on the bench.
The code goes into your repository with a build anyone on your team can run, notes on the peripherals and protocols we touched, a list of known limits, and the programming steps your line needs for production units.
| Checkpoint | What your team can expect |
|---|---|
| Scope and stage | The next defined stage is written before larger work begins, so you can decide what to fund next. |
| Handover | Source files, tests and decision notes are part of the handover, so your team can continue from a known version. |
| Procurement and build | When hardware is involved, you can buy the parts directly or have us source them at itemised cost; alternates and first checks are recorded before any order. |
Frequently asked questions
Do you need our hardware before you can start?
You don't need it on day one. Until the first boards arrive, the schematic, datasheets and a dev kit with the same microcontroller are enough to get the structure and tests in place. The real board matters most once drivers and bring-up begin.
Can you take over firmware someone else wrote?
The first step is getting the existing firmware to build the same way twice and reading through it. We then write down what we'd fix first before changing anything. There's more on this on the Legacy Firmware and Field Rescue page.
How do you handle firmware updates in the field?
We'd design the update path together with the bootloader: how a new image reaches the device, how it's checked, and what happens if power drops halfway through. Making that decision early costs less than changing it after units have shipped.
What will our engineers get at handover?
The source in your repository, a build any of them can run, interface notes and the bring-up checklist we used on the first boards. Known limits and open issues are written down as well, so nothing important lives only in someone's head.