White paper: Root of Trust in the software-defined vehicle


Nothing works until everything works.

Software with a documented origin

ECU software developed and maintained by Diadrom in Sweden, delivered with the records that purchasing and compliance teams ask for.

Illustration, AI-generated: an ECU on a test bench with a debug cable and a CAN interface.

The question has changed

Vehicle manufacturers now have to show where the software in a connected vehicle comes from: who designed it, who supplies it and who maintains it.

Rules such as the US Connected Vehicles Rule ask for it directly. UN R155 and R156 ask for control over the supply chain and over every software update.

The question does not stop at the vehicle manufacturer. It is passed down to every supplier of an electronic control unit.

What it means for a programme

A programme can be technically ready and still be held up, because the origin of the software cannot be documented.

The questions tend to arrive late, close to start of production. They cover the whole life of the unit: development, deliveries, updates in the plant and updates in the workshop.

Answering them afterwards is slow. Building the answers in from the start is not.

Three ways we work

  1. 1

    New development

    We develop bootloader, diagnostics and communication software for your ECU, to the vehicle manufacturer's specification. Every release is delivered with a software bill of materials in the format the manufacturer requires.

  2. 2

    Maintenance takeover

    We take over the maintenance of existing software: corrections, updates and releases, for the full life of the programme, through to the last delivery.

  3. 3

    Origin documentation

    We document what the software contains, where it was built and who has worked on it, so that the question can be answered with records instead of assurances.

For the engineering team

Taking over or replacing software in a running programme is an engineering task before it is a documentation task. These are the areas we work in:

Close-up of a printed circuit board with integrated circuits and solder joints
Photo: Alexandre Debiève, Unsplash
  • Diagnostics: UDS and DoIP communication, diagnostic content and tooling.
  • Software download: flashing in the plant and in the workshop, with the bootloader and the tools as one chain.
  • Bootloader and secure boot: our own bootloader, with secure boot and HSM in production since 2014.

A first step is usually a technical review of what exists today: code, build environment, interfaces and open issues. It gives both sides a realistic picture of what a handover takes.

One example

Between 2017 and 2019 we delivered the bootloader for a parking assistance camera to a global supplier of vehicle safety systems. The work followed the unit from development into production.

Why Diadrom

Diadrom is a Swedish specialist in diagnostics, bootloaders and embedded software for vehicles. We work as a small, dedicated team that stays with the programme.

Our own products, Bootloader, Diag Com Stack and Encrypt, are licensed per programme and maintained by the same engineers who wrote them.

  • 25+

    years in diagnostics and embedded software

  • 250,000+

    vehicles in production running our software

  • 2014

    secure boot and HSM in production since

  • 0

    bricked units since 2016

  • ISO 9001

    and ISO 14001 certified

Our origin statement

One page that states who we are, where our software is written and how it is maintained. It is the document purchasing usually asks for first.

An ECU in an aluminium housing beside a printed release record and a signed tag
Illustration, AI-generated

Tell us about your programme

Leave your work email and we will get in touch.

We use your address to reply to you, nothing else. Privacy notice.

This page describes how Diadrom works. It is not legal advice. Whether a specific vehicle programme meets a specific regulation is decided by the vehicle manufacturer and its advisers.