Renesas PC7501, Руководство пользователя

Страница: 12 / 50

PC7501 User’s Manual 1. Precautions for Safety
R20UT0207EJ0500 Rev.5.00 Page 12 of 50
Nov 01, 2010
IMPORTANT
Note for Installation:
• The emulator PC7501 does not operate stand-alone. It must always be connected with the emulation
probe M3xxxxTx-EPB or R0ExxxxxxEPB00 before you can execute the self-check or download
firmware.
Notes for Difference between the Actual MCU and Emulator:
• Emulator operation differs from that of a mask MCU, as listed below:
(1) Reset conditions
(2) Initial values of internal resource data at power-on
(3) Internal RAM and ROM capacities
(4) A-D converter characteristics when using an emulation probe in the evaluation MCU method.
• Therefore, always be sure to evaluate your system with an evaluation MCU (OTP, EPROM or flash
version). Also, be sure to perform board-mounted evaluation with CS (Commercial Sample) version
MCU to make final confirmation 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
PC7501 is powered off in the middle of a process, 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 target status errors), the emulator PC7501 can
be faulty. In such a case, contact your local distributor.
• If the emulator PC7501 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 PC7501.
(2) If the emulator PC7501 does not return to the normal operation despite the step (1) above, turn off
the power supply switch of the emulator PC7501, and turn it on again.
Note for Downloading Firmware:
• Download firmware as described in "4.4 Downloading Firmware" (P.36) when:
(1) you have set up the emulator PC7501 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.