1. The Importance of Open Source Tooling for ADAS and Automated Driving
Featuring e2 studio and Renesas R-Car
The open, innovative and trusted platform
for assisted and Automated drive
Overview of why Eclipse and Open Source tools makes sense for Renesas for ADAS In particular we will explain:
Using CDT to build open source tooling for ADAS
Using GDB and CDT to provide heterogeneous multicore debugging using Eclipse
Using Trace Compass to build advanced tracing tools for ADAS
Using TCF and CDT for Linux application debugging ADAS and Automated Drive applications need the high-end computing power of the SoCs to analyse the car’s surroundings and for cognitive computing processing.
This requires a broad spectrum of flexible, programmable cores and highly optimized hardware accelerators delivering the highest performance at lowest power consumption, specifically architected for algorithms performing object detection, classification and deep neural networks.
As ADAS, and next Automated Drive, requires not only this drastically increasing performance and features in the silicon, but also the goes into high volume, SoCs are newly designed to be available at highly competitive pricing. Thus developers face the challenge that the new silicon is not available at the start of the development, and the existing silicon cannot be used as it simply does not have the features.
Therefore developers need to start coding and debugging using simulators, with ideally seamless transition to the hardware once the final silicon is available. Eclipse is ideal as it can support this, as it offers diverse tooling within a single central interface.
Users can start on a virtual platform and migrate when ready to use real hardware within the same UI. Plus Eclipse offers multicore debugging and tracing using the latest tools from hardware vendors. Since a silicon supplier develops some tools in-house, but relies also on tools of 3rd parties, an open source environment is mandatory to enable an ecosystem to deliver the leading edge tools.
Renesas will explain its Eclipse strategy for solutions for ADAS and Automated Driving, as part of the Renesas autonomy platform. The key message is that the developer will decide what the future of driving will look like, and e2studio is an important part this.

2. Company Profile: Renesas Electronics Corporation
Operations started: 1st April, 2010 Headquarters
Toyosu Foresia, Tokyo, Japan
Representative Directors
Chairman: Tetsuya Tsurumaru
President & CEO: Bunsei Kure
Number of Employees
19,160 employees (consolidated basis – as of Mar 2016)
Major Operations
Research, development, design, manufacture, sale and servicing of semiconductor products

3. Automotive Security Gateway
Introducing Renesas Autonomy: The End to end Platform for assisted & Automated drive
Deciding
Controlling
Driving (Powertrain)
Braking/Chassis (Safety)
Steering (EPS)
Automotive Security Gateway
Multi-Camera Sensing and Visualization
Sensor Fusion Collection and Fusion of Sensor Data
Introduction to Renesas automony
Radar Sensing
Cognitive Decision Making
Connectivity Geo and Traffic Information
Sensing & Analyzing

4. From ADAS towards AD ADAS Automated Driving
AEB: Advanced Emergency Braking
ACC: Automatic Cruise Control
LKA: Lane Keep Assist
LCA: Lane Change Assist
CTA: Rear Cross Traffic Alert (front/rear)
TJA: Traffic Jam Assist
From ADAS towards AD
ADAS
Automated Driving
Forward driving
Auto Pilot
ACC
City pilot
AEB
LKA
AEB
+ steering
Highway pilot
TJA
Side/rear
LCA
Market is converging.
CTA
Parking
Assisted Parking
Auto
parking
Remote parking
Valet
parking
Level 1 Driver Assistance
Level 2 Partial Automation
Level 3 Conditional Automation
Level 4 High Automation
Level 5 Full Automation
Moving to Full Automation increases complexity dramatically from Assisted Driving.

5. Open and innovative – autonomy platform
“Quick Time to Market”
Rich ecosystem 3
Ecosystem
Choose complete solution or build your own
“Development Efficiency”
Solution Platform 2
Renesas + Ecosystem
Operating System
Middleware
HW Device
SW Drivers
HW & SW Tools
Hardware Accelerator
Functional Safety
ISO 26262
Algorithms
“Technical Differentiation”
Unique features 1
Renesas original
Trusted Roadmap

6. Why an open platform for Automated Driving (AD)?
The software and tooling requirements for Autonomous Driving are diverse and complex.
Companies do not have the desire and in some cases technology to invest and build the entire AD toolchain themselves.
The cost and resource to do so would be huge.
Therefore consortiums, partnerships and open source development communities will be used to reduce the cost and entry to the market.
Specialist companies can focus on key areas of the AD toolchain, e.g. Simulation.
OEM’s can concentrate on differential areas to increase their business.
Collaboration and Open Platforms for AD make sense for all companies involved!

