Renesas RH850 Series, RH850/E2x Series User Manual

E2 Emulator

(Notes on Connection of RH850/E2x series)

Rev.1.00 July 2018

Supported Devices:

RH850/E2x series

All information contained in these materials, including products and product specifications,

website (http://www.renesas.com).

RH850 Family

Additional Docum ent for User’s Manu al

represents information on the product at the time of publication and is subject to change by
Renesas Electronics Corp. without notice. Please review the latest information published by
Renesas Electronics Corp. through various means, including the Renesas Electronics Corp.

Notice

on of

1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operati
semiconductor products and application examples. You are fully responsible for the incorporation or any other use of the circuits,
software, and i nformation i n the desi gn of your produc t or syste m. Renesa s Electr onics discla ims any and al l liabilit y for any loss es and
damages incurred by you or third parti es arising from the use of these circuits, software, or infor ma tion.

2. Renesas Elec tronics hereby expressly disclaims any warranties against and liabi lity for infringeme nt or any other claims involving pa tents,
copyrights, or other intellectual prop erty rights of third part ies, by or arising from the use of Renesas Electronics pr oducts or technical
information described in this document, including but not limited to, the product data, drawings, charts, programs, algorithms, and
application examples.

3. No license, expr ess, impli ed or otherwi se, is gra nted hereb y under an y patents , copyright s or other intell ectual prop erty rights of Renesas
Electronics or others.

4. You shall not alter , modify, copy, or revers e engineer any Renes as Electr onics 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.

5. Renesas Electroni cs products are cla ssified accordi ng to the following two qua lity grades: “Sta ndard” and “High Quali ty”. The intended
applications for each Renesas Electronics product depends on the product’s quality grade, a s indicated below.
“Standard”: Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment;

home electronic appliances; machine tools; persona l electronic equip me nt; 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; et c.
Unless expressl y designated a s a high reli abilit y product or a product for ha rsh environ ments in a Renes as Elec tronics data sheet or ot her
Renesas Electr onic s docum ent, Ren esa s El ectr onic s pr oduc ts a re not i ntended or a uthor i z ed for us e in produc t s or systems tha t may pose a
direct threat to huma n life or bodily injury (ar tificial life supp ort devices or systems; s urgical implantations ; etc.), or may cause ser ious
property damage (s pace system; unders ea repeaters ; nuclear power cont rol systems; a ircraft control systems; key pla nt systems; milit ary
equipment; etc. ). Renesa s El ectroni cs dis claims a ny and al l liab ilit y for any damages or los ses i ncurred b y you or any thi rd parties arising
from the use of any Renes as Electronics product that is inconsistent with any Renesa s Electronics data sheet, us er’s manual or other
Renesas Electronics document.

6. When using Renesas Elect roni cs product s, r efer to t he lates t product informa tion ( data sheet s, user ’s manu als, applica tion not es, “Genera l
Notes for Handling a nd Using Semic onductor Devices ” in the relia bility handbook, etc.), and ens ure that usage c onditions are w ithin the
ranges specified by Renesas Electronics with respect to maximum ratings, operating power supply voltage range, heat dissipation
characterist ics, insta llation, etc. Renesa s Electr onics dis claims any and a ll liabi lity for any ma lfunct ions, fa ilure or acc ident aris ing out of
the use of Renesas Electronics products outside of such specified ranges.

7. Although Renesa s Electroni cs endeavors to imp rove the qual ity and relia bility of Renes as Electroni cs products, semiconductor products
have specific cha racteristics, such as the occurrenc e of failure at a certain rate and malf unctions under certain use conditi ons. Unless
designated as a high reliability product or a product for harsh environments in a Renesas Electronics data sheet or other Renesas
Electronics document, Renesa s Elect ronics produc ts are not s ubject t o radiation res istance des ign. You are r esponsib le for implement ing
safety measures to gua rd aga ins t the pos sibi lity of b odil y injur y, injur y or da mage c aus ed by fir e, a nd/or d anger t o the p ublic in the e vent
of a failure or malf unction of Renesas Elec tronics pr oducts, s uch as safety design for ha rdware a nd software, including b ut not limited t o
redundancy, fire control and malfunction prevention, appropriate treatment for aging degradation or any other appropriate measures.
Because the e valuat ion of mic roc omputer s oft ware a lone is very dif fi cult and imp ract ical, you are res pons ibl e for eval uat ing the s afet y of
the final products or systems manufa ctured by you.

8. Please contact a Renesas El ectronics sa les office f or details as to environmenta l matters such as the en vironmental compatibility of each
Renesas Elec tronic s produc t. Y ou are r esp onsibl e for c aref ully and s uff icient ly inves ti gati ng appl icab le laws and r egulat ions that regula te
the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive, and using Renesas Electronics
products in compl iance with all these applicab le laws and regul ations. Renesa s Electr onics disclai ms any and all liab ility for damages or
losses occurring as a result of your noncompliance with applicable laws and regulations.

9. Renesas Electr oni cs pr oduc ts and t echnol ogi es s ha ll not be us ed f or or incorp or ated i nt o any pr oduc ts or s ystems whos e manuf act ur e, us e,
or sale is pr ohibited under a ny applica ble domestic or foreign laws or regulati ons. You shall comply with an y applicabl e export contr ol
laws and regulations promulgated and administered by the governments of any countries asserting jurisdiction over the parties or
transactions.

10. It is the respons ibility of the buyer or distributor of Renesas Electronics products, or any other party who distr ibutes, disposes of, or
otherwise sell s or tr ansf er s the p r oduct to a thi rd pa r ty, t o noti f y such t hir d p ar ty in a dvanc e of the c ont ent s a nd condi t ions s et f orth i n t his
document.

11. This document sha ll not be repri nted, rep roduced or dup licated i n any form, in whole or in part, wit hout prior wr itten consent of Renesa s
Electronics.

12. Please contact a Renesas Electronics sales of fice if you have an y questions r egarding the information conta ined in this document or
Renesas Electronics products.

(Note 1) “Renesas Electr onics” as used in this document means Renesas El ectronics Corp oration and a lso includes i ts directl y or indirectly

controlled subsidiaries.

(Note 2) “Renesas Electronics product(s)” means any product developed or manufa ctured by or for Renesas Electronics.

(Rev.4.0-1 November 2017)

E2 Emulator Contents

Contents

1. Outline ............................................................................................................................................................................................. 4

1.1 Features of the E2 emulator ..................................................................................................................................................... 4

1.2 Configuration of manuals .......................................................................................................................................................... 4

2. Connecting the Emulator and User System ...................................................................................................................................... 5

2.1 Connector mounted on the user system ................................................................................................................................... 5

2.2 Pin assignments of the connector ............................................................................................................................................. 7

2.3 Examples of recommended connections between the connector and MCU .............................................................................. 8

2.4 E2 Expansion Interface (External trigger input and output) ..................................................................................................... 15

3. Procedure for Connecting the Emulator to the User System ........................................................................................................... 16

3.1 When a separate power supply is used for the user system ................................................................................................... 16

3.2 When power is supplied to the user system from the emulator ............................................................................................... 17

4. Functional overview ....................................................................................................................................................................... 18

4.1 Software tracing (LPD output)................................................................................................................................................. 21

5. Notes on Usage ............................................................................................................................................................................. 22

5.1 General cautionary notes........................................................................................................................................................ 22

5.2 Notes on connecting the E2 emulator ..................................................................................................................................... 23

5.3 Notes on differences in operation between the actual device and the emulator ...................................................................... 24

5.4 Cautionary notes on debugging .............................................................................................................................................. 26

6. Internal Circuit of the Emulator ....................................................................................................................................................... 33

R20UT4140EJ0100 Rev.1.00 Page 3 of 37
Jul. 01, 2018

E2 Emulator 1. Outline

1. Outline

1.1 Features of the E2 emulator

The E2 emulator is an on-chip debugging emulator tha t includes a flash pr ogramming function, which is used for
debugging a nd progra mming programs to be embedded in microcontrollers that have on-chip flash memory. That is, the
product can be used for both debugging programs while the target microcontroller is connected to the user system, and to
write programs to the on-chip flash memory of microcontrollers.

1.2 Configuration of manuals

Documentation for the E2 emulato r manual is in two parts: (1) E2 Emulator User’s Manual and (2) E2 Emulator
Additional Docume nt for User ’s Manual (this manual). Be sure to re ad both of the manuals before using the E2 emulator.

(1) E2 emulator user’s manual

The E2 Emulator User’s Manual describes hardware specifications including the following items:

• Components of the emulator

• Emulator hardware specifications

• Connecting the emulator to a host computer and user sys t em

(2) E2 emulator additional document for user’s manual (this manual)

The E2 Emulator Additional Docume nt for User’s Manual describes functions of the debugger and gives details and
notes on points that depend on the target device.

R20UT4140EJ0100 Rev.1.00 Page 4 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

7614-6002

Sumitomo 3M Limited

14-pin straight type (Japan)

12

11 13

14

9107856341

2

5 mm

5 mm

5 mm 5 mm

Top View

Area where restriction applies to mounted components

(components must have heights no greater than 10 mm)

2. Connecting the Emula tor and User System

To connect t he E2 emulator, a connector for the user system interface cable must be mounted on the user system. When
designing the user system, read this chapter of this manual and the hardware manual for the MCUs to be used.

2.1 Connector mounted on the user system

Table 2-1 shows the recommended connectors for connection of the E2 emulator. When other components are mounted
around the connector, do not mount components with heights exceeding 10 mm within 5 mm of the connector on the user
system as shown in

Figure 2-1

Table 2-1 Recommended Connectors

Type

14-pin
connector

Number

2514-6002 3M Limited 14-pin straight type (other countries)

Manufacturer Specification

Figure 2-1 Area where Restrict ion Applies to Mounted Components

To connect an E2 emulator to the connector on the user system, use the connector conversion adapter that comes with the
E2 and the user system interface cable. Figure 2-2 shows an example of the connection.
After connecting the user system interface cable to the connector conversion adapter, connect the connector conversion
adapter to the connector on the user system.
The connector conversion adapter is provided with a switch. Setting for the switch must be on the “1” side for the
RH850. Operation is not guaranteed if the switch is on the “3” side. For setting the swi tc h, refer to Table 2-2.

R20UT4140EJ0100 Rev.1.00 Page 5 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

Setting

Description

3

The target device is an RL 78 micr oco nt ro ller.

CAUTION

Note on connector insertion and removal (1):

When connecting or disconnecting the user-system interface cable and the connector conversion adapter, grasp

damage the wiring.

CAUTION

Note on connector insertion and removal (2):

20-pin (1.27-mm pi

tch

) user-system

interface cabl e

13 mm

10.5 mm

User syste m

14-pin (2.54-mm pitch)
connector
7614-6002 or 2514-6002

20-pin (1.27-mm pitch)
to 14-pin (2.54-mm
pitch) connector
conv ers i on adap t er

20-pin (1.27-mm pitch) to 14-pin (2.54-mm
pitch) connector conversion adapter
(top view)

The switch (SW1) must be i n posi tion 1 (labelled
“Other”*) for RH850 or RX M CUs or i n pos ition 3
(labelled “RL78”*) for RL78 MCUs.

Connector for the emulator:

10.5 mm

29.0 mm

1

3

SW1

TP1

GND

RL78

Other

CN1

*: These are no t print ed on s om e versions
of the con versi on adapter .

Figure 2-2 Connecting the User System Interface Cable to the 14-pin Connector in the E2 Emulator

Table 2-2 Setting of Switches (SW1)

1 The target device is an RH 8 50 microc ontroller (default setting).

both sides of the board of the connector conversion adapter. Pulling the user-system int erface cable itself will

Be aware that the connector conversio n adapter must be inserted with the correct orientation. Connecting the
connector conversion adapter with the wrong orientation may cause damage.

R20UT4140EJ0100 Rev.1.00 Page 6 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

Signal name ( -: unused)

Debugging

Programming (RFP)

4-pin LPD

2-wire UART

CSI

1

LPDCLK



FPCK

Input

3

TRST





Input 4 FPMD0

FPMD0

FPMD0

Input 5 LPDO

FPDT

FPDT

Output

6



FPMD1

FPMD1

Input 7 LPDIO

FPDR

FPDR

I/O 8 TVDD

TVDD

TVDD

 9 







10 (*2)

EVTO







11

LPDCLKO





Output

12 (*1)

GND

GND

GND



13

RESET

RESET

RESET

Input

14 (*1)

GND

GND

GND



CAUTION

Unused pins:

Do not apply signals from the user system to unused pins. Doing so may damage the pins.

2.2 Pin assignments of the connector

Table 2-3 shows the pin assignments of the 14 -pin connector.

Table 2-3 Pin Assig nments of the 14-pin Connector

Pin No.

2 (*1)

GND GND GND

I/O (*3)



Notes 1. Securely connect pins 2, 12, and 14 of the connector to GND of the user system. These pins are used for

electrical GND and to monitor connection with the user system by the E2 emulator.

2. The EVTO pin provides for the output of event s i gnals from the device to the E2 emulator. Although

connecting the EVTO pin is no t essential, we recommend connecting this pin in advance.
In some devices, the EVTO pin is not pre sent o r is only available as a pin function multiplexed with other
functions. W hen the EVTO pin is a multiplexed pin function and the event output function is to be used, se t
the EVTO pin so that it will function a s the EVTO pin by making the required register settings described in
the user’s manual for the device.

3. Input and output are defined from the perspective of the user system.

R20UT4140EJ0100 Rev.1.00 Page 7 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

Usage

Tool

Device Mode

Connection Interface

Programming

Renesas Flash

Serial programming

2-wire UART or CSI

Debugging

CS+ or MULTI (*)

Normal operation mode

4-pin LPD

2.3 Examples of recommended connections between the connector and MCU

Different tools are used with the E2 emulator according to whether the purpose is debugging or flash programming.
Table 2-4 shows the relationships between the operating modes and connection interfaces.

Table 2-4 Relationships between the Oper ating Modes and Connection Int e rfaces

Programmer (RFP)

mode

or user boot mode

Note: This refers to the MULT I integrated development environment from Green Hills Software. It is simply referred to

as MULTI in the remainder of this document.

This section describes examples of recommended connections between the E2 emul ator and the target MCU. Since there
are various examples of recommended connections according to the purpose of the E2 emulator, select the appropriate
circuit with reference to Table 2-5. Be sure to take the specifications of the target device as well as measures to prevent
noise into consideration when designing your circuit.

Table 2-5 Purpose of the E2 Emulator and the Corresponding Example of Recommended Connection s

Purpose

Both debugging (4-pin LPD) a nd progr ammi ng (2-wire UART or CSI)
Only programming (2-wire UART)
Only programming (CSI)

Figure

Figure 2-3
Figure 2-4
Figure 2-5

R20UT4140EJ0100 Rev.1.00 Page 8 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

CAUTION

Connection of emulators from other manufacturers:

The E2 emulator does not support debugging through a JTAG interface; however, if an emulator from another

2.3.1 Example of recommended connections for both debugging (4-pin LPD) and programming

(2-wire UART or CSI)

Figure 2-3 Example of Connecti on

 Refer to section 2.3.4, Connecting the RESET pin, for more information on the reset circuit.
 For details on TVDD, refer to section 2.3.5, Connecting the TVDD pin.
 Make wiri ng runs between the 14-pin connector and target device as short as possible (within 50 mm is

recommended). Do not connect the signal lines between the connector and MCU to other signal lines.

 Use GND to apply a guard ring for the wiring which runs between the 14-pin connector and target device. Do

not route high-speed signal lines parallel to each other or allow them to cross each other.

 Pin names may vary among target devices. Refer to the user’ s manual for the target device you are using for the

actual pin names.

 Proceed with appropriate processing for pins of target devices which do not require connection to the emulator

in accord with the descriptions in “Handling of Unused Pins” in the user’s manual for the target device.

manufacturer, which supports the JTAG interface, is to be connected, connect the TMS signal to pin 9 of the 14­pin connector. If you use such an emulator for debugging, be sure to read its manual beforehand.

R20UT4140EJ0100 Rev.1.00 Page 9 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

2.3.2 Example of recommended connections for only programming (2-wire UART)

Figure 2-4 Example of Connecti on

 Refer to section 2.3.4, Connecting the RESET pin, for more information on the reset circuit.
 For details on TVDD, refer to section 2.3.5, Connecting the TVDD pin.
 Make wiri ng runs between the 14-pin connector and target device as short as possible (within 50 mm is

recommended). Do not connect the signal lines between the connector and MCU to other signal lines.

 Use GND to apply a guard ring for the wiring which runs between the 14-pin connector and target device. Do

not route hi gh-speed signal lines parallel to each other or allow them to cross each other.

 Pin names may vary among target devices. Refer to the user’s manual for the target device you are using for the

actual pin names.

 Proceed with appropriate processing for pins of target devices which do not require connection to the emulator

in accord with the descriptions in “Handling of Unused Pins” in the user’s manual for the target device.

R20UT4140EJ0100 Rev.1.00 Page 10 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

2.3.3 Example of recommended connections for only programming (CSI)

Figure 2-5 Example of Connecti on

 Refer to section 2.3.4, Connecting the RESET pin, for more information on the reset circuit.
 For details on TVDD, refer to section 2.3.5, Connecting the TVDD pin.
 Make wiri ng runs between the 14-pin connector and target device as short as possible (within 50 mm is

recommended). Do not connect the signal lines between the connector and MCU to other signal lines.

 Use GND to apply a guard ring for the wiring which runs between the 14-pin connector and target device. Do

not route hi gh-speed signal lines parallel to each other or allow them to cross each other.

 Pin names may vary among target devices. Refer to the user’s manual for the target device you are using for the

actual pin names.

 Proceed with appropriate processing for pins of target devices which do not require connection to the emulator

in accord with the descriptions in “Handling of Unused Pins” in the user’s manual for the target device.

R20UT4140EJ0100 Rev.1.00 Page 11 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

RES

RESET

13

Example

Power domain of RES ET

14-pin connector

Target device

2.3.4 Connecting the RESET pin

While you are using the E2 emulator, pin 13 (RESET pin) of the 14-pin connector must be connected to the reset pin of
the target device. An e xample is shown in the figure below.
The E2 emulator fixes the RESET pin to the low level before the debugger is activated. After the debugger is activated,
the emulator either keeps the pin at the low level or plac es it in the high-impedance state in accord with the operation of
the debugger.

Figure 2-6 Example of Connecting a Reset Circuit

 Output of the reset circuit should be either n-channel open drain or be a signal generated solely by a resistor and

capacitor (and possible other components).

 Use the power source for the power domain of the RESET pin of the target device as the destination voltage for

pulling up.

 Pin 13 (RESET) of the E2 emulator is pulled up (by a 100-kΩ resistor) within the emulator (refer to section 6,

Internal Circuit of the Emulato r).

 The RESET pin of the target device may be pulled up or down within the device. On this point, refer to the

user’s manual for the target device.

 The maximum sink current accepted by the RESET pin of the E2 emulator is 2 mA. Select an appropriate pull-

up resistance which does not surpass this value.

 Adjust the time constant of the reset circuit so that the time elapsing before the signal reaches 80% of the high

level from the low level is within 900 µs.

 When you use hot p l ug-in, consider installation of a capacitor between the reset signal and GND in order to

suppress a noise. In this case, however, the specifications of the time described above must be satisfied.

R20UT4140EJ0100 Rev.1.00 Page 12 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

For power supply from the E2 emulator, precision is not guaranteed. When writing a program that requires reliability, do not

program for mass production processes, use the Ren esas Flash Programmer.

WARNING

Warning for Turning the Power On/Off:

connection will result in the host machine, the emulator, and the user system emitting smoke or catching fire.

2.3.5 Connecting the TVDD pin

(1) Power source monitoring function

Be sure to connect the power source for the power domain of the debug interface (JP0 port group) to pin 8 (TVDD
pin) of the 14-pin connector.
The power source connected to the TVDD pin provides power to the final stage output buffer and first stage input
buffer on the E2 emulator circuit. When the E2 emulator is connected, it will draw current as described below in
addition to the current drawn by the user system.

 Approx. 20 mA when TVDD is 3.3 V, and approx. 40 mA when TVDD is 5.0 V

If there is a possibility you will be using hot plug-in connection, be sure to refer to section 2.3.6, Hot plug-in
connection.

(2) Power supply function

The E2 emulator can also supply power at 3.3 V or 5.0 V from the TVDD pin to the user system (at a current of up
to 200 mA). When using this function, take care of the following poi nt s .

 Do not us e this function if power is being separately supplied to the user system. Attempting to do so

might break the E2 emulator.

 Do not us e this function for a user system which draws a current of 200 mA or more. The E2 emulator or

USB interface of the host machine might be broken.

 Make sure that the supplied voltage is within the voltage range required by the user system.
 If 5.0 V is supplied, the voltage might be lower than 5.0 V by 0.3 V or more depending on the environment

of the host machine that is i n use.

use the power supply function of the E2 emulator. Use a stable, separate power supply for the user system. When writing a

When supplying power, ensure that there are no shorts between the user system and power circuit. Only connect
the E2 after confirming that there are no mismatches of alignment on the user system port connector. Incorrect

R20UT4140EJ0100 Rev.1.00 Page 13 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

2.3.6 Hot plug-in connection

Hot plug-in connection of the emulator may lead to a momentary drop in the power-supply voltage on the use r
system. As shown in Figure 2-7, this effect can be reduced by placing a ferrite bead (or inductor) and relatively
large capacitor with low equivalent series resistance near the TVDD line of the connector for connection of the
emulator. However, this measure will not completely elimi nate the voltage drop.

Figure 2-7 Circuit Configuration for Hot Plug-in

Hot plug-in connection can be used with the E2 emulator without the need for a hot pl ug-in adapter. For details, refer to
the E2 Emulator User’s Manual.

2.3.7 Isolator

For a debugging environment where there is a difference in potential between the GND of the user system and that of
the host PC, use the isolator (R0E000010ACB20) which is separately available from Renesas.

2.3.8 Small connector conversion adapter

A small connector conversion adapter (R0E000010CKZ11) is separately available from Renesas for user system
boards which are too small to mount the 14-pin connector that is the standard connector for the E2 emulator. By using
the adapter, you can reduce the area taken up by the connector mounted on your system.
However, when you use the small connector conversion adapter, be aware that the pin assignments of the connector
differ from those of the standard interface connector for the E2 emulator.

R20UT4140EJ0100 Rev.1.00 Page 14 of 37
Jul. 01, 2018

E2 Emulator 2. Connecting the Emulator and User S ystem

2.4 E2 Expansion Interfa ce (External trigger input and output)

Using the expansion interface of the E2 emulato r (the connector for the interface can be found by removing the cover on
which SELF CHECK is printed) enables the input and outp ut of external triggers. For details on the expansion interface,
refer to the E2 Emulator User’s Manual.

Figure 2-8 Expansion Interface of the E2 Emulator

R20UT4140EJ0100 Rev.1.00 Page 15 of 37
Jul. 01, 2018

E2 Emulator 3. Procedure for Connecting the Emulator to the User System

CAUTION

Notes on the User System Power Supply:

While the power of the user system is on, do not turn off the host machine or unplug the USB interface cab le.

3. Procedure for Connecting the Emulator to the User
System

Connect the E 2 emulator t o the user syst em and turn on the po wer by following the procedure below.

3.1 When a separate power supply is used for the user system

<When using the emulator>

(1) Check the power is off.

Check that t he user system is turned off.

(2) Connect t he user syst em.

Connect the emulator and the user system with a user-system interface cable.

(3) Connect t he host machine and turn o n the emulator.

Connect the emulator and the host machine with a USB interface cable. The emulator is turned on by

connecting the USB interface cable.

(4) Turn on t he user system.

Turn on the u s er system.

(5) Launch the debugger .

Launch the debugger.

<When finished using the emulator>

(1) Close the debugger.

Close the debugger.

(2) Turn off the user system.

Turn off the user system.

(3) Turn off the emulator and disconnect the emulator.

Disconnect the USB interface cable from the emulator. The emulator is turned off by disconnecting from the

USB interface cable.

(4) Disconnect the user system.

Disconnect the user-system interface cable from the user system.

The user system may be damaged due to leakage current.

R20UT4140EJ0100 Rev.1.00 Page 16 of 37
Jul. 01, 2018

E2 Emulator 3. Procedure for Connecting the Emulator to the User System

3.2 When power is supplied to the user system from the emulator

Do not use the function that supplies the power to the user system from the emulator for a user sys t em which

draws a current of 200 mA or more. The E2 emulator or USB interface of the host machine might be broken.

<When using the emulator>

(1) Check the power is off.

Check that the user syst em is turned off.

(2) Connect the user system.

Connect the emulator and user system with a user-system interface cable.

(3) Connect the host machine and turn on the emulator.

Connect the emulator and host machine with a USB interface cable, then turn on the emulator.

(4) Launch the debugger.

Launch the debugger and s elect the setting of power supply to the user system.

<When finished using the emulator>

(1) Close the debugger.

Close the debugger.

(2) Turn off the emulator and disconnect the emulator.

Disconnect the USB interface cable from the emulator, then turn off the emulator.

(3) Disconnect the user system.

Disconnect the user-system interface cable from the user system.

R20UT4140EJ0100 Rev.1.00 Page 17 of 37
Jul. 01, 2018

E2 Emulator 4. Functional overview

Parameter

Specification

Corresponding host machine

Computer equipped with a USB port, OS depends on the debugger

User system interface

14-pin connector

Host machine interface

USB 2.0 (full speed or high speed)

Connection to the user system

Connection by the provided user system interface cable

to the user system (make settings with the debugger)

Power supply for the emulator

No need (the host computer supplies power through the USB)

programming

Connection interface for the debugging

4-pin LPD 5.5 MHz /11 MHz /16.5 MHz /33 MHz

Multi-core debugging

Mode selection

Asynchronous debugging or sy nchrono us deb uggi ng

Initial-stop
debugging

Programs can be executed in the initially stopped state after a reset.
Software break

In ROM and RAM areas combined: 2000 points

Hardware break

12 points including those used for both execution and CPU access

hardware break.

Event break

Available (depends on the debugger)

Forced break

Available

Trace-full break
Devices that include an internal trace RAM: Not available

Event

Number of

Devices that do not include an internal trace RAM: 8 points for

available. This depends on the version of the target device.

function

Combination of
events

OR, sequential
Size

Depends on the target device

Traced data

Branches, cycles of data access, cycles of DMA access, cycles of
CRAM access, and software trace

data

Priority

Realtime trace mode (speed is given priority)

priority)

