1. VELOCITY LABTM Embedded Development Ecosystem
0C05B

2. Renesas Technology & Solution Portfolio
Of course Renesas is the leading supplier of silicon to the Global Automotive industry. We are best known as the leading supplier of microcontrollers, but we also have an extensive range of analog and power devices, a rich portfolio of ASIC solutions and some very impressive SoCs. All of these are on display here at DevCon and I’d encourage you to take a look at what else we can offer beyond, say, our MCUs whilst you are here.
We’re talking a lot about “enabling the smart society”: the use of electronics, connectivity and energy efficiency – enabled by Renesas – is perhaps more obvious in the car than anywhere else. With Velocity lab we are taking a further step down this path and enabling faster, more efficient development of the systems and software which use our silicon.

3. Microcontroller and Microprocessor Line-up
32-Bit High Performance,
High Scalability & High Reliability
2010
2013
1200 DMIPS, Superscalar
1200 DMIPS, Performance
Automotive & Industrial, 65nm
600µA/MHz, 1.5µA standby
Automotive, 40nm
500µA/MHz, 35µA deep standby
500 DMIPS, Low Power
32-bit
165 DMIPS, FPU, DSC
Automotive & Industrial, 90nm
600µA/MHz, 1.5µA standby
8/16-Bit True Low Power
High Efficiency & Integration
Industrial, 40nm
242µA/MHz, 0.2µA standby
165 DMIPS, FPU, DSC
Industrial, 90nm
242µA/MHz, 0.2µA standby
Embedded Security, ASSP
Industrial, 90nm
1mA/MHz, 100µA standby
Most of you will be familiar with our existing range of MCUs, four of which are used extensively in the Auto industry – V850 and SH in the 32 bit space, 78K and R8C in the 8-bit space.
This year we are launching two extremely important new microcontrollers for the auto industry. The 32 bit RH850 is the industry’s first 40nm MCU, offers industry leading energy efficiency, and an enormous range covering demands from small, single core up to very large, multicore, safety critical applications. The RL78 combines the best elements from both 78K and R8C and new innovations to provide an extremely low power, efficient 16 bit solution.
Paul Kanan has a great presentation later which takes you through all the great new features of these microcontrollers.
Great silicon, innovative features and quality which is second to none are pretty compelling……But they are not enough. Unless systems (and primarily the software for those systems) can be developed quickly and efficiently it becomes hard for customers to take full advantage of the great capabilities offered by the latest silicon. That is where Velocity Lab comes in.
25 DMIPS, Low Power
Industrial & Automotive, 150nm
190µA/MHz, 0.3µA standby
44 DMIPS, True Low Power
8/16-bit
Industrial & Automotive, 130nm
144µA/MHz, 0.2µA standby
10 DMIPS, Capacitive Touch
Industrial & Automotive, 130nm
350µA/MHz, 1µA standby
Wide Format LCDs

4. ‘Enabling The Smart Society’
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. Agenda The Challenge Velocity Lab How does this change the game?
Overview
QuantiPhi
Processor Models
How does this change the game?
Conclusion

6. The Challenge of Automotive Software

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:
controllers, over 150 distributed functions.
Software from multiple sources, e.g. Infotainment.
Development team split globally and across companies
Safety requires ISO
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.
We’re all familiar with the growing importance (some would say dominance) of software in our industry. Here are some of the specific challenges we see in Automotive.
Over 10M lines of code in the typical car – comparable to an airliner’s flight management system

8. Velocity Lab - Overview

9. MCU Ecosystem - Overview
We’re all familiar with the system engineering “V”, and as you would expect there is an extensive range of tools available for our Microcontrollers.
We provide our own Renesas compilers, IDEs (including the new eclipse based e2studio), AUTOSAR MCALs, etc.
Through our extensive network of partners, support and tools are available for every step of the process from up front model based development through autocoding, AUTOSAR software, compilers, debuggers and testers.

