Firmware your hardware can ship with.
Device code from drivers to OTA updates, plus the factory test program that checks every unit before it is packed.
Who this is for
Hardware that needs code it can ship with: a device running demo code, a board that needs drivers and protocols, or a product that needs a factory test program.
Typical starting points
- Existing code or a repository
- A description of how the device should behave
- A board we designed with you, or your own board and its schematic
What Anvol does
- ESP32 and STM32
- C/C++ and MicroPython
- BLE and Wi-Fi
- Sensor drivers
- Motor control
- Data protocols and SDKs
- OTA updates
- Factory test programs
- API documentation
Deliverables
- Firmware source
- Factory test program
- Protocol and API notes
Typical inputs
- Existing code or repository, or a description of how the device should behave
- The hardware, or its schematic
- Any app or service the device talks to
Timeline and cost drivers
- Timeline
- Set in the written scope, with milestones you confirm.
- Cost depends on
- Number of features, connectivity, and how much existing code can be reused.
What is excluded
- Certification testing (FCC/CE). It is done by a test lab and quoted separately when a product needs it.
- Anything outside the written scope. Major scope changes are re-quoted, with a new timeline, before work continues.
Related cases
Questions
Yes. Firmware source is a deliverable, along with the factory test program and protocol and API notes. Anvol's general libraries stay ours; open-source parts keep their licenses.
Yes. How much can be reused is one of the cost drivers; we read it first and say what we would keep.
Code that checks each unit before it is packed, against the targets from the sample rounds. It is how a batch gets tested unit by unit.