Renesas Emulation Pod M306N4T3-RPD-E, User Manual

Page: 14 / 76

( 14 / 76 )
Notes on MAP References and Settings:
• For details on referencing and setting MAP information, see the emulator debugger M3T-PD30
user's manual.
Make settings as follows:
(1) MAP = INT
The emulation memory inside this product becomes effective.
Set this at MCU internal ROM debugging.
(2) MAP = EXT
The emulation memory inside this product is not used.
Set this where the MCU internal resource (SFR, RAM) or resources on the target system are
used.
• Be sure to set the SFR area and RAM area of the MCU to EXT, and the reserved area of the MCU
to INT.
• Be sure to set mappings in word units.
• When setting 0FFF9h--0FFFFh to EXT:
This product uses the 7 byte area 0FFF9h through 0FFFFh as the stack area. If this 7 byte memory
cannot be read or written to, reset cannot be properly effected. As a result, you need to alter the map
settings if the condition given below is met.
(1) With the system which shifts from the single-chip mode to memory expansion (or micropro-
cessor) mode, using the 7 byte area of 0FFF9h--0FFFFh set to EXT.
(2) With the system which starts up in microprocessor mode, using the 7 byte area of 0FFF9h-
-0FFFFh set to EXT and there is not enough memory to read or write.
The procedures to alter the MAP settings when the conditions (1) or (2) above are met.
(1) Set the 7 byte area of 0FFF9h--0FFFFh to INT.
(2) Execute the RESET command by use of the emulator debugger M3T-PD30.
(3) Set the stack pointer.
(Example)
RESET: FCLR I
LDC #4000H, SP --> Set the stack pointer
(Stop the program after executing this instruction)
(4) Set the 7 byte area 0FFF9h through 0FFFFh to EXT.
IMPORTANT
Note on Stack Area:
• With this product, a maximum 7 bytes of the user stack is consumed. Therefore, ensure the +7 bytes
maximum capacity used by the user program as the user stack area.
If the user stack does not have enough area, do not use areas which cannot be used as stack (SFR
area, RAM area which stores data, or ROM area) as a work area. Using areas like this is a cause
of user program crashes and destabilized emulator control.