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 & services

Rapita Verification Suite (RVS)

  RapiTest - Unit/system testing  RapiCover - Structural coverage analysis  RapiTime - Timing analysis (inc. WCET)  RapiTask - Scheduling visualization  RapiCoverZero - Zero footprint coverage analysis  RapiTimeZero - Zero footprint timing analysis  RapiTaskZero - Zero footprint scheduling analysis  RapiCouplingPreview - DCCC analysis

Multicore Verification

  MACH178  MACH178 Foundations  Multicore Timing Solution  RapiDaemons

Engineering Services

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

Industries

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

Other

RTBx Mx-Suite Software licensing Product life cycle policy RVS Assurance issue policy RVS development roadmap

Latest from Rapita HQ

Latest news

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
Magline joins Rapita Trailblazer Partnership Program to support DO-178 Certification
View News

Latest from the Rapita blog

How to certify multicore processors - what is everyone asking?
Data Coupling Basics in DO-178C
Control Coupling Basics in DO-178C
Components in Data Coupling and Control Coupling
View Blog

Latest discovery pages

control_tower DO-278A Guidance: Introduction to RTCA DO-278 approval
Picture of a car ISO 26262
DCCC Image Data Coupling & Control Coupling
Additional Coe verification thumb Verifying additional code for DO-178C
View Discovery pages

Upcoming events

Avionics and Testing Innovations 2025
2025-05-20
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

Rapita Systems - Safety Through Quality
Simulation for the Motorola 68020 microprocessor with Sim68020
AI-driven Requirements Traceability for Faster Testing and Certification
Multicore software verification with RVS 3.22
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

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

Working at Rapita

Careers

Careers menu

  • Current opportunities & application process
  • Working at Rapita
Back to Top Contact Us

There are how many sources of interference in a multicore system?

Breadcrumb

  1. Home
Daniel Wright & Christos Evripidou
2022-08-02

Multicore processors are being used more and more in the development of critical embedded electronics, including avionics and automotive electronics. This is due to increasing demands on application functionality, the improved SWaP (size, weight and power) characteristics of these processors, and the increasing difficulty in sourcing single core processors.

One of the main challenges in the adoption of multicore processors in critical electronics systems is that software running on one core can affect the execution of software running on another core. Multicore platforms are inherently non-deterministic with regards to their timing behavior, which poses a challenge for certification e.g. in accordance with DO-178C and AC 20-193, AMC 20-193 or CAST-32A guidance for aerospace software. Platform features that contribute to non-determinism are known as interference channels (Figure 1). These features can affect the ability of hosted software to meet its requirements. Some interference channels are obvious, but others are a little harder to identify. In this post, we discuss some of the better and less well-known sources of interference in multicore systems, using the NXP® T2080 processor as an example.

 
Image showing multicore interference
Figure 1. Interference can result from resources used by different cores in a multicore system
 

Types of interference

Interference channels can be classified in three categories: direct, indirect, and unknown.

Examples of direct interference channels include shared on-chip resources such as shared caches, buses and memory management units, and off-chip resources such as I/O devices. Each shared resource may have multiple interference channels associated with it. The T2080 features an L2 cache that is shared across the four e6500 cores (Figure 2). Examples of direct interference channels relating to the L2 cache include one core causing the eviction of another core’s data from the cache, and the L2 cache having a limited bandwidth that is saturated by the four cores accessing the cache simultaneously.

 
Image showing NXP T2080 board architecture
Figure 2. NXP T2080 board architecture (image used with permission from NXP)
 

An example of an indirect interference channel on the T2080 is the potential slowdown induced by an excess of snoop requests on private caches due to cache coherency operations (Figure 3). Cache coherency is a mechanism by which shared data that gets loaded in private caches is updated to ensure that it is consistent with the data in main memory (depending on the configuration of the cache). Typically, when a core accesses shared data, the cache coherency mechanism will trigger snoop requests in order to detect any data in caches that needs to be invalidated.

 
Image showing how snoop requests can cause multicore interference
Figure 3. Snoop requests by cache coherency mechanisms are an example of indirect interference channels
 

Unknown interference channels are typically due to undocumented platform features. An example of these could be differences in the core’s performance and/or sensitivity to multicore interference due to the physical memory layout.

Identifying interference channels

The interference channels present in a platform depend on the chip and board architecture, the critical configuration settings of the system, which off-chip devices are being used, and how they are being used. For DO-178C certification in line with AC 20,193 or AMC 20-193 guidance, all the active interference channels in a multicore system must be identified and considered.

Identifying the potential interference channels in a specific system requires access to be available to comprehensive documentation describing multicore hardware from board and chip manufacturers and RTOS vendors, and the input of specialized engineers. The number of interference channels in a multicore system may be larger than you’d expect – having run a few projects involving the T2080, we’ve identified more than 150 potential interference channels on this system, depending on the configuration settings and peripherals used.

Learn more about interference

Do you need to identify the sources of interference on your system, or want to know more about sources of interference? Rapita’s MACH 178 solution and Multicore Timing Solution can help you.

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
  • 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
    • Automotive Software Testing
    • Certifying eVTOL
    • DO-178C
    • AC 20-193 and AMC 20-193
    • ISO 26262
    • What is CAST-32A?

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