Renesas Network Card HS7630KCM02HE User Guide

SuperH Family E10A Emulator  
Additional Document for User’s Manual  
SH7630 E10A  
HS7630KCM02HE  
Renesas Microcomputer Development Environment System  
SuperH Family / SH7600 Series  
Specific Guide for the SH7630 E10A Emulator  
Rev.1.00  
2003.7.3  
 
Contents  
Section 1 Connecting the Emulator with the User System................................1  
1.1 Components of the Emulator ............................................................................................1  
1.2 Connecting the E10A Emulator with the User System .....................................................4  
1.3 Installing the H-UDI Port Connector on the User System ................................................5  
1.4 Pin Arrangement of the H-UDI Port Connector................................................................5  
1.5 Recommended Circuit between the H-UDI Port Connector and the MPU.......................8  
1.5.1 Recommended Circuit (36-Pin Type)..................................................................8  
1.5.2 Recommended Circuit (14-Pin Type)..................................................................10  
Section 2 Specifications of the SH7630 E10A Emulator’s Software................13  
2.1 Differences between the SH7630 and the Emulator .........................................................13  
2.2 Specific Functions for the SH7630 E10A Emulator .........................................................16  
2.2.1 Emulator Driver Selection ...................................................................................16  
2.2.2 Break Condition Functions ..................................................................................16  
2.2.3 Trace Functions....................................................................................................18  
2.2.4 Notes on Using the JTAG Clock (TCK) and AUD Clock (AUDCK) .................24  
2.2.5 Notes on Setting the [Breakpoint] Dialog Box ....................................................24  
2.2.6 Notes on Setting the [Break Condition] Dialog Box and  
BREAKCONDITION_SET Command ...............................................................25  
2.2.7 Notes on Setting the UBC_MODE Command.....................................................26  
2.2.8 Performance Measurement Function ...................................................................26  
i
 
ii  
 
Section 1 Connecting the Emulator with the User System  
1.1  
Components of the Emulator  
The SH7630 E10A emulator supports the SH7630. Table 1.1 lists the components of the emulator.  
1
 
Table 1.1 Components of the Emulator (HS7630KCM01H, HS7630KCM02H,  
HS7630KCI01H, or HS7630KCI02H)  
Classi-  
fication Component  
Quan-  
tity  
Appearance  
Remarks  
Hard-  
ware  
Card emulator  
1
HS7630KCM01H  
(PCMCIA: 14-pin type):  
PC  
PC  
Card  
Depth: 85.6 mm, Width: 54.0 mm,  
Height: 5.0 mm, Mass: 27.0 g  
(PCMCIA)  
or  
HS7630KCM02H  
(PCMCIA: 36-pin type):  
Depth: 85.6 mm, Width: 54.0 mm,  
Height: 5.0 mm, Mass: 28.0 g  
HS7630KCI01H  
(PCI: 14-pin type):  
Depth: 122.0 mm, Width: 96.0  
mm, Mass: 80.0 g  
(PCI)  
HS7630KCI02H  
(PCI: 36-pin type):  
Depth: 122.0 mm, Width: 96.0  
mm, Mass: 90.0 g  
User system interface  
cable  
1
HS7630KCM01H  
(PCMCIA: 14-pin type):  
Length: 80 cm, Mass: 45.0 g  
HS7630KCM02H  
(PCMCIA: 36-pin type):  
Length: 30 cm, Mass: 55.0 g  
HS7630KCI01H  
(PCI: 14-pin type):  
Length: 150 cm, Mass: 86.0 g  
HS7630KCI02H  
(PCI: 36-pin type):  
Length: 80 cm, Mass: 69.0 g  
Ferrite core  
(connected with the  
user interface cable)  
1
1
Countermeasure for EMI*  
(only for HS7630KCM02H and  
HS7630KCI02H)  
Soft-  
ware  
SH7630 E10A  
emulator setup  
program,  
HS7630KCM01SR,  
SH Family E10A  
Emulator User’s  
Manual, and  
HS0005KCM01HJ,  
HS0005KCM01HE,  
Specific Guide to the  
SH7630 E10A  
Emulator  
HS7630KCM02HJ, and  
HS7630KCM02HE  
(provided on a CD-R)  
Note: The EMI is an abbreviation of the Electrical Magnetic Interference.  
2
 
For EMI countermeasure, use the ferrite core by connecting the user interface cable.  
When the user interface cable is connected with the emulator or user system, connect the ferrite  
core in the user system as shown in figure 1.1.  
Host computer (PC with PC card slot)  
User system  
E10A emulator  
PC  
PC  
Card  
User system connector  
Ferrite core  
PC card slot  
User interface cable  
Figure 1.1 Connecting Ferrite Core  
3
 
