1. Renesas Technology Corp. puts the maximum effort into making semiconductor products
better and more reliable, but there is always the possibility that trouble may occur with them.
Trouble with semiconductors may lead to personal injury, fire or property damage.
Remember to give due consideration to safety when making your circuit designs, with appropriate measures such as (i) placement of substitutive, auxiliary circuits, (ii) use of nonflammable material or (iii) prevention against any malfunction or mishap.
Notes regarding these materials
1. These materials are intended as a reference to assist our customers in the selection of the
Renesas Technology Corp. product best suited to the customer's application; they do not
convey any license under any intellectual property rights, or any other rights, belonging to
Renesas Technology Corp. or a third party.
2. Renesas Technology Corp. assumes no responsibility for any damage, or infringement of any
third-party's rights, originating in the use of any product data, diagrams, charts, programs,
algorithms, or circuit application examples contained in these materials.
3. All information contained in these materials, including product data, diagrams, charts, programs and algorithms represents information on products at the time of publication of these
materials, and are subject to change by Renesas Technology Corp. without notice due to
product improvements or other reasons. It is therefore recommended that customers contact
Renesas Technology Corp. or an authorized Renesas Technology Corp. product distributor
for the latest product information before purchasing a product listed herein.
The information described here may contain technical inaccuracies or typographical errors.
Renesas Technology Corp. assumes no responsibility for any damage, liability, or other loss
rising from these inaccuracies or errors.
Please also pay attention to information published by Renesas Technology Corp. by various
means, including the Renesas Technology Corp. Semiconductor home page (http://
www.renesas.com).
4. When using any or all of the information contained in these materials, including product data,
diagrams, charts, programs, and algorithms, please be sure to evaluate all information as a
total system before making a final decision on the applicability of the information and
products. Renesas Technology Corp. assumes no responsibility for any damage, liability or
other loss resulting from the information contained herein.
5. Renesas Technology Corp. semiconductors are not designed or manufactured for use in a
device or system that is used under circumstances in which human life is potentially at stake.
Please contact Renesas Technology Corp. or an authorized Renesas Technology Corp.
product distributor when considering the use of a product contained herein for any specific
purposes, such as apparatus or systems for transportation, vehicular, medical, aerospace,
nuclear, or undersea repeater use.
6. The prior written approval of Renesas Technology Corp. is necessary to reprint or reproduce
in whole or in part these materials.
7. If these products or technologies are subject to the Japanese export control restrictions, they
must be exported under a license from the Japanese government and cannot be imported
into a country other than the approved destination.
Any diversion or reexport contrary to the export control laws and regulations of Japan and/ or
the country of destination is prohibited.
8. Please contact Renesas Technology Corp. for further details on these materials or the
products contained therein.
M3062PT3-RPD-E User’s Manual Preface
Preface
The M3062PT3-RPD-E is an emulation pod for the M16C/60 Series M16C/62P Group and M16C/30 Series M16C/30P Group
of 16-bit MCUs. It is used with a PC4701 emulator (excluding the PC4701L and PC4700L).
This user's manual mainly describes specifications of the M3062PT3-RPD-E emulation pod and how to setup it. For details on
the emulator main unit and emulator debugger, which are used with the M3062PT3-RPD-E, refer to each product's user's
manual.
All the components of this product are shown in "1.1 Package components" (page 13). If there is any question or doubt about
this product, contact your local distributor.
The related manuals for using this product are listed below. You can download the latest manuals from the Renesas Tools
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 3 of 104
M3062PT3-RPD-E User’s Manual Important
Important
Before using this product, be sure to read this user’s manual carefully.
Keep this user’s manual, and refer to this when you have questions about this product.
Emulator:
The emulator in this document refers to the following products that are manufactured by Renesas Technology Corp.:
(1) PC4701 main unit
(2) Emulation pod
(3) Package converter board for connecting the user system
The emulator herein does not include the customer’s user system and host machine.
Purpose of use of the emulator:
This emulator is a device to support the development of a system that uses the M16C Family M16C/60 Series M16C/62P
Group and M16C/30 Series M16C/30P Group of Renesas 16bit MCUs. It provides support for system development in both
software and hardware.
Be sure to use this emulator correctly according to said purpose of use. Please avoid using this emulator for other than its
intended purpose of use.
For those who use this emulator:
This emulator can only be used by those who have carefully read the user’s manual and know how to use it.
Use of this emulator requires the basic knowledge of electric circuits, logical circuits, and MCUs.
When using the emulator:
(1) This product is a development supporting unit for use in your program development and evaluation stages. In
mass-producing your program you have finished developing, be sure to make a judgment on your own risk that it can be
put to practical use by performing integration test, evaluation, or some experiment else.
(2) In no event shall Renesas Solutions Corp. be liable for any consequence arising from the use of this product.
(3) Renesas Solutions Corp. strives to renovate or provide a workaround for product malfunction at some charge or without
charge. However, this does not necessarily mean that Renesas Solutions Corp. guarantees the renovation or the provision
under any circumstances.
(4) This product has been developed by assuming its use for program development and evaluation in laboratories. Therefore,
it does not fall under the application of Electrical Appliance and Material Safety Law and protection against
electromagnetic interference when used in Japan.
(5) Renesas Solutions Corp. cannot predict all possible situations or possible cases of misuse where a potential danger exists.
Therefore, the warnings written in this user’s manual and the warning labels attached to this emulator do not necessarily
cover all of such possible situations or cases. Please be sure to use this emulator correctly and safely on your own
responsibility.
(6) This product is not qualified under UL or other safety standards and IEC or other industry standards. This fact must be
taken into account when taking this product from Japan to some other country.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 4 of 104
M3062PT3-RPD-E User’s Manual Important
Usage restrictions:
This emulator has been developed as a means of supporting system development by users. Therefore, do not use it as a device
used for equipment-embedded applications. Also, do not use it for developing the systems or equipment used for the following
purposes either:
(1) Transportation and vehicular
(2) Medical (equipment where human life is concerned)
(3) Aerospace
(4) Nuclear power control
(5) Undersea repeater
If you are considering the use of this emulator for one of the above purposes, please be sure to consult your local distributor.
About product changes:
We are constantly making efforts to improve the design and performance of this emulator. Therefore, the specification or
design of this emulator or its user’s manual may be changed without prior notice.
About the 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 for patent rights or any other
rights belonging to us or third parties.
(3) This user’s manual and this emulator are copyrighted, with all rights reserved by us. This user’s manual may not be
copied, duplicated or reproduced, in whole or part, without prior written consent of us.
About diagrams:
The diagrams in this user’s manual may not all represent exactly the actual object.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 5 of 104
M3062PT3-RPD-E User’s Manual Precautions for Safety
Precautions for Safety
Definitions of Signal Words
In both the user’s manual and on the product itself, several icons are used to insure proper handling of this product and also to
prevent injuries to you or other persons, or damage to your properties.
This chapter describes the precautions which should be taken in order to use this product safely and properly. Be sure to read
this chapter before using this product.
This symbol represents a warning about safety. It is used to arouse caution about a
potential danger that will possibly inflict an injury on persons. To avoid a possible
DANGER
injury or death, please be sure to observe the safety message that follows this symbol.
DANGER indicates an imminently dangerous situation that will cause death or heavy
wound unless it is avoided. However, there are no instances of such danger for the
product presented in this user's manual.
WARNING
CAUTION
CAUTION
IMPORTANT
In addition to the five above, the following are also used as appropriate.
means WARNING or CAUTION.
Example:
WARNING indicates a potentially dangerous situation that will cause death or heavy
wound unless it is avoided.
CAUTION indicates a potentially dangerous situation that will cause a slight injury
or a medium-degree injury unless it is avoided.
CAUTION with no safety warning symbols attached indicates a potentially
dangerous situation that will cause property damage unless it is avoided.
This is used in operation procedures or explanatory descriptions to convey
exceptional conditions or cautions to the user.
CAUTION AGAINST AN ELECTRIC SHOCK
means PROHIBITION.
Example:
DISASSEMBLY PROHIBITED
means A FORCIBLE ACTION.
Example:
UNPLUG THE POWER CABLE FROM THE RECEPTACLE.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 6 of 104
M3062PT3-RPD-E User’s Manual Precautions for Safety
警告警告WARNING
Warnings for AC Power Supply:
z If the attached AC power cable does not fit the receptacle, do not alter the AC power cable and do not plug it
forcibly. Failure to comply may cause electric shock and/or fire.
z Use an AC power cable which complies with the safety standard of the country.
z Do not touch the plug of the AC power cable when your hands are wet. This may cause electric shock.
z This product is connected signal ground with frame ground. If your developing product is transformless (not
having isolation transformer of AC power), this may cause electric shock. Also, this may give an unrepairable
damage to this product and your developing one.
While developing, connect AC power of the product to commercial power through isolation transformer in
order to avoid these dangers.
z If other equipment is connected to the same branch circuit, care should be taken not to overload the circuit.
z When installing this equipment, insure that a reliable ground connection is maintained.
z If you smell a strange odor, hear an unusual sound, or see smoke coming from this product, then disconnect
power immediately by unplugging the AC power cable from the outlet.
Do not use this as it is because of the danger of electric shock and/or fire. In this case, contact your local
distributor.
z Before setting up this emulator and connecting it to other devices, turn off power or remove a power cable to
prevent injury or product damage.
Warnings to Be Taken for This Product:
z Do not disassemble or modify this product. Personal injury due to electric shock may occur if this product is
disassembled and modified. Disassembling and modifying the product will void your warranty.
z Make sure nothing falls into the cooling fan on the top panel, especially liquids, metal objects, or anything
combustible.
Warning for Installation:
z Do not set this product in water or areas of high humidity. Make sure that the product does not get wet. Spilling
water or some other liquid into the product may cause unrepairable damage.
Warning for Use Environment:
z This equipment is to be used in an environment with a maximum ambient temperature of 35°C. Care should be
taken that this temperature is not exceeded.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 7 of 104
M3062PT3-RPD-E User’s Manual Precautions for Safety
注意注意CAUTION
Cautions to Be Taken for Turning On the Power:
z Turn ON the power of the emulator and user system as simultaneously as possible. Turn OFF the power of the
emulator and user system as simultaneously as possible.
z Do not leave either the emulator or user system powered on, because of leakage current the internal circuits
may be damaged.
zWhen turning ON the power again after shutting OFF the power, wait about 10 seconds.
Cautions to Be Taken for Handling This Product:
z Use caution when handling the main unit. Be careful not to apply a mechanical shock.
z Do not touch the connector pins of the emulator main unit and the target MCU connector pins. Static electricity
may damage the internal circuits.
z Do not pull this emulator by the communications interface cable or the flexible cable for connecting the user
system. And, excessive flexing or force may break conductors.
z Do not pull the flexible cable (FLX120-RPD) for connecting to the emulator main unit and the flexible cable
(M3T-FLX160C) for connecting the user system excessively. And, excessive flexing or force may break
conductors.
z Do not use inch-size screws for this equipment. The screws used in this equipment are all ISO (meter-size) type
screws. When replacing screws, use same type screws as equipped before.
Caution to Be Taken for System Malfunctions:
z If the emulator malfunctions because of interference like external noise, do the following to remedy the trouble.
(1) Press the RESET switch on the PC4701’s front panel.
(2) If normal operation is not restored after step (1), shut OFF power to the emulator once and then reactivate
it.
Caution to Be Taken for External Trace Input Voltage:
z Assure that the external trace input voltage of emulator main body does not exceed the TTL level (5.0 V).
Otherwise, internal circuit may be damaged because of overload.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 8 of 104
Precautions for Safety .................................................................................................................................................
User Registration .......................................................................................................................................................
1.2 Other Tool Products Required for Development...........................................................................................
1.3 System Configuration ...................................................................................................................................
1.3.1 System Configuration...........................................................................................................................
1.3.2 Names and Functions of the PC4701 Front Panel LEDs ....................................................................
2.1 Flowchart of Starting Up the Emulator..........................................................................................................
2.2 Installing the Emulator Debugger (M16C PC4701 Emulator Debugger)......................................................
2.2.1 Installing the Emulator Debugger ........................................................................................................
2.3 Connecting the Host Machine ......................................................................................................................
2.4 Connecting the PC4701 ...............................................................................................................................
2.4.1 Connecting the FLX120-RPD to the PC4701 ......................................................................................
2.4.2 Connecting the FLX120-RPD to the Emulation Pod............................................................................
2.5 Turning ON the Power ..................................................................................................................................
2.5.1 Checking the Connections of the Emulator System ............................................................................
2.5.2 Turning ON/OFF the Power .................................................................................................................
2.5.3 LED Display When the Emulator Starts Up Normally ..........................................................................
2.9.1 Removing/Attaching the Upper Cover .................................................................................................
2.9.2 Each Setting.........................................................................................................................................
2.9.5 Jumper Switches JP1 and JP2 on the M30620T3-PRT (MCU-dependent board 1)...........................
2.9.6 Installing and Removing Network Resistors for Pullup........................................................................
2.9.7 Bypass Capacitors for A/D Converter ..................................................................................................
3
4
6
9
11
12
13
13
14
15
15
16
18
19
20
20
21
21
22
23
23
24
25
25
25
26
27
27
27
28
28
29
30
31
32
33
34
35
36
37
38
39
39
40
41
45
47
48
49
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 9 of 104
M3062PT3-RPD-E User’s Manual Contents
Page
3. Usage (How to Use the Emulator Debugger) ........................................................................................................ 50
3.1. Making an MCU File ....................................................................................................................................
3.2 Setting the Work Area...................................................................................................................................
3.3 Starting Up the Emulator Debugger .............................................................................................................
3.3.2 Checking Connections of the Emulator System ..................................................................................
3.4 Downloading Program ..................................................................................................................................
3.5 Program execution .......................................................................................................................................
4.5.1 External Dimensions of the Emulation Pod .........................................................................................
4.5.2 External Dimensions of the M30800T-PTC .........................................................................................
4.5.3 External Dimensions of the Converter Board M3062PT-80FPB..........................................................
4.5.4 External Dimensions of the Converter Board M3T-F160-100NRB......................................................
4.5.5 External Dimensions of the Converter Board M3T-F160-100NSD......................................................
4.5.6 External Dimensions of the Converter Board M3T-F160-128NRD......................................................
4.6 Notes on Using This Product........................................................................................................................
5.1 Flowchart to Remedy the Troubles...............................................................................................................
5.2 When the Emulator Debugger Does Not Start Up Properly .........................................................................
5.3 How to Request for Support .......................................................................................................................
6. Maintenance and Guarantee ...............................................................................................................................
6.1 User Registration........................................................................................................................................
6.5 How to Make Request for Repair ...............................................................................................................
50
51
52
52
58
59
60
63
67
71
72
72
73
73
78
83
86
88
88
89
90
90
91
91
92
96
96
97
100
101
101
101
101
101
102
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 10 of 104
M3062PT3-RPD-E User’s Manual User Registration
User Registration
When you have purchased the emulator presented in this user's manual, please be sure to register it. As the H/W Tool Customer
Registration Sheet is included with this manual, fill it in and FAX it to your local distributor or email the same contents to the
following address. If you register it by email, you can use a text format for user registration created when installing the
software in the following folder. Your registered information is used for only after-sale services, and not for any other purposes.
Without user registration, you will not be able to receive maintenance services such as a notification of field changes or trouble
information. So be sure to carry out the user registration.
For more information about user registration, please email to the following address.
Text format for user registration C:\Program Files\Renesas\Hew\Support
For user registration regist_tool@renesas.com
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 11 of 104
M3062PT3-RPD-E User’s Manual Terminology
Terminology
Some specific words used in this user's manual are defined as follows:
Emulator main unit (Hereafter PC4701)
This means a generic name for emulators for M16C, 7700, 740 Families. Take note of the fact that the M3062PT3-RPD-E (this
product) does not support the PC4701L and PC4700L emulators. For details on specific models of PC4701, visit the Renesas
Tools Homepage at http://www.renesas.com/en/tools.
Emulation pod
This means the emulation pod (this product) for the M16C/60 Series M16C/62P Group and M16C/30 Series M16C/30P Group
MCUs.
Emulator system
This means an emulator system built around the PC4701 emulator. The PC4701 emulator system is configured with an
emulator main unit, emulation pod, host machine and integrated development environment High-performance Embedded
Workshop .
Renesas Integrated development environment High-performance Embedded Workshop
This tool provides powerful support for the development of embedded applications for Renesas microcomputers. It has an
emulator debugger function allowing for the emulator PC4701 and emulation pod to be controlled from the host machine via
an interface. Furthermore, it permits a range of operations from editing a project to building and debugging it to be performed
within the same application. What’s more, it supports version management.
Emulator debugger (M16C PC4701 emulator debugger)
This means a software tool starting up from the High-performance Embedded Workshop to control the emulator and this
product and enables debugging.
Firmware
Program that analyzes contents of communication with the emulator debugger and controls the emulator hardware. This
program is installed in the flash memory in the emulator main unit. This program is downloadable from the emulator debugger
to upgrade the firmware or to support other MCUs.
Host machine
This means a personal computer used to control the emulator main unit and emulation pod.
Software break
A software break is a function to break the program before the system executes an instruction at the specified address. The
instruction at the preset address will not be executed.
Hardware break
A hardware break is a function to break the program when the system detects a write/read of data to/from memory or a
leading/trailing edge of the signal entered from the external trace cable. The former break function is called address break; and
the latter break function is called trigger break. While the instruction at the address where the software break is set is not
executed, a hardware break is performed after the specified instruction is executed.
Target MCU
This means the MCU you are going to debug.
User system
This means a user’s application system using the microcomputer to be debugged.
User program
This means the program you are going to debug.
Evaluation MCU
This means the MCU mounted on the emulation pod which is operated in the specific mode for tools.
#
In this user’s manual, this symbol is used to show active Low. (e.g. RESET#: Reset signal)
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 12 of 104
M3062PT3-RPD-E User’s Manual 1. Outline
1. Outline
This chapter describes the package components, the system configuration and the preparation for using this product for the first
time.
1.1 Package Components
The M3062PT3-RPD-E package consists of the following items. When unpacking it, check to see if your M3062PT3-RPD-E
contains all of these items.
Table 1.1 Package components
Item Quantity
M3062PT3-RPD-E emulation pod 1
FLX120-RPD flexible cable for connecting PC4701 1
M30800T-PTC converter board for 100-pin 0.65mm pitch LCC 1
IC61-1004-051 100-pin 0.65mm pitch LCC socket made by Yamaichi Electronics Co., Ltd. 1
OSC-3 16MHz oscillator circuit board for main clock (preinstalled) 1
OSC-2 oscillator circuit board (bare board)
Network resistors for pulling up ports P0--P5 (51kΩ x 8) 6
H/W Tool Customer Registration Sheet (English) 1
H/W Tool Customer Registration Sheet (Japanese) 1
Repair request sheet (English) 1
Repair request sheet (Japanese) 1
M3062PT3-RPD-E User’s Manual (This manual) 1
M3062PT3-RPD-E User’s Manual (Japanese) 1
* Please keep the M3062PT3-RPD-E's packing box and cushion material in your place for reuse at a later time when sending
your product for repair or other purposes. Always use these packing box and cushion material when transporting this
product.
* If there is any question or doubt about the packaged product, contact your local distributor.
* For purchasing the IC61-1004-051 or for technical information, contact Yamaichi Electronics Co., Ltd.
1
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 13 of 104
M3062PT3-RPD-E User’s Manual 1. Outline
1.2 Other Tool Products Required for Development
To bring forward programs development on the M16C/60 Series M16C/62P Group and M16C/30 Series M16C/30P Group, the
products listed below are necessary in addition to those contained package above. Get them separately.
Table 1.2 Other tool products required for development
* To purchase these products, contact your local distributor.
PC4701
(excluding the PC4700L and PC4701L)
M16C PC4701 Emulator Debugger
M3T-PD30
M3062PT-80FPB
M3T-F160-100NRB
M3T-100LCC-DMS
+
M3T-DIRECT100S
M3T-100LCC-DMS
+
M3T-DUMMY100S
M3T-F160-100NSD
M3T-100LCC-QSD
M3T-F160-128NRD
-
Included with the PC4701
Required according to a foot
pattern of a user system.
Refer to “2.8 Connecting
the User System” (page 30)
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 14 of 104
M3062PT3-RPD-E User’s Manual 1. Outline
1.3 System Configuration
1.3.1 System Configuration
Figure 1.1 shows a configuration of the PC4701 system.
(6) Host machine
Interface cable
Host machine
(5) Emulator main unit
(2)
Flexible cable connecting PC4701
(1) Emulation pod
(3 ) Flexible cable connecting user system
Package converter board for connecting user system
(4)
(7 ) User system
Figure 1.1 System configuration
(1) Emulation pod M3062PT3-RPD-E (this product)
Emulation pod for the M16C/60 Series M16C/62P Group and M16C/30 Series M16C/30P Group. This emulation pod
contains an evaluation MCU.
(2) Flexible cable FLX120-RPD (included)
This is a 120-conductor flexible cable for connecting the PC4701 emulator and the emulation pod.
(3) Flexible cable M3T-FLX160C (included)
This is a 160-conductor flexible cable for connecting the emulation pod and the user system.
(4) Converter board M30800T-PTC (included)
This is a converter board for connecting to 100-pin 0.65mm pitch LCC socket IC61-1004-051 on the user system. For
details, refer to "2.8 Connecting the User System" (page 30).
(5) Emulator main unit PC4701
The emulator main unit for the M16C, 7700 and 740 families to be used with this product.
(6) Host machine
A personal computer to control the emulator.
(7) User system
This is your application system.
This emulator cannot supply the power to the user system. Therefore design your system so that the user system is
powered separately.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 15 of 104
M3062PT3-RPD-E User’s Manual 1. Outline
1.3.2 Names and Functions of the PC4701 Front Panel LEDs
Figure 1.2 shows the names of the LEDs on the front panel of the emulator.
Target status LEDs
STATUS OF
TARGET
System status LEDs
POWER
SAFE
ERROR
STATUS OF
SYSTEM
RESET
PERFORMANCE
HIGH
EMULATOR
POWER
CLOCK
RESET
RUN
HALT
Figure 1.2 Names of the LEDs on the front panel of the PC4701
(1) System Status LEDs
The system status LEDs indicate the emulator PC4701's power supply, firmware operating status, etc. Table 1.3 lists the
definition of each system status LED.
Table 1.3 Definitions of the system status LEDs
Name Status Meaning
POWER
ON Emulator system power supply is turned ON.
OFF Emulator system power supply is turned OFF.
ON Emulator system is operating normally.
Special mode (maintenance mode) for downloading firmware. The
SAFE
Flashing
emulator system does not operate except for downloading firmware and
the self-check.
OFF
Emulator system is not operating normally.
ON Emulator system is not operating normally (system status error).
ERROR
Flashing Downloading firmware.
OFF Emulator system is operating normally.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 16 of 104
M3062PT3-RPD-E User’s Manual 1. Outline
(2) Target Status LEDs
The target status LEDs indicate the target MCU's operating status and target board's power supply. Table 1.4 lists the definition
of each target status LED.
Table 1.4 Definitions of the target status LEDs
Name Status Meaning
POWER
CLOCK
RESET
RUN
HALT
ON Power is supplied to the user system.
OFF Power is not supplied to the user system.
ON Target MCU clock is supplied.
OFF Target MCU clock is not supplied.
ON Target MCU is being reset, or reset signal of the user system is held low.
OFF Target MCU is not being reset.
ON User program is being executed.
OFF User program has been halted.
ON CPU clock of target MCU is not oscillating.
OFF CPU clock of target MCU is oscillating.
Note on the Target Status POWER LED:
zIf the MCU has two or more Vcc terminals, the LED does not light unless power is supplied to all the
Notes on the Target Status CLOCK LED:
terminals.
z CLOCK LED is turned off when both main and sub clocks are not oscillating. If either clock is oscillating,
the LED is turned on.
z If the LED is not turned on, check the following.
(1) After powering on the PC4701 (before starting up the emulator debugger):
Make sure that the oscillator circuit board in the emulation pod is properly installed and it is oscillating
normally.
(2) After the emulator debugger is started up (after the Init dialog box settings are completed):
Make sure that the oscillator selected in the Init dialog box is oscillating normally.
IMPORTANT
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 17 of 104
M3062PT3-RPD-E User’s Manual 1. Outline
1.4 Specifications
Tables 1.5 and 1.6 list the specifications of the M3062PT3-RPD-E.
Table 1.5 M3062PT3-RPD-E specifications (1/2)
Item Description
Applicable MCU
Usable MCU mode
Maximum operating frequency 16MHz
Applicable power supply 2.7 to 5.5V
Time between program start and stop
Maximum/minimum/average execution time and pass count of specified four
zones.
Count clock: Equal to MCU Clock or 16MHz
Dedicated parallel (PC4701HS)
LPT parallel (PC4701M/PC4701U)
Serial (PC4701HS/PC4701M)
USB (USB 1.1, full-speed)*1 (PC4701U)
LAN (PC4701HS/PC4701U)
US EMI Standards [FCC part15 Class A]
CE marking [1998 Class A, EN55024: 1998]
Be sure to use this emulator with the operating environmental of the emulator and host machine listed in Tables 1.7 and 1.8.
Table 1.7 Operating environmental conditions
Item Description
Operating temperature 5 to 35°C (no dew)
Storage temperature -10 to 60°C (no dew)
Table 1.8 Operating environment of the host machine
Item Description
Host machine
OS
CPU Pentium III 600 MHz or more recommended
Memory 128 MB or more recommended
Pointing device such as mouse Mouse or any other pointing device usable with the above OS that can be connected to
CD drive Needed to install the emulator debugger or refer to the user’s manual
* Windows is trademarks of Microsoft Corporation in the United States and other countries.
IBM PC/AT compatibles
Windows 98SE
Windows Me
Windows XP
Windows 2000
the main body of the host machine.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 19 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2. Setup
This chapter describes the preparation for using this product, the procedure for starting up the emulator and how to change
settings.
2.1 Flowchart of Starting Up the Emulator
The procedure for starting up the emulator is shown in Figure 2.1. For details, refer to each section hereafter. And, when the
emulator does not start up normally, refer to “5. Troubleshooting” (page 96).
▼
▼
▼
▼
Connect the emulation pod to the emulator.
Check the package components. Refer to “1.1 Package Components” (page 13).
User registration Refer to “User Registration” (page 11).
Install the M16C PC4701 Emulator
Debugger.
Connect the host machine.
Install the M16C PC4701 Emulator Debugger.
Select the interface according to your PC4701 and connect the
PC4701 to the host machine with each interface connector.
Set the interface selection switch on the rear panel of the PC4701 to
the using interface.
Connect the emulation pod M3062PT3-RPD-E to the PC4701 using
the FLX120-RPD.
▼
Connect the power supply for the emulator. Connect a power supply for the emulator.
▼
▼
▼
▼
Start up the emulator debugger from the
High-performance Embedded Workshop.
▼
▼
Debug a program with various functions of
Figure 2.1 Flowchart of starting up the emulator
Connect the user system. Connect the user system as occasion demands.
Turning on the power supply.
Check the LED display of the emulator.
Set the operating environment
of the emulator debugger.
the emulator debugger.
Turn ON the power to the emulator and the user system as
simultaneously as possible.
Check that system status LED, and POWER, CLOCK, RESET and
WARNING of target status LED are lighting. When the user system
is not connected, the POWER LED does not light up.
Start up the High-performance Embedded Workshop, and the
emulator debugger.
Set the INIT dialog box of the emulator debugger.
For how to use the High-performance Embedded Workshop and the
emulator debugger, refer to each online manual.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 20 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.2 Installing the Emulator Debugger (M16C PC4701 Emulator Debugger)
If the OS used in your host machine is Windows XP or 2000, this installation must be executed by a user with administrator
rights. Be aware that users without administrator rights cannot complete the installation.
Install the M16C PC4701 Emulator Debugger following the procedure described below.
2.2.1 Installing the Emulator Debugger
(1) Downloading the M16C PC4701 Emulator Debugger (as occasion demands)
Download the latest M16C PC4701 Emulator Debugger from the URL below (free of charge).
In the “user information” dialog box, enter the user information (contractor, section, contact address, and host machine).
The supplied information will be turned into a format by which user registration will be provided by e-mail.
(4) Completing the installation
A dialog box will be displayed indicating that setup has been completed. It means that the installation you made is
completed.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 21 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.3 Connecting the Host Machine
When connecting the emulator PC4701 to a host machine, interface varies depending on the PC4701 used. Table 2.1 shows the
outline to connect each interface cable. For details on interface, refer to each PC4701 user’s manual used.
Table 2.1 Operating environment of the host machine
PC4701 Interface Remarks
The dedicated parallel interface cable is supplied with the PC4701HS.
For connection with the dedicated parallel interface, the parallel interface
printed circuit board (PCA4202G02: discontinued product) is required on
the host machine side.
The RS232C interface cable, 25-pin female/25-pin female conversion cable
and 25-pin female/9-pin female conversion cable are supplied with the
PC4701HS.
The RS232C interface cable and 25-pin female/9-pin male conversion cable
are supplied with the PC4701M.
No LAN interface cable is supplied with the PC4701U; it is, therefore,
necessary to arrange a LAN interface cable at your end.
PC4701HS
PC4701M
PC4701U
Dedicated parallel
Serial (RS232C)
LAN (10BASE-2/5) The LAN interface cable (10BASE-2/5) is supplied with the PC4701HS.
LPT parallel The LPT parallel interface cable is supplied with the PC4701M.
Serial (RS232C)
LPT parallels The LPT parallel interface cable is supplied with the PC4701U.
USB The USB interface cable is supplied with the PC4701U.
LAN (10BASE-T)
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 22 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.4 Connecting the PC4701
To connect the emulation pod to the PC4701, use the FLX120-RPD 120-pin flexible cable included with this product package.
Connect the PC4701 side connector of the FLX120-RPD to the cable connector of the PC4701, then secure with screws the
FLX120-RPD.
2.4.1 Connecting the FLX120-RPD to the PC4701
Figure 2.2 shows how to connect the PC4701 and FLX120-RPD.
Emulator main unit
PC4701 side connector
of FLX120-RPD
UPSIDE should be face up.
Figure 2.2 Connecting the FLX120-RPD to the PC4701
Note on Connecting the PC4701 and FLX120-RPD:
zAlways shut OFF power before connecting the cable. Otherwise, the internal circuits may be damaged.
Secure this screw.
CAUTION
Secure this screw.
IMPORTANT
Notes on Connecting the PC4701 and FLX120-RPD, and Securing the Screws:
z To connect the FLX120-RPD, be sure to hold the both sides of the PC4701 side connector horizontally with the
"UPSIDE" facing up.
z After connecting the cable to the emulator main unit PC4701, be sure to secure the screws mounted in both
sides of the connector.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 23 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.4.2 Connecting the FLX120-RPD to the Emulation Pod
Figure 2.3 shows how to connect the FLX120-RPD and the emulation pod.
Emulation pod
FLX120-RPD (Secure with the screws)
Figure 2.3 Connecting the FLX120-RPD to the emulation pod
CAUTION
Note on Connecting the FLX120-RPD and emulation pod:
z Always shut OFF power before connecting the emulation pod and the FLX120-RPD. Otherwise, the internal
circuits may be damaged.
IMPORTANT
Note on Securing the Screws:
z After connecting the emulation pod and the FLX120-RPD, be sure to secure the screws mounted in both sides
of the connector cover.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 24 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.5 Turning ON the Power
2.5.1 Checking the Connections of the Emulator System
Before turning the power ON, check the connection of the interface cable with host machine, PC4701, emulation pod, and user
system.
2.5.2 Turning ON/OFF the Power
Turn ON the power of the emulator and user system as simultaneously as possible. Turn OFF the power of the emulator and
user system as simultaneously as possible.
Do not leave either the emulator or user system powered on, because of leakage current the internal circuits may be damaged.
When turning ON the power again after shutting OFF the power, wait for about 10 seconds.
IMPORTANT
Notes on Power Supply:
z The emulator's pin Vcc is connected to the user system in order to monitor user system voltage. For this reason,
the emulator cannot supply power to the user system. Therefore, provide the user system with a separate power
supply from that of the emulator.
z Keep user system power supply voltage within the following range.
(1) When the JP1 of the M30620T3-PRT is set as Vcc1 = Vcc2
2.7[V] ≤ Vcc1 = Vcc2 ≤ 5.5[V]
(2) When the JP1 of the M30620T3-PRT is set as Vcc1 > Vcc2
4.8[V] ≤ Vcc1≤ 5.2[V]
2.7[V] ≤ Vcc2 < Vcc1
zDo not change user system power supply voltage after power has been activated.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 25 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.5.3 LED Display When the Emulator Starts Up Normally
Figure 2.4 shows front panel LED lighting status when the emulator started up properly. Check it when starting up the
emulator system.
POWER
SAFE
ERROR
STATUS OF
SYSTEM
RESET
PERFORMANCE
HIGH
EMULATOR
STATUS OF
TARGET
POWER
CLOCK
RESET
RUN
HALT
This does not light when the user
system is not connected.
: On
: Off
LED display when the emulator starts up normally
Figure 2.4 LED display when the power turned on
Note on the Target Status POWER LED:
Notes on the Target Status CLOCK LED:
z If the MCU has two or more Vcc terminals, the LED does not light unless power is supplied to all the
terminals.
z CLOCK LED is turned off when both main and sub clocks are not oscillating. If either clock is oscillating, the
LED is turned on.
z If the LED is not turned on, check the following.
(1) After powering on the PC4701 (before starting up the emulator debugger):
Make sure that the oscillator circuit board is properly installed in the PC4701 and it is oscillating normally.
(2) After the emulator debugger is started up (after the Init dialog box settings are complete):
Make sure that the oscillator selected in the Init dialog box is oscillating normally.
IMPORTANT
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 26 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.6 Downloading Firmware
2.6.1 When It is Necessary to Download Firmware
It is necessary to download the firmware in the cases listed below. Normally, the following are automatically detected when the
emulator debugger is started up, and the firmware is downloaded.
(1) When you use this product for the first time
(2) When the firmware has been upgraded
(3) When the emulator debugger has been upgraded
(4) When you use this product with a PC4701 which was used with other emulation pod before
If downloading firmware is not completed in the cases below, redownload the firmware in maintenance mode.
- When the power is unexpectedly shut down during a download from the emulator debugger
- When a communications interface cable is unexpectedly pulled out
2.6.2 Downloading Firmware in Maintenance Mode
Download the firmware in maintenance mode as explained here following. The user system must not be connected when
downloading the firmware.
(1) Set the interface select switch on the rear panel of the PC4701 to the dedicated parallel, LPT or serial interface to connect
the PC4701 and the host machine. Set the interface selection switch on the rear panel of the PC4701 according to the using
interface. The firmware may not be downloaded in maintenance mode correctly with the USB interface.
(2) Within 2 seconds of activating power to the emulator, press the RESET switch on the PC4701 upper panel to switch to
maintenance mode.
Switched to maintenance mode, the SAFE SYSTEM STATUS LED begins to flash.
(3) Start up the emulator debugger. When the Init dialog box setup is complete, the dialog which urges to download the
firmware will appear. Download the firmware following messages. Required time for downloading the firmware is about
60 seconds.
POWER
SAFE
ERROR
STATUS OF
RESET
SYSTEM
POWER
CLOCK
RESET
RUN
HALT
All the LEDs light
Immediately after turning on the power
POWER
SAFE
ERROR
STATUS OF
SYSTEM
RES ET
When maintenance mode sta rted
POWER
CLOCK
RESET
RUN
HALT
SAFE LED lights
POWER
SAF E
ERROR
STATUS OF
RESET
SYST EM
POWER
CLOCK
RES ET
RUN
HAL T
ERROR LED lights
When downloading firmwa re started
POWER
SAFE
ERROR
STATUS OF
SYSTEM
RES ET
POWER
CLOCK
RESET
RUN
HALT
SAFE LED blinksAll the LEDs light
POWER
SAFE
ERROR
STATUS OF
RES ET
SYSTEM
POWER
CLOCK
RESET
RUN
HALT
POWER
SAF E
ERROR
STATUS OF
SYSTEM
RESET
POWER
CLOCK
RESET
RUN
HALT
When download complete
: On
: Off
: Blinking
Figure 2.5 Downloading firmware in maintenance mode
IMPORTANT
Note on Downloading Firmware:
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 27 of 104
z Do not shut OFF power while the firmware is being downloaded. Doing so, the emulator will not start up
properly. If power is shut OFF by mistake, redownload the firmware in maintenance mode.
M3062PT3-RPD-E User’s Manual 2. Setup
2.7 Self-check
2.7.1 Self-check Procedure
To run the self-check of the emulator, do so as explained here below. While the self-check is in progress, the LEDs will change
as shown in Figure 2.6.
(1) If the user system is connected, disconnect it.
(2) Set the switches in the emulation pod to the factory settings as shown in Figure 2.7.
(3) Within 2 seconds of activating power to the emulator, press the system reset switch on the emulator front panel to switch
the emulator to maintenance mode.
(4) Check the SAFE LED starts blinking and then press the system reset switch again.
(5) The self-check will start. If the normal result is displayed in about 30 seconds, the self-check has terminated normally.
POWER
SAFE
ERROR
STATUS OF
SYSTEM
RESE T
POWER
CLOCK
RESET
RUN
HALT
(1) All the LEDs light
Immediately after turning on the power
POWER
SAFE
ERROR
STATUS OF
SYSTEM
RESET
Self - check
: On
: Off
: Blinking
POWER
CLOCK
RESET
RUN
HAL T
(2) SAFE LED blinks
POWER
SAF E
ERROR
STATUS OF
SYSTEM
RESET
POWER
SAF E
ERROR
STATUS OF
SYSTEM
RESET
POWER
CLOCK
RESET
RUN
HALT
Completed normally
POWER
CLOCK
RESET
RUN
HALT
ERROR LED lights
System status error
POWER
SAFE
ERROR
STATUS OF
SYSTEM
RESET
Target status error
POWER
CLOCK
RES ET
RUN
HAL T
SAFE and ERROR LED blink
Figure 2.6 LED display in the self-check procedure
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 28 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
BYTE
SW1
(factory-settings)
HOPENL
SW2
CNVss
(factory-settings)
P86/Xcout
SW4
(factory-settings)
L
H
OPEN
P86/XC OP
Xout
SW3
OP Xout
(factory-settings)
P87/Xcin
P87 Xcin
SW5
JP1
(factory-settings)(factory-settings)
M30620T3-PRT board
Figure 2.7 Switch settings for the self-check (factory-settings)
2.7.2 If an Error is Detected in the Self-check
If the self-check does not result normally, check the following.
(1) Whether the emulation pod and PC4701 are connected properly
(2) Whether the proper firmware has been downloaded
(3) Whether the switch settings of this product are the factory-settings
4M
A18_SEL
1M
VCC1>VCC2
VDDIO
=
JP2
VCC1
(factory-settings)
VCC2
Notes on Self-check:
z Perform the self-check while not connecting the user system.
z If the self-check does not result normally (excluding target status error), the emulation pod may be damaged.
Then contact your local distributor.
IMPORTANT
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 29 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8 Connecting the User System
Connect the emulation pod to the user system as shown in Figures 2.8.
Tip of emulation pod probe
80-pin
0.65mm pitch
M 3062PT -80FPB
80-pin
QFP
(not included)
M3T-F160-100NRB
100-pin
QFP
(not included)
100-pin
0.65mm pitch0.5mm pitch
M30800T-PTC
(included)
M3T -10 0LC C- DMS
(not included)
M3T-FLX100-TM3T- FLX100-R
LCC socket
100-pin LCC
(included)
(not included)
M3T-DIRECT100S
100-pin
QFP
(not included)(not included)
M3T-DUMMY100S
100-pin QFP
●: No.1 pin
*: These three items are included in one package .
(not included)
*1
M3T- F160-100NSD
100-pin LQFP
(not included)
128-pin
0.5mm pitch
M30800T-P TC
(included)
M3T -100 LC C- QSD
100-pin LQFP
(not included)(not included)
M3T-F160-128 NRD
128-pin LQFP
Figure 2.8 Connecting the user system
Note on Connecting the User System:
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulation
pod.
CAUTION
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 30 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8.1 Connecting to a 80-pin 0.65mm Pitch Foot Pattern
Figure 2.9 shows how to connect 80-pin 0.65mm pitch foot pattern on the user system to the M3062PT-80FPB (not included),
and here following is its procedure.
For details on the M3062PT-80FPB (not included), refer to its user's manual.
(1) Attach the NQPACK080SB included with the M3062PT-80FPB to the user system.
(2) Attach the YQPACK080SB included with the M3062PT-80FPB to the NQPACK080SB and secure it with the
YQ-GUIDE's.
(3) Attach the CN2 side of the M3062PT-80FPB to the CN2 side of the package converter board connected to the emulation
pod probe.
(4) Attach the M3062PT-80FPB to the YQPACK080SB.
Tip of emulation
pod probe
Package converter board
*
These corners are not round.
*: These four items are included in one package.
Figure 2.9 Connecting to a 80-pin 0.65mm pitch foot pattern
CN2 side
(3)
M3062 PT- 80 FPB (not included)
On-board evaluation
(4)
YQ-GUIDE (x 4)
YQPACK080SB
NQPACK080SB
(2)
80-pin 0.65mm pitch
(PRQP0080JA-A) foot pattern
(1)
No. 1 pin
User system
HQPACK 080SB
(not included)
FLASH MCU, etc.
CAUTION
Note on Connecting the User System:
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulation
pod.
IMPORTANT
Note on Connectors of the Converter board:
zThe small connectors of the M3062PT-80FPB are guaranteed for only 50 insertion/removal iterations.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 31 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8.2 Connecting to a 100-pin LCC socket
Figure 2.10 shows how to connect a 100-pin LCC socket (IC61-1004-051 of Yamaichi Electronics Co., Ltd.) on the user
system to the M30800T-PTC (included).
(1) Attach the CN2 side of the M30800T-PTC to the CN2 side of the package converter board connected to the emulation pod
probe.
(2) Attach the M30800T-PTC to the 100-pin LCC socket.
Tip of emulation pod probe
Package converter board
CN 2 side
(1)
M 30800T- PTC
Figure 2.10 Connecting to a 100-pin LCC socket
Note on Connecting the User System:
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulation
pod.
Notes on Connectors of the Converter board:
z The connectors of the M30800T-PTC are guaranteed for only 50 insertion/removal iterations.
z The connectors of the IC61-1004-051 are guaranteed for only 20 insertion/removal iterations.
z For purchasing the IC61-1004-051 or for technical information, contact Yamaichi Electronics Co., Ltd.
(2)
CAUTION
IMPORTANT
100- pin LCC socket
No . 1 pin
User system
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 32 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8.3 Connecting to a 100-pin 0.65mm Pitch Foot Pattern (Part 1)
Figure 2.11 shows how to connect a 100-pin 0.65mm pitch foot pattern on the user system to the M3T-F160-100NRB (not
included), and here following is its procedure. For details on the M3T-F160-100NRB (not included), refer to its user's manual.
(1) Attach the NQPACK100RB included with the M3T-F160-100NRB to the user system.
(2) Attach the YQPACK100RB included with the M3T-F160-100NRB to the NQPACK100RB and secure it with the
YQ-GUIDE's.
(3) Attach the CN2 side of the M3T-F160-100NRB to the CN2 side of the package converter board connected to the emulation
pod probe.
(4) Attach the M3T-F160-100NRB to the YQPACK100RB.
Tip of emulation pod probe
Package converter board
CN2 side
(3)
M3T-F160-100NRB
(not included))
(4)
*
(2)
These corners are not round.
(1)
*: These four items are available in one package.
Figure 2.11 Connecting to a 100-pin 0.65mm pitch foot pattern (1/3)
On-board evaluation
HQPACK100RB168
YQ-GUIDE (x4)
YQPACK100RB
NQPACK100RB
100-pin 0.65mmpitch
(PRQP0 100JB-A) foot pattern
NO. 1 pin
User system
(not included)
FLASH MCU, etc.
CAUTION
Note on Connecting the User System:
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulator or
user system.
IMPORTANT
Note on Connectors of the Converter board:
zThe connectors of the M3T-F160-100NRB are guaranteed for only 50 insertion/removal iterations.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 33 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8.4 Connecting to a 100-pin 0.65mm Pitch Foot Pattern (Part 2)
Figure 2.12 shows how to connect a 100-pin 0.65mm pitch foot pattern on the user system to the M3T-DIRECT100S (not
included), and here following is its procedure. For details on the M3T-100LCC-DMS (not included) and M3T-DIRECT100S
(not included), refer to each user's manual.
(1) Attach the M3T-DIRECT100S to the user system.
(2) Attach the M3T-100LCC-DMS to the M3T-DIRECT100S.
(3) Attach the CN2 side of the M30800T-PTC to the CN2 side of the package converter board connected to the emulation pod
probe.
(4) Attach the M30800T-PTC to the M3T-100LCC-DMS.
Tip of emulation pod probe
Package converter board
CN2 side
(3)
M30800T-PTC
(4)
(2)
(1)
Figure 2.12 Connecting to a 100-pin 0.65mm pitch foot pattern (2/3)
CAUTION
Note on Connecting the User System:
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulation
pod.
M3T-100LCC-DMS
(not included)
M3T-DIRECT100S
(not included)
100-pin 0.65mm pitch
(PRQP0100JB-A) foot pattern
No. 1 pin
User system
IMPORTANT
Notes on Connectors of the Converter board:
z The connectors of the M30800T-PTC are guaranteed for only 50 insertion/removal iterations.
z The connectors of the M3T-100LCC-DMS and M3T-DIRECT100S are guaranteed for only 20
insertion/removal iterations.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 34 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8.5 Connecting to a 100-pin 0.65mm Pitch Foot Pattern (Part 3)
Figure 2.13 shows how to connect a 100-pin 0.65mm pitch foot pattern on the user system to the M3T-DUMMY100S (not
included), and here following is its procedure. For details on the M3T-100LCC-DMS (not included) and M3T-DUMMY100S
(not included), refer to each user's manual.
(1) Attach the M3T-DUMMY100S to the user system.
(2) Attach the M3T-100LCC-DMS to the M3T-DUMMY100S.
(3) Attach the CN2 side of the M30800T-PTC to the CN2 side of the package converter board connected to the emulation pod
probe.
(4) Attach the M30800T-PTC to the M3T-100LCC-DMS.
Tip of emulation pod probe
Package converter board
CN2 side
(3)
M30800T-PTC
(4)
(2)
100-pin 0.65mm pitch
(PRQP0100JB-A) foot pattern
(1)
No. 1 pin
Figure 2.13 Connecting to a 100-pin 0.65mm pitch foot pattern (3/3)
M3T-100LCC-DMS
(not included)
M3T-DUMMY100S
(not included)
User system
On-board evaluation
FLASH MCU, etc.
CAUTION
Note on Connecting the User System:
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulation
pod.
IMPORTANT
Notes on Connectors of the Converter board:
z The connectors of the M30800T-PTC are guaranteed for only 50 insertion/removal iterations.
z The connectors of the M3T-100LCC-DMS and M3T-DUMMY100S are guaranteed for only 20
insertion/removal iterations.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 35 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8.6 Connecting to a 100-pin 0.5mm Pitch Foot Pattern (Part 1)
Figure 2.14 shows how to connect a 100-pin 0.5mm pitch foot pattern on the user system to the M3T-F160-100NSD (not
included), and here following is its procedure. For details on the M3T-F160-100NSD (not included), refer to its user's manual.
(1) Attach the NQPACK100SD-ND included with the M3T-F160-100NSD to the user system.
(2) Attach the YQPACK100SD included with M3T-F160-100NSD to the NQPACK100SD-ND and secure it with the
YQ-GUIDE's.
(3) Attach the CN2 side of th e M3T-F160-100NSD to the CN2 side of the package converter board connected to the emulation
pod probe.
(4) Attach the M3T-F160-100NSD to the YQPACK100SD.
Tip of emulation pod probe
Package converter board
CN2 side
(3)
M3T-F 160- 100 NSD
( not included)
(4)
*
(2)
These corners are not round.
(1)
*: These four items are available in one package .
Figure 2.14 Connecting to a 100-pin 0.5mm pitch foot pattern (1/2)
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulation
pod.
IMPORTANT
Note on Connectors of the Converter board:
zThe connectors of the M3T-F160-100NSD are guaranteed for only 50 insertion/removal iterations.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 36 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8.7 Connecting to a 100-pin 0.5mm Pitch Foot Pattern (Part 2)
Figure 2.15 shows how to connect a 100-pin 0.5mm pitch foot pattern on the user system to the M3T-100LCC-QSD (not
included), and here following is its procedure. For details on the M3T-100LCC-QSD (not included), refer to its user's manual.
(1) Attach the TQPACK100SD to the user system.
(2) Attach the TQSOCKET100SDG to the TQPACK100SD.
(3) Attach the M3T-100LCC-QSD to the TQSOCKET100SDG.
(4) Attach the CN2 side of the M30800T-PTC to the CN2 side of the package converter board connected to the emulation pod
probe.
(5) Attach the M30800T-PTC to the M3T-100LCC-QSD.
Tip of emulation pod probe
Package converter board
CN2 side
(4)
M30800T-PTC
(5)
(3)
(2)
(1)
Figure 2.15 Connecting to a 100-pin 0.5mm pitch foot pattern (2/2)
M3T-100LCC-QSD
(not included)
TQSOCKET100SDG
TQPACK100SD
100-pin 0.5mm pitch
(PLQP0100KB-A) foot pattern
No. 1 pin
User system
CAUTION
Note on Connecting the User System:
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulation
pod.
IMPORTANT
Notes on Connectors of the Converter board:
z The connectors of the M30800T-PTC are guaranteed for only 50 insertion/removal iterations.
z The connectors of the M3T-100LCC-QSD are guaranteed for only 20 insertion/removal iterations.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 37 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.8.8 Connecting to a 128-pin 0.5mm Pitch Foot Pattern
Figure 2.16 shows how to connect a 128-pin 0.5mm pitch foot pattern on the user system to the M3T-F160-128NRD (not
included), and here following is its procedure.
For details on the M3T-F160-128NRD (not included), refer to its user's manual.
(1) Attach the NQPACK128RD included with the M3T-F160-128NRD to the user system.
(2) Attach the YQPACK128RD included with M3T-F160-128NRD to the NQPACK128RD and secure it with the
YQ-GUIDE's.
(3) Attach the CN2 side of the M3T-F160-128NRD to the CN2 side of the package converter board connected to the emulation
pod probe.
(4) Attach the M3T-F160-128NRD to the YQPACK128RD.
Tip of emulation pod probe
Package converter board
CN2 side
(3)
M3T-F160-128NRD
(not included)
*
These corners are not round.
*: These four item s are available in one package.
Figure 2.16 Connecting to a 128-pin 0.65mm pitch foot pattern
CAUTION
Note on Connecting the User System:
z Take care not to attach the converter board in a wrong direction. It may cause a fatal damage to the emulation
pod.
(4)
YQ-GUIDE (x4)
YQPACK128RD
NQPACK128RD
(2)
128-pin 0.5mm pitch
(PLQP0128KB-A) foot pattern
(1)
No. 1 pin
User system
On-board evaluation
HQPACK128RD
(not included)
FLASH MCU, etc.
IMPORTANT
Note on Connectors of the Converter board:
zThe connectors of the M3T-F160-128NRD are guaranteed for only 50 insertion/removal iterations.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 38 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.9 Changing Settings
This chapter describes how to set the inside of the emulator.
2.9.1 Removing/Attaching the Upper Cover
(1) Removing the upper cover
To open the upper cover, remove the four screws of both sides of the M3062PT3-RPD-E and lift off the upper cover (see
Figure 2.17).
(2) Attaching the upper cover
To close the upper cover, attach the upper cover and secure the four screws of both sides of this product.
Figure 2.17 Removing the upper cover
Note on Removing and Attaching the Upper Cover:
z Always shut OFF power when removing/attaching the upper cover or changing the switch settings. Otherwise
the internal circuit may be damaged.
CAUTION
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 39 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.9.2 Each Setting
Figure 2.18 shows the positions of each part of the M3062PT3-RPD-E.
(1) Position of oscillator circuit board
(2) Position of switches
(3) Position of socket for mounting network resistor for pullup
(4) Position of bypass capacitor for A/D converter
(4) Bypass capacitor for A/D converter
Common board
(M30620T3-RPDC)
MCU dependent board 2
(M3062PT3-PRTM)
MCU dependent board 1
(M30620T3-PRT)
(1) Oscillator circuit board
Figure 2.18 Positions of each part
(3) Socket for
mounting network
resister for pullup
(2) Switches
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 40 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.9.3 Selecting Clock Supply
(1) Clock Supply to the MCU
You can choose a clock supplied to the evaluation MCU by the Emulator tab in the Init dialog box of the emulator debugger.
Table 2.2 lists the factory-settings of each clock supply when you install the emulator debugger.
Table 2.2 Clock Supply to the MCU
Clock Display of emulator debugger Description Default setting
Internal
Main (XIN-XOUT)
External User system -
Internal oscillator circuit of emulation pod
(OSC-3: 16.0MHz or OSC-2)
Ye s
Internal
Sub (XCIN-XCOUT)
External User system Yes
Internal oscillator circuit of emulation pod
(32.768kHz)
-
IMPORTANT
Notes on Changing the Clock Supply:
(2) Using the Internal Oscillator Circuit Board
An oscillator circuit board for 16.0MHz (OSC-3) is mounted on this product. Also the oscillator circuit board (OSC-2) is
attached to change the oscillation frequency. When you use an internal oscillator circuit as a main clock, “Internal” can be set
by the emulator debugger.
z The clock supply can be set in the Init dialog box when starting up the emulator debugger or inputting CLK
command on the script window.
z For pins X
Settings" (page 45).
CIN-XCOUT
, it is necessary to set the switches in the emulation pod. For details, refer to "2.9.4 Switch
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 41 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
(3) Replacing Oscillator Circuit Boards
Figure 2.19 shows how to replace the oscillator circuit boards. For the position of the oscillator circuit board, see Figure 2.18.
(1) Unscrew the screw securing the oscillator circuit board.
(2) Lift off the oscillator circuit board.
(3) Insert the connector of a new oscillator circuit board to the
connector of the main board.
(4) Secure the new oscillator circuit board with the screw.
Figure 2.19 Replacing oscillator circuit boards
CAUTION
Note on Replacing the Oscillator Circuit Board:
zAlways shut OFF power when replacing oscillator circuit board. Otherwise, internal circuits may be damaged.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 42 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
(4) Using the Internal Oscillator Circuit (Bare Board) of the Emulation Pod
To use the emulation pod at a desired frequency, build the desired oscillator circuit on the included OSC-2 oscillator circuit
board (bare board). Figure 2.20 shows an external view of the OSC-2 oscillator circuit board (bare board) and where connector
pins are located. Figure 2.21 shows the circuitry of the OSC-2 oscillator circuit board (bare board). Use the number of
oscillator circuits recommended by the oscillator manufacturer.
J1-4:GND
J1-3:Os cilla tio n output
J1-2:GND
J1-1:VCC
Figure 2.20 External view of the OSC-2 oscillator circuit board and its connector pin positions
11
IC1
10
IC1
9
8
CLK
J1-3
R1
IC1
Vcc
14
7
GND
GND
J1-1
J1-2
J1-4
* *
X3
*
X1 ,X2
C2
X1:5.08-mm- pitch 2- pin oscillator
*.
X2:2.54-mm- pitch 2- pin oscillator
X3:2.54- mm- pitch 3- pin oscillator
R2
C1
1
3
5
13
IC1
2
4
6
12
C3
IC1:Inverter (Unbuffer)
Figure 2.21 Circuits of the OSC-2 oscillator circuit bare board
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 43 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
(5) Using the Oscillator Circuit on the User System
To operate this product with an external clock, construct the oscillator circuit as shown in Figure 2.22 in the user system and
input the oscillator output at 50% duty (within the operating range of the evaluation MCU) into pin X
. And pin X
IN
OUT
should
be open. Choose "External" in the emulator debugger to use this clock.
Figure 2.22 External oscillator circuit
Make note that in the oscillator circuit shown in Figure 2.23 where a resonator is connected between pins X
and X
IN
OUT
oscillation does not occur because a flexible cable, buffer IC and other devices are used between the evaluation MCU and the
user system. It is same for sub-clock oscillator circuits (X
CIN
and X
COUT
).
,
Figure 2.23 Circuit in which oscillation does not occur
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 44 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.9.4 Switch Settings
Here follows explanations of the switches of the emulation pod. Set the switches according to the user system.
Tables 2.3 and 2.4 list how to set toggle switches SW1 to SW5 of the M30620T3-PRT board (MCU-dependent board). Table
2.5 lists how to set jumper switches JP1 and JP2. For the positions of the switches, see Figure 2.18.
Table 2.3 Switch settings of the M3062PT3-RPD-E (1)
Signal Switch Setting Description
SW1
BYTE
HOPEN
Sets pin BYTE of the MCU to "L" when the user system is
unconnected.
Pulls down pin BYTE of the MCU with a resistance of 33kΩ.
Use this setting when the user system is connected.
Does not pull up/down pin BYTE of the MCU.
(Inputs the level of the user system to pin BYTE of the MCU.)
Sets pin BYTE of the MCU to "H" when the user system is
unconnected.
Pulls up pin BYTE of the MCU with a resistance of 33kΩ.
Sets pin CNVss of the MCU to "L" when the user system is
unconnected.
Pulls down pin CNVss of the MCU with a resistance of 1kΩ.
Use this setting when the user system is connected.
Does not pull up/down pin CNVss of the MCU.
(Inputs the level of the user system to pin CNVss of the MCU.)
Sets pin CNVss of the MCU to "H" when the user system is
unconnected.
Pulls up pin CNVss of the MCU with a resistance of 1kΩ.
BYTE SW1
CNVss SW2
L
(factory-settings)
BYTE
SW1
SW1
(factory-settings)
CNVss
CNVss
CNVss
BYTE
SW2
SW2
SW2
H
OPEN
L
H
OPEN
L
H
OPEN
L
H
OPEN
L
H
OPEN
L
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 45 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
Table 2.4 Switch settings of the M3062PT3-RPD-E (2)
Signal Switch Setting Description
SW3
Xout SW3
P86/Xcout SW4
P87/Xcin SW5
Xout
OP Xout
(factory-settings)
(factory-settings)
(factory-settings)
SW3
Xout
P86/Xcout
SW4
P86/Xcout
SW4
P87/Xcin
SW5
OP Xout
P86/XC OP
P86/XC OP
P87 Xcin
Does not connect pin Xout of the MCU to the user system.
Connects pin Xout of the MCU to the user system.
Connects pin P86/Xcout of the MCU to the user system to use it as
port P86 or Xcout.
Does not connect pin P86/Xcout of the MCU to the user system.
Connects pin P87/Xcin of the MCU as port P87.
P87/Xcin
SW5
Note on Switch Settings:
zAlways shut OFF power before changing switch setting.
Note on BYTE and CNVss Switch Settings:
z Switch settings of the BYTE and CNVss are for debugging without the user system connected.
Connects pin P87/Xcin of the MCU as Xcin.
P87 Xcin
CAUTION
IMPORTANT
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 46 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.9.5 Jumper Switches JP1 and JP2 on the M30620T3-PRT (MCU-dependent board 1)
Table 2.5 Switch settings of the M3062PT3-RPD-E (3)
Signal Switch Setting Description
4M
Always use this setting.
A18_SEL JP1
A18_SEL
1M
JP1
(factory-settings)
4M
Do not use this setting.
A18_SEL
1M
JP1
VDDIO JP2
Note on Switch Settings:
zAlways shut OFF power before changing switch setting.
VCC1>VCC2
VDDIO
=
JP2
VCC1
VDDIO
JP2
VCC1
VCC2
VCC1>VCC2
=
VCC2
(factory-settings)
2.7[V] ≤ Vcc1=Vcc2 ≤ 5.5[V]
4.8[V] ≤ Vcc1 ≤ 5.2[V] and 2.7[V] ≤ Vcc2 < Vcc1
CAUTION
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 47 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.9.6 Installing and Removing Network Resistors for Pullup
In this product, you cannot control pullup for ports P0 to P5 by pullup control registers (pullup control register read/write are
possible).
A socket for installing the network resistor for pullup is mounted in this product. Mount the 51kΩ network resistor supplied
with this product to the port for which pullup control is required. For the mounting location, refer to Figure 2.24 below. And
for the positions of each part, refer to Figure 2.18.
VCC2
P50
P51
P52
P53
P54
P55
P56
P57
RM1
P5
VCC2
P00
P01
P02
P03
P04
P05
P06
P07
RM2
P0
VCC2
P40
P41
P42
P43
P44
P45
P46
P47
RM3
P4
Figure 2.24 Position for mounting network resistors for pullup
VCC2
P10
P11
P12
P13
P14
P15
P16
P17
RM4
P1
RM5
VCC2
P20
P21
P22
P23
P24
P25
P26
P27
P2
VCC2
P30
P31
P32
P33
P34
P35
P36
P37
RM6
b0b7
P3
CAUTION
Note on Installing and Removing Network Resistors for Pullup:
z Always shut OFF power before installing or removing network resistors for pullup. Otherwise, internal circuit
board may be damaged. Also install network resistors for pullup properly.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 48 of 104
M3062PT3-RPD-E User’s Manual 2. Setup
2.9.7 Bypass Capacitors for A/D Converter
The M3062PT3-RPD-E has the M3062PT3-PRTM (MCU-dependent board 2) board which has a foot pattern for installing
bypass capacitors for A/D converter near the MCU and premounted 0.1μF capacitors. Mount suitable bypass capacitors as
occasion demands. Figure 2.18 shows where they are installed and Figure 2.25 shows their connection.
CC - AVSS bypass capacitor
AV
AV
SS
C3
V
REF
- AV
SS
bypass capacitor
AVSSVREF
C2
Figure 2.25 Foot patterns of bypass capacitors for A/D converter
IMPORTANT
Note on the A/D Converter Function:
z Because a flexible cable and other devices are used between the evaluation MCU and the user system, the A/D
converter operates differently from that of the actual MCU. Make the final evaluation of the A/D converter
with the actual MCU.
AV
CC
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 49 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
3. Usage (How to Use the Emulator Debugger)
This chapter describes how to start up the M16C PC4701 emulator debugger from the High-performance Embedded Workshop
and how to use the main windows.
3.1. Making an MCU File
It is necessary to make an MCU file to use this product with the emulator debugger. According to the MCU you use, change
the contents of the MCU file. Make the MCU file named “M3062PT3.MCU” etc. following the description below using a text
editor and store it in the "mcufiles" folder in the directory where the emulator debugger is installed.
The emulator debugger has been installed in the following directory by default.
- When using the M16C PC4701 emulator debugger on the High-performance Embedded Workshop
The MCU file contains information such as, SFR area, internal RAM area, internal ROM area, firmware file name. The
contents of the MCU file when using the M30627MHP (31KB RAM, 384KB ROM) are as follows:
0 : SFR area Start address
3FF : End address
400 : Internal RAM Start address
7FFF : End address
A0000 : Internal ROM
FFFFF : End address
M30620P : Name of firmware (Do not change.)
1 : Expansion No. (Do not change.)
When using this product in microprocessor mode, set the internal ROM area as follows.
00000 : Internal ROM Start address
00001 : End address
Start address
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 50 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
3.2 Setting the Work Area
With this product, the emulator uses 54 bytes as a work area in emulation memory. Therefore, according to the memory
mapping of the MCU you use, specify the work area addresses.
In single-chip mode, set the work area address at 10000h.
In memory expansion or microprocessor mode, the areas listed below cannot be used as a work area, specify a work area other
than the areas listed below. And the top address of the work area should be an even-numbered address.
(1) SFR area (00000h--003FFh)
(2) External area of multiplex bus setting
(3) Reserved area of 27000h--27FFFh
(4) Stack area used by the emulator for reset command execution (0FFF9h--0FFFFh)
(5) F6000h to F63FFh and F8000h to F83FFh
The area used as a work area (54 bytes) is specified in the F/W and Work Area tab of the INIT dialog box of the emulator
debugger. And set the work area as MAP=INT.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 51 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
3.3 Starting Up the Emulator Debugger
When debugging the completed programs, switch the session. The session can be changed by the drop down list of the tool bar
shown below.
You will have as many sessions created as the number of targets you selected when creating a project, so select the session that
corresponds to the target to be connected from the drop-down list. Select “SessionM16C_PC4701_Emulator”
3.3.1 Init Dialog Box
After specifying the session, an Init dialog box to connect the target is displayed.
The Init dialog box is used to set the items that need to be set when the emulator debugger starts up. The contents set in this
dialog box remain effective the next time you start the debugger.
(1) MCU tab
1) Specifying the MCU file
Specifying the MCU file
Specify the MCU file for the target MCU.
(1) Click the “Refer…” Button.
(2) ”Select MCU File” dialog box will be displayed. Specify the MCU file
for the target MCU.
- The MCU file contains the information specific to the target MCU.
- The specified MCU file is displayed at the MCU area field of MCU tab.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 52 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
2) Specifying the communication interface
Specifying the communication interface (Parallel)
- In case where the parallel communication is set up, click the radio button
“Parallel” of MCU tab.
- For the host area, only IBM-PC/AT can be designated.
- Set the I/O address value that was set up with the special interface board
PCA4202G02 to the I/O address area.
- Input the I/O address in hexadecimal.
- For I/O address setting of PCA4202G02, refer to the “PCA4202G02
Instruction Manual”.
Specifying the communication interface (Serial)
- For connection with serial communication, click the radio button “Serial”
of MCU tab.
- Specify the communication port of serial interface used to the port area
and the baud rate to the baud rate area.
Specifying the communication interface (LAN)
- For selecting the LAN communication, click the radio button “LAN” of
the MCU tab.
- Specify the IP address of the emulator to the IP address area.
- Specify the IP address of the emulator at the IP address area. Specify the
IP address by one byte of decimal number separating each four bytes with
a period.
- Specify the port number at the Port area.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 53 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
Specifying the communication interface (LPT)
- For selecting the LPT communication, click the radio button “LPT” of
the MCU tab.
- For the Type area, specify the LPT interface communication mode to be
used. When you use the e mulator debugger for the first time, select “AUTO”.
- Specify the I/O address of the parallel port at the I/O address area.
- For BIOS setup, the following addresses are available.
- 378h
- 278h
3) Executing the self-check
Specifying the communication interface (USB)
- For selecting the USB communication, click the radio button “USB” of
the MCU tab.
- The emulators connected by USB cable are shown at Serial No. area.
- Select the serial No. of the emulator you are going to connect.
Executing the self-check
Enable this function when you want the emulator to be self-checked at
startup. Be sure to select the check box only when you want the emulator to
be self-checked at startup.
Note:
In case where self-checking was normally completed, terminate the
emulator debugger once, then start operation with no self-checking
carried out again (with leaving the check box unchecked).
This function may be enabled in the following cases:
- When you are using the emulator you have just purchased and fail to
download the firmware.
- When you successfully download the firmware, but fail to start up the
emulator debugger.
- When you want to confirm whether the emulator is operating normally
because, for example, the MCU runs out of control or something is
wrong with the trace results.
This function can be enabled only when you are starting up the emulator
debugger.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 54 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
4) Specifying the clock frequency
Specifying the clock frequency
Specify the target MCU operation clock and clock dividing ratio.
- Specify the operation clock and clock dividing ratio.
- In case where no value was set up in the area in which the operation clock
is Specified, the unit operates with the reference clock (16MHz) inside the
emulator (PC4701) as time measurement resource.
- In case where no value was set up in the area in which the dividing ratio is
Specified, the unit operates as “No dividing”. (Same as when “1” was
Specified.)
(2) Debugging Information tab
Referencing the compiler and the object format
Reference the compiler you are using and the format of the object file
output by the compiler.
To make this setting, use the dialog box that is brought up by selecting
[Debug] and then [Debug Settings...] from the menu.
Specifying the method for storing debug information
There are two methods for storing debug information: on memory method
and an on demand method.
Select the compiler you are using.
(By default, the on memory is selected)
When selecting the on demand method, check the [On Demand] check box.
z On Memory
The debug information is stored in the memory of your computer. This
method is suitable when the size of the load module (user program) is
small.
z On Demand
The debug information is saved to a reusable temporary file. When you
download the same load module for a second time on, the saved debug
information will be reused and the load module can therefore be
downloaded fast. This method is suitable when the size of the load
module (user program) is large.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 55 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
(3) Work area tab
1) Specifying the firmware
Specifying the firmware file
For the radio button of the firmware group box, be sure to click “Default”.
Specifying the work area
Specifies the top address which is used as a work area at the start address
area of the work area group box.
- For details on specifying the work area, refer to “3.2 Setting the Work
Area” (page 51).
- The top address of the work area is set to “2C00h” by default.
- In single-chip mode , set the work area address at “10000h”.
(4) Memory space expansion tab
(5) Clock tab
Specifying the memory space expansion mode
When the memory expansion mode or micro processor mode is selected,
specify whether you want to use the memory space expansion mode or not.
When you use the memory expansion mode, select “Mode2”, and when not,
select “Normal”.
Note that “Mode1” cannot be selected.
Specifying the target clock
Specify the clock sources supplied to the MCU (main clock and sub clock).
Select the appropriate clock sources according to the clock used by your
target MCU.
z Internal
Emulation pod’s internal clock
z External
User system clock
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 56 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
(6) Script tab
Automatically executing a script command
To automatically execute a script command when starting up the
debugger, click the “Refer...” button and specify the script file to
be executed.
Clicking the “Refer...” button brings up a file selection dialog box.
The script file you have selected is displayed in the Init File:
section of the dialog box shown here. If you do not want to
automatically execute a script command, delete the character
string displayed in the Init File: section of the dialog box.
What you specify here is reflected at only startup. If you specify
back again in the Init dialog box after startup, whatever you
specified has no effect (restart the emulator debugger).
When the tab settings (1) to (6) above are completed, click OK button.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 57 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
3.3.2 Checking Connections of the Emulator System
Check to see that the emulator debugger has been connected correctly to the emulator.
Checking connections of the emulator system
When the emulator debugger is connected correctly to the emulator after
you have finished setting up the Init dialog box and the MCU Setting dialog
box, you will see a message “Connected” displayed on the “Debug” tab of
the Output window.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 58 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
3.4 Downloading Program
Download the user program to be debugged.
1) Downloading from the work space window
Downloading the program
Download the object program you want to debug.
Select Download from “xxx.x30” of “Download module”.
Or you can select “Download module” from the “Debug” menu for
the same effect.
2) Showing the source program
Editor (Source) window
The editor (source) window is a window that always shows the
content of the source file corresponding to the current position of the
program counter (hereafter, PC).
The position of the PC at which the user program has stopped is
marked by a yellow arrow.
The operation up to the cursor position can be executed, and the
software break point can be set up and reset, etc.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 59 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
3.5 Program execution
(1) Program execution
CPU reset
Resets the target MCU.
Go
Runs the program beginning with the current PC position.
Reset Go
Runs the program after resetting the target MCU.
Step In
Single-steps the program executing each statement (including those in
functions).
Step Over
Single-steps the program executing each function call as one step.
Step Out
Exits a function and stops at a statement in the program next to the one that
called the function.
STOP
Stops the program.
Go Free
Runs the program beginning with the current PC position. The software and
hardware breaks set in it are temporarily ignored.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 60 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
(2) Software break
1) Setting the software break point
Execution setup procedure with software break:
(1) By double-clicking the break point setting line on the software
break point setting column in the editor (source) window, the
break point can be set up and released. (In this case, the red
circle is displayed on the setting line as shown in the window on
the left.)
2) Execution completed with software break
(2)
The cursor stops in the position where the software break was set up.
The statement in which the software break was set up is not
executed.
Click the execution button.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 61 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
(3) Executing up to the cursor position (Come command)
1) Specifying the Come command
Setup procedure for executing COME command
(1) Click the line in the editor (source) window at which you
want the program to execute.
2) After the Come command has finished
(2)
The cursor stops in the position where the come command was
executed.
The statement specified with the come command is not executed.
Click the Come button.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 62 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
3.6 Hardware Break
Hardware break is set by event condition such as FETCH or DATA ACCESS, etc. The program stops after executing the
instruction at the set breakpoint (after several cycles).
(1) Break event setup dialog box
1) Opening the hardware break point setup dialog box
Hardware Break Point
Clicking this button opens the hardware break point setup dialog box.
2) H/W Break Points Setting Window
H/W Break Points Setting Window
Select the “Enable H/W Break” check box, and this break function will be
enabled, allowing you to set hardware break points.
Setting Break Event
Click the event line at which you want set a break event.
3) Break event setting dialog box
Specifying the event type
Click to select the event type you want to set.
- FETCH
Detects an instruction prefetch.
- DATA ACCESS
Detects a memory access.
- BIT SYMBOL
Detects a bit access.
- INTERRUPT
Detects an occurrence of interruption or interrupt completion.
- TRIGGER
Detects a signal from the external trace signal input cable.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 63 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
(2) When FETCH is selected
1) Window for setting addresses
Setting the address
You can set eight conditions, e.g., a specified address, a specified address
range, etc. When you have finished setting the address, click OK.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 64 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
(3) When DATA ACCESS is selected
1) Window for setting the address
Setting the address
Sets the address by “Address” tab.
You can set eight conditions, e.g., a specified address, a specified address
range, etc.
When you have finished setting the address, set the data.
2) Window for setting data
Setting data
Sets the address by “Data” tab.
You can set eight conditions, e.g., specified data, specified data range, etc.
Setting the access condition
You can set three conditions, e.g., read, write, and read/write. When you
have finished setting the data and access condition, click OK.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 65 of 104
M3062PT3-RPD-E User’s Manual 3. Usage (How to Use the Emulator Debugger)
3) Example Data Settings
Setting events for wordwise accesses to the even-addresses
td(BCLK-AD) Address output delay time 25 See left
th(BCLK-AD) Address output hold time (BCLK standard) 4 See left
th(RD-AD) Address output hold time (RD standard) 0 -1
th(WR-AD) Address output hold time (WR standard) (*2) See left
td(BCLK-CS) Chip-select output delay time 25 See left
th(BCLK-CS) Chip-select output hold time (BCLK standard) 4 See left
td(BCLK-ALE) ALE signal output delay time 25 See left
th(BCLK-ALE) ALE signal output hold time -4 See left
td(BCLK-RD) RD signal output delay time 25 See left
th(BCLK-RD) RD signal output hold time 0 See left
td(BCLK-WR) WR signal output delay time 25 See left
th(BCLK-WR) WR signal output hold time 0 See left
td(BCLK-DB) Data output delay time (BCLK standard) 40 See left
th(BCLK-DB) Data output hold time (BCLK standard) 4 See left
td(DB-WR) Data output delay time (WR standard) (*1) See left
th(WR-DB) Data output hold time (WR standard) (*2) See left
*1. Calculated by the following formula according to the frequency of BCLK.
Actual MCU [ns] This product [ns]
Min. Max. Min. Max.
()
n
BCLKf
*2. Calculated by the following formula according to the frequency of BCLK.
105.0
×
BCLKf
×−
9
)(
9
105.0
)(
[ns]
40
−
[ns] n: "3" for 3-wait
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 73 of 104
*1 Calculated by the following formula according to the frequency of BCLK.
9
×)(100.5
Address output delay time 25 26
Address output hold time (BCLK standard) 4 See left
Address output hold time (RD standard) (*1) See left
Address output hold time (WR standard) (*1) See left
Chip-select output delay time 25 See left
Chip-select output hold time (BCLK standard) 4
Chip-select output hold time (RD standard) (*1)
Chip-select output hold time (WR standard) (*1)
RD signal output delay time 25 See left
RD signal output hold time 0 -1
WR signal output delay time 25 See left
WR signal output hold time 0 -4
Data output delay time (BCLK standard) 40 See left
Data output hold time (BCLK standard) 4 See left
Data output delay time (WR standard) (*2) See left
Data output hold time (WR standard) (*1) See left
ALE output delay time (BCLK standard) 25 See left
ALE output hold time (BCLK standard) -4 See left
ALE output delay time (Address standard) (*3) See left
ALE output hold time (Address standard) (*4) See left
After address RD signal output delay time 0 -4
After address WR signal output delay time 0 -3
Address output floating start time 8 17
10−
[ns]
Actual MCU
[ns]
Min. Max. Min. Max.
This product
[ns]
See left
See left
See left
BCLKf
*2 Calculated by the following formula according to the frequency of BCLK.
()
n
BCLKf
*3 Calculated by the following formula according to the frequency of BCLK.
100.5
×
BCLKf
*4 Calculated by the following formula according to the frequency of BCLK.
100.5
×
BCLKf
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 75 of 104
Table 4.4 and Figure 4.3 list the timing requirements in memory expansion mode and microprocessor mode.
Table 4.4 Timing requirements
Symbol Item
Actual MCU
[ns]
This product
[ns]
Min. Max. Min. Max.
tsu(DB-RD)
tsu(RDY-BCLK)
tsu(HOLD-BCLK)
th(RD-DB)
th(BCLK-RDY)
th(BCLK-HOLD)
td(BCLK-HLDA)
Data input setup time 40 65
RDY# input setup time 30 55
HOLD# input setup time 40 80
Data input hold time 0 See left
RDY# input hold time 0 See left
HOLD# input hold time 0 See left
HLDA# output delay time 40 See left
Common to “with wait” and “no wait” (actual MCU)
BCLK
th(BCLK-HOLD)
Hi-Z
HOLD input
HLDA output
P0,P1,P2,P3,P4,
P5
0 -- P52
tsu(HOLD-BCLK)
td(BCLK-HLDA)
Common to “with wait” and “no wait” (this product)
BCLK
th(BCLK -HOLD)
Hi-Z
HOLD input
HLDA output
P0,P1,P2,P3,P4,
P5
0 -- P52
tsu(HOLD-BCLK)
td(BCLK-HLDA)
td(BCLK-HLDA)
td(BCLK-HLDA)
* Compared with an actual MCU, this product enters high-impedance state after a 0.5 cycle delay.
Figure 4.3 Timing requirements
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 77 of 104
*1 Calculated by the following formula according to the frequency of BCLK.
()
n
BCLKf
9
105.0
×−
)(
Address output delay time 30 See left
Address output hold time (BCLK standard) 4 See left
Address output hold time (RD standard) 0 -1
Address output hold time (WR standard) (*2) See left
Chip-select output delay time 30 See left
Chip-select output hold time (BCLK standard) 4 See left
ALE signal output delay time 30 See left
ALE signal output hold time -4 See left
RD signal output delay time 30 See left
RD signal output hold time 0 See left
WR signal output delay time 30 See left
WR signal output hold time 0 See left
Data output delay time (BCLK standard) 40 See left
Data output hold time (BCLK standard) 4 See left
Data output delay time (WR standard) (*1) See left
Data output hold time (WR standard) (*2) See left
40
−
[ns] n: "3" for 3 wait
Actual MCU
[ns]
Min. Max. Min. Max.
This product
[ns]
*2 Calculated by the following formula according to the frequency of BCLK.
9
×)(100.5
10−
[ns]
BCLKf
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 78 of 104
*1 Calculated by the following formula according to the frequency of BCLK.
9
×)(100.5
Address output delay time 50 See left
Address output hold time (BCLK standard) 4 See left
Address output hold time (RD standard) (*1) See left
Address output hold time (WR standard) (*1) See left
Chip-select output delay time 50 See left
Chip-select output hold time (BCLK standard) 4 See left
Chip-select output hold time (RD standard) (*1) See left
Chip-select output hold time (WR standard) (*1) See left
RD signal output delay time 40 See left
RD signal output hold time 0 -1
WR signal output delay time 40 See left
WR signal output hold time 0 -4
Data output delay time (BCLK standard) 50 See left
Data output hold time (BCLK standard) 4 See left
Data output delay time (WR standard) (*2) See left
Data output hold time (WR standard) (*1) See left
ALE output delay time (BCLK standard) 40 See left
ALE output hold time (BCLK standard) -4 See left
ALE output delay time (Address standard) (*3) See left
ALE output hold time (Address standard) (*4) See left
After address RD signal output delay time 0 -4
After address WR signal output delay time 0 -3
Address output floating start time 8 17
10−
[ns]
Actual MCU
[ns]
Min. Max. Min. Max.
This product
[ns]
BCLKf
*2 Calculated by the following formula according to the frequency of BCLK.
()
n
BCLKf
*3 Calculated by the following formula according to the frequency of BCLK.
100.5
×
BCLKf
*4 Calculated by the following formula according to the frequency of BCLK.
100.5
×
BCLKf
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 80 of 104
Table 4.7 and Figures 4.6 show timing requirements in memory expansion mode and microprocessor mode.
Table 4.7 Timing requirements
Actual MCU
Symbol Item
[ns]
This product
[ns]
Min. Max. Min. Max.
tsu(DB-RD)
tsu(RDY-BCLK)
tsu(HOLD-BCLK)
th(RD-DB)
th(BCLK-RDY)
th(BCLK-HOLD)
td(BCLK-HLDA)
Data input setup time 50 65
RDY# input setup time 40 55
HOLD# input setup time 50 80
Data input hold time 0 See left
RDY# input hold time 0 See left
HOLD# input hold time 0 See left
HLDA# output delay time 40 See left
Common to “with wait” and “no wait” (actual MCU)
BCLK
HOLD input
HLDA output
P0,P1,P2,P3,P4,
0 -- P52
P5
tsu(HOLD-BCLK)
td(BCLK-HLDA)
th(BCLK-HOLD)
Hi-Z
Common to “with wait” and “no wait” (this product)
BCLK
HOLD input
HLDA output
P0,P1,P2,P3,P4,
0 -- P52
P5
tsu(HOLD-BCLK)
td(BCLK-HLDA)
th(BCLK-HOLD)
Hi-Z
td(BCLK-HLDA)
td(BCLK-HLDA)
* Compared with an actual MCU, this product enters high-impedance state after a 0.5 cycle delay.
Figure 4.6 Timing requirements
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 82 of 104
4.3 Differences between the Actual MCU and Emulator
Differences between the actual MCU and emulator are shown below. When debugging the MCU using this product, be careful
about the following precautions.
IMPORTANT
Note on Differences between the Actual MCU and Emulator:
Note on Emulating External Area:
z Operations of the emulator system differ from those of actual MCUs as listed below.
(1) Reset condition
Set the time for rising (0.2 Vcc to 0.8 Vcc) and falling (0.8 Vcc to 0.2 Vcc) 1μs or less.
(2) Initial values of internal resource data of an MCU at power-on
(3) Internal memories (ROM and RAM) capacities etc.
With this emulator system, regardless of ROM and RAM of the MCU you use, all the areas other than
the SFR area and a reserved area (addresses 27000h--27FFFh) can be read and written into.
(4) Oscillator circuit
In the oscillator circuit where an oscillator is connected between pins XIN and XOUT, oscillation does
not occur because a flexible cable or converter board is used between the evaluation MCU and the user
system. It is same for pins XCIN and XCOUT. For notes on when using the oscillator circuit on the user
system, refer to "2.9.3 (5) Using the Oscillator Circuit on the User System" (page 44).
(5) A/D converter function
Because a converter board, flexible cable and other devices are used between the evaluation MCU and
the user system, the A/D converter operates differently from that of the actual MCU.
(6) Characteristics of ports P0 to P5, and P10
This product emulates some I/O ports (P0 to P5, and P10). Therefore, the electrical characteristics of
these ports differ from those of an actual MCU.
(7) Address and status of BHE#
When the internal RAM or ROM area of an MCU is accessed during user program execution, actual
MCUs retain a preceding address and status of BHE#, while this product does not.
(8) Status of a data bus
In stop or wait mode, actual MCUs retain a preceding status of a data bus, while with this product a data
bus is floating.
(9) ALE signal
When the internal RAM or SFR area of the MCU is accessed during user program execution, with the
actual MCU, ALE output is fixed to Low, while this product outputs ALE signal.
(10) Pins P57/CLKout
When pins P57/CLKout are used for CLKout function and Fc is selected by Clock output selection in
stop mode, CLKout output does not stop.
(11) DBC, single-step and BRK instruction interrupt vector table addresses
As the emulator uses the DBC, single-step and BRK instruction interrupt vector table addresses, when
reading these addresses, the downloaded data cannot be read (see Table 4.8).
Table 4.8 Vector table addresses for the emulator
z To emulate the external area using emulation memory in this product, set 0 wait (8MHz) or less or 1 wait or
more.
Factor of interruption Vector table addresses Data read
DBC*1 FFFF4h--FFFF7h Indefinite
Single-step*1 FFFECh--FFFEFh Indefinite
BRK instruction FFFE4h--FFFE7h Indefinite
*1 Interruption for the emulator only
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 83 of 104
Note on Setting "1" to Protect Bit 2 (PCR2) with Sub Clock:
z A low input from the user system to pin RESET# is accepted only while a user program is being executed
(only while the RUN status LED on the PC4701's front panel is lit).
z A low input from the user system to pin NMI# is accepted only while a user program is being executed (only
while the RUN status LED on the PC4701's front panel is lit).
z Be sure to input "L" to pin RDY# of the user system while a user program is being executed (when the RUN
status LED on the PC4701's front panel is lit). Inputting "L" to pin RDY# during the user program stopping
may cause a malfunction of the emulator.
z You cannot use the hold function with this product. Be sure to input "H" to pin HOLD# of the user system
when you use a processor mode other than single-chip mode. If "L" is input to pin HOLD#, this product will
not work normally.
z Even if a user program is not being executed (including when run-time debugging is being performed), the
evaluation MCU keeps running so as to control the emulation pod. If a maskable interrupt is requested when
the user program is not being executed (including when run-time debugging is being performed), the
maskable interrupt request cannot be accepted, because the emulator disables interrupts. The interrupt request
is accepted immediately after the user program execution is started.
z Take note that when the user program is not being executed (including when run-time debugging is being
performed), a peripheral I/O interruption is not accepted.
z With this product, the program is stopped with a loop program to a specific address. Therefore, if a DMA
request is generated while the program is stopped, a DMA transfer is executed, but it may not be performed
correctly. Also note that the below registers have been changed to generate a DMA transfer as explained here
even when the program is stopped.
DMA0 transfer counter registers : TCR0
DMA1 transfer counter registers : TCR1
z With this product, ports P0 to P5 are not pulled up by the pullup control register. To pull up the ports P0 to
P5, mount the included network resistor (51kΩ) to the inside of the emulator as occasion demands. How to
mount it, refer to "2.9.6 Installing and Removing Network Resistors for Pullup" (page 48).
z The initial value of pullup control register 1 (PUR1) of an actual MCU varies depending on the level of the
CNVss pin, while that of this product is always “00h”.
Table 4.9 Initial value of pullup control register 1 (PUR1)
CNVss = “L” CNVss = “H”
Actual MCU PUR1 = “00h” PUR1 = “02h”
This product PUR1 = “00h” PUR1 = “00h”
z When the CPU clock is set to the sub-clock (low-speed mode or low power dissipation mode), even if you
enable the PRC2 bit, writing to the register protected by the PRC2 bit (PD9, S3C, and S4C registers) cannot
be done properly. When you enable the PRC2 bit and write to the register protected by the PRC2, do not set
the CPU clock to the sub-clock.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 84 of 104
Notes on Setting "1" to Protect Bit 2 (PRC2) in Division by 2 Mode:
z Under the following conditions, even if you enable the PRC2 bit, writing to the register protected by the
PRC2 bit (PD9, S3C, and S4C registers) cannot be done properly.
(1) Between when stop mode is released and when a hardware reset is executed
(2) Between when low power dissipation mode is enabled and when a hardware reset is executed
z Therefore, if the condition (1) or (2) applies, when you enable the PRC2 bit and write to the register protected
by the PRC2, do not set the CPU clock to the main clock in division by 2 mode.
Note on the Input Thresholds for the Pins P1_5/INT3, P1_6/INT4 and P1_7/INT5:
z With this product, regarding pins P1_5/INT3, P1_6/INT4 and P1_7/INT5, a device which port or data bus
inputs to and a device which INT interrupt inputs to are different as follows:
Device which port or data bus inputs to: Port emulation FPGA (input level: TTL)
Device which INT interrupt inputs to: Evaluation MCU for emulating peripheral functions (input level:
CMOS Schmidt)
Therefore, the port input level can be read as “H” immediately after an INT interrupt (falling), and the port
input level can be read as “H” immediately before an INT interrupt (rising).
Note on Input Level for KI0# to KI3#:
z With this product, the KI0# to KI3# are TTL input level using the port emulation FPGA although these are
the CMOS Schmidt input level with the actual MCU. Therefore, the wrong interrupt may occur near the
threshold of the TTL level (2.0V to 0.8V) when the input signal is slow changing.
Note on Shifting from On-chip Oscillator Mode to Stop Mode:
z Do not shift from on-chip oscillator mode or on-chip oscillator low power dissipation mode to stop mode.
Otherwise, this product cannot return by an interrupt.
Note on Debugging M16C/30P Group MCUs:
z The M16C/62P Groups MCUs are used as an evaluation MCU for this product. An initial value of the internal
reserved area expansion bit (PM13) for the M16C/62P Group is different from that of for the M16C/30P
Group.
(1) An initial value of the internal reserved area expansion bit (PM13) for the M16C/62P Group: 1
(2) An initial value of the internal reserved area expansion bit (PM13) for the M16C/30P Group: 0
When developing the program for the M16C/30P Group, be sure to set the initial value of the internal
reserved area expansion bit (PM13) to “0” in the program.
Note on Final Evaluation:
z Be sure to evaluate your system with an evaluation MCU. Before starting mask production, evaluate your
system and make final confirmation with a CS (Commercial Sample) version MCU.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 85 of 104
Notes on using this product are listed below. When debugging the MCU using the emulator, be careful about the following
precautions.
IMPORTANT
Note on the Version of the Emulator Debugger:
z Be sure to use this product with one of the following emulator debuggers.
1. M16C PC4701 Emulator Debugger
2. M3T-PD30 V8.20 Release 1 or later
Note on Selecting the MCU File:
z It is necessary to make an MCU file which contains information such as, SFR area, internal RAM area and
internal ROM area, etc. to use this product. For creating an MCU file, see “3.1 Making an MCU File” on
page 50. For each memory map of MCU, refer to its hardware manual.
Note on Malfunctions in the PC4701 System:
Notes on Downloading Firmware:
Notes on the Self-check:
Note on Quitting the Emulator Debugger:
Note on Clock Supply to the MCU:
z If the emulator malfunctions because of interference like external noise, do the following to remedy the
trouble.
(1) Press the RESET switch on the emulator front panel.
(2) If normal operation is not restored after step (1), shut OFF power to the emulator once and then reactivate
it.
z Before using this product for the first time, it is necessary to download the dedicated firmware (control
software built into the PC4701). Please note that, to do this, it is necessary to start up the emulator main unit
in maintenance mode. For firmware download procedures, see "2.6.2 Downloading Firmware in Maintenance
Mode" (page 27). Once the firmware has been downloaded, the product can be used by simply turning on the
power.
z Do not shut off the power while downloading the firmware. If this happens, the product will not start up
properly. If power is shut off unexpectedly, redownload the firmware in maintenance mode.
z Be sure to disconnect the user system before downloading the firmware.
z If the self-check does not result normally (excluding target status error), the emulation pod may be damaged.
Then contact your local distributor.
z Be sure to disconnect the user system before executing the self-check.
z To restart the emulator debugger after it ends, always shut power to the emulator off once and wait about 10
seconds, then turn the power on again.
z A clock supplied to the evaluation MCU is selected by the Clock tab in the Init dialog box of the emulator
debugger.
(1) When Internal is selected:
A clock generated by the oscillation circuit in the emulation pod is supplied to the evaluation MCU. The
clock is continually supplied to the evaluation MCU regardless of "user system clock status" and "user
program execution status".
(2) When External is selected:
Clock supply to the evaluation MCU depends on oscillation status (oscillate/off) of the user system.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 92 of 104
Notes on Setting the Work Area When Starting Up the Emulator Debugger:
Notes on MAP References and Settings:
z With this product, the emulator uses 54 bytes as a work area in emulation memory. Therefore, according to
the memory mapping of the MCU you use, specify the work area addresses.
In single-chip mode, set the work area address at 10000h.
In memory expansion or microprocessor mode, specify a work area other than the areas listed below.
- SFR area (0000h--003FFh)
- External area of multiplex bus setting
- Reserved area of 27000h--27FFFh
- Stack area used by the emulator for reset command execution (0FFF9h--0FFFFh)
- F6000h to F63FFh and F8000h to F83FFh
For details, see “3.2 Setting the Work Area” on page 51.
z The top address of the work area should be an even-numbered address.
z Be sure to set the work area as MAP=INT.
For example, when the work area set at 10000h, 54 bytes of the addresses 10000h to 10035h used by the
emulator.
z For details on referencing and setting MAP information, see the emulator debugger user's manual.
Make settings as follows:
(1) MAP = INT
The emulation memory inside this product becomes effective.
Set this at MCU internal ROM debugging.
(2) MAP = EXT
The emulation memory inside this product is not used.
Set this where the MCU internal resource (SFR) or resources on the user system are used.
z Be sure to set the SFR of the MCU as MAP = EXT, and set the reserved area of the MCU as MAP = INT.
z Be sure to set mappings in word unit.
z When setting 0FFF8h to 0FFFFh to EXT:
This product uses the 7 byte area 0FFF9h through 0FFFFh as the stack area. If this 7 byte memory cannot be
read or written to, reset cannot be properly effected. As a result, you need to alter the map settings if the
condition given below is met.
(1) With the system which shifts from the single-chip mode to memory expansion (or microprocessor)
mode, using the 8 byte area of 0FFF8h to 0FFFFh set to EXT.
(2) With the system which starts up in microprocessor mode, using the 8 byte area of 0FFF8h to 0FFFFh
set to EXT and there is not enough memory to read or write.
The procedures to alter the MAP settings when the conditions (1) or (2) above are met.
(1) Set the 8 byte area of 0FFF8h to 0FFFFh to INT.
(2) Execute the RESET command by use of the emulator debugger.
(3) Set the stack pointer.
(Example)
RESET: FCLR I
LDC #0480H, SP <-- Set the stack pointer
: (Stop the program after executing this instruction)
(4) Set the 8 byte area 0FFF8h through 0FFFFh to EXT.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 93 of 104
Note on Operation When Not Executing the User Program:
Note on Stop and Wait Modes:
Note on Watchdog Function:
Note on Reading Internal Resources of the MCU:
Note on Protect Register:
Note on Debugging in Flash Memory Area in CPU Rewrite Mode:
z With this product, a maximum 7 bytes of the user stack is consumed. Therefore, ensure the +7 bytes
maximum capacity used by the user program as the user stack area. If the user stack does not have enough
area, do not use areas which cannot be used as stack (SFR area, RAM area which stores data, or ROM area)
as a work area. Using areas like this is a cause of user program crashes and destabilized emulator control.
z With this product, bit 7 of processor mode register 1 (wait bit PM17) is forcibly set to "1" (with wait) when
the user program is not executed (e.g. when the program is stopped or when run-time debugging is being
performed). Therefore, if the external area set to 0 wait is accessed by other than the user program (such as
debugging operation), one wait is inserted. However, when wait bit PM17 is referenced by the dump window
etc. the value set during user program execution is displayed.
z Do not single step an instruction shifting to stop or wait mode. It may cause communication errors.
z The MCU's watchdog timer can be used only while programs are being executed. To use it otherwise, disable
the watchdog timer.
z When the registers listed in Table 4.13 are read with an emulator, those results will be the following (the data
in the MCU are not effected).
(1) Results of real-time trace
The data values of the cycles read are not displayed correctly.
(2) Real-time RAM monitor
The data values read are not displayed correctly.
Table 4.13 Registers and symbols not displayed normally
z The protect is not canceled when bit 2 of protect register PRCR (PRC2), which enables writing into the port
P9 direction register and the SI/Oi control register, is changed with the below procedure.
(1) Step execution of the "instruction for setting ("1") PRC2"
(2) Execution from the instruction setting "1" to PRC2 where a software breakpoint is set
(3) Setting the break point from the "instruction for setting ("1") PRC2" to when the "setting the port P9
direction register and the SI/Oi control register"
(4) Setting ("1") PRC2 from the Memory Window or Script Window
z With this product, an internal flash memory area of an MCU is emulated by high-speed SRAM. Therefore,
you cannot perform debugging operations in CPU rewrite mode.
Symbol
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 94 of 104
z The area displaying break points in the program window of the emulator debugger shows the following
breaks.
(1) Software break
This is a debugging function which generates a BRK interruption by changing an instruction at a
specified address to a BRK instruction (00h) to break a program immediately before the system executes
an instruction at a specified address. The instruction at the preset address will not be executed.
(2) Hardware break
This is a debugging function which breaks a program by setting the detection of an execution of an
instruction at a specified address as a break event. The program will break after the instruction at the
specified address is executed.
Notes on Software Breaks:
z Software breaks change the instruction at a specified address to a BRK (00h). Therefore, take note that when
you reference the result of a trace in bus mode, "00h" is displayed.
z The BRK instruction can be used for the emulator only. You cannot use it in a user program.
z It is not possible to use a software break and a hardware break at the same time. If doing so, it may not
operate normally.
zIn the area where the MAP setting is EXTERNAL, software breaks cannot be used.
Note on Power Supply to the User System:
z Pins Vcc1 and Vcc2 are connected to the user system to observe the voltage. Therefore, the power is not
supplied to the user system from the emulator, design your system so that the user system is powered
separately.
(1) The voltage of the user system should be within the operating range of the evaluation MCU.
(2) Do not change the voltage of the user system after turning on the power.
Notes on Address-Match Interrupts:
Note on Accessing Addresses 00000h and 00001h:
Note on Debugging Operations After Releasing a Reset from the Target:
z To debug address-match interrupts, set a software break or hardware break at the top address of the
address-match interrupt process. If you set a software break or hardware break at an address where an
address-match interrupt occurs, the program may run out of control.
z When an address at which an address-match interrupt occurs is executed in single-step mode, the program
stops after executing the first instruction after returning from the address-match interrupt processing.
z With this product, the yellow LED lights when address 00000h is read out by a process other than an
interrupt. However, because the LED is turned off by other than the reset switch of the emulator main unit,
accessing address 00000h can not be detected properly.
Therefore, to detect that address 00000h is read out by a process other than an interrupt, enable a hardware
breakpoint, and using an event, check the program with the following settings.
z Do not execute debugging operations such as setting a software or hardware break, runtime debugging after
releasing a reset from the user system until an interrupt stack pointer (ISP) is set in the user program.
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 95 of 104
M3062PT3-RPD-E User’s Manual 5. Troubleshooting
5. Troubleshooting
This chapter describes how to troubleshoot when this product does not work properly.
5.1 Flowchart to Remedy the Troubles
Figure 5.1 shows the flowchart to remedy troubles from when power to the emulator is activated until the emulator debugger
starts up. Check this while the user system is not connected. For the latest FAQs visit the Renesas Tools Homepage.
http://www.renesas.com/en/tools
Turning on the power of PC4701
1. Check emulator system connections.
Init dialog box of emulator debugger
1. Check the operating environment etc. of the emulator
Error displayed
See "5.2 (2) Editor (Source) Window is Not Displayed at
PC4701 Front panel LEDs
displayed
Not normal
See "2.4 Connecting the PC4701" (page 23).
2. Redownload the firmware.
See "2.6 Downloading Firmware" (page 27).
3. Restart the PC4701 system.
Not normal or error displayed
debugger.
See the emulator debugger user's manual (online manual).
2. Reinstall the emulator debugger.
Debugger Startup (User System Connected)" (page 98).
See "5.2 (3) Editor (Source) Window is Not Displayed at
Debugger Startup (User System Not Connected)" (page
99).
Editor (source) window of emulator
debugger displayed
Figure 5.1 Flowchart to remedy troubles
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 96 of 104
M3062PT3-RPD-E User’s Manual 5. Troubleshooting
5.2 When the Emulator Debugger Does Not Start Up Properly
(1) When the LED Display of the PC4701 is Abnormal
Table 5.1 LED's abnormal display and its checkpoints
Connection to
Error
LEDs do not light up. -
All LEDs remain lit. -
The "POWER" LED of "STATUS
OF TARGET" does not light up.
The "CLOCK" LED of "STATUS
OF TARGET" does not light up.
The "RESET" LED of "STATUS
OF TARGET" does not go out.
the user
Connected
Disconnected
Connected
Connected
system
Check that the power cable is connected to the PC4701.
See the PC4701 user's manual.
Check the connection between the PC4701 and this product.
See "2.4 Connecting the PC4701" (page 23).
Check that power (Vcc and GND) is properly supplied to the
user system.
(1) Check that both the main/sub clocks are not set to
“External” in the emulator debugger.
See the CLK command of the emulator debugger.
(2) Check the oscillator circuit board is mounted on this
product and it is oscillating properly.
See "2.9.3 Selecting Clock Supply" (page 41).
(1) When the clock supply is set to “External”, check that the
oscillation circuit on the user system is oscillating
correctly.
(2) Check the switches in the emulation pod are correctly set.
See “2.9.4 Switch settings” (page 45).
Check that the reset pin of the user system is at “H” level.
Checkpoint
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 97 of 104
M3062PT3-RPD-E User’s Manual 5. Troubleshooting
(2) Editor (Source) Window is Not Displayed at Debugger Startup (User System Connected)
Table 5.2 Checkpoints of errors when starting up the emulator debugger (user system connected)
Error Checkpoint
ERROR 16005:
Can't connect with the target.
(1) Check the connection between the PC4701 and host machine.
See the PC4701 User's Manual.
(2) Check that the PC4701 is powered on.
See the PC4701 User's Manual.
(3) Check that all switch settings on the rear of the PC4701 and
interface cable settings of the emulator debugger match.
See the PC4701 User's Manual and the emulator debugger user's
manual (online manual).
ERROR 16211:
The version of the emulator and the
firmware on the target are not same.
(1) Check the connection between the PC4701 and this product.
See “2.4 Connecting the PC4701” (page 23).
(2) Download the proper firmware.
See "2.6 Downloading Firmware" (page 27).
(3) Choose the proper MCU file in the Init dialog box.
See the emulator debugger user's manual (online manual).
(4) Check that the descriptions in the MCU file are correct.
See "3.1 Making an MCU File" (page 50).
ERROR 16215:
Cannot communicate with the debugging
monitor. Execute the RESET command.
(1) Check the connection between the PC4701 and this product.
See “2.4 Connecting the PC4701” (page 23).
(2) Check that the reset pin of the user system is at “H” level.
See the MCU specifications.
(3) Check that CNVSS is held low.
See the MCU specifications.
(4) Check that the oscillator circuit of the emulation pod is oscillating
properly.
See "2.9.3 Selecting Clock Supply" (page 41).
ERROR 16014:
Communication ERROR.
Can't accept data.
(1) Check that the oscillator circuit of the user system is oscillating
properly.
See "2.9.3 Selecting Clock Supply" (page 41).
(2) Check that the PC4701 LEDs at startup show normal operation.
See "2.5.3 LED Display When the Emulator Starts Up Normally"
(page 26).
ERROR 16231:
There was sent undefined data from the
emulator.
Check that the emulator debugger has not been started up without
shutting down the PC4701.
See "4.6 IMPORTANT: Note on Quitting the Emulator Debugger"
(page 92).
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 98 of 104
M3062PT3-RPD-E User’s Manual 5. Troubleshooting
(3) Editor (Source) Window is Not Displayed at Debugger Startup (User System Not Connected)
Table 5.3 Checkpoints of errors when starting up the emulator debugger (user system not connected)
Error Checkpoint
ERROR 16005:
Can't connect with the target.
(1) Check the connection between the PC4701 and host machine.
See the PC4701 User's Manual.
(2) Check that the PC4701 is powered on.
See the PC4701 User's Manual.
(3) Check that all switch settings on the rear of the PC4701 and
interface cable settings of the emulator debugger match.
See the PC4701 User's Manual and the emulator debugger user's
manual (online manual).
ERROR 16211:
The version of the emulator and the
firmware on the target are not same.
(1) Check the connection between the PC4701 and this product.
See "2.4 Connecting the PC4701" (page 23).
(2) Download the proper firmware.
See "2.6 Downloading Firmware" (page 27).
(3) Choose the proper MCU file in the Init dialog box.
See the emulator debugger user 's ma n ual (online manual).
(4) Check that the descriptions in the MCU file are correct.
See "3.1 Making an MCU File" (page 50).
ERROR 16215:
Cannot communicate with the debugging
monitor. Execute the RESET command.
(1) Check that switch settings in the emulation pod are correct.
See "2.9.4 Switch Settings" (page 45).
(2) Check that the oscillator circuit of the emulation pod is oscillating
properly.
See "2.9.3 Selecting Clock Supply" (page 41).
ERROR 16014:
Communication ERROR.
Can't accept data.
Check that the PC4701 LEDs at startup show normal operation.
See "2.5.3 LED Display When the Emulator Starts Up Normally"
(page 26).
ERROR 16231:
There was sent undefined data from the
emulator.
Check that the emulator debugger has not been started up without
shutting down the PC4701.
See "4.6 IMPORTANT: Note on Quitting the Emulator Debugger"
(page 92).
REJ10J0040-0600 Rev.6.00 July 01, 2006 Page 99 of 104
M3062PT3-RPD-E User’s Manual 5. Troubleshooting
5.3 How to Request for Support
After checking the items in "5 Troubleshooting", fill in the text file which is downloaded from the following URL, then send