10. ADAS Ecosystem Overview
3rd
Party
network
3rd party
network
Car
ECU
Middleware
Dvpt. Tools
Software
Dvpt. Tools Hardware
Hardware
Carmaker functionality
Infrastructure
Customer/Tier1 Application
System integration
Vision application SW
AUTOSAR
RTE
Demo PoC
Vision SDK
Video IF
Open std.
OpenCV
OpenCL
OpenGL
OpenVG
Customization
& porting
Renesas standard
MCU tools
ADTF – EB toolchain
MCAL
RTOS
Operating Systems
IDE : Eclipse
Debugger
Simulator
Compiler
linker
PRISM for
Multi-core
Look into one of the more demanding applications, in this case Advanced Driver Assistance Systems (ADAS), and the picture becomes even more complex. In addition to provide the normal set of tools for an MCU product, Renesas is working to develop software / middleware building blocks to support ADAS applications. Renesas is also partnering with 3rd parties to offer solution-level product offerings or contract development.
Hardware
debugger
Application board
Intermediate
devices
Companion chips
Device
PHY
bin
Power
Supply

11. R-Car* Ecosystem - Overview
Integration
System
Integration
Hitachi
Advanced
Digital
Go all the way up to our high-end SoC, the R-Car, and the array of tools and solutions is quite something! Ranging from on-board hardware IP up through pre-boot, OS, middleware and system integration our partners and Renesas have an extensive range of offerings to support your development needs.
Ok – Renesas and its partners offer pretty much all the things you would expect to support leading MCUs and SoCs. But how could we go further?
Middleware OS
Pre-Boot
Hardware IP
Pre-Boot OS
Middleware
*tentative naming

12. What sort of Development Ecosystem?
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 do we need?
Automated
Virtual
Integrated
Affordable
Accessible
Lets look at the development Ecosystems most of us are using to develop code for microcontrollers.
Velocity Lab is designed to move us from the left to the right side of this chart.

13. VELOCITY LABTM Building Faster Better Cheaper Safer Complex Systems
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!
There are some key elements in Phase 1 of Velocity Lab

14. QuantiPhi

15. Application Everything Else A2D CAN PWM Model-Based SPI OS
The goal of QuantiPhi is to take care of all of the low-level activities to make you successful on Renesas silicon.
This means organizations can focus on their core IP, their ideas, their applications.

16. Auto Generation of Drivers - QuantiPhi
QuantiPhi RE
Easy, Graphical Configuration of Drivers
Model Based Design
(Stateflow/Simulink)
Autocoding from Models
Production Quality Code
Auto Integration with Drivers
C-Code
(Traditional)
Our automotive driver generation tool is QuantiPhi Renesas Edition from SimuQuest. CLICK
It provides easy, graphical configuration of drivers (you don’t need to read the user guide!) CLICK and MISRA compliant drivers CLICK
In a model based development process it integrates directly with your design in Stateflow/Simulink, allowing you to automatically generate code, configure drivers and integrated application code together with drivers CLICK.
The output is production quality code ready for test and release. CLICK
Use with traditionally written applications in C-code is, of course, very straightforward. Overall, this level of capability goes far beyond any of our competitor’s offerings. CLICK.
We are also working to add AUTOSAR MCAL configuration from RH850 onwards, allowing our customers to use a single tool chain regardless of whether they are working on a c-code, model based or AUTOSAR project.
MISRA Compliant Drivers
AUTOSAR
AUTOSAR MCAL

17. SimuQuest QuantiPhi 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
SimuQuest
The latest version of QuantiPhi is launching on the RL78 automotive MCUs this fall.
We are also supporting the latest version of the SH micro designed specifically for Hybrid and Electric Vehicle use (with on board, hardware based resolver decoder and motor control unit)
Importantly we are also preparing to launch QuantiPhi for our new RH850 range of microcontrollers, starting with Body and Engine Control versions

18. RL78 MICON Racing with QuantiPhi
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
Micon cars are autonomous race cars which navigate through a range of curves, right angle turns and jogs using onboard sensors and control strategy.

