EZ-CUBE On-Chip Debug Emulator with Programming Function

EZ-CUBE
On-Chip Debug Emulator with Programming
Function
Renesas Electronics (China)
www.cn.renesas.com
Rev.2.00 May 2012

Notice
1. All information included in this document is current as of the date this document is issued. Such information, however,
is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein,
please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful
attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our
website.
2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property
rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this
document.
No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property
rights of Renesas Electronics or others.
3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or
in part.
4. 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 of these
circuits, software, and information in the design of your equipment. Renesas Electronics assumes no responsibility for any
losses incurred by you or third parties arising from the use of these circuits, software, or information.
5. When exporting the products or technology described in this document, you should comply with the applicable export
control laws and regulations and follow the procedures required by such laws and regulations. You should not use
Renesas Electronics products or the technology described in this document for any purpose relating to military
applications or use by the military, including but not limited to the development of weapons of mass destruction. Renesas
Electronics products and technology may not be used for or incorporated into any products or systems whose
manufacture, use, or sale is prohibited under any applicable domestic or foreign laws or regulations.
6. Renesas Electronics has used reasonable care in preparing the information included in this document, but Renesas
Electronics does not warrant that such information is error free. Renesas Electronics assumes no liability whatsoever for
any damages incurred by you resulting from errors in or omissions from the information included herein.
7. Renesas Electronics products are classified according to the following three quality grades: “Standard”, “High Quality”,
and “Specific”. The recommended applications for each Renesas Electronics product depends on the product’s quality
grade, as indicated below. You must check the quality grade of each Renesas Electronics product before using it in a
particular application. You may not use any Renesas Electronics product for any application categorized as “Specific”
without the prior written consent of Renesas Electronics. Further, you may not use any Renesas Electronics product for
any application for which it is not intended without the prior written consent of Renesas Electronics. Renesas Electronics
shall not be in any way liable for any damages or losses incurred by you or third parties arising from the use of any
Renesas Electronics product for an application categorized as “Specific” or for which the product is not intended where
you have failed to obtain the prior written consent of Renesas Electronics. The quality grade of each Renesas Electronics
product is “Standard” unless otherwise expressly specified in a Renesas Electronics data sheets or data books, etc.
“Standard”: Computers; office equipment; communications equipment; test and measurement equipment; audio
and visual equipment; home electronic appliances; machine tools; personal electronic equipment; and
industrial robots.
“High Quality”: Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems;
anticrime systems; safety equipment; and medical equipment not specifically designed for life support.
“Specific”: Aircraft; aerospace equipment; submersible repeaters; nuclear reactor control systems; medical
equipment or systems for life support (e.g. artificial life support devices or systems), surgical implantations,
or healthcare intervention (e.g. excision, etc.), and any other applications or purposes that pose a direct
threat to human life.
8. You should use the Renesas Electronics products described in this document within the range specified by Renesas
Electronics, especially with respect to the maximum rating, operating supply voltage range, movement power voltage
range, heat radiation characteristics, installation and other product characteristics. Renesas Electronics shall have no
liability for malfunctions or damages arising out of the use of Renesas Electronics products beyond such specified ranges.
9. Although Renesas Electronics endeavors to improve the quality and reliability of its products, semiconductor products
have specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use
conditions. Further, Renesas Electronics products are not subject to radiation resistance design. Please be sure to
implement safety measures to guard them against the possibility of physical injury, and injury or damage caused by fire in
the event of the failure of a Renesas Electronics product, 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, please evaluate the
safety of the final products or system 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. Please use Renesas Electronics products in compliance with all
applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the
EU RoHS Directive. Renesas Electronics assumes no liability for damages or losses occurring as a result of your
noncompliance with applicable laws and regulations.
11. This document may not be reproduced or duplicated, in any form, in whole or in part, without prior written consent of
Renesas Electronics.
12. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in
this document or Renesas Electronics products, or if you have any other inquiries.
(Note 1) “Renesas Electronics” as used in this document means Renesas Electronics Corporation and also includes its
majorityowned subsidiaries.
(Note 2) “Renesas Electronics product(s)” means any product developed or manufactured by or for Renesas Electronics.
User’s Manual

Preface
The EZ-CUBE emulator (YRCNEZCUBE01) is designed for use with the MCU’s made by Renesas Electronics.
You can download the latest manuals from the Renesas Tools homepage (http://www.cn.renesas.com/tool).
Important
Before using the emulator, be sure to read this user’s manual carefully. Keep this user’s manual, and refer to it when
you have questions about the emulator.
Emulator:
"Emulator" in this user’s manual collectively refers to the EZ-CUBE emulator manufactured by Renesas Electronics
Corporation.
"Emulator" herein encompasses neither the customer's user system nor the host machine.
Purpose of use of the emulator:
This emulator is a device to support the development of systems that uses the Renesas microcomputers. It provides
support for system development in both software and hardware. The emulator is not guaranteed for use in the
production line. Be sure to use the emulator correctly according to said purpose of use. Please avoid using the
emulator other than for its intended purpose of use.
For those who use the emulator:
The emulator can only be used by those who have carefully read the user’s manual and know how to use it.
Use of the emulator requires basic knowledge of electric circuits, logical circuits, and MCUs.
When using the emulator:
(1)The emulator is a development-support unit for use in your program development and evaluation stages. When a
program you have finished developing is to be incorporated in a mass-produced product, the judgment as to
whether it can be put to practical use is entirely your own responsibility, and should be based on evaluation of the
device on which it is installed and other experiments.
(2)In no event shall Renesas Electronics Corporation be liable for any consequence arising from the use of the
emulator.
(3)Renesas Electronics Corporation strives to provide workarounds for and correct trouble with products malfunctions.
However, this does not necessarily mean that Renesas Electronics Corporation guarantees the provision of a
workaround or correction under any circumstances.
(4)The emulator covered by this document has been developed on the assumption that it will be used for program
development and evaluation in laboratories.
(5)Renesas Electronics Corporation cannot predict all possible situations and possible cases of misuse that carry a
potential for danger. Therefore, the warnings in this user's manual and the warning labels attached to the emulator
do not necessarily cover all such possible situations and cases. The customer is responsible for correctly and
safely using the emulator.
(6)Renesas Electronics Corporation will not assume responsibility of direct or indirect damage caused by an
accidental failure or malfunction in the emulator.
When disposing of the emulator:
Penalties may be applicable for incorrect disposal of this waste, in accordance with your national legislation.
Usage restrictions:
The emulator has been developed as a means of supporting system development by users. Therefore, do not use it
as an embedded device in other equipment. Also, do not use it to develop systems or equipment for use in the
User’s Manual

following fields.
(1) Transportation and vehicular
(2) Medical (equipment that has an involvement in human life)
(3) Aerospace
(4) Nuclear power control
(5) Undersea repeaters
(6) Military related business or development of Weapon of Mass Destruction
About product changes:
We are constantly making efforts to improve the design and performance of our product. Therefore, the specification
or design of the emulator, or this user's manual, may be changed without prior notice.
About rights:
(1) We assume no responsibility for any damage or infringement on patent rights or any other rights arising from the
use of any information, products or circuits presented in this user’s manual.
(2) The information or data in this user’s manual does not implicitly or otherwise grant a license to patent rights or any
other rights belonging to Renesas or to a third party.
(3) This user’s manual and the emulator are copyrighted, with all rights reserved by Renesas. This user’s manual may
not be copied, duplicated or reproduced, in whole or part, without prior written consent from Renesas.
About diagrams:
Some diagrams in this user’s manual may differ from the objects they represent.
Terminology
The meanings of the terms used in this manual are described in the table below.
Term Meaning
EZ-CUBE Generic name of EZ-CUBE
Target device This is the device to be emulated.
Target system This is the system to be debugged (user-created system).
It includes software and hardware created by the user.
CubeSuite+ for It is an integrated development environment (China Version).
China
Firmware Program embedded in the device for controlling EZ-CUBE
RFP Renesas Flash Programmer, GUI software used to perform flash
programming.
WriteEZ5 GUI software used to perform flash programming
User’s Manual

CAUTION
Caution to Be Taken for System Malfunctions:
If the emulator malfunctions because of interference like external noise, do the following to remedy the trouble.
(1) Exit the emulator debugger, and shut OFF the emulator and the user system.
(2) After a lapse of 10 seconds, turn ON the power of the emulator and the user system again, then launch the
emulator debugger.
Note
Renesas Electronics (China) does not assume any liability for the user does not follow the user manual for the use of
non-normal and non-practice due to loss of product failure and other related.
User’s Manual

CONTENTS
CHAPTER 1 OVERVIEW..........................................................................................7
1.1 Features .............................................................................................................................. 7
1.2 Notes Before Using EZ-CUBE ............................................................................................ 8
1.3 Hardware Specifications...................................................................................................... 9
1.4 Firmware Update ................................................................................................................. 9
1.5 Standard configuration ...................................................................................................... 10
CHAPTER 2 NAMES AND FUNCTIONS OF HARDWARE ...................................11
2.1 Part Names and Functions of EZ-CUBE........................................................................... 11
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER ..........14
3.1 Target System Design .............................................................................................................. 15
3.1.1 Pin assignment............................................................................................................. 15
3.1.2 Circuit connection examples ........................................................................................ 16
3.1.3 Connection of reset pin ................................................................................................ 18
3.1.4 Cautions on target system design................................................................................ 19
3.1.5 Mounting connector onto target system....................................................................... 20
3.2 On-Chip Debugging .................................................................................................................. 21
3.2.1 Debug functions ........................................................................................................... 21
3.2.2 System configuration.................................................................................................... 22
3.2.3 System startup procedure............................................................................................ 23
3.2.4 System shutdown procedure ....................................................................................... 24
3.2.5 Clock setting................................................................................................................. 24
3.2.6 Securing of user resources and setting of security ID ................................................. 25
3.3 Flash Programming ........................................................................................................... 32
3.3.1 Specifications of programming function....................................................................... 32
3.3.2 System configuration.................................................................................................... 32
3.3.3 System startup procedure............................................................................................ 33
3.3.4 Usage examples .......................................................................................................... 34
3.3.5 System shutdown procedure ....................................................................................... 39
3.3.6 Cautions on flash programming ................................................................................... 39
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER .........40
4.1 Target System Design .............................................................................................................. 41
4.1.1 Pin assignment............................................................................................................. 42
4.1.2 Circuit connection example.......................................................................................... 43
4.1.3 Connection of reset pin ................................................................................................ 44
4.1.4 Mounting connector onto target system....................................................................... 44
4.2 On-Chip Debugging .................................................................................................................. 45
4.2.1 Debug functions ........................................................................................................... 45
User’s Manual

4.2.2 System configuration ....................................................................................................46
4.2.3 System startup procedure.............................................................................................47
4.2.4 System shutdown procedure ........................................................................................48
4.2.5 Securing of user resources and setting of security ID and on-chip debug option byte 49
4.2.6 Cautions on debugging.................................................................................................53
4.3 Flash Programming .................................................................................................................54
4.3.1 Specifications of programming function........................................................................54
4.3.2 System configuration ....................................................................................................54
4.3.3 System startup procedure.............................................................................................55
4.3.4 Usage examples ...........................................................................................................56
4.3.5 System shutdown procedure ........................................................................................60
4.3.6 Cautions on flash programming....................................................................................60
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER............. 61
5.1 Target System Design...............................................................................................................62
5.1.1 Pin assignment .............................................................................................................63
5.1.2 Circuit connection example...........................................................................................64
5.1.3 Connection of pin..........................................................................................................64
5.1.4 Mounting connector onto target system .......................................................................65
5.2 On-Chip Debugging...................................................................................................................66
5.2.1 Debug functions............................................................................................................66
5.2.2 System configuration ....................................................................................................67
5.2.3 System startup procedure.............................................................................................68
5.2.4 System shutdown procedure ........................................................................................69
5.2.5 Notes on Using the EZ-CUBE Emulator.....................................................................69
5.3 Flash Programming ...................................................................................................................80
5.3.1 Specifications of programming function........................................................................80
5.3.2 System configuration ....................................................................................................80
5.3.3 System startup procedure.............................................................................................81
5.3.4 Usage examples ...........................................................................................................82
5.3.5 System shutdown procedure ........................................................................................87
5.3.6 Cautions on flash programming....................................................................................87
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER ........... 88
6.1 Target System Design...............................................................................................................89
6.1.1 Pin assignment .............................................................................................................89
6.1.2 Circuit connection example...........................................................................................90
6.1.3 Connection of reset pin.................................................................................................91
6.1.4 Mounting connector onto target system .......................................................................92
6.2 On-Chip Debugging...................................................................................................................93
6.2.1 Debug functions............................................................................................................93
6.2.2 System configuration ....................................................................................................93
6.2.3 System startup procedure.............................................................................................94
6.2.4 System shutdown procedure ........................................................................................96
6.2.5 Securing of user resources and setting of security ID and on-chip debug option byte 97
6.2.6 Cautions on debugging...............................................................................................101
User’s Manual

6.3 Flash Programming............................................................................................................... 102
6.3.1 Specifications of programming function..................................................................... 102
6.3.2 System configuration.................................................................................................. 102
6.3.3 System startup procedure.......................................................................................... 103
6.3.4 Usage examples ........................................................................................................ 104
6.3.5 System shutdown procedure ..................................................................................... 109
6.3.6 Cautions on flash programming ................................................................................. 109
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER .....110
7.1 Target System Design..................................................................................................... 111
7.1.1 Pin assignment........................................................................................................... 111
7.1.2 Circuit connection examples ...................................................................................... 112
7.1.3 Connection of reset pin .............................................................................................. 113
7.1.4 Mounting connector onto target system..................................................................... 114
7.2 On-Chip Debugging ................................................................................................................ 115
7.2.1 Debug functions ......................................................................................................... 115
7.2.2 System configuration.................................................................................................. 115
7.2.3 System startup procedure.......................................................................................... 116
7.2.4 System shutdown procedure ..................................................................................... 117
7.2.5 Securing of user resources and setting of security ID ............................................... 118
7.2.6 Cautions on debugging .............................................................................................. 123
7.3 Flash Programming ......................................................................................................... 124
7.3.1 Specifications of programming function..................................................................... 124
7.3.2 System configuration.................................................................................................. 124
7.3.3 System startup procedure.......................................................................................... 125
7.3.4 Usage examples ........................................................................................................ 126
7.3.5 System shutdown procedure ..................................................................................... 131
7.3.6 Cautions on flash programming ................................................................................. 131
User’s Manual

CHAPTER 1 OVERVIEW
CHAPTER 1 OVERVIEW
EZ-CUBE is an on-chip debug emulator with flash programming function, which is used for debugging and
programming a program to be embedded in on-chip flash memory microcontrollers.
1.1 Features
• On-chip debugging
Can debug with the target microcontroller connected to the target system.
• Flash memory programming
Can write programs to the on-chip flash memory of microcontrollers.
• USB connection
Can be connected to the host machine via USB interface 2.0.
Since EZ-CUBE operates on power supplied via USB, an external power supply is unnecessary.
• Variety of supported devices and expandability
EZ-CUBE supports a wide variety of Renesas Electronics 8- bit to 32-bit on-chip flash memory
microcontrollers.
- 78K0 Microcontrollers
- 78K0R Microcontrollers
- R8C Microcontrollers
- RL78 Microcontrollers
- V850 Microcontrollers
User’s Manual 7

1.2 Notes Before Using EZ-CUBE
78K0
78K0R
R8C
RL78
V850
CHAPTER 1 OVERVIEW
Chapters 1 and 2 present an overview and the basic specifications of EZ-CUBE, and the following chapters
provide separate descriptions for the target devices and the purpose of use. To utilize this manual effectively,
refer to the following table and see the relevant chapter for your target device and purpose of use.
Table 1-1. Chapters Corresponding to Usage
Target Device Purpose of Use Relevant Chapter
CHAPTER 3 HOW TO USE EZ-CUBE WITH
78K0 MICROCONTROLLER
Target system design 3.1 Target System Design
On-chip debugging 3.2 On-Chip Debugging
Flash memory programming 3.3 Flash Programming
CHAPTER 4 HOW TO USE EZ-CUBE WITH
78K0R MICROCONTROLLER
Target system design 4.1 Target System Design
On-chip debugging 4.2 On-Chip Debugging
Flash memory programming 4.3 Flash Programming
CHAPTER 5 HOW TO USE EZ-CUBE WITH
R8C MICROCONTROLLER
Target system design 5.1 Target System Design
On-chip debugging 5.2 On-Chip Debugging
Flash memory programming 5.3 Flash Programming
CHAPTER 6 HOW TO USE EZ-CUBE WITH
RL78 MICROCONTROLLER
Target system design 6.1 Target System Design
On-chip debugging 6.2 On-Chip Debugging
Flash memory programming 6.3 Flash Programming
CHAPTER 7 HOW TO USE EZ-CUBE WITH
V850 MICROCONTROLLER
Target system design 7.1 Target System Design
On-chip debugging 7.2 On-Chip Debugging
Flash memory programming 7.3 Flash Programming
User’s Manual 8

1.3 Hardware Specifications
CHAPTER 1 OVERVIEW
This section describes the EZ-CUBE hardware specifications.
The specifications related to the on-chip debug and flash memory programming functions are described in the
following chapters.
EZ-CUBE
Table 1-2. Hardware Specifications
Classification Item Specifications
Host machine interface
Target interface
Operating power supply Supplied via USB interface (5 V)
Operating environment
conditions
Storage environment
conditions
Temperature: ±0 to +40°C
Humidity: 40 to 80% RH (no condensation)
Temperature: -15 to +60°C
External dimensions 59 × 35 × 13 mm
Weight Approximately 40 g
Humidity: 40 to 80% RH (no condensation)
Target host machine IBM PC/AT TM compatibles
Target OS Windows XP, Vista, Windows 7 Note
USB 2.0
USB cable 1 m
Note: WriteEZ5 does not support Windows 7.
1.4 Firmware Update
Current consumption 500 mA max.
Target cable length 8-pin cable
Supply voltage 5.0 V±0.3V (typ.)
Supply current 100 mA max.
Voltage range 2.7 to 5.5 V
(1) Installation of the USB driver
This USB driver is required to connect the host machine and EZ-CUBE. Download it from the CD. Please
install this USB driver at first.
(2) Connecting the USB cable
Connect EZ-CUBE to the host machine. Do not connect EZ-CUBE to the target system. The mode LED
glows red after connection.
(3) Startup of EZ-CUBE firmware update tool
Start the EZ-CUBE firmware update tool (QBEZUTL.exe).
User’s Manual 9

CHAPTER 1 OVERVIEW
(4) Select firmware
Click the […] button. Select firmware of EZ-CUBE (*.hex) and click the [OK] button.
(5) Update firmware
Click the [Start] button. Start to update the EZ-CUBE firmware. If firmware update is finished, the following
dialog box appears.
(6) Quit EZ-CUBE firmware update tool
Click the [Exit] button. Quit EZ-CUBE firmware update tool.
(7) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
1.5 Standard configuration
EZ-CUBE, USB cable, target cable and CD.
User’s Manual 10

CHAPTER 2 NAMES AND FUNCTIONS OF HARDWARE
This chapter describes the part names and functions of EZ-CUBE and its accessories.
The part names described in this chapter are used throughout this document. This chapter provides an
overview of the various functions. Reading it through, the reader will gain a basic grasp of EZ-CUBE. While
reading this chapter, also check if the hardware has a defect.
2.1 Part Names and Functions of EZ-CUBE
Figure 2-1 shows the part names of the EZ-CUBE main unit. For their functions, refer to (1) to (9) below.
Target
interface
connector
Mode LED
SW switch
Figure 2-1. Part Names of EZ-CUBE
External X'tal socket
USB interface
connector
(1) SW-1 switch
The position of this switch depends on the target devices. The detail describes, please see the follow chapter.
This switch is set to ″M2″ at shipment.
(2) SW-2 switch
This switch is used to set clock. Table 2-1 describes the setting details. This switch is set to ″Int. Clock″ at
shipment.
Table 2-1. Setting of Clock Select Switch
Setting Description
Int. Clock
Ext. Clock
When this SW-2 is turned to Int. Clock position, 8MHz fixed freq. is to be supplied to
the target board.
If the other freq. is required, it should be turned to Ext. Clock position (Ext. X'tal
should be connected in this case).
(3) SW-3 switch
This switch is used to set run mode of program. Table 2-2 describes the setting details. This switch is set to
″ Debug Mode ″ at shipment.
User’s Manual 11

CHAPTER 2 NAMES AND FUNCTIONS OF HARDWARE
Table 2-2. Setting of Program Run Select Switch
Setting Description
Debug Mode
Stand Alone
(4) SW-4 switch
On "Debug" position, the user's program will run when RUN command is issued from
the debugger GUI.
On "Stand Alone" position, the user's program is automatically run when the reset is
released even the cables from EZ-CUBE is connected to the target board.
This switch is used to set the power supplied to the target system. Table 2-3 describes the setting details.
This switch is set to ″5″ at shipment.
Caution Do not change the switch setting while the USB cable is connected.
5
T
Table 2-3. Setting of Power Select Switch
Setting Description
5 V±0.3V is supplied from EZ-CUBE to the target system Note .
The supplied power is fed back to EZ-CUBE and used only for power detection.
Power supply of the target system is used.
EZ-CUBE only detects the power for the target system.
Note The maximum rating of the current is 100mA, so do not use EZ-CUBE with the target system with the
higher current rating. The power is always supplied after EZ-CUBE is connected to the host
machine.
(5) SW-5 switch
The position of this switch depends on the target devices. The detail describes, please see the follow chapter.
This switch is set to ″Other″ at shipment.
(6) USB interface connector
This is a connector used to connect EZ-CUBE with the host machine, via a USB cable.
A USB 2.0 compliant mini-B connector is employed.
(7) Target interface connector
This is a connector used to connect EZ-CUBE with the target system, via a 8-pin (2*4pin) target cable.
(8) Using the Ext. oscillator connected
SW-2 set for Ext. Clock.
Connect an oscillator or oscillation circuit on the External X'tal socket. (Select for “Clock board” in the
Configuration dialog box of the debugger.) For the operation this step, refer to the user's manual for
CubeSuite+.
Figure 2-2. Mounting Diagram
User’s Manual 12

