Microcontroller firmware
ESP32, Nordic nRF52, STM32 and other ARM Cortex-M parts. We help you pick the right MCU and develop the complete firmware, from initialization to product logic.
Embedded firmware · Barcelona
We write the firmware that makes your device work: ESP32, nRF52 and STM32, bare-metal or on FreeRTOS and Zephyr, with drivers, bootloader, OTA updates and low power. Tested, maintainable code, with over 20,000 devices running in the field.
What we do
From the board's first boot to field updates: one team that understands both the hardware and the code running on it.
ESP32, Nordic nRF52, STM32 and other ARM Cortex-M parts. We help you pick the right MCU and develop the complete firmware, from initialization to product logic.
Bare-metal when every byte and every microamp counts, or FreeRTOS and Zephyr when the product needs concurrent tasks, communication stacks and an architecture that scales.
Drivers for sensors, memories, displays and actuators over I2C, SPI, UART, CAN, ADC and PWM. Clean abstraction layers so swapping a component doesn't mean rewriting the product.
Custom or MCUboot-based bootloaders, updates over BLE, WiFi or cable, with image signing and rollback if something fails. Your product keeps improving after it ships.
Sleep modes, clock and peripheral management, and real current measurements to extend the battery life of battery-powered devices without giving up features.
Unit and integration tests, testing on real hardware, version control and documentation. Code your team can understand, maintain and extend.
When clients call us
You have the idea or the prototype and need production firmware: architecture, MCU selection and development up to the version that goes into production.
The previous supplier is gone or the code is hard to maintain. We audit it, stabilize it and give you back control.
The battery drains faster than expected. We measure, find where the current goes and optimize the firmware to extend battery life.
Your units are already installed and you need to fix bugs or add features without recalling them. We design a secure, robust OTA system.
An obsolete or out-of-stock part forces you to change MCU. We port the firmware to the new platform while keeping the product's behavior.
Your in-house team needs support on a specific part: a driver, the Bluetooth stack, the bootloader or the tests. We fit into your workflow.
What sets us apart
Firmware that works on the lab bench is not the same as firmware that works on thousands of units for years. We design with what comes next in mind: reliable boots, fault recovery, secure updates and code another engineer can pick up.
And because we also design hardware, apps and connectivity, we understand the whole product: over 20,000 devices run on our engineering today.
Success stories
We work under NDA: we show the challenge, not the client. Need technical detail? We'll walk you through it on a call.
Low-power Bluetooth-connected lock with app unlocking, encrypted communication and years of battery life.
Precise control firmware for a linear motor with real-time loops, power-stage management and reliable positioning.
Integration of Hall-effect sensors with ultra-low consumption for precise position and motion detection in battery devices.
Common questions
Yes. It's a common case: we audit the existing code, get it building reproducibly, document what's missing and recommend whether to fix it, refactor it or rewrite specific parts.
We start by understanding your product and its requirements, define the architecture and scope, and develop in iterations with regular deliveries you can test on the hardware. We work remotely or alongside your team, with continuous communication.
It depends on the scope: a driver for a sensor is not the same as a complete product with connectivity, OTA and low power. After the first call we propose an approach, a scope and a realistic timeline for your case.
Of course. We routinely work under NDA and treat all information about your project as confidential.
Yes. We can develop the firmware on your existing board or join a specific part of the project. And if you need it, we also design the hardware (schematic and PCB), the app or the connectivity.
Let's talk
Tell us what your product does, which microcontroller it uses (or whether it's still to be chosen) and where you are. We reply within 24 business hours, with no commitment and under NDA if needed.
Book a meetingTell us what your device must do: we'll propose an architecture, a microcontroller and a timeline in a 30-minute call.
Book 30 minutes Write to us