Renesas | Emulation Pod M30620T2-RPD-E | Technical information | Renesas Emulation Pod M30620T2-RPD-E Technical information

To our customers,
Old Company Name in Catalogs and Other Documents
On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology
Corporation, and Renesas Electronics Corporation took over all the business of both
companies. Therefore, although the old company name remains in this document, it is a valid
Renesas Electronics document. We appreciate your understanding.
Renesas Electronics website: http://www.renesas.com
April 1st, 2010
Renesas Electronics Corporation
Issued by: Renesas Electronics Corporation (http://www.renesas.com)
Send any inquiries to http://www.renesas.com/inquiry.
Notice
1.
2.
3.
4.
5.
6.
7.
All information included in this document is current as of the date this document is issued. Such information, however, is
subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please
confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to
additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website.
Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights
of third parties by or arising from the use of Renesas Electronics products or technical information described in this document.
No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights
of Renesas Electronics or others.
You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part.
Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of
semiconductor products and application examples. You are fully responsible for the incorporation of these circuits, software,
and information in the design of your equipment. Renesas Electronics assumes no responsibility for any losses incurred by
you or third parties arising from the use of these circuits, software, or information.
When exporting the products or technology described in this document, you should comply with the applicable export control
laws and regulations and follow the procedures required by such laws and regulations. You should not use Renesas
Electronics products or the technology described in this document for any purpose relating to military applications or use by
the military, including but not limited to the development of weapons of mass destruction. Renesas Electronics products and
technology may not be used for or incorporated into any products or systems whose manufacture, use, or sale is prohibited
under any applicable domestic or foreign laws or regulations.
Renesas Electronics has used reasonable care in preparing the information included in this document, but Renesas Electronics
does not warrant that such information is error free. Renesas Electronics assumes no liability whatsoever for any damages
incurred by you resulting from errors in or omissions from the information included herein.
Renesas Electronics products are classified according to the following three quality grades: “Standard”, “High Quality”, and
“Specific”. The recommended applications for each Renesas Electronics product depends on the product’s quality grade, as
indicated below. You must check the quality grade of each Renesas Electronics product before using it in a particular
application. You may not use any Renesas Electronics product for any application categorized as “Specific” without the prior
written consent of Renesas Electronics. Further, you may not use any Renesas Electronics product for any application for
which it is not intended without the prior written consent of Renesas Electronics. Renesas Electronics shall not be in any way
liable for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for an
application categorized as “Specific” or for which the product is not intended where you have failed to obtain the prior written
consent of Renesas Electronics. The quality grade of each Renesas Electronics product is “Standard” unless otherwise
expressly specified in a Renesas Electronics data sheets or data books, etc.
“Standard”:
8.
9.
10.
11.
12.
Computers; office equipment; communications equipment; test and measurement equipment; audio and visual
equipment; home electronic appliances; machine tools; personal electronic equipment; and industrial robots.
“High Quality”: Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems; anticrime systems; safety equipment; and medical equipment not specifically designed for life support.
“Specific”:
Aircraft; aerospace equipment; submersible repeaters; nuclear reactor control systems; medical equipment or
systems for life support (e.g. artificial life support devices or systems), surgical implantations, or healthcare
intervention (e.g. excision, etc.), and any other applications or purposes that pose a direct threat to human life.
You should use the Renesas Electronics products described in this document within the range specified by Renesas Electronics,
especially with respect to the maximum rating, operating supply voltage range, movement power voltage range, heat radiation
characteristics, installation and other product characteristics. Renesas Electronics shall have no liability for malfunctions or
damages arising out of the use of Renesas Electronics products beyond such specified ranges.
Although Renesas Electronics endeavors to improve the quality and reliability of its products, semiconductor products have
specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Further,
Renesas Electronics products are not subject to radiation resistance design. Please be sure to implement safety measures to
guard them against the possibility of physical injury, and injury or damage caused by fire in the event of the failure of a
Renesas Electronics product, such as safety design for hardware and software including but not limited to redundancy, fire
control and malfunction prevention, appropriate treatment for aging degradation or any other appropriate measures. Because
the evaluation of microcomputer software alone is very difficult, please evaluate the safety of the final products or system
manufactured by you.
Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental
compatibility of each Renesas Electronics product. Please use Renesas Electronics products in compliance with all applicable
laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS
Directive. Renesas Electronics assumes no liability for damages or losses occurring as a result of your noncompliance with
applicable laws and regulations.
This document may not be reproduced or duplicated, in any form, in whole or in part, without prior written consent of Renesas
Electronics.
Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this
document or Renesas Electronics products, or if you have any other inquiries.
(Note 1) “Renesas Electronics” as used in this document means Renesas Electronics Corporation and also includes its majorityowned subsidiaries.
(Note 2) “Renesas Electronics product(s)” means any product developed or manufactured by or for Renesas Electronics.
User’s Manual
M306NAT2-RPD-E
User’s Manual
Emulation Pod for M16C/6N Group M306NA and
M306NB
Rev.2.00 2004.07
• IC61-1004-051 is a product of Yamaichi Electronics Co., Ltd.
• NQPACK, YQPACK, YQSOCKET, YQ-Guide, HQPACK, TQPACK and TQSOCKET are products of Tokyo Eletech Corporation.
Keep safety first in your circuit designs!
• Renesas Technology Corporation and Renesas Solutions Corporation put 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
• These materials are intended as a reference to assist our customers in the selection of the Renesas Technology 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 Corporation, Renesas Solutions Corporation or a third party.
• Renesas Technology Corporation and Renesas Solutions Corporation assume 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.
• 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 Corporation and Renesas
Solutions Corporation without notice due to product improvements or other reasons. It is therefore recommended that customers contact
Renesas Technology Corporation, Renesas Solutions Corporation or an authorized Renesas Technology 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 Corporation and Renesas Solutions Corporation assume 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
Corporation and Renesas Solutions Corporation by various means, including the Renesas home page (http://www.renesas.com).
• 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 Corporation and Renesas Solutions Corporation assume no responsibility for any damage, liability or
other loss resulting from the information contained herein.
• Renesas Technology 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 Corporation, Renesas Solutions Corporation or an
authorized Renesas Technology 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.
• The prior written approval of Renesas Technology Corporation and Renesas Solutions Corporation is necessary to reprint or reproduce
in whole or in part these materials.
• 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.
• Please contact Renesas Technology Corporation or Renesas Solutions Corporation for further details on these materials or the products
contained therein.
Precautions to be taken when using this product
• 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.
• In no event shall Renesas Solutions Corporation be liable for any consequence arising from the use of this product.
• Renesas Solutions Corporation 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 Corporation guarantees the renovation or the provision under any
circumstances.
• 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.
For inquiries about the contents of this document or product, fill in the text file the installer of the emulator debugger generates in the
following directory and email to your local distributor.
\SUPPORT\Product-name\SUPPORT.TXT
Renesas Tools Homepage http://www.renesas.com/en/tools
( 2 / 76 )
Preface
The M306NAT2-RPD-E is an emulation pod for the M16C/6N Group M306NA and M306NB of 16bit MCUs. It is used with a PC4701 emulator.
This user's manual mainly describes specifications of the M306NAT2-RPD-E emulation pod and
how to setup it. For details on the following products, which are used with the M306NAT2-RPD-E,
refer to each product's user's manual or online manual.
• Emulator:
• Emulator debugger:
PC4701 User's Manual
M3T-PD30 User's Manual
All the components of this product are shown in "Table 2.1 Package components" (page 22) of this
user's manual. If there is any question or doubt about this product, contact your local distributor.
To use the product properly
Precautions for Safety
• In both this 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.
• The icons' graphic images and meanings are given in "Chapter 1. Precautions for
Safety" (page 7). Be sure to read this chapter before using the product.
When using outside Japan
• When using in Europe, the United States, or Canada, be sure to use both the emulator
and the emulation pod which meet local standards. EMI standards are not met when
this product is used with the PC4700H or PC4700L emulator.
( 3 / 76 )
Contents
Chapter 1. Precautions for Safety ........................................................................................... 7
1.1 Safety Symbols and Meanings .............................................................................. 8
Chapter 2. Preparation .......................................................................................................... 21
2.1 Package Components .......................................................................................... 22
2.2 Other Tool Products Required for Development ................................................ 22
2.3 Name of Each Part .............................................................................................. 23
(1) System Configuration............................................................................... 23
(2) Inside of the Emulation Pod ..................................................................... 24
2.4 When Using the Emulator for the First Time ...................................................... 25
Chapter 3. Setting Up ........................................................................................................... 27
3.1 Removing the Upper Cover ................................................................................ 28
3.2 Setting Switches and Pullup Resistors ................................................................ 29
3.3 Selecting Clock Supply ....................................................................................... 33
(1) Using the Oscillator Circuit on the Target System .................................. 34
(2) Changing the Internal Oscillator Circuit of the Emulation Pod ............... 35
(3) Replacing the Oscillator Circuit Boards .................................................. 36
3.4 A-D Conversion Bypass Capacitor ..................................................................... 37
3.5 Connecting the PC4701 ....................................................................................... 38
(1) Connecting the Cable to the PC4701 ....................................................... 38
(2) Connecting the Cable to the Emulation Pod ............................................ 39
3.6 Connecting the Target System ............................................................................ 40
(1) Connecting to a 100-pin 0.65-mm-pitch LCC Socket ............................. 41
(2) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 1) ................ 42
(3) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 2) ................ 43
(4) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 3) ................ 44
Chapter 4. Usage .................................................................................................................. 45
4.1 Making an MCU File for M3T-PD30 ................................................................. 46
4.2 Turning On the Power ......................................................................................... 46
(1) Checking the Connection of Emulator System ........................................ 46
(2) Turning On the Power .............................................................................. 46
(3) LED Display When PC4701 Starts Up Normally .................................... 47
4.3 Downloading Firmware ...................................................................................... 48
(1) When It is Necessary to Download Firmware ......................................... 48
(2) Downloading Firmware in Maintenance Mode ....................................... 48
4.4 Self-check ............................................................................................................ 49
(1) Self-check Procedure ............................................................................... 49
(2) If an Error is Detected in the Self-check .................................................. 49
( 4 / 76 )
Chapter 5. Specifications ...................................................................................................... 51
5.1 Specifications ...................................................................................................... 52
5.2 Operation Timing in Memory Expansion Mode and Microprocessor Mode ......... 53
(1) Separate Bus, No-wait ..............................................................................53
(2) Separate Bus, With Wait, Accessing External Memory Area .................55
(3) Multiplex Bus, With Wait, Accessing External Memory Area ............... 57
(4) Timing Requirements ...............................................................................59
5.3 Electrical Characteristics .....................................................................................61
5.4 Connection Diagram ...........................................................................................62
5.5 External Dimensions ...........................................................................................63
(1) External Dimensions of the Emulation Pod ............................................. 63
(2) External Dimensions of the Converter Board M3T-FLX-100LCC ......... 64
(3) Reference Dimensional Drawing for 100-pin 0.65-mm-pitch QFP Foot Pattern .... 64
Chapter 6. Troubleshooting .................................................................................................. 65
6.1 Flowchart to Remedy the Troubles ..................................................................... 66
6.2 When the Emulator Debugger Does Not Start Up Properly ...............................67
(1) When LED Display of the PC4701 is Abnormal .....................................67
(2) Program Window Does Not Appear at Debugger Startup (target connected) ....68
(3) Program Window Does Not Appear at Debugger Startup (target not connected) . 69
(4) Errors Occur at Debugger Startup (target connected) ...................................... 69
6.3 Operation Differs from That of Actual MCUs ....................................................70
(1) Cannot Reset from the Target System .....................................................70
(2) Data Values of ROM Area at Power-on Are Different ............................70
(3) HOLD* Control ....................................................................................... 70
(4) A-D Conversion Values are Different from Expected Values .................70
(5) Outputs of ALE, Address and Others are Different from Those of Actual MCUs . 70
Chapter 7. Maintenance and Guarantee ................................................................................ 71
7.1 Maintenance ........................................................................................................ 72
7.2 Guarantee ............................................................................................................72
7.3 Repair Provisions ................................................................................................72
7.4 How to Request for Repair ..................................................................................73
( 5 / 76 )
Terminology
Some specific words used in this user's manual are defined as follows:
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 emulator debugger.
Emulator main unit (Hereafter PC4701)
This means a generic name for emulators for M16C, 7700, 740 Families. For details on specific
models of PC4701, visit the Renesas Tools Homepage at http://www.renesas.com/en/tools
Emulation pod
This means the M306NAT2-RPD-E (this product). This emulation pod is for M16C/6N Group M306NA
and M306NB.
Host machine
This means a personal computer used to control the emulator and emulation pod.
Emulator debugger
This means a software tool M3T-PD30 to control the emulator from the host machine through an
interface.
Firmware
Program that analyzes contents of communication with the emulator debugger and controls the
emulator hardware. This program is installed in the EEPROM. This program is downloadable from
the emulator debugger to upgrade the firmware or to support other MCUs.
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 rise/fall edge of the signal entered from the external trace cable. The former break
function is called data 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.
Evaluation MCU
This means the microcomputer mounted on the emulation pod which is operated in the specific mode
for tools.
Target MCU
This means the microcomputer you are going to debug.
Target system
This means a user's application system using the microcomputer to be debugged.
*
In this user's manual, this symbol is used to show active LOW. (e.g. RESET*: Reset signal)
( 6 / 76 )
Chapter 1. Precautions for Safety
This chapter describes precautions for using this product safely and properly. For precautions for the emulator main unit
and the emulator debugger, refer to each user's manual included with your product.
1.1 Safety Symbols and Meanings ..................................................................................................... 8
WARNING
CAUTION
IMPORTANT
Warning for Installation ............................................................................................... 9
Warnings for Use Environment ................................................................................... 9
Caution to Be Taken for Modifying This Product ....................................................... 9
Cautions to Be Taken for Handling This Product ........................................................ 9
Note on Malfunctions in the PC4701 System .............................................................. 9
Notes on Downloading Firmware .............................................................................. 10
Note on When the Emulator Debugger Ends ............................................................. 10
Note on Final Evaluation ........................................................................................... 10
Notes on Target System ............................................................................................. 10
Notes on MAP References and Settings .................................................................... 11
Note on Setting the Work Area .................................................................................. 11
Note on RESET* Input .............................................................................................. 12
Note on HOLD* Input ............................................................................................... 12
Note on RDY* Input .................................................................................................. 12
Notes on NMI* Input ................................................................................................. 12
Notes on Interrupts ..................................................................................................... 12
Note on Oscillation Stop Detection Function (On-chip Oscillator)........................... 13
Note on Accessing Address 00000h .......................................................................... 13
Note on Stop and Wait Modes ................................................................................... 13
Note on Software Reset ............................................................................................. 13
Note on BRK Instruction and BRK Instruction Interrupt .......................................... 13
Notes on Address Match Interrupt ............................................................................. 13
Note on Commands that Access the Single-step Interrupt Vector Area .................... 14
Notes on Software Breaks and Hardware Breaks ...................................................... 14
Note on Protect Register (PRC2) ............................................................................... 14
Notes on Pullup Control Register .............................................................................. 14
Note on Reading Internal Resources of an MCU ...................................................... 15
Notes on Watchdog Function..................................................................................... 15
Notes on Stack Area................................................................................................... 15
Note on DMA Transfer .............................................................................................. 15
Note on Clock Supply to the MCU ............................................................................ 16
Note on Differences between Actual MCU and Emulator ........................................ 17
( 7 / 76 )
Chapter 1. Precautions for Safety
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.
1.1 Safety Symbols and Meanings
WARNING
If the requirements shown in the "WARNING"
sentences are ignored, the equipment may
cause serious personal injury or death.
CAUTION
If the requirements shown in the "CAUTION"
sentences are ignored, the equipment may
malfunction.
IMPORTANT
It means important information on using this
product.
In addition to the three above, the following are also used as appropriate.
means WARNING or CAUTION.
Example:
CAUTION AGAINST AN ELECTRIC SHOCK
means PROHIBITION.
Example:
DISASSEMBLY PROHIBITED
means A FORCIBLE ACTION.
Example:
UNPLUG THE POWER CABLE FROM THE RECEPTACLE.
The following pages describe the symbols "WARNING", "CAUTION", and "IMPORTANT".
( 8 / 76 )
WARNING
Warning for Installation:
• Do not set this product in water or areas of high humidity. Spilling water or some other liquid into
the main unit can cause an unrepairable damage.
Warnings for Use Environment:
• The emulation pod is air-cooled with the ventilation slot. Therefore, do not block the ventilation
slot. When heated to high temperatures, the emulation pod may not work properly.
• 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.
CAUTION
Caution to Be Taken for Modifying This Product:
• Do not disassemble or modify this product. Disassembling or modifying this product can cause
damage. Disassembling and modifying the product will void your warranty.
Cautions to Be Taken for Handling This Product:
• Use caution when handling the main unit. Be careful not to apply a mechanical shock.
• Do not touch the connector pins of the emulator main unit and the target MCU connector pins. Static
electricity may damage the internal circuits.
• Do not pull the emulation pod main unit by the flexible cable (FLX120-RPD) for connecting to the
emulator main unit or the flexible cable (FLX64, FLX100, FLX160 or M3T-FLX160C) for
connecting the target system. The cable may cause a break.
• Flexible cable (FLX120-RPD) for connecting to the emulator main unit and the flexible cable
(FLX64, FLX100, FLX160 or M3T-FLX160C) for connecting the target system are different from
earlier models. The slits make them more flexible. However, excessive flexing or force may break
conductors.
• 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.
IMPORTANT
Note on Malfunctions in the PC4701 System:
• 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.
( 9 / 76 )
IMPORTANT
Notes on Downloading Firmware:
• Before using this product for the first time, it is necessary to download the dedicated firmware
(control software for the emulation pod built into the PC4701). Please note that, to do this, it is
necessary to start up the PC4701 in maintenance mode. For firmware download procedures, see
"4.3 Downloading Firmware" (page 48). Once the firmware has been downloaded, the product can
be used by simply turning on the power.
• 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.
• Except when a target status error occurs, if the self-check is not complete successfully, there may
be trouble with the product. In such case, contact your sales representative. However, perform the
self-check in the below setup.
(1) Target system:
Not connected
(2) Emulation pod internal switches: At their factory settings
Note on When the Emulator Debugger Ends:
• To restart the emulator debugger after it ends, always shut power to the emulator module off once
and then on again.
Note on Final Evaluation:
• Be sure to evaluate your system with an actual MCU. Before starting mask production, evaluate
your system and make final confirmation with a CS (Commercial Sample) version MCU.
Notes on Target System:
• The Vcc pin of the emulator is connected to the target system to observe the voltage of the target
system. Therefore design your system so that the emulator MCU is powered by the target system.
• The voltage of the target system should be within the range of the MCU specification (4.2--5.5 V).
• Do not change the voltage of the target system after turning on the power.
• Before powering on your emulator system, check that the host machine, the emulator main unit,
the converter board and target system are all connected correctly. Next, turn on the power to each
equipment following the procedure below.
(1) Turn ON/OFF the target system and the PC4701 emulator as simultaneously as possible.
(2) When the PC4701 and emulator debugger start up, check the target status LEDs on the
emulator main unit's front panel to see if this product is ready to operate.
• Is the power supplied?
Check target status LED (POWER) is ON.
• Is the reset is released?
Check target status LED (RESET) is OFF.
For details, refer to "Chapter 4. Usage" (page 45).
( 10 / 76 )
IMPORTANT
Notes on MAP References and Settings:
• For details on referencing and setting MAP information, see the user's manual of the emulator
debugger M3T-PD30.
MAP settings are as follows:
(1) MAP = INT
Emulation memory in this product becomes effective.
Set this to debug internal ROM and internal RAM of an MCU.
(2) MAP = EXT
Emulation memory in this product is not used.
Set this to use MCU internal resources (SFR) or resources on the target system.
• Be sure to set the SFR area to EXT.
• When setting 0FFFCh to 0FFFFh to EXT:
This product uses the 4 bytes area 0FFFCh--0FFFFh as the stack area. If this 4 bytes memory cannot
be read or written to, reset cannot be properly effected. As a result, you need to alter the map settings
if either of the two conditions given below is met.
(1) With the system which shifts from single-chip mode to memory expansion (or microprocessor) mode, using the 4 bytes area of 0FFFCh--0FFFFh set to EXT.
(2) With the system which starts up in microprocessor mode, using the 4 bytes area of 0FFFCh-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 are shown
below.
○
○
(1) Set the 4 bytes area of 0FFFCh--0FFFFh to INT.
(2) Execute the RESET command of the emulator debugger M3T-PD30.
(3) Set the stack pointer.
(Example)
RESET:
FCLR
LDC
I
#0480H, SP <-- Set the stack pointer.
(Program stops after executing this instruction.)
(4) Set the 4 bytes area 0FFFCh--0FFFFh to EXT.
Note on Setting the Work Area:
• To use this product, it is necessary to set the work area in the internal reserved area of the MCU.
However, do not set it in the last 10 bytes of the internal reserved area. And be sure to set the internal
reserved area to INT. (Set the work area by the Init dialog box of the emulator debugger M3TPD30.)
For M306NA and M306NB, set this area at address 2C00h. The emulator uses 10 bytes area of
02C00h to 02C09h.
( 11 / 76 )
IMPORTANT
Note on RESET* Input:
• The RESET* input from the target system is accepted only while a user program is being executed
(only while the RUN status LED on the PC4701's front panel is lit).
Notes on HOLD* Input:
• Be sure to input "Low" to the HOLD* pin of the target system during the user program executing
(while the RUN status LED on the PC4701's front panel is lit). Inputting "Low" to the HOLD* pin
when stopping the user program may cause a malfunction of the emulator.
• When inputting "Low" to the HOLD* pin to run into the HOLD state, P00 to P52 will be in the
HOLD state delaying by 2.5 cycles than the actual MCU (see Table 5.5 and Figure 5.5).
Note on RDY* Input:
• Be sure to input "Low" to the RDY* pin of the target system during the user program executing
(while the RUN status LED on the PC4701's front panel is lit). Inputting "Low" to the RDY* pin
when stopping the user program may cause a malfunction of the emulator.
Notes on NMI* Input:
• NMI* input from the target system is accepted only while a user program is being executed (only
while the RUN status LED on the PC4701's front panel is lit).
• The NMI* interrupt is generated in the following situations.
(1) Immediately after the NMI* pin changes from "High" to "Low" level during target program
execution
(2) After the reset is released by the target system when the NMI* pin is "Low" level during target
program execution
(3) Immediately after program execution starts with the NMI* pin "Low" level, following the
reset input from the debug software or emulator main unit
(4) Immediately after program execution starts when the NMI* pin is "High" level immediately
before the target program stops and changes to "Low" level when target program execution
starts
Notes on Interrupts:
• Even when the target program is not being executed (while the target program is stopped or during
runtime debugging), the evaluation MCU keeps running so as to control the emulation pod.
Therefore, note that timers and other components do not stop running even though the target
program is not being executed.
• If a maskable interrupt request is generated when the target program is not being executed (while
the target program is stopped or during runtime debugging), the request is not accepted because the
emulator disables all interrupts. If an interrupt request is generated when the target program is not
being executed, but the target program enables that interrupt, it will be accepted immediately after
program execution starts.
( 12 / 76 )
IMPORTANT
Note on Oscillation Stop Detection Function (On-chip Oscillator):
• Take note that you can not debug a program using the oscillation stop detection function (on-chip
oscillator). To use this function, be sure to evaluate a system with an actual MCU.
• This product is equipped with an M16C/62A MCU as an emulation MCU. Because the M16C/62A
MCU does not have an oscillation stop detection register, when the register is read out, undefined
values are read out. To use the oscillation stop detection function (on-chip oscillator), be sure to
evaluate your system with an actual MCU.
Note on Accessing Address 00000h:
• With the M16C/60 Group MCUs, when a maskable interrupt is generated, the interrupt data
(interrupt No. and interrupt request level) stored in address 00000h is read out. Also, the interrupt
request bit is cleared when address 00000h is read out. Consequently, when the address 00000h
readout instruction is executed or when address 00000h is read out in the cause of a program
runaway, a malfunction occurs in that the interrupt is not executed despite the interrupt request,
because the request bit of the highest priority interrupt factor enabled is cleared.
For this malfunction, when the reading out to the address 00000h is generated excluding the
interrupt, the yellow LED lights up to alarm. When this LED lights, there is a possibility of wrong
access to address 00000h, therefore check the program. This LED is turned off by the RESET
switch of the emulator main unit.
Note on Stop and Wait Modes:
• Do not perform step execution at addresses in the stop or wait mode. It may cause communication
errors.
Note on Software Reset:
• Do not use a software reset. It may not operate correctly.
Note on BRK Instruction and BRK Instruction Interrupt:
• With this emulator system, BRK instructions and BRK instruction interrupts are exclusively used
for software break functions. Therefore, you can not use them for your program.
Notes on Address Match Interrupt:
• Do not set software breaks at the same addresses as address-match interrupts as the program may
run out of control. Therefore, to debug address-match interrupts, set software and hardware breaks
at the top address of an address-match interrupt processing.
• Do not set a hardware break within 4 instructions before an address at which an address-match
interrupt occurs. If you do set a hardware break in this range, the program cannot be controlled from
the emulator.
• When an address at which an address-match interrupt occurs is executed in one-step mode, the
program stops after executing the first instruction after returning from the address-match interrupt
processing.
( 13 / 76 )
IMPORTANT
Note on Commands that Access the Single-step Interrupt Vector Area:
• Do not perform the below debugging operations with the single step interrupt vector area (addresses
FFFECh--FFFEFh).
(1) Step execution of commands that access the single step interrupt vector area
(2) Program execution using commands that access the single step interrupt vector area when a
software breakpoint is set in those commands
Notes on Software Breaks and Hardware Breaks:
• Software breaks generate BRK interrupts by substituting the proper instruction to the BRK
instruction. Therefore, when referencing the result of a trace in bus mode, "00h" is displayed for
the instruction fetch address where a software break is set, and when referencing in reverse
assemble mode, "BRK" instruction is displayed.
• 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.
• In the area where the MAP setting is EXT, software breaks cannot be used.
Note on Protect Register (PRC2):
• Make note of the fact that the protect is not canceled when protect register (PRC2), which enables
writing in the port P7 and port P9 direction registers and the SI/O3 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
register for the protect"
(4) Setting ("1") PRC2 from the dump window or script window
Notes on Pullup Control Register:
• Ports P00 to P57 are not pulled up by the pullup control register.
When pulling up ports P00 to P57, apply a resistance to the inside of the emulator. How to apply
it, refer to "3.2 Setting Switches and Pullup Resistors" (page 29).
Note: Ports P60 to P107 are pulled up by the pullup control register.
Note: The pullup control register can read and write from P00 to P107 properly.
• When the pullup control register 1 (bit 1 of address 3FDh = PU11) of ports P44--P47 is set to "1"
(pulled up), ports P15--P17 are pulled up regardless of the value of the pullup control register 0 (bit
3 of address 3FCh = PU03) of ports P14--P17.
( 14 / 76 )
IMPORTANT
Note on Reading Internal Resources of an MCU:
• When the registers that are listed in Table 1.1 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 1.1 Registers and symbols not displayed normally
Register
Symbol
DMA source pointers 0, 1
SAR0, SAR1
DMA destination pointers 0, 1
DAR0, DAR1
DMA transfer counters 0, 1
TCR0, TCR1
DMA control registers 0, 1
DM0CON, DM1CON
Notes on Watchdog Function:
• The MCU's watchdog timer can be used only while programs are being executed. To use it
otherwise, disable the watchdog timer.
• If the reset circuit of the target system has a watchdog timer, disable it when using the emulator.
Notes on Stack Area:
• With this product, a maximum 8 bytes of the user stack is consumed.
• 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 work area. Using areas like this is a cause of
user program crashes and destabilized emulator control. Therefore, ensure the +8 bytes maximum
capacity used by the user program as the user stack area.
Note on DMA Transfer:
• With this product, the program is stopped with a loop program to a specific address. Therefore, if
a DMA request is generated by a timer or other source while the program is stopped, DMA transfer
is executed. However, make note of the fact that DMA transfer while the program is stopped may
not be performed correctly. Also note that the below registers have been changed to generate DMA
transfer as explained here even when the program is stopped.
DMA0 transfer counter register: TCR0
DMA1 transfer counter register: TCR1
( 15 / 76 )
IMPORTANT
Note on Clock Supply to the MCU:
• Clock can be supplied to the evaluation MCU in one of the following two ways. This is determined
by emulator debugger clock selection.
(1) When Internal is selected:
The 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 "target 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 target
system.
( 16 / 76 )
IMPORTANT
Note on Differences between Actual MCU and Emulator:
• Operations of the emulator system differ from those of actual MCUs as listed below.
(1) Reset condition
Set the rise time (0.2 Vcc to 0.8 Vcc) 1 µs or less.
(2) Data values of ROM and RAM areas at power-on
(3) Internal memories (ROM and RAM) capacities etc.
With this emulator system, "INT" (emulation memory ON) is the default for mapping areas
other than the SFR area (addresses 000h--3FFh). For this reason, the emulation memory can
read and write in areas other than the SFR, internal RAM and internal ROM.
(4) Oscillator circuit
• Make note of the fact that in the oscillator circuit where a resonator is connected between
the XIN and XOUT pins, oscillation does not occur because a flexible cable, buffer IC and other
devices are used between the evaluation MCU and the target system. It is same for sub-clock
oscillator circuits (XCIN and XCOUT).
• For note on when using the oscillator circuit on the target system, refer to "3.3 (1) Using the
Oscillator Circuit on the Target System" (page 34).
(5) Characteristics of ports P00 to P57
With this product, ports P00 to P57 are connected via emulation circuit. The device used for
the port emulation circuit is as follows.
Device: M60081L-0142FP
(6) Characteristics of port P10
With this product, parts of I/O ports (P10) is connected to the target system via analog switch
circuit. Therefore the electrical characteristics are slightly different from those of actual
MCUs.
(7) HOLD* control
When inputting "Low" to the HOLD* pin to run into the HOLD state, P00 to P52 will be in
the HOLD state delaying by 2.5 cycles than the actual MCU (see Figure 5.5 and Table 5.5).
(8) 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 1.2).
Table 1.2 Vector table addresses for the emulator
Factor of interruption
Vector table addresses
Data for reading
DBC*1
FFFF4h--FFFF7h
Indefinite
1
Single-step*
FFFECh--FFFEFh
Indefinite
BRK instruction
FFFE4h--FFFE7h
Indefinite
*1 Interruption for the debugger only
(9) A-D conversion
As a analog switch, flexible cable, pitch converter board and other devices are used between
the evaluation MCU and the target system, some characteristics are slightly different from
those of the actual MCU.
(10) Oscillation stop detection function
With this product, you can not debug the oscillation stop detection function.
(11) Accessing to oscillation stop detection register
With this product, when the register is read out, undefined values are read out.
(12) On-chip oscillator operation
With this product, you cannot use on-chip oscillator operation.
( 17 / 76 )
IMPORTANT
(13) A-D input group select function
When using the A-D input group select function, the following settings are required.
i) When selecting port P0 for A-D input
• Set the whole 8-bit of direction registers P100--P107 to input.
• Set the pullup control registers of P100--P107 to no-pullup.
• P100--P107 cannot be used as an input pin of I/O port and key input interrupt function.
ii) When selecting port P2 for A-D input
• Set the whole 8-bit of direction registers P100--P107 to input.
• Set the pullup control registers of P100--P107 to no-pullup.
• P100--P107 cannot be used as input pins of I/O port and key input interrupt function.
iii) When selecting port P10 for A-D input
• There is no restriction.
(14) Outputs of the actual MCU and this product
Table 1.3 Differences of outputs between actual MCU and this product (when executing program)
Access area
SFR area
(MAP = EXT)
Internal RAM
Signal
Actual MCU
This product
Address
BHE*
Outputs
Outputs
Data
Outputs
(floating during read cycle)
Outputs
(floating during read cycle)
RD*
WR*
Outputs
("Low" at write cycle,
"Low" at read cycle)
Outputs
("Low" at write cycle,
"Low" at read cycle)
CS*
Does not output
(fixed to "High")
Does not output
(fixed to "High")
ALE
Does not output
(fixed to "Low")
Outputs
∗
Address
BHE*
Retains previous status
Outputs
∗
Data
Floating
Floating
RD*
WR*
Does not output
(fixed to "High")
Does not output
(fixed to "High")
CS*
Does not output
(fixed to "High")
Does not output
(fixed to "High")
ALE
Does not output
(fixed to "Low")
Outputs
Address
BHE*
Outputs
Outputs
Data
Outputs
(inputs external data at read cycle)
Outputs
(inputs external data at read cycle)
RD*
WR*
Outputs
("Low" at write cycle,
"Low" at read cycle)
Outputs
("Low" at write cycle,
"Low" at read cycle)
CS*
Outputs
Outputs
ALE
Outputs
Outputs
Internal ROM
External area
( 18 / 76 )
∗ for difference
∗
IMPORTANT
Table 1.4 Differences of outputs between actual MCU and this product (in stop mode)
Access area
-
Signal
Actual MCU
This product
Address
BHE*
Retains previous status
Retains previous status
Data
Retains previous status
Floating
RD*
WR*
Does not output
(fixed to "High")
Does not output
(fixed to "High")
CS*
Retains previous status
Retains previous status
ALE
Does not output
(fixed to "High")
Does not output
(fixed to "High")
∗ for difference
∗
Table 1.5 Differences of outputs between actual MCU and this product (in wait mode)
Access area
-
Signal
Actual MCU
This product
Address
BHE*
Retains previous status
Retains previous status
Data
Retains previous status
Floating
RD*
WR*
Does not output
(fixed to "High")
Does not output
(fixed to "High")
CS*
Retains previous status
Retains previous status
ALE
Does not output
(fixed to "High")
Does not output
(fixed to "High")
Table 1.6 Outputs of this product when the user program is stopping
Signal
This product
Address
BHE*
Outputs
Data
Floating
RD*
WR*
Only RD* outputs
(WR* is fixed to "High")
CS*
Outputs
ALE
Outputs
( 19 / 76 )
∗ for difference
∗
MEMO
( 20 / 76 )
Chapter 2. Preparation
This chapter describes the package components, the system configuration and the preparation for using this product for the
first time.
2.1 Package Components ................................................................................................................... 22
2.2 Other Tool Products Required for Development ......................................................................... 22
2.3 Name of Each Part ....................................................................................................................... 23
(1) System Configuration ........................................................................................................... 23
(2) Inside of the Emulation Pod.................................................................................................. 24
2.4 When Using the Emulator for the First Time .............................................................................. 25
( 21 / 76 )
Chapter 2. Preparation
2.1 Package Components
The M306NAT2-RPD-E package consists of the following items. When unpacking, check to see if
your M306NAT2-RPD-E contains all of these items.
Table 2.1 Package components
Item
Quantity
M306NAT2-RPD-E emulation pod main unit
1
FLX120-RPD flexible cable for connecting PC4701
1
M3T-FLX-100LCC converter board for connecting target system
1
OSC-3 16 MHz oscillator circuit board for main clock (premounted)
1
OSC-2 oscillator circuit board
1
IC61-1004-051 100-pin LCC socket
1
Resistor arrays for pulling up ports P00--P57 (51 kΩ)
12
Hardware tool user registration FAX sheet (English)
1
Hardware tool user registration FAX sheet (Japanese)
1
M306NAT2-RPD-E user's manual (this manual)
1
M306NAT2-RPD-E user's manual (Japanese)
1
Please keep the M306NAT2-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 any of these items are missing or found faulty, please contact your local distributor. Also, if there
is any question or doubt about the packaged product, contact your local distributor.
For details on the IC61-1004-051, contact Yamaichi Electronics Co., Ltd.
2.2 Other Tool Products Required for Development
To bring forward programs development on the M16C/6N Group MCUs, the products listed below
are necessary in addition to those contained package above. Get them separately.
Converter boards
Table 2.2 Other tool products
Product
Product name
Notes
Emulator main unit
PC4701
Required
Emulator debugger
M3T-PD30
Required
M3T-DUMMY100S
100-pin 0.65-mm-pitch QFP
(100P6S-A)
M3T-DIRECT100S
M3T-FLX-100NRB
* To purchase these products, contact your local distributor.
( 22 / 76 )
Required according to the foot
pattern of the target system
(see 3.6 "Connecting the Target
System" on page 40)
2.3 Name of Each Part
(1) System Configuration
Emulator debugger
Interface cable
Host machine
(2) FLX120-RPD
(1) M306NAT2-RPD-E
PC4701
(3) FLX100
(4) Converter board
Figure 2.1 System configuration
(1) to (4) in Figure 2.1 are included in this product package.
(1) Emulation pod M306NAT2-RPD-E
This emulation pod contains an evaluation MCU, emulation memory and circuits to feature the
debugging functions.
(2) Flexible cable FLX120-RPD
This is a 120-pin flexible cable for connecting the PC4701 emulator and the emulation pod.
(3) Flexible cable FLX100
This is a 100-pin flexible cable for connecting the emulation pod and the target system.
(4) Converter board
This is a converter board for connecting to the target system. For details, refer to "3.6 Connecting
the Target System" (page 40).
( 23 / 76 )
(2) Inside of the Emulation Pod
Figure 2.2 Internal view of the emulation pod
(1) MCU-dependent board
Board grouping parts (pins and added functions) which vary according to MCU model.
(2) Base board
Board for the M16C Series MCUs which controls the interface with the PC4701 and the
evaluation MCU.
(3) Memory board
Board for the M16C Series MCUs on which the emulation memory (1 MB) and the map memory
(4 bit × 1 M) are mounted.
(4) Oscillator circuit board
Oscillator circuit board on which the oscillation module device (16 MHz) is mounted. It is
possible to change the operating frequency by replacing it with a separately prepared oscillator
circuit board.
( 24 / 76 )
2.4 When Using the Emulator for the First Time
If you have purchased this emulation pod newly, it is necessary to download the firmware. The
download procedure is given in Figure 2.3.
Before attempting to download the firmware, check the emulator debugger is installed and the
emulator is connected to the host machine. For more information, see each user's manual of the
emulator debugger and the PC4701.
Connect the PC4701 and this product.
Within 2 seconds of turning the power ON, press the
RESET switch of the PC4701 and check maintenance
mode is accessed.
See "3.5 Connecting the PC4701"
(page 38).
See "4.3 Downloading Firmware"
(page 48).
Download the firmware using the emulator debugger.
End the emulator debugger and shut the power of the
PC4701 OFF.
Figure 2.3 Firmware download procedure when using the emulator for the first time
To make sure the emulation pod works properly, run the self-check. For self-check procedure, see
"4.4 Self-check" (page 49).
( 25 / 76 )
MEMO
( 26 / 76 )
Chapter 3. Setting Up
This chapter describes switch settings required for using this product and how to connect this product to the PC4701 and
the target system.
3.1 Removing the Upper Cover ......................................................................................................... 28
3.2 Setting Switches and Pullup Resistors ........................................................................................ 29
3.3 Selecting Clock Supply ............................................................................................................... 33
(1) Using the Oscillator Circuit on the Target System ............................................................... 34
(2) Changing the Internal Oscillator Circuit of the Emulation Pod............................................ 35
(3) Replacing the Oscillator Circuit Boards ............................................................................... 36
3.4 A-D Conversion Bypass Capacitor.............................................................................................. 37
3.5 Connecting the PC4701 ............................................................................................................... 38
(1) Connecting the Cable to the PC4701 .................................................................................... 38
(2) Connecting the Cable to the Emulation Pod ......................................................................... 39
3.6 Connecting the Target System ..................................................................................................... 40
(1) Connecting to a 100-pin 0.65-mm-pitch LCC Socket .......................................................... 41
(2) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 1) ............................................. 42
(3) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 2) ............................................. 43
(4) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 3) ............................................. 44
( 27 / 76 )
Chapter 3. Setting Up
To use this emulation pod with your target system, it is necessary to set as follows. Set the following
after removing the upper cover.
• Change the oscillation frequency in the emulation pod.
• Set the switches according to the target system.
• Install pullup resistors to ports P00 to P57.
• Install the A-D conversion bypass capacitor.
3.1 Removing the Upper Cover
The procedure of removing the upper cover is shown below.
(1) Remove the four screws of both sides of this product and lift off the upper cover. (see Figure 3.1)
(2) Set the jumper switches and others as described below.
(3) Replace the upper cover and secure the four screws.
Figure 3.1 Removing the upper cover
CAUTION
When Removing the Upper Cover:
• Always shut OFF power when removing the upper cover or setting the switches.
• Do not touch the connector pins of the emulator main unit and the target MCU
connector pins. Static electricity may damage the internal circuits.
( 28 / 76 )
3.2 Setting Switches and Pullup Resistors
Figure 3.2 shows the positions of switches and a position for installing pullup resistors. Tables 3.1,
3.2 list how to set each switch and Figure 3.3 shows how to install pullup resistors.
Figure 3.2 Positions of switches and their factory-settings
( 29 / 76 )
Table 3.1 Switch settings of the M306NAT2-RPD-E (1/2)
Signal
Switch
Setting
Description
H
OPEN
L
SW1
CNVSS
(Factory-setting)
Pulls down pin CNVSS of MCU with a resistance of
33 kΩ. Be sure to set this when the target system
is not connected in single-chip mode or memory
expansion mode.
H
CNVSS
OPEN
SW1
L
Connects pin CNVSS to the target system. Be sure
to set this when the target system is connected.
SW1
CNVSS
H
OPEN
L
Pulls up pin CNVSS of MCU with a resistance of 33
kΩ. Be sure to set this when the target system is
not connected in microprocessor mode.
SW1
CNVSS
8
OPEN
16
Pulls down pin BYTE of MCU with a resistance of
33 kΩ. Be sure to set this when the target system
is not connected in 16-bit bus mode.
SW2
BYTE
(Factory-setting)
8
BYTE
OPEN
SW2
16
Connects pin BYTE to the target system. Be sure
to set this when the target system is connected.
SW2
BYTE
8
OPEN
16
Pulls up pin BYTE of MCU with a resistance of 33
kΩ. Be sure to set this when the target system is
not connected in 8-bit bus mode.
SW2
BYTE
XOUT
OPEN
XOUT
SW3
Does not connect pin XOUT of MCU to the target
system.
SW3
XOUT
(Factory-setting)
XOUT
Connects pin XOUT of MCU to the target system.
OPEN
SW3
XOUT
( 30 / 76 )
Table 3.2 Switch settings of the M306NAT2-RPD-E (2/2)
Signal
Switch
Setting
Description
XCOUT
OPEN
Connects pin P86/X COUT of MCU to the target
system. (Uses pin P86/XCOUT as port P86)
P86
SW4
P86/XCOUT
(Factory-setting)
XCOUT
P86/XCOUT
Does not connect pin P86/XCOUT of MCU. (Uses
P86/XCOUT pin as XCOUT and opens XCOUT.)
OPEN
SW4
P86
SW4
P86/XCOUT
XCOUT
OPEN
P86
Connects pin P86/X COUT of MCU to the target
system. (Uses pin P86/XCOUT as XCOUT and connect
XCOUT to the target system.)
SW4
P86/XCOUT
XCIN
P87
P87/XCIN
Connects the P87/XCIN pin of MCU to the target
system. (Uses P87/XCIN pin as port P87)
SW5
P87/XCIN
(Factory-setting)
SW5
XCIN
Uses pin P87/XCIN as XCIN.
P87
SW5
P87/XCIN
L
H Only this setting is available.
JP2
(Factory-setting)
JP2
L
H Do not set in this way.
JP2
IMPORTANT
Note on Switch Settings:
• Switches CNVSS (SW1) and BYTE (SW2) are used for debugging operation without
connecting the target system. When the target system is connected, set both of them
"OPEN" (middle).
( 31 / 76 )
It is not possible to control the pullup by the pullup control registers of ports P00 to P57 (possible to
read and write the pullup control registers).
However, as this product has sockets for installing the pullup resistors, it is possible to pull up by
mounting the resistor arrays included with this product. For the positions for installing them, see
Figure 3.3.
Figure 3.3 Positions for installing the pullup resistors
( 32 / 76 )
3.3 Selecting Clock Supply
There are two ways to supply a clock to the MCU, using the oscillator circuit of the emulation pod
or using the oscillator circuit on the target system. Table 3.3 lists the factory-settings of each clock
supply.
Table 3.3 Clock supply to the MCU
Clock
Description
Display of emulator debugger Default setting
Internal oscillator circuit of emulation pod
(OSC-3: 16 MHz)
Internal
Yes
Target System
External
-
Internal oscillator circuit of emulation pod
(32.768 kHz)
Internal
-
Target System
External
Yes
XIN-XOUT
XCIN-XCOUT
IMPORTANT
Notes on Changing the Clock Supply:
• The clock supply can be set by the Init dialog box when starting up the emulator
debugger or inputting CLK command on the script window.
• For XCIN-XCOUT , it is necessary to set switches in the emulation pod. For details, refer
to "3.2 Setting Switches and Pullup Resistors" (page 29).
( 33 / 76 )
(1) Using the Oscillator Circuit on the Target System
When turning on the power supply, the internal clock of the emulation pod is selected to supply the
clock to the MCU. To use the external clock on the target system, change the clock by the Init dialog
box when starting up the emulator debugger or the CLK command on the script window. (For details,
refer to the user's manual of the emulator debugger.)
Figure 3.4 External oscillator circuit
Figure 3.5 Circuit in which oscillation does not occur (same for XCIN-XCOUT)
IMPORTANT
Notes on External Clock:
• To operate the emulation pod with an external clock, construct the oscillator circuit
as shown in Figure 3.4 in the target system and input the oscillator output at 50% duty
(within the operating range of the evaluation MCU) into the XIN pin. And the XOUT
pin should be open.
• Make note of the fact that in the oscillator circuit shown in Figure 3.5 where a
resonator is connected between the XIN and XOUT pins, oscillation does not occur
because a flexible cable, pitch converter board and other devices are used between
the evaluation MCU and the target system. It is same for sub-clock oscillator circuits
(XCIN and XCOUT).
( 34 / 76 )
(2) Changing the Internal Oscillator Circuit of the Emulation Pod
An oscillator circuit board for 16 MHz is mounted on this product. To use the emulation pod at a
frequency other than 16 MHz, build the desired oscillator circuit on the included OSC-2 oscillator
circuit board (bare board) and replace the board installed in the emulation pod when shipped from
the factory.
Figure 3.6 shows a view of the OSC-2 oscillator circuit board (bare board) and where connector pins
are located. Figure 3.7 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: Oscillator output
J1-2: GND
J1-1: Vcc
Figure 3.6 External view of the oscillator circuit board (OSC-2) and connector pin assignment
IC1
11
IC1
10
CLK
8
9
J1-3
R1
*
*
X1 ,X 2
C2
X3*
Vcc
2
1
R2
C1
3
4
5
6
13
12
IC1
* X1: 5.08-mm-pitch 2-pin oscillator
* X2: 2.54-mm-pitch 2-pin oscillator
* X3: 2.54-mm-pitch 3-pin oscillator
Figure 3.7 Circuit of the oscillator circuit board (OSC-2)
( 35 / 76 )
C3
J1-1
14
IC1
7
J1-2
GND
J1-4
GND
IC1: Inverter (Unbuffer)
(3) Replacing the Oscillator Circuit Boards
Figure 3.8 shows how to replace the oscillator circuit boards. For the position of the oscillator circuit
board, see Figure 2.2.
(1) Unscrew the screw connecting the oscillator circuit board.
(2) Lift off the oscillator circuit board.
(3) Attach the J1 connector of another oscillator circuit board
for replacement to the connector of the MCU-dependent
board.
(4) Secure the oscillator circuit board with the screw.
Figure 3.8 Replacing the oscillator circuit boards
( 36 / 76 )
3.4 A-D Conversion Bypass Capacitor
The emulation pod has foot patterns on the board for mounting a bypass capacitor. Mount a suitable
bypass capacitor as occasion demands.
Figure 3.9 shows where the bypass capacitors are mounted, whereas Figure 3.10 shows an
enlargement of the foot patterns.
Figure 3.9 Position for mounting A-D conversion bypass capacitor (underside of the M30620T2-PRT)
Figure 3.10 Foot patterns of an A-D conversion bypass capacitor
IMPORTANT
Note on the A-D Converter:
• Because a flexible board and other devices are used between the evaluation MCU
and the target system, the A-D converter operates differently from the actual MCU.
Make the final evaluation of the A-D converter from the actual MCU.
( 37 / 76 )
3.5 Connecting the PC4701
To connect the emulation pod to the PC4701, use the FLX120-RPD 120-pin flexible cable included
in 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.
(1) Connecting the Cable to the PC4701
Figure 3.11 shows how to connect the PC4701 and FLX120-RPD.
Emulator main unit PC4701
PC4701 side connector of FLX120-RPD
"UPSIDE" should face up.
Secure this screw.
Secure this screw.
Figure 3.11 Connecting the PC4701 and FLX120-RPD
CAUTION
Notes on Connecting the Cable:
• To connect the FLX120-RPD, be sure to hold the both sides of the PC4701 side
connector horizontally with the "UPSIDE" facing up.
• Always shut OFF power before connecting the cable. The power ON state could
destroy internal circuits.
Note on Securing the Screws:
• After connecting the cable to the emulator main unit PC4701, be sure to secure the
screws mounted in both sides of the connector.
( 38 / 76 )
(2) Connecting the Cable to the Emulation Pod
Figure 3.12 shows how to connect the FLX120-RPD and the emulation pod.
Figure 3.12 Connecting the FLX120-RPD and emulation pod
CAUTION
Note on Connecting the Cable:
• Always shut OFF power before connecting the cable. Otherwise, internal circuits
may be damaged.
Note on Securing the Screws:
• After connecting the cable to the emulation pod, be sure to secure the screws.
( 39 / 76 )
3.6 Connecting the Target System
Figure 3.13 shows how to connect this product to the target system.
Emulator probe
Emulator probe
M3T-FLX100-T
(separately available)
Emulator probe
M3T-FLX100-R
(separately available)
100-pin 0.65-mm-pitch
M3T-FLXT-100LCC
(included)
*1
LCC socket
100-pin LCC
(included)
M3T-DUMMY100S
100-pin QFP
(separately available)
M3T-DIRECT100S
M3T-FLX-100NRB
100-pin QFP
100-pin QFP
(separately available) (separately available)
*1: These three products are available in one package.
: No. 1 pin
Figure 3.13 Connecting the emulation pod and target systems
CAUTION
Notes on Connecting the Target System:
• Take care not to attach the converter board in a wrong direction. It may cause a fatal
damage to the emulation pod.
( 40 / 76 )
(1) Connecting to a 100-pin 0.65-mm-pitch LCC Socket
When connecting the emulation pod probe to a 100-pin LCC socket (Yamaichi Electronics Co., Ltd.
IC61-1004-051 etc.) on the target system, following the procedure below.
(1) Attach the FLX100 to the M3T-FLX-100LCC.
(2) Attach the M3T-FLX-100LCC to the 100-pin LCC socket.
FLX100
(1)
M3T-FLX-100LCC
(2)
100-pin LCC socket
No. 1 pin
Target system
Figure 3.14 Connecting a 100-pin 0.65-mm-pitch LCC socket
CAUTION
Notes on Connecting Target System:
• Take care not to attach the converter board in a wrong direction. It may cause a fatal
damage to the emulation pod.
• The small connectors of the M3T-FLX-100LCC are guaranteed for only 20
insertion/removal iterations.
• The IC61-1004-051 included this product is guaranteed for only 20 insertion/
removal iterations.
• For purchasing the IC61-1004-051 and for any inquiry for it, contact Yamaichi
Electronics Co., Ltd.
( 41 / 76 )
(2) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 1)
Figure 3.15 shows how to connect the emulation pod probe to a 100-pin 0.65-mm-pitch QFP
(100P6S-A) foot pattern on the target system with the M3T-DUMMY100S (not included), and here
following is its procedure. For details on the M3T-DUMMY100S, refer to its user's manual.
(1) Attach the M3T-DUMMY100S to the target system.
(2) Attach the M3T-FLX-100LCC to the M3T-DUMMY100S.
FLX100
Evaluation with actual MCU
(2)
M3T-DUMMY100S
(separately available)
MCU with
flash memory etc.
100-pin 0.65-mm-pitch
(10P6S-A) foot pattern
(1)
No. 1 pin
Target system
Figure 3.15 Connecting a 100-pin 0.65-mm-pitch foot pattern (part 1)
CAUTION
Notes on Connecting the Target System:
• Take care not to attach the converter board in a wrong direction. It may cause a fatal
damage to the emulation pod.
• The small connectors of the M3T-DUMMY100S are guaranteed for only 20
insertion/removal iterations.
( 42 / 76 )
(3) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 2)
Figure 3.16 shows how to connect the emulation pod probe to a 100-pin 0.65-mm-pitch QFP
(100P6S-A) foot pattern on the target system with the M3T-DIRECT100S (not included), and here
following is its procedure. For details on the M3T-DIRECT100S, refer to its user's manual.
(1) Attach the M3T-DIRECT100S to the target system.
(2) Attach the M3T-FLX-100LCC to the M3T-DIRECT100S.
FLX100
(2)
M3T-DIRECT100S
(separately available)
(1)
100-pin 0.65-mm-pitch
(100P6S-A) foot pattern
No. 1 pin
Target system
Figure 3.16 Connecting a 100-pin 0.65-mm-pitch foot pattern (part 2)
CAUTION
Notes on Connecting the Target System:
• Take care not to attach the converter board in a wrong direction. It may cause a fatal
damage to the emulation pod.
• The small connectors of the M3T-DIRECT100S are guaranteed for only 20
insertion/removal iterations.
( 43 / 76 )
(4) Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 3)
Figure 3.17 shows how to connect the emulation pod probe to a 100-pin 0.65-mm-pitch QFP
(100P6S-A) foot pattern on the target system with the M3T-FLX-100NRB (not included), and here
following is its procedure. For details on the M3T-FLX-100NRB, refer to its user's manual.
(1) Attach the M3T-FLX-100NRB to the target system.
(2) Attach the M3T-FLX-100LCC to the M3T-FLX-100NRB.
FLX100
(2)
M3T-FLX-100NRB
(separately available) Evaluation with actual MCU
YQSOCKET100RBF
*
YQPACK100RB
HQPACK100RB168
(separately available)
MCU with
flash memory etc.
NQPACK100RB
100-pin 0.65-mm-pitch
(100P6S-A) foot pattern
(1)
No. 1 pin
*: These four products are available in one package.
Target system
Figure 3.17 Connecting a 100-pin 0.65-mm-pitch foot pattern (part 3)
CAUTION
Notes on Connecting the Target System:
• Take care not to attach the converter board in a wrong direction. It may cause a fatal
damage to the emulation pod.
• The small connectors of the M3T-FLX-100NRB are guaranteed for only 20
insertion/removal iterations.
( 44 / 76 )
Chapter 4. Usage
This chapter describes from turning on the power of this product to starting up the emulator debugger.
4.1 Making an MCU File for M3T-PD30 ......................................................................................... 46
4.2 Turning On the Power ................................................................................................................. 46
(1) Checking the Connection of Emulator System ..................................................................... 46
(2) Turning On the Power........................................................................................................... 46
(3) LED Display When PC4701 Starts Up Normally ................................................................ 47
4.3 Downloading Firmware ............................................................................................................... 48
(1) When It is Necessary to Download Firmware ...................................................................... 48
(2) Downloading Firmware in Maintenance Mode .................................................................... 48
4.4 Self-check .................................................................................................................................... 49
(1) Self-check Procedure ............................................................................................................ 49
(2) If an Error is Detected in the Self-check............................................................................... 49
( 45 / 76 )
Chapter 4. Usage
4.1 Making an MCU File for M3T-PD30
It is necessary to change the contents of the MCU file according to the MCU to be developed. Make
the MCU file "M306NA.MCU" for M306NA, "M306NB.MCU" for M306NB and store it in the
"mcufile" folder in the directory same as emulator debugger M3T-PD30 is stored.
The contents of the MCU file (SFR area, internal RAM area, internal ROM area, name of the firmware
file) are shown below. Change the settings according to the MCU to be debugged. Use your text editor
for changing the contents of the MCU file.
Examples of MCU files are shown below.
(1) M306NAMCT-XXXFP (RAM: 5 KB, ROM: 128 KB, file name: M306NA.MCU)
0
3FF
400
17FF
E0000
FFFFF
M30620B
0
: SFR area
Start address
:
End address
: Internal RAM
Start address
:
End address
: Internal ROM
Start address
:
End address
: Name of firmware (Do not change.)
: Expansion No.
M3T-PD30 V.4.00 or later required (Do not change.)
(2) M306NAFGT (RAM: 10 KB, ROM: 256 KB, file name: M306NA.MCU)
0
3FF
400
2BFF
C0000
FFFFF
M30620B
0
: SFR area
Start address
:
End address
: Internal RAM
Start address
:
End address
: Internal ROM
Start address
:
End address
: Name of firmware (Do not change.)
: Expansion No.
M3T-PD30 V.4.00 or later required (Do not change.)
4.2 Turning On the Power
(1) Checking the Connection of Emulator System
Before turning the power ON, check the connection of the PC4701, emulation pod, converter board
and target system.
(2) Turning On the Power
Power ON/OFF the target system and the PC4701 as simultaneously as possible.
CAUTION
Notes on Power Supply:
• The emulator's VCC pin is connected to the target system in order to monitor target
system voltage. For this reason, the emulator cannot supply power to the target
system. Therefore, provide the target system with a separate power supply from that
of the emulator.
• Keep target system power supply voltage within the MCU's specified range (4.2 to
5.5 V).
• Do not change target system power supply voltage after power has been activated.
( 46 / 76 )
(3) LED Display When PC4701 Starts Up Normally
After the emulator starts up, check the status of the LEDs on the front panel to see whether emulation
pod operation is enabled or not. Figure 4.1 shows front panel LED lighting status when the emulator
is turned ON.
• If this LED does not light, check the voltage
of the target system.
• Check that power is supplied to all the
power terminals.
• When the target system is not connected,
this LED does not light.
• When this LED lights, check the reset pin of
the target system.
Figure 4.1 LED display when the power turned on
IMPORTANT
Note on Microprocessor Mode:
• To use or microprocessor mode, be sure to set pins RDY* and HOLD* so that they
are not active at startup. Otherwise the emulator system will not function correctly.
Note on CLOCK LED:
• If CLOCK LED does not turn on, check the following:
(1) Immediately after starting PC4701 (before starting the emulator debugger)
--> Check if the oscillation circuit within the emulation pod oscillates normally.
(2) After starting up the emulator debugger (after setting the Init dialog box)
--> Check the oscillation circuit set in the Init dialog box oscillates normally.
( 47 / 76 )
4.3 Downloading Firmware
(1) When It is Necessary to Download Firmware
It is necessary to download firmware when:
(1) you use this product for the first time
(2) firmware has been upgraded
(3) emulator debugger has been upgraded
(4) you use this product with a PC4701 which was used with another emulation pod before
(2) Downloading Firmware in Maintenance Mode
Download the firmware in maintenance mode as explained here following. The target system must
not be connected when downloading the firmware.
(1) Within 2 seconds of activating power to the emulator, press the RESET switch on the emulator
front panel. This will switch the emulator to maintenance mode.
(2) 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 depends on the connection of the interface.
• For the USB interface ................. About 20 seconds
• For the LPT interface .................. About 20 seconds
• For the parallel interface ............. About 30 seconds
• For the serial interface ................ About 5 minutes
Figure 4.2 Downloading firmware in maintenance mode
IMPORTANT
Note on Downloading Firmware:
• 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.
( 48 / 76 )
4.4 Self-check
(1) Self-check Procedure
To run the emulator self-check, do so as explained here below. While the self-check is in progress,
LEDs will change as shown in Figure 4.4.
(1) Set the switches in the emulation pod same as the factory-setting (see Figure 4.3).
(2) When the target system is connected, disconnect the target system.
(3) Within 2 seconds of activating power to the emulator, press the 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 RESET switch again.
(5) The self-check will start. If the normal result is displayed in about 40 seconds, the self-check
terminated normally.
L
H
JP2
Figure 4.3 Switch settings when running the self-check (factory-settings)
(2) If an Error is Detected in the Self-check
If the self-check does not result normally (system status error or target status error shown in Figure
4.4), check the following.
• Check the connection of the emulation pod and the PC4701.
• Download the proper firmware.
• Check if the switches in this product are set same as the factory-settings (Figure 4.3).
IMPORTANT
Note on the Self-check:
• If the self-check does not result normally (excluding target system errors), the
emulation pod may be damaged. Then contact your local distributor.
( 49 / 76 )
Figure 4.4 Self-check procedure
( 50 / 76 )
Chapter 5. Specifications
This chapter describes specifications of this product.
5.1 Specifications .............................................................................................................................. 52
5.2 Operation Timing in Memory Expansion Mode and Microprocessor Mode .............................. 53
(1) Separate Bus, No-wait .......................................................................................................... 53
(2) Separate Bus, With Wait, Accessing External Memory Area .............................................. 55
(3) Multiplex Bus, With Wait, Accessing External Memory Area ............................................ 57
(4) Timing Requirements ........................................................................................................... 59
5.3 Electrical Characteristics ............................................................................................................. 61
5.4 Connection Diagram .................................................................................................................... 62
5.5 External Dimensions ................................................................................................................... 63
(1) External Dimensions of the Emulation Pod .......................................................................... 63
(2) External Dimensions of the Converter Board M3T-FLX-100LCC ...................................... 64
(3) Reference Dimensional Drawing for 100-pin 0.65-mm-pitch QFP Foot Pattern ................. 64
( 51 / 76 )
Chapter 5. Specifications
5.1 Specifications
Table 5.1 lists the specifications of the M306NAT2-RPD-E.
Table 5.1 Specifications of the M306NAT2-RPD-E
Emulator
PC4701
Applicable MCU
M16C/6N Group M306NA and M306NB
Evaluation MCU
M30622SAFP x1, M306NAMCT-TOOL x1
Usable mode
Single-chip mode
Memory expansion mode
Microprocessor mode
Emulation memory
1 MB
Maximum operating frequency
16 MHz (no-dividing)
Clock supply
XIN-XOUT
Internal oscillator circuit board (OSC-3)
Switchable to external oscillator input
XCIN-XCOUT
Internal oscillator circuit board
Switchable to external oscillator input
Operating voltage
4.2 to 5.5 V
Operating temperature
5 to 35°C (no dew)
Storage temperature
-10 to 60°C (no dew)
Power supply to emulation pod
Supplied from PC4701
• 100-pin 0.65-mm-pitch QFP (100P6S-A):
Connection to target system
See "3.6 Connecting the Target (1) M3T-FLX-100LCC (included)
+ M3T-DUMMY100S (separately available)
System" (page 40).
(2) M3T-FLX-100LCC (included)
+ M3T-DIRECT100S (separately available)
(3) M3T-FLX-100NRB (separately available)
• 100-pin LCC socket:
M3T-FLX-100LCC (included)
Overseas standards
• U.S. EMI standards (FCC part 15 Class A)
• CE marking (EN55022, EN55024)
( 52 / 76 )
5.2 Operation Timing in Memory Expansion Mode and Microprocessor Mode
(1) Separate Bus, No-Wait
Table 5.2 and Figure 5.1 show the bus timing in memory expansion mode and the microprocessor
mode (separate bus, no-wait).
Table 5.2 Memory expansion mode and microprocessor mode (separate bus, no-wait)
Symbol
Item
Actual MCU This product
(ns)
(ns)
Min.
Max.
Min.
Td (BCLK-AD)
Address output delay time
Th (BCLK-AD)
Address output hold time (BCLK standard)
4
See left
Th (RD-AD)
Address output hold time (RD standard)
0
See left
Th (WR-AD)
Address output hold time (WR standard)
0
See left
Td (BCLK-CS)
Chip-select output delay time
Th (BCLK-CS)
Chip-select output hold time (BCLK standard)
25
Td (BCLK-ALE) ALE signal output delay time
Th (BCLK-ALE) ALE signal output hold time
See left
25
4
See left
See left
25
-4
See left
See left
Td (BCLK-RD)
RD signal output delay time
Th (BCLK-RD)
RD signal output hold time
Td (BCLK-WR)
WR signal output delay time
Th (BCLK-WR)
WR signal output hold time
Td (BCLK-DB)
Data output delay time (BCLK standard)
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)
0
See left
25
0
Td (DB-WR) =
109
f(BCLK)x2
-40 (ns)
( 53 / 76 )
See left
See left
25
0
See left
See left
40
*1 Calculated by the following formula according to the frequency of BCLK.
Max.
See left
Memory expansion mode and microprocessor mode (no-wait)
Read timing
BCLK
CSi
ADi
BHE
ALE
RD
DB
Write timing
BCLK
CSi
ADi
BHE
ALE
WR, WRL,
WRH
DB
Conditions:
• VCC = 5 V
• Input timing voltage: VIL = 0.8 V, VIH = 2.5 V
• Output timing voltage: VOL = 0.8 V, VOH = 2.0 V
Figure 5.1 Memory expansion mode and microprocessor mode (no-wait)
( 54 / 76 )
(2) Separate Bus, With Wait, Accessing External Memory Area
Table 5.3 and Figure 5.2 show the bus timing in memory expansion mode and microprocessor mode
(with wait, accessing external memory area).
Table 5.3 Memory expansion mode and microprocessor mode (with wait, external memory area)
Symbol
Item
Actual MCU This product
(ns)
(ns)
Min.
Max.
Min.
Td (BCLK-AD)
Address output delay time
Th (BCLK-AD)
Address output hold time (BCLK standard)
4
See left
Th (RD-AD)
Address output hold time (RD standard)
0
See left
Th (WR-AD)
Address output hold time (WR standard)
0
See left
Td (BCLK-CS)
Chip-select output delay time
Th (BCLK-CS)
Chip-select output hold time (BCLK standard)
25
Td (BCLK-ALE) ALE signal output delay time
Th (BCLK-ALE) ALE signal output hold time
See left
25
4
See left
See left
25
-4
See left
See left
Td (BCLK-RD)
RD signal output delay time
Th (BCLK-RD)
RD signal output hold time
Td (BCLK-WR)
WR signal output delay time
Th (BCLK-WR)
WR signal output hold time
Td (BCLK-DB)
Data output delay time (BCLK standard)
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)
0
See left
25
0
Td (DB-WR) =
109
f(BCLK)
-40 (ns)
( 55 / 76 )
See left
See left
25
0
See left
See left
40
*1 Calculated by the following formula according to the frequency of BCLK.
Max.
See left
Memory expansion mode and microprocessor mode (with wait, accessing external memory area)
Read timing
BCLK
CSi
ADi
BHE
ALE
RD
DB
Write timing
BCLK
CSi
ADi
BHE
ALE
WR, WRL,
WRH
DBi
Conditions:
• VCC = 5 V
• Input timing voltage: VIL = 0.8 V, VIH = 2.5 V
• Output timing voltage: VOL = 0.8 V, VOH = 2.0 V
Figure 5.2 Memory expansion mode and microprocessor mode (with wait)
( 56 / 76 )
(3) Multiplex Bus, With Wait, Accessing External Memory Area
Table 5.4 and Figure 5.3 show the bus timing in memory expansion mode and microprocessor mode
(with wait, accessing external memory area and using multiplex bus).
Table 5.4 Memory expansion mode and microprocessor mode (with wait, multiplex bus)
Symbol
Actual MCU This product
(ns)
(ns)
Item
Min.
Td (BCLK-AD)
Address output delay time
Th (BCLK-AD)
Address output hold time (BCLK standard)
Th (RD-AD)
Max.
Min.
25
See left
4
See left
Address output hold time (RD standard)
(*1)
(*2)
Th (WR-AD)
Address output hold time (WR standard)
(*1)
(*2)
Td (BCLK-CS)
Chip-select output delay time
Th (BCLK-CS)
Chip-select output hold time (BCLK standard)
Th (RD-CS)
25
See left
4
See left
Chip-select output hold time (RD standard)
(*1)
(*2)
Th (WR-CS)
Chip-select output hold time (WR standard)
(*1)
(*2)
Td (BCLK-RD)
RD signal output delay time
Th (BCLK-RD)
RD signal output hold time
Td (BCLK-WR)
WR signal output delay time
Th (BCLK-WR)
WR signal output hold time
Td (BCLK-DB)
Data output delay time (BCLK standard)
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)
(*1)
(*2)
25
0
See left
See left
25
0
Th (BCLK-ALE) ALE output hold time (BCLK standard)
See left
See left
40
Td (BCLK-ALE) ALE output delay time (BCLK standard)
Max.
See left
25
See left
-4
See left
Td (AD-ALE)
ALE output delay time (Address standard)
(*1)
See left
Th (ALE-AD)
ALE output hold time (Address standard)
50
See left
Td (AD-RD)
After address RD signal output delay time
0
See left
Td (AD-WR)
After address WR signal output delay time
0
See left
Tdz (RD-AD)
Address output floating start time
8
See left
*1 Calculated by the following formulas accord- *2 Calculated by the following formulas according to the frequency of BCLK.
ing to the frequency of BCLK.
Th (RD-AD) =
Th (WR-AD) =
Th (RD-CS) =
Th (WR-CS) =
Td (DB-WR) =
Th (WR-DB) =
Td (AD-ALE) =
109
f(BCLK)x2
109
f(BCLK)x2
109
f(BCLK)x2
109
f(BCLK)x2
109x3
f(BCLK)x2
109
f(BCLK)x2
109
f(BCLK)x2
(ns)
Th (RD-AD) =
(ns)
Th (WR-AD) =
(ns)
Th (RD-CS) =
(ns)
Th (WR-CS) =
109
f(BCLK)x2
109
f(BCLK)x2
109
f(BCLK)x2
109
f(BCLK)x2
-6 (ns)
-6 (ns)
-3 (ns)
-3 (ns)
-40 (ns)
(ns)
-25 (ns)
( 57 / 76 )
Th (RD-AD) =
109
f(BCLK)x2
-6 (ns)
Memory expansion mode and microprocessor mode
(with wait, accessing external memory area and using multiplex bus)
Read timing
BCLK
CSi
ADi
DBi
ADi
BHI
ALE
RD
Write timing
BCLK
CSi
ADi
DBi
ADi
BHI
ALE
WR, WRL,
WRH
Conditions:
• VCC = 5 V
• Input timing voltage: VIL = 0.8 V, VIH = 2.5 V
• Output timing voltage: VOL = 0.8 V, VOH = 2.0 V
Figure 5.3 Memory expansion mode and microprocessor mode (with wait, multiplex bus)
( 58 / 76 )
(4) Timing Requirements
Table 5.5, Figures 5.4 and 5.5 show timing requirements in memory expansion mode and the
microprocessor mode.
Table 5.5 Timing requirements
Symbol
Actual MCU This product
(ns)
(ns)
Item
Min.
Tsu (DB-RD)
Data input setup time
Max.
Min.
40
See left
Tsu (RDY-BCLK) RDY* input setup time
30
See left
Tsu (HOLD-BCLK) HOLD* input setup time
40
(*1)
Th (RD-DB)
0
See left
Th (BCLK-RDY) RDY* input hold time
0
See left
Th (BCLK-HOLD) HOLD* input hold time
0
See left
Data input hold time
Td (BCLK-HLDA) HLDA* output delay time
40
Max.
See left
*1 Minimum 7 ns (The definition is different from that of actual MCUs. For details, see Figure 5.5.)
Memory expansion mode and microprocessor mode (only for "with wait")
BCLK
RD
(separate bus)
WR, WRL, WRH
(separate bus)
RD
(multiplex bus)
WR, WRL, WRH
(multiplex bus)
RDY input
Conditions:
• VCC = 5 V
• Input timing voltage: VIL = 1.0 V, VIH = 4.0 V
• Output timing voltage: VOL = 2.5 V, VOH = 2.5 V
Figure 5.4 Timing requirements
( 59 / 76 )
Common to "with wait" and "no-wait" (actual MCU)
BCLK
HOLD input
HLDA output
P0, P1, P2,
P3, P4,
P50--P52
Common to "with wait" and "no-wait" (This product)
BCLK
HOLD input
HLDA output
P0, P1, P2,
P3, P4,
P50--P52
Note 1. P00 through P52 will be high-impedance status regardless of the input level of pin
BYTE and ports P40 through P43 function selection bit (PM06) of the processor mode
register 0.
Note 2. This product will be high-impedance delaying by 2.5 cycles than an actual MCU.
Note 3. The setup time of HOLD is defined by the startup of BCLK, differently from that of
actual MCUs.
Conditions:
• VCC = 5 V
• Input timing voltage: VIL = 1.0 V, VIH = 4.0 V
• Output timing voltage: VOL = 2.5 V, VOH = 2.5 V
Figure 5.5 Timing requirements
( 60 / 76 )
5.3 Electrical Characteristics
Tables 5.6 and 5.7 list IC electrical characteristics of the user interface.
Table 5.6 Electrical characteristics of the 74HC4066AFT
(P100--P107, AN0--AN7, AN00--AN07, AN20--AN27)
Symbol
Standard values
Parameter
VCC
Min.
3.15
Standard
VIHC
High level control input voltage
4.5
VILC
Low level control input voltage
4.5
RON
ON resistance
4.5
96
RON
Difference of ON resistances
4.5
10
Max.
Unit
V
1.35
V
200
Ω
Ω
Table 5.7 Electrical characteristics of the M60081L-0142FP (P00--P57)
Symbol
Standard values
Parameter
Condition
VIL
Min.
Standard
Max.
VCC = 4.5 V
0
1.35
VCC = 5.5 V
3.85
5.5
VCC = 5.0 V
|IO| < 1 µA
4.95
V
VCC = 4.5 V
VOL = 0.4 V
8
mA
V
Input voltage
VIH
VOH
VOL
Output voltage
IOL
Output current
IOH
VCC = 4.5 V
VOH =4.1 V
IIL
VCC = 5.5 V
VI = 0 V
IIH
IOZL
Input leak current
OFF state output leak current
IOZH
CIO
Unit
( 61 / 76 )
V
-8
mA
-1
+1
µA
VCC = 5.5 V
VI = 5.5 V
-1
+1
µA
VCC = 5.5 V
VO = 0 V
-1
+1
µA
VCC = 5.5 V
VO = 5.5 V
-1
+1
µA
15
pF
f = 1 MHz
VCC = 0 V
I/O pin capacity
0.05
7
5.4 Connection Diagram
Figure 5.6 shows the connection diagram of the M306NAT2-RPD-E. This connection diagram
mainly shows the interface section, and the circuits which are not connected to the target system such
as the emulator's control system are omitted.
Figure 5.6 Connection diagram
( 62 / 76 )
5.5 External Dimensions
(1) External Dimensions of the Emulation Pod
Unit: mm
Figure 5.7 External dimensions of the emulation pod
( 63 / 76 )
(2) External Dimensions of the Converter Board M3T-FLX-100LCC
Figure 5.8 shows external dimensions of the converter board M3T-FLX-100LCC for 100-pin LQFP
(100D0).
Unit: mm
Figure 5.8 External Dimensions of the Converter Board M3T-FLX-100LCC
(3) Reference Dimensional Drawing for 100-pin 0.65-mm-pitch QFP Foot Pattern
Figure 5.9 shows an sample foot pattern for Renesas 100P6S-A, the socket IC61-1004-051 (made by
Yamaichi Electronics Co., Ltd.) for LCC, the IC socket AXS4003M291 (made by Matsushita Electric
Works, Ltd.) for dummy IC and pitch converter board M3T-FLX-100NRB (NQPACK100RB).
0.65x29=18.85
4-R0.25
0.65
24.5
16.1
0.65
12.8
13.8
21.4
0.65x19=12.35
0.35
19.2
19.8
19.9
26.1
27.6
Unit: mm
Figure 5.9 Reference dimensional drawing for a 100-pin 0.65-mm-pitch QFP foot pattern
( 64 / 76 )
Chapter 6. Troubleshooting
This chapter describes how to troubleshoot when this product does not work properly.
6.1 Flowchart to Remedy the Troubles ............................................................................................. 66
6.2 When the Emulator Debugger Does Not Start Up Properly ........................................................ 67
(1) When LED Display of the PC4701 is Abnormal .................................................................. 67
(2) Program Window Does Not Appear at Debugger Startup (target connected) ...................... 68
(3) Program Window Does Not Appear at Debugger Startup (target not connected)................ 69
(4) Errors Occur at Debugger Startup (target connected) .......................................................... 69
6.3 Operation Differs from That of Actual MCUs ............................................................................ 70
(1) Cannot Reset from the Target System .................................................................................. 70
(2) Data Values of ROM Area at Power-on Are Different ........................................................ 70
(3) HOLD* Control .................................................................................................................... 70
(4) A-D Conversion Values are Different from Expected Values ............................................. 70
(5) Outputs of ALE, Address and Others are Different from Those of Actual MCUs .............. 70
( 65 / 76 )
Chapter 6. Troubleshooting
6.1 Flowchart to Remedy the Troubles
Figure 6.1 shows the flowchart to remedy the troubles from when power to the emulator is activated
until the emulator debugger starts up. Check this while the target system is disconnected.
FAQs visit the following URL.
http://www.renesas.com/en/tools
Turning on the power of PC4701
Front panel LEDs
of PC4701
Not normal
1. Check emulator system connections.
See, "3.5 Connecting the PC4701" (page 38).
2. Redownload the firmware.
See "4.3 Downloading Firmware" (page 48).
3. Restart the PC4701 system.
Init dialog box of emulator
debugger displayed
Not normal/Error displayed
1. Check the operating environment etc. of the emulator
debugger.
See the user's manual of the emulator debugger.
2. Reinstall the emulator debugger.
Error displayed
See "6.2 (2) Program Window Does Not Appear at Debugger
Startup (target connected) (page 68).
See "6.2 (3) Program Window Does Not Appear at Debugger
Startup (target not connected) (page 69).
See "6.2 (4) Errors Occur at Debugger Startup (target connected)
(page 69).
Program window of emulator debugger displayed
Figure 6.1 Flowchart to remedy the troubles
( 66 / 76 )
6.2 When the Emulator Debugger Does Not Start Up Properly
(1) When LED Display of the PC4701 is Abnormal
Table 6.1 LED's abnormal display and its checkpoints
Error
LEDs do not light up.
Connection to
the target system
-
Checkpoint
Recheck that the power cable is connected to the
PC4701.
See the instruction manual of the PC4701.
All LEDs remain lit.
POWER LED of
STATUS OF TARGET
does not light up.
-
Connected
Recheck that the connection between the PC4701
and this product.
See "3.5 Connecting the PC4701" (page 38).
Check that power is properly supplied to the target
system and that the target system is properly
grounded.
(1) Check that both the main and sub clocks of the
emulator debugger are not set to "EXT".
Disconnected
See the CLK command of the emulator
debugger.
(2) Check that the oscillation circuit in the emulation
pod is oscillating.
CLOCK LED of STATUS
OF TARGET does not
light up.
See "3.3 Selecting Clock Supply" (page 33).
Connected
(1) Check that the oscillation circuit in the target
system is oscillating.
(2) Check that the switches in the emulation pod
are correctly set.
See "3.2 Setting Switches and Pullup Resistors"
(page 29).
RESET LED of STATUS
OF TARGET does not
turn off.
Connected
( 67 / 76 )
Check that the reset pin of the target system is
pulled "High".
(2) Program Window Does Not Appear at Debugger Startup (target connected)
Table 6.2 Checkpoints of errors when starting up the emulator debugger (target connected)
Error
Checkpoint
Check that all emulator debugger settings, interface cable
connection and switches on the rear of the PC4701 match.
Communication error occurred
Data was not sent to the target
See the user's manuals of the PC4701 and the emulator
debugger.
(1) Download the proper firmware.
See "4.3 Downloading Firmware" (page 48).
Target system cannot be properly built
(2) Recheck that the connection between the PC4701
and this product.
See "3.5 Connecting the PC4701" (page 38).
M3T-PD30 version is not the same version Download the proper firmware.
See "4.3 Downloading Firmware" (page 48).
as the firmware in the target
Target MCU is in the reset state
Check the reset pin of the target system has changed
from "Low" to "High" level.
Target MCU cannot be reset
(1) Check that pins RESET* and NMI* are held "High".
(2) If in memory expansion mode or microprocessor
mode, check that pins RDY* and HOLD* are held
"High".
(3) If the reset circuit of the target system has a watchdog
timer, disable the timer.
(4) Check that power is properly supplied to the target
system and that the target system is properly
grounded.
(5) The program may be uncontrollable in areas where
memory is not allocated. Recheck the map setting.
See the user's manual of the emulator debugger.
(1) The MCU is either in stop mode or wait mode. Either
reset the MCU or cancel the mode with an interrupt.
See the MCU specifications.
Target is in HOLD state
(2) The program may be uncontrollable in areas where
memory is not allocated. Recheck the map setting.
See the user's manual of the emulator debugger.
(1) Check that the oscillation circuit of the target system
is oscillating properly.
(2) Check that the switches in the emulation pod are
correctly set.
Target clock is stopped
See "3.2 Setting Switches and Pullup Resistors"
(page 29).
Target MCU is not receiving power
( 68 / 76 )
Check that power is properly supplied to the target
system and the target system is properly grounded.
(3) Program Window Does Not Appear at Debugger Startup (target not connected)
Table 6.3 Checkpoints of errors when starting up the emulator debugger (target not connected)
Error
Checkpoint
Check that all emulator debugger settings, interface cable
connection and switches on the rear of the PC4701 match.
Communication error occurred
Data was not sent to the target
See the user's manuals of the PC4701 and the emulator
debugger.
(1) Download the proper firmware.
See "4.3 Downloading Firmware" (page 48).
Target system cannot be properly built
(2) Recheck the connection between the PC4701 and
this product.
See "3.5 Connecting the PC4701" (page 38).
M3T-PD30 version is not the same version Download the proper firmware.
See "4.3 Downloading Firmware" (page 48).
as the firmware in the target
The program may be uncontrollable in areas where
memory is not allocated. Recheck the map setting.
Target MCU cannot be reset
See the user's manual of the emulator debugger.
(1) The MCU is either in stop mode or wait mode. Either
reset the MCU or cancel the mode with an interrupt.
See the MCU specifications.
Target is in HOLD state
(2) The program may be uncontrollable in areas where
memory not allocated. Recheck the map setting.
See the user's manual of the emulator debugger.
Check that the switches in the emulation pod are correctly
set.
Target clock is stopped
See "3.2 Setting Switches and Pullup Resistors" (page 29).
(4) Errors Occur at Debugger Startup (target connected)
Table 6.4 Checkpoints of errors when starting up the emulator debugger (target connected)
Error
Checkpoint
(1) If in memory expansion mode or microprocessor
mode, check pins RDY* and HOLD* are held "High".
(2) The program may be uncontrollable in areas where
memory is not allocated. Recheck the map setting.
Target MCU is uncontrollable.
See the user's manual of the emulator debugger.
( 69 / 76 )
6.3 Operation Differs from That of Actual MCUs
(1) Cannot Reset from the Target System
Set the rise time (0.2 Vcc to 0.8 Vcc) 1 µs or less.
(2) Data Values of ROM Area at Power-on Are Different
For this product, 04h is written into the ROM area at power-on. Therefore, the data values are different
from those of an actual MCU.
(3) HOLD* Control
When inputting "Low" to pin HOLD* to run into the HOLD state, P00 to P52 will be in the HOLD
state delaying by 2.5 cycles than an actual MCU (see Figure 5.5 and Table 5.5).
(4) A-D Conversion Values are Different from Expected Values
As a flexible cable, a pitch converter board and other devices are used between the evaluation MCU
and the target system, some characteristics are slightly different from those of the actual MCU.
Therefore, be sure to evaluate your system with an actual MCU.
(5) Outputs of ALE, Address and Others are Different from Those of Actual MCUs
This product has some output signals which are different from those of actual MCU as following.
• ALE signal output in accessing the SFR area
• Address, BHE* and ALE signal outputs in accessing the internal RAM and ROM
• State of the data bus in stop mode and wait mode
For details, see Chapter 1 "Note on Differences between Actual MCU and Emulator" (pages 17 to 19).
( 70 / 76 )
Chapter 7. Maintenance and Guarantee
This chapter describes how to maintenance, repair provisions and how to request for repair.
7.1 Maintenance................................................................................................................................. 72
7.2 Guarantee ..................................................................................................................................... 72
7.3 Repair Provisions ......................................................................................................................... 72
7.4 How to Request for Repair .......................................................................................................... 73
( 71 / 76 )
Chapter 7. Maintenance and Guarantee
7.1 Maintenance
If dust or dirt collects on any equipment of your emulation system, wipe it off with a dry soft cloth.
Do not use thinner or other solvents because these chemicals can cause the equipment's surface
coating to separate.
7.2 Guarantee
If your product becomes faulty within one year after its purchase while being used under good
conditions by observing "Precautions for Safety" described in Chapter 1 of this user's manual, we will
repair or replace your faulty product free of charge. Note, however, that if your product's fault is raised
by any one of the following causes, we will repair it or replace it with new one with extra-charge:
• Misuse, abuse, or use under extraordinary conditions
• Unauthorized repair, remodeling, maintenance, and so on
• Inadequate user's system or misuse of it
• Fires, earthquakes, and other unexpected disasters
In the above cases, contact your local distributor. If your product is being leased, consult the leasing
company or the owner.
7.3 Repair Provisions
(1) Repair with extra-charge
The products elapsed more than one year after purchase can be repaired with extra-charge.
(2) Replacement with extra-charge
If your product's fault falls in any of the following categories, the fault will be corrected by
replacing the entire product instead of repair, or you will be advised to purchase new one,
depending on the severity of the fault.
• Faulty or broken mechanical portions
• Flaw, separation, or rust in coated or plated portions
• Flaw or cracks in plastic portions
• Faults or breakage caused by improper use or unauthorized repair or modification
• Heavily damaged electric circuits due to overvoltage, overcurrent or shorting of power supply
• Cracks in the printed circuit board or burnt-down patterns
• Wide range of faults that makes replacement less expensive than repair
• Unlocatable or unidentified faults
(3) Expiration of the repair period
When a period of one year elapses after the model was dropped from production, repairing
products of the model may become impossible.
(4) Transportation fees at sending your product for repair
Please send your product to us for repair at your expense.
( 72 / 76 )
7.4 How to Request for Repair
If your product is found faulty, follow the procedure below to send your product for repair.
Customer
Fill in the Repair Request Sheet included with this product, then send it
along with this product for repair to your local distributor. Make sure
that information in the Repair Request Sheet is written in as much detail
as possible to facilitate repair.
Distributor
After checking the contents of fault, the distributor should please send
the faulty product along with the Repair Request Sheet to Renesas
Solutions Corp.
Renesas Solutions
When the faulty product is repaired, it will be returned to the customer
at the earliest convenience.
CAUTION
Note on Transporting the Product:
• When sending your product for repair, use the packing box and cushion material supplied with this
product when delivered to you and specify handling caution for it to be handled as precision
equipment. If packing of your product is not complete, it may be damaged during transportation.
When you pack your product in a bag, make sure to use conductive polyvinyl supplied with this
product (usually a blue bag). When you use other bags, they may cause a trouble on your product
because of static electricity.
( 73 / 76 )
MEMO
( 74 / 76 )
M306NAT2-RPD-E User's Manual
Rev.2.00
July 1, 2004
REJ10J0202-0200Z
COPYRIGHT ©2003-2004 RENESAS TECHNOLOGY CORPORATION
AND RENESAS SOLUTIONS CORPORATION ALL RIGHTS RESERVED
M306NAT2-RPD-E
User’s Manual
1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa 211-8668 Japan
REJ10J0202-0200Z
Download PDF