1.2  
Connecting the E10A Emulator with the User System  
To connect the E10A emulator (hereinafter referred to as the emulator), the H-UDI port connector  
must be installed on the user system to connect the user system interface cable. When designing  
the user system, refer to the recommended circuit between the H-UDI port connector and the  
MCU. In addition, read the E10A emulator user's manual and hardware manual for the related  
device.  
Table 1.2 shows the type number of the E10A emulator, the corresponding connector type, and the  
use of AUD function.  
Table 1.2 Type Number, AUD Function, and Connector Type  
Type Number  
Connector  
AUD Function  
Available  
HS7630KCM02H, HS7630KCI02H  
HS7630KCM01H, HS7630KCI01H  
36-pin connector  
14-pin connector  
Not available  
The H-UDI port connector has the 36-pin and 14-pin types as described below. Use them  
according to the purpose of the usage.  
1. 36-pin type (with AUD function)  
The AUD trace function is supported. A large amount of trace information can be acquired in  
realtime. The E10A emulator supports the window trace function that memory access  
(memory access address or memory access data) in the specified range can be acquired by  
tracing.  
2. 14-pin type (without AUD function)  
The AUD trace function cannot be used because only the H-UDI function is supported. For  
tracing, only the internal trace function is supported. Since the 14-pin type connector is  
smaller than the 36-pin type (1/2.5), the area where the connector is installed on the user  
system can be reduced.  
4
 
1.3  
Installing the H-UDI Port Connector on the User System  
Table 1.3 shows the recommended H-UDI port connectors for the emulator.  
Table 1.3 Recommended H-UDI Port Connectors  
Connector  
Type Number  
Manufacturer  
Specifications  
Screw type  
36-pin connector DX10M-36S  
Hirose Electric Co., Ltd.  
DX10M-36SE,  
Lock-pin type  
DX10G1M-36SE  
14-pin connector 2514-6002  
Minnesota Mining &  
Manufacturing Ltd.  
14-pin straight type  
Note: When the 36-pin connector is used, do not connect any components under the H-UDI  
connector. When the 14-pin connector is used, do not install any components within 3 mm  
of the H-UDI port connector.  
1.4  
Pin Arrangement of the H-UDI Port Connector  
Figures 1.2 and 1.3 show the pin arrangement of the 36-pin and 14-pin H-UDI port connectors,  
respectively.  
Note: Note that the pin number assignment of the H-UDI port connector shown below differs  
from that of the connector manufacturer.  
5
 
Pin  
No.  
Pin  
No.  
SH7630  
Pin No.  
Input/  
Output  
Input/  
Output  
SH7630  
Pin No.  
Note  
*1  
*1  
Signal  
Note  
Signal  
TMS  
1
AUDCK  
Output  
Output  
85  
19  
20  
Input  
Input  
28  
2
3
4
GND  
GND  
*2  
AUDATA0  
GND  
86  
21  
22  
/TRST  
GND  
24  
5
6
AUDATA1  
GND  
Output  
Output  
Output  
87  
90  
91  
23  
24  
TDI  
Input  
26  
25  
7
GND  
7
8
AUDATA2  
GND  
25  
26  
TDO  
GND  
Output  
*2  
9
AUDATA3  
GND  
27  
28  
/ASEBRKAK Output  
GND  
10  
*2  
11  
12  
/AUDSYNC  
GND  
Output  
92  
29  
30  
NC  
Pulled-up  
User reset  
GND  
*2  
13  
14  
15  
16  
NC  
31  
32  
/RESETP  
GND  
Output  
Output  
141  
GND  
NC  
*3  
33  
34  
GND  
GND  
GND  
17  
18  
TCK  
Input  
27  
35  
36  
NC  
GND  
GND  
Notes:  
1. Input to or output from the user system.  
2. The slash (/) means that the signal is active-low.  
3. The emulator monitors the GND signal of the user system and detects  
whether or not the user system is connected.  
Edge of the board  
(connected to the connector)  
H-UDI port connector  
(top view)  
4
+0.2  
0
2
+0.1  
0
36  
φ
2.8  
φ
0.7  
(Pin 1 mark)  
3
35  
1
1.27  
M2.6 x 0.45  
4.09  
21.59  
37.61  
43.51  
: Pattern inhibited area  
H-UDI port connector (top view)  
H-UDI port connector (front view)  
Unit: mm  
Figure 1.2 Pin Arrangement of the H-UDI Port Connector (36 Pins)  
6
 
Input/  
Output*1  
SH7630 Pin No. Note  
Pin No. Signal  
1
2*2  
TCK  
Input  
27  
24  
25  
7
/TRST  
TDO  
Input  
3
Output  
4*2  
5
/ASEBRKAK Output  
TMS  
Input  
28  
26  
141  
6
TDI  
Input  
7*2  
11  
/RESETP  
Not  
Output  
Pulled-up  
connected  
8 to 10 GND  
12 to 13  
14*3  
GND  
Output  
Notes:  
1. Input to or output from the user system.  
2. The slash (/) means that the signal is active-low.  
3. The emulator monitors the GND signal of the user system  
and detects whether the user system is connected or not.  
Pin 1 mark  
H-UDI port connector (top view)  
25.0  
23.0  
6 x 2.54 = 15.24  
H-UDI port connector  
(top view)  
(2.54)  
Pin 8  
Pin 1  
Pin 14  
Pin 7  
0.45  
Pin 1 mark  
Unit: mm  
Figure 1.3 Pin Arrangement of the H-UDI Port Connector (14 Pins)  
7
 
