100% found this document useful (1 vote)
282 views21 pages

Automotive ECU SW Function Development Chart Template

Feature development plan reference for an electronic control unit that is part of a mechatronics system. Please only download in excel format for full content view.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
282 views21 pages

Automotive ECU SW Function Development Chart Template

Feature development plan reference for an electronic control unit that is part of a mechatronics system. Please only download in excel format for full content view.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 21

Introduction--Autosar based Software

1.This document attempts to outline a developme


for instance an electronic control unit(ECU) for a su
2.It specifically dwells into a plan for autosar based
the norm for autonomous vehicles.
3.This also provides an overview of how Software
4.This plan details the extent of Software developm
3. This is a good engineering development referen
systems to car manufacturers (shifting to electric v
employees in the united states through product off
4.The plan could be applied for a mechatronic brak
as required.
5.Target Audience would be project managers try
manufacturer developing electric or autonomous v
ction--Autosar based Software Infrastructure Plan for an ECU part of Automotive Mechatronic system.
cument attempts to outline a development plan to integrate Software features to a component of a Automotive mechatronic system like
ce an electronic control unit(ECU) for a suspension controller.
fically dwells into a plan for autosar based ECUs which are prevalent in electric vehicle and modern gasoline vehicle electrical architectures
for autonomous vehicles.
o provides an overview of how Software feature integration is split and handled at initial stages of functional development for an ECU.
n details the extent of Software development in an autosar based automotive ECU.
a good engineering development reference plan for businesses trying to shift from supplying traditional mechanical systems to modern me
o car manufacturers (shifting to electric vehicle or intelligent vehicle technologies) to stay relevant in the rapidly changing market and reta
s in the united states through product offering repositioning.
n could be applied for a mechatronic braking ,steering or a suspension control system using an electronic control unit and adapted to othe
d.
Audience would be project managers trying to define direction of a new mechatronics product that the business tries to develop and sell t
urer developing electric or autonomous vehicles.
Mechatronic system.
motive mechatronic system like ,

e vehicle electrical architectures and are

al development for an ECU.

echanical systems to modern mechatronic


apidly changing market and retain their

ontrol unit and adapted to other systems

siness tries to develop and sell to a car

Author : Bargav Srinivasan


Date: 2.21.2018
Version 1: 21.2.2018

INFRASTRUCTURE ROLLOUT PLAN

Automotive Supplier Delivery date to the car manufacturer

[%] implemented / (Total)


[%] (implemented+under construction) / (Total)
[%] under construction / (Total)
[%] not started + planned/(Total)

Total items : planned+implemented+under construction


planned
under construction
implemented
to be clarified

GENERAL-Autosar Software implementation packets for the control Unit


ECUEctractPackage versions planned for the controller development-Application Software
xxx-Version number
xxx-Version number
xxx-Version number
xxx-Version number
xxx-Version number
xxx-Version number
ECUEctractPackage versions planned for the controller development-Bootloader Software
xxx-Version number
xxx-Version number
xxx-Version number
SUM package version(list standardized utility module versions from vector for example is listed below
1.28.00
1.29.02

POWER MODING
Proper Wake-Up (All Wake-Ups)
Proper Shutdown, including Partial Networks
Power Moding (Acc, Run, Crank …)
CYBERSECURITY (MAC)
General
Unique ECU_ID Downloaded from GM Servers
Unique UNLOCK_KEY Downloaded from GM Servers
Unique MASTER_KEY Downloaded from GM Servers
Diagnostic identifier Read ECU_ID
Controller Hardening
MMU/MPU Usage
Privilege Level Usage
Secure Programming
Programming via DPS/GBFTT
SBAT(secure bypass authorization ticket) Support to Bypass Signature Validation (Programming Unsigned Files)
Diagnostic identifier Write SBAT into the ECU
Diagnostic identifier Read Read ECU_NAME and SUBJECT_NAME in the Bootloader
Programming with Signature Validation (Programming Signed Files)
Secure Unlock (UDS - Service $27)
Support ALL Unlock Levels with Proper Authorization
SBAT Support to Keep Module Unlocked (SBAT Validation in Application)
Secure Diagnostics
Implement ALL Rationality and Security Checks as Defined in Open diagnostic File(s)
Message Authentication-Cybersecurity requirements mandating secure encryption/decryption
MAC Tx
Compliance with ALL Tx frames defined in MACT
Diagnostic identifier Read Message Authentication Anti Replay Counters
MAC Rx
Bypass Message Authentication for Received Messages
Compliance with ALL frames defined in MACT
Routine identifier Provision Security Peripheral General Keys
Diagnostic identifier ReadECU Key Provision State Flag
Diagnostic identifier Read Read ECU Key Configuration Data
Routine Identifier ECU Key Provision Data (Get Unencrypted MACT for the ECU)
Routine Identifier Secured ECU Key Provision Data (Get Encrypted MACT for the ECU)
Diagnostic trouble code Key Table Not Provisioned - No SubType Info
Diagnostic trouble code Security Peripheral Perfromance - incorrect operation
Dianostic trouble code Unable to Authenticate Serial Data - No SubType Info
MAC Failsofting Action (Loss of Comm)
Message Authentication for Tx PDUS (MAC support)-Signals sent by the component
Vehicle top speed limiting-
lateral /longitudinal acceleration
Message Authentication for Rx PDUS (MAC support)- Signals received by the component
Backup System Power Mode
Roll Pitch Yaw-
Brake pressure
Steering wheel angle
Vehicle power mode
Average vehicle speed
CAN FD
BTR Setting
ARXML Compliant
Basic Send & Receive Messages
Initial Hardware support for CAN FD
Wake Up on all traffic (not PN)
ISO CAN FD Frame Format
interleave CAN FD and Classical CAN Messages
Wake up on PN message, not all traffic
Programming support with CAN FD
Programming through gateway
STD CAN
BTR Settings
Basic Send & Receive Messages
Flash Programmable Capable using car manufacturing tool
Programming Capable through gateway
ARXML Compliant
FLASH PROGRAMMING
Flash Programming on the component using car manufacturer tool
Flash Programming Other (USB)
OTA-Over the air flashing ,using wifi.
Installation
Compression (refer technical requirement provided by car manufacturer)
Delta Client – or Bit Diff (vehicle ecus communicating in the same bus with this component ONLY)
Learned Values protection or retention
Backup System Power Mode Protected: Remote Programming Active Authenticated
Routine identifier: Diagnostic initiate Extended reflash
Routine identifier: Check Programming Dependencies
Routine identifier: OTA(Over the Air) Programming State Flag Control
Are all flash programmable micros flashable with car manufacturing tool? If not, what release?

DIAGNOSTICS:
status:
Controller_diagnostics_state < v0.4
Application
Inputs
CAN input signal processing
Internal sensor reading (SPI)
External sensor reading (PWM)
SBC driver integration

Outputs
Powerstage integration (current output)
CAN output integration

Control functions
Application mode
DIAG current control
CUR Current cotrol loop
Application control loop
Mode Control (DIAG)
Mode Control (CAN)

Diagnostic integration
Diagnostic state control
Logistic data
Security access (Seed & Key)
IO control: CUR Calibration
IO control: Position Learning
IO control: Current Output

Error handling-Fault handling for the component


Project specific error codes
Diagnostic fault codes Test conditions
Diagnostic fault code required conditions
Internal error mapping for power stages and pcb components to customer diagnostic fault codes
CAN signal error evaluation
CAN cybersecurity error evaluation
Car battery supply error detection
Internal Valve errors detection
Sensor errors detection
OEM Development Milestone OEM Development Milestone

Initial Bench build Electrical verification bench build

76% 60%
100% 88%
24% 28%
0% 12%

49 67
0 8
12 19
37 40
10 8

Worksheet version: 14.0 Worksheet version: 19.0

implemented
not supported implemented
not supported not supported
not supported not supported

not supported implemented


not supported not supported

implemented implemented
implemented under construction
implemented implemented

implemented implemented
implemented implemented
implemented implemented
implemented planned

not supported not supported


not supported not supported

not supported not supported


implemented implemented
implemented planned
implemented planned
implemented implemented

not supported under construction


not supported under construction

not supported to be clarified

under construction planned


not supported not supported
not supported not supported
implemented to be clarified
not supported not supported
not supported not supported
implemented implemented
not supported implemented
not supported under construction
implemented under construction
not supported under construction
not supported under construction
not supported under construction
not supported under construction
not supported not supported

not supported to be clarified


not supported to be clarified

not supported planned


not supported to be clarified
not supported to be clarified
not supported planned
not supported planned
not supported planned

implemented implemented
implemented implemented
implemented implemented
implemented implemented
implemented implemented
to be clarified implemented
to be clarified implemented
under construction implemented
not supported not supported
not supported not supported

implemented implemented
implemented implemented
implemented implemented
to be clarified to be clarified
implemented implemented

not supported under construction


not supported not supported

to be clarified not supported


implemented implemented
to be clarified not supported
to be clarified not supported
to be clarified not supported
not supported not supported
to be clarified implemented
to be clarified implemented
to be clarified not supported

implemented implemented

not supported not supported


implemented implemented
under construction to be clarified
implemented implemented

implemented implemented
not supported under construction

implemented implemented
under construction implemented
implemented implemented
under construction implemented
not supported not supported
not supported not supported

not supported under construction


implemented implemented
implemented implemented
implemented implemented
not supported not supported
implemented implemented
under construction under construction
under construction under construction
under construction under construction
under construction under construction
under construction under construction
under construction under construction
implemented implemented
implemented implemented
under construction under construction
OEM Development Milestone OEM Development Milestone OEM Development Milestone

Vehicle Engineering Build Release Pre Production Builds Production Builds

67% 77% 76%


96% 93% 88%
30% 16% 12%
4% 7% 12%

81 94 90
3 7 11
24 15 11
54 72 68
5 3 3

Worksheet version: 19.0 Worksheet version: YY

implemented

implemented implemented implemented

implemented implemented
planned implemented

implemented implemented
not supported planned implemented

implemented implemented implemented


implemented implemented implemented
implemented implemented implemented

implemented implemented implemented


implemented implemented implemented
implemented implemented implemented
implemented implemented implemented

not supported planned planned


to be clarified to be clarified to be clarified

not supported implemented implemented


under construction implemented implemented
under construction implemented implemented
under construction under construction under construction
implemented implemented implemented

implemented implemented implemented


implemented implemented implemented

under construction under construction under construction

under construction implemented implemented


under construction implemented implemented
under construction implemented implemented
under construction implemented implemented
under construction implemented implemented
under construction implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
under construction implemented implemented
under construction implemented implemented
not supported under construction under construction
not supported under construction under construction
not supported under construction under construction
not supported planned planned

implemented implemented implemented


implemented implemented implemented

implemented implemented implemented


to be clarified implemented implemented
to be clarified implemented implemented
under construction implemented implemented
under construction implemented implemented
under construction to be clarified to be clarified

implemented implemented implemented


implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
not supported implemented
not supported under construction under construction

implemented implemented implemented


implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented

not supported implemented implemented


not supported not supported not supported

planned planned planned


implemented implemented implemented
planned planned planned
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
not supported under construction planned

implemented implemented implemented

under construction under construction planned


implemented implemented implemented
to be clarified implemented implemented
implemented implemented implemented

implemented implemented implemented


to be clarified to be clarified to be clarified

implemented implemented
implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
planned under construction implemented
under construction under construction planned

implemented implemented implemented


implemented implemented implemented
implemented implemented implemented
implemented implemented implemented
not supported not supported not supported
implemented implemented implemented
under construction planned under construction
under construction under construction under construction
under construction under construction under construction
under construction implemented planned
under construction under construction under construction
under construction under construction under construction
implemented implemented planned
implemented implemented planned
under construction under construction planned
Questions and Answers(In blue) for interface between OEM engineers and tier-1 engineers
d tier-1 engineers
implemented
under construction
not supported
to be clarified
planned
The feature is implemented
The feature is under contruction
The feature is not supported / not planned / not to be delivered
The feature need clarification with OEM
The feature should be implemented in given milestone

You might also like