Note On Address 0 Access; Note On Differences Between Actual Mcu And Emulator; Note On Referencing And Setting The Work Area; Notes On Map References And Settings - Renesas Emulation Pod forM16C/20 Series M30200T-RPD-E User Manual

Emulation pod form16c/20 series
Table of Contents

Advertisement

Note on Address 0 Access:

• With the M16C/20 series MCU, when a maskable interrupt is generated, the interrupt data
(interrupt No. and interrupt request level) stored in address 0 is read out. Also, the interrupt request
bit is cleared when address 0 is read out. Consequently, when the address 0 read-out instruction is
executed or when address 0 is read out in the cause of a program runaway, a malfunction occurs
in that the interrupt is not executed despite the interrupt request, because the request bit of the
highest priority interrupt factor enabled is cleared.

Note on Differences between Actual MCU and Emulator:

• Emulator operation differs from mask MCU operation, as listed below:
(1) Initial values of internal resource data at power-on
(2) Internal ROM and RAM capacities, etc.
(3) A/D converter

Note on Referencing and Setting the Work Area:

• The work area given below is assigned as the initial setting at the time of starting up the emulator
debugger.

Notes on MAP References and Settings:

• When starting up M30200T-RPD-E, initial MAP settings are as follows.
• Always set the SFR area to EXT (external).

Note on Changing Settings of the Memory Area:

• To debug an MCU different in memory capacity, be sure to modify the settings in the memory area
before using the MCU. For memory maps of respective MCUs, see the MCU User's Manual.
IMPORTANT
A/D converter characteristics differ from actual MCU characteristics because the flexible
cable and other elements are used between the emulation MCU and target system.
02C00
to 02C0F
: Work area
16
16
00000
to 003FF
: EXT
16
16
00400
to FFFFF
: INT
16
16
( 13 / 32 )

Advertisement

Table of Contents
loading

Table of Contents