e2Studio – Getting Started

Renesas Technology & Solution Portfolio The wealth of technology you see here is a direct result of the fact that Renesas Electronics Corporation was formed on April 1, 2010 as a joint venture between Renesas Technology and NEC Electronics — Renesas Technology having been launched seven years ago by Hitachi, Ltd. and Mitsubishi Electric Corporation. There are four major areas where Renesas offers distinct technology advantage. --The Microcontrollers and Microprocessors are the back bone of the new company. Renesas is the undisputed leader in this area with 31% of W/W market share. --We do have a rich portfolio of Analog and power devices. Renesas has the #1 market share in low voltage MOSFET solutions. --We have a rich portfolio of ASIC solution with an advanced 90nm, 65nm, 40nm and 28nm processes. The key solutions are for the Smart Grid, Integrated Power Management and Networking --ASSP: Industry leader for USB 2.0 and USB 3.0. Solutions for the cell phone market -- Memory: #1 in the Networking Memory market

Microcontroller and Microprocessor Line-up 2010 2012 1200 DMIPS, Superscalar 1200 DMIPS, Performance Automotive & Industrial, 65nm 600µA/MHz, 1.5µA standby 8/16-Bit True Low Power High Efficiency & Integration 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 Industrial, 40nm 200µA/MHz, 0.3µA deep standby 165 DMIPS, FPU, DSC Industrial, 90nm 200µA/MHz, 1.6µA deep standby Embedded Security, ASSP Industrial, 90nm 1mA/MHz, 100µA standby Those of you who have attended the last DevCon in 2010, the left side of this slide should look familiar. In 2010, as a result of the merger between Renesas Technology and NEC Electronics, we started offering MCU solutions based on these five cores. The R8C and 78K were mainly focusing on low end 8/16 bit applications in both automotive and industrial applications,. The RX with 32 bit CISC core was mainly offering solutions for Industrial and consumer applications.  The high-end V850 and SH cores with 32-bit RISC architecture were very successful in high end automotive and industrial applications.   Within 6 months after the merger, we launched a brand new 16-bit product family named RL78, combining the low power flash technology and the CPU core from NEC’s 78K product line and innovative peripherals from Renesas’ R8C product family. The RL78 family is a great example of the synergy effect of this merger. The RL78 is now our main focus product line for cost sensitive low power applications. It consumes only 144uA/MHz power in active mode and only 0.2uA in standby mode. With up to 44DMIPS throughput, it offers much higher performance compared to any other 8/16 microcontrollers in the market place. The RX family continues to be our flagship 32-bit family for Industrial and consumer applications. With 100 MHz single cycle flash, 1.65DMIPS/MHz throughput and packed with connectivity peripherals it  is ideal for digital signal controller applications. Since its introduction in 2009, we are rapidly expanding the RX product line. Now we have more than 500 different RX MCUs covering from 32KB to 2MB flash memory options. Similar to the RX, we have recently announced the launch of our next generation high-end 32 bit microcontroller architecture for automotive applications. The new family is called RH850 and provides a next-generation migration path to automotive customers currently using V850 or SH in their application. For Industrial customers currently using V850 or SH, the migration path is the RX product family. Very soon we will launch a 240MHz RX product line which can cover the need of Industrial customers requiring more than 100MHz performance. So, in summary, from 2013 and beyond, we will mainly be focusing on the three CPU cores, RL78, RX, and RH850, to cover the broad spectrum of the industrial and automotive application space, and we will continue to support legacy architectures like R8C, 78K, SH, and V850 for existing customers.    In addition to the above mentioned microcontroller families, we do have an ASSP family called R-Secure which offers a wide range of products for embedded security applications. In this presentation I will mainly focusing on R-Secure product line. 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

‘Enabling The Smart Society’ Challenge: “MCUs continue to become more complex especially when creating applications to enable the Smart Society, and therefore the tools become more complex as well. As a result we must create tools that enable complete debug capability at minimal cost.”  Solution: “OpenSource IDE’s with custom layers must be developed to enable engineers to create applications for the 2010’s”

Agenda Introduction to e2Studio Tools and Installation Workspaces and Projects Project Wizard Editor Features Basic Simulation and Debugging Lab Summary

