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
56
6. If a condition of which intervals are satisfied closely is set, no sequential condition will
be satisfied.
• Set the Event conditions, which are satisfied closely, by the program counter with
intervals of two or more instructions.
• After the Event condition has been matched by accessing data, set the event
condition by the program counter with intervals of 17 or more instructions.
7. If the settings of the Event condition or the sequential conditions are changed during
execution of the program, execution will be suspended. (The number of clock cycles to
be suspended during execution of the program is a maximum of about 102 bus clock
cycles (Bφ). If the bus clock (Bφ) is 66.6 MHz, the program will be suspended for 1.53
μs.)
8. If the settings of Event conditions or the sequential conditions are changed during
execution of the program, the emulator temporarily disables all Event conditions to
change the settings. During this period, no Event conditions will be satisfied.
9. If the break condition before executing an instruction is set to the instruction followed
by DIVU and DIVS, the factor for halting a break will be incorrect under the following
condition:
If a break occurs during execution of the above DIVU and DIVS instructions, the break
condition before executing an instruction, which has been set to the next instruction,
may be displayed as the factor for halting a break.
10. If the break conditions before and after executing instructions are set to the same
address, the factor for halting a break will be incorrectly displayed. The factor for
halting a break due to the break condition after executing an instruction will be
displayed even if a break is halted by the break condition before executing an
instruction.
11. Do not set the break condition after executing instructions and BREAKPOINT
(software break) to the same address.
12. When the emulator is being connected, the user break controller (UBC) function is not
available.