User`s manual
Table Of Contents
- Cover
- Notes regarding these materials
- Contents
- Section 1 System Configuration
- Section 2 Connecting the Emulator to the User System
- 2.1 Connecting the Emulator to the User System
- 2.2 Connecting the Emulator to the User System by Using the EV-chip Unit
- 2.2.1 Connecting the EV-chip Unit to the Emulator
- 2.2.2 Connecting the E200F External Bus Trace Unit to the EV-chip Unit
- 2.2.3 Connecting the Probe Head to the EV-chip Unit
- 2.2.4 Connecting the E200F Emulation Memory Unit to the EV-chip Unit
- 2.2.5 Connecting the E200F External Bus Trace Unit, Emulation Memory Unit, and EV-chip Unit
- 2.2.6 Connecting the EV-chip Unit to the User System Interface Board
- 2.3 Connecting the Emulator to the User System by Using the H-UDI Port Connector
- 2.4 Installing the H-UDI Port Connector on the User System
- 2.5 Pin Assignments of the H-UDI Port Connector
- 2.6 Recommended Circuit between the H-UDI Port Connector and the MCU
- 2.7 Connecting the E200F External Bus Trace Unit with the User System
- 2.8 Installing the External Bus Trace Unit Connector
- 2.8.1 External Bus Trace Unit Connector Installed on the User System
- 2.8.2 Pin Assignments of the User System Connector
- 2.8.3 Recommended Foot Pattern
- 2.8.4 Restrictions on Component Installation
- 2.8.5 Pin Assignments of the External Bus Trace Unit Connector
- 2.8.6 Layout of the External Bus Trace Unit Connector
- 2.9 Connecting the External Bus Trace Unit to the User System
- 2.9.1 Connecting the E200F External Bus Trace Unit to the Emulator Main Unit
- 2.9.2 Connecting the E200F External Bus Trace Unit to the User System
- 2.9.3 Connecting the E200F Emulation Memory Unit to the Emulator Main Unit
- 2.9.4 Connecting the Emulation Memory Unit to the User System
- 2.9.5 Connecting the E200F External Bus Trace Unit, Emulation Memory Unit, and User System
- Section 3 Software Specifications when Using the SH7211
- 3.1 Differences between the SH7211 and the Emulator
- 3.2 Specific Functions for the Emulator when Using the SH7211
- 3.2.1 Event Condition Functions
- 3.2.2 Trace Functions
- 3.2.3 Notes on Using the JTAG (H-UDI) Clock (TCK) and AUD Clock (AUDCK)
- 3.2.4 Notes on Setting the [Breakpoint] Dialog Box
- 3.2.5 Notes on Setting the [Event Condition] Dialog Box and the BREAKCONDITION_ SET Command
- 3.2.6 Performance Measurement Function
- Section 4 User System Interface Circuits
- Colophon

68
Note: When [M-BUS] or [I-BUS] is selected, the following bus cycles will be traced.
• M-BUS: A bus cycle generated by the CPU is acquired.
• I-BUS: A bus cycle generated by the CPU or DMA is acquired.
(c) Software Trace Function
Note: This function can be supported with SuperH C/C++ compiler (manufactured by Renesas
Technology Corp.; including OEM and bundle products) V7.0 or later.
When a specific instruction is executed, the PC value at execution and the contents of one
general register are acquired by trace. Describe the Trace(x) function (x is a variable name) to
be compiled and linked beforehand. For details, refer to the SuperH
TM
RISC engine C/C++
Compiler, Assembler, Optimizing Linkage Editor User’s Manual.
When the load module is downloaded on the emulator and is executed while a software trace
function is valid, the PC value that has executed the Trace(x) function, the general register
value for x, and the source lines are displayed.
To activate the software trace function, select the [Software trace] check box in the [AUD
function] group box of the [Trace mode] page.
Notes on AUD Trace:
1. When the trace display is performed during user program execution, the mnemonics, operands,
or source is not displayed.
2. The AUD trace function outputs the differences between newly output branch source addresses
and previously output branch source addresses. The window trace function outputs the
differences between newly output addresses and previously output addresses. If the previous
branch source address is the same for the upper 16 bits, the lower 16 bits are output. If it
matches the upper 24 bits, the lower 8 bits are output. If it matches the upper 28 bits, the lower
4 bits are output.
The emulator regenerates the 32-bit address from these differences and displays it in the
[Trace] window. If the emulator cannot display the 32-bit address, it displays the difference
from the previously displayed 32-bit address.
3. If the 32-bit address cannot be displayed, the source line is not displayed.
4. In the emulator, when multiple loops are performed to reduce the number of AUD trace
displays, only the IP counts up.
5. In the emulator, the maximum number of trace displays is 262144 lines (131072 branches).
However, the maximum number of trace displays differs according to the AUD trace
information to be output. Therefore, the above pointers cannot always be acquired.
6. If a completion-type exception occurs during exception branch acquisition, the next address to
the address in which an exception occurs is acquired.










