VELOCITY LAB TM Embedded Development Ecosystem

(1)

Renesas Electronics America Inc.

VELOCITY LAB

TM

Embedded Development Ecosystem

(2)

(3)

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

242µA/MHz, 0.2µA standby Automotive & Industrial, 90nm

600µA/MHz, 1.5µA standby Automotive & Industrial, 65nm

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

500µA/MHz, 35µA deep standby

Industrial, 40nm

242µA/MHz, 0.2µA standby

Industrial, 90nm

1mA/MHz, 100µA standby

Industrial & Automotive, 130nm

144µA/MHz, 0.2µA standby

2010 2013 32 -b it 8/ 16 -bit

32-Bit High Performance,

High Scalability & High Reliability

8/16-Bit True Low Power High Efficiency & Integration

(4)

 Cars and trucks clearly one of the biggest elements of the

smart society – many dramatic innovations.

Challenge:

 How to develop these innovations:

 Quickly  Efficiently

 Software is the single biggest challenge facing the auto

industry – controls timing, development cost and quality Solution:

 Velocity LabTM offers dramatic improvements in the speed

and efficiency of software and system development

 Effectively the smart society concept applied to a

development ecosystem

(5)

 The Challenge  Velocity Lab

 Overview  QuantiPhi

 Processor Models

 How does this change the game?  Conclusion

(6)

(7)

The Challenge of Automotive Software

 10-100M lines of code per car.

 New Features, Lead Time and Quality all driven by software.  System integration:

 50-100 controllers, over 150 distributed functions.  Software from multiple sources, e.g. Infotainment.

 Development team split globally and across companies  Safety requires ISO 26262.

 Off board communication.

 New mobile devices/applications.

 At tier 1, up to 50% of resource and all timing set by SW.  Software is now the biggest challenge in Automotive.

(8)

(9)

(10)

ADAS Ecosystem Overview

Car ECU Middleware Dvpt. Tools Software Dvpt. Tools Hardware Hardware IDE : Eclipse bin Operating Systems Video IF Open std. OpenCV OpenCL OpenGL OpenVG Customer/Tier1 Application Vision application SW AUTOSAR RTE RT O S Compiler linker Debugger Simulator PRISM for Multi-core Application board System integration Demo PoC Infrastructure Customization & porting Companion chips PHY Power Supply Intermediate devices Carmaker functionality Device Hardware debugger Vision SDK 3rd _party network MC A L Renesas standard MCU tools A DTF – E B t oo lc h ai n 3rd Party network

(11)

R-Car

*

_{Ecosystem - Overview}

Middleware OS Pre-Boot Hardware IP Pre-Boot OS Middleware

Hitachi Advanced Digital System Integration System Integration

*

*tentative naming

(12)

What have we typically used?

 Lot of manual steps

 Need physical hardware  Tools are point solutions  Expensive tools

 Tools sometimes lag silicon, IT

effort to manage licensing, installation, etc.

What sort of Development Ecosystem?

What do we need?  Automated  Virtual  Integrated  Affordable  Accessible

(13)

 An integrated toolkit of development components from

Renesas and our partners

 Build embedded solutions quickly & efficiently

 Simultaneously leverage the latest technology for performance

gains

 Ties together

 Model based design  Extensive simulation

 Full auto-code generation and auto-integration  Launching now!

VELOCITY LAB

TM

(14)

(15)

A2D CAN PWM Model-Based SPI OS Everything Else Application

(16)

Auto Generation of Drivers - QuantiPhi

Model Based Design (Stateflow/Simulink) C-Code (Traditional) AUTOSAR

QuantiPhi RE

Easy, Graphical Configuration of Drivers

Autocoding from Models

Auto Integration with Drivers

Production Quality

Code MISRA Compliant Drivers

(17)

 Where are we launching QuantiPhi?”

 How do I learn more?

 Model-Based Development (6P16B)

 QuantiPhi for RL78: The Fastest Path from Idea to Implementation

(0C07B)

 RH850 & RL78: Introducing the Next Gen Microcontrollers (1C06B)

 Working with AUTOSAR (0C13B)

 HEV/EV Traction Motor Control Lab (0L04A)

 MICON Racing – Qualify using QuantiPhi for RL78

QuantiPhi

(18)

 Walk in knowing nothing about

