Filter
Top Products
( 45 / 52 )
6.3 Operation Differs from That of Actual MCUs
(1) Cannot Reset from the Target System
Set the time for starting up (0.2 Vcc to 0.8 Vcc) 1 µs or less.
(2) Data Values of RAM Area at Power-on are Different
For this product, 04h is written into the RAM area at power-on. Therefore, the data values are different
from those of an actual MCU.
(3) The A-D and D-A Conversion Values are Different from Expected Values
Because 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 CS (Commercial Sample) version MCU.
(For details, refer to "1.1 Note on Differences between the Actual MCU and Emulator" on page 14.)
(3) Errors Occur When Starting Up the Emulator Debugger
(When the target system is not connected)
Table 6.3 Checkpoints of errors when starting up emulator debugger (target is not connected)
Error
Communication ERROR.
Can't send data.
Target system is not constructed properly.
The version of M3T-PD30 and the firmware
on the target are not same.
Target MCU cannot be reset.
Target MCU is in HOLD state
Target MCU is not given clock.
Checkpoint
Check that 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 "4.2 Downloading Firmware" (page 34).
(2) Recheck that the connection between the PC4701
and this product.
See "3.4 Connecting the PC4701 and Emulation
Pod" (page 27).
(1) Download the proper firmware.
See "4.2 Downloading Firmware" (page 34).
(2) Check that the descriptions in the MCU file are
correct.
See "2.4 (1) Making the MCU File" (page 18).
The program may be uncontrollable in areas where
memory is not allocated. Recheck that the map setting.
See "1.1 Notes on MAP References and Settings"
(page 11).
(1) 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.
(2) The program may be uncontrollable in areas where
memory is not allocated. Recheck that the map setting.
See "1.1 Notes on MAP References and Settings"
(page 11).
Check the oscillator in the emulation pod is oscillating
properly.