Renesas e1 User Manual

E1/E20/E2/E2 Lite Additional Document 3. Notes on Usage
R20UT2937EJ0301 Rev.3.01 Page 37 of 45
Jul 1, 2020
3.3.2 Securing a Stack Area for Debugging
The debugger requires 10 bytes as a stack area for debugging. Since this area is allocated immediately
after the stack area, the address of this area varies depending on the stack increase and decrease. That
is, 10 extra bytes are consumed for the stack area used.
Make sure the stack area for debugging does not exceed the range of the internal RAM space.
Figure 3-2 shows an example in which the stack area has increased with the start address of the
internal RAM space being 0xFFE60.
Stack area for
debugging
10 bytes
Stack area
Available space
in internal RAM
0xFFE60
0xFFEDF
Stack area for
debugging
10 bytes
Stack area
Available space
in internal RAM
0xFFE60
0xFFEDF
Stack area for
debugging
10 bytes
Stack area
0xFFEDF
0xFFE60
Figure 3-2 Variation of Address of Stack Area for Debugging
3.3.3 Setting an On-Chip Debugging Option Byte
This is the area for the security setting to prevent the flash memory from being read by an unauthorized
person.
For settable values, refer to the user's manual for each MCU.
[Setting an on-chip debugging option byte]*
1
Set the on-chip debugging option byte in either of the following ways.
(a) Embed the on-chip debugging option byte at address 0xC3 in the user program.
(b) Set the on-chip debugging option byte by the build tool.
For details on the setting method, refer to the user's manual for the build tool.
*1
If the value of the on-chip debugging option byte set in the device disables on-chip debugging
(OCDENSET = 0), the debugger cannot be started when "No" is selected in the [Permit flash
programming] property of the debugger. If a setting to enable flash programming is made, though the
debugger can be started, the flash memory will be in an erased state when the debugger is started.

Renesas e1 Specifications

General

Host Interface	USB
On-Chip Debugging	Yes
Manufacturer	Renesas Electronics
Product Category	Debug Emulators
Target MCU Family	Renesas MCUs
Programming	Supported
Power Supply	USB
Category	Emulators
Supported Devices	Renesas MCUs

Summary

General Precautions in the Handling of Microprocessing Unit and Microcontroller Unit Products

1. Overview

1.1 Overview of E1/E20/E2 Emulator and E2 Lite

Introduces the E1, E20, E2, and E2 Lite emulators and their primary functions as debugging tools.

1.4 Supported RL78 Devices

Details the specific RL78 family MCUs supported by the emulators, including RL78/G1x series.

1.5 External Trigger I/O Specifications

2. Designing the User System

2.1 Connecting Emulators to User System

Guides on establishing the physical connection between the emulators and the user system.

2.2 User System Connector Installation

2.3 14-Pin Connector Specifications

Details the specifications and pinout of the standard 14-pin connector used for system connection.

2.4 Recommended Connection Circuits

Shows recommended circuit designs for connecting the 14-pin connector to RL78 family MCUs.

2.5 Notes on Connection

Offers important guidelines and considerations for making reliable connections between the emulator and the MCU.

2.5.1 RESET# Pin Handling

2.5.3 GND and 2.5.4 VDD Connections

2.7 User System Design Notes

3. Notes on Usage

3.1 Turning Power On/Off

Provides step-by-step procedures for safely powering the emulators and the user system on and off.

3.1.2 Emulator-Supplied Power to User System

Details the process and considerations when the emulator supplies power to the user system.

3.2 Emulator Power Supply Function

Explains the voltage supply capabilities of the E1/E2/E2 Lite emulators and associated voltage drops.

3.3 MCU Resource Occupation for Debugging

3.3.4 Security ID Setting

3.8 Final User Program Evaluation

3.9 Debug Functions

Covers various debugging functions like step execution, breakpoints, and standby mode debugging.

3.9.6 Extended Functions of the E2