User's Manual

e² studio
Integrated Development Environment
User’s Manual: Quick Start Guide
RENESAS MCU
RX, RL78, RH850, RISC-V MCU Family

All information contained in these materials, including products and product specifications,represents information on the product at the time of publication and is subject to change byRenesas Electronics Corp. without notice. Please review the latest information published byRenesas Electronics Corp. through various means, including the Renesas Electronics Corp.
website (http://www.renesas.com).

www.renesas.com

Rev.1.10 March 2024

Notice1.

Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products
and application examples. You are fully responsible for the incorporation or any other use of the circuits, software, and information in the design of yourproduct or system. Renesas Electronics disclaims any and all liability for any losses and damages incurred by you or third parties arising from the use of
these circuits, software, or information.
2. Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other claims involving patents, copyrights, orother intellectual property rights of third parties, by or arising from the use of Renesas Electronics products or technical information described in thisdocument, including but not limited to, the product data, drawings, charts, programs, algorithms, and application examples.
3. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics orothers.
4. You shall be responsible for determining what licenses are required from any third parties, and obtaining such licenses for the lawful import, export,
manufacture, sales, utilization, distribution or other disposal of any products incorporating Renesas Electronics products, if required.
5. You shall not alter, modify, copy, or reverse engineer any Renesas Electronics product, whether in whole or in part. Renesas Electronics disclaims any
and all liability for any losses or damages incurred by you or third parties arising from such alteration, modification, copying or reverse engineering.
6. Renesas Electronics products are classified according to the following two quality grades: “Standard” and “High Quality”. The intended applications foreach Renesas Electronics product depends on the product’s quality grade, as indicated below.
"Standard": Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment; homeelectronic appliances; machine tools; personal electronic equipment; industrial robots; etc.
"High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control (traffic lights); large-scale communication equipment; key
financial terminal systems; safety control equipment; etc.
Unless expressly designated as a high reliability product or a product for harsh environments in a Renesas Electronics data sheet or other Renesas
Electronics document, Renesas Electronics products are not intended or authorized for use in products or systems that may pose a direct threat tohuman life or bodily injury (artificial life support devices or systems; surgical implantations; etc.), or may cause serious property damage (space system;
undersea repeaters; nuclear power control systems; aircraft control systems; key plant systems; military equipment; etc.). Renesas Electronics disclaims
any and all liability for any damages or losses incurred by you or any third parties arising from the use of any Renesas Electronics product that isinconsistent with any Renesas Electronics data sheet, user’s manual or other Renesas Electronics document.
7. No semiconductor product is absolutely secure. Notwithstanding any security measures or features that may be implemented in Renesas Electronics
hardware or software products, Renesas Electronics shall have absolutely no liability arising out of any vulnerability or security breach, including but notlimited to any unauthorized access to or use of a Renesas Electronics product or a system that uses a Renesas Electronics product. RENESASELECTRONICS DOES NOT WARRANT OR GUARANTEE THAT RENESAS ELECTRONICS PRODUCTS, OR ANY SYSTEMS CREATED USINGRENESAS ELECTRONICS PRODUCTS WILL BE INVULNERABLE OR FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE,
HACKING, DATA LOSS OR THEFT, OR OTHER SECURITY INTRUSION (“Vulnerability Issues”). RENESAS ELECTRONICS DISCLAIMS ANY AND
ALL RESPONSIBILITY OR LIABILITY ARISING FROM OR RELATED TO ANY VULNERABILITY ISSUES. FURTHERMORE, TO THE EXTENTPERMITTED BY APPLICABLE LAW, RENESAS ELECTRONICS DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, WITHRESPECT TO THIS DOCUMENT AND ANY RELATED OR ACCOMPANYING SOFTWARE OR HARDWARE, INCLUDING BUT NOT LIMITED TO THE
IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
8. When using Renesas Electronics products, refer to the latest product information (data sheets, user’s manuals, application notes, “General Notes for
Handling and Using Semiconductor Devices” in the reliability handbook, etc.), and ensure that usage conditions are within the ranges specified byRenesas Electronics with respect to maximum ratings, operating power supply voltage range, heat dissipation characteristics, installation, etc. Renesas
Electronics disclaims any and all liability for any malfunctions, failure or accident arising out of the use of Renesas Electronics products outside of suchspecified ranges.
9. Although Renesas Electronics endeavors to improve the quality and reliability of Renesas Electronics products, semiconductor products have specificcharacteristics, such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Unless designated as a high reliability
product or a product for harsh environments in a Renesas Electronics data sheet or other Renesas Electronics document, Renesas Electronics products
are not subject to radiation resistance design. You are responsible for implementing safety measures to guard against the possibility of bodily injury,
injury or damage caused by fire, and/or danger to the public in the event of a failure or malfunction of Renesas Electronics products, such as safety
design for hardware and software, including but not limited to redundancy, fire control and malfunction prevention, appropriate treatment for aging
degradation or any other appropriate measures. Because the evaluation of microcomputer software alone is very difficult and impractical, you areresponsible for evaluating the safety of the final products or systems manufactured by you.
10. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas
Electronics product. You are responsible for carefully and sufficiently investigating applicable laws and regulations that regulate the inclusion or use ofcontrolled substances, including without limitation, the EU RoHS Directive, and using Renesas Electronics products in compliance with all theseapplicable laws and regulations. Renesas Electronics disclaims any and all liability for damages or losses occurring as a result of your noncompliancewith applicable laws and regulations.
11. Renesas Electronics products and technologies shall not be used for or incorporated into any products or systems whose manufacture, use, or sale isprohibited under any applicable domestic or foreign laws or regulations. You shall comply with any applicable export control laws and regulations
promulgated and administered by the governments of any countries asserting jurisdiction over the parties or transactions.
12. It is the responsibility of the buyer or distributor of Renesas Electronics products, or any other party who distributes, disposes of, or otherwise sells ortransfers the product to a third party, to notify such third party in advance of the contents and conditions set forth in this document.
13. This document shall not be reprinted, reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas Electronics.
14. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas
Electronics products.
(Note1)(Note2)“Renesas Electronics” as used in this document means Renesas Electronics Corporation and also includes its directly or indirectly controlledsubsidiaries.
“Renesas Electronics product(s)” means any product developed or manufactured by or for Renesas Electronics.
(Rev.5.0-1 October 2020)

Corporate Headquarters

Contact information

TOYOSU FORESIA, 3-2-24 Toyosu,
Koto-ku, Tokyo 135-0061, JapanFor further information on a product, technology, the most up-to-dateversion of a document, or your nearest sales office, please visit:www.renesas.com/contact/.

www.renesas.com

Trademarks
Renesas and the Renesas logo are trademarks of Renesas
Electronics Corporation. All trademarks and registered trademarks
are the property of their respective owners.

© 2024 Renesas Electronics Corporation. All rights reserved.

General Precautions in the Handling of Microprocessing Unit and Microcontroller Unit
Products
The following usage notes are applicable to all Microprocessing unit and Microcontroller unit products from Renesas. For detailed usage notes on the products
covered by this document, refer to the relevant sections of the document as well as any technical updates that have been issued for the products.
1.

Precaution against Electrostatic Discharge (ESD)
A strong electrical field, when exposed to a CMOS device, can cause destruction of the gate oxide and ultimately degrade the device operation. Steps must
be taken to stop the generation of static electricity as much as possible, and quickly dissipate it when it occurs. Environmental control must be adequate.
When it is dry, a humidifier should be used. This is recommended to avoid using insulators that can easily build up static electricity. Semiconductor devices
must be stored and transported in an anti-static container, static shielding bag or conductive material. All test and measurement tools including work
benches and floors must be grounded. The operator must also be grounded using a wrist strap. Semiconductor devices must not be touched with barehands. Similar precautions must be taken for printed circuit boards with mounted semiconductor devices.

2.

Processing at power-on
The state of the product is undefined at the time when power is supplied. The states of internal circuits in the LSI are indeterminate and the states of registersettings and pins are undefined at the time when power is supplied. In a finished product where the reset signal is applied to the external reset pin, the statesof pins are not guaranteed from the time when power is supplied until the reset process is completed. In a similar way, the states of pins in a product that isreset by an on-chip power-on reset function are not guaranteed from the time when power is supplied until the power reaches the level at which resetting is
specified.

3.

Input of signal during power-off state
Do not input signals or an I/O pull-up power supply while the device is powered off. The current injection that results from input of such a signal or I/O pull-up
power supply may cause malfunction and the abnormal current that passes in the device at this time may cause degradation of internal elements. Follow theguideline for input signal during power-off state as described in your product documentation.

4.

Handling of unused pins
Handle unused pins in accordance with the directions given under handling of unused pins in the manual. The input pins of CMOS products are generally inthe high-impedance state. In operation with an unused pin in the open-circuit state, extra electromagnetic noise is induced in the vicinity of the LSI, anassociated shoot-through current flows internally, and malfunctions occur due to the false recognition of the pin state as an input signal become possible.

5.

Clock signals
After applying a reset, only release the reset line after the operating clock signal becomes stable. When switching the clock signal during program execution,
wait until the target clock signal is stabilized. When the clock signal is generated with an external resonator or from an external oscillator during a reset,
ensure that the reset line is only released after full stabilization of the clock signal. Additionally, when switching to a clock signal produced with an external
resonator or by an external oscillator while program execution is in progress, wait until the target clock signal is stable.

6.

Voltage application waveform at input pin
Waveform distortion due to input noise or a reflected wave may cause malfunction. If the input of the CMOS device stays in the area between VIL (Max.) andVIH (Min.) due to noise, for example, the device may malfunction. Take care to prevent chattering noise from entering the device when the input level is fixed,
and also in the transition period when the input level passes through the area between VIL (Max.) and VIH (Min.).

7.

Prohibition of access to reserved addresses
Access to reserved addresses is prohibited. The reserved addresses are provided for possible future expansion of functions. Do not access these addresses
as the correct operation of the LSI is not guaranteed.

8.

Differences between products
Before changing from one product to another, for example to a product with a different part number, confirm that the change will not lead to problems. The
characteristics of a microprocessing unit or microcontroller unit products in the same group but having a different part number might differ in terms of internal
memory capacity, layout pattern, and other factors, which can affect the ranges of electrical characteristics, such as characteristic values, operating margins,
immunity to noise, and amount of radiated noise. When changing to a product with a different part number, implement a system-evaluation test for the given
product.

Table of Contents
Corporate Headquarters ........................................................................................................ 1
Contact information................................................................................................................ 1
Trademarks ........................................................................................................................... 1
1.

General ......................................................................................................................... 1

2.

Installation..................................................................................................................... 3

3.

Project generation ....................................................................................................... 17

1.1
1.2
1.3
1.4
1.5

2.1
2.2
2.3
2.4
2.5

System Configuration................................................................................................................................. 1
System Requirements................................................................................................................................ 1
Supported Toolchains ................................................................................................................................ 2
Supported Emulator Device ....................................................................................................................... 2
Supported Simulator .................................................................................................................................. 2

Installation of e² studio IDE (64-bit version) ............................................................................................... 3
About 32-bit version of e² studio .............................................................................................................. 13
Uninstallation of e² studio IDE ................................................................................................................. 14
Installation of Compiler Package ............................................................................................................. 14
Tutorial ..................................................................................................................................................... 16

3.1
3.2
3.3
3.4

New Project Generation ........................................................................................................................... 17
New Debug Only Project Generation....................................................................................................... 21
Importing a sample project....................................................................................................................... 24
Importing Projects into Workspace .......................................................................................................... 25
3.4.1
Import Existing Projects ................................................................................................................. 25
3.4.2
Download and import sample projects in Smart Browser view ...................................................... 30

4.

Build ............................................................................................................................ 31

5.

Debug ......................................................................................................................... 36

4.1
4.2
4.3

Build Option Settings ............................................................................................................................... 31
Build A Sample Project ............................................................................................................................ 34
Export Build Configuration Settings ......................................................................................................... 35

5.1
5.2
5.3
5.4

Change Existing Debug Configurations ................................................................................................... 36
Create New Debug Configurations .......................................................................................................... 40
Launch Bar ............................................................................................................................................... 41
Basic Debugging Features....................................................................................................................... 42
5.4.1
Breakpoints View ........................................................................................................................... 43
5.4.2
Expressions View ........................................................................................................................... 44
5.4.3
Registers View ............................................................................................................................... 46
5.4.4
Memory View.................................................................................................................................. 47
5.4.5
Disassembly View .......................................................................................................................... 49
5.4.6
Variables View ............................................................................................................................... 51
5.4.7
Eventpoints View ............................................................................................................................ 52
5.4.8
IO Registers View .......................................................................................................................... 55
5.4.9
Trace View ..................................................................................................................................... 56
5.4.10 Memory Usage View ...................................................................................................................... 59

6.

Help ............................................................................................................................ 63

Renesas e² studio1.

Quick Start Guide

GeneralRenesas e² studio is the Integrated Development Environment for Renesas embedded microcontrollers. e²
studio is based on the industry-standard open-source Eclipse IDE framework and the C/C++ Development
Tooling (CDT) project, covering build (editor, compiler, and linker control) and debug phases with an extended
GNU Debug (GDB) interface support.
This document describes the usage of e² studio IDE to develop applications for the RX family series
microcontrollers as an example.

1.1

System Configuration

Below is an example of a typical system configuration.

Figure 1-1 System Configuration

1.2

System Requirements

Hardware Environment:
Processor:
x64-based processor, at least 2GHz (support hyper-threading/multi-core CPU)
Main Memory:
At least 4GB, recommended 8GB of free memory space.
Hard disk Capacity:
At least 2GB of free space
Display:
Resolution at least 1,024 x 768; at least 65,536 colors
Interface:USB 2.0 (High-speed/Full-speed). High-speed is recommended.
[Windows PC]
Supported OS:[Linux PC]
Supported OS:

Windows 10 and Windows 11 (64-bit edition).
(32-bit Windows is supported with e² studio V7.8.0)
Ubuntu 20.04 LTS Desktop (64-bit version)
Ubuntu 22.04 LTS Desktop (64-bit version)

Note: Supported features of Linux versions are different from Windows versions. Please refer to the Release
Note for details. Project build features are not supported for the compiler products which do not have Linuxsupport versions (such as CC-RX, CC-RL and CC-RH). Please use Windows for those compiler projects.
This document is described based on Windows version. Please refer to e² studio Release Note or FAQ page
(mentioned in the Release Note) for installation in Linux PC. Operations after installation are very similar toWindows version.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 1 of 63

Renesas e² studio

1.3

Quick Start Guide

Supported Toolchains

Renesas C/C++ compiler package for RX family (CC-RX)
Renesas C compiler package for RL78 family (CC-RL)
Renesas C compiler package for RH850 family (CC-RH)
GCC for Renesas RX Toolchain
LLVM and GCC for Renesas RL78 Toolchain
LLVM for Renesas RISC-V MCU Toolchain
Note 1: Two types of packages (with CS+ and without IDE) for each CC-RX, CC-RL and CC-RH are available.
Any of those can be applied to e² studio.
Note 2: For RH850, the e² studio can be used to debug load modules in the ELF/DWARF format which werebuilt with the IAR Embedded Workbench from IAR Systems or the MULTI IDE from Green Hills Software.

1.4

Supported Emulator Device

E2 emulator Lite (RX, RL78, RISC-V MCU)
E1 (RX, RL78, RH850) (Note 1)
E2 (RX, RL78, RH850, RISC-V MCU)
E20 (RX) (Note 2)
Segger J-Link (RX)Note 1: E1 emulator is EOL (end-of-life) product.
Note 2: The E20 does not support RH850-family MCUs with the next-generation G4MH core, such as those of
the RH850/E2x series. The E2 emulator is available for use with them.

1.5

Supported Simulator

Renesas Simulator (RX, RL78)
GDB Simulator (RH850)

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 2 of 63

Renesas e² studio

2.

Quick Start Guide

Installation

The latest e² studio IDE installer package can be downloaded from Renesas website for free. It is recommended
to install the 64-bit version on 64-bit PC. The e² studio installers and related documentation are available on thee² studio product page https://www.renesas.com/e2studio, on the device-family information page. Note thatusers must log in to the Renesas account (on MyRenesas page) for the software download.
e² studio is available in 32-bit (V7.8.0 or earlier) and 64-bit (2020-04 or later). Use the 64-bit e² studio versions
unless in the 32-bit OS environment.
This chapter describes the installation and uninstallation for the e² studio IDE.
Please uninstall the earlier versions before installation. Alternatively, install new e² studio into a new folder if you
would like to keep earlier versions. Although upgrade installation is available, upgrading between incompatible
versions is not allowed such as from V7.8.0 to 2020-04, 2022-10 to 2023-01. Please install it into a new folder if
fails.
The detailed information is described below.

2.1

Installation of e² studio IDE (64-bit version)

1. Launch the e² studio installer. For e² studio 2023-07 and later, there are three (Lite/Standard/Custom) typesof new installations. Select any of the items and click [Install].

Figure 2-1 e² studio installation – Start page
Lite installs the minimum functionality required to build and debug your project. In addition, Standard can install
extended functionality. Any function can be installed in Custom. Clicking on the "Click here" link displayed on thefirst page of the installer will show a list of the functions that will be installed by Lite and Standard, so pleaseconfirm it before proceeding.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 3 of 63

Renesas e² studio

Quick Start Guide

Note: If the e² studio is already installed, the [Modify] (modifying installed e² studio) and [Uninstall] options are
displayed in addition to [Install].

Figure 2-2 e² studio installation – Detected installation of e² studio

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 4 of 63

Renesas e² studio

Quick Start Guide

2. Welcome pageThe install folder can be changed by clicking [Change…]. Click [Next] to continue.
Note1: If you would like to have multiple versions of e² studio, please specify new folder here.
Note2: Multi-byte characters cannot be used for e² studio installation folder name.

Figure 2-3 e² studio installation – Welcome page
If the installer cannot access Renesas web, a warning message will appear as follows:

Figure 2-4 e² studio installation – Website access warning message
As stated in the message, the installation can continue. Although the software listed under "Additional Software"(such as compiler products mentioned later) are not installed, they can be installed separately after e² studioinstallation.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 5 of 63

Renesas e² studio

Quick Start Guide

3. Device Families
Select all Devices Families you will use. Click [Next] to continue.

Figure 2-5 e² studio installation – Device Families
Note: Unchecked device families will not support any build features (project creation, import and build), or
debug features. Please ensure that you select the device family that you may possibly use. If you want to
add device family later, rerun the installer and choose the Modify option.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 6 of 63

Renesas e² studio

Quick Start Guide

4. Extra Features
This dialog is skipped in Lite/Standard installation type. Select Extra Features (i.e. Language packs, Git
support, RTOS support…) to install.
For non-English language menu, please select Language packs at this step.
Click [Next] to continue.

Figure 2-6 e² studio installation – Extra Features
5. Customise Features
This dialog is also skipped in Lite/Standard installation type. Select the components to install and click the[Next] button to continue.

Figure 2-7 e² studio installation – Customise Features
R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 7 of 63

Renesas e² studio

Quick Start Guide

6. Additional Software
Select additional software (i.e. compilers, utilities, QE…) and click [Next] to continue.
Note: If no Internet access is available, additional software installation can be skipped because software
catalog cannot be downloaded. The additional software can be installed later.

Figure 2-8 e² studio installation – Additional Software

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 8 of 63

Renesas e² studio

Quick Start Guide

7. License Agreement
Read and accept the software license agreement. Click the [Next] button.
Please note that user must accept the license agreement, otherwise installation cannot be continued.

Figure 2-9 e² studio installation – Licenses
You can also check the contents displayed here after installation. You can read them by clicking the icon in"About e² studio" under the e² studio "Help" menu and select the License button, or by opening "Features" tab in"Installation Details".

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 9 of 63

Renesas e² studio

Quick Start Guide

8. Shortcuts
Select shortcut name (not mandatory) for start menu and click [Next] button to continue.
Note: If e² studio was installed in another location, it is recommended to rename to distinguish from the othere² studio(s).

Figure 2-10 e² studio installation – Shortcuts

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 10 of 63

Renesas e² studio

Quick Start Guide

9. Drivers
This dialog asks whether to install the debugger driver. Do not install drivers if you have previously installed
the same version of the e² studio.

Figure 2-11 e² studio installation – Drivers

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 11 of 63

Renesas e² studio

Quick Start Guide

10. Summary
Components list to be installed is shown. Please confirm the contents and click the [Install] button to install
the Renesas e² studio IDE.

Figure 2-12 e² studio installation – Summary
11. Installing…
The installation is in progress. Based on selected items of Additional Software, new dialogs are opened toproceed with the software installation.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 12 of 63

Renesas e² studio

Quick Start Guide

12. Results
Installation results are listed here. Please note if any errors are shown.
Click [OK] button to complete the installation.

Figure 2-13 e² studio installation – Results
Note: If you have installed as a different account than the one you normally use such as for administrator
privileges, do not start the e² studio by checking "Launch e2 studio?" in this dialog. If you do so, discard theworkspace that was used at that time.

2.2

About 32-bit version of e² studio
There is no Lite/Standard selection for e² studio V7.8.0 or earlier installers.
The installer’s interface follows a similar flow to that of the 64-bit version, although the displayed content mayvary slightly. Therefore, refer to the above explanation when using it.
For users of 32-bit OS environment in which 64-bit versions of e² studio do not work, the e² studio V7.8.0 isavailable on the e² studio product page. Unless there is a specific requirement for this version, it isrecommended to use the 64-bit versions (202x-xx).

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 13 of 63

Renesas e² studio

2.3

Quick Start Guide

Uninstallation of e² studio IDE

By Windows OS, you can uninstall programs by selecting "e² studio" from the list of installed programs in [Start]→ [Control Panel] → [Apps & features]. However, if uninstallation is not possible, run the uninstaller directly fromthe following folder:{e² studio installed folder}/uninstall/uninstall.exe.
If this still doesn't work, remove it using the same version of the e² studio installer, or just delete the destination
folder.

2.4

Installation of Compiler Package

As mentioned above in installation procedure, compiler packages can be installed with e² studio when you haveaccess to the Internet. Please install compiler packages separately from e² studio installation when Internet
access is not available.
Compiler packages are found in the following websites. Please read descriptions on the websites for installation
procedures.
Renesas Compiler for RX : http://www.renesas.com/rx_c
Renesas Compiler for RL78 : http://www.renesas.com/rl78_c
Renesas Compiler for RH850 : http://www.renesas.com/rh850_c
LLVM and GNU toolchain for RL78 : https://llvm-gcc-renesas.com/rl78-download-toolchains/
GCC for Renesas RX toolchain: https://llvm-gcc-renesas.com/rx-download-toolchains/
LLVM for Renesas RISC-V MCU toolchain : https://llvm-gcc-renesas.com/riscv-download-toolchains/

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 14 of 63

Renesas e² studio

Quick Start Guide

Open “Renesas Toolchain Management” dialog ([Help] menu -> [Add Renesas Toolchains]) to confirm which
toolchains are installed and integrated. The checked toolchains are integrated into e² studio. Click [Add] button to
add new toolchain installed path if it is not found in this list.

Figure 2-14 Renesas Toolchain management
You can also click [Download] button to install new toolchain when you have Internet connection.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 15 of 63

Renesas e² studio

2.5

Quick Start Guide

Tutorial

The following chapters will explain the process of creating a project to starting the debugger. Additionally, youwill also find a tutorial for each type of Device Family and toolchain (compilers) in the e² studio Help.
Note: Tutorials are available for the supported Device Families that you selected during installation.

Figure 2-15 Tutorial

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 16 of 63

Renesas e² studio

3.

Quick Start Guide

Project generation

In e² studio, "Project" is a basic unit to perform build and debug operations.
This chapter describes the creation of new project and import of existing e² studio project, High-performance
Embedded Workshop IDE (described as “HEW” below) project and CS+ project to e² studio IDE.
Note:

1. To install and use the e² studio on your PC, you must install the compiler package provided separately.
2. Multi-byte characters cannot be used for e² studio installation folder name, project name and its folder,and source file name.

3.1

New Project Generation

To create a new project, invoke e² studio IDE from the Windows ([Start] menu) and specify a workspace
directory. To create a new project, proceed as follows:
1. Click [File] → [New] → [C/C++ Project] to open new project creation wizard.

Figure 3-1 Open New Project Creation Wizard
2. Select template for the new project (For e.g., Renesas RX: “Renesas CC-RX C/C++ Executable Project”). If
the target device family or the toolchain were not listed, you may need to run e² studio installer to add"Build/Debug support plugins" for the target device family. Click [Next] to proceed.

Figure 3-2 New Project Creation Wizard (1/6)
R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 17 of 63

Renesas e² studio

Quick Start Guide

3. Enter the project name. Click [Next] to proceed.

Figure 3-3 New Project Creation Wizard (2/6)
4. Select Language, Toolchain, Toolchain Version, RTOS, RTOS Version, Target Board, Target Device andConfigurations.
Click [Next] to proceed.
Note:•"E1" or “E2” can be selected in the same way as E2 Lite in the Hardware Debug Configuration pull
down menu.

•

Please select “C++” as Language when you use C++ source files in the project.

Figure 3-4 New Project Creation Wizard (3/6)

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 18 of 63

Renesas e² studio

Quick Start Guide

5. Coding Assistant feature can be applied if necessary. Click [Next] to proceed.
•

Peripheral Code Generator (CG) supports the generation of driver and peripheral function code basedon GUI settings. Functions are provided as APIs and are not limited to initialization of peripheral function.

•

FIT provides drivers and codes higher layer than CG, such as communication protocol stack and sample
application programs using peripheral functions. All FIT modules are interchangeable because they are
implemented with common interfaces.

•

Smart Configurator supports a single user interface that combines the functionalities of Code Generator
and FIT Configurator. Smart Configurator encompasses unified clock configuration view, interrupt
configuration view and pin configuration view.

Note: Peripheral Code Generator and Smart Configurator may not be available for some devices.

Figure 3-5 New Project Creation Wizard (4/6)
6. Keep the “Use Renesas Debug Virtual Console” unchecked and click [Next] to proceed.

Figure 3-6 New Project Creation Wizard (5/6)

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 19 of 63

Renesas e² studio

Quick Start Guide

7. A project summary is displayed. Click [Finish] to generate the project.

Figure 3-7 New Project Creation Wizard (6/6)
8. A new C project named “Tutorial” is created.

Figure 3-8 New C Project CreatedThis project consists of an application file “Tutorial.c” and standard start-up files (e.g. “dbsct.c”, “intprg.c”, “sbrk.c”
etc). All these project and source files listed in the [Project Explorer] panel reflect the folder structure of the
project, just as seen on the standard file explorer.
Notes for backing up projects:•

Project properties are stored in files or folders which filenames or folder names are prefixed with a '.'(dot), for example ".project" and ".cproject". It is necessary to include these files or folders whenarchiving the project for back-up purposes.

•

In order to restore properties shared among projects, for instance when one project makes reference toanother project's files, please backup the whole workspace folder.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 20 of 63

Renesas e² studio

3.2

Quick Start Guide

New Debug Only Project Generation

Creating a debug only project allows user to debug an existing executable which user has already built. Thisfeature will automatically create a project and debug configuration for user.
Note: The e² studio can be used to debug load modules in the ELF/DWARF format which were built with the IAR
Embedded Workbench from IAR Systems or the MULTI IDE from Green Hills Software.
To create a debug only project,
1. Click [File] → [New] → [C/C++ Project] to open new project creation wizard.

Figure 3-9 Open New Project Creation Wizard
2. Select template for the new project: [Renesas Debug] → [Renesas Debug Only Project]. Click [Next] toproceed.

Figure 3-10 Specify The Project Template

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 21 of 63

Renesas e² studio

Quick Start Guide

3. Enter the project name. Click [Next] to proceed.

Figure 3-11 Specify Project Name
4. Select debug hardware (e.g. “E2 (RH850)”), target device (e.g. R7F701007xAFP). Note that these settings
should be consistent with the settings to build the executable file. Then specify the location of prebuilt
executable file (i.e. executable file built in other IDEs) which should be built as ELF/DWARF format to berecognized by debugger. Click [Finish] to create the project.

Figure 3-12 Specify Project Settings

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 22 of 63

Renesas e² studio

Quick Start Guide

5. The project named “DebugOnly_Tutorial” is created. User can only modify the debug configuration of thisproject and start the debugging.

Figure 3-13 Debug Only Project Is Created

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 23 of 63

Renesas e² studio

3.3

Quick Start Guide

Importing a sample projecte² studio can search and import sample projects on Renesas website.
Open “File” menu and select “Import...” to launch Import Wizard. Then select “Sample Project on Renesas
Website”.

Figure 3-14 Sample Project Import
Select target device family in Online or Local category, then select device. Sample projects will be listed for thedevice. Click [Finish] to import the selected project. If the project does not appear on this dialog due to PC or
networking limitations, refer to alternative method mentioned in the following chapter.

Figure 3-15 Sample Projects of Target Device

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 24 of 63

Renesas e² studio

3.4

Quick Start Guide

Importing Projects into Workspace

The migration guideline between integrated development environments (i.e. import CS+/HEW projects to e²
studio, or export to CS+) can be found at the following site.
https://www.renesas.com/us/en/software-tool/migration-tools-ide
3.4.1 Import Existing Projects
To import an existing e² studio project to current workspace, please follow below instructions. These steps importa sample project from Renesas website to use for demonstrating debugging features in section 5.
1. Download the sample code for RX64M by searching for “RX64M Renesas Starter Kit Sample Code for e²
studio” from Renesas website: https://www.renesas.com.

Figure 3-16 Download The Sample CodeR20UT5293EJ0110 Rev.1.10
March 26,2024

Page 25 of 63

Renesas e² studio

Quick Start Guide

2. “Tutorial” project is included in the download file.

Figure 3-17 Downloaded file contents
3. In e² studio, select [File] → [Import]

Figure 3-18 Import The Sample Project

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 26 of 63

Renesas e² studio

Quick Start Guide

4. In the [Import] dialog, select [General] → [Existing Projects into Workspace]. Click [Next].

Figure 3-19 Select Import Wizard
5. In the [Import Projects] dialog, select “Select archive file”. Click [Browse] then select the downloaded zip fileFigure 3-20 Select Project Location To Import

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 27 of 63

Renesas e² studio

Quick Start Guide

6. The project “Tutorial” will be listed in “Projects”. Check “Tutorial” then click [Finish]

Figure 3-21 Complete Project Import

7. Right click on the imported project and select “Upgrade Legacy e2 studio Projects…”

Figure 3-22 Upgrade The Imported Project

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 28 of 63

Renesas e² studio

Quick Start Guide

8. Select “Tutorial” project and click [Finish]

Figure 3-23 Finish The Upgrading
9. Open the project properties, select [C/C++ Build] → [Settings] in the left pane. Select tab [Toolchain] andselect the latest toolchain for the project. Click [Apply and Close].

Figure 3-24 Update Project Toolchain

10. Build the project and make sure that it is successful.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 29 of 63

Renesas e² studio
3.4.2

Quick Start Guide

Download and import sample projects in Smart Browser view

You can also download sample projects from Renesas website through Smart Browser view.
Open “Renesas Views” -> “Solution Toolkit” -> “Smart Browser” menu (or via “Window” -> “Show View”) to open
the view. Right-click on an item listed in [Application Notes] tab and select “Sample Code (import projects)” toimport a sample project into current workspace. The Application Notes marked as “available” in “Sample Code”
column are provided with sample projects.

Figure 3-25 Application Notes in Smart Browser view

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 30 of 63

Renesas e² studio

4.

Quick Start Guide

Build

This chapter describes the build configurations and key build features for e² studio IDE.

4.1

Build Option Settings

A new project built with default option can work properly. However, if user would like to change build options(e.g. toolchain version, optimization options, etc.), please follow the following steps before building the project.
1. Right click on project “Tutorial” and select [Properties] to open the Properties window.
Properties window is supported at workspace, project and source level. Properties window for project supports
more configurations which apply across all the files within the same project workspace.

Figure 4-1 Open The Properties Window

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 31 of 63

Renesas e² studio

Quick Start Guide

2. Click [C/C++ Build] → [Settings] → [Toolchain] to view or change toolchain version.
Click the “Versions” option to change toolchain version (if additional toolchain is installed).

Figure 4-2 Change Toolchain Version
3. Click [C/C++ Build] → [Environment] to set build option and add or edit the environment variables.

Figure 4-3 Build Environment Settings

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 32 of 63

Renesas e² studio

Quick Start Guide

4. Setting Build Options
Right click on a project in the Project Explorer and select [Properties] to open the Properties window.
Build options for compiler and linker, etc. can be set on "C/C ++ Build" → "Settings"→ “Tool Setting” tab.
User could set all build settings under ‘Tool Settings’ tab.
The “Build configuration” can be switched via “Configuration:” dropdown list at the top of the window. Eachbuild configuration manages a set of build options.
Click [Apply and Close] to save the build setting changes.
Build configuration name

Confirm settings in command format

List of settings

Linker option specifies the section alignment,

Figure 4-4 Build Option Settings
The detail of build option is described in compiler user manual which is stored at “{Compiler installation
directory}\doc”. For example, it can be found in “C:\Program Files (x86)\Renesas\RX\3_2_0\doc\ ".
Note: There is "Toolchain Editor" under "C/C++ Build", please do not change the configuration. The Toolchain
editor is used for toolchains which are NOT supported by Renesas build support plugins.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 33 of 63

Renesas e² studio

Quick Start Guide

4.2 Build A Sample ProjectA project can be built by the steps below:
1. Right click on the project and select [Build Project].

Figure 4-5 Build A Sample “Tutorial” Project
2. Check that the [Console] pane shows ‘Build complete.’ message to indicate a successful build.
At the end of this build, files output to the ${CONFIGDIR} directory consists of “makefile”, “Tutorial.abs”,“Tutorial.map”, “Tutorial.mot”, “Tutorial.x” etc.
“Tutorial.abs” is a Renesas standard load module in ELF/DWARF format (*.abs) used for the debugging.
Because GDB supports a load module format with different ELF/DWARF specification (*.x or *.elf), hence“Tutorial.abs” has to be converted to “Tutorial.x” for the debugging in e² studio IDE.

Figure 4-6 Project Is Built Successfully.
3. In some cases, the build can be unsuccessful. The console window will show error messages, please checkit and revise the source code or configuration and rebuild the project

Figure 4-7 Unsuccessful Build Shows Error Messages

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 34 of 63

Renesas e² studio

Quick Start Guide

4.3 Export Build Configuration Settings
The Project Reporter feature can export project and build configuration settings from e² studio IDE to a file foreasy checking and comparison of project/build environment settings.
1. Right-click at [Project Explorer] to pop up the context menu.
2. Select [Renesas C/C++ Project Settings] -> [Save build settings report] to save build settings report.

Figure 4-8 Project Reporter

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 35 of 63

Renesas e² studio

5.

Quick Start Guide

Debug

This chapter describes the usage of debug configuration and key debugging features for e² studio. The following
illustration refers to “Tutorial” project built (in Chapter 4.2) and based on hardware configuration E2 emulator Liteand RSK RX64M board.
Firstly, open “Tutorial” project workspace in e² studio IDE and click [Debug] perspective.

Figure 5-1 Switch To [Debug] Perspective
Perspective defines the layout views (related to development tools) in the Workbench window. Each perspective
consists of a combination of views, menus and toolbars that enable user to perform specific task.
For instance, [C/C++] perspective has views that help user to develop C/C++ programs and [Debug] perspective
has views that enable user to debug the program. If user attempts to connect the debugger in the [C/C++]
perspective, IDE will prompt users to switch to the [Debug] perspective.
One or more perspectives can exist in a single Workbench window. User can customize them or add new
perspective.
Note: For more information on debug, please refer to “e2 studio User Guide” as described in chapter 6.

5.1

Change Existing Debug Configurations

The debug configuration has to be configured when debugging for the first time and it just needs to be done
once. An existing debug configuration can be changed as follows.
1. Click “Tutorial” Project in [Project Explorer] pane to set focus.
Click [Run] → [Debug Configurations…] oropen the “Debug Configurations” window.

icon (downward arrow) → [Debug Configurations…] toFigure 5-2 Open Debug Configurations Window
R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 36 of 63

Renesas e² studio

Quick Start Guide

2. In “Debug Configurations” windows, go to [Renesas GDB Hardware Debugging]  [Tutorial
HardwareDebug]. Click on the [Main] tab to ensure the load module is “Tutorial.x”.

Figure 5-3 Select Load Module
3. Switch to the [Debugger] tab, set “E2 Lite (RX)” as the debug hardware and “R5F564ML” as the target
device.

Figure 5-4 Select Target Device
4. Under the [Debugger] tab, go to the [Connection Settings] sub tab which is related to emulator connection.
The following example is based on the environment with E1 emulator and RSK RX64M board:•

Clock- Main Clock Source = “EXTAL”- Extal Frequency(MHz) = “24.0000”
Note: Extal frequency is the value printed on the oscillator device on your board.

•

Connection with Target Board- Connection Type = “JTag”

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 37 of 63

Renesas e² studio

Quick Start Guide- JTag Clock Frequency [MHz] = “6.00”- Hot plug = “No”
Hot plugin feature is only available with the device which has the capability. Please refer to device
Hardware manual for "On chip debugger" specifications for the details.
•

Power- Power Target From The Emulator (MAX 200mA) = “No”
Choose "Yes" if you would like to supply power through an emulator, when external power is
unplugged. Choose "No" if external power is plugged.

•

Communication Mode
- Mode = “Debug Mode”
Another communication mode "Write On Chip Flash Memory" is used for flashing codes including ID
code area, however debugger will be disconnected after flash.

Note: This debug configuration in Figure 5-5 is shown as an example. The wrong settings may cause
malfunction or damage to the hardware. So, be cautious to verify the board and emulator settings before
connection.

Figure 5-5 Change Connection Setting

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 38 of 63

Renesas e² studio

Quick Start Guide

5. Switch to [Debug Tool Settings] sub tab which is related to debugger behavior, please refer to the e² studio
Help content at "e² studio User Guide" → "Debugging Projects" for the details.

Figure 5-6 Change Debug Tool Settings•

Memory- Endian = “Little Endian”
Endian setting of debugger memory reference. This configuration does not affect the target program
behavior.
- “Internal Flash Memory Overwrite”, "External Memory Areas"
These configuration control to allow/deny flashing blocks upon module downloads. Uncheck specificmemory blocks if you would like to reserve the contents.

6. Click [Apply] button to confirm the settings. Then click [Debug] to launch debugger.
7. For a successful connection, [Debug] view to show target debugging information in a tree hierarchy. The
program entry point is set at “PowerON_Reset() in “resetprg.c”.

Figure 5-7 User Target Connection In The [Debug] View

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 39 of 63

Renesas e² studio

5.2

Quick Start Guide

Create New Debug Configurations

The simplest way to create a new debug configuration is by duplicating an existing one. It can be done by thefollowing steps.
1. Repeat step 1 in section 5.1 to open “Debug Configurations” window.
2. Select a debug configuration (e.g. “Tutorial HardwareDebug”) and then click
icon (Duplicates thecurrently selected launch configuration). A new debug launch configuration (e.g. “Tutorial HardwareDebug(1)”) is created. User can rename it to identify the settings by typing in the “Name” textbox then click [Apply]
button.

Figure 5-8 Duplicate A Selected Debug Launch Configuration
Note: If no debug configurations have been created and duplication is not possible, then right-click the load
module (extension *.x or *. elf) in Project Explorer to start the debugger with "Debug As" → "Renesas GDB
Hardware Debugging" (or “Renesas Simulator Debugging” for the simulator), and then back to Debug
Configurations dialog to make the required settings.
3. The debug launch configuration can be configured as described in chapter 5.1. For example, change the
Debug Hardware to “E2 Lite (RX)”.
4. If the launch configuration was added with [local] and * (red star) marker, it is not yet attached to any project.
Then please specify the project name in the Common tab.

Figure 5-9 Attach Launch Configuration To Specific Project

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 40 of 63

Renesas e² studio

5.3

Quick Start Guide

Launch Bar

This section explains the usage of ‘Launch Bar’ in the toolbar area of e² studio main window. This interface ishidden by default in some of e² studio versions.
The interface shown below builds and debugs for the selected launch target. (May or may not be the same
project as active project in Project Explorer.)

Buttons to perform build/launch debug for selected target

Figure 5-10 Launch Bar Interface
Launch Bar buttons behave as follows:•

button builds the load module of the selected launch configuration.
Note: There is another build buttonin the "File toolbar" that builds active build configuration of Project

Explorer, while the launch bar does not reflect the active state in Project Explorer.
•

buttons are trigger of debugger launch and terminate the selected launch target.

Launch Bar and build button can be shown or hidden through the following dialog.
• Click [Window] menu → [Preferences], then click [Run/Debug] → [Launching] → [Launch Bar]

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 41 of 63

Renesas e² studio

5.4

Quick Start Guide

Basic Debugging Features

This section explains the typical Debug views supported in e² studio IDE.
•

Standard GDB Debug (supported by Eclipse IDE framework): Breakpoints, Expressions, Registers, Memory,
Disassembly and Variables•

Renesas Extension to Standard GDB Debug: Eventpoints, IO Registers and Trace.

The following are some useful buttons exist in the [Debug] view:

Step Into (F5)Resume (F8)Suspend

Step Over (F6)

Terminate(Cltrl+F2)

Step Return (F7)

Download
Disconnect

Reset

RestartFigure 5-11 Useful Toolbars In Debug Views
The program is run by clicking

button or pressing [F8].

The program can be paused by breakpoint or by clicking
the following operations:button. When program is paused, user can perform•button or [F5] can be used for stepping into the next method call at the currently executing line of code.

•

button or [F6] can be used for stepping over the next method call (executing but without entering it) at
the currently executing line of code.

•

button can be clicked again to resume running.

To stop the debugging process,button is clicked to end the selected debug session and/or process or
button is clicked to disconnect the debugger from the selected process.
The other operations are as following:•

button can be clicked to start new debug session.

•

button can be clicked to reset the program to entry point at the PowerOn Reset.

•

button is used for re-downloading the binary file to target system.

Note: To demonstate the features in the following section, please use the sample code for RX64M from
Renesas website as instructed in section 3.3.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 42 of 63

Renesas e² studio
5.4.1

Quick Start Guide

Breakpoints View

The Breakpoints view stores the breakpoints that were set on executable lines of a program. If a breakpoint isenabled during debugging, the execution suspends before that line of code executes. e² studio allows softwareand hardware breakpoints to be set explicitly in the IDE. Any breakpoints added via double click on the marker
bar are by default hardware breakpoints. If the hardware resources are not there then the breakpoint setting will
fail. In case of a hardware breakpoint setting failure, an error message will prompt the user to switch to asoftware breakpoint.
To select a default Hardware or Software breakpoint type:• Right-click on the marker bar to pop up the context menu. For a hardware breakpoint, select [Breakpoint
Types] → [e² studio Breakpoint]. For a software breakpoint, select [Breakpoint Types] → [C/C++
Breakpoints].
To set a breakpoint:
1. Open “r_cg_main.c”, double-click on the marker bar located in the left margin of the [C/C++ Editor] pane toset a breakpoint. A dot(Hardware breakpoint) or(Software breakpoint) is displayed in the marker bar
depending on the [Breakpoint Type] selected. [Breakpoint Type] is hardware breakpoint by default.
2. Alternatively, right-click at the marker bar to choose [Toggle Hardware Breakpoint] or [Toggle Software
Breakpoint] to set a hardware breakpoint
or a software breakpoint .
3. Click [Windows] → [Show View] → [Breakpoints] or icon
(or use shortcut key [ALT] + [Shift] + [Q], [B]) toopen the [Breakpoints] view to view the corresponding software breakpoints set. Software breakpoints canbe enabled and disabled in the [Breakpoints] view.
To disable breakpoints, users can choose to disable specific breakpoints or to skip all breakpoints:
1. To disable a specific breakpoint, right-click on the Software breakpoint or Hardware breakpoint located in
the left margin of the [C/C++ Editor] pane and select [Disable Breakpoint], or uncheck the related line in the
Breakpoints view. A disabled breakpoint is displayed as a white dot (or ).
2. To skip all breakpoints, click on theicon in the Breakpoints view. A blue dot with a backslash will appear
in the editor pane as well as in the Breakpoints view.

Figure 5-12 [Breakpoints] View

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 43 of 63

Renesas e² studio
5.4.2

Quick Start Guide

Expressions View

Expressions view monitors the value of global variable, static variable or local variable during debugging. For all
RX debuggers, these variables (including the local variables in scope) can be set for real-time refresh.

Figure 5-13 [Expressions] View
To watch a global variable,
1. Click [Window] → [Show View] → [Expressions] or icon

to open the [Expressions] view

2. Drag and drop a global variable over to the [Expressions] view. (Alternatively, right-click at the global variable
to select “Add Watch Expression…”menu item to add it to the [Expressions] view).
3. In the [Expressions] view, right-click to select “Real-time Refresh” menu item. This refresh the expression
value in real-time when program is running. The character “R” indicates that this global variable will be
updated in real-time.
4. To disable the “Real-time Refresh”, simply right-click to select “Disable Real-time Refresh” menu item.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 44 of 63

Renesas e² studio

Quick Start Guide

Local variables can be added with the same way. However, the watch is not available when the program isrunning out of the scope of the variable.

Figure 5-14 Add Local Variable To Expression View
For a variable of which address is uniquely determined (static variable), the value can be referenced by explicitly
specifying the scope even when the variable is executing outside the scope.
For example, if you want to refer to the "myval" variable in the scope of the function myfunc(), you can create it in
the expression view in the format "myfunc::myval" (with two colons between them).

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 45 of 63

Renesas e² studio
5.4.3

Quick Start Guide

Registers View

Registers view lists the information about the general registers of the target device. Changed values arehighlighted when the program stops.

Figure 5-15 [Registers] View
To view the general register “r0”,1. Click [Window] → [Show View] → [Registers] or icon

to open the [Registers] view.

2. Click “r0” to view the values in different radix format.
Values that have been changed are highlighted (e.g. in yellow) in the [Registers] view when the program stops.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 46 of 63

Renesas e² studio
5.4.4

Quick Start Guide

Memory View

Memory view allows users to view and edit the memory presented in “memory monitors”. Each monitor
represents a section of memory specified by its location called “base address”. The memory data in eachmemory monitor can be presented in different “memory renderings”, which are the predefined data formats (e.g.
Hex integer, signed integer, unsigned integer, ASCII, image etc.).
To view memory of a variable (e.g. “adc_count”),
1. Click [Window] → [Show View] → [Memory] or icon
2. Click the icon

to open the [Memory] view.

to open [Monitor Memory] dialog box. Enter the address of the variable “adc_count”.

The global variable “adc_count” is presented inmemory renderings of “Hex Integer” format.

MemoryMonitorfor“adc_count” is specified by
the address “&adc_count”

Figure 5-16 [Memory] View (1/2)

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 47 of 63

Renesas e² studio

Quick Start Guide

To add new renderings format (e.g. Raw Hex) for the variable “adc_count”,
3. Click the tab

to select “Raw Hex” to add the rendering

This creates a new tab named “&adc_count < Raw Hex>” next to the tab “&adc_count<Hex Integer>”.

Figure 5-17 [Memory] View (2/2)

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 48 of 63

Renesas e² studio
5.4.5

Quick Start Guide

Disassembly View

Disassembly view shows the loaded program as assembler instructions mixed with the source code forcomparison. Current executing line is highlighted by an arrow marker in the view. In the [Disassembly] view, user
can set breakpoints at the assembler instruction, enable or disable these breakpoints, step through thedisassembly instructions and even jump to a specific instruction in the program.

This allows the assembly
source to be linked with the C(
Opcodes

ti

d b

t

t)

Function Offsets

Figure 5-18 [Disassembly] View

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 49 of 63

Renesas e² studio

Quick Start Guide

To view both C and assembly codes in a mixed mode,
1. Click [Window] → [Show View] → [Disassembly] or icon
2. Click iconcontext).