(9) Mode LED
CHAPTER 2 NAMES AND FUNCTIONS OF HARDWARE
The appearance of the mode LED changes according to the status of hardware and software, as shown in
Table 2-4.
Mode LED
Color
Appearance USB
- Extinguished
Table 2-4. Mode LED Status
Connection
Not
connected
Description
Not yet started
Software Operation
Red Glowing Power or the CPU is in the break
Connected
mode.
Green Glowing
A debugger has been started
User’s Manual 13

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This chapter describes how to use EZ-CUBE when performing on-chip debugging and flash programming for a
78K0 microcontroller.
On-chip debugging is a method to debug a microcontroller mounted on the target system, using a debug function
implemented in the device. Since debugging is performed with the target device operating on the board, this method
is suitable for field debugging.
Flash programming is a method to write a program to the flash memory embedded in a device. Erasing, writing and
verifying the program can be performed on-board with the device.
Please update firmware for 78K0 at first. Refer to description (1) to (3) on the following order. For detail, refer to 1.4
Firmware Update.
(1) Connect EZ-CUBE to the host machine. Do not connect EZ-CUBE to the target system.
(2) Start the EZ-CUBE firmware update tool”QBEZUTL.exe”. Select firmware of 78K0 (78K0_OCD_FW.hex).
(3) Click the [Start] button. Start to update the EZ-CUBE firmware.
Read the following chapters if you are using EZ-CUBE for the first time with a 78K0 microcontroller as the target
device.
3.1 Target System Design
For communication between EZ-CUBE and the target system, communication circuits must be mounted on the
target system. This section describes the circuit design and mounting of connectors.
3.2 On-Chip Debugging
This section describes the system configuration and startup method to perform on-chip debugging with
EZ-CUBE.
3.3 Flash Programming
This section describes the system configuration and startup method to perform flash programming with
EZ-CUBE.
User’s Manual 14

3.1 Target System Design
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This section describes the target system circuit design required for on-chip debugging and flash programming.
Figure 3-1 present overviews of the EZ-CUBE communication interface. For communication between EZ-CUBE
and the target system, communication circuits must be mounted on the target system, as shown on the left side of
the figure. Refer to this section to design circuits appropriately.
Target device
Target system
Figure 3-1. Outline of Communication Interface for On-Chip Debugging
UART
communication
Communication circuits
must be mounted on
.
the target system. .
RENESAS
EZ-CUBE
EZ-CUBE
USB
Communication
Host machine
3.1.1 Pin assignment
This section describes the interface signals used between EZ-CUBE and the target system. Table 3-1 lists the
pin assignment when a 8-pin target cable is used. Table 3-2 describes the functions of each pin.
Pin No. Pin name Note
1 GND
2 RESET_IN
3 Vdd
4 FLMD0
5 CLK
6 RxD.
7 RESET_OUT
8 TxD
Note Signal names in EZ-CUBE
Table 3-1. Pin Assignment When Using 8-Pin Target Cable
Target interface
connector
7
8
5
6 4
User’s Manual 15
3
1
2

Pin Name IN/OUT Note
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
Table 3-2. Pin Functions
Description
RESET_IN IN Pin used to input reset signal from the target system
RESET_OUT
OUT Pin used to output reset signal to the target device
CLK OUT Pin used to output clock signal to the target device
FLMD0 OUT Pin used to set the target device to debug mode or programming
mode
RxD IN Pin used to receive command/data from the target device
TxD OUT Pin used to transmit command/data to the target device
N ote As seen from EZ-CUBE.
3.1.2 Circuit connection examples
The circuit design on the target system varies depending on the used connector and interface signals.
The following (1) to (2) are the major purpose of use. Confirm the purpose, refer to Table 3-1 and see the
relevant
circuit connection example for specifications.
Caution The constants described in the circuit connection example are reference values. If you perform
flash programming aiming at mass production, thoroughly evaluate whether the specifications of
the target device are satisfied.
(1) Used to perform on-chip debugging.
(2) Used to perform flash programming.
User’s Manual 16

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
Figure 3-2. When Debugging is Performed
Notes 1. This connection is designed assuming that the RESET signal is output from the N-ch open-drain buffer
(output resistance: 100Ω or less). For details, refer to 3.1.3 Connection of reset pin .
2. OCD1A may be a different name, depending on the device used. For details, refer to the user's manual
for the target device.
User’s Manual 17

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
Figure 3-3. When Programming is Performed
Notes 1. This connection is designed assuming that the RESET signal is output from the N-ch open-drain buffer
(output resistance: 100 Ω or less). For details, refer to 3.1.3 Connection of reset pin.
2. Connect TxD (transmit side) of the target device to RxD (receive side) of the target connector, and TxD
(transmit side) of the target connector to RxD (receive side) of the target device.
3.1.3 Connection of reset pin
This section describes the connection of the reset pin, for which special attention must be paid, in circuit
connection examples shown in the previous section.
During on-chip debugging, a reset signal from the target system is input to EZ-CUBE, masked, and then output
to the target device. Therefore, the reset signal connection varies depending on whether EZ-CUBE is connected.
For flash programming, the circuit must be designed so that the reset signals of the target system and EZ-CUBE
do not conflict.
Automatically switching the reset signal via resistor (recommended; described in recommended circuit
connection in the previous section).
Figure 3-4 illustrates the reset pin connection described in 3.1.2 Circuit connection examples. This
connection is designed assuming that the reset circuit on the target system contains an N-ch open-drain buffer
(output resistance: 100Ω or less). The VDD or GND level may be unstable when the logic of RESET_IN/OUT of
EZ-CUBE is inverted, so observe the conditions described below in Remark.
User’s Manual 18

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
Figure 3-4. Circuit Connection with Reset Circuit That Contains Buffer
EZ-CUBE
RESET_OUT
RESET_IN
R1
Target device
_RESET
R2
VDD V
Reset connector
Buffer
Remark Make the resistance of at least R1 ten times that of R2, R1 being 10 kΩ or more.
Pull-up resistor R2 is not required if the buffer of the reset circuit consists of CMOS output.
The circuit enclosed by a dashed line is not required when only flash programming is performed.
Figure 3-5 illustrates the circuit connection for the case where the reset circuit on the target system contains
no buffers and the reset signal is only generated via resistors or capacitors. Design the circuit, observing the
conditions described below in Remark.
Figure 3-5. Circuit Connection with Reset Circuit That Contains No Buffers
EZ-CUBE
RESET_OUT
RESET_IN
_RESET
R1 R2
V DD
V DD
Target device Reset connector
Remark Make the resistance of at least R1 ten times that of R2, R1 being 10 kΩ or more.
The circuit enclosed by a dashed line is not required when only flash programming is performed.
3.1.4 Cautions on target system design
Note the following cautions when designing the target system.
• Do not place X1/OCD1A and X2/OCD1B next to each other on the target system. If the layout requires this,
they should be made as short as possible.
• Make the distance between the target connector and the target device as short as possible.
• Since the X1/OCD1A and X2/OCD1B lines are used for clock supply, be sure to shield them, such as with a
GND pattern.
• Before shipping the product, use jumpers or other means to physically separate the X1/OCD1A and
X2/OCD1B pins from the target connector in order to ensure normal clock oscillation.
• When debugging, remove capacitors, feedback resistors, and other elements for the resonator in order to
prevent signal degradation due to the load placed on the X1/OCD1A and X2/OCD1B pins.
User’s Manual 19

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
3.1.5 Mounting connector onto target system
The connector must be mounted on the target system for connecting EZ-CUBE with the target system. 2.54
mm pitch 8-pin general-purpose connector can be used.
Compact connectors and loose-wire cables are also available as options.
User’s Manual 20

3.2 On-Chip Debugging
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This section describes the system configuration, startup/shutdown procedure and cautions for debugging when
on-chip debugging is performed with EZ-CUBE.
3.2.1 Debug functions
Table 3-3 lists the debug functions when a 78K0 microcontroller is the target device.
Table 3-3. Debug Functions
Functions Specifications
Target device 78K0
78K0/Kx2, Lx3
Security 10-byte ID code authentication
Download Available
Execution Go, Step In, Step Over, CPU Reset, Restart
Hardware break 1 point
Software break Multiple points
User spaces used for debugging Internal ROM: 256 to 400 bytes
Function pins used for debugging X1, X2
Internal RAM: 7 to 9 bytes
depending on the device used
User’s Manual 21

3.2.2 System configuration
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
Figure 3-6 illustrates the system configuration for on-chip debugging.
Target device
Target device
Host machine
Products with USB ports
Software
Figure 3-6. System Configuration for On-Chip Debugging
EZ-CUBE
Includes CubeSuite+ for China, USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory)
User’s Manual 22

3.2.3 System startup procedure
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform on-chip debugging. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• CubeSuite+ for China
• USB driver
(2) Switch setting
SW-1: Select switch to ″M2″.
SW-2: Depend on the user system environment.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″Other″.
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system.
Perform connection before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The mode LED glows red after connection.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) Debugger startup
Start the debugger.
For the operation after this step, refer to the user's manual for CubeSuite+.
If the debugger does not start normally or the operation is unstable, the possible causes may be the following.
• Communication error between EZ-CUBE and target system
Whether firmware is update.
Whether switch is selected normally.
Whether communication is performed normally.
• The user resource has not been secured or the security ID has not been set
To perform debugging with EZ-CUBE, the user resource must be secured and the security ID must be set.
For details, refer to 3.2.6 Securing of user resources and setting of security ID.
• Unsupported software (debugger, device file, or firmware) is used
The software used may not support debugging of the target device.
• Defect of EZ-CUBE
EZ-CUBE may have a defect.
User’s Manual 23

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
3.2.4 System shutdown procedure
Terminate debugging and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Debugger termination
Terminate the debugger.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
3.2.5 Clock setting
EZ-CUBE can supply a clock to be used as the high-speed system clock (4, 8, or 16 MHz).
Select SW-2 is “Int. Clock”
Remove the oscillator or oscillation circuit (Selected for ”Generate by emulator” in the Configuration dialog box
of the debugger).
For the settings, refer to the user's manual for CubeSuite+.
User’s Manual 24

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
3.2.6 Securing of user resources and setting of security ID
EZ-CUBE uses the user memory spaces (shaded portions in Figure 3-7) to implement communication with the
target device, or each debug functions. The areas marked with a dot (•) are always used for debugging, and other
areas are used for each debug function used. Refer to the descriptions of (a) to (e) on the following pages and
secure these spaces in the user program or using the compiler options.
Figure 3-7. Reserved Area Used by EZ-CUBE
User’s Manual 25

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
(a) Debug monitor area (this area must be secured)
Addresses 0x02, 0x03 and area starting from address 0x8F must be secured to embed the debug monitor
program.
If this area is rewritten by flash self programming, on-chip debugging can no longer be performed.
[How to secure areas]
When using Renesas Electronics compiler, addresses 0x02, 0x03 and area starting from address can be
secured for debug monitoring, using the linker option (-go). Figure 3-8 shows the Linker Options dialog box of
CubeSuite+. Select the ″Use on-chip debug″ check box as shown in the figure below. Set the size to 256
bytes (in actuality, 257 bytes from 0x8F to 0x18F are secured).
Figure 3-8. Link Options Setting (Debug Monitor Area)
User’s Manual 26

