Firmware that does what the product promises, and still updates safely in the field.
We write the code that runs on your board, from the first bring-up to the update path a shipped unit relies on, in C, bare-metal or RTOS, against the datasheet and errata of the part you chose.
Clayton, North Carolina. Serving Raleigh and the Triangle. Ships nationwide.
You have hardware, and need the software that makes it a product.
Maybe the boards are back and nothing runs on them yet, a prototype sketch has to become firmware you can ship, or a chip is going obsolete and the code has to move to another family. We work across vendors rather than tied to one, so the right part drives the design: STM32, ESP32, Nordic nRF52, Microchip PIC/AVR/SAM, TI MSP430/CC, and Arduino-compatible.
Firmware you can build, ship and update.
- Source and build Written in C, bare-metal or RTOS, with build instructions and register-level notes on any non-obvious configuration.
- Connectivity The links your product needs: UART, RS-232, RS-485, I²C, SPI, CAN, LIN, USB, Ethernet, BLE, Wi‑Fi, and sub-GHz/2.4 GHz radio.
- Update and recovery Bootloaders (ROM/system, USB DFU, UART, custom), OTA over BLE and Wi‑Fi, dual-slot updates with rollback, browser-based flashing (Web Serial/WebUSB), so a failed or interrupted update does not brick a unit.
- Ports between vendors When a part goes away we move the code to its replacement, for example STM32 to Nordic, Microchip to TI, and others.
- Protocol and interface notes What each interface carries and how, written down so the next engineer does not have to rediscover it.
- A pinned release A version-pinned release build, and the files listed in your quote.
Four steps from requirements to a release.
- 01 Tell us what it has to do Send the product description, the board or chip if you have one, the interfaces it must support and any existing code through the quote form.
- 02 Choose the architecture We pick the approach with you: bare-metal or RTOS, the update scheme and how it talks to the outside world.
- 03 Write and test on your hardware We write the firmware and run it on the real board, against the datasheet and errata.
- 04 Release You receive the release build, the notes and the files listed in your quote, with the update and recovery path tested.
Our own firmware, on our own boards.
This is code of ours that hands an STM32 to its system bootloader for a field update, next to the chip on one of our prototype boards. The free flashers below are ours too.
Before you ask
Which microcontrollers do you write firmware for?
We write firmware for STM32, ESP32, Nordic nRF52, Microchip PIC/AVR/SAM, TI MSP430/CC, and Arduino-compatible, in C, bare-metal or RTOS.
Can you make a shipped device safe to update in the field?
Yes. We design the update path: bootloaders (ROM/system, USB DFU, UART, custom), OTA over BLE and Wi‑Fi, dual-slot updates with rollback, browser-based flashing (Web Serial/WebUSB).
What should I send to get a firmware quote?
A short description of what the product does, the chip or board if you have one, the interfaces it must support and any existing code. Send it through the quote form and we scope it from there.
Notes and tools that go with this.
Tell us about your firmware.
All servicesClayton, North Carolina. Serving Raleigh and the Triangle. Ships nationwide.