Filter
Top Products
( 32 / 40 )
Chapter 5. Troubleshooting
When this product does not work properly, check the following.
5.1 When the Emulator Debugger Does Not Operate
(1) Errors Occur When Operating the Emulator Debugger
(When the target system is connected)
Table 5.1 Checkpoints of errors when starting up the emulator debugger M3T-PD79 (target is connected)
Error
Communication ERROR
Data is not sent to the target
Target system is not constructed properly
The version of M3T-PD79 and the firmware
on the target system are not same
Target MCU is reset state
Target MCU cannot be reset
Flash ROM erase error occurred
Target clock is stopped
Target MCU is not receiving power
Not connected to target
Cannot connect to target
Target MCU is uncontrollable
Reset target system
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) Recheck the connection between the PC4701, the
emulation pod and this product.
- See "3.3 Connecting the Emulation Pod Main Unit"
(page 22).
- See user's manual of the M37900T2-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) If the reset circuit of the target system has a watchdog
timer, disable the timer.
(2) Check power is properly supplied to the target system
and that the target system is properly grounded.
(3) Check your emulator debugger M3T-PD79 is Ver.2.10
or greater.
(4) The flash ROM of the MCU may be worn-out. Contact
your local distributor.
Check the oscillation circuit of the target system is
oscillating properly.
Check power is properly supplied to the target system
and that the target system is properly grounded.
(1) Recheck the connection of the emulation pod and this
product.
- See "3.3 Connecting the Emulation Pod Main Unit"
(page 22).
(2) Recheck the connection of the SSOP42B-450 and
the socket.
- See "3.4 Connecting the Target System" (page 24).
Check the program is not accessing to the unused area.