INTRODUCTION AND INSTALLATION This module introduces the Eclipse ecosystem, including a brief history, details of licensing, and the role played by Renesas e2Studio. 6

About e2Studio An Integrated Development Environment for cross-platform development targeting Renesas processors Based on the Eclipse workbench Extendable open source tooling technology Large ecosystem of compatible components Widespread user community Incorporates C/C++ Development Tooling (CDT) components Code editor Build system Basic debug capabilities Extensive support for Renesas processors Project creation wizards Toolchain integrations Remote launch and advanced debug capabilities e2Studio is an IDE designed specifically for cross-platform development of embedded applications for deployment on Renesas processors. It is based on Eclipse, an open source development tooling platform and infrastructure. Eclipse has been widely adopted by embedded systems developers and it’s use as the foundation for e2Studio allows developers to take advantage of a wide range of additional Eclipse-compatible components. e2Studio also makes use of the Eclipse C/C++ Development Tooling to provide code editing, project build and basic debugging capabilities. e2Studio extends the capabilities of Eclipse and CDT with project creation wizards, toolchain integrations, remote launch and advanced debug capabilities. These components are designed to deliver a powerful and flexible IDE specifically for Renesas processors. 7

e2Studio With Eclipse/CDT e2Studio Features Other Features Other Features C/C++ Development Tooling (CDT) This block diagram illustrates how CDT and other features build on the Eclipse Platform, extending it’s capabilities. The e2Studio features build on both CDT and the Eclipse Platform. Eclipse Platform 8

e2Studio Advanced Features Project wizards Create skeleton projects targeting Renesas processors Projects build and run without modification Integration with KPIT GNU toolchains RX RL78 V850 Cross-platform launchers Download to remote hardware via debug probe Simulator alternative where hardware unavailable Advanced debug capabilities Simplified access to I/O registers Non-invasive inspection and tracing of target state The project wizards within e2Studio allow the developer to create skeleton projects which include startup code for Renesas processors and will therefore build and run without any further customisation. Projects are typically built using GNU toolchains available from KPIT. RX, RL78 and V850 architectures are supported. Critically, e2Studio provides the debug infrastructure which allows application code to be downloaded to target hardware via a suitable debug probe. It also supports the debugging of code within the GDB simulator where hardware is not yet available. Finally, e2Studio enables developers to take full advantage of peripheral I/O and debug capabilities within the Renesas range of processors, including the non-invasive inspection and tracing of target state. 9

e2Studio Download and Setup Procedure Complete KPIT Cummins registration form Download KPIT GNU Tools Download e2Studio When setting up e2Studio, the IDE and the toolchains are downloaded separately. It is necessary to register on the KPIT Cummins website to gain access to the GNU tools downloads. Integration of the GNU tools with e2Studio occurs automatically once the tools and the IDE have been installed. Install KPIT GNU Tools Install e2Studio 10

KPIT Cummins Registration Register at the KPIT GNU Tools web site http://www.kpitgnutools.com Select Register link and complete registration form Receive toolchain activation code by email In order to register for toolchain downloads, navigate to the KPIT GNU Tools web site, click on the Register link and complete the form. You will be sent a password for the web site and a toolchain activation code by email. 11

KPIT GNU Tools Download Download KPIT GNU Tools from the KPIT GNU Tools web site http://www.kpitgnutools.com Select Free Downloads tab and complete login form if necessary Locate toolchain for appropriate target architecture in the Windows Hosted ELF Toolchains section You can then login to the KPIT GNU Tools website. Appropriate toolchains for each of the target architectures supported by e2Studio are located in the Windows Hosted ELF Toolchains section on the Free Downloads tab. Most developers will be working with a single architecture and will need to download only one of these toolchains. 12

KPIT GNU Tools Installation Double click on downloaded executable file to launch installer Default installation options are appropriate Double click on the downloaded KPIT GNU Tools installer to begin installation. The default installation options are appropriate for use with e2Studio. 13