to open the [Disassembly] viewto enable the synchronization between assembly source and the C source (active debug

3. In [Disassembly] view, right-click at the address column to select “Show Opcodes” and “Show Function
Offsets”.
4. You can enable source addresses within the editor using the context menu.

Figure 5-19 Source Addresses Menu

Figure 5-20 Source Addresses Displayed In Editor

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 50 of 63

Renesas e² studio
5.4.6

Quick Start Guide

Variables View

Variables view displays all the valid local variables in the current program scope.
Please refer to ‘Expressions’ view to watch global variables or external variables out of current program scope.

Figure 5-21 [Variables] View
To observe a local variable (e.g. “position” for function “R_LCD_Display()”),
1. Click [Window] → [Show View] → [Variables] or icon

to open the [Variables] view.

2. Step into the function “R_LCD_Display()” to view the value of local variable “position”.
Note:
The variables which optimized out or temporary allocated to accumulator registers may not appear in this view.
Please refer to Disassembly view if necessary to confirm which registers (also refer to Registers view) ormemory are used as the variable.
By disabling optimization, variables would become visible in most of the cases. However, it means to give up all
benefits of optimization such as memory efficiency, code size reduction and performance improvement.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 51 of 63

Renesas e² studio
5.4.7

Quick Start Guide

Eventpoints View

An event refers to a combination of conditions set for executing break or trace features during program
execution. [Eventpoints] view enables user to set up or view defined events of different category e.g. trace start,
trace stop, trace record, event break, before PC, performance (timer) start and performance (timer) stop.
The number of events that can be set and the setting conditions differ with each MCU. These are two (2) typesof events:•

Execution address: The emulator detects execution of the instruction at the specified address by the CPU. It
can be a “before PC” break (e.g. with event condition is satisfied immediately before execution of the
instruction at the specified address) or other events (e.g. with event condition is satisfied immediately after
execution of the instruction at the specified address).

•

Data access: The emulator detects access under a specified condition to specified address or specified
address range. This allows to setup complex address and data matching criteria.

Event combination (e.g. OR, AND (cumulative) and Sequential) can be applied to two (2) or more events.

Figure 5-22 [Eventpoints] View (1/2)
To set an event break for a global variable when address/data is matched (e.g. when adc_count = “0x6”),
1. Click [Window] → [Show View] → [Eventpoints] or icon

to open the [Eventpoints] view.

2. Double-click at “Event Break” option to open [Edit Event Break] dialog box
3. Click [Add…] button to continue.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 52 of 63

Renesas e² studio

Quick Start Guide

Figure 5-23 [Eventpoints] View (2/2)
4. Select “Data Access” as the eventpoint type.
5. Go to the [Address Settings] tab, click the icon
this global variable is “&_$adc_count”)
R20UT5293EJ0110 Rev.1.10
March 26,2024

