Firmware
The battery dies in three days. The Bluetooth link drops. A sensor driver does not work and nobody left on the team wrote it. We fix the program inside the device.
What we work on
- Battery life: sleep states, when to wake the radio. The most common reason people write.
- Radios: BLE, Wi-Fi, and LoRaWAN, including outdoor nodes that must survive a Dutch winter.
- Drivers: I2C, SPI, UART, CAN. Getting a new sensor to talk.
- Someone else's code: an undocumented codebase, read with a debugger and an oscilloscope.
- Cases and mounts: 3D files for the board's enclosure, yours to print or send to a manufacturer.
C and C++ on ESP32, nRF and ARM Cortex-M, FreeRTOS, Zephyr, or bare metal.
How it goes
- Short call. You explain the idea or the problem.
- Written scope and price. What you get, by when, for how much. Nothing starts before you agree.
- Work in short steps. You see progress along the way, not only at the end.
- Handover. The files and the code are yours.
This is for you if
- Our ESP32 or nRF device crashes, drops Bluetooth, or drains the battery.
- We need drivers for a new sensor.
- The firmware was written by someone who left, and nobody can change it.
We built devices for Madglove, sensors on a rehabilitation glove, and for Mycofarming, sensors and cameras for a mycelium filter. See the projects.