e2Studio Download Download e2Studio from the Renesas web site http://www.renesas.com Select Development Tools tab Select IDEs and Project Managers category Select e2Studio The e2Studio IDE is downloaded from the Renesas web site. Navigate to the IDEs and Project Managers category on the Development Tools tab and select e2Studio for download. 14

e2Studio Installation Double click on downloaded executable file to launch installer Default installation options are appropriate Double click on the downloaded e2Studio installer to begin installation. The default installation options are usually appropriate. 15

e2Studio Project Creation and Build This module describes the capabilities of the Eclipse platform, the extensible framework supporting Renesas e2Studio. 16

Workspace Preferences e2Studio Workspaces e2Studio prompts for a Workspace folder at launch Multiple related projects created in each Workspace Projects of selected workspace presented in Project Explorer view One project per application under development Workspaces also store global e2Studio preferences Avoid workspace paths containing spaces Project A Project Folder Before working with e2Studio, it is important to understand the concept of Eclipse workspaces. e2Studio will prompt for a workspace folder at launch. The workspace is a mechanism for grouping multiple development projects and IDE preferences. The developer will usually create one project per application under development. Related projects should be located in a single workspace and will be presented together in the Project Explorer view. Non-related projects may be placed in their own workspaces but many developers choose to use a single workspace for all their projects. A new workspace is created simply by specifying an empty, or non-existent folder when launching e2Studio. When using GNU toolchains, workspace folders containing spaces in their path should be avoided. Project B Project Folder Workspace Preferences 17

e2Studio Projects Projects created using a New Project Wizard Project folder typically created within workspace folder Project content created within project folder Source Code Sub-Folders Build Output (config A) New projects are always created using the New Project Wizard. Project content is created within a project folder. The project folder is typically located under the workspace folder, but it is possible to override this behaviour and place the project elsewhere. Project properties, source code and build output will all be located within the project folder. Build Output (config B) Project Settings 18

e2Studio New Project Wizards Launch from workbench File menu or Project Explorer context menu Select the C Project or C++ Project wizard from the tree C project wizard for C source code application C++ project wizard for C and/or C++ code application Start C/C++ Project Wizard Toolchain Target-Specific Build Settings The New Project Wizard may be launched from the workbench File menu or the context menu of the Project Explorer view. The developer should select the C project wizard or the C++ project wizard depending on whether the project will contain any C++ code. If the user creates a C project then project properties specific to the C++ language are not presented within the user interface. Library Generator Default Debug Settings Finish 19

Project Name, Type and Toolchain Enter new project name Select Executable (Renesas) >> Sample Project type New project will include startup code and skeleton main() Project builder will generate a fully linked application Select toolchain Toolchain architecture will influence subsequent wizard pages On the first page of the project wizard, the user provides a name for the project and chooses whether the project will use the managed build system or allow the user to provide a makefile. Another option allows for the creation of a debug-only project suitable for debugging an application which has been built outside the IDE. The user must also choose an appropriate toolchain for the processor architecture of the intended target. 20

Target-Specific Settings Select toolchain version if multiple versions installed Select CPU series, type and endianness where applicable Selections may affect processor instruction set Critical for correct execution on target hardware Select other CPU options On the next page of the wizard, the user selects architecture-specific build options. The precise options presented depend on the toolchain selection made on the previous page. Typical options allow for the selection of the CPU family, CPU part and processor endianness. Many of these options may be critical to the correct execution of the application on the target. In cases where more than one version of the selected toolchain is installed, the user may also select the toolchain version to be used when building the project. 21

Library Generator Settings Select library source Newlib library – complete ISO C library supporting C/C++ code Optimized library – subset of ISO C library supporting C code Select required library modules Select library generation Pre-built for convenience Project-built for source- level debugging On the next page of the wizard, the user selects whether to use the newlib implementation of the Standard C library or a size-optimised implementation. The size-optimised implementation does not fully support C++ code. The user must also decide whether to use a pre-built version of the library for speed or to build the library as part of the project, allowing the stepping into library code while debugging. Finally, the user selects which modules of the library will be included in the project. 22

