
( 13 / 48 )
IMPORTANT
Note for Installation:
• The emulator PC4701U does not operate stand-alone. It must always be
connected with the emulation pod before you can execute the self-check or
download firmware after setting up. If using an emulator MCU method
emulation pod, both the emulator MCU and target system must be con-
nected as well.
Notes for Difference between the Actual MCU and Emulator:
• Emulator operation differs from a mask MCU, as listed below:
(1) Reset condition
(2) Initial values of internal resource data at power-on
(3) Internal RAM and ROM capacities
(4) A-D converter characteristics when using emulation pods in the
evaluation MCU method.
• Therefore, always be sure to evaluate your system with an evaluation MCU
(EPROM or OTP version). Also, be sure to perform board-mounted evalu-
ation with CS (Commercial Sample) version MCU to make final confirma-
tion of device operation before starting mask production.
Notes for Unusual Operation:
• Do not turn off the power when executing the self-check or downloading
firmware. If the emulator PC4701U is powered off in the middle of a pro-
cess, it will become unable to start up normally. In cases when the power is
inadvertently shut off, re-execute the self-check or downloading.
• If the self-check does not terminate normally (except for status errors), the
emulator PC4701U can be faulty. In such a case, contact your local dis-
tributor.
• If the emulator PC4701U 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
PC4701U.
(2) If the emulator PC4701U doesn't return to the normal operation de-
spite the step (1) above, turn off the power source of the emulator
PC4701U, and turn it on again.
Notes for Downloading Firmware:
• Download firmware as described in "4.3 Downloading Firmware" (P.37)
when:
(1) you have set up the emulator PC4701U for the first time.
(2) you have upgraded the firmware.
(3) you have upgraded your emulator debugger.
(4) you have changed your emulator debugger.
(5) you have changed your emulation probe.
Comentarios a estos manuales