What Custom Firmware Development Involves, and What Drives the Cost

Firmware is the software that runs inside a device: the code that reads the sensors, drives the motors, talks to the app and decides what happens when something goes wrong. If you are planning a product, it helps to know what a firmware project really includes before you ask for quotes.

What firmware does

Firmware runs on a microcontroller (such as an ESP32 or an STM32) without a full operating system. It typically:

• Reads sensors and inputs, and controls outputs such as relays, motors and displays.
• Talks to other chips over buses such as I2C, SPI and UART.
• Connects to Wi-Fi, Bluetooth, 4G or LoRa, and to a cloud backend or app.
• Saves settings, logs data and handles power cuts.
• Updates itself safely in the field.

What a firmware project includes

1. Requirements

What exactly should the device do, in which situations, and how fast? Clear requirements are the biggest single factor in delivering on time and on budget.

2. Board bring-up

Getting a new custom board running for the first time: clocks, power, programming and every peripheral confirmed working. Hardware mistakes usually show up here, which is why firmware and hardware teams should work together.

3. Drivers and core features

Code for each sensor and peripheral, then the actual application logic.

4. Connectivity

Connecting to the network, reconnecting reliably after drop-outs and exchanging data securely with the server. On real deployments, reconnecting after a network failure takes more work than connecting the first time.

5. Over-the-air (OTA) updates

The ability to update firmware remotely. For a connected product this is essential: it is how you fix bugs and add features after devices are installed. A good OTA system checks that the new firmware is genuine and rolls back automatically if an update fails.

6. Reliability and safety

• A watchdog that restarts the device if the code ever hangs.
• Safe states: after a crash or power cut, outputs come back in a known, safe position (a pump off, a door locked).
• Handling of bad sensor readings and unexpected inputs.

7. Security

No default passwords, encrypted connections, protected credentials and signed updates. Security is much cheaper to design in from the start than to add later.

8. Testing

Testing on the real hardware, in the real conditions: heat, weak signal, power cuts and long running times. A production test routine checks each unit before it ships.

What drives the time and cost

How to get an accurate quote

Bring a short description of what the device does, the hardware (or the chip you plan to use), how it connects, how it is powered and how many units you plan to build. Even a rough list lets an engineer estimate properly.

Our custom firmware development covers everything from bootloader to application layer, on ESP32, STM32 and other platforms. We also design the PCB, so hardware and firmware are built to work together from the start.