Filter
Top Products
( 29 / 36 )
(2) Errors Occur When the Emulator Debugger Starts Up
(When the target system is connected)
Table 5.2 Checkpoints of errors when starting up the emulator debugger (target is connected)
Error 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 manuals of the emulator debugger.
(2) Check the connection between the M30200T-RPD-E
and this product.
See "3.3 Connecting M30200T-RPD-E" (page 16).
(3) Check the connection between the PC4701 and the
M30200T-RPD-E.
See user's manual of the M30200T-RPD-E.
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 and GND are properly supplied to the
target system.
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 oscillator circuit on the target system is
oscillating properly.
(2) Check the switches of the FLX64-PRB are correctly
set.
See "3.1 Switch Settings" (page 14).
Check power and GND are properly supplied to the target
system.
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 is unable to reset
Target is "HOLD" state
Target MCU is not given clock
Target MCU is not given power