Skip to main content
Synergetic SoftwareBuild Together
Service 03 · Standardised ECU software

AUTOSARServices

We provide AUTOSAR engineering services for automotive software teams building scalable, standardised and production-ready ECU software.

Layered software architecture

SW-CSW-CSW-CSW-C

Application

RTE

Runtime Environment (RTE)

ServicesECU abstractionComplex drivers

Basic Software

MCAL

Microcontroller Abstraction (MCAL)

Hardware

Microcontroller

Tier-1 suppliersOEM software teamsElectric mobility
Practice overview

StandardisedECUsoftware,configuredwithcare.

AUTOSAR rewards teams that get configuration, integration and timing right. We provide hands-on Classic and Adaptive engineering from basic-software configuration and MCAL support to RTE integration, diagnostics and bootloaders.

Discuss your ECU programme

Tier-1 suppliers

Series ECU software delivered to supplier-grade process and cadence.

OEM software teams

Platform and vehicle-level integration across programmes.

Electric mobility

Drive, battery and charging ECUs on electric platforms.

Autonomous & ADAS platforms

High-performance Adaptive compute for ADAS and autonomy.

Two platforms

Choose the platform  that fits the product.

Choose a platform to see where it fits. We engineer both.

Deeply embedded ECUs

AUTOSAR Classic

  • Statically configured at build time
  • Deterministic, real-time operating system
  • Signal-based communication
  • Typical for powertrain, chassis and body ECUs

Best whenYou need hard real-time, deterministic control.

High-performance computing

AUTOSAR Adaptive

  • Service-oriented, dynamically deployable
  • POSIX-based, C++ applications
  • Service-based communication and updates
  • Typical for ADAS, gateways and connected compute

Best whenYou need high compute, updates and service-oriented design.

Expertise includes

The disciplines  we configure.

Six areas that decide whether an AUTOSAR stack behaves, each one drawn as a skyline of its own.

BsConfiguration

  

Configuring communication, diagnostic, memory and mode-management modules for the target ECU.

Configuration journey

Working down  the stack.

Scroll through the phases the stack shows where in the architecture the work is happening.

Application
Runtime Environment (RTE)
Basic Software
Microcontroller Abstraction (MCAL)
Microcontroller

Phase

  1. Platform assessment

    We review the target MCU, the stack vendor and the ECU function to define the AUTOSAR scope and configuration strategy.

  2. Configuration & MCAL

    Basic-software modules and MCAL are configured, with complex drivers added where the standard modules do not reach.

  3. RTE & application integration

    Software components are mapped through the RTE, and runnables, ports and timing are integrated with the basic software.

  4. Diagnostics, boot & test

    Diagnostic services, bootloading and stack behaviour are tested, with defects traced back to configuration or code.

Deliverables & standards

A configuration package  ready to build.

sheet_01.arxml

Configured BSW and MCAL projects ready to build

✓
sheet_02.arxml

RTE and software-component integration

✓
sheet_03.arxml

Diagnostic, memory and communication configuration

✓
sheet_04.arxml

Bootloader and flashing support

✓
sheet_05.arxml

Configuration documentation and test results

✓

Hover or tap to spread the package.

Platform & toolchain

Platforms
AUTOSAR Classic · AUTOSAR Adaptive
Basic software
COM · Diagnostics (Dcm / Dem) · NvM · ECU state management
Low level
MCAL · Complex drivers · Bootloader (UDS flashing)
Tooling
BSW configuration suites · RTE generators · Code generation
Outcomes

Protection,  layer on layer.

Layer

Standards-aligned software

Configuration that follows the specification, easing reuse across platforms and variants.

1
Layer

Fewer integration cycles

Stack behaviour is verified early so application teams build on solid ground.

2
Layer

Classic and Adaptive covered

One partner for both deterministic ECUs and service-oriented platforms.

3
Engagement models

Choose how we  work together.

Five ways to engage on autosar services pick the one that fits your roadmap.

Hover or tap a card to turn it over.

Questions

Ask.  Then decide.

The questions teams ask us most answered without the sales gloss.

Answer

Do you support both Classic and Adaptive?

Yes. We engage on AUTOSAR Classic for deeply embedded ECUs and AUTOSAR Adaptive for high-performance, service-oriented platforms.

Future Engineering
What’s nextEngineering Partnership Available

Tell us what you are building.

Whether it is embedded software, AUTOSAR, ECU engineering or a full device-to-cloud product our teams will help you identify the right solution path.

Your solution pathPaused

I'm building…

  1. Requirements & architecture

    Systems Engineering

  2. Firmware, drivers & middleware

    Embedded Software

  3. Diagnostics & communication stacks

    Automotive Software

  4. ECU testing & validation

    V&V and Test Automation

Suggested engagement

Project-based delivery

Start this path