Renesas AUTOSAR MCAL Product · PDF fileAUTOSAR and vehicle networking Experience ... “Common API” means the processor no longer matters Analogy – Windows and x86 -> Intel’s

Renesas Electronics America Inc.

© 2012 Renesas Electronics America Inc. All rights reserved.

Class ID:

Working with

Eric Winder, Senior Applications Engineer

0C13B

© 2012 Renesas Electronics America Inc. All rights reserved. 2

Eric Winder

Technical Applications Engineer

16-bit automotive

AUTOSAR and vehicle networking

Experience

Vector CANtech (7 years)

– Standard, reusable software components for automotive embedded systems:

• CAN

• LIN

• ISO Diagnostics

– Facilitated and supported first deployment of AUTOSAR components at a major U.S. OEM.

Education

BSEE from Michigan State University


Renesas Technology & Solution Portfolio


Microcontroller and Microprocessor Line-up

Wide Format LCDs Industrial & Automotive, 130nm

350µA/MHz, 1µA standby

44 DMIPS, True Low Power

Embedded Security, ASSP

165 DMIPS, FPU, DSC

1200 DMIPS, Performance 1200 DMIPS, Superscalar

500 DMIPS, Low Power

165 DMIPS, FPU, DSC

25 DMIPS, Low Power

10 DMIPS, Capacitive Touch

Industrial & Automotive, 150nm

190µA/MHz, 0.3µA standby

Industrial, 90nm

200µA/MHz, 1.6µA deep standby

Automotive & Industrial, 90nm


Automotive & Industrial, 65nm

600µA/MHz, 1.5µA standby Automotive, 40nm

500µA/MHz, 35µA deep standby

Industrial, 40nm

200µA/MHz, 0.3µA deep standby

Industrial, 90nm

1mA/MHz, 100µA standby

Industrial & Automotive, 130nm


2010 2012

32

-bit

8

/1

6-b

it


‘Enabling The Smart Society’

Challenge: “Automotive electronic complexity is increasing exponentially. As cars become smarter with more feature content, as well as new drive-train technology and safety systems, development requires smarter tools and methods.”

Solution:

“A solution is to standardize software design processes, tools and software. Renesas has a long history of involvement, and offers a rich portfolio of solutions to facilitate this effort. This class will introduce the concepts, processes, and challenges of implementing AUTOSAR.”


Agenda

Basics- Who is AUTOSAR?

Basics- What’s the problem?

Basics- When is AUTOSAR coming?

Basics- What is defined?

Basics- How does it work?

ECU Configuration

Challenges

Wrap-up

Takeaways


Basics- Who is AUTOSAR?


AUTOSAR

Initial discussions in 2002

Official since 2003

Started with 5 German companies

NEC Electronics Corp. and Renesas Technology Corp. joined the effort in 2004

Approx. 175 Partners now (still growing)

www.autosar.org

AUTomotive Open System ARchitecture “Cooperate on standards, compete on implementation”

http://www.daimler.com/


AUTOSAR – Partnership Structure

Core Partner (OEM & Tier 1 Supplier) •Organizational control

•Technical contributions

•Administrative control

•Definition of external information

(web release, clearance, etc.)

•Leadership of working groups

•Involvement in working groups

Premium Members (incl. Tool Manufacturers)

•Leadership of working groups

•Involvement in working groups

•Technical contributions

•Access to current information

Associate Members •Access to finalized documents

•Utilization of standards


Core Partners

Premium Members

Associate Members

AUTOSAR – Partnership Structure

Growing Community

Please find updated info on

www.autosar.org

http://www.preh.de/

http://www.daimler.com/

http://www.magna.com/

http://www.denso.co.jp/index-e.html

http://www.elektrobit.com/

http://www.mazda.com/

http://www.mentor.com/

http://www.nxp.com/

http://www.porsche.com/

http://de.etasgroup.com/

http://www.fraunhofer.de/autosar

http://world.honda.com/

http://www.mbtech-group.com/

http://www.altran.com/

http://www.b2i-automotive.com/

http://www.freescale.com/

http://www.johnsoncontrols.com/

http://www.tttech-automotive.com/

http://www.zf.com/

http://www.delphi.com/

http://www.dspace.de/

http://www.etri.re.kr/eng

http://www.ibm.com/

http://www.fiatgroup.com/index.php?lang=en

http://www.lear.com/

http://www.tataelxsi.com/

http://www.magnetimarelli.com/

http://www.patni.com/industries/automotive/automotive-overview.html

http://www.renault.com/

http://www.mathworks.com/

http://www.valeo.com/

http://www.autoliv.com/

http://www.hella.com/

http://www.infineon.com/

http://us.st.com/stonline/products/applications/automotive/index.htm

http://www.trw.com/

http://www.vector-informatik.com/


Basics- What’s the Problem?


