Your browser does not support JavaScript! Skip to main content
Free 30-day trial DO-178C Handbook RapiCoupling Preview DO-178C Multicore Training Multicore Resources
Rapita Systems
 

Industry leading verification tools

Rapita Verification Suite (RVS)

RapiTest - Functional testing for critical software RapiCover - Low-overhead coverage analysis for critical software RapiTime - In-depth execution time analysis for critical software RapiTask - RTOS scheduling visualization RapiCoverZero - Zero-footprint coverage analysis RapitimeZero - Zero-footprint timing analysis RapiTaskZero - Zero-footprint event-level scheduling analysis RVS Qualification Kits - Tool qualification for DO-178 B/C and ISO 26262 projects RapiCoupling - DCCC analysis

Multicore Verification

MACH178 - Multicore Avionics Certification for High-integrity DO-178C projects MACH178 Foundations - Lay the groundwork for A(M)C 20-193 compliance Multicore Timing Solution - Solving the challenges of multicore timing analysis RapiDaemon - Analyze interference in multicore systems

Other

RTBx - The ultimate data logging solution Sim68020 - Simulation for the Motorola 68020 microprocessor

RVS Software Policy

Software licensing Product life cycle policy RVS Assurance issue policy RVS development roadmap

Industry leading verification services

Engineering Services

V&V Services Data Coupling & Control Coupling Object code verification Qualification Training Consultancy Tool Integration Support

Latest from Rapita HQ

Latest news

Rapita partners with Asterios Technologies to deliver solutions in multicore certification
SAIF Autonomy to use RVS to verify their groundbreaking AI platform
RVS 3.22 Launched
Hybrid electric pioneers, Ascendance, join Rapita Systems Trailblazer Partnership Program
View News

Latest from the Rapita blog

How emulation can reduce avionics verification costs: Sim68020
Multicore timing analysis: to instrument or not to instrument
How to certify multicore processors - what is everyone asking?
Data Coupling Basics in DO-178C
View Blog

Latest discovery pages

Military Drone Certifying Unmanned Aircraft Systems
control_tower DO-278A Guidance: Introduction to RTCA DO-278 approval
Picture of a car ISO 26262
DCCC Image Data Coupling & Control Coupling
View Discovery pages

Upcoming events

IEEE SMC-IT/SCC 2025
2025-07-28
DASC 2025
2025-09-14
DO-178C Multicore In-person Training (Fort Worth, TX)
2025-10-01
DO-178C Multicore In-person Training (Toulouse)
2025-11-04
View Events

Technical resources for industry professionals

Latest White papers

Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP
Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
View White papers

Latest Videos

How to make AI safe in autonomous systems with SAIF
Rapita Systems - Safety Through Quality
Simulation for the Motorola 68020 microprocessor with Sim68020
AI-driven Requirements Traceability for Faster Testing and Certification
View Videos

Latest Case studies

GMV case study front cover
GMV verify ISO26262 automotive software with RVS
Kappa: Verifying Airborne Video Systems for Air-to-Air Refueling using RVS
Supporting DanLaw with unit testing and code coverage analysis for automotive software
View Case studies

Other Resources

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

 Multicore resources

Discover Rapita

Who we are

The company menu

  • About us
  • Customers
  • Distributors
  • Locations
  • Partners
  • Research projects
  • Contact us
  • Careers
  • Working at Rapita

Industries

  Civil Aviation (DO-178C)   Automotive (ISO 26262)   Military & Defense   Space

US office

+1 248-957-9801
info@rapitasystems.com Rapita Systems, Inc., 41131 Vincenti Ct., Novi, MI 48375, USA

UK office

+44 (0)1904 413945
info@rapitasystems.com Rapita Systems Ltd., Atlas House, Osbaldwick Link Road, York, YO10 3JB, UK

Spain office

+34 93 351 02 05
info@rapitasystems.com Rapita Systems S.L., Parc UPC, Edificio K2M, c/ Jordi Girona, 1-3, Barcelona 08034, Spain
Back to Top Contact Us

ED4I tool - generating diverse code automatically to satisfy ISO26262 requirements

2014-09-23

Is it possible to use diversity on a single processor to reliably detect hardware faults?

That's the thought that lead to research which resulted in ED4I, a technique to support error detection. How we got from this research to the point where cars on the road are now relying upon ECUs that have been developed using this technique is an interesting story.

The story starts a few years ago when one of our customers asked if we could do anything to help them use ED4I to automate how they generate diverse code of their embedded safety-critical control systems. Maintaining different variants of the same control system and having to maintain a diverse version was using up a lot of engineering work. If they could automate how diverse versions of their control algorithms were generated, then the customer could save a lot of precious time and effort.