7. Synergy with Eclipse and Open Source community mind-set and approach.
R-Car Consortium
Renesas have engaged with numerous 3rd parties as part of the the R-Car consortium
Renesas are committed to an open platform approach
The R-Car Consortium aims to lead the market through
Collaboration with partners
Mutual cooperation to shorten the development period (accelerate development)
Enhancement of a support system
Implementation of next-generation ADAS and AD solutions
Synergy with Eclipse and Open Source community mind-set and approach.

8. R-Car solutions vision
OEM
SoC Platform solution
Lead Tier 1
with own Vision IP
(SW & HW)
HW Device
SW Drivers
Devt Tools
Op. System
Application Software
Middleware
Device Solution
Platform
Solution
Camera
solution
Tier1
Integrated ADAS system
Lead Tier1 model
Vehicle
Midrange Tier1 model
Renesas Ecosystem
Midrange Tier 1
Application software package
Competitive system cost
Open SW framework
Short time to market
Scalable solution
Cutting edge vision performance
State of the art Functional Safety
Easy to use tools & software libraries
Ultimate objective is to offer a competitive and open solution

9. Why Eclipse?

10. Renesas e2 studio
Previously Renesas provided proprietary IDE tools to their customers.
The burden of developing core tools functionality was taken by Renesas.
In 2011 Renesas started the e² studio project based on Eclipse.
Renesas could then focus on Renesas functionality and less on core function.
This project covered general purpose Renesas MCU such as RX and RL78.

11. Initial Requirements for ADAS Tools
High performance debugging of R-Car SOC
Real-time OS (RTOS) or bare metal high-performance debugging solution.
Customised plugins specifically for debugging heterogeneous cores or ADAS applications.
ADAS system debug complex – tools required to assist the customer and debug complex use cases.
Linux target debugging of Applications on the R-Car SOC
User-space Linux application debugging
Development using Virtual Platforms
Renesas customers want to develop their software without the dependency of real silicon.
Allow rapid prototyping of software on host machines (x86).
Simulation of real hardware.
Allow faster time to market by allowing development to start in advance of real silicon.
One tool required to satisfy all use cases for our customers!

12.       Renesas e2 studio
e² studio was a natural choice for the ADAS tools project.
The product already existed and supported other Renesas MCU and SOC.
Renesas customers were already familiar with the tool.
The diverse use cases for the ADAS tools can all be satisfied within Eclipse.
Eclipse is an open tools platform already in use by partners and 3rd party tools providers.
Renesas can access a huge eco-system of open tools when using Eclipse.      

13. Why Eclipse made it easier?

14. Open Community – building blocks
Eclipse offers a wide and varied community which are developing software for diverse use cases.
There are many projects running which could provide plugins and starting points for many features of e2 studio.
In particular we would like to share and discuss the following:
C/C++ Development ToolKit (CDT)
Trace Compass
Nebula
Eclipse TCF (Target Communication Framework)

15. Open Community – C/C++ Development ToolKit (CDT)
Renesas build the e² studio product using the CDT Eclipse project.
CDT Project has been running 15 years and used for many commercial products.
Popular in Embedded IDE domain area.
Features include:
Support for project creation.
Managed build for various toolchains.
Source navigation.
Call graph.
Code editor with syntax highlighting.
Source code refactoring and code generation.
Visual debugging tools, including memory,
registers, and disassembly viewers.

16. Open Community – C/C++ Development ToolKit (CDT)
Using CDT as a basis for the ADAS e2 studio product enables Renesas to focus on the areas that increase customer productivity.
CDT also provides GDB integration. This is a key requirement as the Renesas debugger is built on GDB.
Renesas can then access multicore heterogeneous debugging capability supported by CDT and GDB.
This allows our customers to debug the ARM cores and IMP-X5 IP and a 64-thread MIMD (Multiple Instruction, Multiple Data) processor concurrently in the same IDE.

17. Open Community – GDB/Multicore
ARM A53 Core.
IMP-X5 Core.
IMP-X5 Simulator – large number of cores and threads.

