Capabilities

Engineering services

Six disciplines, each backed by delivered projects rather than a capability statement. Everything listed here has been through a build: a board that was manufactured, firmware that shipped, or a production line that ran on it.

Firmware development
Embedded Linux
Hardware and PCB design
Wearables and wireless
Automotive and reverse engineering
Production tooling

Firmware development

Bare-metal and RTOS firmware for microcontroller platforms: device drivers, communication stacks, bootloaders and power management, developed against the hardware and validated on the bench.

Board bring-up, from first power-on to a booting image
Device drivers developed against the datasheet and verified with a logic analyser
Serial protocols, data serialisation and third-party protocol integration
Bootloaders, signed firmware updates and recovery of failed units
Sleep, wake and current consumption measured with a power profiler

Embedded Linux

Custom Linux distributions built with Yocto and Buildroot: bootloader, device tree, kernel drivers and the userspace applications above them, delivered as a reproducible build.

Yocto and Buildroot images with custom layers and recipes
u-boot, device tree and board support for new carrier boards
Kernel drivers and the userspace services that consume them
Packaging and update infrastructure for deployed fleets

Hardware and PCB design

Schematic design, multilayer PCB layout and hardware bring-up. Analog front ends, power stages and battery charging, specified for the process that will manufacture them.

Schematic capture and multilayer layout in Altium or DipTrace
Analog front ends, power stages and battery charging
Component selection against supply chain availability
Assembly troubleshooting, rework and failure analysis
Design for manufacture, and supervision of the first production build

Wearables and wireless

Low-power wireless devices over BLE, ANT+, sub-GHz and proprietary 2.4 GHz links. Current consumption is measured on a profiler and verified against the battery specification.

BLE, ANT+, sub-GHz and proprietary 2.4 GHz links
Low-power design verified with a power profiler
Charging, fuel gauge and battery behaviour across temperature
Antenna placement within a fixed enclosure
Certification support, including firmware changes required for compliance

Automotive and reverse engineering

Production tooling

Automated test equipment, production programmers and factory software. This is the work that determines whether unit 500 behaves identically to unit 5.

Automated test equipment firmware and the software that drives it
Production programmers, including custom implementations over the debug interface
Test fixtures and the pass criteria applied to them
Build systems, continuous integration and reproducible releases

Technology

Platforms and tools we work with

Not a wish list. These are the families, toolchains and instruments in current use, which is why a project does not begin with two weeks of learning the part.

Languages: C, C++, ARM assembly, Python, C#, Objective-C, Swift, Java
Microcontrollers: ST STM32 and Nordic nRF5 / nRF54, across the full range of each. Espressif ESP32, Raspberry Pi RP2040 and RP2350, NXP i.MX RT, Silicon Labs EFR32, Texas Instruments CC13xx and CC26xx, Microchip ATSAM
RTOS and Linux: Bare metal, Zephyr, FreeRTOS, TI-RTOS. Embedded Linux with Yocto, Buildroot, Bitbake, u-boot, kernel drivers and device tree
Radio and buses: BLE, ANT+, sub-GHz, 2.4 GHz proprietary, Wi-Fi, GSM and GPS, CAN, LIN, RS-485, Modbus, SPI, I²C, UART, USB, OneWire, Ethernet and TCP/IP
Build and test: Make, CMake, CTest, Ceedling, GoogleTest and gmock, GCC, Clang, IAR, Segger tools, Docker, Git and CI pipelines
Hardware bench: Altium and DipTrace, oscilloscopes, logic analysers, power profilers, signal generators, rework and soldering, automated test equipment
Reverse engineering: Ghidra, the ARM debug interface, logic analysis, schematic recovery from a finished board, custom programmers

Engagement models

Four ways to start

Most engagements start small and expand once the technical risk is understood. Select whichever matches your situation.

How we work

You have a design and need a second opinion

Technical assessment

We review the schematic, the firmware and the test setup, and report what we would change, what we would keep, and in what order. In some cases the conclusion is that the design is sound and the problem is elsewhere.

You need to prove feasibility

Proof of concept

A single technical question answered on the bench, normally on development kits and a wired-up board. The deliverable is the answer and the evidence supporting it.

You need working units

Prototype and low-volume production

Custom board, firmware, enclosure fit and a first batch of assembled units. Low volume is our standard scope rather than an exception to it.

A project has stalled

Project recovery

Loss of the original engineer, a failed board revision, or a defect that cannot be reproduced. We regularly take over existing code and existing hardware.

Send us the technical problem

A schematic, a failing board, an undocumented protocol, or a product that exists only as a specification. Describe it and you will get a direct answer on whether it falls within our scope.

Start a conversation View our work