Filter
Top Products
( 51 / 58 )
(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 not connected)
6.3 Operation Differs from That of Actual MCUs
The operations of the emulation pod differs from those of actual MCU as listed (1) to (5) below.
(1) Data values of internal resources of MCU at power-on
(2) Internal memories (RAM and ROM) capacities etc.
(3) Oscillator circuit
•Make note of the fact that in the oscillator circuit where a resonator is connected between
the XIN and XOUT pins, oscillation does not occur because a flexible cable, buffer IC and other
devices are used between the evaluation MCU and the target system.
•Make note of the fact that if the internal oscillator circuit of the emulator is selected when
the MCU is stopping, the oscillation does not stop.
(4) DBC, single-step and BRK instruction interrupt vector table addresses
As the emulator uses the DBC, single-step and BRK instruction interrupt vector table addresses,
when reading these addresses, the downloaded addresses cannot be read.
(5) A-D conversion
As a flexible cable, a pitch converter board and other devices are used between the evaluation
MCU and the target system, some characteristics are slightly different from those of the actual
MCU. Therefore, be sure to evaluate your system with an evaluation MCU. Before starting
mask production, evaluate your system and make final confirmation with an ES (Engineering
Sample) version MCU.
Error
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
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 38).
(2) Recheck the connection between the PC4701 and
this product.
See "3.5 Connecting the PC4701 and Emulation Pod"
(page 30).
Download the firmware in the maintenance mode.
See "4.2 Downloading Firmware" (page 38).
The program may be uncontrollable in areas where
memory not allocated. Recheck the map setting.
See "1.1 Notes on MAP References and Settings" (page
13).
(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.
See "1.1 Notes on MAP References and Settings"
(page 13).
Check the switches in the emulation pod are correctly set.
See "3.3 Selecting Clock Supply (page 25).