to browse for the symbol “_$adc_count”. (The address ofPage 53 of 63

Renesas e² studio

Quick Start Guide

6. Next, switch to the [Data Access Settings] tab, enable the [Compare Settings] checkbox and set the compare
value equals to “0x6”. Click [OK] to proceed.
7. Ensure that the event break for “adc_count = 0x6” is set and enabled in the [Eventpoints] view. Reset to
execute the program from the start. Press SW1 6 times.

Figure 5-24 Execution Of Event BreakFigure 5-24 shows that when adc_count reaches the value of 6 (or 0x6), the program stops at code line No.140(right after the line of code increasing adc_count).

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 54 of 63

Renesas e² studio
5.4.8

Quick Start Guide

IO Registers View

IO Registers is also known as the Special Function Registers (SFR). The [IO Register] view displays all theregisters set defined in a target-specific IO file, including their address, hex and binary value. User can further
customize own [IO registers] view by adding IO registers selectively to the [Selected Registers] pane.

Figure 5-25 [IO Registers] View
To view selected IO registers (e.g. PDR and PCR in PORT0),
1. Click [Windows] → [Show View] → [Others…]. In “Show View” dialog, click [IO Registers] under [Debug] oricon

to open the [IO Registers] view

2. Under the [All Registers] tab, locate [PORT0] in the [IO Registers] view. Expand the PORT0 IO register list.
You could also use Search buttonin the IO Register toolbar to quickly search by name.

3. Drag and drop the “PDR” and “PCR” to the [Selected Registers] pane. A green dot
indicates the status of being the selected register(s).

besides the IO register

4. Switch to the [Selected Registers] tab to view “PDR” and “PCR” of the “PORT0” IO register.
The expanded IO register list may take a longer time to load in the [All Registers] pane. Hence, it is advisable tocustomize and view multiple selected IO registers from the [Selected Registers] pane.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 55 of 63

Renesas e² studio
5.4.9

Quick Start Guide

Trace View

Tracing means the acquisition of bus information per cycle from the trace memory during user program
execution. The acquired trace information is displayed in the [Trace] view. It helps user to track the program
execution flow to search for and examine the points where problems arise.
The trace buffer is limited (with size of 1 to 32 Mbytes), oldest trace data is overwritten with the new data after
the buffer has become full.

Figure 5-26 [Trace] View (1/2)

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 56 of 63

Renesas e² studio

Quick Start Guide

To set a point-to-point trace between the two (2) functions (e.g. tracing from function “main()” to“R_LCD_Display()”),
1. Click [Windows] → [Show View] → [Others…]. In “Show View” dialog, click [Trace] under [Debug] or icon
to open the [Trace] view.
2. Turn on the Trace view by selecting the
3. Click icon

icon.

(Acquisition) to set•

Trace Mode: "Fill until stop”•

Trace Type: “Branch”•

Bus Master Of Data Access: “CPU”

4. Click [OK] to proceed.

Figure 5-27 [Trace] View (2/2)
R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 57 of 63

Renesas e² studio
5. Click

Quick Start Guide(Edit Trace Event Points) to open [Trace Eventpoints] dialog box

6. Under the [Start] tab, add the 1st event point at “main()” function (by the execution address “&main”).
7. Then, switch to [Stop] tab, add the 2nd event point at “R_LCD_Display()” function (by the execution address“&R_LCD_Display”).
8. Next, execute the program after reset.

Disassembly
Save

Filter

SourceReverseOrder

Trace On/OffBus

Figure 5-28 Point-To-Point Trace Between Two Functions
The figure above shows the trace result from function “main()” to “R_LCD_Display()”. The trace result can befiltered by the key trace parameters (e.g. branch type, address range) and saved to the .xml format (with theinclusion of bus, assembly and source information).
Note:External trace feature of RX device with E20 emulator works only through Mictor-38pin interface. However,
it is not available through 14pin JTAG/FINE interface, even with E20 emulator. RX emulator interface
specifications can be downloaded at the following site.
https://www.renesas.com/search/keyword-search.html#q=R20UT0399
R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 58 of 63

Renesas e² studio
5.4.10Quick Start Guide

Memory Usage View

Memory view allows users to view the total memory size, usage of ROM and RAM ratio and detailed informationof sections, objects, symbols, module, vector and cross reference used in project.
To view the memory usage of a project,
1. Click [Window] → [Show View] → [Other…] → [Debug] → [Memory Usage] to open the memory usage view.
2. The default display of memory usage view is different for each kind of project.
a. The GUI of memory usage view for executable project which uses Renesas Toolchain includes 3
regions: (1) Group size region, (2) RAM/ROM Usage region/Device Memory Usage region, (3) Detailtable region. The map file location is shown at bottom bar.

(1)
(2)

(3)
Map file location

Figure 5-29 Executable Project - Renesas Toolchain

b. For executable project which uses GCC Toolchain, “Memory region usage" region (2) will be displayed
instead of RAM/ROM usage region:

(1)
(2)

(3)

Map file location

Figure 5-30 Executable Project - GCC Toolchain

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 59 of 63

Renesas e² studioc.

Quick Start Guide

For library project which uses Renesas Toolchain, “Library information view" will be displayed instead of“Group size view”
Note: Only available for Renesas CCRX or CCRL toolchains.

(1)

(2)

(3)
Map file location

Figure 5-31 Library Project - Renesas Toolchain

d. Memory usage view is not available for library project which uses GCC Toolchain.
Group size view:
Displays the total size of Program, Constant, Initialized Data, Uninitialized Data, Data, Stack and Other
according to the selected map file.
Note: This view only displays for executable project of supported toolchains.
Library information view:
Displays the information of selected library list file. The information to be visualized on this region consists of:• The name of the selected library•

The type of CPU specified by the project•

Endian•Attribute•

Number of module.

RAM/ROM usage region:
Shows percentage of RAM/ROM usage by numerical value and status of bar. Color of bar is based on
percentage value.
•

If percentage < 75%: Green.

•

If percentage >= 75% and percentage < 90%: Orange.

•

If percentage >= 90%: Red.

Memory region usage region:
Display feature of this region is similar to RAM/ROM usage region.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 60 of 63

Renesas e² studio

Quick Start Guide

Device memory usage region:
Device Memory Usage region shows device memory of selected project’s device. Each memory areashows name, start address, end address, used size and size.

Figure 5-32 Device Memory Usage Region
Expand memory area to see all sections. Color of sections corresponds with that of Group Size Region.

Figure 5-33 Expand Memory Area
Detail table region:
Display the map file information of an active project or the opened map file.
•“Section” tab: contains “Linkage map” table which displays the list of Sections analyzed from map fileand its detailed information.

•“Object” tab: contains “Object” table which displays the list of Objects analyzed from map file and its
detailed information.

•“Symbol” tab: contains “Symbol” table which displays the list of Symbols analyzed from map file and its
detailed information.

•“Vector” tab: displays the vector table information that is retrieved from map file. This tab is only available
for executable project that is configured to work with Renesas CC-RX/CC-RL/CC-RH toolchains.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 61 of 63

Renesas e² studio

Quick Start Guide•“Cross Reference” tab: displays the cross reference information that is retrieved from map file. This tab is
only available for executable project.

•“Module” tab: contains “Module” table. “Module” tab is only available for library project that is configured
to work with Renesas CC-RX/CC-RL/CC-RH toolchains.

Map file location:
Memory Usage will display the information of (*.map) file or library list file (*.lbp) from project. User can see
the relative path of selected map file or library list file at the bottom of Memory Usage view.

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 62 of 63

Renesas e² studio

6.

Quick Start Guide

Help

The help system allows users to browse, search, bookmark and print help documentation from a separate Help
window or Help view within the workbench. Users can also access an online forum dedicated to the e² studiofrom here.
Click on [Help] tab to open the Help menu.

(1)
(2)
(3)

(4)

Figure 6-1 Help – Help Menu
Quick Help Tips:(1) Click [Welcome] for an overview of the e² studio and to view Release Notes.
(2) Click [Help Contents] to open a separate Help window with a search function.
There are many useful topics under the [Help Contents]. Example, the “Debugging Projects” topic which
provides useful information such as debug configuration, supported number of breakpoints, etc. It can belaunched by clicking on the [Help] menu → [Help Contents] → “e2 studio User Guide”.
(3) Click [Show Contextual Help] to open the Help view within the workbench.
(4) Click [RenesasRulz Community Forum] to go an online forum that is dedicated to topics and discussions
related to the e² studio (Internet connection is required).

R20UT5293EJ0110 Rev.1.10
March 26,2024

Page 63 of 63

Revision History
Rev.

Renesas e² studio User’s Manual: Quick Start Guide

Date

Description
Page

Summary

1.00

June 21, 2023-

First edition for RX, RL78, RH850 based on e² studio 2023-04

1.10

March 26, 2024-

Updated installation procedure as the latest e² studio version. Added descriptions of
RISC-V MCU.

Renesas e² studio User’s Manual: Quick Start Guide for RX, RL78,
RH850, RISC-V MCU Family
Publication Date:

Rev.1.10

March 26.2024

Published by:Renesas Electronics Corporation

RX/RL78/RH850/RISC-V MCU Family

R20UT5293EJ0110