(b) Option byte area (essential)
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This is the area for the security setting to prevent the flash memory from being read by an unauthorized person.
The target device operates in accordance with the set value, as shown below.
Table 3-4. Option Byte Setting and Operation
Set Value Description Remark
0x00 Debugging is unavailable even if an on-chip debug emulator
(such as EZ-CUBE) is connected.
0x02 The on-chip flash memory is not erased no matter how many
times the security ID code authentication fails.
0x03 All on-chip flash memory areas are erased if the security ID
code authentication fails.
This setting is available
only for flash programming.
Other than above Setting prohibited -
[How to set]
Describe the code for setting the option byte in the user program. Refer to the following and add a code to
the assembler source.
Example When setting 0x02
SSS CSEG AT 084H; ″SSS″ is an arbitrary symbol name (eight characters or less)
DB 2H
Caution If address 0x84 is overwritten by 0x00 by self programming, communication is disabled, and
debugging and connection can no longer be performed even if the debugger is restarted. In
such as case, erase the memory via flash programming.
(c) Security ID area (essential)
This is the area for the security setting to prevent the flash memory from being read by an unauthorized person.
The security ID functions as a password for starting the debugger. The debugger starts only when the
security ID that is input during debugger startup and the security ID embedded in this area match.
[How to set]
Figure 3-9 shows the Linker Options dialog box of CubeSuite+. Select the ″Security ID″ check box as shown
in the figure below and set an arbitrary ID code (10 bytes).
User’s Manual 27
-
-

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
Figure 3-9. Linker Option Setting (Security ID)
(d) Stack area for debugging (this area must be secured)
This area requires 7 to 9 bytes as the stack area for debugging. Since this area is allocated immediately
before the stack area, the address of this area varies depending on the stack increase and decrease.
Figure 3-10 illustrates the case where the stack area is increased when the internal high-speed RAM starts
from 0xFB00.
0xFEDF
0xFB00
Figure 3-10. Variation of Address of Stack Area for Debugging
7 bytes
Stack area
Stack area for
debugging
Available space
in internal highspeed
RAM
0xFEDF
0xFB00
7 bytes
0xFEDF
0xFB07
0xFB00
7 bytes
User’s Manual 28

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
The size of this area also varies depending on whether software breaks or pseudo real-time RAM monitor is
used.
Table 3-5. Size of Stack Area for Debugging
Item Size of Stack Area for Debugging
Standard 7 bytes
When software breaks are used 9 bytes
[How to secure areas]
Refer to the address range shown below and set the stack pointer.
Example When internal high-speed RAM starts from 0xFB00
- Standard
Within the range 0xFB07 to 0xFEDF Note
- When software breaks are used (also refer to (e))
Within the range 0xFB09 to 0xFEDF Note
Note Because the area 0xFEDF is used by EZ-CUBE during a break, set the initial value of the stack
pointer to 0xFEDF, not 0xFEE0 (when the initial value is set to 0xFEDF, the actual value used for the
stack is 0xFEDE, so there will be no problems).
Furthermore, 0xFEDF is prohibited for use as stack area, but it can be used as variable area.
(e) Software break area
This area is used for software breaks.
[How to secure areas]
Refer to the following and secure the area.
SSS CSEG AT 07EH; ″SSS″ is an arbitrary symbol name (eight characters or less)
DB 0FFH, 0FFH
User’s Manual 29

3.2.7 Cautions on debugging
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This section describes cautions on performing on-chip debugging for a 78K0 microcontrollers.
Be sure to read the following to use EZ-CUBE properly.
(1) Handling of device that was used for debugging
Do not mount a device that was used for debugging on a mass-produced product, because the flash memory
was rewritten during debugging and the number of rewrites of the flash memory cannot be guaranteed.
(2) Overwriting flash memory during on-chip debugging
If the following operations are performed during on-chip debugging, the flash memory in the device is
overwritten.
Downloading a program
Manipulation in Memory Fill dialog box
Manipulation in Memory Copy dialog box
Manipulation to change memory in Memory window
Online assembly in Assemble window
Settings when using software breaks
It takes time from completion of flash memory programming until the control is passed to GUI.
(3) Software break
During program running, do not rewrite the data at the address where a software break is set. This includes
self programming and rewriting to RAM. If performed, the instruction placed at the address may be invalid.
(4) Boot swapping during self programming
The boot swapping function cannot be emulated. This is because boot swapping moves the memory spaces
used for debugging, and thus the debug communication can no longer be performed.
(5) Break function for stack pointer initialization failure
This function executes a break when an interrupt occurs or a PUSH instruction is executed while the initial
setting has not been made for the stack pointer.
If the manipulation or instruction shown below is executed immediately after a reset operation, the break
function for stack pointer initialization failure becomes invalid.
• Setting a software break
• Write to the stack pointer from the Register window
• Write to the flash memory from the Memory window, etc
If a software break occurs while the initial setting has not been made for the stack pointer, the message
″Uninitialized Stack Pointer″ is displayed on the status bar.
The subsequent operations are not performed normally, so make sure to set the SP value in the user program.
(6) Caution on downloading a HEX file
When downloading a HEX file, do not set specify a filling value other than 0xFF for the object converter option
(-U).
(7) Caution on performing step execution
Some SFRs (special function registers) remain stopped during step execution. In such a case, execute the
instruction with the real-time execution function.
User’s Manual 30

(8) Caution on mounting a clock
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
When a clock is mounted, power supply may not become the GND level even if the power to the target system
is shut down.
(9) Emulation of POC function
The POC function of the target device cannot be emulated. Make sure that the power to the target system is
not shut down during debugging
User’s Manual 31

3.3 Flash Programming
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This section describes the system configuration and startup/shutdown procedure when flash programming is
performed for a 78K0 microcontroller, using EZ-CUBE.
3.3.1 Specifications of programming function
Host interface
Target interface
Table 3-6. Specifications of Programming Function
Functions Specifications
Target system voltage
Clock supply
Power supply
Acquisition of device-specific
information
Security flag setting
Standalone operation
3.3.2 System configuration
USB 2.0
UART
2.7 to 5.5 V (depends on the target device)
8MHz clock can be supplied
Clock mounted on the target system can be used
5 ±0.3 V (maximum current rating: 100 mA)
Parameter file for Renesas Electronics is used
Available
Unavailable (must be connected to host machine)
Figure 3-11 illustrates the system configuration for flash programming.
Target device
Host machine
Products with USB ports
Software
Figure 3-11. System Configuration for Flash Programming
EZ-CUBE
Includes the RFP, USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory)
User’s Manual 32

3.3.3 System startup procedure
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform flash programming. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• RFP
• USB driver
(2) Switch setting
SW-1: Select switch to ″M1″.
SW-2: Depend on the user system environment.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″Other″.
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The power is always supplied after EZ-CUBE is connected to the host machine with the USB cable.
Caution Do not change the switch setting while the USB cable is connected.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) RFP startup
Start the RFP. For detailed usage of the RFP, refer to the RFP User's Manual.
User’s Manual 33

3.3.4 Usage examples
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
This section describes a series of basic operations using the RFP, using the UPD78F0513D as an example.
The operations from execution of the [Autoprocedure (EP)] command to programming for the target device are
described. For other commands and their applications, refer to the RFP User's Manual.
The conditions used for a series of operations in this section are as follows.
Target device: UPD78F0513D
Power supply voltage: 5 V±0.3V (supplied from EZ-CUBE)
Communication channel: UART, 115,200 bps
Switches: SW-1: M1
SW-2: Int.Clock
SW-3: Debug Mode
SW-4: 5
SW-5: Other
Clock setting: 8 MHz, x1
Operation mode: chip
Program file: sample.hex
Command option: [Blank check before Erase] selected
[Verify after Program] selected
User’s Manual 34

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
(1) Setting of programming environment
Set the programming environment, following the steps to described below.
On the taskbar, click the Start button, point to [All Programs], [Renesas Electronics CubeSuite+],
[Programming Tools], [Renesas Flash Programmer Vx.xx], and then click [Renesas Flash Programmer
Vx.xx [Basic mode]]. The [Welcome!] dialog box will open. Select [Create new workspace.] and then click
the Next button to open the [Create a new workspace] dialog box.
Figure 3-12. [Welcome!] Dialog Box
In the [Using Target Microcontroller:] list box, select “UPD78F0513D”. Enter any text string (such as
“sample” in this case) in the [Workspace Name:] box, and specify any folder in the [Folder:] box.
Clicking the Next button displays the [Select Communication Interface] dialog box.
Figure 3-13. Parameter File Select Dialog Box
User’s Manual 35

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
Select “Tool”, in the [Select Communication Interface] dialog box. For EZ-CUBE, the area is
fixed to “PC port No.(Renesas Virtual UART)”.
Clicking the Next button displays the [Setting Oscillator] dialog box.
Figure 3-14. [Select Communication Interface] Dialog Box
Select “Frequency” from the [Supply Oscillator] list box. For EZ-CUBE, the [Supply Oscillator] area is
fixed to “8MHz”.
Clicking the Next button.
Figure 3-14. [Setting Oscillator] Dialog Box
User’s Manual 36

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
“Chip” is the default value for [Operation mode] under the [Target] category, and the default value for “Blank
Check before Erase” in the [Command Options] category is “Valid”. And the default value for “Verify after
Program” in the [Command Options] category is “Valid”.
Clicking the Complete button saves the project file and displays the main window.
(2) Selection of program file
Figure 3-15. [Information Settings] Dialog Box
Select the program file, following the steps to described below.
Click the Browse… button in “User/Data area:” of the program file area to open the [Open File] dialog box.
Select “sample.hex” in the [Open File] dialog box, and then click the Open button to open the main
window.
User’s Manual 37

CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
(3) Execution of [Autoprocedure (E.P)] command
Click the [Microcontroller] menu and select the [Autoprocedure (E.P)] command. A check mark is then
placed on the left of the command, and the command is assigned to the Start button. After clicking the Start
button, execute the following commands in the following order for UPD78F0513D: [Blank Check] command,
[Erase] command (if there are no blanks), [Program] command, and [Verify] command.
Figure 3-16. Completion of [Autoprocedure (E.P)] Command Execution
User’s Manual 38

3.3.5 System shutdown procedure
CHAPTER 3 HOW TO USE EZ-CUBE WITH 78K0 MICROCONTROLLER
Terminate flash programming and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Terminating the RFP
Terminate the RFP if you are not going to perform programming to other devices.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″ 5 ″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
When the power select switch is set to ″T″, the step of (4) Unplugging the target cable can be performed
before this step.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
3.3.6 Cautions on flash programming
This section describes the cautions for flash programming. Be sure to read the following for the proper use of
EZ-CUBE.
• To improve the writing quality, fully understand, verify, and evaluate the following items before using EZ-CUBE.
- Circuits are designed as described in the user's manuals for the device and EZ-CUBE.
- The device, RFP and EZ-CUBE are used as described in each user's manual.
- The power supplied to the target system is stable.
User’s Manual 39

CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This chapter describes how to use EZ-CUBE when performing on-chip debugging and flash programming for a
78K0R microcontroller.
On-chip debugging is a method to debug a microcontroller mounted on the target system, using a debug function
implemented in the device. Since debugging is performed with the target device operating on the board, this method
is suitable for field debugging.
Flash programming is a method to write a program to the flash memory embedded in a device. Erasing, writing
and verifying the program can be performed on-board with the device.
Please update firmware for 78K0R at first. Refer to description (1) to (3) on the following order. For detail, refer to
1.4 Firmware update.
(1) Connect EZ-CUBE to the host machine. Do not connect EZ-CUBE to the target system.
(2) Start the EZ-CUBE firmware update tool”QBEZUTL.exe”. Select firmware of 78K0R (78K0R_OCD_FW.hex).
(3) Click the [Start] button. Start to update the EZ-CUBE firmware.
Read the following chapters if you are using EZ-CUBE for the first time with a 78K0R microcontroller as the target
device.
4.1 Target System Design
For communication between EZ-CUBE and the target system, communication circuits must be mounted on the
target system. This section describes the circuit design and mounting of connectors.
4.2 On-Chip Debugging
This section describes the system configuration and startup method to perform on-chip debugging with
EZ-CUBE.
4.3 Flash Programming
This section describes the system configuration and startup method to perform flash programming with
EZ-CUBE.
User’s Manual 40

4.1 Target System Design
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes the target system circuit design required for on-chip debugging and flash programming.
Figure 4-1 presents an overview of the EZ-CUBE communication interface. As shown on the left side of the
figure, EZ-CUBE performs serial communication with the target device on the target system. For this
communication, communication circuits must be mounted on the target system. Refer to this section to design
circuits appropriately.
Target device
Target system
Figure 4-1. Outline of Communication Interface
UART communication
(1-wire/2-wire mode) Note
Communication circuits
must be mounted on
.
the target system. .
RENESAS
EZ-CUBE
EZ-CUBE
USB
communication
Host machine
Note 1-wire mode: Single-wire UART communication using TOOL0 pin
2-wire mode: Single-wire UART communication using TOOL0 and TOOL1 pins
Communication
Mode
Table 4-1. Differences Between 1-Wire Mode and 2-Wire Mode
Flash Programming
Function
Debugging Function
1-wire mode Available • User resources secured for debugging
Internal ROM: 1036 bytes
Internal RAM: 6 bytes (stack)
2-wire mode Available • User resources secured for debugging
Internal ROM: 100 bytes
Internal RAM: 6 bytes (stack)
User’s Manual 41

4.1.1 Pin assignment
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes the interface signals used between EZ-CUBE and the target system. Table 4-2 lists the
pin assignment. Table 4-3 describes the functions of each pin. The pin assignment varies between 1-wire and
2-wire modes, so design the circuit appropriately according to the circuit connection examples described on the
following sections.
Pin No. Pin name Note
1 GND
2 RESET_IN
3 Vdd
4 FLMD0
5 CLK
6 RxD.
7 RESET_OUT
8 TxD
Note Signal names in EZ-CUBE
Note 1
Pin Name IN/OUT
Table 4-2. Pin Assignment
Target
interface
connector
Table 4-3. Pin Functions
7
8
5
Description
RESET_IN IN Pin used to input reset signal from the target system
RESET_OUT OUT Pin used to output reset signal to the target device
3
6 4
FLMD0 OUT Pin used to set the target device to debug mode or programming mode
RXD IN/OUT Pin used to transmit/receive command/data between the target device
TXD IN/OUT Pin used to transmit/receive command/data between the target device
CLK IN Pin used to input handshake signal from the target device
Note As seen from EZ-CUBE
User’s Manual 42
1
2

4.1.2 Circuit connection example
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
Refer to Figure 4-2 and design an appropriate circuit.
Caution The constants described in the circuit connection example are reference values. If you perform
flash programming aiming at mass production, thoroughly evaluate whether the specifications of
the target device are satisfied.
Figure 4-2. Recommended Circuit Connection
Notes 1. This connection is designed assuming that the RESET signal is output from the N-ch open-drain
buffer (output resistance: 100Ω or less). For details, refer to 4.1.3 Connection of reset pin
2. The circuit enclosed by a dashed line is not required when only flash programming is performed.
3. This connection is required for 2-wire communication, but not for 1-wire communication. This pin
is left open when EZ-CUBE is not connected, so connect a pull-up or pull-down resistor to this pin
before using.
User’s Manual 43

4.1.3 Connection of reset pin
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes the connection of the reset pin, for which special attention must be paid, in the circuit
connection example shown in the previous section.
During on-chip debugging, a reset signal from the target system is input to EZ-CUBE, masked, and then output
to the target device. Therefore, the reset signal connection varies depending on whether EZ-CUBE is connected.
For flash programming, the circuit must be designed so that the reset signals of the target system and EZ-CUBE
do not conflict.
Recommend automatically switching the reset signal via series resistor.
Figure 4-3 illustrates the reset pin connection described in 4.1.2 Circuit connection example.
This connection is designed assuming that the reset circuit on the target system contains an N-ch open-drain
buffer (output resistance: 100Ω or less). The VDD or GND level may be unstable when the logic of
RESET_IN/OUT of EZ-CUBE is inverted, so observe the conditions described below in Remark.
Figure 4-3. Circuit Connection with Reset Circuit That Contains Buffer
EZ-CUBE
RESET_OUT
RESET_IN
R1
Target device
_RESET
R2
VDD V
Reset connector
Buffer
Remark Make the resistance of at least R1 ten times that of R2, R1 being 10 kΩ or more.
Pull-up resistor R2 is not required if the buffer of the reset circuit consists of CMOS output.
The circuit enclosed by a dashed line is not required when only flash programming is performed.
Figure 4-4 illustrates the circuit connection for the case where the reset circuit on the target system contains
no buffers and the reset signal is only generated via resistors or capacitors. Design the circuit, observing the
conditions described below in Remark.
Figure 4-4. Circuit Connection with Reset Circuit That Contains No Buffers
EZ-CUBE
RESET_OUT
RESET_IN
_RESET
R1 R2
VDD DD
V DD
Target device Reset connector
Remark Make the resistance of at least R1 ten times that of R2, R1 being 10 kΩ or more.
The circuit enclosed by a dashed line is not required when only flash programming is performed.
4.1.4 Mounting connector onto target system
The connector must be mounted on the target system for connecting EZ-CUBE with the target system. 2.54
mm pitch 8-pin general-purpose connector can be used.
Compact connectors and loose-wire cables are also available as options.
User’s Manual 44

4.2 On-Chip Debugging
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes the system configuration, startup/shutdown procedure and cautions for debugging when
on-chip debugging is performed with EZ-CUBE.
4.2.1 Debug functions
Table 4-4 lists the debug functions when a 78K0R microcontroller is the target device.
Table 4-4. Debug Functions
Functions Specifications
Target device 78K0R
78K0R/Kx3,Lx3
Security 10 byte ID code authentication
Download Available
Execution Go, Step In, Step Over, CPU Reset, Restart
Hardware break 1 point (commonly used by execution and access)
Software break Multiple points
User spaces used for debugging 1-wire mode:Internal ROM: 1036 bytes, Internal RAM: 6 bytes Note
Function pins used for debugging 1-wire mode: TOOL0
2-wire mode:Internal ROM: 100 bytes, Internal RAM: 6 bytes Note
2-wire mode: TOOL0, TOOL1
Note For details, refer to 4.2.5 Securing of user resources and setting of security ID and on-chip debug option
byte.
User’s Manual 45

4.2.2 System configuration
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
Figure 4-5 illustrates the system configuration for on-chip debugging.
Target device
Target device
Host machine
Products with USB ports
Software
Figure 4-5. System Configuration for On-Chip Debugging
EZ-CUBE
Includes CubeSuite+ for China, USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory)
User’s Manual 46

