E2, IE850A
5. Notes on Usage
R20UT4140EJ0300 Rev.3.00
Page 35 of 41
Oct.09.20
5.4.24 Cautionary points regarding external trigger input/output [E2]
•
When external trigger input or external trigger output functions are in use, access to memory during the
execution of a program, changes to event conditions, the reading of internal trace memory, and the display
of state indicators such as STOP are disabled.
•
When the software tracing (LPD output) function is not in use, breaks are not detectable during the 10-
µ
sec
period after a program has started to run.
5.4.25 Trace-full break [IE850A]
In external tracing, trace data are stored in the trace memory in the IE850A. The emulator requests a break in
execution by the target device before the trace memory becomes full (trace-full break). If the request is not
accepted immediately, the output of trace data may continue even after the trace memory is full and data will
thus be lost.
5.4.26 Cautionary point regarding hot plug-in connection
Allowing hot plug-in connection prevents usage of the following debugging functions.
•
Initializing RAM areas
•
Masking of pins
Accordingly, reading of the RAM areas before the user program has initialized them will lead to an ECC error.
Refer to section 5.3.4, Initialization of RAM areas.
5.4.27 Cautionary point regarding execution of the user program immediately after hot plug-in
connection
During execution of the user program until a break occurs due to a forced break or a CPU reset after hot plug-
in connection, only the debugging functions listed below are available.
•
Read or write access to the internal RAM area or peripheral I/O registers
•
Forced break
•
CPU reset
After the break, all debugging functions become available in the same way as for normal starting of the
program.
During hot plug-in connection, the EIPC and general-purpose registers are not initialized. Accordingly, reading
of these registers before the user program has initialized them will lead to an ECM error. Refer to section
5.3.9, Reading registers with undefined initial values and an ECM error.
5.4.28 Cautionary points regarding GTM debugging
•
If a debugger resets the device during GTM debugging, multiple resets will be internally applied and a
clock signal will temporarily be supplied to the GTM.
•
The debugger cannot access the GTM area before the clock signal is supplied to the GTM.
•
The debugging target is one instance of the MCS. To debug other instances implemented in the MCS, re-
connect the debugger.
•
The program counter of the MCS cannot be modified.
•
If a break occurs during GTM debugging, the value of the program counter of the MCS may be incorrect. In
such cases, re-connect the debugger since continued debugging is not possible.
