Key AUTOSAR Methodology and RTE - ArtistDesign NoESIG RTE MO INT Queue SEND MO Actuator SWC-1SWC BSW...
7
8 © Dr. Kai Richter, Symtavision GmbH The AUTOSAR Timing Model - Status and Challenges ARTIST2 Workshop, 23.3.06 Innsbruck Key AUTOSAR "Methodology and RTE" Flexible mapping of software components ... ... enabled by standardized run-time environment (RTE)
Transcript of Key AUTOSAR Methodology and RTE - ArtistDesign NoESIG RTE MO INT Queue SEND MO Actuator SWC-1SWC BSW...
8© Dr. Kai Richter, Symtavision GmbHThe AUTOSAR Timing Model - Status and Challenges ARTIST2 Workshop, 23.3.06 Innsbruck
Key AUTOSAR "Methodology and RTE"
Flexible mapping of software components ...
... enabled by standardized run-time environment (RTE)
9© Dr. Kai Richter, Symtavision GmbHThe AUTOSAR Timing Model - Status and Challenges ARTIST2 Workshop, 23.3.06 Innsbruck
ActuatorSWCSWC-1
BSWRTE
ActuatorActuatorSWCSWC1Sensor Sensor
SWC
BSWRTE
Sensor
SensorSWC
ActuatorSignal Path / Data Flow
Mapping in More Detail:SW Component Structure and Execution Platform
Standardized RTE eases compiling & linking together several SW components from different teams/vendors/...
Vehicle Function
13© Dr. Kai Richter, Symtavision GmbHThe AUTOSAR Timing Model - Status and Challenges ARTIST2 Workshop, 23.3.06 Innsbruck
Sensor SWCSens BSW RTE
BSW BSW RTE Actuator SWCSWC1 RTE
RTEI/O CAN
BSWRTE ActI/O
end-to-end timing chain
HOPs
Timing Chains and Hand-Over Points (HOPs)
INTER-ECU
communication
INTRA-ECU
communication
ActuatorSWCSWC-1
BSWRTE
BSWRTE
Sensor
SensorSWC
ActuatorSignal Path / Data Flow
timing chain segments
ActuatorActuatorSWCSWC1Sensor Sensor
SWC
16© Dr. Kai Richter, Symtavision GmbHThe AUTOSAR Timing Model - Status and Challenges ARTIST2 Workshop, 23.3.06 Innsbruck
SW-Components vs. "Runnables" and Tasks
SW architecture:2 SW components,6 runnables
Implementation: 3 Tasks
Schedule and timing dependencies
ECU 1SW-C2
runnableY
runnableX
runnableZ
BSWRTE
SW-C 1runnableA
runnableB
runnableC
runnableArunnableY runnableBrunnableCrunnableX runnableZ
OS
OS
OS
OS Task 4
OS
SW-C 1runnableA
runnableB
runnableC
SW-C 2
runnableY
runnableX
runnableZ
17© Dr. Kai Richter, Symtavision GmbHThe AUTOSAR Timing Model - Status and Challenges ARTIST2 Workshop, 23.3.06 Innsbruck
timing chain segment
SW-C 1BSW RTE
BSWRTE
Challenge: Associating Schedules with Timing Chain Segments
software component w/ 3 runnables
sequential model
actual implementation
meaning ?
SW-C 1runnableA
runnableB
runnableC
OS
OS
OS
OSTask 4
OS
OS
OS
OS
OSTask 4
OS
what about runnable Bend of runnable C
start of runnable A
B B
25© Dr. Kai Richter, Symtavision GmbHThe AUTOSAR Timing Model - Status and Challenges ARTIST2 Workshop, 23.3.06 Innsbruck
Summary: Local Timing Effects
Complex timing
is not directly reflected in the software architecture is induced by the execution platform!
runnables and tasks
timing dependencies andcommunication semantics
non-standardized drivers and middleware (BSW)
etc...
OS
OS
OS
OSTask 4
OS
SWC 2SWC 1 SWC 3
client serveroversampling
undersamplingsender/receiverinternal state
CAN HW
CANBSW
RTESIG SIG
MO
INT
SEND
SIG
Queue
MO MO
52© Dr. Kai Richter, Symtavision GmbHThe AUTOSAR Timing Model - Status and Challenges ARTIST2 Workshop, 23.3.06 Innsbruck
Industry-Research Mismatch ???
SW-C 1
runnableArunnableBrunnableC
SW-C 2
runnableYrunnableX
runnableZ
CAN HW
CANBSW
RTESIG SIG
MO
INT
SEND
SIG
Queue
MO MO
ActuatorSWCSWC-1
BSWRTE
BSWRTE
Sensor
SensorSWC
Actuator
Signal Path / Data FlowO
S
OS
OS O
STask 4
OS
complex systems,manifold dependencies
revolutionary problems revolutionary solutions
clear semantics, well-defined interactions
Automotive Industry Research Community