4.2.3 System startup procedure
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform on-chip debugging. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• CuebSuite+ for China
• USB driver
(2) Switch setting
SW-1: Select switch to ″M2″.
SW-2: Depend on the user system environment.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″Other″.
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The mode LED glows red after connection.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) Debugger startup
Start the debugger.
For the operation after this step, refer to the user's manual for CuebSuite+.
If the debugger does not start normally or the operation is unstable, the possible causes may be the following.
Communication error between EZ-CUBE and target system
Whether firmware is update.
Whether switch is selected normally.
Whether communication is performed normally.
• The user resource has not been secured or the security ID has not been set
To perform debugging with EZ-CUBE, the user resource must be secured and the security ID must be set.
For details, refer to 4.2.5 Securing of user resources and setting of security ID.
• Unsupported software (debugger, device file, or firmware) is used
The software used may not support debugging of the target device.
• Defect of EZ-CUBE
EZ-CUBE may have a defect.
User’s Manual 47

4.2.4 System shutdown procedure
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
Terminate debugging and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Debugger termination
Terminate the debugger.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
User’s Manual 48

CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
4.2.5 Securing of user resources and setting of security ID and on-chip debug option byte
The user must prepare the following to perform communication between EZ-CUBE and the target device and
implement each debug function. If Renesas Electronics assembler or compiler is used, the items can be set by
using linker options. Refer to the descriptions on the following pages and set these items.
• Securing of memory space
The shaded portions in Figure 4-6 are the areas reserved for placing the debug monitor program, so user
programs or data cannot be allocated in these spaces. These spaces must be secured so as not to be
used by the user program. Moreover, this area must not be rewritten by the user program.
Internal ROM space
1024 bytes
10 bytes
10 bytes
1 byte
2 bytes
Note
Figure 4-6. Memory Spaces Where Debug Monitor Programs Are Allocated
Internal ROM end address
(a) Debug monitor area
D8H
D7H
(a) Debug monitor area
CEH
CDH
(c) Security ID area
C4H
C3H (b) On-chip debug option byte area
03H
(a) Debug monitor monitor area
02H
Internal RAM space
6 bytes
Internal RAM end address
(d) Stack area for debugging
: Area used for on-chip debugging
Note In debugging, reset vector is rewritten to address allocated to a monitor program.
• Setting of security ID and on-chip debug option byte
The security ID or on-chip debug option byte must be embedded in the area filled with yellow (0xC3 and
0xC4 to 0xCD) in Figure 4-6, to prevent the memory from being read by an unauthorized person.
User’s Manual 49

CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
(a) Securing of debug monitor area
This is the area to which the debug monitor program is to be allocated. The monitor program performs
initialization processing for debug communication interface and RUN or break processing for the CPU.
This user programs or data must not be placed in an area of 22 bytes near the on-chip debug option
byte, and an area of 1,024 bytes before the internal ROM end address. In addition, reset vector is
rewritten to address allocated to a monitor program.
[How to secure areas]
This is the area to which the debug monitor program is to be allocated. However To avoid problems that
may occur during the debugger startup, it is recommended to secure this area in advance, using the
compiler. Figure 4-7 shows example for securing the area, using the CubeSuite+. Set in “device” in link
options tab as figure 4-7.
(b) On-chip debug option byte area
This is the area for the security setting to prevent the flash memory from being read by an unauthorized
person. The debugger manipulates the target device in accordance with the set value, as shown
below.
Table 4-5. On-Chip Debug Option Byte Setting and Operation
Set Value Description Remark
0x04 Debugging is disabled even if an on-chip debug This setting is available only
emulator (such as EZ-CUBE) is connected.
for flash programming and self
programming.
0x85 The on-chip flash memory is not erased no matter
how many times the security ID code authentication
fails.
-
0x84 All on-chip flash memory areas are erased if the
security ID code authentication fails.
-
Other than above Setting prohibited -
Caution Values can be set only to bits 7 and 0 (OCDENSET and OCDERSD). Be sure to write
000010B to bits 6 to 1.
Remark Values set to bits 3 to 1 are changed during on-chip debugging, so values of these bits are
undefined after setting. However, be sure to set these bits to initial values (0, 1, 0).
[How to set]
The following shows a setting example when using Renesas Electronics assembler or compiler. Set a
value for the Control Value text box under the ″ Use on-chip debug [-go]″ check box as shown in the
figure below.
Example Setting 0x84 for control value
User’s Manual 50

CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
Figure 4-7. On-Chip Debug Option Byte and Monitor Area Setting Example
Caution If bit 7 (OCDENSET) of the on-chip debug option byte area (address 0xC3) is set to ″0″ by flash
programming or self programming, debugging is disabled and the debugger can no longer start
unconditionally. To enable debugging, erase the flash memory by flash programming.
(c) Security ID area
This is the area for the security setting to prevent the flash memory from being read by an unauthorized person.
The security ID functions as a password for starting the debugger. The debugger starts only when the
security ID that is input during debugger startup and the security ID embedded in this area match. If the ID
codes do not match, the debugger manipulates the target device in accordance with the value set to the
on-chip debug option byte area (refer to Table 4-5).
[How to set]
An ID code is generated in the security ID area by setting the security ID when using Renesas Electronics
assembler or compiler. Set in “device” in the common options tab as figure 4-8.
User’s Manual 51

CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
Figure 4-8. Security ID Setting Example
Caution If you have forgotten the security ID, erase the flash memory by flash programming or self
programming and then set the security ID again.
(d) Securing of stack area for debugging
This area requires 6 bytes as the stack area for debugging. Since this area is allocated immediately before
the stack area, the address of this area varies depending on the stack increase and decrease. That is, 6
extra bytes are consumed for the stack area used.
Figure 4-9 illustrates the case where the stack area is increased when the internal high-speed RAM starts from
0xFCF00.
0xFFEDF
0xFCF00
6bytes
[How to secure areas]
Figure 4-9. Variation of Address of Stack Area for Debugging
Stack area
Stack area for
debugging
Available space
In internal highspeed
RAM
0xFFEDF
0xFCF00
6 bytes
0xFFEDF
0xFCF06
0xFCF00
6 bytes
Set the stack pointer by estimating the stack area consumed by the user program + 6 bytes. Make sure that
the stack pointer does not extend beyond the internal high-speed RAM start address.
Remark Refer to the self programming manual for how to secure the stack area for self programming.
User’s Manual 52

4.2.6 Cautions on debugging
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes cautions on performing on-chip debugging for a 78K0R microcontroller.
Be sure to read the following to use EZ-CUBE properly.
(1) Handling of device that was used for debugging
Do not mount a device that was used for debugging on a mass-produced product, because the flash memory
was rewritten during debugging and the number of rewrites of the flash memory cannot be guaranteed.
Moreover, do not embed the debug monitor program into mass-produced products.
(2) Flash self programming
If a space where the debug monitor program is allocated is rewritten by flash self programming, the debugger
can no longer operate normally. This caution also applies to boot swapping for such an area.
(3) Operation after reset
After an external pin reset or internal reset, the monitor program performs debug initialization processing.
Consequently, the time from reset occurrence until user program execution differs from that in the actual
device operation.
(4) Debugging with real machine running without using EZ-CUBE
If debugging is performed with a real machine running, without using EZ-CUBE, write the user program using
the RFP. Programs downloaded by the debugger include the monitor program, and such a program
malfunctions if it includes processing to make the TOOL0 pin low level.
(5) Operation when debugger starts
When the debugger is started, if the Target Device Connection setting in the Configuration dialog box of the
debugger is different from the setting for the previous debugging, the internal flash memory is erased.
(6) Debugging after program is written by flash programming
If a program is written to the internal flash memory using the RFP, on-chip debugging is disabled even if it is
enabled in the on-chip debugging option byte setting. To perform debugging of the target device after that,
erase the internal flash memory using the RFP and then download the program using the debugger.
(7) LVI default start function setting (address C1H)
The LVI setting at address C1H in the internal flash memory during debugging is set as follows.
- When EZ-CUBE is connected: The LVI default start function is available.
- When EZ-CUBE is not connected: The LVI default start function is unavailable.
(8) On-chip debugging option byte setting (address C3H)
The on-chip debugging option byte setting is rewritten arbitrarily by the debugger.
(9) Debugging in 1-wire mode
Note the following points when debugging is performed in 1-wire mode (selected by choosing TOOL0 in the
Connection with Target Board area in the Communication method dialog box of the debugger).
When the internal high-speed oscillator is used for the CPU operating clock, breaks may not occur normally if
the frequency variation between debugger startup and break occurrence (except for when changing the
register) is too large. This situation may occur when the variation of operating voltage or temperature is too
large.
User’s Manual 53

4.3 Flash Programming
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes the system configuration and startup/shutdown procedure when flash programming is
performed for a 78K0R microcontroller, using EZ-CUBE.
4.3.1 Specifications of programming function
Table 4-6. Specifications of Programming Function
Functions Specifications
Host interface USB 2.0
Target interface UART (1-wire mode)
Target system voltage 2.7 to 5.5 V (depends on the target device)
Clock supply Internal high-speed oscillation clock is used
Power supply 5 V ±0.3 V (maximum current rating: 100 mA)
Acquisition of device-specific
information
Security flag setting Available
Parameter file for Renesas Electronics is used
Standalone operation Unavailable (must be connected to host machine)
4.3.2 System configuration
Figure 4-10 illustrates the system configuration for flash programming.
Target device
Host machine
Products with USB ports
Software
Figure 4-10. System Configuration for Flash Programming
EZ-CUBE
Includes the RFP, USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory)
User’s Manual 54

4.3.3 System startup procedure
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform flash programming. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• RFP
• USB driver
(2) Switch setting
SW-1: Select switch to ″M2″.
SW-2: Depend on the user system environment.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″Other″
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The power is always supplied after EZ-CUBE is connected to the host machine with the USB cable.
Caution Do not change the switch setting while the USB cable is connected.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) RFP startup
Start the RFP.
For detailed usage of the RFP, refer to the RFP User's Manual.
User’s Manual 55

4.3.4 Usage examples
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
This section describes a series of basic operations using the RFP, using the UPD78F1166 as an example. The
operations from execution of the [Autoprocedure (E.P)] command to programming for the target device are
described. For other commands and their applications, refer to the RFP User's Manual.
The conditions used for a series of operations in this section are as follows.
Target device: UPD78F1166
Power supply voltage: 5 V±0.3V (supplied from EZ-CUBE)
Switches: SW-1: M2
Operation mode: chip
SW-2: Int.Clock
SW-3: Debug Mode
SW-4: 5
SW-5: Other
Program file: sample.hex
Command options: [Blank check before Erase] selected
[Verify after Program] selected
User’s Manual 56

CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
(1) Setting of programming environment
Set the programming environment, following the steps to described below.
On the taskbar, click the Start button, point to [All Programs], [Renesas Electronics CubeSuite+],
[Programming Tools], [Renesas Flash Programmer Vx.xx], and then click [Renesas Flash Programmer
Vx.xx [Basic mode]]. The [Welcome!] dialog box will open. Select [Create new workspace.] and then click
the Next button to open the [Create a new workspace] dialog box.
Figure 4-11. [Welcome!] Dialog Box
In the [Using Target Microcontroller:] list box, select “UPD78F1166”. Enter any text string (such as
“sample” in this case) in the [Workspace Name:] box, and specify any folder in the [Folder:] box.
Clicking the Next button displays the [Select Communication Interface] dialog box.
Figure 4-12. Parameter File Select Dialog Box
User’s Manual 57

CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
Select “Tool”, in the [Select Communication Interface] dialog box. For EZ-CUBE, the area is
fixed to “PC port No.(Renesas Virtual UART)”.
Clicking the Next button displays the [Setting Oscillator] dialog box.
Figure 4-13. [Select Communication Interface] Dialog Box
“Chip” is the default value for [Operation mode] under the [Target] category, and the default value for “Blank
Check before Erase” in the [Command Options] category is “Valid”. And the default value for “Verify after
Program” in the [Command Options] category is “Valid”.
Clicking the Complete button saves the project file and displays the main window.
Figure 4-14. [Information Settings] Dialog Box
User’s Manual 58

(2) Selection of program file
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
Select the program file, following the steps to described below.
Click the Browse… button in “User/Data area:” of the program file area to open the [Open File] dialog box.
Select “Sample.hex” in the [Open File] dialog box, and then click the Open button to open the main
window.
(3) Execution of [Autoprocedure (E.P)] command
Click the [Microcontroller] menu and select the [Autoprocedure (E.P)] command. A check mark is then
placed on the left of the command, and the command is assigned to the Start button. After clicking the Start
button, execute the following commands in the following order for UPD78F1166: [Blank Check] command,
[Erase] command (if there are no blanks), [Program] command, and [Verify] command.
Figure 4-15. Completion of [Autoprocedure (E.P)] Command Execution
User’s Manual 59

4.3.5 System shutdown procedure
CHAPTER 4 HOW TO USE EZ-CUBE WITH 78K0R MICROCONTROLLER
Terminate flash programming and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Terminating the RFP
Terminate the RFP if you are not going to perform programming to other devices.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
When the power select switch is set to ″T″, the step of (4) Unplugging the target cable can be performed
before this step.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
4.3.6 Cautions on flash programming
This section describes the cautions for flash programming. Be sure to read the following for the proper use of
EZ-CUBE.
• To improve the writing quality, fully understand, verify, and evaluate the following items before using EZ-CUBE.
- Circuits are designed as described in the user's manuals for the device and EZ-CUBE.
- The device, RFP and EZ-CUBE are used as described in each user's manual.
- The power supplied to the target system is stable.
User’s Manual 60

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
This chapter describes how to use EZ-CUBE when performing on-chip debugging and flash programming for a
R8C microcontroller.
On-chip debugging is a method to debug a microcontroller mounted on the target system, using a debug function
implemented in the device. Since debugging is performed with the target device operating on the board, this method
is suitable for field debugging.
Flash programming is a method to write a program to the flash memory embedded in a device. Erasing, writing
and verifying the program can be performed on-board with the device.
Please update firmware for R8C at first. Refer to description (1) to (3) on the following order. For detail, refer to 1.4
Firmware update.
(1) Connect EZ-CUBE to the host machine. Do not connect EZ-CUBE to the target system.
(2) Start the EZ-CUBE firmware update tool”QBEZUTL.exe”. Select firmware of R8C (R8C_OCD_FW.hex).
(3) Click the [Start] button. Start to update the EZ-CUBE firmware.
Read the following chapters if you are using EZ-CUBE for the first time with a R8C microcontroller as the target
device.
5.1 Target System Design
For communication between EZ-CUBE and the target system, communication circuits must be mounted on the
target system. This section describes the circuit design and mounting of connectors.
5.2 On-Chip Debugging
This section describes the system configuration and startup method to perform on-chip debugging with
EZ-CUBE.
5.3 Flash Programming
This section describes the system configuration and startup method to perform flash programming with
EZ-CUBE.
User’s Manual 61

5.1 Target System Design
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
This section describes the target system circuit design required for on-chip debugging and flash programming.
Figure 5-1 presents an overview of the EZ-CUBE communication interface. As shown on the left side of the
figure, EZ-CUBE performs serial communication with the target device on the target system. For this
communication, communication circuits must be mounted on the target system. Refer to this section to design
circuits appropriately.
Target device
Target system
Figure 5-1. Outline of Communication Interface
communication
(MODE/RESET)
Communication circuits
must be mounted on
.
the target system. .
RENESAS
EZ-CUBE
EZ-CUBE
USB
communication
Host machine
User’s Manual 62

5.1.1 Pin assignment
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
This section describes the interface signals used between EZ-CUBE and the target system. Table 5-1 lists the
pin assignment. Table 5-2 describes the functions of each pin.
Pin No. Pin name Note
1 GND
2 RESET_IN
3 Vcc
4 N.C
5 N.C
6 N.C
7 N.C
8 MODE
Note Signal names in EZ-CUBE
Pin Name IN/OUT Note
Table 5-1. Pin Assignment
Target interface
connector
Table 5-2. Pin Functions
7
8
5
Description
3
6 4
GND P Ground potential
Target Vcc (5V) P (OUT) Positive power supply
MODE IN/OUT Pin used to transmit/receive command/data between the target device
RESET_IN IN/OUT Pin used to input reset signal from the target system
Note As seen from EZ-CUBE
User’s Manual 63
1
2

5.1.2 Circuit connection example
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
Refer to Figure 5-2 and design an appropriate circuit.
Caution The constants described in the circuit connection example are reference values. If you perform
flash programming aiming at mass production, thoroughly evaluate whether the specifications of
the target device are satisfied.
Vcc
MODE (Pin8)
RESET
Vss
5.1.3 Connection of pin
Figure 5-2. Recommended Circuit Connection
Vcc
Vcc
Vcc
User logic
circuit
2.54 mm pitch 8-pin
general-purpose connector
Pull-up resistor 4.7KΩ ±10%
Pull-up resistor
4.7KΩ or more
User System
*
MODE
RESET
*: Buffer with Open-Collector
(1) MODE pin
The EZ-CUBE emulators use the MODE pin for MCU control and forced break control.
Do not connect a capacitor etc. to this pin.
Figure 5-3. Connection of the Emulator and the MODE Pin
MCU
User’s Manual 64

