Renesas Electronics America Inc. © 2012 Renesas Electronics America Inc. All rights reserved. Migration from HEW to e 2 studio

© 2012 Renesas Electronics America Inc. All rights reserved.2 Renesas Technology & Solution Portfolio

© 2012 Renesas Electronics America Inc. All rights reserved.3 Challenge: In the smart society, engineers require access to an increasingly diverse range of development tools to support the complexity of new embedded system designs. Solution: This class will show you how to migrate existing development projects to take advantage of the class-leading tooling integration offered by the Eclipse-based e2studio IDE. ‘Enabling The Smart Society’

© 2012 Renesas Electronics America Inc. All rights reserved.4 Introduction to e 2 studio Key usage differences between HEW (High-performance Embedded Workshop) and e 2 studio Project metadata HEW to e 2 studio migration procedure Debugger setup Team working with e 2 studio Hands-on lab Agenda

© 2012 Renesas Electronics America Inc. All rights reserved.5 Introduction to e 2 studio

© 2012 Renesas Electronics America Inc. All rights reserved.6 About e 2 studio Modern development environment for Renesas MCUs built on Eclipse open-source platform and C/C++ Development Tooling (CDT) Workbench already familiar to many developers Opportunity for diverse workflows by combining Eclipse features from multiple sources

© 2012 Renesas Electronics America Inc. All rights reserved.7 Project import capability allows rapid migration from HEW to e 2 studio Broadly equivalent build and debug capabilities Key differences in the areas of: project source file presentation and manipulation debugger setup Migrating from HEW

© 2012 Renesas Electronics America Inc. All rights reserved.8 Project Presentation

© 2012 Renesas Electronics America Inc. All rights reserved.9 Fundamental difference between HEW and e2studio Project Presentation

© 2012 Renesas Electronics America Inc. All rights reserved.10 Workspace root node Multiple projects in workspace One active project Source files grouped by category Source files explicitly added to project are built Source files may be grouped in virtual folders Source files may reside anywhere on file system No representation of physical directory structure HEW Project and Source File Presentation

© 2012 Renesas Electronics America Inc. All rights reserved.11 No workspace node Multiple projects in workspace All projects active but may be explicitly closed Source file presentation reflects physical directory structure – similar to a standard File Explorer All source files under nominated source folders are built but may be explicitly excluded Nominated source folders presented with decorated icon e 2 studio Project and Source File Presentation

© 2012 Renesas Electronics America Inc. All rights reserved.12 Working Sets allow grouping of projects within a single workspace One or more working sets may be selected for viewing via Project Explorer view menu A project may belong to multiple working sets Useful mechanism for managing large workspaces e 2 studio Working Sets

© 2012 Renesas Electronics America Inc. All rights reserved.13 Critical difference between HEW and e 2 studio Deleting a file within the Project Explorer will delete the file within the physical file system Use Resource Configurations > Exclude from Build to mirror HEW Remove Files behavior e 2 studio File Deletion

© 2012 Renesas Electronics America Inc. All rights reserved.14 Source files existing outside project folder may be included as linked resources Linked resources presented with arrow decoration on icon Links may be absolute or relative to project location Source files within the nominated source folders may be excluded from one or more build configurations Excluded resources presented with grayed text and strikethrough decoration on icon e 2 studio Excluded and Linked Resources

© 2012 Renesas Electronics America Inc. All rights reserved.15 e 2 studio Executable projects built using an managed makefile and *.mk fragment files generated just-in-time Build output folder adopts build configuration name: Debug HardwareDebug Release Object code folder hierarchy mirrors that of source folders ELF executable generated with.x file suffix Other output files mirror HEW output e 2 studio Generated Resources

© 2012 Renesas Electronics America Inc. All rights reserved.16 e 2 studio Debug-Only projects used to debug executable code generated elsewhere – no project build capability e2studio Makefile projects built using a static makefile containing all necessary build rules Other project types support third-party toolchains Projects folders created within the current workspace folder by default e 2 studio Alternative Project Types

© 2012 Renesas Electronics America Inc. All rights reserved.17 e 2 studio toolchain settings for the project or file currently selected in the Project Explorer are modified from the Renesas Tool Settings context menu item (Alt-T) Toolchain Settings

© 2012 Renesas Electronics America Inc. All rights reserved.18 Tool setting changes made at the project level or source folder level apply to all source files within that hierarchy Tool setting changes made at the source file level apply to the individual source files selected A source file with tool settings that differ from the project wide settings is presented with a wrench decoration on its icon in the Project Explorer Individual Source File Settings