Default Debug Settings Select default debug mode Hardware Debug debug probe and target device must be specified Simulator Debug Release optimised build not intended for debugging Selection determines initially active build configuration On the final page of the wizard, the user selects the initial method of debugging the application that will be built within the project. In addition to the typical debugging of application code on the target hardware, options are available for debugging using the HEW debugger, the GDB simulator or an arbitrary debugger launched from a script. The launch type selected in this dialog will also determine the initial project build configuration. When using hardware debugging, the debug probe and precise CPU part should also be selected. 23

e2Studio Project Layout Project source files typically located within src folder Multiple build configurations per project Release Hardware Debug Debug (simulator) Build output located in corresponding build configuration folders On completion of the new project wizard, the project and its resources will appear in the Project Manager view. Source code and header files are located in the src folder within the project. Virtual folders are used to present the generated binary files and the header files used by the project. A number of build configurations are created by default, allowing the user to customise the build for simulations, hardware debug and release. Build output is placed in a build configuration folder corresponding to the active build configuration. 24

Project Editing Create new source files via context menu wizards New >> Source File – for C or C++ files (*.c, *.cpp) New >> Header File – for header files (*.h, *.hpp) New >> Source Folder Any new source files are typically added to the project under the src folder directly or within a sub-folder. However, it also possible to define other folders in which source code will reside by manipulating the project’s properties. 25

C/C++ Coding Assistance Double click on source file in the Project Explorer to edit Advanced C/C+ Editor Syntax colouring Code completion Code templates Code indentation Refactoring Open declaration Outline view Virtual folders C/C++ search CDT implements many forms of coding assistance to make the task of authoring C/C++ code as easy as possible. A C/C++ syntax-colouring editor is provided which incorporates facilities for code completion, code templates, indentation and refactoring. The structure of individual C/C++ source files is analysed as a background activity and used to present a tree-like representation of code structure within the Project Manager view and an Outline view. C/C++ search and replace facilities allow for the renaming of symbols across multiple files and for navigation from a symbol reference to the corresponding symbol declaration. 26

C/C++ Managed Build System All source files under src folder are built C source (*.c) C++ source (*.cpp) Assembly source (*.asm) Select active build configuration prior to build Build on demand via workbench menu items Project >> Build Project (builds currently selected project) Project >> Build All (builds all projects in workspace) Monitor build progress in Console view Review build issues in Problems view Double click to open related source code in C/C++ Editor Build options Build Automatically (not recommended for C/C++) Save automatically before build CDT includes a managed build system which analyses the content of a C/C++ project and determines how to build it based on the naming of source folders and files. The build system adapts to the addition and removal of source files automatically. The required build configuration is selected prior to build. Build progress may be monitored within the Console view and any build issues are presented within the Problems view, providing rapid access to the problematic source code. 27

Extended Project Properties Toolchain-related properties specific to a project or file First select a project or file in Project Explorer Project >> Renesas Tool Settings Code generation, linking and archiving options Standard C library generation and usage options Linker script editing The toolchain integrations provided with Renesas e2Studio enable the adjustment of many toolchain-specific build properties including code generation options, code linking and archiving options. They also allow control of the generation and usage of the standard C library and of the linker script used to describe the mapping of code and data to the physical memory on the target. 28

Frequently Used Project Properties Limited set of options available via quick settings dialog Project >> Renesas Quick Settings Optimisation for speed, size or both Debug information – no effect on generated code Warnings – simplified control of warning groups List files – compiler, assembler, linker listings Commonly used project properties are also accessible via a Quick Settings dialog. Note that code optimisation is disabled by default when one of the debug-oriented build configurations is selected. It is possible to undertake source-level debugging of optimised code but this can be confusing where processor instructions have been reordered or eliminated by the optimiser. The options to generate debug information and list files have no effect on the generated code. 29

Execution In Simulator Immediate execution of applications in the absence of target hardware Run As >> Renesas GDB Simulator Running Standard I/O channels accessible via Console view Limitations Instruction set simulation only No peripheral emulation Once an application has been built successfully, it may be executed directly within the GDB simulator without a debugger and without use of target hardware. The application’s standard I/O channels are then accessible via the Console view. However, note that the simulator performs no emulation of peripherals and its use is therefore limited to code which does not reference peripheral hardware. 30