1.5  
Recommended Circuit between the H-UDI Port Connector and the  
MPU  
1.5.1  
Recommended Circuit (36-Pin Type)  
Figure 1.4 shows a recommended circuit between the H-UDI port connector (36 pins) and the  
MPU.  
Notes: 1. Do not connect anything to the N.C. pin of the H-UDI port connector.  
2. The processing of the /ASEMD0 pin differs depending on whether the emulator is used  
or not. As the emulator does not control this pin, it must be controlled by a switch on  
the board.  
(1)  
(2)  
When the emulator is used: /ASEMD0 = low (ASE mode)  
When the emulator is not used: /ASEMD0 = high (normal mode)  
3. The reset signal in the user system is input to the /RESETP pin of the MPU. Connect  
this signal to the H-UDI port connector as the output from the user system.  
4. When a joined resistance is used for pull-up, it may be affected by a noise. Separate  
TCK from other resistances.  
5. When the emulator is in use, pin 29 of the H-UDI connector must be pulled up by a  
resistance of several kilo-ohms.  
6. The pattern between the H-UDI connector and the MPU must be as short as possible.  
Do not connect the signal lines to other components on the board.  
7. The resistance values shown in figure 1.4 are recommended.  
8. For the pin processing in cases where the emulator is not used, refer to the hardware  
manual of the related device.  
8
 
VccQ (3.3 V)  
VccQ (3.3 V)  
H-UDI port connector  
(36-pin type)  
SH7630  
AUDCK  
4.7 k  
4.7 kΩ  
1
2
GND  
GND  
GND  
AUDCK  
AUDATA0  
AUDATA1  
4
3
5
AUDATA0  
AUDATA1  
6
8
7
GND AUDATA2  
GND AUDATA3  
AUDATA2  
AUDATA3  
AUDSYNC  
9
10  
12  
11  
GND  
GND  
GND  
GND  
GND  
GND  
GND  
GND  
GND  
GND  
GND  
GND  
GND  
AUDSYNC  
N.C.  
13  
15  
17  
19  
21  
14  
16  
18  
20  
N.C.  
TCK  
TMS  
TCK  
TMS  
22  
TRST  
TRST  
23  
25  
27  
24  
26  
28  
TDI  
TDO  
TDI  
TDO  
ASEBRKAK  
NC  
ASEBRKAK  
29  
31  
33  
35  
30  
32  
34  
36  
RESET  
RESETP  
ASEMD0  
GND  
N.C.  
Reset signal  
1 kΩ  
Figure 1.4 Recommended Circuit for Connection between the H-UDI Port Connector and  
MPU (36-Pin Type)  
9
 
1.5.2  
Recommended Circuit (14-Pin Type)  
Figure 1.5 shows a recommended circuit between the H-UDI port connector and the MPU.  
Notes: 1. Do not connect anything to the N.C. pin of the H-UDI port connector.  
2. The processing of the /ASEMD0 pin differs depending on whether the emulator is  
used or not. As the emulator does not control this pin, it must be controlled by a  
switch on the board.  
(1) When the emulator is used: /ASEMD0 = low (ASE mode)  
(2) When the emulator is not used: /ASEMD0 = high (normal mode)  
3. The reset signal in the user system is input to the /RESETP pin of the MPU. Connect  
this signal to the H-UDI port connector as the output from the user system.  
4. When a joined resistance is used for pull-up, it may be affected by a noise. Separate  
TCK from other resistances.  
5. When the emulator is in use, pin 11 of the H-UDI connector must be pulled up by a  
resistance of several kilo-ohms.  
6. The pattern between the H-UDI connector and the MPU must be as short as possible.  
Do not connect the signal lines to other components on the board.  
7. The resistance values shown in figure 1.5 are recommended.  
8. For the pin processing in cases where the emulator is not used, refer to the hardware  
manual of the related device.  
10  
 
VccQ (3.3 V)  
VccQ (3.3 V)  
H-UDI port connector  
(14-pin type)  
4.7 k  
4.7 kΩ  
SH7630  
1
8
TCK  
TCK  
GND  
GND  
GND  
9
2
3
TRST  
TRST  
TDO  
10  
TDO  
ASEBRKAK  
TMS  
4
5
6
ASEBRKAK  
TMS  
12  
13  
14  
GND  
GND  
GND  
TDI  
TDI  
7
RESET  
NC  
RESETP  
11  
Reset signal  
1 kΩ  
ASEMD0  
Figure 1.5 Recommended Circuit for Connection between the H-UDI Port Connector and  
MPU (14-Pin Type)  
11  
 
12  
 
