(When The Target System Is Not Connected); (When The Target System Is Connected); Operation Differs From That Of Actual Mcus; When The A-D Conversion Values Are Different From Expected Values - Renesas M30830T-RPD-E User Manual

Emulation pod for m32c/81, 82, 83 group mcus
Table of Contents

Advertisement

(3) EMEM Dialog Box is Not Displayed When the Emulator Debugger Starts Up
Table 6.3 Checkpoints of errors when starting up the emulator debugger (target is not connected)
Communication error occurred.
Data was not sent to the target.
Target system cannot be properly built.
PD308 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.
(4) Errors Occur When the Emulator Debugger Starts Up
Table 6.4 Checkpoints of errors when starting up the emulator debugger (target is connected)
Target MCU is uncontrollable.

6.3 Operation Differs from That of Actual MCUs

(1) When the A-D Conversion Values are Different from Expected Values

Because a flexible 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.

(When the target system is not connected)

Error

(When the target system is connected)

Error
Check all emulator debugger settings, interface cable
settings and switches on the rear of the PC4701 match.
See the instruction manuals of the PC4701 and emulator
debugger.
(1) Download the proper firmware.
See "4.2 Downloading Firmware" (page 48).
(2) Recheck the connection between the PC4701 and
this product.
See "3.5 Connecting the PC4701 and Emulation Pod"
(page 34).
Download the proper firmware.
See "4.2 Downloading Firmware" (page 48).
The program may be uncontrollable in areas where
memory is not allocated. Recheck the map setting.
See "4.3 Starting Up the Emulator Debugger (Setting
EMEM Dialog Box)" (page 49).
(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 the map setting
See "4.3 Starting Up the Emulator Debugger (Setting
EMEM Dialog Box)" (page 49).
Check the switches in the emulation pod are correctly set.
See "3.2 Switch Settings" (page 25).
(1) Check pin NMI* is held high.
(2) If in memory expansion mode or microprocessor
mode, check pins RDY* and HOLD* are "H" level.
(3) The program may be uncontrollable in areas where
memory is not allocated. Recheck the map setting.
See "4.3 Starting Up the Emulator Debugger (Setting
EMEM Dialog Box)" (page 49).
( 67 / 74 )
Checkpoint
Checkpoint

Advertisement

Table of Contents
loading

Table of Contents