Renesas M3062PT-EPB Switch User Manual


 
( 12 / 80 )
IMPORTANT
Note on NMI* Input:
•A low input to pin NMI* from the target system is accepted only when a user program is being
executed (when the RUN status LED on the PC7501's front panel is lit).
Note on RDY* Input:
Be sure to input a low to pin RDY* of the target system during the user program execution (only
while the RUN status LED on the PC7501's upper panel is lit). Inputting a low signal to pin RDY*
when the user program is stopped may cause a malfunction of the emulator.
Note on HOLD* Input:
Be sure to input a low to pin HOLD* of the target system during the user program execution (only
while the RUN status LED on the PC7501's upper panel is lit). Inputting a low signal to pin HOLD*
when the user program is stopped may cause a malfunction of the emulator.
Note on Clock Supply to the MCU:
•A clock supplied to the evaluation MCU is selected by the Emulator tab in the Init dialog box of
the emulator debugger.
(1) When "Internal" is selected:
A clock generated by the oscillator circuit board in the PC7501 is supplied. It is continually
supplied regardless of the status of the target system clock and that of the user program
execution.
(2) When "External" is selected:
A clock generated by the oscillator in the target system is supplied. It depends on the status
of the oscillation (on/off) of the target system.
(3) When "Generate" is selected:
A clock generated by the dedicated circuit in the PC7501 is supplied. It is continually supplied
regardless of the status of the target system clock and that of the user program execution.
Notes on Maskable Interrupts:
Even if a user program is not being executed (including when run-time debugging is being
performed), the evaluation MCU keeps running so as to control the emulation probe. Therefore,
timers and other components do not stop running.
If a maskable interrupt is requested when the user program is not being executed (including when
run-time debugging is being performed), the maskable interrupt request cannot be accepted,
because the emulator disables interrupts. The interrupt request is accepted immediately after the
user program execution is started.
Take note that when the user program is not being executed (including when run-time debugging
is being performed), a peripheral I/O interruption is not accepted.