Note on Pullup Control Resistor ................................................................................ 16

Note on Reading Internal Resources of an MCU ...................................................... 16

Notes on Watchdog Function ..................................................................................... 16

Note on Differences between Actual MCU and Emulator ........................................ 17

( 8 / 77 )

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

CAUTION

IMPORTANT

If the requirements shown in the "WARNING" 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 cause personal injury or damage to the products.

NOTE: 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".

( 9 / 77 )

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 / 77 )

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 50). 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 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 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.

For details, refer to "Chapter 4. Usage" (page 47).

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 / 77 )

IMPORTANT

Notes on MAP References and Settings:

• For details on referencing and setting MAP information, see User's Manual of emulator debugger

PD30.

• 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 the condition 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.

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 INTERNAL.

(2) Execute the RESET command of emulator debugger PD30.

(3) Set the stack pointer.

(Example)

RESET:

FCLR I

LDC #0480H, SP <-- Set the stack pointer.

(Stop the program after executing this instruction.)

(4) Set the 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 emulator debugger PD30.)

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.

( 12 / 77 )

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).

Note on HOLD* Input:

• Be sure to input "L" 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 "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 executing (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:

• 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 "H" to "L" level during target program execution

(2) After the reset is released by the target system when the NMI* pin is "L" level during target program execution

(3) Immediately after program execution starts with the NMI* pin "L" level, following the reset input from the debug software 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 / 77 )

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/6N 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 S/W 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 / 77 )

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

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

Notes on S/W Breaks and H/W Breaks:

• S/W 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 S/W break and a H/W break at the same time. If doing so, it may not operate normally.

• In the area where the MAP setting is EXTERNAL, S/W 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 P7 and port P9 direction registers and the SI/O3, 4 control registers, is changed with the below 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 / 77 )

IMPORTANT

Note 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 resistor.

Note: The pullup control resistor 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

DMA destination pointers 0, 1

DMA transfer counters 0, 1

DMA control resistors 0, 1

SAR0, SAR1

DAR0, DAR1

TCR0, TCR1

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.

( 16 / 77 )

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 X

IN

and X

OUT

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 (X

CIN

and X

COUT

).

• 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 "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).

(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

DBC*

1

Single-step*

1

BRK instruction

Vector table addresses

FFFF4h - FFFF7h

FFFECh - FFFEFh

FFFE4h - FFFE7h

Data for reading

Indefinite

Indefinite

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) 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.

(11) Oscillation stop detection function

With this product, you can not debug the oscillation stop detection function.

( 17 / 77 )

IMPORTANT

(12) 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 resisters P107 - P100 to input.

• Set the pullup control resistors of P107 - P100 to no-pullup.

• P107 - P100 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 resisters P107 - P100 to input.

• Set the pullup control resistors of P107 - P100 to no-pullup.

• P107 - P100 cannot be used as an input pin of I/O port and key input interrupt function.

iii) When selecting port P10 for A-D input

• There is no restriction.

(13) 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 Signal Actual MCU

This product

∗

for difference

Address

BHE*

Outputs Outputs

Data

Outputs

(floating during read operating)

Floating

∗

SFR area

(MAP = EXT)

RD*

WR*

CS*

ALE

Outputs

("L" at write cycle,

"L" at read cycle)

Does not output

(fixed to "H" output)

Does not output

(fixed to "L" output)

Does not output

(fixed to "H" output)

Does not output

(fixed to "H" output)

Outputs

∗

∗

Internal RAM

Internal ROM

Address

BHE*

Data

RD*

WR*

CS*

ALE

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

Floating

Does not output

(fixed to "H" output)

Does not output

(fixed to "H" output)

Outputs

∗

∗

Address

BHE*

Outputs Outputs

External area

Data

RD*

WR*

CS*

ALE

Outputs

(inputs external data at read cycle)

Outputs

("L" at write cycle,

"L" at read cycle)

Outputs

Outputs

Outputs

(inputs external data at read cycle)

Outputs

("L" at write cycle,

"L" at read cycle)

Outputs

Outputs

( 18 / 77 )

IMPORTANT

Table 1.4 Differences of outputs between actual MCU and this product (in stop mode)

Access area Signal Actual MCU This product

∗

for difference

Address

BHE*

Retains previous status Retains previous status

Data Retains previous status Floating

∗

-

RD*

WR*

CS*

Does not output

(fixed to "H" output)

Retains previous status

Does not output

(fixed to "H" output)

Retains previous status

ALE

Does not output

(fixed to "H" output)

Does not output

(fixed to "H" output)

Table 1.5 Differences of outputs between actual MCU and this product (in wait mode)

Access area Signal Actual MCU This product

∗

for difference

Address

BHE*

Retains previous status Retains previous status

Data Retains previous status Floating

∗

-

RD*

WR*

Does not output

(fixed to "H" output)

Does not output

(fixed to "H" output)

CS*

ALE

Retains previous status

Does not output

(fixed to "H" output)

Retains previous status

Does not output

(fixed to "H" output)

Table 1.6 Outputs of this product when the user program is stopping

Signal This product

Address

BHE*

Data

RD*

WR*

CS*

ALE

Outputs

Floating

Only RD* outputs

(WR* is fixed to "H" output)

Outputs

Outputs

( 19 / 77 )