Chapter 3: Software Platform & Architecture for Telematics

More documents

Recommendations

Info

Software‐ and System‐Architecture of ECUs• Future: Function oriented Architecture for higher Flexibility362010/2/3
Software‐ and System‐Architecture of ECUs• What disappears?– Proprietary Basic Software with proprietary interface towardsthe application software• What comes up?– Standardized Basic Software Modules– RTE (Runtime Environment) make application softwareindependent from Basic SW and specialities of ECU hardware– Application SW Components with standardized interfacedescription (syntax and specific signals)• What stays?– Application Software as a brand differentiating key element forthe development of new vehicle functions372010/2/3
Page 2 and 3: Content• ECU• Automotive Open S
Page 4 and 5: ECU• Some modern cars have up to
Page 6 and 7: ECU• Based on information from th
Page 8 and 9: Autosar• Cooperate on standards -
Page 10 and 11: Project Objectives and Main Working
Page 12 and 13: Technical scope of AUTOSAR122010/2/
Page 14 and 15: AUTOSAR -Core Partners and Members1
Page 16 and 17: Use Case ‘Pedal Management’ vie
Page 18 and 19: Exchange of type of front‐light18
Page 20 and 21: Use case ‘Front‐Light Managemen
Page 22 and 23: Main Concepts: Architecture• Basi
Page 24 and 25: AUTOSAR Basic Software242010/2/3
Page 26 and 27: Intra‐ and Inter‐ECU Communicat
Page 28 and 29: Used Release 2.0 AUTOSAR specificat
Page 30 and 31: Development ofAUTOSAR SW Components
Page 32 and 33: Software‐ and System‐Architectu
Page 34 and 35: Software‐ and System‐Architectu
Page 38 and 39: Development of AUTOSAR SW Component
Page 44 and 45: AUTOSAR -System Design - Implementa
Page 46 and 47: AUTOSAR -Input Descriptions• Step
Page 48 and 49: AUTOSAR -Input Descriptions• Step
Page 50 and 51: AUTOSAR -ECU‐Configuration• Ste
Page 52: Use case ‘Front‐Light Managemen

Chapter 3: Software Platform & Architecture for Telematics

Create successful ePaper yourself

Delete template?

Save as template?