Example - Automotive Integrated Center Stack


Example - Automotive Integrated Center Stack


How much code?

1.7M

Source: http://spectrum.ieee.org/green-tech/advanced-cars/this-car-runs-on-code/0

5.7M

10M

100M


Reasons for the effort

Rising Automotive electronic complexity

Quantity of software increasing

ECU counts increasing

Large number of disparate processors used

Software portability limited

High effort for reuse of software features

Customized solutions increase:

Maintenance cost

Testing effort

OEM integration effort

Risk


Overall Objectives of AUTOSAR

Standardization

Workflows, software interfaces, tools

Increase modularity and transferability of features

Process to manage feature allocation

Clear division of hardware dependent and standard software versus the higher level features

Facilitate collaboration

Draw on experience from domain experts

Increase dependability and quality

Reuse standard solutions among Tier 1’s and across OEMs

Reduce effort/time to market


Basics- What is Defined?


System Configuration

Source: http://www.autosar.org


ECU Configuration


ECU Hardware

AUTOSAR Runtime Environment (RTE)

AUTOSAR SW-C 1

AUTOSAR Interface

AUTOSAR SW-C 3

AUTOSAR Interface

Basic Software (BSW) Services and Hardware Abstraction

AUTOSAR Interfaces

Complex Device Drivers

AUTOSAR Interface

MicroController Abstraction Layer

Standardized Interfaces

Standardized Interfaces

AUTOSAR SW-C 7

AUTOSAR Interface

AUTOSAR SW-C 12

AUTOSAR Interface


Basics- When is AUTOSAR Coming?


AUTOSAR is Here



R4.0 Additions

Multi Core

Main impact will be on OS

System impact (power saving, memory sharing)

Software reuse from low end to high end

Cryptography

Hardware accelerations (ICU, SHE)

AUTOSAR software libraries

Functional safety

Development processes

Safety-related features (Core test, RAM test, ROM test, etc.)

Ethernet

Legal requirement for OBD-II

Investigation to use Ethernet as network backbone


Basics- How does it Work?


3rd Party Software

Goal is to create a complete AUTOSAR solution

Renesas supplies MicroController Abstraction Layer

(MCAL – hardware-dependent software) drivers for standard peripherals and communication interfaces.

ECU Hardware


AUTOSAR SW-C 1

AUTOSAR SW-C 3

Basic Software (BSW)




MCAL Components


ECU Hardware

Microcontroller Drivers

GPT D

river

Watc

hdog D

river

MCU

Dri

ver

FLS D

river

FEE D

river

Memory Drivers

Communication Drivers

SPI

Driver

LIN

Driver

CAN

Dri

ver

Fle

xRay D

river

Eth

ern

et

Dri

ver

I/O Drivers

ICU

Driver

PW

M D

river

AD

C D

river

DIO

Dri

ver

PO

RT D

river

SPI

Driver


MCAL Development Roadmap

R32C

R32C

V850 /Fx3

V850/Fx4 SH2A V850/Px4

V850/Fx3

V850/Fx4

RH850F1X RH850/E1X RH850/P1X RH850/R1X

Instrumentation Body Schedule Airbag Powertrain ADAS Autosar

Release

Safety /

Chassis

V850/Fx4L

RH850/D1X RH850/V1X

SH2A V850/Px4

RH850F1X RH850/E1X RH850/P1X RH850/R1X RH850/D1X RH850/V1X

V850/Fx4

V850/Fx4L

V850/Px4

V850/Dx4

V850/Dx4

AS 3.x

AS4.0

AS 2.1

2012

2013

available

2013

available

available

available

2012

available

available

available


3rd Party Software

What about non-standard peripherals?

Renesas and partner companies can supply complex device drivers.

ECU Hardware


AUTOSAR SW-C 1

AUTOSAR SW-C 3





3rd Party Software

Tier 1 and/or 3rd party software vendor(s) contribute the Basic SoftWare (BSW - hardware-independent software)

Tier 1 or 3rd party software vendor(s) contribute the RunTime Environment (RTE – top-level abstraction software)

ECU Hardware


AUTOSAR SW-C 1

AUTOSAR SW-C 3





3rd Party Software

Integration is a joint activity with Renesas and the 3rd party vendor

Joint project planning

Issue tracking tools

Regular meetings

Renesas is open to working with any BSW provider.


ECU Configuration


Software Design Process

HW User Manual

application idea

SW implementation HW/SW integration


Software Design Process

System configuration

application idea

Integration of top-level

application & low-level

software

HW/SW integration

SW development flow will change:

Configuration Tool replaces hand-coded configuration


XML as an exchange format

Input and output formats are standardized by AUTOSAR

This ensures that any AUTOSAR compatible configuration editor can be used

Schema

ECU Configuration

Parameter Definition

Template

conforms to

Schema

ECU Configuration

Description Template

conforms to