Section 2 Specifications of the SH7630 E10A Emulator’s  
Software  
2.1  
Differences between the SH7630 and the Emulator  
When the emulator system is initiated, it initializes the general registers and part of the control  
registers as shown in table 2.1. The initial values of the actual SH7630 registers are undefined.  
Table 2.1 Register Initial Values at Emulator Power-On  
Register  
Emulator at Power-on  
H'00000000  
H'A0000000  
H'00000000  
H'A0000000  
H'700000F0  
H'00000000  
H'00000000  
H'00000000  
H'00000000  
H'00000000  
H'00000000  
H'000000F0  
R0 to R14  
R15 (SP)  
R0_BANK to R7_BANK  
PC  
SR  
GBR  
VBR  
MACH  
MACL  
PR  
SPC  
SSR  
The emulator uses the H-UDI; do not access the H-UDI.  
Low-Power States (Sleep, Software Standby, and Module Standby)  
For low-power consumption, the SH7630 has sleep, software standby, and module standby states.  
The sleep, software standby, and module standby states are switched using the SLEEP instruction.  
When the emulator is used, only the sleep state can be cleared with either the normal clearing  
function or with the [Stop] button, and a break will occur.  
Note: The memory must not be accessed or modified in sleep state.  
13  
 
Reset Signals  
The SH7630 reset signals are only valid during emulation started with clicking the GO or STEP-  
type button. If these signals are input from the user system in command input wait state, they are  
not sent to the SH7630.  
Note: Do not break the user program when the /RESETP and /WAIT signals are being low. A  
TIMEOUT error will occur. If the /WAIT signal is fixed to low during break, a  
TIMEOUT error will occur at memory access.  
Direct Memory Access Controller (DMAC)  
The DMAC operates even when the emulator is used. When a data transfer request is generated,  
the DMAC executes DMA transfer.  
Memory Access during User Program Execution  
When a memory is accessed from the memory window, etc. during user program execution, the  
user program is resumed after it has stopped in the E10A emulator to access the memory.  
Therefore, realtime emulation cannot be performed.  
The stopping time of the user program is as follows:  
Environment:  
Host computer: 650 MHz (Pentium® III)  
SH7630: 60 MHz  
JTAG clock: 3.75 MHz  
When a one-byte memory is read from the command-line window, the stopping time will be about  
20 ms.  
Memory Access during User Program Break  
The emulator can download the program for the flash memory area. Other memory write  
operations are enabled for the RAM area. Therefore, an operation such as memory write or  
BREAKPOINT should be set only for the RAM area.  
Cache Operation during User Program Break  
When cache is enabled, the emulator accesses the memory by the following methods:  
At memory write: Writes through the cache, then writes to the memory.  
At memory read: Does not change the cache write mode that has been set.  
Therefore, when memory read or write is performed during user program break, the cache state  
will be changed.  
14  
 
UBC  
When [User] is specified in the [UBC mode] list box in the [Configuration] dialog box, the UBC  
can be used in the user program.  
Do not use the UBC in the user program as it is used by the E10A emulator when [EML] is  
specified in the [UBC mode] list box in the [Configuration] dialog box.  
Loading Sessions  
Information in [JTAG clock] of the [Configuration] dialog box cannot be recovered by loading  
sessions. Thus the TCK value will be as follows:  
When HS7630KCI01H or HS7630KCI02H is used: TCK = 4.125 MHz  
When HS7630KCM01H or HS7630KCM02H is used: TCK = 3.75 MHz  
[IO] Window  
Display and modification  
Do not change values of the User Break Controller because it is used by the emulator.  
For each Watchdog Timer register, there are two registers to be separately used for write and  
read operations.  
Table 2.2 Watchdog Timer Register  
Register Name  
WTCSR(W)  
WTCNT(W)  
WTCSR(R)  
WTCNT(R)  
Usage  
Write  
Write  
Read  
Read  
Register  
Watchdog timer control/status register  
Watchdog timer counter  
Watchdog timer control/status register  
Watchdog timer counter  
The watchdog timer operates only when the user program is executed. Do not change the value  
of the frequency change register in the [IO] window or [Memory] window.  
The internal I/O registers can be accessed from the [IO] window. However, note the following  
when accessing the SDMR register of the bus-state controller. Before accessing the SDMR  
register, specify addresses to be accessed in the I/O-register definition file (SH7630.IO) and then  
activate the HEW. For details on I/O-register definition file, refer to the Hitachi Debugging  
Interface User's Manual. Note that, however, the E10A emulator does not support the bit-field  
function described in the Hitachi Debugging Interface User's Manual.  
Verify  
In the [IO] window, the verify function of the input value is disabled.  
15  
 
