Firmware is what turns a board into a product. It also decides how reliable, updatable and secure that product is over its whole life. We write embedded firmware for microcontrollers and SoCs, and we design security in from the first architecture decision, not as a patch at the end.
What we develop
- Bare-metal firmware and RTOS-based applications for a wide range of microcontrollers and SoCs.
- Drivers and board support for sensors, displays, memories, power management and communication peripherals.
- Connectivity: Bluetooth Low Energy, Wi-Fi, Ethernet, CAN, RS-485, USB and common industrial protocols.
- Bootloaders and over-the-air or wired update mechanisms.
- Low-power strategies for battery-operated devices.
Cybersecurity designed in
Connected products must be secure throughout their life, and regulation increasingly expects it. For example, European rules such as the cybersecurity requirements of the Radio Equipment Directive and the Cyber Resilience Act set obligations for manufacturers. We design firmware and hardware so these expectations can be met, although we do not issue certifications ourselves.
In practice that means working through questions such as:
- What needs protecting, and who might attack it? We start with a simple threat analysis.
- Secure boot, so only trusted firmware runs on the device.
- Signed and verified firmware updates, with a recovery path if an update fails.
- Safe storage of keys and credentials, using hardware security features where the chosen chip offers them.
- Secure communication with authentication and encryption, and sensible defaults instead of shared passwords.
- Reducing the attack surface: disabling debug interfaces and unused services in production units.
How we work
We agree the architecture with you first, then develop in small increments that can run on the target hardware early. Code is structured, version controlled and documented so your team can maintain it. We test on real hardware, and where useful we add automated tests to catch regressions.
What you receive
- Firmware source code with build instructions and documentation.
- A documented update and security concept for the device.
- Test results and a list of known limitations.
Frequently asked questions
Can you work with the microcontroller we already chose?
Usually yes. We also help compare candidates when the choice is still open, including their security features.
Do you test the finished product for cybersecurity compliance?
We design for compliance and prepare the technical documentation you will need, but formal conformity assessment is carried out by the appropriate notified bodies or laboratories. See also test and validation.