* IBM and PC/AT are registered trademarks of International Business Machines 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 user's 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.
The M306V0T-RPD-E is an emulation pod for the M16C/6V group of Renesas 16-bit MCUs. The
M306V0T-RPD-E is used by being connected to the PC4701 emulator (PC4701HS, PC4701L,
PC4700H or PC4700L) and is controlled by the emulator debugger.
This manual mainly explains specifications and setting up of the M306V0T-RPD-E. For detail
information about the PC4701 emulator and the emulator debugger, refer to each user's manual.
To check the components of this product, refer to "Things to Check When Unpacking" in this 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". 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.
10.1 When M306V0T-RPD-E Does Not Work Properly .........................................42
Appendix A. External Dimensions.......................................................................................43
A.1 External Dimensions of the M306V0T-RPD-E .................................................43
A.2 External Dimensions of the FLX-100LCC ........................................................44
Appendix B. Connection Diagrams......................................................................................45
( 5 / 48 )
Terminology
Some specific words used in this User's Manual are defined as follows:
PC4701
This means the generic name of the PC4701HS, PC4701L, PC4700H, and PC4700L emulators.
PC4701 system
This means an emulator system built around a PC4701 emulator. The PC4701 emulator system is
configured with the emulator main unit, an emulation pod, an emulator debugger, and a host machine.
Emulator debugger
This means a software tool to control the emulator from the host machine through an interface.
Target MCU
This means the microcomputer you are going to debug.
Target system
Emulator debugger: M3T-PD30 (V.3.00 Release 1 or later)
Host machine: IBM PC/AT or compatible
OS: Windows 95 or Windows NT 4.0
CPU: 486DX4-100 MHz or Pentium 75 MHz (or faster recommended)
Memory: 16 MB or more
This means a user's application system using the microcomputer to be debugged.
( 6 / 48 )
Things to Check When Unpacking
The M306V0T-RPD-E consists of the following parts and manuals. When unpacking, check to see
if your M306V0T-RPD-E package contains all of these items.
M306V0T-RPD-E (Emulation pod)
FLX120-RPD (Flexible cable for connecting PC4701 emulator)
Screws for connecting PC4701 emulator
FLX100 (Flexible cable for connecting target system, already connected)
FLX-100LCC (Converter board for 100LCC package)
OSC-2 (Oscillator board)
M306V0T-RPD-E English user's manual (this manual)
M306V0T-RPD-E Japanese user's manual
1
1
2
1
1
1
1
1
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 products, contact your local distributor.
CAUTION
Please keep the M306V0T-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 the M306V0T-RPD-E.
( 7 / 48 )
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.
( 8 / 48 )
1.2 Precautions for Safety
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.
Warning for Use Environment:
• 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
Cautions to Be Taken for This Product:
• Do not disassemble or modify this product as personal. Disassembling or modifying this product
can cause damage.
• Use caution when handling the main unit. Be careful not to apply a mechanical shock.
• Do not touch directly the connector pins of the emulator main unit or the target MCU connector pins
with your hand.
•Do not pull the emulation pod main unit by the FLX120-RPD flexible cable or the FLX100 flexible
cable for connecting the target system.
• The flexible cables FLX120-RPD and FLX100 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 used on the equipment.
Cautions for Installation:
• Do not place the main unit on its side when in use.
( 9 / 48 )
IMPORTANT
Notes on PC4701 Emulators:
• The PC4700H emulators whose serial number ends with a number cannot be used with M306V0T-
RPD-E. Use only products whose serial number ends with a letter of the alphabet. The serial number
is on the bottom of the PC4700H.
Example: 5KE100 ........ Can NOT be used with M306V0T-RPD-E.
Example: 5LE123B ......Can be used with M306V0T-RPD-E.
• Do not turn off the power when downloading firmware. If the emulator is powered off in the middle
of the process, it will become unable to start up normally. In cases when the power is inadvertently
shut off, re-execute downloading.
Notes on Abnormal Operation:
• If the PC4701 system does not pass all self-checks (excluding when an target system error occurs),
there is the possibility of trouble in the system. In such case, contact the place of purchase.
Please take note that self-check should be executed under the following conditions.
(1) The target system is not connected.
(2) The Switch SW6 is set to 'L' position, SW7 to '16' (see Chapter 4).
Requires an upgrade.
• If the emulator malfunctions due to external interference or some other causes, follow the steps
given below.
(1) Press the system reset switch located on the front panel of the emulator.
(2) If the emulator does not return to the normal operation despite the step (1) above, turn off the
power source of the emulator, turn it on again.
Notes on Target System:
• Because the emulation pod does not have the capacity to supply power to other devices, design your
system so that the emulator MCU is powered by the target system.
• Make sure that the target's supply voltage is within the MCU specification and in the range of +4.5
to 5.5 V.
• Do not change power supply voltage of the target system after activating the power.
• Before turning on power to anything, check the host machine, emulator main unit, emulation pod,
conversion board and user's target system are properly connected. Activate power to units as
explained here following.
(1) Turn on and off power to the target system, and then the PC4701 continuously.
(2) After turning on power to the PC4701, check the Target Status LEDs on the emulator' front
panel to see if the M306V0T-RPD-E is ready to operate.
• Is the power supplied? Check that Target Status LED (POWER) is on.
• Is the reset released? Check that Target Status LED (RESET) is off.
( 10 / 48 )
IMPORTANT
Notes on Connecting Target System:
• When connecting the FLX100 flexible cable and the converter board, be careful not to forcibly
press the connector top of the converter board. (The flexible cable and the converter board are
guaranteed for only 20 insertion/removal iterations.)
• Especially be careful not to insert the converter board in the wrong direction.
Note on Reset Input from Target System:
•The reset input from the target system is accepted only during program execution (while the RUN
signal lamp on the PC4701 is lit).
Note on HOLD Input from Target System:
• Input an 'L' level signal into the HOLD pin only during program execution. Doing so while the
program is stopped or during run time debugging may cause the emulator to malfunction.
Note on Address 0 Access:
• With M16C/6V group MCUs, when a maskable interrupt is generated, the interrupt data (interrupt
number and interrupt request level) stored in address 0 is read out.
Also, the interrupt request bit is cleared when address 0 is read out. Consequently, when the address
0 readout instruction is executed or when address 0 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.
Therefore, with M306V0T-RPD-E, if address 0 is read out for anything other than interrupt
processing, the yellow LED lights up as a warning. When this LED lights up, there is the possibility
of illegal access to address 0, therefore check the program. This LED is extinguished from the
emulator reset switch.
( 11 / 48 )
IMPORTANT
Notes on Differences between Actual MCU and Emulator:
• Emulator operation differs from mask MCU operation, as listed below:
(1) Reset condition
(2) Initial values of internal resource data at power-on
(3) Internal RAM and ROM capacities, etc.
(4) Ports P00 to P57
Of the M306V0T-RPD-E's I/O ports, ports P00- P57are connected to the user's target system
through the port emulation circuit inside M306V0T-RPD-E.
Table 1.1 gives the device which uses these ports.
Table 1.1 I/O device used by each of the ports
Port
I/O device
P00-P57
(5) Writing into pullup control registers 0 and 1 (addresses 03FC16 and 03FD16 respectively)
To write into pullup control registers 0 and 1 (addresses 03FC16and 03FD16 respectively), it
is necessary to write the word data from address 03FC16. This is an M306V0T-RPD-E
restriction.
(6) Ports P50 - P53
To enable pullup when setting bit 2 (PUR12) of the pullup register 1 to '1' in single chip mode,
be sure to set the bit 2 (PM02) and bit 7 (PM07) of the processor mode register 0 to '0'. This
is an M306V0T-RPD-E restriction.
(7) BCLK output disable
To disable the BCLK output, it is necessary to set the BCLK output disable bit (PM07) of
processor mode register 0 (address 000416) to '1' and to set bit 3 of the port P5 direction register
(address 03EB16) to '0'. This is an M306V0T-RPD-E restriction.
(8) Hold control
When an 'L' level signal is input to the terminal HOLD and the terminal enters the hold state,
in actuality, ports P00to P5 2 enter the hold state one half cycle later than the MCU (see Chapter
7, Operation Timing).
(9) A/D converter
A/D converter characteristics differ from actual MCU characteristics because the flexible
cable and other elements are used between the emulation MCU and user’s target.
M60074-0111FP
(10) Status while the program is stopped
In a system using the PC4701, the loop iteration at the address F800016establishes and
maintains the status during program stop. Also, when debug commands are issued to check
or edit memory data, addresses F800016to F83FF16 and addresses F600016to F63FF16 are used
as work area. For this reason, when the CS0 output is enabled in the microprocessor mode,
the CS0 signal is output.
( 12 / 48 )
IMPORTANT
(11) Actual MCU output and emulator output
Table 1.2 Actual MCU and emulator outputs
SFR area
Internal RAM area
Internal ROM area
External area
In STOP state
Address
Data
RD/WR
CS
ALE
BHE
Address
Data
RD/WR
CS
ALE
BHE
Address
Data
RD/WR
CS
ALE
BHE
Address
Data
RD/WR
CS
ALE
BHE
Output
Output (Floating during
read operations
Output (WR=Low at write cycle,
RD=Low at read cycle)
No output
(High output fixed)
No output
(Low output fixed)
Output
Previous status maintained
Floating
No output
(High output fixed)
No output
(High output fixed)
No output
(Low output fixed)
No output (Previous
status maintained)
Output
Output (Inputs external
data when reading)
Output (WR=Low at write cycle,
RD=Low at read cycle)
Output
Output
Output
M306V0T-RPD-EActual MCUSignalAccess area
Output
Floating
)
No output
(High output fixed)
No output
(High output fixed)
Output
Item with
different
output
s
*
*
*
Output
Output
Floating
No output
(High output fixed)
No output
(High output fixed)
Output
*
*
Output
*
Output
Output (Inputs external
data when reading)
Output (WR=Low at write cycle,
RD=Low at read cycle)
Output
Output
Output
Output
Floating
Output only for Read operations
(WR = High output fixed)
Output
Output
Output
( 13 / 48 )
IMPORTANT
Notes on MAP Settings and References:
• For details on MAP settings and references, refer to the M3T-PD30 emulator debugger user's
manual.
•Always set the SFR area to EXTERNAL.
• Set the OSD RAM area to INTERNAL.
• This pod uses the 4 bytes from 0FFFC16 to 0FFFF16 as a stack area for a RESET command. The
RESET command cannot be correctly executed when these 4 bytes cannot be read or written to.
You must therefore take care using the MAP resetting procedure when the following condition (1)
or condition (2) are true.
(1) When the 4 bytes from 0FFFC16 to 0FFFF16 are set to EXTERNAL in a system shifting from
single chip mode to memory expansion mode or microprocessor mode
(2) When the 4 bytes from 0FFFC16 to 0FFFF16 are set to EXTERNAL in a system started in
microprocessor mode and there is no read/write-enabled memory in the external area.
Use the following MAP setting procedure when either of the above conditions (1) or (2) are true.
(1) Set the 4 bytes from bytes from 0FFFC16 to 0FFFF16 to INTERNAL.
(2) Execute the M3T-PD30 emulator debugger RESET command.
(3) Set the stack pointer.
(Example)
RESET:
FCLR I
LDC #480H, SP <- stack pointer setting
:(STOP the program after executing this command.)
(4) Set the 4 bytes from 0FFFC16 to 0FFFF16 to EXTERNAL.
Note on Changing Data in OSD RAM Area When Program is not Executed:
•To change data when a program is not executed, write data when the map setting is in both
'INTERNAL' and 'EXTERNAL'.
Procedure
(1) With 'INTERNAL' specified, change data in the OSD RAM area.
Change data in the MEMORY WINDOW, Script Window, etc.
(2) From the script window, change the map setting of the OSD RAM area to 'EXTERNAL' .
MAP 400,FFF,EXT
(3) With 'EXTERNAL' specified, change data in the OSD RAM area.
Change data in the MEMORY WINDOW, Script Window, etc.
(4) Change the map setting of the OSD RAM area to 'INTERNAL' again.
MAP 400,FFF,INT
(Example)When changing the data in the OSD RAM area (Address: 410h) to '55h'.
set MemoryByte( MB ) 410,55
MAP 400,FFF,EXT
set MemoryByte( MB ) 410,55
MAP 400,FFF,INT
( 14 / 48 )
IMPORTANT
Note on Reading MCU Internal Sources:
• When this product is configured with the emulator debugger, the following results occur when
reading the registers listed in Table 1.3. Data is not displayed correctly, but internal data is not
affected at all.
(1) Real-time tracing
Data values in the MCU internal source read cycle are not displayed correctly.
(2) Real-time RAM monitoring
Data is not displayed correctly.
This happens because data read from the MCU internal source is not output to an external
point. When data is written into an MCU internal source, the data input from the external point
is displayed correctly.
Table 1.3 Registers and signals
Register
Processor mode registers 0, 1
System clock control registers 0, 1
Chip select control register
Address identity interrupt enable register
Protect register
Supervisor timer start register
Supervisor timer control register
Address identity interrupt registers 0, 1
DMA source pointers 0, 1
DMA destination pointers 0, 1
DMA transfer counters 0, 1
DMA control registers 0, 1