Consultancy

Engineering engagements in FPGA acceleration and real-time signal processing.

Specialist engineering delivered against a written scope: FPGA acceleration, real-time signal processing, and modelling and verification for systems where determinism and throughput decide whether the design works at all.

Engagement types

What's on offer.

Each of these is grounded in work already done — see capabilities for the evidence behind them.

FPGA acceleration

Moving compute into fabric where determinism and throughput matter: RTL architecture from scratch, AXI4-Stream / AXI-Lite / AXI DMA integration, timing closure, and verification against reference models.

Real-time signal processing

Streaming DSP pipelines on FPGA fabric, from acquisition through to edge processing, verified against a reference model rather than assumed correct.

Modelling and simulation

Reference models built in MATLAB/Simulink or Python, with circuit-level modelling in SPICE. The implementation is checked against a physics-first model both before and after it is built.

Optimisation

A measure, model, re-architect, verify approach applied to existing systems — float-to-fixed conversion, latency reduction, and resource or points-of-failure reduction, with the trade-offs made explicit rather than assumed.

Power-aware embedded systems

Firmware for power-managed, field-deployed embedded systems: shutdown and wake-up sequencing, power-state control, and the practical constraints of running hardware somewhere it can't easily be serviced.

How it works

How an engagement runs.

Scope

The work is scoped in writing before it starts — the problem, the deliverables, the timescale, and any constraints — so both sides are working from the same understanding of what's being built.
Work

Progress is reported as the engagement runs, not only at the end. Confidentiality is expected on either side; NDAs are accepted as standard practice.
Deliverables

What's handed over depends on the scope, but typically includes RTL, firmware, models, test procedures, and documentation sufficient for someone else to pick up the work.
IP

Ownership of what's produced is agreed as part of the scope, in writing, before work begins.

Getting in touch

What a first conversation looks like.

Send the problem, the platform, and the timescale. What comes back is a straight assessment of whether it is a good fit — including, when that is the right answer, that the problem does not need an FPGA at all. There is no cost to asking.

Terms of engagement

The practical details.

Engagement shape: Fixed-scope project or day rate, depending on the work.
Location: Remote by default; on-site by arrangement. Based in the UK.
Confidentiality: NDAs accepted as standard practice.

Contact

Start the conversation.

Include the problem, the platform, and the timescale — it's enough to give an honest first read.

[email protected]