Illegal Instructions  
If illegal instructions are executed by STEP-type commands, the emulator cannot go to the next  
program counter.  
2.2  
Specific Functions for the SH7630 E10A Emulator  
The SH7630 E10A emulator does not support the following function:  
MMU-related functions (The SH7630 does not mount the MMU.)  
VPMAP-related command  
Virtual and Physical specification in the [Configuration] window  
Virtual and Physical specification on the command-line function  
Virtual and Physical specification in the [Breakpoint] window  
LDTLB instruction execution break function  
MEMORYAREA_SET command  
2.2.1  
Emulator Driver Selection  
Table 2.3 shows drivers which are selected in the [E10A Driver Details] dialog box.  
Table 2.3 Type Number and Driver  
Type Number  
Driver  
HS7630KCM01H  
HS7630KCM02H  
HS7630KCI01H  
HS7630KCI02H  
E10A PC Card Driver 7  
E10A PC Card Driver 8  
E10A PCI Card Driver 7  
E10A PCI Card Driver 8  
2.2.2  
Break Condition Functions  
In addition to BREAKPOINT functions, the emulator has Break Condition functions. Three types  
of conditions can be set under Break Condition 1, 2, 3. Table 2.4 lists these conditions of Break  
Condition.  
16  
 
Table 2.4 Types of Break Conditions  
Break Condition Type  
Description  
Address bus condition (Address)  
Breaks when the SH7630 address bus value or the program  
counter value matches the specified value.  
Data bus condition (Data)  
Breaks when the SH7630 data bus value matches the  
specified value. Byte, word, or longword can be specified as  
the access data size.  
Bus state condition  
(Bus State)  
There are two bus state condition settings:  
Read/Write condition: Breaks when the SH7630 RD or  
RDWR signal level matches the specified condition.  
Bus state condition: Breaks when the operating state in an  
SH7630 bus cycle matches the specified condition.  
Types of buses that can be specified are listed below.  
L-bus (CPU-ALL): Indicates an instruction fetch and data  
access, including a hit to the cache memory.  
L-bus (CPU-Data): Indicates a data access by the CPU,  
including a hit to the cache memory.  
I-bus (CPU.DMA): Indicates a CPU cycle when the  
cache memory is not hit, and a data access by the  
DMA.  
Internal I/O break condition  
Count  
Breaks when the SH7630 accesses the internal I/O.  
Breaks when the conditions set are satisfied the specified  
number of times.  
Note: When U-RAM is accessed from the P0 space, the I-bus must be selected, and when  
accessed from the P2 space, the L-bus must be selected. When cache fill cycle is acquired,  
the I-bus must be selected.  
17  
 
Table 2.5 lists the combinations of conditions that can be set under Break Condition 1, 2, 3.  
Table 2.5 Dialog Boxes for Setting Break Conditions  
Type  
Address Bus Data Bus  
Bus State  
Condition  
(Bus Status) (Count)  
Count  
Condition  
Condition  
(Address)  
Condition  
(Data)  
Internal  
Dialog Box  
I/O Break  
[Break Condition 1]  
dialog box  
O
O
X
O
O
O
X
O
X
[Break Condition 2]  
dialog box  
X
X
X
X
[Break Condition 3]  
dialog box  
X
O
Note: O: Can be set in the dialog box.  
X: Cannot be set in the dialog box.  
2.2.3  
Trace Functions  
The SH7630 E10A emulator supports the trace functions listed in table 2.6.  
Table 2.6 Trace Functions  
Function  
Internal Trace  
AUD Trace  
Supported  
Supported  
Supported  
Branch trace  
Supported (eight branches)  
Not supported  
Range memory access trace  
Software trace  
Not supported  
Table 2.7 shows the type numbers that the AUD function can be used.  
Table 2.7 Type Number and AUD Function  
Type Number  
AUD Function  
Not supported  
Supported  
HS7630KCM01H, HS7630KCI01H  
HS7630KCM02H, HS7630KCI02H  
18  
 
AUD Trace Functions: This function is operational when the AUD pin of the device is  
connected to the emulator. Table 2.8 shows the AUD trace acquisition mode that can be set in  
each trace function.  
Table 2.8 AUD Trace Acquisition Mode  
Type  
Mode  
Description  
Continuous  
trace occurs  
Realtime trace  
When the next branch occurs while the trace information is  
being output, the trace information being output is output but  
the next trace information is not output. The user program  
can be executed in realtime, but some trace information may  
be lost.  
Non realtime trace When the next branch occurs while the trace information is  
being output, the CPU stops operations until the information  
is output. The user program is not executed in realtime.  
Trace buffer  
full  
Trace continue  
This function overwrites the oldest trace information to store  
the latest trace information.  
Trace stop  
After the trace buffer becomes full, the trace information is no  
longer acquired. (The user program is continuously  
executed.)  
19  
 
To set the AUD trace acquisition mode, click the [Trace] window with the right mouse button and  
select [Setting] from the pop-up menu to display the [Acquisition] dialog box. The AUD trace  
acquisition mode can be set in the [AUD mode1] or [AUD mode2] group box in the [Trace mode]  
page of the [Acquisition] dialog box.  
Figure 2.1 [Trace mode] Page  
When the AUD trace function is used, select the [AUD function] radio button in the [Trace type]  
group box of the [Trace mode] page.  
20  
 
