Engagements · Hardware Rescue
Your product half-works. We get it to a board and firmware you can ship.
For a hardware product stuck between prototype and production: we take over the firmware nobody can maintain, fix the faults that show up in the field, review and respin the board, and hand back a build you can manufacture and update.
Hardware Rescue
- Typical length
- 8 weeks
- What you get
- 6 written deliverables, listed below
- What decides the number
- How much of the original firmware build survives, how reproducible the field failures are, and the layer and part count of the board. A two-layer sensor board with a buildable codebase sits near the floor.
- Scoping
- One call, then a written scope. We say no when it is not ours.
Contact salesGet a quote
01 The terms
Quoted per project, after a call. We do not publish a band for this, because a number without a scope is a guess and you would have to unpick it later anyway.
Tell us what the work has to do and when it has to be done, and you get the scope and the number in writing — or a straight answer that this is not ours.
03 The problem
Units lock up in the field, the developer who wrote the firmware has left, and the next production run is waiting on a board revision nobody has finished.
Fixing firmware on a board with a design fault, or respinning a board for firmware that is still broken, wastes both.
04 What you get
- Paid assessment: the failure reproduced and its cause chain written down
- A reproducible firmware build that runs on more than one machine
- Fault detection, watchdogs and automatic recovery for the failures you see
- Pre-fab design review of the board with a ranked findings list
- One board respin taken to fabrication-ready files
- An update path, so the next fix does not need a site visit
05 How it runs
- Weeks 1–2
- Assessment and board review. You get both documents whether or not you continue.
- Weeks 3–6
- Firmware fixes and the respin, in parallel, tested together.
- Weeks 7–8
- Fabrication files, update path, handover.
06 Whether this is for you
This is for you if
- Hardware startups between prototype and first production run
- OEMs with a deployed product that costs them support visits
- Teams hiring a firmware engineer who need the fix before the hire starts
This is not for you if
- Linux or Android embedded systems. This is bare metal and RTOS.
- Certification work (UL, CE) beyond design-for-compliance advice
- Products with no hardware yet. That is Board-to-Fab.
07 Proof
The eFuelPro framing layer resynchronises byte by byte through corruption on a shared legacy bus, on a 120 mm board designed and brought up in-house.
08 Questions
Can we do firmware only?
Yes. That is Firmware Rescue, from $8,000. This package is for when the board needs to change too.
Next 8 weeks
Hardware Rescue
Tell us what the work has to do and when it has to be done. You will get a person who has read it, not a sequence.