Automotive & Mobility

Automotive Embedded & AUTOSAR

ECU software that ships. We configure Classic and Adaptive AUTOSAR stacks, develop BSW and MCAL layers, integrate application software, and stay on the programme until the build passes the OEM gate.

Request a quote All automotive services

Overview

Production-grade ECU software, from stack configuration to release

Part of our Automotive & Mobility Engineering practice.

Most embedded programmes do not fail on the algorithm. They fail in integration — a BSW parameter that was never tuned, a diagnostic session that times out, a CAN matrix that drifted from the DBC three sprints ago.

Our engineers work inside your toolchain and your process. We pick up a Vector, ETAS or EB stack, configure it against your ARXML, integrate the application layer, and stay through flashing, calibration and the validation cycle.

Capabilities

What we deliver

Classic AUTOSAR

BSW configuration across MCAL, COM, DCM, DEM, NvM, WdgM and OS. RTE generation, SWC contract and internal behaviour definition, full ARXML authoring and merge.

Adaptive AUTOSAR & SOA

ara::com service interfaces, SOME/IP and DDS transport, Execution and State Management, and migration paths from signal-based CAN designs to service-oriented architectures.

MCAL & driver development

Microcontroller abstraction layer configuration and custom driver development on AURIX, S32, RH850 and Renesas targets, including complex device drivers.

Communication stacks

CAN, CAN FD, LIN, FlexRay, Automotive Ethernet, SOME/IP and DoIP. Gateway routing, network management, PDU routing and bus-load analysis.

Diagnostics

UDS (ISO 14229) and OBD implementation, DTC and freeze-frame design, DEM/DCM configuration, ODX authoring and diagnostic test-case validation.

Application & model-based design

MATLAB/Simulink and TargetLink models, autocode generation, MISRA C:2012 compliant handwritten C/C++, and integration of supplier-delivered SWCs.

How we work

A predictable path from first call to handover

No two engagements are identical, but the shape is consistent — so you always know what happens next and what you get at the end of each stage.

Engagement models

Assess the baseline

We review your ARXML, CAN matrix, tool versions and existing build. You get a written gap list and a risk register before anyone writes code.

Configure and integrate

Stack configuration, RTE generation and application integration run in short cycles against your CI, so the ECU is always in a flashable state.

Validate on target

Unit and integration tests, static analysis, HIL runs and diagnostic validation on real hardware — not just on the desk.

Release and sustain

Release notes, traceability, defect closure and a support window. We hand over documentation your auditors can actually use.

Outcomes

What changes for you

Fewer integration surprises: gaps are found in week one, not at the OEM gate.
Traceability that survives audit — requirements to code to test, maintained as you go.
MISRA C:2012 and static-analysis compliance built into the pipeline, not bolted on.
A team that can scale up for a launch push and back down afterwards.

Tools & standards

What we work with

Vector DaVinci
EB tresos
ETAS ISOLAR
MATLAB / Simulink
TargetLink
CANoe / CANalyzer
Lauterbach TRACE32
Vector CANape
Polyspace
QAC
Green Hills
Infineon AURIX
NXP S32
Renesas RH850
Classic AUTOSAR
Adaptive AUTOSAR

Questions

Frequently asked

Do you work with a specific AUTOSAR vendor stack?

We are vendor-neutral. Our engineers have delivered on Vector, EB tresos and ETAS stacks, and we work inside whichever one your programme has already licensed rather than pushing you to change.

Can you take over an ECU mid-programme?

Yes, and it is a common request. We start with a two-week assessment so we inherit the code base with our eyes open, then agree a stabilisation plan before taking delivery responsibility.

How does this relate to your cybersecurity and testing services?

They are sibling practices in the same pillar. Most ECU programmes run all three together — see Automotive Cybersecurity and V-Model Testing & ASPICE.

Let’s scope your next build.

Tell us what you are trying to ship. We will come back with an approach, a team shape and an honest estimate — we aim to reply within two working days.

Request a quote Browse services