1 Overview

E2E (End-To-End) is a safety module proposed by AUTOSAR for the functional safety standard ISO26262. It is a data protection protocol/ mechanism designed to prevent faults (HW/SW) that may exist in the communication link for safety-related data. It is applicable to various network structures: CAN, CANFD, FlexRay, Ethernet, etc.

The testing of E2E mainly includes communication testing between SWCs (Software Components). However, according to the current market situation, with the increasing complexity of the AUTOSAR architecture, the design and implementation of E2E testing have become more complex, and the creation and management of test cases have become more challenging. Despite designing numerous test cases, it may still not cover all boundary conditions and potential errors, leading to some issues going unnoticed during actual use. The testing workload for the hundreds or thousands of E2E messages, along with the corresponding DTC (Diagnostic Trouble Codes) tests, is substantial and consumes a significant amount of human resources.

To address these issues, Shanghai ZC Technology Co., Ltd. provides comprehensive E2E testing services, which can effectively improve customers' E2E testing efficiency and reduce the costs associated with E2E testing.

2 Test points

E2E testing primarily focuses on communication testing between SWCs (Software Components), with different testing strategies formulated based on various CRC (Cyclic Redundancy Check) verification methods. This includes, but is not limited to:

Ø  The use of DataID (Data Identifier)

Ø  Changes in Counter values

Ø  The calculation rules for CRC

Ø  Testing of related DTCs (Diagnostic Trouble Codes)

3 Test Bench and General Environment

Test Bench Architecture

4 Test Equipment Description

4.1 Hardware Requirements

ZC possesses a complete set of E2E testing equipment, which can effectively support the conduct of E2E testing.

4.2 Software Requirements

4.2.1 Testing Environment Software

Vector CANoe series tools, version Canoe12.0

4.2.2  TRACE32

5 E2E Testing Steps Example

5.1 The Upper Computer Simulates Sending E2E Messages

5.2   Observing Received Data for Verification via Debugger

5.3       The Upper Computer Receives Messages, Compares the E2E Data within the Messages, and Verifies the Correctness via In-House Tools.

For example, with ID: 0xDBC0040, using E2E - Profile05 as an example.

Step 1:Calculate the CRC value of the data, with an initial value of 0xFFFF.

Step 2: Calculate the CRC value of LowID in DataID, with the initial value being the value calculated in the first step: 0x50CF.

Step 3: Calculate the CRC value of HighID in DataID, with the initial value being the value calculated in the first step: 0x5479.

Final CRC value obtained: 0x50 0x73

5.4      Test Report

According to the AUTOSAR_CP_SWS2ETransformer specification and the testing requirements of customer E2E, design test cases and complete test reports using equivalence classes, boundary values, and other methods to ensure bidirectional traceability and consistency.

Click to download the product manual