(2)RESET# pin
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
The RESET#
pin is used by the emulator for outputting “L” and monitoring pin states. Therefore, use an
open-collector
output buffer or a CR reset circuit as the reset circuit for the user system. The recommended pull-up
value is 4.7 kΩ or more.
The MCU can be reset
by outputting “L” from the emulator. However, if the reset IC output is “H”, the
user
system reset circuit cannot be set to “L”. As such, the emulator will not operate normally.
(3)Other
pins
Figure 5-4. Connection of the Emulator and the RESET Pin
- Connect Vss
and Vcc to the Vss and Vcc of the MCU, respectively.
- The amount of voltage input to Vcc must be within the specified range
of the MCU.
- Do not connect anything to the N.C. pin
5.1.4 Mounting connector onto target system
The
connector must be mounted on the target system for connecting EZ-CUBE with the target system. 2.54
mm pitch 8-pin general-purpose connector can be used.
Compact connectors and loose-wire cables are also available as options.
User’s Manual 65

5.2 On-Chip Debugging
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
This section describes the system configuration, startup/shutdown procedure and cautions for debugging when
on-chip debugging is performed with EZ-CUBE.
5.2.1 Debug functions
Table 5-3 lists the debug functions when a R8C microcontroller is the target device.
Table 5-3. Debug Functions
Functions Specifications
Target device R8C/3x Series R8C/35M Group
Operation mode Single mode
Operating frequency range
Download Available
R8C/3x Series R8C/L3AM, LA8A Group
Maximum operating frequency :20MHz
Minimum operating frequency :32.768KHz
Execution Go, Step In, Step Over, CPU Reset, Restart
Break functions
Break function
- Hardware break (before break), 8 points
- Date access break (1 points)
- Event A:Comparison and access condition (R, W, R/W) can be set.
- Software breakpoint (up to 256 points)
- Forced break
Cause of break Cause of break display
User interface 1-wire clock asynchronous series interface (Use MODE pin with communication)
MCU resources to be used
Target system voltage
- ROM: 2KB[*1]
- Stack 8 bytes
- Hardware break (before break) - BRK interrupt
- Vector area (BRK instruction, address match, single-step, address break)
2.7 to 5.5 V (depends on the target device)
User’s Manual 66

5.2.2 System configuration
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
Figure 5-5 illustrates the system configuration for on-chip debugging.
Target device
Target device
Host machine
Products with USB ports
Software
Figure 5-5. System Configuration for On-Chip Debugging
EZ-CUBE
Includes CubeSuite+ for China, USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory) or target connector (sold separately)
User’s Manual 67

5.2.3 System startup procedure
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform on-chip debugging. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• CuebSuite+ for China
• USB driver
(2) Switch setting
SW-1: Select switch to ″M2″.
SW-2: Select switch to ″Int. Clock″.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″R8C″.
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The mode LED glows red after connection.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) Debugger startup
Start the debugger.
For the operation after this step, refer to the user's manual for CubeSuite+.
If the debugger does not start normally or the operation is unstable, the possible causes may be the following.
• Communication error between EZ-CUBE and target system
Whether firmware is update.
Whether switch is selected normally.
Whether communication is performed normally.
• Unsupported software (debugger, device file, or firmware) is used
The software used may not support debugging of the target device.
• Defect of EZ-CUBE
EZ-CUBE may have a defect.
User’s Manual 68

5.2.4 System shutdown procedure
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
Terminate debugging and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Debugger termination
Terminate the debugger.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
5.2.5 Notes on Using the EZ-CUBE Emulator
5.2.5.1 MCU resources used by the emulator
(1) Program area for the emulator
Table 5-4 list the program area for the emulator. Do not change this area, otherwise the emulator will not
control the MCU. In this case, disconnect the debugger and then reconnect it.
Table 5-4. Program Area for the Emulator
Notes 1. The emulator rewrites the OFS, OFS2 and ID code areas
2. Start the debugger. Right-click on [R8C EZ-CUBE Emulator (Debugging Tool)] on [Project Tree], and
select [Property] of the R8C EZ-CUBE Emulator. Select the [Debug Tool Setting] tab. It is located under
[System]. Specify the area which will not be used by the user system.
(2) Pins used by the EZ-CUBE emulator
The emulator controls the MCUs by using the following pins depending on the usage.
- RESET# pin and MODE pin
User’s Manual 69

(3) Interrupts (unusable)
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
The BRK instruction interrupt, address match interrupt, single-step interrupt and address break interrupt
are used by the EZ-CUBE emulator program.
Therefore, make sure the user program does not use any of these interrupts. The emulator changes these
interrupt vector values to the values to be used by the emulator. No problems occur if the interrupt vector
values are written in the user program. These vector addresses cannot be rewritten in the [Memory] panel.
(4) Stack area used by the EZ-CUBE emulator
The emulator uses up to 8 bytes of the stack pointer (ISP) during a user program break. Therefore, set
aside 8 bytes for the stack area.
(5) SFRs used by the EZ-CUBE emulator program
The SFRs listed in Table 5-5 are used by the EZ-CUBE emulator program as well as the user program.
- Do not change the value in the [Memory] panel, etc., by other than the user program. If register
contents are referred to, a value that has been set in the EZ-CUBE emulator program will be read out.
Table 5-5 SFRs Used by the EZ-CUBE Emulator Program (1)
The SFRs listed in Table 5-6 are used by the EZ-CUBE emulator program, not the user program. Do not
change the values, otherwise the EZ-CUBE cannot control the MCU.
Table 5-6 SFRs Used by the EZ-CUBE Emulator Program (2)
Notes 1. When debugging with the EZ-CUBE emulator, the high-speed on-chip oscillator does not stop
although the options for high-speed on-chip oscillator enable bit are available and FRA00 can be
set to “high-speed on-chip oscillator off”. To check the functions of low power consumption etc. with
high-speed on-chip oscillator off, make the evaluation with the final products or system
manufactured by you in which only the user program is written to the MCU and the emulator is
disconnected.
If the high-speed on-chip oscillator frequency or the frequency control register needs to be
changed, be sure to do that change in the user program. If such changes are made in the [Memory]
panel, etc., the EZ-CUBE emulator will become uncontrollable.
2. Not applicable for the R8C/LA8A.
3. Only applicable for the R8C/L3AM. The bit value is always “1” when the register is used by
the EZ-CUBE emulator.
User’s Manual 70

(6) Option function select area
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
The EZ-CUBE emulator sets each of bit 0 and bit 7 of the option function select register (OFS: 0FFFFh)
to 1b. Although these addresses can be rewritten and the changed values can be referred to in the
[Memory] panel, etc., the changed values for bit 0 is invalid.
- b0: Watchdog timer start select bit 1: Watchdog timer is stopped after reset.
- b7: Count source protection mode after reset select bit 1: Count source protect mode disabled
after reset
Also, the emulator sets the lower 4 bits of the option function select register 2 (OFS2: 0FFDBh) to
1111b.
- b1, b0: Watchdog timer underflow period set bit 11: 3FFFh
- b3, b2: Watchdog timer refresh acknowledgement period set bit 11: 100%
Watchdog timer:
During the user program halt, the EZ-CUBE emulator program refreshes the watchdog timer. Note
that if the user program uses the watchdog timer, the watchdog timer will be refreshed by the
EZ-CUBE emulator program during the user program halt, making the refresh timing differ from the
actual operational timing.
Also, note that the watchdog timer is not refreshed during the execution of the user program.
Count source protection mode:
Count source protection mode cannot be debugged with the EZ-CUBE emulator.
(7) Registers initialized by the EZ-CUBE emulator
When the system is launched, the emulator initializes the CPU registers as shown in Table 5-7.
(8) RAM initialization
Table 5-7 EZ Emulator Register Initial Values
Note that the EZ-CUBE emulator initializes part of the MCU's internal RAM area (00400h-004FFh) with
"00h" at startup.
(9) MCU reserved area
The addresses not defined in the MCU hardware manual are a reserved area. Do not change the content
of the reserved area.
If changed, the EZ-CUBE emulator will not control the MCU.
User’s Manual 71

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
- The value of this area is undefined when referenced in the [Memory] panel.
- In this area, the [Memory] panel's search, compare and move functions do not work normally.
(10) DTC during a user program halt (It corresponds excluding the R8C/LA8A group. )
When the user program halts, data transfer using DTC is prohibited.
However, the DTC interrupt request itself does not stop. Therefore, the DTC interrupt request occurred
during the user program halt will be executed when the user program is restarted.
(11) Note on internal power low consumption
Make sure that bit 0 of voltage detect register 2 (VCA2) for the EZ-CUBE emulator is set to "0: Low
consumption disabled".
If "1" is selected, the emulator will not control the MCU.
(12) Debugging the functions to reduce power consumption
When debugging the low-current-consumption read mode, do not operate windows until the program
stops at the breakpoint by setting the breakpoint at the line of the program which will be executed after the
mode is cancelled.
When debugging the function to stop the flash memory, do not operate windows until the program stops
at the breakpoint by setting the breakpoint at the line of the program which will be executed after the
function is cancelled.
(13) Notes on accessing the SFR areas
You can reference or set the contents of the SFR areas in the [Memory] panel or the [IO] panel. Note the
followings.
- When accessing the special registers
You may not be able to access some special registers successfully during the user program halt Note .
These registers include:
- Access prohibited addresses
- Registers for which access order is specified from high-order byte to low-order byte
- Registers that can be accessed only by a specific instruction
- Registers whose bus width specification does not match the bus width set in the [Memory] panel
- Registers that can be accessed on conditions (one of which is that fOCO-F must be faster than the
CPU clock to access the register)
Note Follow the instructions in the hardware manual of the target MCU to access to the SFR areas.
5.2.5.2 Reset
(1) Reset function
The power-on reset and the voltage monitor 0 cannot be used. If either reset is executed, the
EZ-CUBE emulator becomes uncontrollable.
Do not stop the user program while the reset pin remains in the "L" state. A timeout error will occur.
(2) Reset vector address
During a debug with the EZ-CUBE emulator, the reset vector addresses are used by a program for
the emulator. While the user program is halted, the values set in a downloaded program or the [Memory]
panel can be referenced. But, when the user program is being run, the values set by a program for the
emulator are displayed. If a reset vector address value is set while the user program is halted, only the
User’s Manual 72

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
emulator's internal cache is updated.
(3) Behavior after a reset
If the MCU is reset while the user program is being run, the EZ-CUBE emulator program is entered into
temporarily before the user program restarts (see Table 5-8). Therefore, there is a time lag until the user
program starts after a reset. Also, note that the behavior is different between a hardware reset (RESET#)
and other resets, as shown in the table below Note1 .
Table 5-8 Behavior when the MCU Is Reset during the Execution of the User Program and It Is Restarted
Notes 1. Hardware break points (before break) can be set or deleted during the execution of the user
program, but hardware breaks (before break) that are set during the execution of the user
program are initialized by a reset.
2. If a watchdog timer reset or an S/W reset is made during the execution of the user program,
hardware breaks (before break) (Channel 0 to Channel 3) are disabled (no break occurs)
because the SFRs are initialized.
(4) Watchdog timer reset
The watchdog timer continues counting even while the user program is halted, with its counts
refreshed in a program for the emulator.
Therefore, if an underflow or other abnormal condition occurs immediately after the user program
breaks, causing the watchdog timer to be reset immediately before it is refreshed, the emulator may
become uncontrollable.
(5) Reset-related limitations
Do not perform a hardware reset (RESET#) while the user program is halted. The EZ-CUBE emulator
will not control the MCU. Note that if a reset is asserted from the MCU pin while the user program is halted,
the contents of the CPU registers are not initialized and their values as of the time the user program has
stopped or those set in the CPU register panel are prioritized.
(6) Contentions
If contention occurs between a reset (hardware reset (RESET#), watchdog timer reset, etc.) and
operations by the EZ-CUBE emulator (memory access in the [Memory] panel, etc.), the emulator may run
out of control. Error messages such as a timeout error are displayed.
Also, a message box asking whether to issue a system reset or not is displayed. Clicking the [Yes]
button initializes the emulator and stops the user program. Clicking the [No] button neither initializes the
emulator nor stops the user program. After clicking either button, you can continue the debugging.
Caution If the automatic memory update is enabled in the [Memory] or [Watch] panel, do not perform a
hardware reset to the MCU. Otherwise communications with the MCU will be lost and the EZ
–CUBE emulator will run out of control.
User’s Manual 73

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
5.2.5.3 Internal ROM Area (Flash Memory)
(1) Changing the Internal ROM Area
When changing the contents of the MCU's internal ROM without downloading from the emulator
debugger, only the EZ-CUBE emulator's internal cache is updated and the changed contents are reflected
in the MCU immediately before the user program starts running.
(2) Notes on debugging in CPU rewrite mode
(a) Unrewritable area in CPU rewrite mode
When debugging in CPU rewrite mode, do not rewrite CPU for the internal ROM area containing the
following areas. If these areas are rewritten, the EZ-CUBE emulator will not control the MCU. CPU rewrite
can be executed only for the data area.
- Fixed interrupt vector area
- Area containing the emulator program
- Block 3 in program ROM (except for the R8C/LA8A. See the table below.)
MCUs Applicable areas
4 KB ROM version -
8 KB ROM version -
16 KB ROM version -
24 KB ROM version Block 3: 0A000h-0BFFFh
32 KB ROM version -
48 KB ROM version Block 3: 08000h-0BFFFh
64 KB ROM version Block 3: 08000h-0BFFFh
96 KB ROM version -
128 KB ROM version -
(b) Operation in CPU rewrite mode
- When debugging in the CPU rewrite mode, do not halt the user program while the CPU rewrite
mode is enabled or while in the erase suspend state. And do not perform a step execution of the instruction
which enables a CPU rewrite mode or enters an erase-suspend state. If halted, the EZ-CUBE emulator
may not control the MCU. In addition, disable the automatic update in the [Watch] panel or fix the display in
the [Memory] panel before running the program so memory accesses do not occur during an execution.
- To check the internal ROM area after rewriting the internal ROM in the CPU rewrite mode, halt the
user program after disabling the CPU rewrite mode and refer to the [Memory] panel, etc. If CPU rewrite can
be executed for the data flash area, and erase process can be suspended, do not use S/W breaks.
- When rewriting the flash memory in the program area, start the debugger. Right-click on [R8C EZ
–CUBE Emulator (Debugging Tool)] on [Project Tree], and select [Property] of the R8C EZ-CUBE Emulator.
Select the [Debug Tool Setting] tab. "Debugging the program re-writing the internal flash“ is located under
[System]. Then, select "Yes".
Caution 1. When [Debugging the program re-writing the internal flash.] is selected, do not rewrite
User’s Manual 74

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
the internal ROM area in the [Memory] panel, etc. Also note that a S/W break cannot be
used when [Debugging the program re-writing the internal flash.] is selected.
2. When debugging a program in CPU rewrite mode, memory reference or modification
functions can be used. However, do not use these functions in the following condition.
• While write instruction is being executed to the register which requires continuous writing
(ex. FMR13 bit) The MCU does not recognize the writing is continuously executed if the
write instruction is interrupted by the memory reference or modification process.
(3) Note on rewriting flash memory by the EZ emulator
Do not reset nor execute debugging operations to the MCU while the internal ROM (flash memory) is being
written by the EZ-CUBE emulator. If the MCU is reset or debugged when rewriting the flash memory, the user
program or the EZ-CUBE emulator program may be disrupted.
Flash memory rewrite occurs:
- When downloading the user program
- After setting software breaks in the internal ROM area and performing an operation for executing
the user program
- After canceling software breaks in the internal ROM area and performing an operation for
executing the user program
- After rewriting the value of the internal ROM area in the [Memory] panel and performing an
operation for executing the user program
(4) Flash memory during the user program execution
While the user program is being run, the internal ROM area cannot be changed in other than the user
program (in the memory panel, etc.).
(5) MCUs used for debugging
When debugging, the Flash memory is frequently rewritten by the EZ-CUBE emulator. Therefore, do not
use an MCU that has been used for debugging in products. Also, as the EZ-CUBE emulator program is written
to the MCU while debugging, do not save the contents of the MCU Flash memory which were used for
debugging nor use them as the ROM data for products.
(6) Flash memory ID code
This MCU function prevents the Flash memory from being read out by anyone other than the user.
The ID code written to the ID code area of the MCU (see Table 5-9) must match the one entered for the
"ID code" in the [Connect Settings] tab, otherwise the debugger cannot be launched. Note that when the ID
code is FFh, FFh, FFh, FFh, FFh, FFh, FFh, the ID code is regarded as undefined. In this case, the ID code is
automatically authenticated.
The values written into the ID code area differs depending on the mode.
- [Debugging mode] : FFh, FFh, FFh, FFh, FFh, FFh, FFh (regardless of the contents of the
downloaded user program)
Caution If the ID code written to the ID code area of the MCU matches the one entered for the [ID Code]
in the [Flash] Category displayed at emulator debugger startup, the EZ emulator writes FFh, FFh,
FFh, FFh, FFh, FFh, FFh to the ID code area.
User’s Manual 75

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
Table 5-9 ID Code Storage Area
Address Description
FFDFh First byte of ID code
FFE3h Second byte of ID code
FFEBh Third byte of ID code
FFEFh Fourth byte of ID code
FFF3h Fifth byte of ID code
FFF7h Sixth byte of ID code
FFFBh Seventh byte of ID code
5.2.5.4 Operation during a user program halt
(1) Operation clock during a user program halt
When the user program halts, the emulator changes the CPU clock to the internal high-speed on-chip
oscillator clock to operate.
However, the peripheral features operate with the clock specified by the user program.
(2) Peripheral I/Os during a user program halt
During a user program halt, the maskable interrupt request cannot be accepted, because the emulator
disables interrupts. However, since peripheral I/Os continue to run, the interrupt request is accepted
immediately after the user program execution is started.
For example, a timer interrupt is not accepted although the timer continues to count when a user
program is stopped by a break after the timer started.
(3) [CPU Register] panel and [Memory] panel during a user program halt
If the CPU register values are changed in the [CPU Register] panel or the flash memory contents are
changed in the [Memory] panel, only the values of the emulator's internal cache are reflected while the user
program is halted. The changed register values or memory contents are reflected in the MCU immediately
before the user program starts running.
5.2.5.5 Final evaluation of the program
Before entering the mass-production phase, be sure to perform a final evaluation of the program singly,
without the EZ-CUBE emulator connected.
5.2.5.6 Debug functions
(1) Memory access
Checksum
The vector area, ID code area and the OFS, OFS2 areas have their values rewritten by the emulator, so
be aware that their checksums do not match. For the reset vector addresses also, although downloaded
values are displayed in the [Memory] panel, etc., be aware that they are the emulator's internal values in the
cache, and that the values set in the actual flash memory are those that were specified in the emulator.
(2) Software break functions
(a) Setting-inhibited area
Software breaks cannot be specified in other than the MCU's internal RAM and internal ROM areas.
User’s Manual 76

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
(b) Notes on software breakpoints
When you change a program in the [Editor] panel and download that program for the MCU, the addresses
at which you've set software breaks may not be corrected normally, depending on changed contents. For this
reason, it is possible that the addresses at which software breaks are set will shift.
After the user program is downloaded, check again the addresses at which software breaks are set.
(c) Memory reference during the user program execution
When the instruction of the address where a S/W breakpoint was placed is displayed in the [Memory] panel,
what is displayed is not “BRK” instruction (00h).
(d) User program execution from the address at which a software break is set
When the user program is executed from the address at which a software break is set, the relevant address
(i.e., the user program start address) is stepped through before the user program is run. Therefore, the
program behaves differently, with regard to the execution time and interrupts, than it would when no software
breaks are set.
(3) Step execution
(a) Limitations during the step execution
During stepped execution, software breaks and on-chip breaks are invalid.
(b) Step out execution
Stepping out of a function that uses a jump instruction (i.e. not a subroutine-return instruction) to return
to the origin of the call is not possible.
(c) Note on using automatic memory update
When the automatic memory update is enabled in the [Memory] or [Watch] panel, do not execute step
out or multiple-step. Otherwise, it will take longer to update memory data and the operation will be delayed.
(d) Exceptional step execution
ⅰ ) Software interrupt instruction
Step execution cannot be performed in the internal processing of instructions (undefined, overflow,
BRK and INT) which generate a software interrupt continuously in the program (see Figure 5-6).
ⅱ ) INT instruction
Figure 5-6 Example of Software Interrupt Instruction
User’s Manual 77

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
To debug the user program with the INT instruction, set a software break for the internal processing
of the INT instruction and execute the program with the GO command (see Figure 5-7).
ⅲ ) Other: Flag manipulating instructions
Figure 5-7 Example of INT Instruction
The following instructions, when single-stepped, only manipulate a flag in the EZ-CUBE emulator,
with no MCU operations involved.
Therefore, when these instructions are executed, be aware that the Start/Stop function does not work.
LDC src, FLG
STC FLG, dest
LDINTB src
(4) Other debug functions
(a) "Go to Here" function
The "Go to Here " function is actualized using an hardware break (before break) . When you execute the "Go
to Here" command, all the hardware break point (before break) and on-chip breaks you set become invalid.
When executing the program in steps from the address at which it stopped after being executed as specified by
[Go To Here] function, and there exist a hardware break set at that address, step execution may not be possible
(the PC will not advance).
Cancel the hardware break before performing step execution.
In addition to the [Go To Here] function, there are cases where you must cancel the hardware break before
performing step execution from the address at which the program has stopped. Those cases involve the use of the
following two functions.
・ CPU reset that is performed when [Yes] is selected in the [Execute to the specified symbol after CPU
Reset] property
・ [Step Over]
As shown below, if, while a hardware break is set to the address following a JSR (or JSRI, INT, INTO, UND)
instruction, the step over execution of instruction (a) is performed, the subsequent attempt to perform the step
execution of instruction (b) fails.
JSR SUB

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
If, while a hardware break is set to an RTS instruction (return-from-subroutine instruction), a [Return Out]
function is used in the sub routine, the program may break at the RTS instruction.
Do not set a hardware break to an RTS instruction when using the [Return Out] function.
(b) Debugging in stop mode or wait mode
When debugging in stop mode or wait mode, do not operate windows until the program stops at the
breakpoint by setting the breakpoint at the line of the program which will be executed after the stop mode or wait
mode is cancelled.
And do not perform a step execution of the instruction shifting to stop mode or wait mode.
Also, if memory contents are referenced or changed during the stop mode or wait mode, the program.after
exiting the stop or wait mode and accessing the MCU memory.restarts from the instruction next to the one by
which it was placed into the stop or wait mode. If the program enters the stop or wait mode in the middle of a
memory access, a reference or a change of memory contents may not be performed normally.
Therefore, disable the automatic update in the [Memory] panel or [Watch] panel or fix the display in the
[Memory] panel before running the program, and do not make refresh operations during an execution so memory
accesses do not occur during user program execution.
When the program is forcibly stopped in stop mode or wait mode, these modes will be cancelled.
(c) Watch dog timer in user system
If the reset circuit of the user system has a watchdog timer, disable it when using the emulator.
(d) Hardware breakpoint change executing program
Do not set or delete a hardware break point (before break) during program execution to reset a pin from
the target board.
If the pin is reset during program execution, the hardware break you set will not occur and the hardware
break you delete will occur.
If the pin is not reset during program execution, the hardware break will occur properly according to
hardware break settings.
Once the program is halted after setting or deleting a hardware break point, the hardware break occurs
as you set even when the pin is reset.
5.2.5.7 Communication Baud Rate
- When you have selected the [Data flash area] for the debug monitor location, use a 250000 bps or lower
communication baud rate.
- The baud rate of 57600 bps or below is designated for checking purpose in case there is a failure in the
connection with the emulator.
With such a low baud rate, it takes a long time to write into the flash memory of the target MCU, and the
emulator debugger may appear to be giving no response.
Also note if the data of 1024 bytes or larger is handled when displaying the memory contents or in memory
fill function, a time-out error may occur because the communication takes up much time.
User’s Manual 79

5.3 Flash Programming
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
This section describes the system configuration and startup/shutdown procedure when flash programming is
performed for a R8C microcontroller, using EZ-CUBE.
5.3.1 Specifications of programming function
Table 5-10. Specifications of Programming Function
Functions Specifications
Host interface USB 2.0
Target interface UART (1-wire mode)
Target system voltage 2.7 to 5.5 V (depends on the target device)
Clock supply Internal high-speed oscillation clock is used
Power supply 5 V ±0.3 V (maximum current rating: 100 mA)
Acquisition of device-specific
information
Security flag setting Available
Parameter file for Renesas Electronics is used (*.PRR)
Standalone operation Unavailable (must be connected to host machine)
Note: WriteEZ5 does not support Windows 7.
5.3.2 System configuration
Figure 5-8 illustrates the system configuration for flash programming.
Target device
Host machine
Products with USB ports
Software
Figure 5-8. System Configuration for Flash Programming
EZ-CUBE
Includes the WriteEZ5 USB driver, parameter files, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory) or target connector (sold separately)
User’s Manual 80

