Technical information

( 69 / 76 )
(3) Program Window Does Not Appear at Debugger Startup (target not connected)
Table 6.3 Checkpoints of errors when starting up the emulator debugger (target not connected)
Error Checkpoint
Check that all emulator debugger settings, interface cable
connection and switches on the rear of the PC4701 match.
See the user's manuals of the PC4701 and the emulator
debugger.
(1) Download the proper firmware.
See "4.3 Downloading Firmware" (page 48).
(2) Recheck the connection between the PC4701 and
this product.
See "3.5 Connecting the PC4701" (page 38).
Download the proper firmware.
See "4.3 Downloading Firmware" (page 48).
The program may be uncontrollable in areas where
memory is not allocated. Recheck the map setting.
See the user's manual of the emulator debugger.
(1) The MCU is either in stop mode or wait mode. Either
reset the MCU or cancel the mode with an interrupt.
See the MCU specifications.
(2) The program may be uncontrollable in areas where
memory not allocated. Recheck the map setting.
See the user's manual of the emulator debugger.
Check that the switches in the emulation pod are correctly
set.
See "3.2 Setting Switches and Pullup Resistors" (page 29).
Communication error occurred
Data was not sent to the target
Target system cannot be properly built
M3T-PD30 version is not the same version
as the firmware in the target
Target MCU cannot be reset
Target is in HOLD state
Target clock is stopped
(4) Errors Occur at Debugger Startup (target connected)
Table 6.4 Checkpoints of errors when starting up the emulator debugger (target connected)
Error Checkpoint
(1) If in memory expansion mode or microprocessor
mode, check pins RDY* and HOLD* are held "High".
(2) The program may be uncontrollable in areas where
memory is not allocated. Recheck the map setting.
See the user's manual of the emulator debugger.
Target MCU is uncontrollable.