Filter
Top Products
( 47 / 54 )
(2) Errors Occur When Starting Up the Emulator Debugger
(When the target system is connected)
Table 6.2 Checkpoints of errors when starting up the emulator debugger (target is connected)
Error
Communication ERROR
Data is not sent to the target
Target system is not constructed properly
The version of M3T-PD30 and the firmware
on the target system are not same
Target MCU is reset state
Target MCU cannot be reset
Target MCU is in "HOLD" state
Target clock is stopped
Target MCU is not receiving power
Checkpoint
Check all emulator debugger settings, interface cable
connections and switches on the rear of the PC4701
match.
See the user's manuals of the PC4701 and emulator
debugger.
(1) Download the proper firmware.
See the user's manual of the emulator debugger.
(2) Recheck the connection between the M30200T-RPD-
E and this product.
See "3.3 Connecting the M30200T-RPD-E" (page 21).
(3) Recheck the connection between the PC4701 and
the M30200T-RPD-E.
See the M30200T-RPD-E User's Manual.
Download the proper firmware.
See the user's manual of the emulator debugger.
(1) Check the reset pin of the target system is pulled up.
(2) Check the reset pin of the target system has changed
from "L" to "H" level.
(1) Check the NMI* pin is "H" level.
(2) If the reset circuit of the target system has a watchdog
timer, disable the timer.
(3) Check power is properly supplied to the target system
and that the target system is properly grounded.
The MCU is either in the stop mode or wait mode. Either
reset the MCU or cancel the mode with an interrupt.
See MCU specifications.
(1) Check the oscillation circuit in the target system is
oscillating properly.
(2) Check the switches of the FLX64-PRB are correctly
set.
See "3.1 Switch Settings" (page 18).
Check power is properly supplied to the target system
and that the target system is properly grounded.