Premium
ECU Inter‐processor data communication End to End verification in Autosar for achieving Functional Safety Goals
Author(s) -
Gowda Jagadish Narayan
Publication year - 2019
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2019.00698.x
Subject(s) - autosar , functional safety , automotive industry , communication source , computer science , embedded system , software , process (computing) , software engineering , engineering , operating system , computer network , aerospace engineering
Safety is absence of unreasonable risk. Functional safety emphasis to handle unintended behavior of the system. ISO26262 recommends the process and development of electrical components in automotive vehicle weighing less than 3000kg. Features are assigned with Automotive safety integrate levels (ASIL) A,B,C and D by performing Hazard Analysis and Risk Assignment(HARA). ISO 26262 recommends integrity of data communicated between sender and receiver components which handles data associated with ASIL features. This is achieved by developing each software or hardware components in compliance with ISO26262 ASIL recommended process and implementation. The process requires lot of effort to develop and validate each software component as per ISO26262 recommendations. This is more challenging when data integrity needs to be maintained between sender and receiver components which resides on two different microprocessors in the ECU. Also, it is more challenging to achieve freedom from interference between QM (quality managed) and ASIL feature software with in the software or hardware components. This paper detailed the decomposition of ASIL as per ISO‐ 26262 and exploring the end to end verification methods in AUTOSAR (Automotive Open System Architecture) to achieve safety goals. This paper considers achieving data integrity between two microprocessors in infotainment. This paper highlights the software components on sender and receiver that must comply to ISO26262 and recommendations, instead of developing all software and hardware components as per ISO 26262.