(a) Branch Trace Function  
The branch source and destination addresses and their source lines are displayed.  
Branch trace can be acquired by selecting the [Branch trace] check box in the [AUD function]  
group box of the [Trace mode] page.  
The branch type can be selected in the [AUD Branch trace] page.  
Figure 2.2 [AUD Branch trace] Page  
(b) Window Trace Function  
Memory access in the specified range can be acquired by trace.  
Two memory ranges can be specified for channels A and B. The read, write, or read/write  
cycle can be selected as the bus cycle for trace acquisition.  
[Setting Method]  
(i) Select the [Channel A] and [Channel B] check boxes in the [AUD function] group  
box of the [Trace mode] page. Each channel will become valid.  
(ii) Open the [Window trace] page and specify the bus cycle and memory range that are to be  
set for each channel.  
21  
 
Figure 2.3 [Window trace] Page  
Note: When the [L-bus] or [I-bus] radio button is selected, the following bus cycles will be  
traced.  
L-bus: A bus cycle generated by the CPU is acquired. A bus cycle is also acquired when  
the cache has been hit.  
I-bus: A bus cycle generated by the CPU or DMA is acquired. A bus cycle is not acquired  
when the cache has been hit. The address information acquired by the I-bus is 28 bits and  
the upper 4 bits are displayed as ‘*’. The source cannot be displayed in the [Trace]  
window.  
When U-RAM is accessed from the P0 space, the I-bus must be selected, and when  
accessed from the P2 space, the L-bus must be selected. When a cache fill cycle is  
acquired, I-bus must be selected.  
22  
 
(c) Software Trace Function  
Note: This function can be supported with SHC compiler V7.0 and 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 SHC manual.  
When the load module is loaded on the emulator and a valid software trace function is  
executed, 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 as 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 SH7630 E10A emulator, when multiple loops are performed to reduce the number of  
AUD trace displays, only the IP counts up.  
5. In the SH7630 E10A emulator, the maximum number of trace display pointers is as follows:  
When HS7630KCM02H is used: D'8191 to -0  
When HS7630KCI02H is used: D'32767 to -0  
However, the maximum number of trace display pointers differs according to the AUD trace  
information to be output. Therefore, the above pointers cannot be always acquired.  
6. When [User] is specified in the [UBC mode] list box in the [Configuration] window, the AUD  
trace is not acquired. In this case, exit the [Trace] window.  
7. When the branch information for the odd address is acquired, it may be displayed as the  
software trace.  
8. If a completion-type exception occurs during exception branch acquisition, the next address to  
the address in which an exception occurs is acquired.  
9. For the AUD non-realtime trace, the written access may be executed again. If this is a  
problem on the user system, do not use the non-realtime trace.  
23  
 
Internal Trace Function: This function is activated by selecting the [Internal trace] radio button  
in the [Trace type] group box of the [Trace mode] page. See figure 2.1, [Trace mode] Page. The  
internal trace functions are also activated by selecting each check box on the [Branch trace] page.  
Notes: 1. If an interrupt is generated at the program execution start or end, including a step  
execution, the emulator address may be acquired. In such a case, the following  
message will be displayed. Ignore this address because it is not a user program address.  
*** EML ***  
2. If a completion-type exception occurs during exception branch acquisition, the next  
address to the address in which an exception occurs is acquired.  
3. Trace information cannot be acquired for the following branch instructions:  
The BF and BT instructions whose displacement value is 0  
Branch to H'A0000000 by reset  
4. When [User] is specified in the [UBC mode] list box in the [Configuration] window,  
the internal trace is not acquired. In this case, exit the [Trace] window.  
2.2.4  
Notes on Using the JTAG Clock (TCK) and AUD Clock (AUDCK)  
The JTAG clock (TCK) and AUD clock (AUDCK), which can be set in the [Configuration]  
window, have notes as follows.  
Set the JTAG clock (TCK) frequency to less than the frequency of the SH7630 peripheral module  
clock (CKP).  
Set the AUD clock (AUDCK) frequency 50 MHz or below for PCMCIA and PCI cards.  
2.2.5  
Notes on Setting the [Breakpoint] Dialog Box  
1. When an odd address is set, the next lowest even address is used.  
2. A BREAKPOINT is accomplished by replacing instructions of the specified address.  
Accordingly, it can be set only to the internal RAM area. However, a BREAKPOINT cannot  
be set to the following addresses:  
An area other than CS0 to CS6 and the internal RAM  
An instruction in which Break Condition 2 is satisfied  
A slot instruction of a delayed branch instruction  
3. During step execution, a BREAKPOINT is disabled.  
4. Conditions set at Break Condition 2 are disabled when an instruction to which a  
BREAKPOINT has been set is executed. Do not set a BREAKPOINT to an instruction in  
which Break Condition 2 is satisfied.  
5. When execution resumes from the address where a BREAKPOINT is specified, single-step  
execution is performed at the address before execution resumes. Therefore, realtime operation  
cannot be performed.  
24  
 