tracing due to the input of an external trigger of E2 emulator

4. Functional overview

Specifications that the E2 emulator supports are listed in the table below. Support for some debugging-related functions
also depends on the debugger. Refer to the user’s manual, etc. for the debugger you are using.

Table 4-1 Specifications

Power supply function 3.3 V or 5.0 V (with current up to 200 mA) can be supplied from TVDD

Connection interface for the flash

Break

events that can
be set

Available

2-wire UART or CSI

conditions (8 points only for execution conditions, and 4 points for either
execution or access conditions)
Comparison with data in access cannot be used as a condition for a

Devices that do not include an internal trace RAM: Available

execution and 8 points for CPU access
Devices that include an internal trace RAM: 8 points for execution, 8
points for CPU access, 4 points for DMA access, and 4 points for
CRAM access

Note: Specifying a range of events for execution may not be

Break, performance measure ment, trace

Tracing
(only for devices
including an internal
trace RAM)

Conditions to
start and stop
recording of

Tracing methods Full stop, full break, overwriting (ring buffer), delay stop and halting

Stopping of program execution, the setting of event condition and
tracing methods

Non-realtime trace mode (comprehensive data collection is given

R20UT4140EJ0100 Rev.1.00 Page 18 of 37
Jul. 01, 2018

E2 Emulator 4. Functional overview

Perfor-

Time (1)

Measurement
section

From run to break
Items measured

Execution time

Performance

32-bit counters

Time (2)

Measurement
section

From run to break, or between two event points

Items measured

Execution time, total execution time, pass count, maximum execution
time, minimum execution time

Performance

32-bit counters (for three sections)

Time (3)

Items measured

Number of instructions executed (all or branches only), number of
interrupts accepted, etc.

section

Items measured

Maximum value, minimum value, latest value, total value, pass count

Performance

32-bit counters (for four sections)

Available (occupies a bus (steals cycles))

Bus, I-Bus, and CPU peripheral areas.

Reset Masking

Available (for selecting whether resets are masked or not during the
execution of a program)

Hot plug-in

Available

Peripheral breaks

Available

Emulator detection by user programs

Available

Address: FF0B 00E0H

Download function

Available

Security ID authentication

Available

Debugging when ICUM is enabled

Available

debugging mode

Target CPU

Selection of a single CPU. (When the debugger is connected to the

the debugger must be re-connected to the emulator.)

storage

Traced data

Software trace data + timestamps (given by the E2 emulator)
Resolution: 8.333 ns, maximum 27 days

Conditions to start

of data

Starting and stopping of program execution (breaks)
Priority of trace
acquisition

Real-time trace mode (priority given to speed)
Non-real-time trace mode (priority given to data)

Trace-full break mode

External trigger

Input signal
channels

E2 expansion interface: 2 (ch. 0: pin 11, ch. 1: pin 12)
channels

mance
mea­sure­ment

(only for

devices
including an
internal
trace RAM)

Pseudo real-time RAM monitoring, Direct
memory modification

Measurement

From run to break, or between two event points

Note: Only available for the general local RAM, cluster RAM, H-Bus, P-

Software tracing
(LPD output)

Condition of the

Destination for

and stop recording

Any 32-bit value which is debugging information from the debugger is
specified and held in the debugging startup register (DBGIFE0) while
the emulator is connected. This function can be used to determine the
state of the emulator being connected or not from within user
programs.

Debugging startup register (DBGIFR0)
Initial value: 0000 0000

H

Only available in the synchronous debugging mode

emulator, a single target CPU is selected. If the target CPU is changed,

“E2 storage”: memory for storage in the E2 emulator

input/output

Recording of trace
memory

Output signal

Ring mode (overwriting mode)
Trace-full stop mode

E2 expansion interface: 2 (ch. 0: pin 9, ch. 1: pin 10)

R20UT4140EJ0100 Rev.1.00 Page 19 of 37
Jul. 01, 2018

E2 Emulator 4. Functional overview

Interface voltage

When the emulator is not supplying power to the user syste m:

Voltage being supplied to the user system

inputs

Operation when a

When software tracing (LPD output) is in use:

Break or stopping of recording in internal trace memory

Condition for

outputs

Break detection
Operation when a
trigger is output

Output of a low or high pulse (for from 1 µsec to 65535 µsec) can be
specified.

TVDD voltage or any voltage between 1.8 V to 5.0 V
When the emulator is supplying power to the user system:

Conditions for
detection of trigger

trigger is input

detection of trigger

Edge detection (rising, falling, or both edges)
Level detection (low or high)

Break
When software tracing (LPD output) is not in use:

R20UT4140EJ0100 Rev.1.00 Page 20 of 37
Jul. 01, 2018

E2 Emulator 4. Functional overview

Debugging Instruction

Function

Interval between Execution of the

4-pin LPD (33 MHz)

DBCP

Outputs the current PC value as software

DBTAG imm10

Outputs a 10-bit immediate (imm10)

DBPUSH rh-rt

Outputs the register numbers and values

4.1 Software tra cing (LPD output)

Devices of the RH850 family support debugging instructions for the output of software trace data. Software trace data are
stored in the internal trace memory of the device and output to the emulato r via the LPD pins, which is the debugging­connection interface. Unlike conventional tracing, the software tracing function does not cater for the setting of events or
conditions so that trace data are o utput when the settings match the results of program execution; instead, this func t io n
helps the user to embed debugging instructions in the program to be executed as checkpoints or for the purpose of the
output of specific information or register values and output of the history execution to the emulator side as trace data.
Make use of this function as a new way of debugging. The debugger of CS+ provides useful functionality for applying
this software tra c i ng func t io n ( LP D output). For details, refer to the user’s manual and application note for CS+.

For details of the debugging instructions, refer to the RH850 User’s Manual: Debugging Instructions. Table 4-2 gives an
overview of these instructions.
When the emulator is not connected and the debugging instructions embedded in a program are executed, Software trace
data are not output from the LPD interface.

Table 4-2 Debugging Instructions for Software Tracing

Embedded Instruction and the LPD

Output (*)

trace data.

value as software trace data.
Output of the PC value is also selectable.

(General-purpose
registers are specified as
rh ≤ rt (in ascending
order).)

(*) This item indicates the time required for the LPD output of software trace data generated by executing a debugging instruction.
When this interval follows the execution of a debugging instruction, overflows (losses) of software trace data can be avoided. Even if
the debugging instruction is executed with a short interval, the device has an internal buffer for tracing and an overflow (a loss of data)
will not occur immediately; however, note that an overflow occurs if the internal buffer becomes full. For DBPUSH instruction, set the
total number of the registers to less than 5 to avoid an overflow.

of general-purpose registers from rh to rt
as software trace data.

Output of the PC value is also selectable.

1.727 usec

0.576 usec
(without the PC value)

1.727 usec

(Output one register without the PC value)

R20UT4140EJ0100 Rev.1.00 Page 21 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

5. Notes on Usage

Cautionary notes on using the E 2 emulator are given below.

5.1 General cautionary notes

5.1.1 Handling of devices which were used for debugging

Do not use devices that were used for debugging in mass-production. This is because writing to the flash memory of

such devices has already proceeded during debugging, so we cannot guarantee the number of times rewriting of the

flash memory can proceed. Debugger errors oc cur when progr amming of the flash memory is no longer possible.

Replace the device in such situations.

5.1.2 Quality of flash programming

To improve the quality, follow the guidelines below.

• Circuits are designed as described in the user's manuals for the MCU and E2 emulator.

• The MCU, E2 emulator , and the software are used as described in respective user's manuals.

• The supply of power to the user system is stable.

R20UT4140EJ0100 Rev.1.00 Page 22 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

5.2 Notes on connecting the E2 emulator

5.2.1 Entering the ID code

To start debugging after the E2 emulator has been connected, the OCDID, customer ID, and data flash ID must be
authenticated. Authentication of other ID codes may also be required (refer to section 5.4.3).
Enter the ID codes that have been set in the Security Settings area in the following order from the debugger when the
emulator is connected.

ID7 (ID[255:224]), ID6 (ID[223:192]), ID5 (ID[191:160]), ID4 (ID[159,128]),
ID3 (ID[127:96]), ID2 (ID[95:64]), ID1 (ID[63:32]), ID0 (ID[31:0])

The ID code s that have been set in the Security Settings area matching those entered from the debugger means success
in authentication, so debugging can be started.

5.2.2 Setting of the OIDDIS bit of S_OPBT0

It’s not possible to start debugging if the setting of the OIDDIS bit of S_OPBT0 is 0 (disabling ID authentication).

5.2.3 Setting of the MOSC_40MHz bit of OPBT7

Set the MOSC_40MHz bit of OPBT7 according to the input frequency of the main OSC. The ini tial value of the
MOSC_40MHz bit is 1 (40 MHz).

When the input frequency of the main OSC is 20 MH z, set the MOSC_40MHz bit to 0 (20 MHz) by the Renesas Flash
Programmer (RFP).

5.2.4 Cases where connecting the debugger is not possible

It’s not possible to start debugging if the target device is in any of the following s tate s (this also applies in cases where
hot plug-in connection i s in use).

• Reset input state (except for a reset input from the E2 emulator)

• Power shutoff standby mode

R20UT4140EJ0100 Rev.1.00 Page 23 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

5.3 Notes on differences in operation between the actual device and the emulator

5.3.1 Serial programming function

The serial programming function c annot be used with the emulator during debugging.

5.3.2 Current drawn

The target device draws more current when an emulator is connected than when it is not. That is, the target device
consumes more power while it is connected an emulator than while it is not, since the debugging circuit is operating.

5.3.3 Multiplexed pins for the debugging interface

The multiplexed pin functions for the LPD interface, which is a debugging interface, cannot be used during debugging.

5.3.4 Initialization of RAM areas

Be sure to initialize RAM fro m wit hi n the user program. If RAM is not initialized by the user program, a p rogram may

operate incorrectly when the device is not connected to the emulator but operate normally when the emulator is
connected.

If any setting is made to initialize the RAM area when the emulator is connected, the debugger initializes local RAM

and cluster RAM areas to 0000 0000H. This leads to the following differences between the cases where the emulator is
and is not connected.

- The initial values in the RAM area immediately after starting the emulator are different from the initi al values

(which are undefined) of the device.

- ECC errors due to non-initialization of the RAM are not detected with the emulator connected.

To emulate ECC errors, make the setting not to initialize the RAM ar e a when the emulator is connec t ed. However, if

the setting is for not initializing the RAM area when the emulator is connected, the following functions are not

available in the [Memory] window.

- Downloading to on-chip flash memory

- Changes to on-chip fl as h memory by using the [Memory] panel or the [Disassemble] panel

- Setting of software breaks

ECC errors occur when the RAM area is displayed in the [Memory] window before the RAM area is initialized by the

user program.

R20UT4140EJ0100 Rev.1.00 Page 24 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

5.3.5 Executing a program in the initially s to pp ed state after a reset

When a reset is applied while a debugger is connected, it forcibly releases all CPUs from their initially stopped states

and places them in the break state, regardless of whether the debugger is i n the synchronous deb ugging mode or

asynchronous debugging mode. If a program is executed in this state, note that the target device may not operate

normally.

Using the [Debug initial stop state] property (for CS+) and the FETCHSTOP command (for MULTI ) enables

execution of a program with the CPUs in the initially stopped state. For deta ils of the procedure, refer to the user’s

manual for the debugger.

5.3.6 Setting the STMSEL1 bit of OPBT3

When STMSEL1 is set to 1 and the emulator is not connected (TRST = low), the device enters the serial programming

mode. When the emulator is connected (TRST = high), the device enters the normal operating mode or user boot mode

(for details, refer to the user’s manual for the target device). When STMSEL1 is set to 1 and the E2 emulator is not

connected, the device enters the serial programming mode and does not start execution of the user program.

5.3.7 Power off standby mode

The E2 emulator does not support emulation of power off standby. Check the operation of the power shutoff standby

when the emulator is not connected.

5.3.8 BIST

BIST is skipped when the emul ator is connected (TRST = high).

5.3.9 Reading registers with undefined initial values and an ECM error

Reading a register with undefined initial values, such as the EIPC and general-purpose registers when they have not
been initialized, leads to different values being read by the master CPU and checker CPU, which is detected as an error
by the error control module (ECM).

After the debugger is started (exclusive of the case of a hot plug-in connection), the debugger internally initializes the
EIPC and general-purpose registers. Thus , if you have forgotten to initialize these registers in the user program, there is
a difference between the connected and non-connected states in that an ECM error does not occur when the emulator is
connected but does occur when the emulator is not connected.
Be sure to initialize and read registers with undefined initial values in the user program.

The debugge r saves the EI PC and general-purpose registers whenever a break occurs and restores the saved values
before execution of the user program is restarted. If a break occurs when these registers have not been initialized, an
ECM error will occur due to processing for saving by the debugger .

R20UT4140EJ0100 Rev.1.00 Page 25 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

5.4 Cautionary notes on debugging

5.4.1 Power to the target system while debugging

Do not turn t he power to the target system off during debugging. Doing so will require reconnection of the debugger.

5.4.2 OTP flag

Do not set the one-time programming (OTP) flag i n self-programming with the emulator. Setting the fl ag makes further
debugging impossible.
The OTP flag cannot be set in downloading by the debugger. Note that downloading is suspended if the file to be
downloaded includes the OTP setting. We recommend that files to be downloaded are divided into those for the area
for setting OTP and for other areas.

5.4.3 Authenticating and downloading ID code

When the debugger is started, it is p ossible to authenticate IDs other than the OCDID, customer ID, and data flash ID,
however, authentication of such IDs is invalidated by a user-system reset and a debugger reset. Be sure to access areas
protected by these IDs (in terms o f downloading to flash m emor y and reading memory) before issuing a reset after the
debugger is started.
In case of downloading to areas including those protected by such IDs after a reset has been issued so tha t
authentication of the IDs has been invalidated, note t hat progra mmi ng of the protected areas will fai l and subsequent
downloading to the protected areas is suspended. We recommend that files to be downloaded are divided into those for
the areas protected by IDs and for other areas.

5.4.4 Downloading to Configuration Setting, Security Settings, and Block Protection areas

Downloading to Configuration Setting, Security Settings, and Block Protection areas from the debugger is possible.
However, after downloading to these areas, continued debugging is not possible. Disconnect and re-connect the
emulator on the debugger.
We recommend that files to be downloaded are divided into those for these areas and for the user, user boot, data flash,
and extended data areas.

5.4.5 Modifying the PEx_DISABLE bit of OPBT3

Do not modify the PEx_DISABLE bit of OPBT3 by self-programming d uring execution of a user program. The

debugger cannot keep track of the number of cores in operation if this is dynamically altered. If PE x_DISABLE is

modified, the debugger cannot continue debugging and must be re-connected.

5.4.6 Debugging for Code flash (Mirror) area

Instruction execution on Code flash (mirror) area is not supported.

5.4.7 Event detection

Data in access by the FXU instruction cannot be compared as an access event.
Write access that has been suppressed in response t o an STC instruction failing and read/write access which has been

R20UT4140EJ0100 Rev.1.00 Page 26 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

suppressed in response to the inhibition of MDP exceptions may be detected when an access event is set without data
comparison but not detected when an access event is set with data comparison.

5.4.8 The order of event detection

In the following cases, since the orders of inst ructions and event dete ction may not oper ate as set, to measure the time

or performance in sequential events, section tracing, and desired sections may not be possible.

• Adjacent read and write instructions may be detected as a single access event since multiple instructions are executed
at the same time and the timing of event detection differs in write and read access events which are set for consecutive
instructions. The timing may b e detected in the order of reading then writing, even thou gh the instructions are executed
in the order of writing then reading.

• Access events may be detected at the same time since LRAM and CRAM can be accessed simultaneously and up to
four access events are detectable.

5.4.9 Access trace function

The following restrictions app ly to access to trace data.

- When tracing is performed with an access-type point or a range event, data comparison conditions are always

ignored regardless of whether or not such conditions have been set and access in which any condition except for a
data comparison condition is detected is traced.

- In case of access to data by the FXU instruction, the data cannot be traced.

- Write access which has been suppressed in response to an STC instruction failing and read/write access which has

been suppressed in response to the inhibition of MDP exceptions may not be traced.

5.4.10 Losing trace information

In some cases, acq uire d trace information will be lost (trace overflow). This depends on the program being executed.
The lost information cannot be r e stored, but the fact of the loss is indicated (displayed).

5.4.11 Recording trace memory during non-realtime tracing

When priority in tracing is given to non-realtime operation, the functions to stop tracing when the trace memory
becomes full (trace-full stop function) and when a specified number of trace messages have been acquired following an
event (trace delay-stop function) are not available. T o use these functions, give priority to realti me operation.

5.4.12 Performance measurement

In the case of measuri ng a specific section, if the intervals between the start and the end of one measurement, and
between the end of that measurement and the start of the next is s hort, the meas urement is not possible. To obtain
correct measurements, the interval* should be long e nough.
*: The required detection interval depends on the operating fr equency and the LPD communications frequency of the
MCU.

R20UT4140EJ0100 Rev.1.00 Page 27 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

State of a device

In breaks

In single stepping

In user program

In C-source-level

Reset mask

Resets not

Resets masked

Resets not

Depends on the

Resets

Resets masked

5.4.13 Stepped execution of the HALT mode and the HALT instruction

A break leads to release from HALT mode.
When a HALT instruction is encountered during single step execution (execution in units of assembly instruct ion), a
break is set a t the next instruction following th e HALT instruction, and the mode does not change to the HALT mode.
When a HALT instruction is encountered during C-source-level stepped execution, whether or not the transition to the
HALT mode proceeds depends on the facilities of the debugger.

5.4.14 Masking of resets while the emulator is in use

Table 5-1, State of a Device and Masking of Resets, shows the state of a device while the emulator is in use and the
operation of resets issued by the user system or the user p rogram (i.e. use r system reset). During single stepping, resets
are masked to emulate each step in the source code of the program in non-realtime. In C-source-level stepping, resets
are masked in di fferent wa ys depending on the debugger; one method is to use single stepping and another is to set an
internal breakpoint and execute the user program. Accordingly, this document cannot define enabling and disabling of
reset masking per debugge r; refer to the manual for the debugger you are using.

Table 5-1 State of a Device and Masking of Resets

specification
on the
debugger

masked

masked

execution

masked

stepping

debugger

- When a reset is issued by a debugger (by pressing the reset button of the debugger or in some other way), the reset

is always enabled regardless of enabling or disabling of reset masking. After a reset is issued by the debugger,
breaks are generated for all CPUs.

- Do not issue a pin reset from the user system, regardless of the presence or absence of masking, other than in cases

where a user program is running.

- The software reset might not be generated when execution resumes following a break that occurs before a software

reset instruction

R20UT4140EJ0100 Rev.1.00 Page 28 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

State of a device

In breaks

In single stepping

In user program execution

In C-source-level stepping

Interrupt masked*

Interrupt masking disabled

Depends on the debugger

5.4.15 Masking of interrupts while the emulator is in use

Table 5-2, State of a Device and Masking of Interrupts, shows the states of a device while the emulator is in use and the
operation of interrupts (EIINT, FEINT, or FENMI). During single stepping, interrupts are masked to emulate each line
of source code of the program in non-realtime. When interrupt processing is to be stepped through, set a breakpoint at
the beginni ng of the inte rrupt processing, generate an interrupt dur ing execution of the user program. A break will then
be generated at the beginning of the interrupt processing. In C-source-level stepping, resets are masked in different
ways depending on the debugger; one method is to use single stepping and another is to set a temporary breakpoint and
execute the user program. Accordingly, this document cannot define enabling and disabling of reset masking per
debugger; r efer to the manual for the debugger you are using.

Table 5-2 State of a Device and Masking of Interrupts

(operation according to the
specification of the user system)

- An interrupt generated in the state marked (*) in Table 5-2 is kept pending and interrupt processing proceeds after

interrupt masking is canceled.

5.4.16 Rewriting of on-chip flash memory (working RAM)

When the debugger performs any operation that involves programming of the flash memory* during a break, part of the
internal RAM area is used as a working RAM area. The 4-KB area from the last address of the local RAM (self) area of
CPU0 are initially set as the working RAM area.

The debugger can change the working RAM area. After the debugger has saved the value s from the working RAM area
and rewrites the flash memory, it restores the saved values to the working RAM area. To guarantee the values, it is
required to set an area to which there will be no access by the DMAC or any external master to the working RAM area
so that operation may continue even if the device enters the break state.

Note: Rewriting of flash memory proceeds in response to any of the operations below.

• Downloading to on-chip flash me mory

• Changes to on-chip flash memory by using the [Memory] panel or the [Disassemble] panel

• Setting or cancellation of software breaks

• Re-execution after a software break is encountered (including stepped execution)

R20UT4140EJ0100 Rev.1.00 Page 29 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

5.4.17 Rewriting of on-chip flash memory (modifying the clock settings)

The debugge r temporarily changes t he clock settings (the PLL is selecte d with no frequency division) to improve the
speed of processing while the flash memory is being rewritten* and restores the previous clock settings after this
processing.

If the change in the clock frequency due to the debugger causes a problem, e.g. the frequency surpasses the upper limit
which was set by the clock monitor (CL MA), stop the modification of clock settings by using the setting of the [Change
the clock to flash writing] property (for CS+) or the FLASHCLOCK command or the -noflashclock option (for
MULTI).

Note: Rewriting of flash memory proceeds in response to any of the operations below.

• Downloading to on-chip flash me mory

• Changes to on-chip flash memory by using the [Memory] panel or the [Disassemble] panel

• Setting or cancellation of software breaks

• Re-execution after a software break is encountered (including stepped execution)

5.4.18 Breaks during execution of code for making clock settings

The flash memory cannot be programmed if a break occurs while the MCU is running code written to memory for
making clock settings (setting of the main oscillator or PLL frequency divider and so on).
If you wish e i ther of the following types of operation to proceed when a break has occurred during clock settings, set
[Change the clock to flash writing] in the [Property] panel to [No].

a. Any operation that i nvolves programming of the flash memory (e.g. re-downloading)
b. Setting or deleting software breakpoints

Also, do not set software breakpoints within code for making clock settings.

5.4.19 Software break functions (RAM areas)

The software break function is implemented by replacing instructions. Thus, note that no break will occur if the value
at an address where a software break has been set is rewritten by a user pr ogram which is running. A b reak will also not
occur if a reset is generated during the execution o f a user program, since RAM areas may b e initialized by hardware
with certain settings.

5.4.20 Cases where no break occurs

No breaks occur when the CPU is in any of states listed below.

- Initially stopped state

- Reset state

5.4.21 Cautionary points on synchronous debugg ing mode

In the synchronous debugging mode, a break may occur for all CPUs. However, if any of CPUs is in the initially
stopped state, note that no break will occ ur. A breakpoint must be set in the program at a point after all CPUs have
been released from the initially stopped state. If you want to generate a break earlier than this, use the asynchronous
debugging mode.

R20UT4140EJ0100 Rev.1.00 Page 30 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

5.4.22 Cautionary points on asynchronous debugging mode

- In the asynchronous debugging mode, peripheral break functions cannot be used. Even if peripheral break

functions are enabled, peripheral functions are not stopped.

- In the asynchronous debugging mode , when any of CPUs is in the break state, no user system resets are acceptable.

- During exec ution of a user program, there may be a case that the ECC error function does not normally operate for

flas h m emor y.

Example: When any CPU accesses flash memory during execution of a user program causing an ECC error and
another CPU which is in the break state accesses the same resources in the memory window at the same timing,
the debugger temporarily controls the ECC error and no ECC error occurs in any CPU.

5.4.23 Cautionary points regarding trace data acquired by software tracing (LPD output)

- When the software tracing (LPD output) is in use, acces s to memor y during the execution of a program,

changes to event conditions, the reading of internal trace memory, and the display of state indicato rs suc h as
STOP are disabled.

A timestamp indicates the time that the E2 emulator acquires the software tracing data, not the time the

-

instruction in the so ftware being debugged was executed. The E2 emulator requires execution of the program
by the MCU to start only after it has started counting its timestamp values. Since the start of counting of
timestamp values cannot be precisely synchroni ze d with the start of program execution, the timestamps which
have been added to the software tracing data stored from the head of the E2 storage may include some errors.

- When a break is generated as a forced break, a trace-full break from t he E2 storage, or a break d ue to the input

of an external trigger, information from a debugging instruction that was executed immediately before the
break will not be stored in the E2 storage.

- When a debugging instruc tion is executed during single-stepped execution and a software break or hardware

break is specified and executed by the debugging instruction, software trace data are not output through the
LPD interface.

- When trace acquisition is stopped due to a break generated by a software break, hardware break, event break,

or trace-full break from internal trace memory, the history of execution from a DBCP instruction executed in
the debugging area is stored as the final trace data in the E2 storage and internal trace memory after the break
in execution.

R20UT4140EJ0100 Rev.1.00 Page 31 of 37
Jul. 01, 2018

E2 Emulator 5. Notes on Usage

5.4.24 Cautionary points regarding external trigger input/output

- When external t rigger input or external tr igger outp ut functions a re in use, access to memory during the

execution o f a program, changes to event conditions, the reading of internal trace memory, and the display of
state indicators such as STOP are disabled.

- When the software tracing (LPD output) function is not in use, breaks are not detectable during the 10-µsec

period after a program has started to run.

R20UT4140EJ0100 Rev.1.00 Page 32 of 37
Jul. 01, 2018

E2 Emulator 6. Internal Circuit of the Emulator

Emulator

control

circuit

74LVC1T45

74LVC1T45

74LVC1T45

74LVC1T45

74LVC8T245

74LVC1T45

74LVC1T45

74LVC8T245

74LVC1T45

NFL21SP

Noise filter

47 Ω

1 MΩ x 6

3.3 V

47 Ω

47 Ω

47 Ω

47 Ω

NFL21SP

Noise filter

47 Ω

3.3 V

100 kΩ

Self-recovering

fuse

8 TVDD

1 LPDCLK

5 LPDO

3 TRST

9 

11 LPDCLKO

4 FPMD0

7 LPDI/FPDR

10 

14 GND

13 RESET

2,12 GND

6 

74LVC8T245

47 Ω

1 MΩ

14-pin connect or

47 Ω

NFL21SP

Noise filter

3 MΩ x 2

100

kΩ

0.1 μF

74LVC1T45

20-pin connect or

1

4

16

6

2

12
18

8

20

9

10

14

3,5,15,
17,19

3

1

SW is on 1 side.

6. Internal Circuit of the Emulator

The internal interface circuit related to the communications interface between the E2 emulator and user sys tem is shown
in figure A below. Please refer to the figure when determining parameters in board design.

Figure A Interface Circuits in the E2 Emulator (4-Pin LPD, 2-Wire UART, CSI)

R20UT4140EJ0100 Rev.1.00 Page 33 of 37
Jul. 01, 2018

Page

Summary

1.00

Jul. 01, 2018

First Edition issued

Revision History

E2 Emulator Additi o nal Document for User's Manual

(Notes on Connection of RH850/E2x series)

Rev. Date Description



Jul. 01,2018

Renesas Electronics Corporation

E2 Emulator

Additional Document for User's Manual (Notes on Connection of RH850/E2x series)

Publication Date:

Rev.1.00

Published by:

http://www.renesas.com

Refer to "http://www.renesas.com/" for the latest and detailed information.

Renesas Electronics America Inc.

1001 Murphy Ranch Road, Milpitas, CA 95035, U.S.A.
Tel: [phone], Fax: [phone]

Renesas Electronics Canada Limited

9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3
Tel: [phone]

Renesas Electronics Europe Limited

Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K
Tel: [phone], Fax: [phone]

Renesas Electronics Europe GmbH

Arcadiastrasse 10, 40472 Düsseldorf, Germany
Tel: [phone], Fax: [phone]

Renesas Electronics (China) Co., Ltd.

Room 1709 Quantum Plaza, No.27 ZhichunLu, Haidian District, Beijing, 100191 P. R. China
Tel: [phone], Fax: [phone]

Renesas Electronics (Shanghai) Co., Ltd.

Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, 200333 P. R. China
Tel: [phone], Fax: [phone]

Renesas Electronics Hong Kong Limited

Unit 1601-1611, 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong
Tel: [phone], Fax: [phone]

Renesas Electronics Taiwan Co., Ltd.

13F, No. 363, Fu Shing North Road, Taipei 10543, Taiwan
Tel: [phone], Fax: [phone]

Renesas Electronics Singapore Pte. Ltd.

80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore 339949
Tel: [phone], Fax: [phone]

Renesas Electronics Malaysia Sdn.Bhd.

Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, 46050 Petaling Jaya, Selangor Darul Ehsan, Malaysia
Tel: [phone], Fax: [phone]

Renesas Electronics India Pvt. Ltd.

No.777C, 100 Feet Road, HAL 2nd Stage, Indiranagar, Bangalore 560 038, India
Tel: [phone], Fax: [phone]

Renesas Electronics Korea Co., Ltd.

17F, KAMCO Yangjae Tower, 262, Gangnam-daero, Gangnam-gu, Seoul, 06265 Korea
Tel: [phone], Fax: [phone]

SALES OFFICES

© 2018 Renesas Electronics Corporation. All rights reserved.

Colophon 5.0

R20UT4140EJ0100

E2 Emulator

Additional Docum ent for User’s Manu al

(Notes on Connection of RH850/E2x series)