© 2012 Renesas Electronics America Inc. All rights reserved.19 HEW workspaces and projects are selected by navigating to.hws and.hwp data files respectively Eclipse workspaces are selected by navigating to a workspace folder containing multiple workspace preference data files within a hidden.metadata sub-folder Eclipse projects are selected by navigating to a project folder containing an Eclipse project description held within a hidden.project data file Project settings specific to e 2 studio projects and to CDT are stored in additional hidden data files within the project folder Use Eclipse Navigator view to inspect hidden files (optional) Metadata folders and files fully visible outside Eclipse – not hidden at operating system level Workspace and Project Metadata

© 2012 Renesas Electronics America Inc. All rights reserved.20 HEW Project Import

© 2012 Renesas Electronics America Inc. All rights reserved.21 HEW Project import wizard selected from the File > Import dialog Browse to HEW project file (*.hwp) within the wizard Wizard confirms validity of HEW project and availability of appropriate toolchain within e 2 studio Imported project appears in current e 2 studio workspace HEW Project Import Procedure

© 2012 Renesas Electronics America Inc. All rights reserved.22 HEW project content not copied e 2 studio project metadata generated within existing HEW project folder HEW project settings faithfully migrated absolute/relative file paths observed toolchain settings preserved (including per-file settings) per-configuration file exclusions observed variables (PROJDIR, CONFIGDIR, …) replaced with equivalent Eclipse variables where appropriate HEW and e 2 studio projects share source files HEW project source files located outside the project folder imported as linked resources Source files located within the project folder but not referenced by the HEW project marked as excluded HEW Project Import Implementation

© 2012 Renesas Electronics America Inc. All rights reserved.23 Import each project once only Subsequent changes to HEW project or e 2 studio project not mirrored in the other IDE HEW project cannot be re-imported (overwriting e 2 studio project description) following initial import Only RX and SH architectures supported at present HEW dependent project settings not imported – equivalent e 2 studio feature available HEW custom build steps not imported – equivalent e 2 studio feature available HEW debugger setup not imported – equivalent e 2 studio feature available HEW Project Import Limitations

© 2012 Renesas Electronics America Inc. All rights reserved.24 HEW allows a project to be dependent on a number of other projects - dependent projects will be re-built when necessary e 2 studio offers equivalent project references Dependent Projects

© 2012 Renesas Electronics America Inc. All rights reserved.25 HEW allows developer to add custom build phases for a project e 2 studio offers equivalent external builders Custom Build Steps

© 2012 Renesas Electronics America Inc. All rights reserved.26 e 2 studio projects typically transferred between users across organizational boundaries via project archive files (*.zip) manipulated using export and import wizards Sender exports currently selected project(s) in workspace using File > Export > General > Archive File Recipient imports project to their own workspace using File > Import > General > Existing Projects into Workspace e 2 studio Project Export

© 2012 Renesas Electronics America Inc. All rights reserved.27 Debugger Setup

© 2012 Renesas Electronics America Inc. All rights reserved.28 HEW debug communication and launch settings held in session data files (*.hsf) – session settings may be used with multiple build configurations HEW session settings may describe multiple images files for download to the target at launch HEW Debug Settings

© 2012 Renesas Electronics America Inc. All rights reserved.29 An e 2 studio debug configuration combines project name, executable file, communication and launch settings in a single entity e 2 studio Debug Configurations

© 2012 Renesas Electronics America Inc. All rights reserved.30 Separate debug configurations required for each build configuration and for each target (hardware, simulator, …) Initial debug configuration for each project generated automatically based on information provided within the New Project wizard Debug configurations for other targets generated on initial launch via Project Explorer context menu e 2 studio Debug Configuration Generation

© 2012 Renesas Electronics America Inc. All rights reserved.31 Debugger-specific settings acquire sensible default values Review and customization of settings via Debugger tab in Debug Configurations dialog Debug Hardware Settings

© 2012 Renesas Electronics America Inc. All rights reserved.32 Debug Configurations held in.launch files Initial debug configuration generated by project wizard and stored in project folder User-generated launch configurations saved as local files in workspace metadata by default Specify shared file folder to save within project Debug Configuration Persistence

© 2012 Renesas Electronics America Inc. All rights reserved.33 HEW allows customization of the debug session launching using HEW Debugger Command (*.hdc) files e 2 Studio allows customization by adding GDB commands to the initialization sequence Commands may include “source ” to execute multiple GDB commands from a file Use GDB “restore” command to download an image from file in various formats (ihex, srec, binary, …) Launch Scripting