an RL78 – develop your own model-based control strategy, fully auto generate and auto

integrate the code, and use it to run a functioning race car

around our track.

 Shows how QuantiPhi makes

migration to a new micro easy

 Rapidly and easily change

strategy

 Proves the speed and efficiency

Velocity Lab can deliver (idea to integrated production code in a couple of hours)

 See how the benefits would

translate into day to day work

(19)

(20)

Virtual ECU

What is a Processor Simulation Model?

Virtual Microcontroller Power Device Models Mixed Signal Models Fast ISS Core Model Timed Core Model Peripheral Models Peripheral Models Peripheral Models Peripheral Models Peripheral Models Peripheral Models Peripheral Models Peripheral Models Peripheral Models Peripheral Models Peripheral Models Peripheral Models Mixed Signal Models Power Supply Models Passive Device Models Passive Device Models Passive Device Models Passive Device Models

(21)

Processor Models

Traditional Process: Hardware Design Proto Build Software Development Software Test Launch

With Processor Models:

Hardware Design Proto Build Software Development Software Test AND: Virtual ECU Global Teams Suppliers Partners Customers Plant Models Whole System Test Multiple ECUs Whole Vehicle Test Fault Injection Validate Error Handling Acceleration Int’n Test Launch

(22)

 Where are we launching Processor Models?”

 How do I learn more?

 Simulation: Expert Insights into Modeling Microcontrollers (6P17I)  Simulation – Moving Development into the Virtual World (0C08I)  Using Processor Models for SW Development & Validation (0C22B)  Virtual HIL test/ISO26262 using processor models (0C18B)

 Lab - Using Processor Models (0L02A)

(23)

(24)

 Acme Autos are planning a 2nd Gen plug-in HEV.

 Lead engineer and buyer attended DevCon for the first time:

 Integrated RDC/MCU

 IGBTs

 Battery Control  Smart Charging  Velocity Lab

 Decided to go with SH72AY/integrated RDC for gen 2 HEV:

 Used QuantiPhi to configure new MCU – including comms and

complex drivers for RDC and MCU… one month instead of three

 Linked existing models to QuantiPhi blocks in parallel

 Configured to use IRIS board auto generated/integrated code

and ported direct to compiler…same day instead of 3 months

 Basic migration of app to new silicon up and running in 2 mths!

HEV/EV Design

Re-write Re-read

Write & Test Drivers

Read User

ManualQuantiPhi

Code Gen

(25)

HEV/EV Design

 Exported pin out assignment direct from QuantiPhi to board

designer

 Saved 2 weeks of meetings.  Saved 6 weeks of redesign.

 Iteration and update as expected (though less than before):  Cycle from issue creation to detection shortened from 3

months to 2 weeks

 Code maturity pulled up by over 6 months  Excellent launch!

Hardware Design Re-design Application

QuantiPhi

Hardware Design Re-design Application

Code Gen

(26)

 Technology plan for Gen 3:  Migrate to RH850 C1x  Adopt AUTOSAR

 Latest gen Battery Control  Latest gen Smart Charging  Set up from QuantiPhi:

 Very fast configuration/adoption of new MCU

 Migration of model based applications to new MCU very

fast

 Mixed Signal configuration now added to QuantiPhi – able

to configure both battery control and smart charge

(27)

 Adopted AUTOSAR 4.0

 Used QuantiPhi to swap between standard MCAL and fast

complex drivers for SPI and ADC

 Ported code to Processor Model:

 Started development 3 months ahead of first silicon

 Linked to plant models:

 Virtual HIL before first silicon

 Confirmed MCU performance/selection before laying out

board

(28)

(29)

 An integrated toolkit of development components from

Renesas and our partners

 Build embedded solutions quickly & efficiently

 Simultaneously leverage the latest technology for

performance gains

 Ties together

 Model based design  Extensive simulation

 Full auto-code generation and auto-integration  Launching now!

VELOCITY LAB

TM

(30)

 Cars and trucks clearly one of the biggest elements of the

smart society – many dramatic innovations.

Challenge:

 How to develop these innovations:

 Quickly  Efficiently

 Software is the single biggest challenge facing the auto

industry – controls timing, development cost and quality Solution:

 Velocity LabTM offers dramatic improvements in the speed

and efficiency of software and system development

 Effectively the smart society concept applied to a

development ecosystem

(31)

(32)