6. When a BREAKPOINT is set to the slot instruction of a delayed branch instruction, the PC  
value becomes an illegal value. Accordingly, do not set a BREAKPOINT to the slot  
instruction of a delayed branch instruction.  
7. When a BREAKPOINT is set to the cacheable area, the cache block containing the  
BREAKPOINT address is filled immediately before and after user program execution.  
8. Note on DSP repeat loop:  
A BREAKPOINT is equal to a branch instruction. In some DSP repeat loops, branch  
instructions cannot be set. For these cases, do not set BREAKPOINTs. Refer to the hardware  
manual for details.  
9. If an address of a BREAKPOINT cannot be correctly set in the ROM or flash memory area, a  
mark ! will be displayed in the [BP] area of the address on the [Editor] or [Disassembly]  
window by refreshing the [Memory] window, etc. after Go execution. However, no break will  
occur at this address. When the program halts with the break condition, the mark ! disappears.  
2.2.6  
Notes on Setting the [Break Condition] Dialog Box and BREAKCONDITION_SET  
Command  
1. Break Condition 2 is disabled during step execution.  
2. Break Condition 2 is disabled when an instruction to which a BREAKPOINT has been set is  
executed. Accordingly, do not set a BREAKPOINT to an instruction which satisfies Break  
Condition 2.  
3. When a Break Condition is satisfied, emulation may stop after two or more instructions have  
been executed.  
4. If a PC break address condition is set to the slot instruction after a delayed branch instruction,  
user program execution cannot be terminated before the slot instruction execution; execution  
stops before the branch destination instruction.  
5. Break Condition 1,2 is used as the measurement range in the performance measurement  
function when [PA-1 start point] and [PA-1 end point] are displayed on the [Action] part in  
the [Break condition] sheet of the [Event] window. This applies when the Break Condition is  
displayed with the BREAKCONDITION_DISPLAY command in the command-line function.  
In this case, a break does not occur when Break Condition 1,2 is satisfied.  
6. Note that a break occurs with a break satisfaction condition by an instruction that has been  
cancelled due to the generation of an exception.  
7. Use the sequential break or count break with the L-bus condition. If such break is used with  
the I-bus condition, it will not operate correctly.  
8. A break will not occur with the execution counts specified on the execution of the multi-step  
instruction.  
25  
 
2.2.7  
Notes on Setting the UBC_MODE Command  
In the [Configuration] window, if [User] is set while the [UBC mode] list box has been set, the  
STEP-type commands that use Break Condition 2 for implementation cannot be used.  
2.2.8  
Performance Measurement Function  
The SH7630 E10A emulator supports the performance measurement function.  
1. Setting the performance measurement conditions  
To set the performance measurement conditions, use the [Performance Analysis] dialog box  
and the PERFORMANCE_SET command. When any line on the [Performance Analysis]  
window is clicked with the right mouse button, the popup menu is displayed and the  
[Performance Analysis] dialog box is displayed by selecting [Setting].  
Note: For the command line syntax, refer to the online help.  
Specifying the measurement start/end conditions  
The measurement start/end conditions are specified in [Mode] in the [Performance  
Analysis] dialog box. Three conditions can be set as shown in table 2.9.  
Table 2.9 Conditions Specified in [Mode]  
Item  
Description  
Normal break  
Measurement is started by executing a program and ended when a  
break condition is satisfied.  
Break Condition 1 -> 2  
Break Condition 2 -> 1  
Measurement is started from the satisfaction of the condition set in  
Break Condition 1 to the satisfaction of the condition set in Break  
Condition 2.  
Measurement is started from the satisfaction of the condition set in  
Break Condition 2 to the satisfaction of the condition set in Break  
Condition 1.  
26  
 
Figure 2.4 [Performance Analysis] Dialog Box  
Measurement range  
One of the following ranges can be specified. This depends on the item selected for [Mode]  
in the [Performance Analysis] dialog box.  
1. From the start to the end of the user program execution (When Normal Break is  
selected for [Mode])  
2. From the satisfaction of the condition set in Break Condition 1 to the satisfaction of the  
condition set in Break Condition 2 (When Break condition 1->2 is selected for  
[Mode])  
3. From the satisfaction of the condition set in Break Condition 2 to the satisfaction of the  
condition set in Break Condition 1 (When Break condition 2->1 is selected for  
[Mode])  
(In the second and third ranges, [PA-1 start point] and [PA-1 end point] are displayed on the  
[Action] part in the [Break condition] sheet of the [Event] window.)  
For measurement errors,  
The measured value includes errors.  
Error will occur before or after a break.  
Notes: 1. When the second and third ranges are specified, execute the user program after the  
measurement start condition is set to Break Condition 1 (or Break Condition 2) and the  
measurement end condition to Break Condition 2 (or Break Condition 1).  
27  
 