© 2012 Renesas Electronics America Inc. All rights reserved.34 Debugging

© 2012 Renesas Electronics America Inc. All rights reserved.35 HEW and e 2 studio debugging capabilities broadly equivalent e 2 studio prompts user to open an alternative Eclipse perspective (combination and layout of views) when launching a debug session Return to C/C++ perspective via workbench toolbar icon or Window > Open Perspective menu item later HEW debugger remains connected to target over multiple application build cycles typically Eclipse debugging paradigm encourages new debug session for each application build but e 2 studio provides an optional reload capability e 2 studio advanced debugging views enabled via Window > Show View dialog Debugging Overview

© 2012 Renesas Electronics America Inc. All rights reserved.36 Toolbar in Renesas Debug view allows target state control and stack frame selection Eclipse Variables view presents local variables of the selected stack frame Toolbar commands for restart, reload, reset and loading of ancillary files Toggle between source-level and instruction-level stepping Keyboard shortcuts differ from those in HEW Debugging State Control

© 2012 Renesas Electronics America Inc. All rights reserved.37 Debug State Presentation HEWe 2 studio Symbol > LocalsVariables View Symbol > WatchExpressions View Symbol > LabelsInspect.map File Disassembly in EditorDisassembly View CPU > RegistersRegisters View CPU > IOIO Registers View CPU > MemoryMemory View Code > TraceTrace View Code > Stack TraceRenesas Debug View

© 2012 Renesas Electronics America Inc. All rights reserved.38 Local variables only Modified variables highlighted Basic Debug Views - Variables

© 2012 Renesas Electronics America Inc. All rights reserved.39 Any expression understood by underlying debugger (GDB) Modified expressions highlighted Basic Debug Views - Expressions

© 2012 Renesas Electronics America Inc. All rights reserved.40 Multiple memory monitors Multiple word lengths Multiple rendering formats Modified memory words presented in red Basic Debug Views - Memory

© 2012 Renesas Electronics America Inc. All rights reserved.41 All registers known to underlying debugger (GDB) Multiple numeric formats Modified registers highlighted Basic Debug Views - Registers

© 2012 Renesas Electronics America Inc. All rights reserved.42 Source code interleaving Presentation tracks program counter Basic Debug Views - Disassembly

© 2012 Renesas Electronics America Inc. All rights reserved.43 Advanced debug views opened via Show View dialog at Window > Show View > Other… Selection and layout of views in all perspectives persisted in workspace metadata Restore default layout via Window > Reset Perspective… Opening Debug Views

© 2012 Renesas Electronics America Inc. All rights reserved.44 Team Working

© 2012 Renesas Electronics America Inc. All rights reserved.45 Eclipse accommodates sharing and version control via Team Provider features CVS team provider accompanies e 2 studio Many third-party team providers available, including: EGit MercurialEclipse SourceAnywhere for VSS Subversive Many team-oriented capabilities supported by a common user interface including sharing, differencing and merge Team providers work at Eclipse project level Eclipse workspaces private by design and contain non- portable metadata Eclipse Team Working

© 2012 Renesas Electronics America Inc. All rights reserved.46 Mark debug configurations as shared files providing associated project folders Initiate project sharing via Team > Share Project… context menu item Add all e 2 studio project files (including hidden files) to shared repository except the generated build folders Define sets of projects using Working Sets where appropriate Save list of projects and/or working sets to file using Team Project Sets export wizard Resulting.psf file contains all information necessary to check out project set (including shared repository information) for distribution to team members Import of.psf file by team members will initiate check out from shared repository Sharing e 2 studio Projects

© 2012 Renesas Electronics America Inc. All rights reserved.47 e 2 studio provides modern extensible environment for development with Renesas MCUs Capabilities broadly equivalent to HEW but adopting a different approach for project presentation and debugger setup HEW project import wizard allows rapid migration HEW debugging views mirrored in e 2 studio debug perspective Collaboration achieved using third-party team provider features Summary

© 2012 Renesas Electronics America Inc. All rights reserved.48 Questions? Questions?

© 2012 Renesas Electronics America Inc. All rights reserved.49 Challenge: In the smart society, engineers require access to an increasingly diverse range of development tools to support the complexity of new embedded system designs. Solution: This class will show you how to migrate existing development projects to take advantage of the class-leading tooling integration offered by the Eclipse-based e2studio IDE. Do you agree that we accomplished the above statement? ‘Enabling The Smart Society’

Renesas Electronics America Inc. © 2012 Renesas Electronics America Inc. All rights reserved.