5.3.3 System startup procedure
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform flash programming. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• WriteEZ5
• USB driver
• Parameter file
(2) Switch setting
SW-1: Select switch to ″M2″.
SW-2: Select switch to ″Int. Clock″.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″R8C″
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The power is always supplied after EZ-CUBE is connected to the host machine with the USB cable.
Caution Do not change the switch setting while the USB cable is connected.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) WriteEZ5 startup
Start the WriteEZ5.
For detailed usage of the WriteEZ5, refer to the WriteEZ5 User's Manual.
User’s Manual 81

5.3.4 Usage examples
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
This section describes a series of basic operations using the WriteEZ5, using the R5F21356M as an example.
The operations from execution of the [Autoprocedure (EPV)] command to programming for the target device are
described. For other commands and their applications, refer to the WriteEZ5 User's Manual.
The conditions used for a series of operations in this section are as follows.
Target device: R5F21356M
Power supply voltage: 5 V±0.3V (supplied from EZ-CUBE)
Switches: SW-1: M2
SW-2: Int.Clock
SW-3: Debug Mode
SW-4: 5
SW-5: R8C
Parameter file: R5F21356M.prr
Clock setting: None (internal high-speed oscillation clock is used)
Operation mode: chip
Program file: sample.hex
Command options: [Blank check before Erase] selected
[Read verify after Program] selected
User’s Manual 82

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
(1) Setting of programming environment
Set the programming environment, following the steps to described below.
Click the [Device] menu on the menu bar and then click [Setup...].
The Device Setup dialog box appears, in which the [Standard] tab is active.
Figure 5-9. [Standard] Tab of Device Setup Dialog Box
Click the PRM File Read button to open the Parameter File Select dialog box. Select the parameter
file for the target device and then click the Open button.
Set the items in the [Host Connection], [Operation Mode] and [Supply Oscillator] areas, in accordance
with your programming environment. The following figure shows an example.
Figure 5-10. [Standard] Tab of Device Setup Dialog Box After Setting
Switch to the [Advanced] tab. Set the items in the [Command options] and [Security flag settings] areas,
in accordance with your programming environment. For detail, refer to the WriteEZ5 User's Manual.
User’s Manual 83

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
By clicking the OK button, the programming environment is set and the Device Setup dialog box is
closed. The main window appears as follows.
Figure 5-11. Completion of Programming Environment Setting
User’s Manual 84

(2) Selection of program file
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
Select the program file, following the steps to described below.
Click the [File] menu on the menu bar and then click [Load...].
The program file select dialog box appears.
Select the program file for the target device and then click the Open button.
Figure 5-12. Completion of Program File Selection
User’s Manual 85

CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
(3) Execution of [Autoprocedure (EPV)] command
Click the [Device] menu on the menu bar and then click [Autoprocedure (EPV)].
The [Blank Check], [Erase] (if the flash memory in the target device is not blank), [Program], and [Verify]
commands are executed for the target device sequentially. When the command execution is completed
normally, the following window appears.
Figure 5-13. Completion of [Autoprocedure (EPV)] Command Execution
User’s Manual 86

5.3.5 System shutdown procedure
CHAPTER 5 HOW TO USE EZ-CUBE WITH R8C MICROCONTROLLER
Terminate flash programming and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Terminating the WriteEZ5
Terminate the WriteEZ5 if you are not going to perform programming to other devices.
Remark When the WriteEZ5 is terminated, the setting information is saved. Due to this file, the same
setting is maintained when the WriteEZ5 is started the next time.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
When the power select switch is set to ″T″, the step of (4) Unplugging the target cable can be performed
before this step.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
5.3.6 Cautions on flash programming
This section describes the cautions for flash programming. Be sure to read the following for the proper use of
EZ-CUBE.
• To improve the writing quality, fully understand, verify, and evaluate the following items before using EZ-CUBE.
- Circuits are designed as described in the user's manuals for the device and EZ-CUBE.
- The device, WriteEZ5 and EZ-CUBE are used as described in each user's manual.
- The power supplied to the target system is stable.
User’s Manual 87

CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
This chapter describes how to use EZ-CUBE when performing on-chip debugging and flash programming for a
RL78 microcontroller.
On-chip debugging is a method to debug a microcontroller mounted on the target system, using a debug function
implemented in the device. Since debugging is performed with the target device operating on the board, this method
is suitable for field debugging.
Flash programming is a method to write a program to the flash memory embedded in a device. Erasing, writing
and verifying the program can be performed on-board with the device.
Please update firmware for RL78 at first. Refer to description (1) to (3) on the following order. For detail, refer to 1.4
Firmware update.
(4) Connect EZ-CUBE to the host machine. Do not connect EZ-CUBE to the target system.
(5) Start the EZ-CUBE firmware update tool”QBEZUTL.exe”. Select firmware of RL78 (RL78_OCD_FW.hex).
(6) Click the [Start] button. Start to update the EZ-CUBE firmware.
Read the following chapters if you are using EZ-CUBE for the first time with a RL78 microcontroller as the target
device.
6.1 Target System Design
For communication between EZ-CUBE and the target system, communication circuits must be mounted on the
target system. This section describes the circuit design and mounting of connectors.
6.2 On-Chip Debugging
This section describes the system configuration and startup method to perform on-chip debugging with
EZ-CUBE.
6.3 Flash Programming
This section describes the system configuration and startup method to perform flash programming with
EZ-CUBE.
User’s Manual 88

6.1 Target System Design
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
This section describes the target system circuit design required for on-chip debugging and flash programming.
Figure 6-1 presents an overview of the EZ-CUBE communication interface. As shown on the left side of the
figure, EZ-CUBE performs serial communication with the target device on the target system. For this
communication, communication circuits must be mounted on the target system. Refer to this section to design
circuits appropriately.
Target device
Target system
Figure 6-1. Outline of Communication Interface
UART communication
Communication circuits
must be mounted on
.
the target system. .
RENESAS
EZ-CUBE
EZ-CUBE
USB
communication
Host machine
6.1.1 Pin assignment
This section describes the interface signals used between EZ-CUBE and the target system. Table 6-1 lists the
pin assignment. Table 6-2 describes the functions of each pin.
Pin No. Pin name Note
1 GND
2 RESET_IN
3 Vdd
4 FLMD0
5 CLK
6 RxD.
7 RESET_OUT
8 TOOL0
Note Signal names in EZ-CUBE
Table 6-1. Pin Assignment
Target interface
connector
7
8
5
3
6 4
User’s Manual 89
1
2

Pin Name IN/OUT Note
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Table 6-2. Pin Functions
Description
RESET_IN IN Pin used to input reset signal from the target system
RESET_OUT OUT Pin used to output reset signal to the target device
FLMD0 OUT Pin used to set the target device to debug mode or programming mode
RXD IN/OUT Pin used to transmit/receive command/data between the target device
TOOL0 IN/OUT Pin used to transmit/receive command/data between the target device
CLK IN Pin used to input handshake signal from the target device
N ote As seen from EZ-CUBE
6.1.2
Circuit connection example
Refer to Figure 6-2 and Figure 6-3
design an appropriate circuit.
Caution
The constants described in the circuit connection example are reference values. If you perform
flash programming aiming at mass production, thoroughly evaluate whether the specifications of
the target device are satisfied.
Figure 6-2. RL78/G12(20pin,24pin) Recommended Circuit Connection
User’s Manual 90

CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Figure 6-3. RL78/G12(30pin), RL78/G13, RL78/G14, RL78/I1A Recommended Circuit Connection
6.1.3 Connection of reset pin
This section describes the connection of the reset pin, for which special attention must be paid, in the circuit
connection
example shown in the previous section.
During on-chip debugging, a reset signal from the target
system is input to EZ-CUBE, masked, and then output
to the target device. Therefore, the reset signal connection varies depending on whether EZ-CUBE is connected.
For flash programming, the circuit must be designed so that the reset signals of the target system and EZ-CUBE
do not conflict.
Recommend automatically switching the reset signal via series resistor.
Figure 6-4 illustrates the reset pin connection described in 6.1.2 Circuit connection
example.
This connection is designed assuming that the reset circuit on the target system contains an N-ch
open-drain
buffer
(output resistance: 100Ω or less). The VDD or GND level may be unstable when the logic of
RESET_IN/OUT of EZ-CUBE is inverted, so observe the conditions described below in Remark.
Remark
Figure 6-4. Circuit Connection with Reset Circuit That Contains Buffer
EZ-CUBE
Target device
Reset connector
RESET_OUT
_RESET
VDD V
V DD
RESET_IN
R1
Make the resistance of at least R1 ten times that of R2, R1 being 10 kΩ or more.
Pull-up resistor R2 is not required if the buffer of the reset circuit consists of CMOS output.
The circuit enclosed by a dashed line is not required when only flash programming is performed.
R2
Buffer
User’s Manual 91

CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Figure 6-5 illustrates the circuit connection for the case where the reset circuit on the target system contains
no buffers and the reset signal is only generated via resistors or capacitors. Design the circuit, observing the
conditions described below in Remark.
Remark
Figure 6-5. Circuit Connection with Reset Circuit That Contains No Buffers
EZ-CUBE
RESET_OUT
RESET_IN
Make the resistance of at least R1 ten times that of R2, R1 being 10 kΩ or more.
The circuit enclosed by a dashed line is not required when only flash programming is performed.
6.1.4 Mounting connector onto target system
The connector must be mounted on the target system
for connecting EZ-CUBE with the target system. 2.54
mm pitch 8-pin general-purpose connector can be used.
Target device Reset connector
_RESET
R1 R2
Compact connectors and loose-wire cables are also available as options.
VDD DD
User’s Manual 92