2. Step execution is not possible when Break condition 1->2 or Break condition 2->1 is  
selected for the PERFORMANCE_SET command or in [Mode] of the [Performance  
Analysis] dialog box.  
3. When Break condition 1->2 or Break condition 2->1 is selected in [Mode] of the  
[Performance Analysis] dialog box, specify one or more items for measurement.  
When there is no item, the error message “Measurement item does not have  
specification. Please set up a measurement item.” will be displayed. When no item is  
specified for the PERFORMANCE_SET command, the settings of Break condition 1  
->2 or Break condition 2->1 will be an error.  
Measurement item  
Items are measured with [Channel 1 to 4] in the [Performance Analysis] dialog box.  
Maximum four conditions can be specified at the same time. Table 2.10 shows the  
measurement items (Options in table 2.10 are parameters for <mode> of the  
PERFORMANCE_SET command. They are displayed for CONDITION in the  
[Performance Analysis] window).  
28  
 
Table 2.10 Measurement Item  
Selected Name  
Option  
None  
AC  
Disabled  
Elapsed time  
Number of execution states  
Branch instruction counts  
Number of execution instructions  
DSP-instruction execution counts  
VS  
BT  
I
DI (Devices incorporating the DSP function can  
only be measured.)  
Instruction/data conflict cycle  
Other conflict cycles than instruction/data  
Exception/interrupt counts  
MAC  
OC  
EA  
Data-TLB miss cycle  
MTS (Devices incorporating the MMU function  
can only be measured.)  
Instruction-TLB miss cycle  
ITS (Devices incorporating the MMU function  
can only be measured.)  
Interrupt counts  
INT  
BL1  
MD1  
IC  
Number of BL=1 instructions  
Number of MD=1 instructions  
Instruction cache-miss counts  
Data cache-miss counts  
Instruction fetch stall  
DC  
IF  
Data access stall  
DA  
Instruction cache-miss stall  
Data cache-miss stall  
Cacheable access stall  
X/Y-RAM access stall  
ICS  
DCS  
CS  
XYS (Devices incorporating the X/Y memory  
can only be measured.)  
URAM access stall  
US (Devices incorporating the U memory can  
only be measured.)  
Instruction/data access stall cycle  
MA  
Other access cycles than instruction/data  
Non-cacheable area access cycle  
Non-cacheable area instruction access cycle  
Non-cacheable area data access cycle  
Cacheable area access cycle  
NMA  
NCC  
NCI  
NCD  
CC  
29  
 
Table 2.10 Measurement Item (cont)  
Selected Name  
Option  
CIC  
Cacheable area instruction access cycle  
Cacheable area data access cycle  
Access counts other than instruction/data  
Non-cacheable area access counts  
Non-cacheable area instruction access counts  
Non-cacheable area data access counts  
Cacheable area access counts  
CDC  
NAM  
NCN  
NCIN  
NCDN  
CN  
Cacheable area instruction access counts  
Cacheable area data access counts  
CIN  
CDN  
Each measurement condition is also counted when conditions in table 2.11 are generated.  
Table 2.11 Performance Measurement Conditions to be Counted  
Measurement Condition  
Notes  
Cache-on counting  
Accessing the non-cacheable area is counted less than the actual  
number of cycles and counts. Accessing the cacheable and U  
memory areas is counted more than the actual number of cycles  
and counts.  
Branch count  
The counter value is incremented by 2. This means that two cycles  
are valid for one branch.  
Notes: 1. In the non-realtime trace mode of the AUD trace, normal counting cannot be performed  
because the generation state of the stall or the execution cycle is changed.  
2. Since the clock source of the counter is the CPU clock, counting also stops when the  
clock halts in the sleep mode.  
2. Displaying the measured result  
The measured result is displayed in the [Performance Analysis] window or the  
PERFORMANCE_ANALYSIS command with 32 bits.  
Note: If a performance counter overflows as a result of measurement, “********” will be  
displayed.  
3. Initializing the measured result  
To initialize the measured result, select [Initialize] from the popup menu in the [Performance  
Analysis] window or specify INIT with the PERFORMANCE_ANALYSIS command.  
30  
 
SuperHTM Family E10A Emulator  
Additional Document for User's Manual  
Specific Guide for the SH7630 E10A Emulator  
Publication Date: Rev.1.00, July 3, 2003  
Published by:  
Sales Strategic Planning Div.  
Renesas Technology Corp.  
Edited by:  
Technical Documentation & Information Department  
Renesas Kodaira Semiconductor Co., Ltd.  
2003 Renesas Technology Corp. All rights reserved. Printed in Japan.  
 
SuperH Family E10A Emulator  
Additional Document for User’s Manual  
REJ10B0015-0100H  
 

Pyramid Car Audio Car Speaker PW10290 User Guide
Q See Security Camera QSC13212D User Guide
Quantum Boiler GAS FIRED BOILERS User Guide
RCA CD Player RCU500 User Guide
Renesas Network Card R0E5212BACFG00 User Guide
Revolutionary Cooling Systems Portable Generator PVP1800 User Guide
Rival Gas Grill GR225 User Guide
Samsung Washer Dryer SW 903P User Guide
Sega Video Games 10086680263 User Guide
Sennheiser Headphones 502399 User Guide