ECU Configuration

Editor(s)

XML

ECU Configuration

Parameter

Definition

XML

ECU

Configuration

Description

creates

read

back


“ECU Spectrum” Editor Tool

A simple configuration editor is included in the Renesas MCAL package free of charge

Generic tool for “quick start” and testing that offers:

– AUTOSAR compatible xml file read / write

– Basic validation checks

– Read-back of existing configuration descriptions


ECU Configuration (Overview)

This is a precise description

with information about:

• Number of instances (e.g.

channel no.)

•parameter value definitions

Extract of the

System

Description

Configuration

Parameter

Definition

(Module MCU)

Configuration

Parameter

Definition

(Module MCU)

Configuration

Parameter

Definition

(Module MCU)

.xml

.xml

Module Generator Module

Generator Module Generator

Configuration

Files

(.c .h)

Configuration

Files

(.c .h)

Configuration Data

generated for the

AUTOSAR module

The Generator

translates the

configuration

information into

source code that is

then used by the

driver module

Standardized definition

format per module:

Type, allowed range,

multiplicity, default

values etc.

ECU

Configuration

Description

ECU

Configuration

Description

ECU Configuration

Editor(s)

ECU

Configuration

Description

.xml


Generators

Implementation specific tool to generate code that contains the configuration data from the AUTOSAR configuration description file(s)

Renesas delivers Generators as command line executables (one for each software module)

Command line interface that take the ECU configuration description file as input

Generate .h files (for pre-compile configuration) and .c files (for link-time and post-build configuration)

Are written in perl

Renesas Generators provide plug-in capability for configuration editors and can be used in makefile environment

ECU

Configuration

Description

.xml

Module Generator

Executable

Configuration

Files

(.c .h)


Challenges


Questions

What are some possible downsides to hardware abstraction?

What are some possible downsides to commonization and standardization?


Challenges – Hardware Abstraction

Layered approach provides great flexibility, but

it increases configuration complexity and the number of chances to “get it wrong”

– Tools have to balance ease of use against the restriction of this flexibility


Standard API

Designed for the

“Least Common Denominator”

Decreases the advantage of innovation

– Non-standard features may not be available

– Special features must be either

• made transparent to BSW by MCAL, or

• handled outside of MCAL by “complex device drivers”

Software Supply Chain

BSW from multiple vendors must work together

Integration and runtime issue resolution requires

cooperation , potentially among competitors

Challenges – Standardization


Challenges – Commonization

Specifications still under development

Released versions available, but not all changes/updates are backward-compatible, even within minor revisions

OEMs adopt at different times and for different reasons.

– Support of multiple releases necessary to support legacy and future development

Historically, OEMs have different interpretations or desired features which are not agreed upon

– OEM-specific AUTOSAR implementations increase complexity

– More is standardized in later revisions to avoid this.


Wrap-Up


Pitfalls to Avoid - Possible Misconceptions

“AUTOSAR-compliance is a precise concept”

Full process

Black box behavior

Everything in-between

“Common API” means the processor no longer matters

Analogy – Windows and x86 -> Intel’s HTT

Processor architectures, instruction sets, pipelines, and special peripherals and features can make all the difference.

“Common API” means “cheaper and faster to market”

True, but only after reuse is factored in. Change costs money.

“Standard” means “Easy”


Optimizations

Herstellerinitiative Software (HIS) recommended optimization AUTOSAR

Subset specification

Allows application to 16-bit and

smaller/less powerful 32-bit microcontrollers

Similar initiative from JASPAR

Black box AUTOSAR-compliance


Implement leaner hardware access for time-critical features

Control unspecified hardware peripherals (e.g. RDC, EMU)


Takeaways

Implement the subset that makes sense

AUTOSAR is not an end in itself

“Don’t sacrifice usability for the sake of reusability.”

Get help from the experts

Save money in the long run by getting it right from the start

Reap the benefits of lessons learned by others


Questions?


‘Enabling The Smart Society’ in Review…

Challenge: “Automotive electronic complexity is increasing exponentially. As cars become smarter with more feature content, as well as new drive-train technology and safety systems, development requires smarter tools and methods.”

“One solution is to standardize software design processes, tools and software. Renesas has a long history of involvement, and offers a rich portfolio of solutions to facilitate this effort. This class will introduce the concepts, processes, and challenges of implementing AUTOSAR.”

Do you agree that we accomplished the above statement?


Please Provide Your Feedback…

Please utilize the ‘Guidebook’ application to leave feedback

or

Ask me for the paper feedback form for you to use…

Renesas Electronics America Inc.

© 2012 Renesas Electronics America Inc. All rights reserved.

Documents

Renesas AUTOSAR MCAL Product · PDF fileAUTOSAR and vehicle networking Experience ... “Common API” means the processor no longer matters Analogy – Windows and x86 -> Intel’s