Working with. Eric Winder, Senior Applications Engineer. Renesas Electronics America Inc Renesas Electronics America Inc. All rights reserved.

Transcription

1 Working with Eric Winder, Senior Applications Engineer Class ID: 0C13B Renesas Electronics America Inc.

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 2

3 Renesas Technology & Solution Portfolio 3

4 8/16-bit 32-bit Microcontroller and Microprocessor Line-up DMIPS, Superscalar Automotive & Industrial, 65nm 600µA/MHz, 1.5µA standby 500 DMIPS, Low Power Automotive & Industrial, 90nm 600µA/MHz, 1.5µA standby 165 DMIPS, FPU, DSC Industrial, 90nm 200µA/MHz, 1.6µA deep standby 25 DMIPS, Low Power Industrial & Automotive, 150nm 190µA/MHz, 0.3µA standby 10 DMIPS, Capacitive Touch Wide Industrial Format & LCDs Automotive, 130nm 350µA/MHz, 1µA standby 1200 DMIPS, Performance Automotive, 40nm 500µA/MHz, 35µA deep standby 165 DMIPS, FPU, DSC Industrial, 40nm 200µA/MHz, 0.3µA deep standby Embedded Security, ASSP Industrial, 90nm 1mA/MHz, 100µA standby 44 DMIPS, True Low Power Industrial & Automotive, 130nm 144µA/MHz, 0.2µA standby 4

5 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. 5

6 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 6

7 Basics- Who is AUTOSAR? 7

8 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) AUTomotive Open System ARchitecture Cooperate on standards, compete on implementation 8

9 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 9

10 AUTOSAR Partnership Structure Core Partners Premium Members Growing Community Please find updated info on Associate Members 10

11 Basics- What s the Problem? 11

12 Example - Automotive Integrated Center Stack 12

13 Example - Automotive Integrated Center Stack 13

14 How much code? 1.7M 5.7M 10M 100M Source: 14

15 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 15

16 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 16

17 Basics- What is Defined? 17

18 System Configuration Source: 18

19 ECU Configuration AUTOSAR SW-C 1 AUTOSAR SW-C 3 AUTOSAR SW-C 7 AUTOSAR SW-C 12 AUTOSAR Interface AUTOSAR Interface AUTOSAR Interface AUTOSAR Interface AUTOSAR Runtime Environment (RTE) AUTOSAR Interfaces Basic Software (BSW) Services and Hardware Abstraction AUTOSAR Interface Complex Device Drivers Standardized Interfaces Standardized Interfaces MicroController Abstraction Layer ECU Hardware Source: 19

20 Basics- When is AUTOSAR Coming? 20

21 AUTOSAR is Here Source: 21

22 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 22

23 Basics- How does it Work? 23

24 3rd Party Software Goal is to create a complete AUTOSAR solution AUTOSAR SW-C 1 AUTOSAR SW-C 3 AUTOSAR Runtime Environment (RTE) Basic Software (BSW) Complex Device Drivers MicroController Abstraction Layer ECU Hardware Renesas supplies MicroController Abstraction Layer (MCAL hardware-dependent software) drivers for standard peripherals and communication interfaces. 24

25 GPT Driver Watchdog Driver MCU Driver FLS Driver FEE Driver SPI Driver LIN Driver CAN Driver FlexRay Driver Ethernet Driver ICU Driver PWM Driver ADC Driver DIO Driver PORT Driver MCAL Components Microcontroller Drivers Memory Drivers Communication Drivers I/O Drivers ECU Hardware Source: 25

26 MCAL Development Roadmap Autosar Release Body Safety / Chassis Powertrain Airbag Instrumentation ADAS Schedule RH850F1X RH850/E1X RH850/P1X RH850/R1X RH850/D1X RH850/V1X 2013 AS4.0 V850/Fx4L 2012 V850/Fx4 V850/Px4 V850/Dx RH850F1X RH850/P1X RH850/E1X RH850/R1X RH850/D1X RH850/V1X 2013 V850/Fx4L available AS 3.x V850/Fx4 V850/Px4 SH2A V850/Dx4 available V850/Fx3 available R32C available AS 2.1 V850/Fx4 V850 /Fx3 V850/Px4 SH2A available available R32C available 26

27 3rd Party Software What about non-standard peripherals? AUTOSAR SW-C 1 AUTOSAR SW-C 3 AUTOSAR Runtime Environment (RTE) Basic Software (BSW) Complex Device Drivers MicroController Abstraction Layer ECU Hardware Renesas and partner companies can supply complex device drivers. 27

28 3rd Party Software Tier 1 and/or 3rd party software vendor(s) contribute the Basic SoftWare (BSW - hardware-independent software) AUTOSAR SW-C 1 AUTOSAR SW-C 3 AUTOSAR Runtime Environment (RTE) Basic Software (BSW) Complex Device Drivers MicroController Abstraction Layer ECU Hardware Tier 1 or 3rd party software vendor(s) contribute the RunTime Environment (RTE top-level abstraction software) 28

29 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. 29

30 ECU Configuration 30

31 Software Design Process application idea HW User Manual SW implementation HW/SW integration 31

32 Software Design Process application idea SW development flow will change: Configuration System configuration Tool replaces hand-coded configuration Integration of top-level application & low-level software HW/SW integration 32

33 XML as an exchange format Schema ECU Configuration Parameter Definition Template Schema ECU Configuration Description Template conforms to conforms to XML ECU Configuration Parameter Definition read back XML ECU Configuration Description ECU Configuration Editor(s) creates Input and output formats are standardized by AUTOSAR This ensures that any AUTOSAR compatible configuration editor can be used 33

34 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 34

35 ECU Configuration (Overview) Extract of the System Description.xml Configuration Parameter Configuration Definition Parameter Configuration (Module Definition Parameter MCU) (Module Definition MCU) (Module MCU).xml ECU Configuration Editor(s) ECU Configuration ECU Description Configuration ECU Description Configuration Description.xml Module Generator Module Generator Module Generator Configuration Data generated for the AUTOSAR module Configuration Configuration Files (.c Files.h) (.c.h) Standardized definition format per module: Type, allowed range, multiplicity, default values etc. This is a precise description with information about: Number of instances (e.g. channel no.) parameter value definitions The Generator translates the configuration information into source code that is then used by the driver module 35

36 Generators ECU Configuration Description.xml Module Generator Executable Configuration Files (.c.h) 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 linktime and post-build configuration) Are written in perl Renesas Generators provide plug-in capability for configuration editors and can be used in makefile environment 36

37 Challenges 37

38 Questions What are some possible downsides to hardware abstraction? What are some possible downsides to commonization and standardization? 38

39 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 39

40 Challenges Standardization 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 40

41 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. 41

42 Wrap-Up 42

43 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 43

44 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 Complex Device Drivers Implement leaner hardware access for time-critical features Control unspecified hardware peripherals (e.g. RDC, EMU) 44

45 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 45

46 Questions? 46

47 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? 47

48 Please Provide Your Feedback Please utilize the Guidebook application to leave feedback or Ask me for the paper feedback form for you to use 48

49 Renesas Electronics America Inc.