18. Open Community – Memory & image view
Viewing images is a key part of the Renesas ADAS tooling.
It needed to support multiple image formats.
We used the provided framework to create another memory renderer.
It also uses the Renesas real-time memory facility so the view can be refreshed automatically at the user specified refresh rate.
The key application area for Renesas currently is “Smart Camera” so this enables users to view images easily within the IDE.

19. Open Community – Memory & image view
Image View based on Memory View
Real-time refresh of the memory view. Refresh the image automatically.

20. Open Community – Trace compass
Trace is a very important aspect of the ADAS e2 studio environment.
With complex software designs and multicore, customers need this trace data to work out where problems occur when debugging.
e² studio supports the high-end Lauterbach JTAG probes which support the latest ARM CoreSight IP.
This can output a huge level of trace data and manipulating this level of data in the IDE has always traditionally been a problem for the development team.
To improve this situation the development team used the Trace Compass project.
Lauterbach debugger integration and full trace support is a key requirement for ease of debugging for customers.

21. Open Community – Trace compass
Trace Compass provide Linux trace views as standard which we also need for this project.
However they also provide an extensible framework which we use to build up our own trace data related views.
This framework is capable of supporting huge amounts of data with filtering and search functions also provided.
Trace Compass enables visualisation of customer trace output for easy debugging.

22. Open Community – Trace compass
Trace Compass was used as a basis to create our CoreSight trace based plugins:

23. Open Community – Trace compass
DTA Trace based on Trace Compass:

24. Open Community – NEBULA
Visualisation of data is always a problem when huge data sets are captured within the debugger.
This can be made easier by charting or graphs to visually show the data to users.
This is made easier by the Nebula project.
This project provides functionality explicitly for this purpose for showing data sets visually.

25. Open Community – NEBULA
In the ADAS e² studio project this is used by the bus monitoring plugin.
This view can show bus activity for all of the various bus within the R-Car device.
It is useful for determining bottlenecks when diagnosing performance problems.
Nebula enables easy visualisation of debugger data in e2 studio.
Visualisation of the data ensures the debugger is easier to use for customers.

26. Open Community – NEBULA
Bus monitoring view from ADAS e² studio:

27. Open Community – Eclipse TCF
Linux target debugging is supported by CDT and the Linux Tools Project which is a key use case for our tool.
We use this along with the Target Communication Framework (TCF) to communicate with the hardware over Ethernet.
Enabled very fast support of Linux target debugging on R-Car.

28. Partnerships

29. Partnerships
Using the open source Eclipse framework makes it easier to collaborate with our partners.
The platform is open and the interfaces well known. This has enabled us to pick up plugins from other companies for usage in the product.
In addition partners familiar with Eclipse and GDB find it much easier to contribute and work with Renesas tools.
Examples for the ADAS e² studio include:
Lauterbach – Trace32 debug probe integration
ASTC – Virtual Simulation
ARM – ARM Compiler Build Plugin integration

30. Future plans

31. For AD applications Renesas realise that customers will expect more.
Future plans
Traditionally debugging close to the hardware has been the Renesas focus which is important as a semiconductor.
We are providing this debug capability by specialist debugging views that are needed by customers developing for AD.
Renesas are now ready to become more involved and contribute to the ADAS Eclipse working groups who are providing functionality higher in the AD toolchain.
For AD applications Renesas realise that customers will expect more.
Many more development tools for pre-development, simulation, data analysis are required for efficient AD development.

32. Future plans OpenPASS Eclipse Sumo OpenADx OpenMDM App4MC
Renesas are motivated to be involved in the Environment Simulation and Big Data analysis areas in the near future.
We are planning active involvement with the following working groups:
OpenPASS
Virtual traffic and environment simulation to assess the advanced driver assistance systems and partially automated driving functions.
Eclipse Sumo
Simulation of Urban Mobility (SUMO) is a microscopic and mesoscopic traffic simulator.
OpenADx
Autonomous Driving working group.
OpenMDM
openMDM® 5 is a kit of components and concepts, which can be used to compose applications for measured data management systems. 
App4MC
Multicore timing, optimization and tuning.

33. Future plans
Committed to create more tools to assist development further up the open platform with Eclipse

34. Renesas are committed to contribute in Open Source ADAS Tooling!
Future plans
Renesas can understand and appreciate the value of the Open Source Communities.
Our motivation to contribute and invest in Open Source groups underlines the value we receive.
Renesas are committed to contribute in Open Source ADAS Tooling!

35. Thank you – questions?