Filter
Top Products
( 65 / 72 )
(3) Errors Occur When the Emulator Debugger Starts Up
(When the target system is not connected)
Table 6.3 Checkpoints of errors when starting up the emulator debugger (target is not connected)
6.3 Operation Differs from That of Actual MCUs
(1) A-D Conversion Values are Different from Expected Values
As a flexible cable, a pitch converter board and other devices are used between the evaluation MCU
and the target system, the A-D converter operates differently from the actual MCU. Make the final
evaluation of the A-D converter from the actual MCU.
Error Checkpoint
Check all emulator debugger settings, interface cable
connection and switches on the rear of the PC4701 match.
See the instruction manuals of the PC4701 and the
emulator debugger.
(1) Download the proper firmware.
See "4.2 Downloading Firmware" (page 42).
(2) Recheck the connection between the PC4701 and
this product.
See "3.6 Connecting the PC4701 and Emulation Pod"
(page 36).
Download the proper firmware.
See "4.2 Downloading Firmware" (page 42).
The program may be uncontrollable in areas where
memory not allocated. Recheck the map setting.
(1) The MCU is either in the 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.
Check the switches in the emulation pod are correctly set.
See "3.2 Switch Settings" (page 25).
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