e 2 Studio Getting Started

Transcription

1 e 2 Studio Getting Started Renesas Electronics America Inc.

2 Renesas Technology & Solution Portfolio 2

3 Microcontroller and Microprocessor Line-up bit 8/16-bit 1200 DMIPS, Superscalar Automotive & Industrial, 65nm 600µA/MHz, 1.5µA standby 500 DMIPS, Low Power 8/16-Bit True Low Power High Efficiency & Integration 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 3

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

5 Agenda Introduction to e 2 Studio Tools and Installation Workspaces and Projects Project Wizard Editor Features Basic Simulation and Debugging Lab Summary 5

6 INTRODUCTION AND INSTALLATION 6

7 About e 2 Studio 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 7

8 e 2 Studio With Eclipse/CDT e 2 Studio Features Other Features Other Features C/C++ Development Tooling (CDT) Eclipse Platform 8

9 e 2 Studio 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 9

10 e 2 Studio Download and Setup Procedure Complete KPIT Cummins registration form Download KPIT GNU Tools Download e 2 Studio Install KPIT GNU Tools Install e 2 Studio 10

11 KPIT Cummins Registration Register at the KPIT GNU Tools web site Select Register link and complete registration form Receive toolchain activation code by 11

12 KPIT GNU Tools Download Download KPIT GNU Tools from the KPIT GNU Tools web site Select Free Downloads tab and complete login form if necessary Locate toolchain for appropriate target architecture in the Windows Hosted ELF Toolchains section 12

13 KPIT GNU Tools Installation Double click on downloaded executable file to launch installer Default installation options are appropriate 13

14 e 2 Studio Download Download e2studio from the Renesas web site Select Development Tools tab Select IDEs and Project Managers category Select e2studio 14

15 e 2 Studio Installation Double click on downloaded executable file to launch installer Default installation options are appropriate 15

16 e 2 Studio Project Creation and Build 16

17 e 2 Studio Workspaces e 2 Studio 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 e 2 Studio preferences Avoid workspace paths containing spaces Project A Project Folder Project B Project Folder Workspace Preferences 17

18 e 2 Studio 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) Build Output (config B) Project Settings 18

19 e 2 Studio 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 Library Generator Default Debug Settings Finish 19

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

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

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

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

24 e 2 Studio 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 24

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

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

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

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

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

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

31 E 2 STUDIO BASIC DEBUGGING 31

32 e 2 Studio 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 32

33 e 2 Studio 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 e 2 Studio Customization possible but seldom necessary Run >> Debug Configurations... 33

34 Launching e 2 Studio 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 34

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

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

37 Summary 37

38 Questions? 38

39 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

40 Renesas Electronics America Inc.