Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

BMW Autostar

Download as pdf or txt
Download as pdf or txt
You are on page 1of 28
At a glance
Powered by AI
Some of the key takeaways from the document are that multi-core systems will become more common in automobiles to handle increasing functionality, but that they significantly increase complexity and require new development methods and tools. They also make migrating legacy software more challenging.

Some of the challenges with adopting multi-core systems in automobiles include massively increased internal complexity of ECUs requiring more stringent development practices, shifting the major integration task from bus-level to software integration, and that current automotive operating systems were not designed to support multi-core architectures.

Customer studies with BMW's MINI E and BMW ActiveE electric vehicles found that the average daily driving distance was less than 50km and that a total range of 140-160km was sufficient for most drivers' needs. This helped inform the development of BMW's BMW i3 electric vehicle.

Simon Frst, General Manager Software Development and Software Infrastructure.

AN OEMS POINT OF VIEW ON MULTI-CORE.


EMBEDDED MULTI-CORE CONFERENCE, 16.-18. JUNE 2015, MUNICH, GERMANY

AGENDA.

1.

Increasing Functionality for Future Automotive E/E Systems.

2.

The Need of Multi-Core Systems.

3.

Impact on Hardware and Software.

4.

Opportunities for E/E Architectures.

5.

Outlook on Adaptive AUTOSAR.

EMCC 2015, BMW Group, 17th June 2015

Seite 2

AGENDA.

1.

Increasing Functionality for Future Automotive E/E Systems.

2.

The Need of Multi-Core Systems.

3.

Impact on Hardware and Software.

4.

Opportunities for E/E Architectures.

5.

Outlook on Adaptive AUTOSAR.

EMCC 2015, BMW Group, 17th June 2015

Seite 3

GLOBAL TRENDS DRIVING THE FUTURE OF SUSTAINABLE MOBILITY.

Environment

Urbanisation

Politics

Global Trends
Economy

EMCC 2015, BMW Group, 17th June 2015

Culture

Customer Expectations

Seite 4

MINI E AND BMW ACTIVE E FIELD RESEARCH AND CUSTOMER STUDIES


SERVED AS BASIS FOR THE DEVELOPMENT OF THE BMW i3.
MINI E (2009-2012)

BMW ActiveE (2011-2014)

BMW i3 (seit 2013)

Average distance a day [km]


100
80

MINI E France
MINI E UK

60

MINI E Germany
MINI E China

40

MINI Cooper
BMW 116i

20

BMW 530d

0
0

50

100

150

200

250

300

350

400

-daily driving distance < 50km


Total coverage 140-160 km is
sufficient.
EMCC
2015, BMW Group, 17th June 2015

Improved space provided in the vehicle


and comfort.
90% demands of mobility are covered.

A holistic offer of mobility and the


development of a fast charging
infrastructure, close the gap. Seite 5

CUSTOMER JOURNEY A FULLY COMPREHENSIVE PRODUCT EXPERIENCE


FOR THE BMW i3.
PREPARING THE DRIVE

ConnectedDrive Portal
BMW i Remote App
Planning the route

EMCC 2015, BMW Group, 17th June 2015

DRIVING EXPERIENCE

One-pedal-feeling
Charging Infrastructure ChargeNow
Dynamic Navi-Information

AFTER THE DRIVE

BMW i Wallbox pro


Efficiencytainment
BMW Green Energy

Seite 6

BMW i8 UND BMW i3.


FIGURES AND FACTS.
BMW i8

BMW i3

Diagnosable ECUs

BMW i8

BMW i3

41

36

Non diagnosable ECUs


Computing power ca.

EMCC 2015, BMW Group, 17th June 2015

64
3600 MIPS

3200 MIPS

Bus Systems

Potential capacity (Mbit/s)

13
Seite 7

AGENDA.

1.

Increasing Functionality for Future Automotive E/E Systems.

2.

The Need of Multi-Core Systems.

3.

Impact on Hardware and Software.

4.

Opportunities for E/E Architectures.

