Filter
Top Products
( 30 / 36 )
(3) Errors Occur When the Emulator Debugger Starts Up
(When the target system is not connected)
Table 5.3 Checkpoints of errors when starting up the emulator debugger (target is not connected)
5.2 Operation Differs from That of MCUs with PROM
(1) When the A-D Conversion Values are Different from Expected Values
The A-D converter characteristics differ from actual MCU characteristics because there are a
converter board and other devices between the evaluation MCU and the target system. Make the final
evaluation of the A-D converter with the actual MCU.
(2) When the D-A Conversion Values are Different from Expected Values
The D-A converter characteristics differ from actual MCU characteristics because there are a
converter board and other devices between the evaluation MCU and the target system. Make the final
evaluation of the D-A converter with the actual MCU.
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 manual 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 the user's manual of the M30200T-RPD-E.
Download the proper firmware.
See the user's manual of the emulator debugger.
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.
Check the switches of the FLX64-PRB are correctly set.
See "3.1 Switch Settings" (page 14).
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 are not same
Target is "HOLD" state
Target MCU is not given clock