Technical information

( 12 / 76 )
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).
Notes on HOLD* Input:
• Be sure to input "Low" 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 "Low" to the HOLD* pin
when stopping the user program may cause a malfunction of the emulator.
• When inputting "Low" 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 Table 5.5 and Figure 5.5).
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 "High" to "Low" level during target program
execution
(2) After the reset is released by the target system when the NMI* pin is "Low" level during target
program execution
(3) Immediately after program execution starts with the NMI* pin "Low" level, following the
reset input from the debug software or emulator main unit
(4) Immediately after program execution starts when the NMI* pin is "High" level immediately
before the target program stops and changes to "Low" level when target program execution
starts
Note on RDY* Input:
• Be sure to input "Low" 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 "Low" to the RDY* pin
when stopping the user program may cause a malfunction of the emulator.
Notes on Interrupts:
• 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.