Renesas Emulation Pod M37641T2-RPD-E, Руководство пользователя

Страница: 16 / 70

( 14 / 68 )
IMPORTANT
Note on Reading MCU Internal Resources:
• When the M37641T2-RPD-E is configured with the emulator debugger, the following results occur
when reading MCU internal resources (SFR and internal RAM area). In both cases, data is not
displayed correctly, but internal data is not affected at all.
(1) Real-time tracing
Data values in the MCU internal resource read cycle are not displayed correctly.
(2) Real-time RAM monitoring
Data values in the MCU internal resource read cycle are not displayed correctly.
Note on a Watch Point:
• When the M37641T2-RPD-E is configured with the emulator debugger, note the following if
specifying a watch point for MCU internal resources (SFR and internal RAM area).
Change the address specified as a watch point so as not to overlap the area set for the real-time RAM
monitor (you can check using the RRAM command of the M3T-PD38). When the address specified
as a watch point overlaps the area set for the real-time RAM monitor and the MCU internal
resources are read out, data will not be displayed correctly. The initial setting of the real-time RAM
monitor is 0000H to 03FFH.
Example:
Watch point ................................ 0000H
Real-time RAM monitor ............ 0010H to 040FH
Note on Event Breaks:
• With the emulator debugger you can not use data read out from the MCU internal resources (RAM
and SFR area) as a condition for event breaks.
Note on Software Breaks:
• Software breaks generate BRK interruptions by forcibly inserting a BRK instruction at "00h"
instead of a instruction code. Therefore, when you reference the result of a trace in bus mode, "00h"
is displayed as the instruction fetch address where a software break is set.