Renesas M306H2T-RPD-E User Manual
M306H2T-RPD-E
Emulation Pod for M16C/6H Group M306H2
User's Manual
Rev.1.00
September 1, 2003
REJ10J0259-0100Z
* NQPACK, YAPACK, YQSOCKET, YQ-Guide, HQPACK, TQPACK, and TQSOCKET are trademarks of Tokyo Eletech Corporation.
• 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.
• 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.
Keep safety first in your circuit designs!
Notes regarding these materials
• 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.
• Do not attempt to modify this equipment. If modified, your authority to operate this equipment might be voided by FCC.
Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules.
These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely
to cause harmful interference in which case the user will be required to correct the interference at his own expense.
Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
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
Precautions to be taken when using this product
( 2 / 76 )
Preface
The M306H2T-RPD-E is an emulation pod for M306H2 of M16C/6H Group of 16-bit MCUs. It is
used with a PC4701 emulator.
This user's manual mainly describes specifications of the M306H2T-RPD-E emulation pod and how
to setup it. For details on the following products, which are used with M306H2T-RPD-E, refer to each
product's user's manual.
• Emulator: PC4701 User's Manual
• Emulator debugger: Emulator debugger for PC4701 series User's Manual
All the components of this product are shown in "2.2 Package Components" (page 23) 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 overseas standards. EMI standards are not met
when the M306H2T-RPD-E is used with the PC4700H or PC4700L emulator.
( 3 / 76 )
Contents
Chapter 1. Precautions for Safety ...........................................................................................7
1.1 Safety Symbols and Meanings ..............................................................................9
Chapter 2. Preparation ..........................................................................................................21
2.1 Terminology ........................................................................................................22
2.2 Package Components ..........................................................................................23
2.3 Other Tool Products Required for Development ................................................23
2.4 Name of Each Part ..............................................................................................24
(1) System Configuration...............................................................................24
(2) Inside of the Emulation Pod .....................................................................25
2.5 When Using the Emulator for the First Time......................................................26
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 .......................................................................................35
(1) Using the Oscillator Circuit on the Target System ..................................36
(2) Changing the Internal Oscillator Circuit of the Emulation Pod ...............37
(3) Replacing the Oscillator Circuit Boards ..................................................38
3.4 A-D Conversion Bypass Capacitor .....................................................................39
3.5 Data Slicer I/O Signal and FSC Clock I/O Signal Circuit ..................................40
3.6 Connecting the PC4701.......................................................................................41
(1) Connecting the Cable to the PC4701 .......................................................41
(2) Connecting the Cable to the Emulation Pod ............................................42
3.7 Connecting the Target System ............................................................................43
3.8 Making an MCU File for PD30 ..........................................................................44
Chapter 4. Usage ..................................................................................................................45
4.1 Turning On the Power .........................................................................................46
(1) Checking the Connection of the Emulator System ..................................46
(2) Turning On the Power ..............................................................................46
(3) LED Display When PC4701 Starts Up Normally....................................47
4.2 Downloading Firmware ......................................................................................48
(1) When It is Necessary to Download Firmware .........................................48
(2) Downloading Firmware in the Maintenance Mode .................................48
4.3 Self-checks ..........................................................................................................49
(1) Self-check Procedure ...............................................................................49
(2) If an Error is Detected in Self-checks ......................................................49
( 4 / 76 )
Chapter 5. Specifications......................................................................................................51
5.1 Specifications ......................................................................................................52
5.2 Operation Timing in the Memory Expansion and Microprocessor Modes (5 V) ...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 Pitch Converter Board (FLX160-PRB).......64
(3) External Dimensions of the Pitch Converter Board (M306H2T-PTC)....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 the LED Display of the PC4701 is Abnormal ...............................67
(2) Errors Occur When the Emulator Debugger Starts Up
(When the target system is connected)....................................68
(3) Errors Occur When the Emulator Debugger Starts Up
(When the target system is not connected) .............................69
6.3 Operation Differs from That of Actual MCUs....................................................70
(1) Cannot Reset from the Target System......................................................70
(2) Data Values of RAM 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 )
MEMO
( 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 .....................................................................................................9
WARNING
CAUTION
IMPORTANT
Warning for Installation.............................................................................................10
Warnings for Use Environment ................................................................................. 10
Caution to Be Taken for Modifying This Product ..................................................... 10
Cautions to Be Taken for Handling This Product...................................................... 10
Note on Malfunctions in the PC4701 System............................................................10
Notes on Downloading Firmware..............................................................................11
Note on When the Emulator Debugger Ends............................................................. 11
Note on Final Evaluation ........................................................................................... 11
Notes on Target System ............................................................................................. 11
Notes on Stack Area...................................................................................................11
Notes on MAP References and Settings ....................................................................12
Note on Setting the Work Area.................................................................................. 12
Note on RESET* Input ..............................................................................................13
Note on HOLD* Input ............................................................................................... 13
Note on RDY* Input..................................................................................................13
Notes on NMI* Input ................................................................................................. 13
Note on Clock Supply to the MCU............................................................................13
Notes on Interruption .................................................................................................14
Note on Address 00000h Access ...............................................................................14
Note on Stop and Wait Modes ................................................................................... 14
Note on Software Reset ............................................................................................. 14
Note on BRK Instruction and BRK Instruction Interruption.....................................14
Notes on Address Match Interrupt.............................................................................14
Note on Commands that Access the Single-step Interrupt Vector Area.................... 15
Note on DMA Transfer..............................................................................................15
Notes on Software Breaks and Hardware Breaks ...................................................... 15
Note on Protect Resistor (PRC2) ...............................................................................15
( 7 / 76 )
Notes on Pullup Control Resistor .............................................................................. 16
Note on Reading Internal Resources of an MCU ......................................................16
Notes on Watchdog Function.....................................................................................16
Note on Differences between Actual MCUs and the Emulator .................................17
( 8 / 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
If the requirements shown in the "WARNING"
WARNING
CAUTION
IMPORTANT
In addition to the three above, the following are also used as appropriate.
sentences are ignored, the equipment may
cause serious personal injury or death.
If the requirements shown in the "CAUTION"
sentences are ignored, the equipment may
malfunction.
It means important information on using this
product.
means WARNING or CAUTION.
Example: CAUTION AGAINST AN ELECTRIC SHOCK
means PROHIBITION.
Example: DISASSEMBLY PROHIBITED
means A FORCIBLE ACTION.
Example:
The following pages describe the symbols "WARNING", "CAUTION", and "IMPORTANT".
UNPLUG THE POWER CABLE FROM THE RECEPTACLE.
( 9 / 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 or FLX160) 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 or FLX160) 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.
( 10 / 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 the maintenance mode. For firmware download procedures, see
"4.2 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 self-checks are not completed successfully, there may
be trouble with the product. In such case, contact your sales representative. However, perform selfchecks 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 evaluation 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 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.
•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.
For details, refer to "Chapter 4. Usage" (page 45).
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.
( 11 / 76 )
IMPORTANT
Notes on MAP References and Settings:
• For details on referencing and setting MAP information, see user's manual of the emulator
debugger.
• Be sure to set the SFR area to EXTERNAL (an external section).
•When setting 0FFFCh - 0FFFFh to EXTERNAL:
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 conditions given below is met.
(1) With the system which shifts from the single-chip mode to the memory expansion (or
microprocessor) mode, using the 4 bytes area of 0FFFCh - 0FFFFh set to EXTERNAL.
(2) With the system which starts up in the microprocessor mode, using the 4 bytes area of 0FFFCh
- 0FFFFh set to EXTERNAL and there is not enough memory to read or write to.
The procedures to alter the MAP settings when the condition (1) or (2) above is met are shown
below.
(1) Set the 4 bytes area of 0FFFCh - 0FFFFh to INTERNAL.
(2) Execute the RESET command of the emulator debugger.
(3) Set the stack pointer.
(Example)
RESET:
FCLR I
○○
LDC #0480H, SP --> Set the stack pointer.
(4) Set the 4 bytes area 0FFFCh - 0FFFFh to EXTERNAL.
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 INTERNAL. (Set the work area by Init dialog of the emulator debugger.)
Example 1: When debugging the program of the MCU whose internal reserved area is 02C00h -
03FFFh, set the work area within the range of 02C00h - 03FF6h.
Example 2: When debugging the program of the MCU whose internal reserved area is 05400h -
05FFFh, set the work area within the range of 05400h - 05FF6h.
For instance, when setting the work area at 05C00h, the emulator uses 10 bytes area of 05C00h -
05C09h.
(Stop the program after executing this instruction.)
( 12 / 76 )
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).
Note on HOLD* Input:
• Be sure to input "L" to the HOLD* pin of the target system during the user program execution (while
the RUN status LED on the PC4701's front panel is lit). Inputting "L" to the HOLD* pin when
stopping the user program may cause a malfunction of the emulator.
Note on RDY* Input:
• Be sure to input "L" to the RDY* pin of the target system during the user program execution (while
the RUN status LED on the PC4701's front panel is lit). Inputting "L" to the RDY* pin when
stopping the user program may cause a malfunction of the emulator.
Notes on NMI* Input:
IMPORTANT
• 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).
•NMI* interrupts are generated in the following situations.
(1) Immediately after the NMI* pin changes from "H" to "L" level during the target program
execution
(2) After a reset is released by the target system when the NMI* pin is "L" level during the target
program execution
(3) Immediately after program execution starts with the NMI* pin "L" level, following the reset
input from the emulator debugger or emulator main unit
(4) Immediately after program execution starts when the NMI* pin is "H" level immediately
before the target program stops and changes to "L" level when target program execution starts
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.
( 13 / 76 )
IMPORTANT
Notes on Interruption:
• 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.
Note on Address 00000h Access:
•With the M16C/6H 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.
Note on BRK Instruction and BRK Instruction Interruption:
• With this emulator system, BRK instructions and BRK instruction interruptions 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.
• 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 will run out of control.
•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.
( 14 / 76 )
IMPORTANT
Note on Commands that Access the Single-step Interrupt Vector Area:
• Do not perform the following debugging operations with the single step interrupt vector area
(addresses FFFECh - FFFEFh).
(1) Step execution of instructions that access the single step interrupt vector area
(2) Program execution using instructions that access the single step interrupt vector area when a
software breakpoint is set in those instructions
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 following 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
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 EXTERNAL, software breaks cannot be used.
Note on Protect Resistor (PRC2):
•Make note of the fact that the protect is not canceled when protect register (PRC2), which enables
writing in the port P9 direction registers and the SI/O3, SI/O4 control registers, is changed with the
following procedure.
(1) Step execution of the instruction for setting ("1") PRC2
(2) Setting the break point from the instruction for setting ("1") PRC2 to when the setting the
register for the protect"
(3) Setting ("1") PRC2 from the dump window or script window
( 15 / 76 )
IMPORTANT
Notes on Pullup Control Resistor:
• Ports P00 to P57 are not pulled up by the pullup control resistor.
When pulling up the 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 resistors.
Note: The pullup control resistors can read and write from P00 to P107 properly.
• When the pullup control resistor 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 resistor 0 (bit
3 of address 3FCh = PU03) of Ports P14 - P17.
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 Resisters and symbols not displayed normally
Resister Symbol
DMA source pointers 0, 1 SAR0, SAR1
DMA destination pointers 0, 1 DAR0, DAR1
DMA transfer counters 0, 1 TCR0, TCR1
DMA control resisters 0, 1 DM0CON, DM1CON
Notes on Watchdog Function:
• The MCU's watchdog timer can be used only while a program is 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.
( 16 / 76 )
IMPORTANT
Note on Differences between Actual MCUs and the 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) Initial values of MCU's internal resources
(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 36).
(5) Characteristics of ports P00 to P57
With this product, ports P00 to P57 are connected via an emulation circuit. The device used
for the port emulation circuit is as follows.
Device: M60081L-0142FP
(6) HOLD* control
When inputting "L" 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).
(7) DBC, Single-step and BRK instruction interrupt vector table addresses
You can download data to the DBC, Single-step and BRK instruction interrupt vector table
addresses. However, the data read out from this area is different from expected values, because
the emulator system uses this area (see Table 1.2).
Table 1.2 Vector table addresses for the emulator
Factor of interruption Vector table addresses Data for reading
1
DBC*
Single-step*
BRK instruction FFFE4h
1
FFFF4h - FFFF7h Indefinite
FFFECh - FFFEFh Indefinite
- FFFE7h Indefinite
*1 Interruption for the debugger only
(8) 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.
(9) D-A conversion
As a 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) Outputs of the actual MCU and this product
Outputs of this product are determined according to the user program as listed in Tables 1.3
to 1.6.
( 17 / 76 )
IMPORTANT
Table 1.3 Differences of outputs between actual MCUs and this product (when executing program)
Access area Signal
Address
BHE*
Data
SFR area
(MAP = EXT)
Internal RAM
Internal ROM
External area
RD*
WR*
CS*
ALE
Address
BHE*
Data
RD*
WR*
CS*
ALE
Address
BHE*
Data
RD*
WR*
CS*
ALE
Actual MCU
Outputs
Outputs
(floating during read cycle)
Outputs
("L" output at write cycle,
"L" output at read cycle)
Does not output
(fixed to "H" output)
Does not output
(fixed to "L" output)
Retains previous status
Floating
Does not output
(fixed to "H" output)
Does not output
(fixed to "H" output)
Does not output
(fixed to "L" output)
Outputs
Outputs
(inputs external data at read cycle)
Outputs
("L" output at write cycle,
"L" output at read cycle)
Outputs
Outputs
This product
Outputs
Floating
Does not output
(fixed to "H" output)
Does not output
(fixed to "H" output)
Outputs
Outputs
Floating
Does not output
(fixed to "H" output)
Does not output
(fixed to "H" output)
Outputs
Outputs
Outputs
(inputs external data at read cycle)
Outputs
("L" output at write cycle,
"L" output at read cycle)
Outputs
Outputs
∗ for difference
∗
∗
∗
∗
∗
( 18 / 76 )
IMPORTANT
Table 1.4 Differences of outputs between actual MCUs and this product (in stop mode)
Access area-Signal
Address
BHE*
Data Floating
RD*
WR*
CS*
ALE
Actual MCU
Retains previous status
Retains previous status
Does not output
(fixed to "H" output)
Retains previous status
Does not output
(fixed to "H" output)
Table 1.5 Differences of outputs between actual MCUs and this product (in wait mode)
Access area-Signal Actual MCU
Address
BHE*
Data
RD*
WR*
CS*
ALE
Retains previous status
Retains previous status
Does not output
(fixed to "H" output)
Retains previous status
Does not output
(fixed to "H" output)
This product
Retains previous status
Does not output
(fixed to "H" output)
Retains previous status
Does not output
(fixed to "H" output)
This product
Retains previous status
Floating
Does not output
(fixed to "H" output)
Retains previous status
Does not output
(fixed to "H" output)
∗ for difference
∗ for difference
∗
∗
Table 1.6 Outputs of this product when the user program is stopping
Signal
Address
BHE*
Data
RD*
WR*
CS*
ALE
This product
Outputs
Floating
Outputs RD* only
(WR* fixed to "H" output)
Outputs
Outputs
( 19 / 76 )
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 Terminology ............................................................................................................................... 22
2.2 Package Components..................................................................................................................23
2.3 Other Tool Products Required for Development........................................................................23
2.4 Name of Each Part......................................................................................................................24
(1) System Configuration ........................................................................................................... 24
(2) Inside of the Emulation Pod..................................................................................................25
2.5 When Using the Emulator for the First Time.............................................................................26
( 21 / 76 )
Chapter 2. Preparation
2.1 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 8 and 16-bit MCUs. For details on specific models of
PC4701, visit the Renesas Tools Homepage.
Emulation pod
This means M306H2T-RPD-E (this product). This emulation pod is for M16C/6H Group M306H2.
Host machine
This means a personal computer used to control the emulator and emulation pod.
Emulator debugger
http://www.renesas.com/en/tools
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 leading/trailing 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 MCU mounted on the emulation pod which is operated in the specific mode for tools.
Target MCU
This means the MCU 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)
( 22 / 76 )
2.2 Package Components
The M306H2T-RPD-E package consists of the following items. When unpacking, check to see if
your M306H2T-RPD-E contains all of these items.
Package components
Item
M306H2T-RPD-E emulation pod main unit
FLX120-RPD flexible cable for connecting PC4701
FLX160 flexible cable for connecting pitch converter board (pre-installed in emulation pod)
FLX160-PRB pitch converter board for connecting target system (pre-mounted on FLX160)
M306H2T-PTC pitch converter board for connecting 116-pin 0.65-mm-pitch (116P6A-A)
foot pattern (includes YQPACK116SB×1, NQPACK116SB×1 and YQ-GUIDE×4)
OSC-2 oscillator circuit board
Hardware tool user registration FAX sheet (English)
Hardware tool user registration FAX sheet (Japanese)
M306H2T-RPD-E user's manual (this manual)
M306H2T-RPD-E user's manual (Japanese)
Quantity
1
1
1
1
1
1
1
1
1
1
Please keep the M306H2T-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.
2.3 Other Tool Products Required for Development
To bring forward programs development on the M16C/6H Group MCUs, the products listed below
are necessary in addition to those contained package above. Get them separately.
Other tool products required for development
Emulator main unit
Emulator debugger
To purchase these products, contact your nearest distributer.
PC4701
M3T-PD30
( 23 / 76 )
Loading...