What is ED4I?

ED4I stands for "Error Detection by Diverse Data and Duplicated Instructions", it was a technique published in 2000 by Nahmsuk Oh, Subahshish Mitra and Edward J. McCluskey from the Center for Reliable Computing, Stanford [1].

A common technique to detect temporary faults is to run the same program twice and see if you get the same results. ED4I is a variant on this, that detects permanent faults too.

ED4I works by running two similar but different versions of the software. Each version of the software performs the same basic computations but it uses different numbers in those calculations. This means that the data used in the computation uses different binary bits throughout its journey through the system architecture: memory, registers, data bus, arithmetic logic unit. Therefore a variety of faults in the hardware (temporary or permanent) can be detected.

Oversimplifying the theory a lot: if you scale (multiply) all the inputs to an algorithm by a constant value then the output you get is also scaled by the same value. There are a number of transformations that you need to make to the program to make this true. This presentation [2] has some simple explanations.

The scaling factor used is -2, which means that all the numbers in an algorithm are shifted and inverted. e.g.

 

    57 (0011 1001) becomes
  -114 (1000 1110)

The basic transformations needed to use this technique are concerned with comparisons (<, > etc), constants, multiplication and division:

An example of ED4I

/* Version 1 of computation */
x1 = 2;
y1 = 3;
z1 = x1 * y1
/* z1 is 6 */


/* Version 2 of computation */
x2 = -4; /* scale all constants */
y2 = -6;
z2 = x2 * y2 / (-2); /* transform multiplication by dividing by -2*/
/* z2 is -12 */

/* Compare results */

if (z1 != z2/(-2) )
{
  /* error detected */
}

There are, of course, lots of loose ends to tie up: constants, global variables, arrays, pointer arithmetic, types, overflow... the list goes on. Some of these are explained in [1]. These situations are handled automatically by our ED4I tool.

What did we do?

We wrote a tool which takes embedded C software and produces an ED4I version of certain functions by automatically applying the correct transformations, scaling constants, dealing with comparisons and all the other oddities.

The customer has used this several times on automotive applications as a fast way of getting redundant software versions to detect hardware faults. It turns out that this is an efficient and cost-effective way of getting a diverse version of software, suitable for certain ISO-26262 and AUTOSAR systems.

The real cost saving comes from being able to automatically generate diverse software without having to maintain multiple versions. This is especially important when you have many similar product variants generated from the same basic software source.

We are now doing some research in the VeTeSS project based on this, to understand how this technique can be applied more broadly. If you're interested, why not get in touch?

[1] http://www-crc.stanford.edu/crc_papers/CRC-TR-00-8.pdf
[2] http://www.cs.cornell.edu/courses/cs717/2001fa/lectures/ED4I%20Presentation.ppt

DO-178C webinars

DO178C webinars

White papers

Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis

Related blog posts

Going above and beyond the quality standards

.
2020-11-03

What’s the difference between a SIL and a DAL? How does it affect my Code Coverage?

.
2014-10-07

Major trends in automotive software development

.
2012-12-03

Explaining the RapiCover Tool Qualification Process

.
2012-06-14

Pagination

  • Current page 1
  • Page 2
  • Next page Next ›
  • Last page Last »
  • Solutions
    • Rapita Verification Suite
    • RapiTest
    • RapiCover
    • RapiTime
    • RapiTask
    • MACH178

    • Verification and Validation Services
    • Qualification
    • Training
    • Integration
  • Latest
  • Latest menu

    • News
    • Blog
    • Events
    • Videos
  • Downloads
  • Downloads menu

    • Brochures
    • Webinars
    • White Papers
    • Case Studies
    • Product briefs
    • Technical notes
    • Software licensing
  • Company
  • Company menu

    • About Rapita
    • Careers
    • Customers
    • Distributors
    • Industries
    • Locations
    • Partners
    • Research projects
    • Contact
  • Discover
    • Multicore Timing Analysis
    • Embedded Software Testing Tools
    • Worst Case Execution Time
    • WCET Tools
    • Code coverage for Ada, C & C++
    • MC/DC Coverage
    • Verifying additional code for DO-178C
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®
    • Data Coupling & Control Coupling
    • Aerospace Software Testing
    • DO-178C
    • Meeting DO-178C Objectives
    • AC 20-193 and AMC 20-193
    • Meeting A(M)C 20-193 Objectives
    • Certifying eVTOL
    • Cerifying UAS

All materials © Rapita Systems Ltd. 2025 - All rights reserved | Privacy information | Trademark notice Subscribe to our newsletter