6.2 On-Chip Debugging
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
This section describes the system configuration, startup/shutdown procedure and cautions for debugging when
on-chip debugging is performed with EZ-CUBE.
6.2.1 Debug functions
Table 6-3 lists the debug functions when a RL78 microcontroller is the target device.
Table 6-3. Debug Functions
Functions Specifications
Target device RL78
RL78/G12,G13,G14,I1A
Security 10 byte ID code authentication
Download Available
Execution Go, Step In, Step Over, CPU Reset, Restart
Hardware break 1 point
Software break Multiple points
User spaces used for debugging 1-wire mode:Internal ROM: 1024 bytes + 22 bytes, Internal RAM: 6 bytes Note
Function pins used for debugging TOOL0
Note For details, refer to 6.2.5 Securing of user resources and setting of security ID and on-chip debug option
byte.
6.2.2 System configuration
Figure 6-6 illustrates the system configuration for on-chip debugging.
Target device
Target device
Host machine
Products with USB ports
Software
Figure 6-6. System Configuration for On-Chip Debugging
EZ-CUBE
Includes CubeSuite+ for China, USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory)
User’s Manual 93

6.2.3 System startup procedure
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform on-chip debugging. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• CuebSuite+ for China
• USB driver
(2) Switch setting
For RL78/G12(20pin, 24pin)
SW-1: Select switch to ″M2″.
SW-2: Select switch to ″Int. Clock″.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″R8C″.
For RL78/G12(30pin), RL78/G13, RL78/G14, RL78/I1A
SW-1: Select switch to ″M2″.
SW-2: Select switch to ″Int. Clock″.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″Other″.
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
User’s Manual 94

(4) Connecting the USB cable
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The mode LED glows red after connection.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) Debugger startup
Start the debugger.
For the operation after this step, refer to the user's manual for CuebSuite+.
If the debugger does not start normally or the operation is unstable, the possible causes may be the following.
Communication error between EZ-CUBE and target system
Whether firmware is update.
Whether switch is selected normally.
Whether communication is performed normally.
• The user resource has not been secured or the security ID has not been set
To perform debugging with EZ-CUBE, the user resource must be secured and the security ID must be set.
For details, refer to 6.2.5 Securing of user resources and setting of security ID.
• Unsupported software (debugger, device file, or firmware) is used
The software used may not support debugging of the target device.
• Defect of EZ-CUBE
EZ-CUBE may have a defect.
User’s Manual 95

6.2.4 System shutdown procedure
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Terminate debugging and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Debugger termination
Terminate the debugger.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
User’s Manual 96

CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
6.2.5 Securing of user resources and setting of security ID and on-chip debug option byte
The user must prepare the following to perform communication between EZ-CUBE and the target device and
implement each debug function. If Renesas Electronics assembler or compiler is used, the items can be set by
using linker options. Refer to the descriptions on the following pages and set these items.
• Securement of memory space
The shaded portions in Figure 6-7 are the areas reserved for placing the debug monitor program, so user
programs or data cannot be allocated in these spaces. These spaces must be secured so as not to be
used by the user program. Moreover, this area must not be rewritten by the user program.
Figure 6-7. Memory Spaces Where Debug Monitor Programs Are Allocated
Note 1. In debugging, reset vector is rewritten to address allocated to a monitor program.
2. When the self programming is executed, it will be 12 bytes.
• Setting of security ID and on-chip debug option byte
This is the area for the security setting to prevent the flash memory from being read by an unauthorized person.
The security ID functions as a password for starting the debugger. The debugger starts only when the
security ID that is input during debugger startup and the security ID embedded in this area match. If the ID
codes do not match, the debugger manipulates the target device in accordance with the value set to the
on-chip debug option byte area (refer to Table 6-4).
[How to set]
An ID code is generated in the security ID area by setting the security ID when using Renesas Electronics
assembler or compiler. Select the ″Security ID″ check box and set an arbitrary ID code (10 bytes) as
shown in the figure below.
User’s Manual 97

On-chip debug option byte area
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Figure 6-8. Security ID Setting Example
This is the area for the security setting to prevent the flash memory from being read by an unauthorized person.
The debugger manipulates the target device in accordance with the set value, as shown below.
Table 6-4. On-Chip Debug Option Byte Setting and Operation
Set Value Description Remark
0x04 Debugging is disabled even if an on-chip debug This setting is available only
emulator (such as EZ-CUBE) is connected.
for flash programming and self
programming.
0x85 The on-chip flash memory is not erased no matter
how many times the security ID code authentication
fails.
-
0x84 All on-chip flash memory areas are erased if the
security ID code authentication fails.
-
Other than above Setting prohibited -
[How to set]
The following shows a setting example when using Renesas Electronics assembler or compiler. Set a value
for the Control Value text box under the ″ Use on-chip debug [-go]″ check box as shown in the figure below.
Example Setting 0x85 for control value
User’s Manual 98

(a) Securing of debug monitor area
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Figure 6-9. On-Chip Debug Option Byte Setting Example
This is the area to which the debug monitor program is to be allocated. The monitor program performs
initialization processing for debug communication interface and RUN or break processing for the CPU.
This user programs or data must not be placed in an area of 22 bytes near the on-chip debug option byte, and an
area of 512 bytes before the internal ROM end address. In addition, reset vector is rewritten to address allocated
to a monitor program.
[How to secure areas]
It is not necessarily required to secure this area if the user program does not use this area.
However To avoid problems that may occur during the debugger startup, it is recommended to secure this
area in advance, using the compiler. Figure 6-10 shows example for securing the area, using the CubeSuite+.
Set in “device” in link options tab as figure 6-10.
Figure 6-10 Example for securing the debug monitor area
User’s Manual 99

CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
(b) Securement of stack area for debugging
This area requires 4 bytes as the stack area for debugging. Since this area is allocated immediately before
the stack area, the address of this area varies depending on the stack increase and decrease. That is, 4
extra bytes are consumed for the stack area used.
Figure 6-11 illustrates the case where the stack area is increased when the internal high-speed RAM starts
from 0xFCF00.
[How to secure areas]
Figure 6-11. Variation of Address of Stack Area for Debugging
Set the stack pointer by estimating the stack area consumed by the user program + 4 bytes. Make sure that
the stack pointer does not extend beyond the internal high-speed RAM start address.
Remark Refer to the self programming manual for how to secure the stack area for self programming.
User’s Manual 100

6.2.6 Cautions on debugging
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
This section describes cautions on performing on-chip debugging for a RL78 microcontroller.
Be sure to read the following to use EZ-CUBE properly.
(1) Handling of device that was used for debugging
Do not mount a device that was used for debugging on a mass-produced product, because the flash memory
was rewritten during debugging and the number of rewrites of the flash memory cannot be guaranteed.
Moreover, do not embed the debug monitor program into mass-produced products.
(2) Flash self programming
If a space where the debug monitor program is allocated is rewritten by flash self programming, the debugger
can no longer operate normally. This caution also applies to boot swapping for such an area.
(3) Operation after reset
After an external pin reset or internal reset, the monitor program performs debug initialization processing.
Consequently, the time from reset occurrence until user program execution differs from that in the actual
device operation.
(4) Debugging with real machine running without using EZ-CUBE
If debugging is performed with a real machine running, without using EZ-CUBE, write the user program using
the RFP. Programs downloaded by the debugger include the monitor program, and such a program
malfunctions if it includes processing to make the TOOL0 pin low level.
(5) Operation when debugger starts
When the debugger is started, if the Target Device Connection setting in the Configuration dialog box of the
debugger is different from the setting for the previous debugging, the internal flash memory is erased.
(6) Debugging after program is written by flash programming
If a program is written to the internal flash memory using the RFP, on-chip debugging is disabled even if it is
enabled in the on-chip debugging option byte setting. To perform debugging of the target device after that,
erase the internal flash memory using the RFP and then download the program using the debugger.
User’s Manual 101

6.3 Flash Programming
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
This section describes the system configuration and startup/shutdown procedure when flash programming is
performed for a RL78 microcontroller, using EZ-CUBE.
6.3.1 Specifications of programming function
Table 6-5. Specifications of Programming Function
Functions Specifications
Host interface USB 2.0
Target interface UART (1-wire mode)
Target system voltage 2.7 to 5.5 V (depends on the target device)
Clock supply Internal high-speed oscillation clock is used
Power supply 5 V ±0.3 V (maximum current rating: 100 mA)
Acquisition of device-specific
information
Security flag setting Available
Parameter file for Renesas Electronics is used
Standalone operation Unavailable (must be connected to host machine)
6.3.2 System configuration
Figure 6-12 illustrates the system configuration for flash programming.
Target device
Host machine
Products with USB ports
Software
Figure 6-12. System Configuration for Flash Programming
EZ-CUBE
Includes the RFP USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory)
User’s Manual 102

6.3.3 System startup procedure
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform flash programming. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• RFP
• USB driver
(2) Switch setting
For RL78/G12(20pin, 24pin)
SW-1: Select switch to ″M2″.
SW-2: Select switch to ″Int. Clock″.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″R8C″.
For RL78/G12(30pin), RL78/G13, RL78/G14, RL78/I1A
SW-1: Select switch to ″M2″.
SW-2: Select switch to ″Int. Clock″.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″Other″.
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The power is always supplied after EZ-CUBE is connected to the host machine with the USB cable.
Caution Do not change the switch setting while the USB cable is connected.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) RFP startup
Start the RFP.
For detailed usage of the RFP, refer to the RFP User's Manual.
User’s Manual 103

6.3.4 Usage examples
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
This section describes a series of basic operations using the RFP, using the R 5 F 100LE as an example. The
operations from execution of the [Autoprocedure (E.P)] command to programming for the target device are
described. For other commands and their applications, refer to the RFP User's Manual.
The conditions used for a series of operations in this section are as follows.
Target device: R5F100LE
Power supply voltage: 5 V±0.3V (supplied from EZ-CUBE)
Switches: SW-1: M2
Voltage 5
Operation mode: chip
SW-2: Int.Clock
SW-3: Debug Mode
SW-4: 5
SW-5: Other
Program file: sample.hex
Command options: [Blank check before Erase] selected
[Verify after Program] selected
User’s Manual 104

CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
(1) Setting of programming environment
Set the programming environment, following the steps to described below.
On the taskbar, click the Start button, point to [All Programs], [Renesas Electronics CubeSuite+],
[Programming Tools], [Renesas Flash Programmer Vx.xx], and then click [Renesas Flash Programmer
Vx.xx [Basic mode]]. The [Welcome!] dialog box will open. Select [Create new workspace.] and then click
the Next button to open the [Create a new workspace] dialog box.
Figure 6-13. [Welcome!] Dialog Box
In the [Using Target Microcontroller:] list box, select “R5F100LE”. Enter any text string (such as “sample”
in this case) in the [Workspace Name:] box, and specify any folder in the [Folder:] box.
Clicking the Next button displays the [Select Communication Interface] dialog box.
Figure 6-14. Parameter File Select Dialog Box
User’s Manual 105

CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Select “Tool”, in the [Select Communication Interface] dialog box. For EZ-CUBE, the area is
fixed to “PC port No.(Renesas Virtual UART)”.
Clicking the Next button displays the [Setting Oscillator] dialog box.
Figure 6-15. [Select Communication Interface] Dialog Box
Select the [Power target from the emulator] check box, and then select “5.0 V” for [Supply voltage].
Clicking the OK button displays the [Mode Pin Settings at Connection] dialog box.
Figure 6-16. [Setting Power Supply] Dialog Box
“Chip” is the default value for [Operation mode] under the [Target] category, and the default value for “Blank
Check before Erase” in the [Command Options] category is “Valid”. And the default value for “Verify after
Program” in the [Command Options] category is “Valid”.
Clicking the Complete button saves the project file and displays the main window.
User’s Manual 106

(2) Selection of program file
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Figure 6-17. [Information Settings] Dialog Box
Select the program file, following the steps to described below.
Click the Browse… button in “User/Data area:” of the program file area to open the [Open File] dialog box.
Select “sample.hex” in the [Open File] dialog box, and then click the Open button to open the main
window.
User’s Manual 107

CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
(3) Execution of [Autoprocedure (E.P)] command
Click the [Microcontroller] menu and select the [Autoprocedure (E.P)] command. A check mark is then
placed on the left of the command, and the command is assigned to the Start button. After clicking the Start
button, execute the following commands in the following order for R 5 F 100LE: [Blank Check] command,
[Erase] command (if there are no blanks), [Program] command, and [Verify] command.
Figure 6-18. Completion of [Autoprocedure (E.P)] Command Execution
User’s Manual 108

6.3.5 System shutdown procedure
CHAPTER 6 HOW TO USE EZ-CUBE WITH RL78 MICROCONTROLLER
Terminate flash programming and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Terminating the RFP
Terminate the RFP if you are not going to perform programming to other devices.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
When the power select switch is set to ″T″, the step of (4) Unplugging the target cable can be performed
before this step.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
6.3.6 Cautions on flash programming
This section describes the cautions for flash programming. Be sure to read the following for the proper use of
EZ-CUBE.
• To improve the writing quality, fully understand, verify, and evaluate the following items before using EZ-CUBE.
- Circuits are designed as described in the user's manuals for the device and EZ-CUBE.
- The device, RFP and EZ-CUBE are used as described in each user's manual.
- The power supplied to the target system is stable.
User’s Manual 109

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This chapter describes how to use EZ-CUBE when performing on-chip debugging and flash programming for a
V850 microcontroller.
On-chip debugging is a method to debug a microcontroller mounted on the target system, using a debug
function implemented in the device. Since debugging is performed with the target device operating on the board,
this method is suitable for field debugging.
Flash programming is a method to write a program to the flash memory embedded in a device. Erasing,
writing and verifying the program can be performed on-board with the device.
Please update firmware at first. Follow step (1)-(3). For detail on update firmware, refer to 1.4 Firmware
Update.
(1) Connect EZ-CUBE to the host machine. Do not connect EZ-CUBE to the target system.
(2) Start the EZ-CUBE firmware update tool”QBEZUTL.exe”. Select firmware of V850” V850_OCD_FW.hex”.
(3) Click the [Start] button. Start to update the EZ-CUBE firmware.
Read the following chapters if you are using EZ-CUBE for the first time with a V850 microcontroller as the target
device.
7.1 Target System Design
For communication between EZ-CUBE and the target system, communication circuits must be mounted on
the target system. This section describes the circuit design and mounting of connectors.
7.2 On-Chip Debugging
This section describes the system configuration and startup method to perform on-chip debugging with
EZ-CUBE.
7.3 Flash Programming
This section describes the system configuration and startup method to perform flash programming with
EZ-CUBE.
User’s Manual 110

7.1 Target System Design
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This section describes the target system circuit design required for on-chip debugging and flash programming.
Figure 7-1 presents an overview of the EZ-CUBE communication interface. As shown on the left side of the
figure, EZ-CUBE performs serial communication with the target device on the target system. For this
communication, communication circuits must be mounted on the target system. Refer to this section to design
circuits appropriately.
UART are supported as communication modes.
The pins used for serial communication are basically the same as those of the flash memory programmer
(such as EZ-CUBE), but some devices do not support some of them.
Target device
7.1.1 Pin assignment
Figure 7-1. Outline of Communication Interface
This section describes the interface signals used between EZ-CUBE and the target system. Table 7-1 lists the
pin assignment. Table 7-2 describes the functions of each pin.
Pin No. Pin Name Note
1 GND
2 RESET_IN
3 VDD
4 FLMD0
5 CLK
6 RxD
7 RESET_OUT
8 TxD
Note Signal names in EZ-CUBE
Communication circuits
must be mounted on
the target system. .
Renesas
EZ-CUBE
Serial communication
(UART)
Target system Host machine
EZ-CUBE
Table 7-1. Pin Assignment
Target interface
connector
USB
communication
7
8
5
3
6 4
1
2
User’s Manual 111

Pin Name IN/OUT Note
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
Table 7-2. Pin Functions
Description
RESET_IN IN Pin used to input reset signal from the target system
RESET_OUT OUT Pin used to output reset signal to the target device
CLK OUT Pin used to output clock signal to the target device
FLMD0 OUT Pin used to set the target device to debug mode or
programming mode
RxD IN Pin used to receive command/data from the target device
TxD OUT Pin used to transmit command/data to the target device
Note As seen from EZ-CUBE
7.1.2 Circuit connection examples
The circuit design on the target system varies depending on the communication interface mode. Refer to the
following table and see the relevant circuit connection example.
Caution The constants described in the circuit connection example are reference values. If you perform
flash programming aiming at mass production, thoroughly evaluate whether the specifications of
the target device are satisfied.
Figure 7-2. Recommended Circuit Connection
Notes 1. This connection is designed assuming that the RESET signal is output from the N-ch open-drain buffer
(output resistance: 100Ω or less). For details, refer to 7.1.3 Connection of reset pin.
2. Connect TxD (transmit side) of the target device to RxD (receive side) of the target connector, and TxD
(transmit side) of the target connector to RxD (receive side) of the target device. Read the serial interface
pin names on the target device side as those for flash programming supported by the target device.
User’s Manual 112

