Renesas Single-Chip Microcomputer M37900T2-RPD-E - Manual (Page 45)

( 45 / 52 )
(3) Errors Occur at Debugger Startup (target not connected)
Table 6.3 Checkpoints of errors of the emulator debugger M3T-PD79 (target is not connected)
Error
Communication error occurred
Data was not sent to the target
Target system cannot be properly built
M3T-PD79 version is not the same version
as the firmware in the target
Target MCU cannot be reset
Flash ROM erase error occurred
Target clock is stopped
Target MCU is uncontrollable
Reset target system
Checkpoint
Check 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 emulator
debugger.
(1) Download the proper firmware.
See "4.2 Downloading Firmware" (page 32).
(2) Recheck the connection between the PC4701, this
product and pod probe.
See the user's manual of the pod probe.
See "3.3 Connecting the PC4701 and Emulation Pod"
(page 26).
Download the proper firmware.
See "4.2 Downloading Firmware" (page 32).
(1) The program may be uncontrollable in areas memory
not allocated. Recheck the map setting.
See "4.3 Starting up the Emulator Debugger (Setting
EMEM Dialog)" (page 33).
(2) The contents of an MCU file varies with the version of
the emulator debugger M3T-PD79. Check the current
MCU file is the one included with your emulator
debugger M3T-PD79.
(3) The flash ROM of the MCU may be worn-out. Contact
your local distributor.
Check the switches in the pod probe are correctly set.
See the user's manual of the pod probe.
(1) Check the program is not accessing to the unused
area.
(2) If using PLL circuit, check the switch settings of the
pod probe.
See the user's manual of the pod probe.