5.

Outlook on Adaptive AUTOSAR.

EMCC 2015, BMW Group, 17th June 2015

Seite 8

MOORES LAW WITHIN THE AUTOMOTIVE INDUSTRY - MEMORY.

Size
(log!)

1GB
100MB

~7 years

Gordon Moore
PII

Intel CEO

10MB

E60
E65

80486

1MB

All 4 years multiplied by 10


E38

68000

100kB
10kB

6502

1980
EMCC 2015, BMW Group, 17th June 2015

L6!

P4

E32

1985

1990

PC RAM
Memory within BMWs cars
1995

2000

2005

2010
Seite 9

MOORES LAW WITHIN THE AUTOMOTIVE INDUSTRY CPU FREQUENCY.

ALC & Navigation

Electronic Gear Box Control


Anti Slip Control
Anti Blocking System
Telephone
Seat Heating Control System
Automatic Mirror Dimming
.

Night Vision

Navigation System
CD Changer
Bus Systems
Active Cruise Control
Airbag
Dynamic Stability Control
Adaptive Gear Box Control
Dynamic Drive (ARS)
RDS/TMC
Emergency Call

AFS I+II

Telematics
Bluetooth

Brake-by-Wire
Steer-by-Wire

Lane Change Assist


Personalization

Software-Update

Force Feedback Pedal

1980

1985

1990

1995

2000

2005

2010

Integrated Aftersales
Personal Radio
OTA SW-Updates
Lifetime Func. Upgrades
Augmented Reality
Pay-Per-Use Systeme
Mobile Vernetzung
Vernetztes Fahrzeug
Ad-hoc Netzwerke
Brake-by-Wire
Steer-by-Wire
Elektromotor
Prventiv-Diagnose
...

2015

Automotive

Singlecore

ACC Stopp & Go

Dualcore
(EA/EF/EI)

1 MHz

Main-/
Co-CPU

(Lockstep)

Dualcore

10 MHz

EMCC 2015, BMW Group, 17th June 2015

PC

>7 Jahre

Singlecore

100 MHz

Multicore
(Terascale)

1 GHz

Quadcore

Dualcore

Hyperthreading

10 GHz

Seite 11

POWER CONSUMPTION WITHIN BMW CARS.

Power

60
ELV

8Bit
EMCC 2015, BMW Group, 17th June 2015

40
CAS
AHM
RDC
RK
HSR
SZL
NIVI
LVM
HC2
FZD
FKA
PDC

30

16Bit

32Bit

ICM
HSR
DME
ZFM
CIC

50W
Rising electrical power consumption
is not acceptable within future cars.

Seite 13

AGENDA.

1.

Increasing Functionality for Future Automotive E/E Systems.

2.

The Need of Multi-Core Systems.

3.

Impact on Hardware and Software.

4.

Opportunities for E/E Architectures.

5.

Outlook on Adaptive AUTOSAR.

EMCC 2015, BMW Group, 17th June 2015

Seite 14

MULTI-CORE SYSTEMS WITHIN BMW CARS.

Note:
Only ECUs in concurrent
operating mode using a
real multicore OS.

8
7
6
5

Estimated MC ECUs
Amount of MC ECUs

4
3
2
1
0
35up
EMCC 2015, BMW Group, 17th June 2015

SOP2017

SOP2020
Seite 15

IMPACT OF ARCHITECTURE OF MICROCONTROLLER.

Infineon TriCore AURIX TC29x

EMCC 2015, BMW Group, 17th June 2015

Freescale Matterhorn MPC5777M

Seite 17

IMPACT ON SOFTWARE SYSTEMS.


Callgraph of a
Engine Control Unit
Data exchange is mostly
handled via global
variables

EMCC 2015, BMW Group, 17th June 2015

Seite 19

IMPACT ON SOFTWARE SYSTEMS.


Directed call-graph of an integration platform
150 software components
14 of them are safety-relevant according to ASIL B
Over 1000 assembly connectors
Multiple n:m edges between SWCs
How to realize safety principle: As less dependencies to other
components as possible to avoid ASIL inheritance?