7.1.3 Connection of reset pin
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This section describes the connection of the reset pin, for which special attention must be paid, in circuit
connection examples shown in the previous section.
During on-chip debugging, a reset signal from the target system is input to EZ-CUBE, masked, and then
output to the target device. Therefore, the reset signal connection varies depending on whether EZ-CUBE is
connected.
For flash programming, the circuit must be designed so that the reset signals of the target system and
EZ-CUBE do not conflict.
Automatically switching the reset signal via series resistor (recommended; described in recommended
circuit connection in the previous section)
Figure 7-3 illustrates the reset pin connection described in 7.1.2 Circuit connection examples.
This connection is designed assuming that the reset circuit on the target system contains an N-ch open-drain
buffer (output resistance: 100Ω or less). The VDD or GND level may be unstable when the logic of
RESET_IN/OUT of EZ-CUBE is inverted, so observe the conditions described below in Remark.
Figure 7-3. Circuit Connection with Reset Circuit That Contains Buffer
EZ-CUBE
RESET_OUT
RESET_IN
R1
Target Device
_RESET
R2
VDD V
Reset connector
Buffer
Remark Make the resistance of at least R1 ten times that of R2, R1 being 10 kΩ or more.
V DD
Pull-up resistor R2 is not required if the buffer of the reset circuit consists of CMOS output.
The circuit enclosed by a dashed line is not required when only flash programming is performed.
Figure 7-4 illustrates the circuit connection for the case where the reset circuit on the target system contains
no buffers and the reset signal is only generated via resistors or capacitors. Design the circuit, observing
the conditions described below in Remark.
Figure 7-4. Circuit Connection with Reset Circuit That Contains No Buffers
EZ-CUBE
RESET_OUT
RESET_IN
R1
Target Device
_RESET
Reset connector
R2
V DD
Remark Make the resistance of at least R1 ten times that of R2, R1 being 10 kΩ or more.
The circuit enclosed by a dashed line is not required when only flash programming is performed.
User’s Manual 113

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
7.1.4 Mounting connector onto target system
The connector must be mounted on the target system for connecting EZ-CUBE with the target system. A 2.54
mm pitch 8-pin general-purpose connector can be used.
Compact connectors and loose-wire cables are also available as options.
User’s Manual 114

7.2 On-Chip Debugging
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This section describes the system configuration, startup/shutdown procedure and cautions for debugging when
on-chip debugging is performed with EZ-CUBE.
7.2.1 Debug functions
Table 6-3 lists the debug functions when a V850 microcontroller is the target device and the debugger is used.
Table 7-3. Debug Functions
Functions Specifications
Target Device V850
V850ES/Jx3,V850ES/Jx3-L
Security 10-byte ID code authentication
Download Available
Execution Go, Step In, Step Over, CPU Reset, Restart
Hardware break 1 point
Software break Multiple points
RAM monitoring Available
Function pins used for debugging RXD, TXD
7.2.2 System configuration
Figure 7-5 illustrates the system configuration for on-chip debugging.
Target device
Target device
Host machine
Products with USB ports
Software
Figure 7-5. System Configuration for On-Chip Debugging
EZ-CUBE
Includes CubeSuite+ for China, USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory)
User’s Manual 115

7.2.3 System startup procedure
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform on-chip debugging. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• CuebSuite+
• USB driver
(2) Switch setting
SW-1: Select switch to ″M1″.
SW-2: Depend on the user system environment.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″Other″.
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The mode LED glows red after connection.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) Debugger startup
Start the debugger.
For the operation after this step, refer to the user's manual for the CubeSuite+.
If the debugger does not start normally or the operation is unstable, the possible causes may be the following.
• Communication error between EZ-CUBE and target system
Whether firmware is update.
Whether switch is selected normally.
Whether communication is performed normally.
• The user resource has not been secured or the security ID has not been set
To perform debugging with EZ-CUBE, the user resource must be secured and the security ID must be set.
For details, refer to 7.2.5 Securing of user resources and setting of security ID.
• Unsupported software (debugger, device file, or firmware) is used
The software used may not support debugging of the target device.
• Defect of EZ-CUBE
EZ-CUBE may have a defect.
User’s Manual 116

7.2.4 System shutdown procedure
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
Terminate debugging and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Debugger termination
Terminate the debugger.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
User’s Manual 117

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
7.2.5 Securing of user resources and setting of security ID
The user must prepare the following to perform communication between EZ-CUBE and the target device and
implement each debug function. Refer to the descriptions on the following pages and set these items in the user
program or using the compiler options.
• Securement of memory space
The shaded portions in Figure 7-6 are the areas reserved for placing the debug monitor program, so user
programs and data cannot be allocated in these spaces. These spaces must be secured so as not to be used
by the user program.
Figure 7-6. Memory Spaces Where Debug Monitor Programs Are Allocated
• Securement of serial interface for communication
The register settings, concerning UART used for communication between EZ-CUBE and the target device,
performed by the debug monitor program must not be changed.
• Security ID setting
The ID code must be embedded in the area filled with yellow (0x70 to 0x79) in Figure 7-6, to prevent the
memory from being read by an unauthorized person.
User’s Manual 118

(a) Reset vector
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
A reset vector includes the jump instruction for the debug monitor program.
[How to secure areas]
It is not necessary to secure this area intentionally. When downloading a program, however, the debugger
rewrites the reset vector in accordance with the following cases. If the rewritten pattern does not match the
following cases, the debugger generates an error.
• When two nop instructions are placed in succession from address 0
Before writing After writing
0x0 nop → Jumps to debug monitor program at 0x0
0x2 nop
0x4 xxxx
0x4 xxxx
• When two 0xFFFF are successively placed from address 0 (already erased device)
Before writing After writing
0x0 0xFFFF → Jumps to debug monitor program at 0x0
0x2 0xFFFF
0x4 xxxx
0x4 xxxx
• The jr instruction is placed at address 0 (when using Renesas Electronics compiler)
Before writing After writing
0x0 jr disp22 → Jumps to debug monitor program at 0x0
0x4 jr disp22 - 4
• The jump instruction for the debug monitor program is placed at address 0
Before writing After writing
Jumps to debug monitor program at 0x0 → No change
User’s Manual 119

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
(b) Securement of area for debug monitor program
The shaded portions in Figure 6-6 are the areas where the debug monitor program is allocated. The monitor
program performs initialization processing for debug communication interface and RUN or break processing
for the CPU. The internal ROM area must be filled with 0xFF. This area must not be rewritten by the user
program.
[How to secure areas]
It is not necessarily required to secure this area if the user program does not use this area.
To avoid problems that may occur during the debugger startup, however, it is recommended to secure this
area in advance, using the compiler.
The following shows examples for securing the area, using the Renesas Electronics compiler. Add the
assemble source file and link directive code, as shown below.
• Assemble source (Add the following code as an assemble source file.)
-- Secures 2 KB space for monitor ROM section
.section "MonitorROM", const
.space 0x800, 0xff
-- Secures interrupt vector for debugging
.section "DBG0"
.space 4, 0xff
-- Secures interrupt vector for serial communication
-- Change the section name according to serial communication mode used
.section "INTCSI00"
.space 4, 0xff
-- Secures 16 byte space for monitor ROM section
.section "MonitorRAM", bss
.lcomm monitorramsym, 16, 4 /* defines monitorramsym symbol */
• Link directive (Add the following code to the link directive file.)
The following shows an example when the internal ROM end address is 0x6ffff and internal RAM end
address is 0x6ffefff.
MROMSEG : !LOAD ?R V0x03f800{
MonitorROM = $PROGBITS ?A MonitorROM;
};
MRAMSEG : !LOAD ?RW V0x03ffeff0{
MonitorRAM = $NOBITS ?AW MonitorRAM;
};
User’s Manual 120

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
(c) Securement of communication serial interface
UART is used for communication between EZ-CUBE and the target system. The settings related to the serial
interface modes are performed by the debug monitor program, but if the setting is changed by the user
program, a communication error may occur.
To prevent such a problem from occurring, communication serial interface must be secured in the user
program.
[How to secure communication serial interface]
Create the user program observing the following points.
• Serial interface registers
Do not set the registers related to UART in the user program.
• Interrupt mask register
When UART is used, do not mask receive end interrupts Note .
Note Do not mask receive error interrupts.
• Port registers
When UART is used, do not set port registers to make the TxD and RxD pins invalid.
(d) Security ID setting
This setting is required to prevent the memory from being read by an unauthorized person. Embed a security
ID at addresses 0x70 to 0x79 in the internal flash memory. The debugger starts only when the security ID
that is set during debugger startup and the security ID set at addresses 0x70 to 0x79 match.
If bit 7 of address 0x79 is ″0″, however, debugging is disabled. In such a case, there are no methods to start
the debugger. Debugging is mainly disabled for mass-produced devices.
If the user has forgotten the security ID or to enable debugging, erase the flash memory and set the security ID
again.
[How to set security ID]
Embed a security ID at addresses 0x70 to 0x79 in the user program.
If the security ID is embedded as follows, for example, the security ID set by the debugger is
″126456789ABCDEF126D4″ (not case-sensitive).
User’s Manual 121

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
Address Value [7:0]
0x70 0x12
0x71 0x64
0x72 0x56
0x76 0x78
0x74 0x9A
0x75 0xBC
0x76 0xDE
0x77 0xF1
0x78 0x26
0x79 0xD4
If Renesas Electronics compiler is used, the security ID can be set using the Compiler Common Options
menu.
Figure 7-7. Setting Security ID
User’s Manual 122

7.2.6 Cautions on debugging
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This section describes cautions on performing on-chip debugging for a V850 microcontroller.
Be sure to read the following to use EZ-CUBE properly.
(1) Handling of device that was used for debugging
Do not mount a device that was used for debugging on a mass-produced product, because the flash memory
was rewritten during debugging and the number of rewrites of the flash memory cannot be guaranteed.
Moreover, do not embed the debug monitor program into mass-produced products.
(2) When breaks cannot be executed
Forced breaks cannot be executed if one of the following conditions is satisfied.
• Interrupts are disabled (DI)
• Interrupts issued for the serial interface, which is used for communication between EZ-CUBE and the target
device, are masked
• Standby mode is entered while standby release by a maskable interrupt is prohibited
• Mode for communication between EZ-CUBE and the target device is UART, and the main clock has been
stopped
(3) Device with which the debugger startup is slowed
When the debugger is started for the first time, chip erasure and writing of debug monitor program are
performed. The device require about a dozen seconds for these operations.
(4) Writing of debug monitor program
If the CPU operating clock setting is changed by the debugger, the debugger rewrites the debug monitor
program. At this time, it takes about a dozen seconds for this operation. When using Renesas Electronics
debugger, this specification applies when the setting in the Clock area in the Configuration dialog box.
(5) Flash self programming
If a space where the debug monitor program is allocated is rewritten by flash self programming, the debugger
can no longer operate normally.
(6) Emulation of POC function
The POC function of the target device cannot be emulated. Make sure that the power to the target system is
not shut down during debugging.
(7) Operation after reset
After an external pin reset or internal reset, the monitor program performs debug initialization processing.
Consequently, the time from reset occurrence until user program execution differs from that in the actual
device operation.
(8) Debugging with real machine running without using EZ-CUBE
If debugging is performed with a real machine running, without using EZ-CUBE, write the user program using
the RFP. Programs downloaded by the debugger include the monitor program, and such a program
malfunctions if it is not controlled via EZ-CUBE.
User’s Manual 123

7.3 Flash Programming
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This section describes the system configuration and startup/shutdown procedure when flash programming is
performed for a V850 microcontroller, using EZ-CUBE.
7.3.1 Specifications of programming function
Host interface
Target interface
Table 7-4. Specifications of Programming Function
Functions Specifications
Target system voltage
Clock supply
Power supply
Acquisition of device-specific
information
Security flag setting
Standalone operation
7.3.2 System configuration
USB 2.0
UART
2.7 to 5.5 V (depends on the target device)
8MHz clock can be supplied
Clock mounted on the target system can be used
5 V±0.3V (maximum current rating: 100 mA)
Parameter file for Renesas Electronics is used
Available
Unavailable (must be connected to host machine)
Figure 7-8 illustrates the system configuration for flash programming.
Target device
Host machine
Products with USB ports
Software
Figure 7-8. System Configuration for Flash Programming
EZ-CUBE
Includes the RFP, USB driver, and so on.
USB cable (accessory)
EZ-CUBE (this product)
8-pin target cable (accessory)
User’s Manual 124

7.3.3 System startup procedure
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This section describes the system startup procedure. Observe the following order.
(1) Preparation and installation of software
The following software is required to perform flash programming. For details on preparation and installation of
software, refer to the setup manual supplied with EZ-CUBE.
• RFP
• USB driver
(2) Switch setting
SW-1: Select switch to ″M1″.
SW-2: Depend on the user system environment.
SW-3: Select switch to ″Debug Mode″.
SW-4: Depend on the user system environment.
SW-5: Select switch to ″Other″
Caution 1. Do not change the switch setting while the USB cable is connected.
2. The maximum rating of the current is 100 mA, so do not use EZ-CUBE with the target
system with the higher current rating. The power is always supplied after EZ-CUBE is
connected to the host machine.
(3) Connecting the target system
Connect EZ-CUBE to the target system, before the power to the target system is turned on.
(4) Connecting the USB cable
Connect EZ-CUBE to the host machine, before the power to the target system is turned on.
The power is always supplied after EZ-CUBE is connected to the host machine with the USB cable.
Caution Do not change the switch setting while the USB cable is connected.
(5) Applying power to target system
Turn on power to the target system. This step is not necessary if the power select switch is set to ″5″.
(6) RFP startup
Start the WriteRFP. For detailed usage of the WriteEZ5, refer to the RFP User's Manual.
User’s Manual 125

7.3.4 Usage examples
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
This section describes a series of basic operations using the RFP, using the UPD70F3717 as an example. The
operations from execution of the [Autoprocedure (E.P)] command to programming for the target device are
described. For other commands and their applications, refer to the RFP User's Manual.
The conditions used for a series of operations in this section are as follows.
Target device: UPD70F3717
Power supply voltage: 3.3 V
Communication channel: UART 38,400 bps
Switches: SW-1: M1
SW-2: Int.Clock
SW-3: Debug Mode
SW-4: T
SW-5: Other
Clock setting: 5 MHz, x4 (oscillator on the target system side)
Operation mode: chip
Program file: sample.hex
Command options: [Blank check before Erase] selected
[Verify after Program] selected
User’s Manual 126

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
(1) Setting of programming environment
Set the programming environment, following the steps to described below.
On the taskbar, click the Start button, point to [All Programs], [Renesas Electronics CubeSuite+],
[Programming Tools], [Renesas Flash Programmer Vx.xx], and then click [Renesas Flash Programmer
Vx.xx [Basic mode]]. The [Welcome!] dialog box will open. Select [Create new workspace.] and then click
the Next button to open the [Create a new workspace] dialog box.
Figure 7-9. [Welcome!] Dialog Box
In the [Using Target Microcontroller:] list box, select “UPD70F3717”. Enter any text string (such as
“sample” in this case) in the [Workspace Name:] box, and specify any folder in the [Folder:] box.
Clicking the Next button displays the [Select Communication Interface] dialog box.
Figure 7-10. Parameter File Select Dialog Box
User’s Manual 127

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
Select “Tool”, in the [Select Communication Interface] dialog box. For EZ-CUBE, the area is
fixed to “PC port No.(Renesas Virtual UART)”.
Clicking the Next button displays the [Setting Oscillator] dialog box.
Figure 7-11. [Select Communication Interface] Dialog Box
Set the items in the [Supply Oscillator] areas, in accordance with your programming environment. The following
figure shows an example.
Figure 7-12. [Setting Power Supply] Dialog Box
User’s Manual 128

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
“Chip” is the default value for [Operation mode] under the [Target] category, and the default value for “Blank
Check before Erase” in the [Command Options] category is “Valid”. And the default value for “Verify after
Program” in the [Command Options] category is “Valid”.
Clicking the Complete button saves the project file and displays the main window.
(2) Selection of program file
Figure 7-13. [Information Settings] Dialog Box
Select the program file, following the steps to described below.
Click the Browse… button in “User/Data area:” of the program file area to open the [Open File] dialog box.
Select “sample.hex” in the [Open File] dialog box, and then click the Open button to open the main
window.
User’s Manual 129

CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
(3) Execution of [Autoprocedure (E.P)] command
Click the [Microcontroller] menu and select the [Autoprocedure (E.P)] command. A check mark is then
placed on the left of the command, and the command is assigned to the Start button. After clicking the Start
button, execute the following commands in the following order for U P D 7 0 F 3717: [Blank Check] command,
[Erase] command (if there are no blanks), [Program] command, and [Verify] command.
Figure 7-14. Completion of [Autoprocedure (E.P)] Command Execution
User’s Manual 130

7.3.5 System shutdown procedure
CHAPTER 7 HOW TO USE EZ-CUBE WITH V850 MICROCONTROLLER
Terminate flash programming and shutdown the system in the following order.
If the following order is not observed, the target system or EZ-CUBE may be damaged.
(1) Terminating the RFP
Terminate the RFP if you are not going to perform programming to other devices.
(2) Target system power shutdown
Shutdown the power supplied to the target system. This step is not necessary if the power select switch is
set to ″5″.
(3) Unplugging the USB cable
Unplug the USB cable from EZ-CUBE or the host machine.
When the power select switch is set to ″T″, the step of (4) Unplugging the target cable can be performed
before this step.
(4) Unplugging the target cable
Unplug the target cable from EZ-CUBE or the target system.
7.3.6 Cautions on flash programming
This section describes the cautions for flash programming. Be sure to read the following for the proper use of
EZ-CUBE.
• To improve the writing quality, fully understand, verify, and evaluate the following items before using EZ-CUBE.
- Circuits are designed as described in the user's manuals for the device and EZ-CUBE.
- The device, RFP and EZ-CUBE are used as described in each user's manual.
- The power supplied to the target system is stable.
User’s Manual 131