HS7144KCI02H Renesas Electronics America, HS7144KCI02H Datasheet
HS7144KCI02H
Specifications of HS7144KCI02H
Related parts for HS7144KCI02H
HS7144KCI02H Summary of contents
Page 1
To our customers, Old Company Name in Catalogs and Other Documents st On April 1 , 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the ...
Page 2
All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm ...
Page 3
To all our customers Regarding the change of names mentioned in the document, such as Hitachi Electric and Hitachi XX, to Renesas Technology Corp. The semiconductor operations of Mitsubishi Electric and Hitachi were transferred to Renesas Technology Corporation on April ...
Page 4
Cautions Keep safety first in your circuit designs! 1. Renesas Technology Corporation puts the maximum effort into making semiconductor products better and more reliable, but there is always the possibility that trouble may occur with them. Trouble with semiconductors may ...
Page 5
SH7144F E10A Emulator User’s Manual Renesas Microcomputer Development Environment System Rev.1.0 2002.08 ...
Page 6
Cautions 1. Hitachi neither warrants nor grants licenses of any rights of Hitachi’s or any third party’s patent, copyright, trademark, or other intellectual property rights for information contained in this document. Hitachi bears no responsibility for problems that may arise ...
Page 7
IMPORTANT INFORMATION • READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference. Do not attempt to use the emulator product until you fully understand its mechanism. Emulator Product: Throughout this document, ...
Page 8
LIMITED WARRANTY Hitachi warrants its emulator products to be manufactured in accordance with published specifications and free from defects in material and/or workmanship. Hitachi, at its option, will replace any emulator products returned intact to the factory, transportation charges prepaid, ...
Page 9
State Law: Some states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages, so the above limitation or exclusion may not apply to you. This warranty gives you specific legal rights, and ...
Page 10
READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference. Do not attempt to use the emulator product until you fully understand its mechanism. DEFINITION OF SIGNAL WORDS This is the ...
Page 11
Observe the precautions listed below. Failure will result in a FIRE HAZARD and will damage the user system and the emulator product or will result in PERSONAL INJURY. The USER PROGRAM will be LOST not ...
Page 12
Warnings on Emulator Usage Be sure to read and understand the warnings below before using this emulator. Note that these are the main warnings, not the complete list. Always switch OFF the host computer and user system before connecting or ...
Page 13
Thank you for purchasing the E10A emulator. READ section 2, Preparation before Use, of this User’s Manual before using the emulator product. Incorrect operation will damage the user system and the emulator product. This emulator is an efficient development tool ...
Page 14
Related Manuals: SuperH RISC Engine C/C++ Compiler, Assembler, Optimizing Linkage Editor User's Manual Hitachi Debugging Interface User's Manual Hardware Manual for each MCU Programming Manual for each MCU Notes: 1. IBM registered trademark of International Business Machines ...
Page 15
Section 1 Overview............................................................................................1 1.1 Warnings ........................................................................................................................... 3 1.2 Environmental Conditions ................................................................................................ 4 1.3 Components ...................................................................................................................... 6 Section 2 Preparation before Use.......................................................................7 2.1 Emulator Preparation ........................................................................................................ 7 2.2 HDI Installation ................................................................................................................ 8 2.2.1 Installing under Windows 2.2.2 Installing under Windows NT ...
Page 16
Executing [Step Out] Command .......................................................................... 48 3.13.3 Executing [Step Over] Command ........................................................................ 50 3.14 Forced Breaking of Program Executions .......................................................................... 52 3.15 Displaying Local Variables............................................................................................... 53 3.16 Break Function.................................................................................................................. 54 3.16.1 Software Break Function ..................................................................................... 54 3.17 Hardware Break ...
Page 17
DEVICE_TYPE: DE ........................................................................................... 135 5.2.12 GO_OPTION: GP................................................................................................ 136 5.2.13 JTAG_CLOCK: JCK ........................................................................................... 138 5.2.14 REFRESH: RF ..................................................................................................... 140 5.2.15 RESTART: RST .................................................................................................. 141 5.2.16 STATUS: STS ..................................................................................................... 142 5.3 RAM Monitor Commands ................................................................................................ 143 5.3.1 RAM_R: RR ........................................................................................................ 143 ...
Page 18
Figures Figure 1.1 System Configuration with the Emulator (PCMCIA Card Emulator Used)............. 1 Figure 1.2 System Configuration with the Emulator (PCI Card Emulator Used)...................... 2 Figure 2.1 Emulator Preparation Flow Chart............................................................................. 7 Figure 2.2 Inserting the PCMCIA Card Emulator in ...
Page 19
Figure 3.16 [Memory] Window................................................................................................. 42 Figure 3.17 [Instant Watch] Dialog Box.................................................................................... 43 Figure 3.18 [Watch] Window (Displaying the Array) ............................................................... 44 Figure 3.19 [Add Watch] Dialog Box........................................................................................ 44 Figure 3.20 [Watch] Window (Displaying a Variable).............................................................. 45 Figure 3.21 [Watch] Window ...
Page 20
... Figure 6.7 User System Interface Circuit of the AUD Pin (HS7144KCM02H) ........................ 155 Figure 6.8 User System Interface Circuit (HS7144KCI01H) .................................................... 156 Figure 6.9 User System Interface Circuit of the Hitachi-UDI Pin (HS7144KCI02H)............... 157 Figure 6.10 User System Interface Circuit of the AUD Pin (HS7144KCI02H) ........................ 158 viii ...
Page 21
Tables Table 1.1 Environmental Conditions...................................................................................... 4 Table 1.2 Operating Environments......................................................................................... 5 Table 2.1 Recommended Hitachi-UDI Port Connector.......................................................... 12 Table 2.2 Contents of the CD-R Directories .......................................................................... 25 Table 3.1 Tutorial Program: Configuration and Parts ............................................................ 27 Table 3.2 Step Option............................................................................................................. ...
Page 22
... Table 5.18 RAM_R Command Parameter ............................................................................... 143 Table 5.19 RAM_W Command Parameter .............................................................................. 145 Table 6.1 Components of the Emulator (HS7144KCM01H, HS7144KCM02H, HS7144KCI01H, or HS7144KCI02H)................................................................... 148 Table 6.2 Register Initial Values at Emulator Power-On ....................................................... 159 Table 6.3 Type Name and Driver ........................................................................................... 161 Table 6.4 Hardware Break Condition Specification Items..................................................... 161 Table 6 ...
Page 23
The E10A emulator (hereafter referred to as the emulator software and hardware development support tool for application systems using the microprocessor developed by Hitachi, Ltd. The PCMCIA card emulator or PCI card emulator (hereafter referred to as the ...
Page 24
Host computer (PC rith PCI slot) Figure 1.2 System Configuration with the Emulator (PCI Card Emulator Used) The emulator provides the following features: Excellent cost-performance card emulator Compactness and low price are implemented using the PCMCIA interface or the PCI ...
Page 25
Note: The AUD is an abbreviation of the Advanced User Debugger. Support for the AUD varies with the product. 1.1 Warnings READ the following warnings before using the emulator product. Incorrect operation will damage the user system and the emulator ...
Page 26
Environmental Conditions Observe the conditions listed in tables 1.1 and 1.2 when using the emulator. Failure will cause illegal operation in the user system, the emulator product, and the user program. Table 1.1 Environmental Conditions Item ...
Page 27
Table 1.2 Operating Environments Item Description Host computer Built-in Pentium or higher-performance CPU (200 MHz or higher recommended); IBM PC or compatible machine with the PCMCIA TYPE II slot or the PCI slot. OS Windows Minimum memory 32 Mbytes or ...
Page 28
Components Check all the components unpacking. For details on the E10A emulator components, refer to table 6.1, Components of the Emulator. If the components are not complete, contact a Hitachi sales agency. 6 ...
Page 29
Section 2 Preparation before Use 2.1 Emulator Preparation READ the reference sections shaded in figure 2.1 before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. Unpack the ...
Page 30
HDI Installation When the CD-R is inserted in the host computer’s CD-ROM drive, the HDI installation wizard is automatically activated (holding the Shift key down while the CD-R is inserted cancels this automatic activation). To run the installation wizard ...
Page 31
Installing under Windows NT (1) When the emulator is a PCI card: 1. Shut the operating system down and turn off the power to the host computer. 2. Insert the PCI-card emulator in a slot on the host computer. ...
Page 32
Installing under Windows (1) When the emulator is a PCI card: 1. Log-on with an administrator-level user name. 2. Install the HDI. (When a component is selected, be sure to select [PCI Card Driver].) 3. Shut the operating system ...
Page 33
Connecting the Card Emulator to the Host Computer Insert the card emulator, according to its type PCMCIA TYPE II slot or PCI slot on the host computer (figures 2.2 and 2.3). Note: When using Windows before putting ...
Page 34
When inserting the PCI-card emulator, note the following. Failure will damage the host computer. 1. Turn off the host computer. 2. Insert the emulator into the PCI slot in parallel. 3. Screw in the emulator after checking ...
Page 35
GND line User system GND connection Figure 2.4 Connecting the User System Interface Cable to the User System when the 14-pin Straight Type Connector is Used Notes connect the signals output from the Hitachi-UDI port connector, refer to ...
Page 36
Hitachi-UDI port TDI TDO JTAG port TDI TAP 14 SHxxxx Hitachi-UDI IC IC TDO TDI TDO TAP Boundary scan loop User system Figure 2.5 User System Example IC TDI TDO TAP TDI: Test data input TDO: Test data output TAP: ...
Page 37
System Check When the HDI program is executed, check that the emulator operates correctly according to the following procedure: 1. Check that the card emulator is inserted into the host computer. 2. Connect the user system interface cable to ...
Page 38
Power on the user system and select the setting to be used. Figure 2.7 [Select Session] Dialog Box 16 ...
Page 39
The [E10A Driver Details] dialog box is displayed. With the [Driver] combo box, select the driver to connect the HDI with the emulator. [Interface] displays the interface name of the PC interface board to be connected, and [Channel] displays ...
Page 40
Supply power to the user system. The subsequent procedures depend on the activation mode that was selected in step 5. 2.5.1 SHxxxx E10A Emulator Mode This mode is used for debugging in the emulator. 1. The HDI window is ...
Page 41
When "Link up" appears on the status bar, the user and emulator programs have been downloaded to the flash memory, and the HDI initialization is complete. Notes: 1. When the HDI is not linked up even if the above ...
Page 42
If the emulator is not initiated, the following dialog boxes shown in figures 2.14 through 2.17 will be displayed. (a) If the following dialog box is displayed, the user system may not be turned on or the RESET signal ...
Page 43
Figure 2.17 [INVALID ASERAM FIRMWARE!] Dialog Box 4. If the driver is not correctly connected, the following dialog box will be displayed. Figure 2.18 [Unable to restore the previous driver settings] Dialog Box The [E10A Driver Details] dialog box is ...
Page 44
After the [System Clock] window appears, input the system clock frequency. Figure 2.20 [System Clock] Dialog Box 3. When the [Load Program] window appears, specify a user program to be downloaded. Click the [Open] button to start downloading. Figure ...
Page 45
Ending the HDI Exit the HDI by using the following procedure: 1. Select [Exit] from the [File] menu to end the HDI. When the [Exit HDI] dialog box is displayed, click the [Yes] button. 2. Then, the [Save session] ...
Page 46
Uninstalling the HDI Follow this procedure to remove the installed HDI from the user’s host computer. 1. Open [Add/Remove Programs Properties] from the control panel. Select the HDI program from the list and click the [Add/Remove…] button. 2. The ...
Page 47
CD-R 2.8.1 Configuration of the CD-R The root directory of the CD-R contains a setup program for HDI installation. The folders contain the files and programs listed below. Table 2.2 Contents of the CD-R Directories Directory Name Contents Dlls ...
Page 48
26 ...
Page 49
Introduction The following describes the main functions of the HDI by using a tutorial program. The tutorial program is based on the C program that sorts ten random data items in ascending or descending order. The tutorial program performs ...
Page 50
Notes: 1. This program was created by using Hitachi Embedded Workshop (hereafter referred to as HEW) V1.2. Older versions of HEW will not open the workspace included with the package, so create a new workspace in such situations. 2. This ...
Page 51
Running the HDI To run the HDI, select the [HDI for E10A SHxxxx] -> [Hitachi Debugging Interface] from the [Start] menu. For the procedure of running the HDI, refer to section 2.5, System Check. Figure 3.1 [Start] Menu 29 ...
Page 52
Window The key functions of the HDI are described in section 4, Descriptions of Windows. Numbers in figure 3.2 indicate the following: 1. Menu bar: Gives the user access to the HDI commands for using the HDI debugger. ...
Page 53
Setting up the Emulator The clocks which are used for data communications must be set up on the emulator before the program is downloaded. JTAG clock (TCK) A communication clock for downloading data to the emulator except for acquiring ...
Page 54
Setting the [Configuration] Dialog Box Select [Configure Platform...] from the [Setup] menu to set a communication clock. The [Configuration] dialog box is displayed. Figure 3.3 [Configuration] Dialog Box Set any value in the [JTAG clock] combo boxes. The clock ...
Page 55
Downloading the Tutorial Program 3.6.1 Downloading the Tutorial Program Download the object program to be debugged. Select [Load Program...] from the [File] menu. The [Load Program] dialog box is displayed. Enter ‘[installation directory]\tutorial\tutorial\Debug\tutorial.abs’ in the [File name] list box ...
Page 56
Displaying the Source Program The HDI allows the user to debug a program on the source level. Select [Source...] from the [View] menu. The [Open] dialog box is displayed. Select the C source file that corresponds to the object ...
Page 57
Figure 3.7 [Source] Window (Displaying the Source Program) If necessary, select the [Font] option from the [Customise] submenu on the [Setup] menu to select a font and size that are legible. Initially the [Source] window shows the start of the ...
Page 58
Setting a Software Breakpoint A breakpoint is one of simple debugging functions. The [Source] window provides a very simple way of setting a software breakpoint at any point in a program. For example, to set a breakpoint at the ...
Page 59
Setting Registers Set values of the program counter and the stack pointer before executing the program. Select [Registers] from the [View] menu. The [Registers] window is displayed. Figure 3.9 [Registers] Window 37 ...
Page 60
To change the value of the program counter (PC), double-click the value area in the [Registers] window with the mouse. The following dialog box is then displayed, and the value can be changed. Set the program counter to H’00000800 in ...
Page 61
Executing the Program Execute the program as described in the following: To execute the program, select [Go] from the [Run] menu, or click the [Go] button on the toolbar. The program will be executed up to the breakpoint that ...
Page 62
The user can see the cause of the break that occurred last time in the [System Status] window. Select [Status] from the [View] menu. After the [System Status] window is displayed, open the [Platform] page, and check the status of ...
Page 63
Reviewing Breakpoints The user can see all the breakpoints set in the program in the [Breakpoints] window. Select [Breakpoints] from the [View] menu. The pop-up menu, opened by clicking the [Breakpoints] window with the right mouse button, also allows ...
Page 64
Viewing Memory When the label name is specified, the user can view the memory contents that the label has been registered in the [Memory] window. For example, to view the memory contents corresponding to the _main in word size: ...
Page 65
Watching Variables As the user steps through a program possible to watch that the values of variables used in the user program are changed. For example, set a watch on the long-type array a declared at the ...
Page 66
Click [Add Watch] button to add a variable to the [Watch] window. Figure 3.18 [Watch] Window (Displaying the Array) The user can also add a variable to the [Watch] window by specifying its name. Click the [Watch] window with the ...
Page 67
The [Watch] window will now also show the int-type variable max. Figure 3.20 [Watch] Window (Displaying a Variable) The user can double-click the + symbol to the left of any variable in the [Watch] window to watch the all elements ...
Page 68
Stepping Through a Program The HDI provides a range of step menu commands that allow efficient program debugging. Table 3.2 Step Option Menu Command Description Step In Executes each statement, including statements within functions. Step Over Executes a function ...
Page 69
Figure 3.23 [Source] Window (Step In) The highlighted line moves to the first statement of the sort function in the [Source] window. 47 ...
Page 70
Executing [Step Out] Command The [Step Out] steps out of the called function and stops at the next statement of the calling statement. To step out of the sort function, select [Step Out] from the [Run] menu, or click ...
Page 71
To execute two steps, use [Step In] twice. Figure 3.26 [HDI] Window (Step In The value of max displayed in the [Watch] window is changed to the maximum data value. Step In) 49 ...
Page 72
Executing [Step Over] Command The [Step Over] executes a function call as a single step and stops at the next statement of the main program. Using [Step Over], execute two steps to reach the change function statement. Figure 3.27 ...
Page 73
Figure 3.29 [HDI] Window (Step Over) 51 ...
Page 74
Forced Breaking of Program Executions The HDI can force a break in the execution of a program. To execute the remaining sections of the main function, select [Go] from the [Run] menu or the [Go] button on the toolbar. ...
Page 75
Displaying Local Variables The user can display local variables in a function using the [Locals] window. For example, we will examine the local variables in the main function, which declares five local variables min, and max. ...
Page 76
Break Function The emulator has software and hardware break functions. With the HDI, a software breakpoint can be set using the [Breakpoints] window, and a hardware break condition can be set using the [Break Condition] dialog box. An overview ...
Page 77
Click the [Breakpoints] window with the right mouse button and select [Add] from the pop-up menu. The [Break] dialog box is displayed. The [Point] page is displayed by default. Figure 3.34 [Point] Page ([Break] Dialog Box) 55 ...
Page 78
Click the [Add...] button to display the [Breakpoint] dialog box. Enter H'00003056 in the [Value] edit box. Figure 3.35 [Break Point] Dialog Box Click the [OK] button. 56 ...
Page 79
The [Break] dialog box is displayed. The address set in the value field of [Breakpoint] and the memory space are displayed. Figure 3.36 [Point] Page ([Break] Dialog Box) (After Software Breakpoint Setting) Click the [Close] button (or the [OK] button ...
Page 80
The software breakpoint that has been set is displayed in the [Breakpoints] window. Figure 3.37 [Breakpoints] Window (Software Breakpoint Setting) To stop the tutorial program at the breakpoint, the following procedure must be executed: Close the [Breakpoints] window. Set the ...
Page 81
Figure 3.38 [Source] Window at Execution Stop (Software Break) The [System Status] window displays the following contents. Figure 3.39 Displayed Contents of the [System Status] Window (Software Break) Note: The items that can be displayed in this window differ according ...
Page 82
Hardware Break Function A method is given below in which the address bus condition and the read cycles for the bus status condition are set under Break Condition 1 as hardware break conditions. Select [Breakpoint Window] from the [View] ...
Page 83
The [Break] dialog box is displayed. To set hardware break conditions, select [Condition] in the [Break] dialog box to display the [Condition] page. Figure 3.41 [Condition] Page ([Break] Dialog Box five breakpoints can be set independently for the ...
Page 84
Clear the [Don't Care] check box in the [Address] page. Select the [Address] radio button and enter H'00003046 as the value in the [Address] edit box. Figure 3.42 [Address] Page ([Break Condition 1] Dialog Box) Note: The items that can ...
Page 85
Select [Bus State] to display the [Bus State] page. Select the [Read] radio button in the [Read/Write] group box. Figure 3.43 [Bus State] Page ([Break Condition 1] Dialog Box) Note: The items that can be set in this window differ ...
Page 86
Click the [OK] button. The [Break] dialog box is displayed, and the first point display in the [Break Condition] list box changes from Empty to Enable. Figure 3.44 [Break] Dialog Box (After Hardware Break Condition Setting) Note: The number of ...
Page 87
The newly set hardware breakpoint is displayed in the [Breakpoints] window. With this setting, Break Condition 1 is displayed in [Type] in the [Breakpoints] window. This completes the setting of the Break Condition 1 hardware break condition. When the program ...
Page 88
The program runs and then stops at the condition specified under Break Condition 1. Figure 3.46 [Source] Window at Execution Stop (Break Condition 1) 66 ...
Page 89
The [System Status] window displays the following contents. Figure 3.47 Displayed Contents of the [System Status] Window (Break Condition 1) Note: The items that can be displayed in this window differ according to the product. For the items that can ...
Page 90
Setting the Sequential Break Condition The emulator has sequential break functions. When the hardware break conditions listed in table 3.3 are satisfied, program execution halts. This mode is called sequential break. Table 3.3 Sequential Break Conditions Break Condition Sequential ...
Page 91
Set hardware break conditions as follows: Break condition 1: When address H'0000305A is accessed in a read cycle, a break condition is satisfied. Break condition 2: When address H'00003046 is accessed in a read cycle, a break condition is satisfied. ...
Page 92
The program runs and then stops at the condition specified under Break Condition 1. Figure 3.50 [Source] Window at Execution Stop (Sequential Break) 70 ...
Page 93
The [System Status] window displays the following contents. Figure 3.51 Displayed Contents of the [System Status] Window (Sequential Break) Note: The items that can be displayed in this window differ according to the product. For the items that can be ...
Page 94
Trace Functions AUD Trace Function This is the large-capacity trace function that is enabled when the AUD pin is connected to the emulator. This function displays the branch destination addresses, mnemonics, operands, and source lines. When the branch destination ...
Page 95
AUD Trace Function This function is operational when the AUD pin of the MCU is connected to the emulator. The following is the procedure for setting the AUD trace function (this function need not to be set in an ...
Page 96
The following is an example of the display in the SH7144F E10A emulator. Figure 3.53 [Trace] Window in the SH7144F E10A Emulator 74 ...
Page 97
Stack Trace Function The emulator uses the stack information to display the name of the calling function for a function at which the program counter is currently pointing. Notes: 1. This function can be used only when the load ...
Page 98
Figure 3.55 shows that the position of the program counter is currently in the sort() function, and that the sort() function is called from the main() function. Notes the function is not deeply nested (lower than 10), the ...
Page 99
What Next? This tutorial has described the major features of the emulator and the use of the HDI. Sophisticated debugging can be carried out by using the emulation functions that the emulator offers. This provides for effective investigation of ...
Page 100
78 ...
Page 101
Section 4 Descriptions of Windows 4.1 HDI Windows HDI window menu bars and the corresponding pull-down menus are listed in table 4.1. Where a description of a menu is included in the Hitachi Debugging Interface User's Manual or in this ...
Page 102
Table 4.1 HDI Window Menus and Related Manual Entries (cont) Menu Bar Pull-Down Menu View Menu Breakpoints Command Line Disassembly... I/O Area Labels Locals Memory... Performance Analysis Profile-List Profile-tree Registers Source… Stack Trace Status Trace Watch Run Menu Reset CPU ...
Page 103
Table 4.1 HDI Window Menus and Related Manual Entries (cont) Menu Bar Pull-Down Menu Memory Menu Refresh Load Save Verify Test Fill Copy Compare Setup Menu Status bar Options Radix Customise Configure Platform… Window Menu Cascade Tile Arrange Icons Close ...
Page 104
Descriptions of Each Window This section describes each window. Figures in this section are used as examples. Each E10A emulator type has explanatory notes. Read section 6, SHxxxx E10A Emulator Specifications. 4.2.1 [Configuration] Dialog Box Function: This dialog box ...
Page 105
Description: The [Configuration] dialog box consists of the [General] page listed in table 4.2. Table 4.2 [Configuration] Dialog Box Page Page Name [General] Clicking the [OK] button sets the emulation conditions. If the [Cancel] button is clicked, this dialog box ...
Page 106
Page ([Configuration] Dialog Box) Function: This page sets the emulator operation conditions, displays the device name, sets the emulation mode, JTAG clock (TCK), flash memory synchronization, port D, and selects the driver. Window: Figure 4.2 [General] Page ([Configuration] ...
Page 107
Description: Table 4.3 [General] Page Options Option [Mode] combo box [Emulation mode] combo box [JTAG clock] combo box [Flash memory synchronization] combo box [Port D] combo box [Driver] group box [Change...] button Description Displays the device name. Selects the emulation ...
Page 108
Notes: 1. When using the sequential break function, set the corresponding hardware break conditions. 2. The range of frequencies that the AUD operates under is different according to the devices used. For details, refer to section 6.5.5, AUD Functions. 3. ...
Page 109
When a driver changed with the [Change..] button, the following message is displayed. When the [Yes] button is clicked, the [E10A Driver Details] dialog box is displayed. When the [No] button is clicked, the display returns to ...
Page 110
Driver Details] Dialog Box Function Function: When the [Change] button in the [Driver] group box is clicked on the [General] page in the [Configuration] dialog box, the [E10A Driver Details] dialog box is displayed. Figure 4.4 [E10A Driver ...
Page 111
Window Function: This window lists all break conditions that have been set. Window: Figure 4.5 [Breakpoints] Window 89 ...
Page 112
Description: The [Breakpoints] window displays breakpoint setting information. The items listed in the following tables are displayed. Table 4.5 [Breakpoints] Window Display Items Item Description [Enable] Displays whether the break condition is enabled or disabled. BREAKPOINT: Break Condition: o (If ...
Page 113
The pop-up menu, which is opened by clicking the right mouse button, can be used to set, change, and clear breakpoints, and to enable or disable break conditions. The pop-up menu functions are described in the following table. Table 4.6 ...
Page 114
Dialog Box Function: This dialog box displays the break condition settings. Window: 92 Figure 4.6 [Break] Dialog Box ...
Page 115
Description: The [Break] dialog box consists of the pages listed in table 4.7. Table 4.7 [Break] Dialog Box Pages Page Name [Point] [Condition] The dialog boxes which set or modify break conditions can be displayed from the pages above. Clicking ...
Page 116
Page ([Break] Dialog Box) Function: This page displays software breakpoint settings. In this page, software breakpoints can be set, changed, and cleared. Window: Figure 4.7 [Point] Page ([Break] Dialog Box) 94 ...
Page 117
Description: Table 4.8 [Point] Page Options Option Description [Break point] list box Lists the software breakpoints currently being set. The display contents are <breakpoint address>. [Add...] button Sets software breakpoints. Clicking this button displays the [Break Point] dialog box. [Edit...] ...
Page 118
Page ([Break] Dialog Box) Function: This page displays the Break Condition settings. These conditions can also be set or cleared in this page. Window: Figure 4.8 [Condition] Page ([Break] Dialog Box) Note: The number of hardware break conditions ...
Page 119
Description: Table 4.9 [Condition] Page Options Option Description [Break Condition] list Displays the Break Condition settings. box The display at system initiation is as follows: When conditions are set, Enable is displayed. When no conditions are set, Empty is displayed. ...
Page 120
Point] Dialog Box Function: This dialog box sets software breakpoints. Window: Note: The items that can be set in this window differ according to the product. For the settings for each product, refer to the online help. 98 ...
Page 121
Description: The [Break Point] dialog box consists only of the [Address] page. This dialog box sets address conditions and address areas. The [Address] page options are as follows: Table 4.10 [Address] Page Options Option [Value] edit box Clicking the [OK] ...
Page 122
Condition] Dialog Box Function: This dialog box sets hardware break conditions. Window: Figure 4.10 [Break Condition] Dialog Box Note: The items that can be set in this window differ according to the product. For the settings for each ...
Page 123
Description: The [Break Condition] dialog box consists of multiple pages. A condition to halt the program can be set in each page. Contents to be set by each page are described in section 4.2.6, [Break Condition] Dialog Box Pages. Clicking ...
Page 124
Condition] Dialog Box Pages Function: The [Break Condition] dialog box pages allow a number of hardware break conditions to be set. Some functions may not be supported by some types of emulators. The setting conditions may differ from ...
Page 125
Table 4.12 shows all the [Break Condition] dialog box pages. Table 4.12 [Break Condition] Dialog Box Pages Page Name Function [Address] Sets the address conditions of Break Condition 1 to Break Condition 4, and Break Condition R. [Data] Sets the ...
Page 126
Page ([Break Condition] Dialog Box) Function: This page sets the address bus conditions. Window: Figure 4.11 [Address] Page ([Break Condition 1] Dialog Box) Note: The items that can be set in this window differ according to the product. ...
Page 127
Description: Table 4.13 [Address] Page Options (BREAK_CONDITION1 to 4) Option Description [Only program fetched Sets a break before prefetched address execution as break address] radio button conditions. [Only program fetched Sets a break after prefetched address execution as break conditions. ...
Page 128
Page ([Break Condition] Dialog Box) Function: This page sets the data bus conditions. Window: Figure 4.12 [Data] Page ([Break Condition 1] Dialog Box) Note: The items that can be set in this window differ according to the product. ...
Page 129
Description: Table 4.16 [Data] Page Options Option [Don’t Care] check box [Value] edit box [Byte] radio button [Word] radio button [Long] radio button [Non user mask] radio button [User mask] radio button [Mask] edit box Note: This page is displayed ...
Page 130
State] Page ([Break Condition] Dialog Box) Function: This page sets bus state conditions and read/write cycle conditions. Window: Figure 4.13 [Bus State] Page ([Break Condition] Dialog Box) Note: The items that can be set in this window differ ...
Page 131
Description: Table 4.17 [Bus State] Page Options Group Box Option [Bus State] group [All] radio button box [Data] radio button [DTC] radio button [Read/Write] group [Read/Write] radio box button [Read] radio button [Write] radio button Note: This page is displayed ...
Page 132
Page ([Break Condition] Dialog Box) Function: This page sets the conditions for Break Condition 1. Window: Figure 4.14 [Count] Page ([Break Condition] Dialog Box) Table 4.18 [Count] Page Options Option [Don’t Care] check box Input area Note: Some ...
Page 133
Window Function: This window displays the trace buffer contents. Window: Note: The types of information and the number of branch instructions differ according to the product. For the settings for each product, refer to the online help. Figure ...
Page 134
Description: This window displays the trace buffer contents. The items listed in table 4.19 are displayed. Table 4.19 [Trace] Window Display Items Item Description [No.] Displays the number in ascending order as the trace stop point is 0 (signed decimal). ...
Page 135
Acquisition] Dialog Box Function: This dialog box sets trace acquisition conditions. When the [Acquisition] menu is selected from the pop-up menu, which is displayed by clicking the right mouse button in the [Trace] window, the [Trace Acquisition] dialog ...
Page 136
Mode] Page ([Trace Acquisition] Dialog Box) Function: This page sets the conditions for trace mode. Window: Figure 4.16 [Trace mode] Page ([Trace Acquisition] Dialog Box) Note: This function differs according to the product. For the specifications of each ...
Page 137
Status] Window Function: This window lists information, such as conditions that have been set to the emulator and execution results. Window: Note: The items that can be displayed in this window differ according to the product. For the ...
Page 138
The items listed in the following table are displayed in the [System Status] window. Table 4.21 [System Status] Window Display Items Page Item [Session] Target System Session Name Program Name [Platform] Connected To CPU Run status Cause of last break ...
Page 139
Section 5 Command-line Functions 5.1 Table and Symbol Description This section describes the format used in section 5.2, Command Descriptions. The descriptions of some commands are given over two or more pages. 5.1.1 Format The input format for each command ...
Page 140
Examples These are actual input examples. For commands whose execution results in a specific display output, an example of the display is given. 5.1.4 Related Items Related E10A HDI commands (abbreviations) and dialog boxes are shown. (Refer to section ...
Page 141
Command Descriptions The command list of the E10A emulator is shown below. Table 5.1 E10A HDI Commands No. Command 1 AUD_MODE 2 AUD_TRACE 3 BREAKCONDITION_ CLEAR 4 BREAKCONDITION_ DISPLAY 5 BREAKCONDITION_ ENABLE 6 BREAKCONDITION_ SET 7 BREAKPOINT 8 BREAKPOINT_CLEAR ...
Page 142
AUD_MODE:AUM Description: Displays AUD trace acquisition conditions. Format: aum [<option1>] <option1> = full<full> Table 5.2 AUD_MODE Command Parameter Parameter Type <full> Keyword Note: When <option1> is omitted, the current setting conditions are displayed. Note: The parameters for this command ...
Page 143
Examples: To set continue option: > aum full c (RET) To display settings: > aum (RET) mode = Realtime trace, continue Related Item: [Trace Acquisition] dialog box 121 ...
Page 144
AUD_TRACE:AUT Description: Displays the trace information. Format: aut [<option1>] [<option2>] <option1> = start<start_pointer> <option2> = end<end_pointer> Table 5.3 AUD_TRACE Command Parameter Parameter Type <start_pointer> Numerical value <end_pointer> Numerical value Notes the PCMCIA card emulator, –D’16383 to D’0 ...
Page 145
Example: To display trace information according to the information acquired during user program execution: > AUD_TRACE (RET) IP -D’xxxxxx (a) (a) Instruction pointer (signed decimal) (b) Types of branch destination DESTINATION: Branch destination (c) Address of instruction word (d) Instruction ...
Page 146
BREAKCONDITION_CLEAR: BCC Description: Clears hardware breakpoints that have been set. Format: bcc [<channel>] <channel> = channel <channel_number> Table 5.4 BREAKCONDITION_CLEAR Command Parameter Parameter Type <channel number> Numerical value Note: When <channel> is omitted, all hardware breakpoints that have been ...
Page 147
BREAKCONDITION_DISPLAY: BCD Description: Displays hardware breakpoints that have been set. The display contents include a hardware breakpoint channel number, enable or disable of the setting, and setting conditions. Format: bcd [<channel>] <channel> = channel <channel_number> Table 5.5 BREAKCONDITION_DISPLAY Command ...
Page 148
BREAKCONDITION_ENABLE: BCE Description: Enables or disables hardware breakpoints that have been set. Format: bce [<channel>] <mode> <channel> = channel <channel_number> Table 5.6 BREAKCONDITION_ENABLE Command Parameters Parameter Type <channel_number> Numerical value <mode> Keyword Note: When <channel> is omitted, all hardware ...
Page 149
BREAKCONDITION_SET: BCS Description: Sets hardware breakpoints. Note: The function will differ according to the devices used. For functions of each emulator product, refer to section 6.5.2, Hardware Break Functions. Format: bcs <channel> <option> [<option> ... ] <channel> = channel ...
Page 150
Table 5.7 BREAKCONDITION_SET Command Parameters Parameter Type <channel_number> Numerical value <address> Numerical value <addrcycle> Keyword <maskdata> Character string <data> Numerical value 128 Description Hardware break condition channel number Specifiable options change depending on the channel number. For details, refer to ...
Page 151
Table 5.7 BREAKCONDITION_SET Command Parameters (cont) Parameter Type <datawidth> Keyword <r/w> Keyword <access> Keyword <count> Numerical value Note: The parameters for this command differ according to the product. For the specifications of each product, refer to the online help. Description ...
Page 152
Examples: To set the following conditions for channel 1 hardware breakpoint: <addropt> item: An address bus value of H'1000, <dataopt> item: D0 bit of the byte access data is 0, <r/wopt> item: write cycle. > bcs channel 1 address H'1000 ...
Page 153
BREAKPOINT: BP Description: Sets software breakpoints. Note: The function will differ according to the devices used. Format: bp <address> Table 5.8 BREAKPOINT Command Parameters Parameter Type <address> Numerical value Note: The parameters for this command differ according to the ...
Page 154
BREAKPOINT_CLEAR: BC Description: Clears software breakpoints that have been set. Format: bc [<address>] Table 5.9 BREAKPOINT_CLEAR Command Parameters Parameter Type <address> Numerical value Notes: When no parameters are set, all software breakpoints are cleared. Note: The parameters for this ...
Page 155
BREAKPOINT_DISPLAY: BD Description: Displays software breakpoints that have been set. Format: bd Table 5.10 BREAKPOINT_DISPLAY Command Parameter Parameter Type None Example: To display the software breakpoints that have been set: > bd (RET) H'00000110 enable H'0000011c disable H'00000250 enable ...
Page 156
BREAKPOINT_ENABLE: BE Description: Enables or disables software breakpoints that have been set. Format: be <address> <mode> Table 5.11 BREAKPOINT_ENABLE Command Parameters Parameter Type <address> Numerical value <mode> Keyword Examples: To enable a software breakpoint at address H'1002: > be ...
Page 157
DEVICE_TYPE: DE Description: Displays the currently selected device. Format: de Table 5.12 DEVICE_TYPE Command Parameter Parameter Type None Example: To display the currently selected device: > de (RET) Current device = SHxxxx Description 135 ...
Page 158
GO_OPTION: GP Description: Displays or sets the emulation mode. Format: Displays emulation mode. gp Sets emulation mode. gp <eml_opt> <eml_opt> = eml_mode <eml_mode> Table 5.13 GO_OPTION Command Parameter Parameter Type <eml_mode> Keyword 136 Description Specifies the emulation mode. normal: ...
Page 159
Examples: To display the currently set emulation mode for user program execution: > gp (RET) Emulator execution mode = Sequential break Condition 2-1 To set the normal emulation mode for user program execution: > gp eml_mode normal (RET) Notes: 1. ...
Page 160
JTAG_CLOCK: JCK Description: Displays or sets the JTAG clock (TCK) frequency. Format: Displays the JTAG clock (TCK) frequency. jck Sets the JTAG clock (TCK) frequency. jck <jck_opt> Table 5.14 JTAG_CLOCK Command Parameter Parameter Type <jck_opt> Numerical value Note: The ...
Page 161
Examples: (when PCMCIA used): To set the JTAG clock (TCK) frequency: > jck 15 (RET) JTAG Clock 15MHz To display the JTAG clock (TCK) frequency: > jck (RET) JTAG Clock 15MHz (when PCI used): To set the JTAG clock (TCK) ...
Page 162
REFRESH: RF Description: Updates the HDI memory information. Format: rf Table 5.15 REFRESH Command Parameter Parameter Type None Example: To update the HDI memory information: > rf (RET) 140 Description ...
Page 163
RESTART: RST Description: Restarts the emulator. The settings of breakpoints or trace acquisition conditions are not reset here. Format: rst Table 5.16 RESTART Command Parameter Parameter Type None Example: To restart the emulator: > rst (RET) Description 141 ...
Page 164
STATUS: STS Description: Displays status information of the emulator. Format: sts Table 5.17 STATUS Command Parameter Parameter Type None Example: To display status information of the emulator: > sts (RET) Emulator Status Connected to: CPU Run status Cause of ...
Page 165
RAM Monitor Commands 5.3.1 RAM_R: RR Description: Displays the specified address contents on the status bar during user program execution. The memory can be read by using the RAM monitor function (a maximum of three addresses are displayed). Format: ...
Page 166
Examples: To set the address to be displayed on the status bar: >rr address 00000100 size B address 00000102 size L To display the current setting address: > rr (RET) address 00000100 size B address 00000102 size L To clear ...
Page 167
RAM_W: RW Description: Writes the specified contents in the specified address to the memory. Memory can be written by using the RAM monitor function (a maximum of three addresses are written). Format: RW <option1> <option2> [<option3>] [<option1> <option2> [<option3>]] ...
Page 168
146 ...
Page 169
Section 6 SH7144F E10A Emulator Specifications 6.1 Overview of the SH7144F E10A Emulator In the SH7144F E10A emulator, the SH7144F enables realtime emulation. In addition, realtime data tuning with the AUD function is also enabled. The supported operating modes are ...
Page 170
... Table 6.1 Components of the Emulator (HS7144KCM01H, HS7144KCM02H, HS7144KCI01H, or HS7144KCI02H) Classi- fication Component Hard- Card emulator ware (HS7144KCM01H, HS7144KCM02H, HS7144KCI01H, or HS7144KCI02H) User system interface cable Ferrite core (connected with the user interface cable) Soft- SH7144F E10A ware emulator setup program, SH7144F E10A Emulator User’ ...
Page 171
... In the HS7144KCM02H and HS7144KCI02H, 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 6.1. Host computer (PC with PC card slot) ...
Page 172
Pin Arrangement of the Hitachi-UDI Port Connector Figure 6.2 shows the pin arrangement of the Hitachi-UDI port connector (14 pins). Note that the pin number assignment of the Hitachi-UDI differs from that of the connector manufacturer. Hitachi-UDI Pin 1 ...
Page 173
Figure 6.3 shows the pin arrangement of the Hitachi-UDI port connector (36 pins). Hitachi-UDI port connector (Pin 1 mark) Pin Input/ SH7144F SH7145F No. Signal *1 Output Pin No. Pin No.* AUDCK I/O 53 109 1 2 GND 60 116 ...
Page 174
Notes: 1. Handling of the TCK, TMS, TDI, TDO, /TRST, /ASEBRKAK, and DBGMD pins depends on the use conditions of the Hitachi-UDI as follows: (a) When the user system is used by connecting the emulator, the TCK, TMS, TDI, TDO, ...
Page 175
User System Interface Circuit The emulator is connected to the user system via the user interface cable. Figure 6.5 shows the user system interface circuit of the emulator (HS7144KCM01H). JTAG controller (EPF6016ATC144-2) TDI TCK TMS TDO TRST URESET BRK ...
Page 176
The user system interface circuits of the emulator (HS7144KCM02H) are shown. Figures 6.6 and 6.7 show the circuits of the Hitachi-UDI pin and AUD pin, respectively. JTAG controller (EPF6016ATC144-2) TDI TCK TMS TDO TRST URESET ASEBRKAK Figure 6.6 User System ...
Page 177
AUD logic circuit (EPF6024ATC144-2) AUDATA[3:0] AUDSYNC AUDRST AUDMD CLKIN AUDCK CLKOUT Figure 6.7 User System Interface Circuit of the AUD Pin (HS7144KCM02H) 3Vcc 10 k 3Vcc 10 k 3Vcc 74LVT125 user system ...
Page 178
Figure 6.8 shows the user system interface circuit of the emulator (HS7144KCI01H). JTAG controller (EPF10K10QC208-3) TDI TCK TMS TDO TRST URESET BRK ACK Figure 6.8 User System Interface Circuit (HS7144KCI01H) 156 74LVT244 4 74LVT244 4 ...
Page 179
... The user system interface circuits of the emulator (HS7144KCI02H) are shown. Figures 6.9 and 6.10 show the circuits of the Hitachi-UDI pin and AUD pin, respectively. JTAG controller (EPF10K10QC208-3) TDI TCK TMS TDO TRST URESET BRK ACK Figure 6.9 User System Interface Circuit of the Hitachi-UDI Pin (HS7144KCI02H) 74LVT244 4 ...
Page 180
... AUD logic circuit (EPF10K10QC208-3) AUDATA_I[3:0] AUDATA_O[3:0] AUDI AUDO AUDRST AUDMD CLKOUT CLKIN Figure 6.10 User System Interface Circuit of the AUD Pin (HS7144KCI02H) 158 74LVT244 4 74LVT125 A Y 74LVT244 4 74LVT125 A Y 74LVT125 A Y 74LVT125 A Y CDC351 4 74LVT125 user system 3Vcc AUDATA[3:0] 3Vcc AUDSYNC ...
Page 181
... H’FFFF861E) nor the RAME bit the SYSCR register (address H’FFFF8618), since doing so may prevent the emulator from operating correctly. 2. When the HS7144KCM02H or HS7144KCI02H is used, do not set the following bits to 0: the MSTP3 bit in the MSTCR2 register (address H’FFFF861E) and the AUDSRST bit in the SYSCR register (address H’FFFF8618). The AUD function cannot be used ...
Page 182
RESET Signal (/RES) The RESET signal can be accepted during user program break, when the peripheral modules are reset. Since the PC, SR, and SP registers are not initialized, reset them and execute the GO command when the user program ...
Page 183
... Table 6.3 shows drivers which can be selected in the [E10A Driver Details] dialog box. Table 6.3 Type Name and Driver Type Name HS7144KCM01H HS7144KCM02H HS7144KCI01H HS7144KCI02H 6.5.2 Hardware Break Functions The emulator can set hardware break conditions. Table 6.4 lists these hardware break conditions. Table 6.4 Hardware Break Condition Specification Items Items ...
Page 184
Table 6.5 lists the combinations of conditions that can be set in the [Break Condition 1] dialog box. Table 6.5 Conditions Set in the [Break Condition] Dialog Box Type Address Bus Condition Dialog Box ([Address] page) [Break Condition 1] dialog ...
Page 185
Notes on Setting the [Break Condition] Dialog Box and BREAKCONDITION_SET Command: 1. When [Go to cursor], [Step In], [Step Over], or [Step Out] is selected, the settings of Break Condition 3 are disabled. 2. Break Condition 3 is disabled when ...
Page 186
Notes on Setting the [Breakpoint] Dialog Box 1. When an odd address is set, the address is rounded down to an even address software break is accomplished by replacing instructions. Accordingly, it can be set only to ...
Page 187
AUD Functions In the SH7144F E10A emulator, the following functions using the AUD function can be used. These functions are operational when the AUD pin is connected to the emulator Table 6.7 AUD Functions Function Branch trace function RAM ...
Page 188
Branch Trace Function When a branch occurs during user program execution, the branch destination address is acquired. When the next branch occurs while the trace information is being output, the information is stopped and the next trace information is ...
Page 189
... In the SH7144F E10A emulator, the maximum number of trace display pointers is as follows: When HS7144KCM02H is used: D'16383 to 0 When HS7144KCI02H is used: D'65535 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. ...
Page 190
Notes on HDI 1. Note on Moving Source File Position after Creating Load Module When the source file is moved after creating the load module, the [Open] dialog box may be displayed to specify the source file during the ...
Page 191
Example: Array display When array elements exceed 1000, elements from after 1000 will not be displayed. 6. Memory Load Function When [Load...] is selected from the [Memory] menu, the Memory Load function can be used although it takes time to ...
Page 192
Example: C:\\HEW\\HDI5\\E10A\\Tutorial\\Debug\\TUTORIAL.ABS 9. About Hitachi Debugging Interface User’s Manual This version of HDI does not support section 10, Selecting Functions, written in Hitachi Debugging Interface User’s Manual. 10. Note on Initiating HDI When the emulator is initiated by using another ...
Page 193
Load of Motorola S-type Files This HDI does not support Motorola S-type files with only the CR code (H'0D) at the end of each record. Load Motorola S-type files with the CR and LF codes (H'0D0A) at the end ...
Page 194
Note on Radix in the [Register] Dialog Box The default input radix in the [Register] dialog box is hexadecimal irrespective of the Radix display. When a radix other than a hexadecimal is input, specify the prefix code such as ...
Page 195
Note on Downloading Program In the [Load Program] dialog box, which is opened when [Load Program…] is selected, the verify function is invalid. After downloading the program, perform verify in the [Verify S- Record File with Memory] dialog box, ...
Page 196
174 ...