E2STUDIO BASIC DEBUGGING This module introduces the basic debugging features of Renesas e2Studio . These features adapt the Eclipse platform and CDT to enable cross-platform debugging targeting Renesas processors. 31

e2Studio Cross Development Launchers Launchers enable the execution and debugging of non-native code Support for simulators and remote hardware using the GNU debugger (GDB) Download and debug via on-chip debug hardware Support for a number of debug probes Renesas E1 Renesas E10A Renesas E20 Renesas IECUBE Segger J-Link Additional support for debugging using HEW and for custom debug scripts Of critical importance for embedded development, Renesas e2Studio extends the Eclipse platform launch mechanism to enable the execution and debugging of non-native code, either on a simulator or on remote hardware using the GNU debugger, GDB. e2Studio supports a number of debug probes directly, and can additionally launch a debug session using the Renesas High-performance Embedded Workshop (HEW) or a custom debug script. 32

e2Studio Launch Configurations One launch configuration per application and per debug target Encapsulates all launch-related parameters Launch type (hardware or simulator) Application executable file Connection parameters Debug probe details Launch configuration for default debug mode generated by project wizard Other configurations generated on initial launch within e2Studio Customization possible but seldom necessary Run >> Debug Configurations... Prior to launching a debug session, it is necessary to create a launch configuration which describes how the session will be launched. A separate launch configuration is required for each combination of application executable file and debug target. A launch configuration for the default debug mode specified within the new project wizard is created automatically. Other launch configurations are generated on initial launch within e2Studio. It is possible to customise these launch configurations but this is seldom necessary. 33

Launching e2Studio Debug Sessions Specify launch type at point of launching First select a project or executable file in Project Explorer view Run >> Debug As >> Renesas GDB Hardware Launch Run >> Debug As >> Renesas GDB Simulator Launch Open Renesas Debug Perspective Alternative presentation of views within Eclipse workbench Views for inspection and manipulation of target state Standard CDT views updated when execution suspends C/C++ editor presents source code at program counter Variables (local variables only) Expressions (including global variables) Registers Memory Disassembly A debug session is launched by selecting a project or executable file within the Project Explorer view and then invoking the Debug As menu item from the Run menu in the workbench or the Project Explorer’s context menu. The launch type, hardware or simulator, is specified at the point of launch. e2Studio will prompt the user to open the Renesas Debug perspective when launching a debug session. A perspective is simply an appropriate arrangement of Eclipse views for a particular activity. The Renesas Debug perspective includes many views which present the state of the target while debugging. The content of these views is updated each time code execution on the target becomes suspended. The current value of the processor’s program counter register is used to present the corresponding source code within the source code editor and, optionally, within the Disassembly view. 34

Renesas Debug View Control execution of code on target Toolbar buttons Suspend Resume Terminate Step into Step over Step return Instruction stepping mode Call stack Select stack frame to inspect related local variables One active debug session only Terminate any existing session before launching another Use Reload to avoid termination within edit/build/debug cycle Execution of code on the target is controlled using a set of toolbar buttons within the Renesas Debug view. An instruction stepping mode may be selected, allowing the code to be executed one instruction at a time. The current call stack is also presented within the Renesas Debug view. Users may click on a stack frame within the call stack to navigate to the associated source code and review local variables associated with that frame. 35

Breakpoints Applicable to both hardware and simulator debug launches Create via context menu of left margin in C/C++ editor First open source file Toggle Breakpoint Enable/Disable Breakpoint Review and manipulate all breakpoints within Breakpoints view Breakpoints may be set by right-clicking in the left margin of the source code editor and selecting the “Toggle Breakpoint” menu item. All breakpoints are also listed in the Breakpoints view where they may be disabled and re-enabled as necessary. 36

Summary

Questions?

‘Enabling The Smart Society’ Challenge: “MCUs continue to become more complex especially when creating applications to enable the Smart Society, and therefore the tools become more complex as well. As a result we must create tools that enable complete debug capability at minimal cost.”  Solution: “OpenSource IDE’s with custom layers must be developed to enable engineers to create applications for the 2010’s” Do you agree that we accomplished the above statement? 39