EMCC 2015, BMW Group, 17th June 2015

Seite 20

IMPACT ON SOFTWARE SYSTEMS.

EMCC 2015, BMW Group, 17th June 2015

Seite 21

IMPACT ON SOFTWARE SYSTEMS.

EMCC 2015, BMW Group, 17th June 2015

Seite 22

AGENDA.

1.

Increasing Functionality for Future Automotive E/E Systems.

2.

The Need of Multi-Core Systems.

3.

Impact on Hardware and Software.

4.

Opportunities for E/E Architectures.

5.

Outlook on Adaptive AUTOSAR.

EMCC 2015, BMW Group, 17th June 2015

Seite 23

PARTIAL SYMMETRIC APPROACH.


MULTI-CORE OPERATION IN AUTOSAR CLASSIC.
ECU
core 0:
partition 0:

core 1:
partition 1:

partition 2:

partition 3:

partition 4:

Application Layer
RTE
BswM

BswM

BswM

EcuM

EcuM

OS

OS
Other BSW
modules

Other BSW
modules

Other BSW
modules

BswM

Other BSW
modules

BswM

Other BSW
modules

Microcontroller (C)

Classic approach: AUTOSAR SWCs are merged on a common Basic Software.


Potential: Already standardized in AUTOSAR. Isolation on SWC level possible.
EMCC 2015, BMW Group,
June 2015
17th
Problems:
No strict software isolation is possible (due to common BSW). Solution needs an optimized SWC to core mapping.

Seite 24

ASYMMETRIC APPROACH.
INDEPENDENT AUTOSAR STACKS.
ECU
core 0:
Application
Layer

core 1:

ASIL B(D)

ASIL B(D)

ASIL A

QM

QM

QM

Sensor
Software
Component

Application
Software
Component

Actuator
Software
Component

Sensor
Software
Component

Application
Software
Component

Actuator
Software
Component

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

Application
Layer

RTE

RTE

Services Layer

Microcontroller Abstraction Layer

ECU Abstraction
ECU Abstraction
Layer Layer

Complex
Drivers

Complex
Drivers

ECU Abstraction
ECU Abstraction
Layer Layer

Services Layer

Microcontroller Abstraction Layer

Microcontroller (C)
AUTOSAR Stacks are independently integrated and assigned to different cores. Operation similar to two independent ECUs.
Potential: Different operating systems are possible. Isolated development scenario for OEM and Tier1 partition.
Problems: Hardware must be fully separated. Not standardized within AUTOSAR.
EMCC 2015, BMW Group, 17th June 2015

Seite 25

VIRTUALIZATION.
INTEGRATION OF VIRTUAL AUTOMOTIVE SYSTEMS.
ECU
core 1:

core 0:
Virtual Machine 2

Virtual Machine 1
Application
Layer

Virtual Machine 3

ASIL B(D)

ASIL B(D)

ASIL A

ASIL B(C)

ASIL A(C)

QM

QM

QM

Sensor
Software
Component

Application
Software
Component

Actuator
Software
Component

Sensor
Software
Component

Application
Software
Component

Sensor
Software
Component

Application
Software
Component

Actuator
Software
Component

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

AUTOSAR
Interface

Application
Layer

Services Layer

Services Layer

Microcontroller
Abstraction Layer

Services Layer

ECU Abstraction
ECU Abstraction
Layer Layer

Complex
Drivers

ECU Abstraction Layer

ComplexDriver

Complex
Drivers

Microcontroller Abstraction Layer

Complex
Drivers

ECU Abstraction
ECU Abstraction
Layer Layer

RTE

RTE

RTE

Application
Layer

Microcontroller Abstraction Layer

Embedded Hypervisor
Microcontroller (C)
AUTOSAR Stacks isolated within virtual machines by usage of an embedded hypervisor and integrated on a common ECU.
Potential: System isolation offers full separation between virtual machines to achieve freedom from interference.
EMCC 2015, BMW Group,
17th June 2015 State of the art hardware has less virtualization supporting features. Approach is not standardized in AUTOSAR.
Problems:

Seite 26

AGENDA.

1.

Increasing Functionality for Future Automotive E/E Systems.

2.

The Need of Multi-Core Systems.

3.

Impact on Hardware and Software.

4.

Opportunities for E/E Architectures.

5.

Outlook on Adaptive AUTOSAR.

EMCC 2015, BMW Group, 17th June 2015

Seite 27

INTEGRATION OF SOFTWARE PLATFORMS BASED ON STANDARDS.

Adaptive
Application

Classic
Application

Adaptive
Application

Adaptive
Application

HMI to selected the demo App


FSA PoC

Web Browser PoC

Audio Manager PoC

Qt5

Non-AUTOSAR
Application

Adaptive AUTOSAR API

ECU Abstraction Layer

Services Layer
ECU Abstraction Layer

Complex Drivers

Services Layer

AUTOSAR Runtime Enviroment (RTE)


Complex Drivers

AUTOSAR Runtime Enviroment (RTE)

Operating system

AUTOSAR Adaptive Services


SW
configuration

Software Platform

Platform
resources

Platform modes

Middleware
DLT

NSM

NSC

Persistency

Audio
Manager
Deamon

Audio
Manager
Plugins

Webkit

Automotive
Message
Broker

Communication HW acceleration
AUTOSAR Adaptive Foundation

Kernel

Microcontroller

Microcontroller

(Virtual) Machine / HW

(Virtual) Machine / HW

AUTOSAR Classic Platform

AUTOSAR Classic Platform

AUTOSAR Adaptive Platform

Non-AUTOSAR Basic
Software (Genivi)

Microcontroller Abstraction Layer

Microcontroller Abstraction Layer

Non-AUTOSAR
Offboard
System

SOME/IP
System Description
EMCC 2015, BMW Group, 17th June 2015

Common Bus Interface Specification


Seite
Page 28

AUTOSAR ADAPTIVE PLATFORM - ARCHITECTURE DRAFT.

Application
Software
Component

Backend
Proxy

Application
Software
Component

Application
Software
Component

Application Level
Standardized AUTOSAR Adaptive API

Operating system

AUTOSAR Adaptive Services


SW
configuration

Platform
resources

Platform modes

Standardized
AUTOSAR
Adaptive Lib

AUTOSAR Adaptive Platform


Communication

HW acceleration

AUTOSAR Adaptive Foundation


(Virtual) Machine / HW

EMCC 2015, BMW Group, 17th June 2015

Standardized
AUTOSAR
Adaptive Service
Platform
Functionality
Service Oriented
Communication

Seite
Page 29

SUMMARY
There is no doubt that multi-core systems will become common in the automotive domain.
Multi-core systems will massively increase the internal complexity of ECUs and therefore require
more enhanced and stringent development methods and tools.
Multi-core systems will shift the major integration task from bus-level to software-integration
Migration of legacy software to multi-core systems as a very challenging task. But this can be taken
as unique opportunity for new and clean software architectures and implementations.
Current Automotive Operation Systems have not been designed to support multi-core
After 25 years of automotive e/e development and architectures we have reached a
disruptive point.
EMCC 2015, BMW Group, 17th June 2015

Seite 30

TOPICS FOR FURTHER DISCUSSION AT THIS EVENT


Will state of the art multi-core systems scale up in the future?
Can multi-core systems be qualified according to ISO26262?
Can we achieve the required level of dependability (availability) for highly automated driving?
How can we deal with failures within large scale integrated systems (exceptions, resets, etc.)?
Will virtualization become common in automotive ECUs?
Will operating systems and symmetric multiprocessing be preferred over static operating systems
and asymmetric multiprocessing?
EMCC 2015, BMW Group, 17th June 2015

Seite 31

THANKS FOR YOUR ATTENTION.

EMCC 2015, BMW Group, 17th June 2015

32

You might also like