Firmware that runs for years without a reboot.
Microcontroller firmware in C and C++, with drivers, connectivity, safe over-the-air updates and power management, written to be maintained.
Firmware Development at picoBytes
Firmware is where products quietly succeed or fail. A watchdog that never fires, an update that can’t brick the device, a sleep mode that actually reaches its current target: these details decide whether customers trust your product.
We write structured firmware with clear module boundaries, so new features don’t break old ones and another engineer can pick it up later. We can start from scratch, extend your existing code, or rescue a codebase that has become hard to change.
What we do
Drivers & peripherals
Sensors, displays, motors, ADC/DAC, I²C, SPI, UART, CAN and RS485 drivers.
RTOS & architecture
FreeRTOS or bare-metal designs with a clean task structure and proper error handling.
Connectivity
Wi-Fi, BLE, LoRa, cellular and Modbus, with reconnect logic that survives the real world.
OTA updates
Secure bootloaders and fail-safe update schemes that roll back if something goes wrong.
Low-power design
Sleep strategies and current measurements for battery-powered devices.
Code rescue
Audits, refactoring and documentation for firmware that has become fragile.
From first call to launch
Discover
We map the requirement, constraints and budget, and agree on what “done” looks like.
Prototype
A proof-of-concept board, clickable design or first build that tests the riskiest parts early.
Build
Development in short milestones with regular demos, on real hardware and real screens.
Launch & support
Production handover, store or server deployment, and updates after release.
Common questions
Which microcontrollers do you work with?
Mostly ESP32 and STM32, along with other ARM Cortex-M parts and Allwinner and SigmaStar SoCs. If your chip has a datasheet and a toolchain, we can work with it.
Can you take over firmware written by someone else?
Yes. We start with a short audit, explain what we found, and agree with you whether to extend, refactor or rewrite.
Do you test firmware?
Where it matters, yes. We unit-test hardware-independent logic on a PC and build simple test rigs for critical hardware paths.
How are updates delivered to devices in the field?
Usually over the air through Wi-Fi or BLE, using a signed image and a fallback partition so a failed update can’t brick the device.
Let’s talk about your project.
Answer four quick questions and we’ll get back to you with next steps. No obligation, no jargon.