19. Processor Simulation Models

20. What is a Processor Simulation Model?
Virtual ECU
Power Supply Models
Mixed Signal Models
Mixed Signal Models
Power Device Models
Virtual Microcontroller
Peripheral Models
Peripheral Models
Peripheral Models
Peripheral Models
Peripheral Models
Timed Core Model
Fast ISS Core Model
Peripheral Models
Peripheral Models
Peripheral Models
Virtual model of a microcontroller typically contains:
Interchangeable core models – one which is “timed” and provides 95-98% cycle accuracy. This model is used to simulate timing critical tasks. The other core model is a Fast Instruction Set Simulator which trades off some cycle accuracy for greater simulation speed (typically close to real time) and can be used for the majority of development work.
Once you have a virtual model of the Microcontroller, you can add models of other silicon to build a model of your complete ECU
Peripheral Models
Peripheral Models
Peripheral Models
Peripheral Models
Passive Device Models
Passive Device Models
Passive Device Models
Passive Device Models

21. Processor Models Traditional Process: Hardware Design Proto Build
Software Development
With Processor Models:
Software Test
Launch
Hardware Design
Acceleration
Proto Build
Int’n
Test
Software Development
Launch
Software Test
AND:
Customers
Now let’s take a look at how processor models help our customers. This picture is deliberately simplified a little, but it does show the important principles CLICK
In a traditional development process CLICK you pretty much have to complete your hardware design and an initial prototype build CLICK before you can start your software development CLICK and then test it. CLICK. Eventually you get to launch (probably after a lot of iteration!). CLICK
Now lets add processor models (model based approaches and AUTOSAR also help here) CLICK
In this approach software development and test are pulled ahead and happen first (a better systems engineering approach anyway) CLICK
Hardware design and proto build can now happen later in the process – in fact, you can use processor models to help select the right hardware CLICK and the two streams come together at launch CLICK which of course is much accelerated compared to the traditional approach.
Whilst time to market is a big benefit, that is not all CLICK.
The processor model gives you a virtual platform which has several advantages. You gain far greater visibility during development than is possible with real hardware CLICK
The virtual platform is much easier to share with global teams, CLICK with your suppliers, CLICK with your partners, CLICK and, increasingly, with your customers. CLICK
Add fault injection CLICK and you can perform the testing required for functional safety (which is often impossible on hardware). CLICK
Add plant models to simulate the rest of your system CLICK and you have the capability to perform whole system testing earlier, faster and cheaper than on a HIL (Hardware in the Loop) stand. CLICK
Add in multi-ECU simulation and you can now test and develop the entire vehicle electronic system together – tackling one of the OEMs biggest challenges.
Fault
Injection
Validate
Error Handling
Global
Teams
Virtual
ECU
Plant
Models
Whole System
Test
Multiple ECUs
Whole Vehicle Test
Partners
Suppliers

22. Processor Models 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)
V850 and SH2 processor models are available today and have been used successfully in development
RH850 processor models will be available form early next year, and (for the first time) a core model of a 16 bit Renesas microcontroller, the RL78, will also be available next year.
Three of the leading software simulation companies are here with us at DevCon.

23. How Does This Change the Game?

24. HEV/EV Design 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!
QuantiPhi
Read User
Manual
Write & Test
Drivers
Code
Gen
Re-read
Re-write

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!
QuantiPhi
Code
Gen
Application
Application
Hardware Design
Hardware Design
Re-design
Re-design

26. HEV/EV Design – Gen 3 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
Now let’s fast forward two years – Acme are now planning their 3rd Generation product

27. HEV/EV Design – Gen 3 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
Now let’s fast forward two years – Acme are now planning their 3rd Generation product

28. Conclusion

29. VELOCITY LABTM Building Faster Better Cheaper Safer Complex Systems
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!

30. ‘Enabling The Smart Society’
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. Questions?