To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.
Notice 1. 2. 3. 4. 5. 6. 7. 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 the latest product information with a Renesas Electronics sales office.
User’s Manual SH7641 E10A Emulator User’s Manual SH7641 E10A HS7641KCM01HE Renesas Microcomputer Development Environment System Rev.1.0 2003.
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 lead to personal injury, fire or property damage.
IMPORTANT INFORMATION READ FIRST • 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, the term "emulator product" shall be defined as the following products produced only by Renesas Technology Corp. excluding all subsidiary products.
LIMITED WARRANTY Renesas warrants its emulator products to be manufactured in accordance with published specifications and free from defects in material and/or workmanship. Renesas, at its option, will replace any emulator products returned intact to the factory, transportation charges prepaid, which Renesas, upon inspection, shall determine to be defective in material and/or workmanship. The foregoing shall constitute the sole remedy for any breach of Renesas' warranty.
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 you may have other rights which may vary from state to state.
SAFETY PAGE READ FIRST • 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 safety alert symbol. It is used to alert you to potential personal injury hazards. Obey all safety messages that follow this symbol to avoid possible injury or death.
WARNING Observe the precautions listed below. Failure to do so 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. 1. Do not repair or remodel the emulator product by yourself for electric shock prevention and quality assurance. 2. Always switch OFF the host computer and user system before connecting or disconnecting any CABLES or PARTS. 3.
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. WARNING Always switch OFF the host computer and user system before connecting or disconnecting any CABLES or PARTS. Failure to do so 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.
Preface Thank you for purchasing the E10A emulator. CAUTION 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 for software and hardware of user systems based on Renesas’ original microprocessor.
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 device • Programming Manual for each device Notes: ii 1. IBM PC is a registered trademark of International Business Machines Corporation. ® ® ® 2. Microsoft , Windows , and Windows NT are registered trademarks of Microsoft Corporation in the United States and/or other countries.
Contents Section 1 Overview............................................................................................1 1.1 1.2 1.3 Warnings ........................................................................................................................... 3 Environmental Conditions ................................................................................................ 4 Components ............................................................................................................
3.14.3 Executing [Step Over] Command ........................................................................ 50 3.15 Forced Breaking of Program Executions .......................................................................... 52 3.16 Displaying Local Variables............................................................................................... 53 3.17 Break Function.................................................................................................................. 54 3.17.
5.2.8 5.2.9 5.2.10 5.2.11 5.2.12 5.2.13 5.2.14 5.2.15 5.2.16 5.2.17 5.2.18 5.2.19 5.2.20 5.2.21 5.2.22 5.2.23 5.2.24 5.2.25 BREAKPOINT: BP ............................................................................................. 158 BREAKPOINT_CLEAR: BC.............................................................................. 160 BREAKPOINT_DISPLAY: BD.......................................................................... 162 BREAKPOINT_ENABLE: BE ................................................
Figures Figure 1.1 Figure 1.2 Figure 2.1 Figure 2.2 Figure 2.3 Figure 2.4 System Configuration with the Emulator (PCMCIA Card Emulator Used)............. 1 System Configuration with the Emulator (PCI Card Emulator Used)...................... 2 Emulator Preparation Flow Chart............................................................................. 7 Inserting the PCMCIA Card Emulator in the Host Computer’s Slot........................ 11 Inserting the PCI Card Emulator in the Host Computer’s Slot.......
Figure 3.21 Figure 3.22 Figure 3.23 Figure 3.24 Figure 3.25 Figure 3.26 Figure 3.27 Figure 3.28 Figure 3.29 Figure 3.30 Figure 3.31 Figure 3.32 Figure 3.33 Figure 3.34 Figure 3.35 Figure 3.36 Figure 3.37 Figure 3.38 Figure 3.39 Figure 3.40 Figure 3.41 Figure 3.42 Figure 3.43 Figure 3.44 Figure 3.45 Figure 3.46 Figure 3.47 Figure 3.48 Figure 3.49 Figure 3.50 Figure 3.51 Figure 3.52 Figure 3.53 Figure 3.54 Figure 3.55 Figure 3.56 Figure 3.57 Figure 3.58 Figure 3.59 Figure 3.60 Figure 3.61 Figure 3.
Figure 3.64 [Source] Window (Software Break Setting)........................................................... 87 Figure 3.65 [Profile-List] Window ............................................................................................ 87 Figure 3.66 [Profile-Tree] Window ........................................................................................... 88 Figure 3.67 [Profile-Chart] Window.......................................................................................... 88 Figure 3.
Figure 6.10 Figure 6.11 Figure 6.12 Figure 6.13 Figure 6.14 Figure 6.15 Figure 6.16 Figure 6.17 [Trace mode] Page.................................................................................................. 203 [AUD Branch trace] Page....................................................................................... 204 [Window trace] Page .............................................................................................. 205 [Trace] Window ..............................................
Tables Table 1.1 Environmental Conditions ......................................................................................... 4 Table 1.2 Operating Environments ............................................................................................ 5 Table 2.1 Recommended H-UDI Port Connector ...................................................................... 12 Table 2.2 Contents of the CD-R Directories.............................................................................. 23 Table 3.
Table 5.6 BREAKCONDITION_DISPLAY Command Parameter .......................................... 152 Table 5.7 BREAKCONDITION_ENABLE Command Parameters.......................................... 153 Table 5.8 BREAKCONDITION_SET Command Parameters .................................................. 155 Table 5.9 BREAKPOINT Command Parameters...................................................................... 158 Table 5.10 BREAKPOINT_CLEAR Command Parameters.....................................................
xii
Section 1 Overview The E10A emulator (hereafter referred to as the emulator) is a software and hardware development support tool for application systems using the microprocessor developed by Renesas, Ltd. The PCMCIA card emulator or PCI card emulator (hereafter referred to as the card emulator), which is the main unit of the emulator, is connected, through the H-UDI (user debug interface) port*, to the user system.
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 interface. • Realtime emulation Realtime emulation of the user system is enabled at the maximum operating frequency of the CPU.
• AUD trace function* The AUD trace function enables realtime trace. Note: The AUD is an abbreviation of the Advanced User Debugger. Support for the AUD varies with the product. 1.1 Warnings CAUTION READ the following warnings before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. 1. Check all components against the component list after unpacking the emulator. 2. Never place heavy objects on the casing. 3.
1.2 Environmental Conditions CAUTION Observe the conditions listed in tables 1.1 and 1.2 when using the emulator. Failure to do so will cause illegal operation in the user system, the emulator product, and the user program. Table 1.1 Environmental Conditions Item Specifications Temperature Operating: +10°C to +35°C Storage: –10°C to +50°C Humidity Operating: 35% RH to 80% RH, no condensation Storage: 35% RH to 80% RH, no condensation Vibration Operating: 2.45 m/s max. 2 Storage: 4.9 m/s max.
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 98, Windows Me, Windows 2000, or Windows NT Minimum memory capacity 32 Mbytes or more (double of the load module size recommended) Hard-disk capacity Installation disk capacity: 10 Mbytes or more.
1.3 Components Check all the components unpacking. For details on the E10A emulator components, refer to section 6.1, Components of the Emulator. If the components are not complete, contact a Renesas sales agency.
Section 2 Preparation before Use 2.1 Emulator Preparation WARNING 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 emulator and prepare it for use as follows: Reference Unpack the emulator Component list Check the components against the component list When the emulator is used first.
2.2 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 when it has not been automatically activated, execute Setup.exe from the root directory of the CD-R. Follow the cues given by the installation wizard to install the HDI.
2.2.2 Installing under Windows NT4.0 Operating System (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. Refer to section 2.3, Connecting the Card Emulator to the Host Computer. 3. Start the host computer and log-on with an administrator-level user name. 4. Install the HDI. (For a component, be sure to select [PCI Card Driver].
2.2.3 Installing under Windows2000 Operating System (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 down and turn off the power to the host computer. 4. Insert the PCI-card emulator in a slot on the host computer. Refer to section 2.3, Connecting the Card Emulator to the Host Computer. 5.
2.3 Connecting the Card Emulator to the Host Computer Insert the card emulator, according to its type, in a PCMCIA TYPE II slot or PCI slot on the host computer (figures 2.2 and 2.3). Note: When using Windows98, WindowsMe, or Windows2000, be sure to install the HDI before putting the card emulator in place. Figure 2.2 Inserting the PCMCIA Card Emulator in the Host Computer’s Slot Figure 2.3 Inserting the PCI Card Emulator in the Host Computer’s Slot Use the procedure, described in section 2.
WARNING When inserting the PCI-card emulator, note the following. Failure to do so 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 the connector and cable positions. 2.4 Connecting the Card Emulator to the User System (1) The H-UDI port connector must be installed to the user system. Table 2.1 shows the recommended H-UDI port connector for the emulator. Table 2.
User system interface cable Tab GND line H-UDI port connector Pin 8 User system GND connection Pin 1 User system Figure 2.4 Connecting the User System Interface Cable to the User System when the 14-pin Straight Type Connector is Used Notes: 1. To connect the signals output from the H-UDI port connector, refer to the device pin alignment. 2. To remove the user system interface cable from the user system, pull the tab on the connector upward. 3.
H-UDI port SHxxxx TDI TDO JTAG port H-UDI IC TDI IC TDO TDI TAP IC TDI TDO TAP TDO TAP Boundary scan loop User system TDI: Test data input TDO: Test data output TAP: Test access port Figure 2.
2.5 System Check When the HDI program is executed, use the procedure below to check that the emulator is operating correctly. 1. Check that the emulator card is inserted in the host computer’s slot. 2. Connect the user system interface cable to the connector of the card emulator. 3. Connect the user system interface cable to the H-UDI port connector. 4. Supply power to the host computer and select [HDI for E10A SHxxxx] -> [Hitachi Debugging Interface] from the [Start] menu. Figure 2.
5. Select the setting to be used. Figure 2.
6. 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 the interface to which the board is connected. Once the driver is selected in the [E10A Driver Details] dialog box, this dialog box is not displayed when the HDI is run next time. (This procedure will not be executed by target devices.) Figure 2.
• Click the [Close] button. 7. The HDI window is displayed, and the dialog box is displayed as shown in figure 2.9. Figure 2.9 Dialog Box of the RESET Signal Input Request Message 8. Power on the user system. 9. Input the reset signal from the user system, and click the [OK] button. 10. When "Link Up" is displayed on the status bar, the HDI initiation is completed. Figure 2.10 [HDI] Status Bar Notes: 1.
Figure 2.11 [JTAG Connector Disconnected] Dialog Box 3. If the emulator is not initiated, the following dialog boxes shown in figures 2.12 through 2.16 will be displayed. (a) If the following dialog box is displayed, the power of the user system may not be input or the RESET signal may not be input to the device. Check the input circuits for the power of the user system and the reset pin. Figure 2.
Figure 2.14 [COMMUNICATION TIMEOUT ERROR] Dialog Box Figure 2.15 [INVALID ASERAM FIRMWARE!] Dialog Box Figure 2.16 [Error JTAG boot] Dialog Box 4. If the driver is not correctly connected, the following dialog box will be displayed. Figure 2.
The [E10A Driver Details] dialog box is displayed when the [OK] button is clicked. Select the correct driver. For details, refer to section 6.5.1, Emulator Driver Selection. 2.6 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. Figure 2.18 [Exit HDI] Dialog Box 2. Then, the [Save session] dialog box is displayed. If necessary, click the [Yes] button to save session.
2.7 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 setup program is executed again and the installed application can be changed, modified, or removed. When the application is to be uninstalled, select removal. CAUTION A shared file may be detected while the program is being removed.
2.8 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 Description Dlls Microsoft runtime library A runtime library for the HDI. The version is checked at installation and this library is copied to the hard disk as part of the installation process. Drivers E10A emulator driver The E10A emulator drivers.
24
Section 3 Tutorial 3.1 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 the following actions: • The main function generates random data to be sorted. • The sort function sorts the generated random data in ascending order. • The change function then sorts the data in descending order. The file tutorial.
Notes: 1. Operation of tutorial.abs is big endian. For little-endian operation, tutorial.abs must be recompiled. After recompilation, the addresses may differ from those given in this section. 2. This program was created by using High-performance 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. 3. This program was compiled without optimization for the SH2 CPU.
3.2 Running the HDI To run the HDI, select the [HDI for E10A SHxxxx] -> [Hitachi Debugging Interface] from the [Start] menu. Figure 3.1 [Start] Menu For the procedure of running the HDI, refer to section 2.5, System Check.
3.3 [HDI] Window Figure 3.2 [HDI] 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. 2. Toolbar: Provides convenient buttons as shortcuts for the most frequently used menu commands. 3. Source window: Displays the source program being debugged. 4. Status bar: Displays the status of the emulator, and progress information about downloading. 5.
3.4 Setting up the Emulator The clocks which are used for data communications must be set up on the emulator before the program is downloaded. • AUD clock A clock used in acquiring AUD traces. If its frequency is set too low, complete data may not be acquired during realtime tracing. If the frequency is set too high, the upper limit for the device’s AUD clock may be exceeded. The AUD clock is only needed for emulators that have an AUD trace function.
3.5 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 [AUD clock] and [JTAG clock] combo boxes. The clock also operates with the default value. 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.
3.6 Checking the Operation of the Target Memory for Downloading Check that the destination memory area for downloading is operating correctly. When the destination memory is SDRAM or DRAM, a register in the bus controller must be set before downloading. Set the bus controller correctly in the [I/O Registers] window according to the memory type. For details, refer to section 8.6, I/O Register Display, in the Hitachi Debugging Interface User’s Manual.
• Placing the mouse cursor on a point in the display of data in the [Memory] window and double clicking allows the values at that point to be changed. Data can also be directly edited around the current position of the text cursor.
3.7 Downloading the Tutorial Program 3.7.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 as shown in figure 3.6, then click the [Open] button. Figure 3.6 [Load Program] Dialog Box Notes: 1.
3.7.2 Displaying the Source Program The HDI allows the user to debug a program at 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 file the user has loaded. Figure 3.8 [Open] Dialog Box • Select [tutorial.c] and click the [Open] button. The [Source] window is displayed.
Figure 3.9 [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 main program, but the user can use the scroll bar to scroll through the program and look at the other statements.
3.8 Setting a Software Breakpoint A breakpoint is a simple debugging function. 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 sort function call: • Select by double-clicking the [BP] column on the line containing the sort function call. Figure 3.
3.9 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.
• 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’0c00006c in this tutorial program, and click the [OK] button. • Move the mouse pointer on the value to be changed in the [PC] value area and enter the new value by the keyboard. Figure 3.12 [Register] Dialog Box (PC) • Change the value of the stack pointer (SP) in the same way.
3.10 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. Figure 3.13 [Go] Button The program will be executed up to the breakpoint that has been inserted, and a statement will be highlighted in the [Source] window to show the position that the program has halted, with the message [Break=BREAKPOINT] in the status bar. Figure 3.
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 Cause of last break. Figure 3.15 [System Status] Window Note: The items that can be displayed in this window differ according to the product. For the items that can be displayed, refer to the online help.
3.11 Reviewing Breakpoints The user can see all the breakpoints set in the program in the [Breakpoints] window. • Select [Breakpoints] from the [View] menu. Figure 3.16 [Breakpoints] Window The pop-up menu, opened by clicking the [Breakpoints] window with the right mouse button, also allows the user to set or change breakpoints, define new breakpoints, and delete, enable, or disable breakpoints.
3.12 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: • Select [Memory …] from the [View] menu, enter _main in the [Address] edit box, and set Word in the [Format] combo box. Figure 3.17 [Open Memory Window] Dialog Box • Click the [OK] button. The [Memory] window showing the specified area of memory is displayed. Figure 3.
3.13 Watching Variables As the user steps through a program, it is 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 beginning of the program, by using the following procedure: • Click the left of displayed array a in the [Source] window to position the cursor. • Click the [Source] window with the right mouse button and select [Instant Watch...] from a pop-up menu.
• Click [Add Watch] button to add a variable to the [Watch] window. Figure 3.20 [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 right mouse button and select [Add Watch…] from the pop-up menu. The following dialog box will be displayed. Figure 3.21 [Add Watch] Dialog Box • Input variable max and click the [OK] button.
The [Watch] window will now also show the int-type variable max. Figure 3.22 [Watch] Window (Displaying the Variable) The user can double-click the + symbol to the left of any variable in the [Watch] window to watch the all elements in array a. Figure 3.
3.14 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 call in a single step. Step Out Steps out of a function, and stops at the statement following the statement in the program that called the function. Step… Steps the specified times repeatedly at a specified rate. 3.14.
Figure 3.25 [Source] Window (Step In) • The highlighted line moves to the first statement of the sort function in the [Source] window.
3.14.2 Executing [Step Out] Command The [Step Out] steps out of the called function and stops at the next statement of the calling statement in the main function. • To step out of the sort function, select [Step Out] from the [Run] menu, or click the [Step Out] button in the toolbar. Note: It takes time to execute this function. Figure 3.26 [Step Out] Button Figure 3.27 [HDI] Window (Step Out) • The data of variable a displayed in the [Watch] window is sorted in ascending order.
• To execute two steps, use [Step In] twice. Figure 3.28 [HDI] Window (Step In −> Step In) • The value of max displayed in the [Watch] window is changed to the maximum data value.
3.14.3 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.29 [Source] Window (Before Step Over Execution) • To step through all statements in the change function at a single step, select [Step Over] from the [Run] menu, or click the [Step Over] button in the toolbar. Figure 3.
Figure 3.
3.15 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. Figure 3.32 [Go] Button • The program goes into an endless loop. To force a break in execution, select [Halt] from the [Run] menu or the [Stop] button on the toolbar. Figure 3.
3.16 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: a, j, i, min, and max. • Select [Locals] from the [View] menu. The [Locals] window is displayed. Initially, the [Locals] window is empty because local variables have not yet been declared. The [Locals] window will now show the local variables and their values. Figure 3.
3.17 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 and setting of the break function are described below. 3.17.1 Software Break Function The emulator can set up to 255 software breakpoints. Other methods for setting a software breakpoint than in section 3.8 are described below.
• 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 as a default. Figure 3.
• Click the [Add...] button to display the [Breakpoint] dialog box. • Enter H'0c0000c2 to the [Value] edit box. Figure 3.37 [Break Point] Dialog Box • Click the [OK] button.
The [Break] dialog box is displayed. The address set in the value field of [Breakpoint] and the memory space are displayed. Figure 3.38 [Point] Page ([Break] Dialog Box) (After Software Breakpoint Setting) • Click the [Close] button (or [OK] button in some emulator products).
The software breakpoint that has been set is displayed in the [Breakpoints] window. Figure 3.39 [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 program counter and stack pointer values (PC = H’0c00006c and R15 = H’0c000c00) that have been set in section 3.9, Setting Registers, in the [Registers] window. Click the [Go] button.
The [System Status] window displays the following contents. Figure 3.41 Displayed Contents of the [System Status] Window (Software Break) Note: The items that can be displayed in this window differ according to the product. For the items that can be displayed, refer to the online help.
3.18 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] menu. The [Breakpoints] window is displayed. • Click the [Breakpoints] window with the right mouse button and select [Delete All] from the pop-up menu to cancel all breakpoints that have been set.
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.43 [Condition] Page ([Break] Dialog Box) Up to three breakpoints can be set independently for the Break Condition hardware break condition. In this example, set the hardware break condition for Break Condition 1. Note: The number of hardware break conditions differs according to the product.
• Clear the [Don't Care] check box in the [Address] page. • Select the [Address] radio button and enter H'0c0000b2 as the value in the [Address] edit box. Figure 3.44 [Address] Page ([Break Condition 1] Dialog Box) 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.
• Select [Bus State] to display the [Bus State] page. • Select the [Read] radio button in the [Read/Write] group box. Figure 3.45 [Bus State] Page ([Break Condition 1] Dialog Box) 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.
• 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.46 [Break] Dialog Box (After Hardware Break Condition Setting) Note: The number of hardware break conditions differs according to the product. For the number that can be specified for each product, refer to the online help. • Click the [OK] button.
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 is executed, a break will occur when address H'0c0000b2 is accessed in a read cycle. Figure 3.47 [Breakpoints] Window ([Break Condition 1] Setting) • Close the [Breakpoints] window.
The program runs then stops at the condition specified under Break Condition 1. Figure 3.
The [System Status] window displays the following contents. Figure 3.49 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 be displayed, refer to the online help.
3.18.1 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 is halted. This mode is called sequential break. Table 3.3 Sequential Break Conditions Break Condition Description Sequential break condition 2-1 Program is halted when Break Condition 2 and Break Condition 1 are satisfied in that order. Sequential break condition 2-1 is described below as an example.
Figure 3.50 [Configuration] Dialog Box (Sequential Break Setting) 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. Click the [OK] button and close the [Configuration] dialog box.
Set hardware break conditions as follows: Break condition 1: When address H'0c0000c6 is accessed in a read cycle, a break condition is satisfied. Break condition 2: When address H'0c0000b2 is accessed in a read cycle, a break condition is satisfied. Follow the setting method described in the previous section. • When Break Condition 1,2 setting has been completed, the state of the [Breakpoints] window is as follows. Figure 3.
The program runs then stops at the condition specified under Break Condition 1. Figure 3.
The [System Status] window displays the following contents. Figure 3.53 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 displayed, refer to the online help.
3.19 Trace Functions The E10A emulator has two branch-instruction trace functions. (1) Internal Trace Function The branch source and branch destination addresses, mnemonics, operands, and source lines are displayed. Since this function uses the trace buffer built into the MCU, a realtime trace can be acquired. Notes: 1. The number of branch instructions that can be acquired by a trace differs according to the product. For the number that can be specified for each product, refer to the online help. 2.
Table 3.4 AUD Trace Functions Type Mode Description Acquisition mode when branches continuously occur Realtime trace When the next branch occurs while the trace information is being output, the output is stopped and the next trace information is output. The user program can be executed in realtime, but some trace information will not be output. Non realtime trace When the next branch occurs while the trace information is being output, the CPU stops operations until the information is output.
3.19.1 Internal Trace Function The branch source and branch destination information for the latest several branch instructions are displayed. The following is a procedure to set the internal trace function (this function is not needed to be set in the emulator that does not support the AUD trace function): 1. Select [Trace] from the [View] menu. 2. Click the [Trace] window with the right mouse button and select [Acquisition] from the pop-up menu to display the [Trace Acquisition] window. 3.
Run the program as shown in the example of section 3.17.1, Software Break Function. The trace results are displayed in the [Trace] window after the program execution is completed. Figure 3.55 [Trace] Window • If necessary, adjust the column width by dragging the header bar immediately below the title bar. Note: The number of branch instructions that can be acquired by a trace differs according to the product. For the number that can be specified for each product, refer to the online help.
3.19.2 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 does not need to be set in an emulator that does not support the internal trace function): 1. Select [Trace] from the [View] menu. 2. Click the [Trace] window with the right mouse button and select [Acquisition] from the pop-up menu to display the [Trace Acquisition] window. 3.
The following is an example of the display in the SH7751 E10A emulator. Figure 3.
3.19.3 VP_MAP Translation The MCU, which has an MMU, translates internal addresses (virtual addresses) to actual memory addresses (physical addresses). Address translation is performed according to the address translation table (translation look-aside buffer: TLB) in the MCU. The MMU operates during command input wait state as well as during user program execution.
H'0 H'FFF H'10000 H'10FFF H'11000 H'11FFF H'12000 H'12FFF H'12000 H'12FFF H'4000000 H'4000FFF Virtual address Physical address Figure 3.58 Address Translation according to VP_MAP Tables How to translate addresses depends on the settings of the radio buttons of the memory area group in the [Configuration] dialog box. The following shows how to translate addresses in each setting state. • When the Normal radio button is selected: The VP_MAP table has a priority over the TLB.
Table 3.
3.20 Stack Trace Function The emulator uses the stack’s 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 module that has the Dwarf2-type debugging information is loaded. 2. For details on the stack trace function, refer to the online help. • Double-click the [BP] column in the sort function and set a software breakpoint. Figure 3.
Figure 3.60 [Stack Trace] Window Figure 3.60 shows that the position of the program counter is currently at the selected line of the sort() function, and that the sort() function is called from the main() function. Notes: 1. If the function is not deeply nested (lower than 10), the main() function will be displayed multiple times. 2. For details on this function, refer to the online help. The online help is opened when the [F1] key is pressed in the [Stack Trace] window.
3.21 Profiling Function The profile function can measure performance for each function. Notes: 1. Realtime operation is not possible while this function is in operation, since internal breaks are generated during program execution. Measuring the profile itself affects the measurements. For details, refer to section 6, SHxxxx Emulator Specifications. 2.
• The profile function is now enabled. Place the mouse cursor on an entry in the [Profile-List] window, click the right-hand mouse button, then select [Enable Profiler] from the pop-up menu. Figure 3.
• Data to be measured for the selected function is now set. Select [Select Data] from the pop-up menu by clicking with the right mouse button. The [Select Data] dialog box is displayed. Figure 3.63 [Select Data] Dialog Box • Use the [Select Data] dialog box to select the data to be measured. [All operand access count] is selected for Data1 as a first item to be measured. [Elapsed-time cycle] is selected for Data2 as a second item to be measured. • After the data has been selected, press the [OK] button.
Figure 3.64 [Source] Window (Software Break Setting) • Set the same program counter and stack pointer values (PC = H’0c00006c and R15 = H’0c000c00) as were set in section 3.9, Setting Registers (again, use the [Registers] window). Click the [Go] button. • After the break in execution, the results of the measurements are displayed in the [Profile-List] window. Figure 3.
• Figures 3.66 and 3.67 show the [Profile-Tree] and [Profile-Chart] windows, respectively. Figure 3.66 [Profile-Tree] Window Figure 3.
3.22 Download Function to the Flash Memory Area The E10A emulator enables downloading to the flash memory area. This function requires a program for writing the flash memory (hereinafter referred to as a write module), a program for erasing the flash memory (hereinafter referred to as an erase module), and the RAM area for downloading and executing these modules. Note: The write/erase module must be prepared by users.
Flash memory download method It is required to perform necessary settings on the [Loading flash memory] page in the [Configuration] window for downloading to the flash memory. Figure 3.
Table 3.7 shows the options for the [Loading flash memory] page. Table 3.7 [Loading flash memory] Page Options Option Description [Loading flash memory] radio button Sets Enable for flash memory downloading. [Erasing flash memory] radio button Sets Enable for erasing before the flash memory is written. [File name] edit box Sets the write/erase module name. The file that has been set is loaded to the RAM area before loading to the flash memory.
Examples of downloading to the flash memory The following shows examples of downloading to the flash memory manufactured by Intel Corporation (type number: G28F640J5-150) that has been mounted on Renesas' SH7751 CPU board (type number: HS7751STC01H). A sample is provided in the \Fmtool folder in the installation destination folder. Create the program for user specification according to this sample. The SH7751 E10A emulator must be used when the SH7751 CPU board is used. Table 3.
Table 3.9 Sample Program Specifications Item Contents RAM area to be used H'0C001000 to H'0C0015BF Write module start address H'0C001100 Erase module start address H'0C001000 (i) Since the SDRAM is used, the bus controller is set. (ii) Options on the [Loading flash memory] page in the [Configuration] window are set as follows: Figure 3.
Notes: 1. When the data has already been written in the flash memory, be sure to select [Enable] for [Erasing flash memory]. If [Disable] is selected, a verify error occurs. 2. When [Erasing flash memory] is selected, it takes about one minute. (iii) [Load Program…] is selected from the [File] menu for downloading to the flash memory area.
3.23 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 hardware and software problems by accurately isolating and identifying the conditions under which such problems arise. Further details on the use of the HDI can be found in the separately issued Hitachi Debugging Interface User's Manual.
96
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 manual, a O mark or the relevant section number is shown. Related commands in the E10A Emulator User's Manual are also shown. Table 4.
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 Go Reset Go Go to Cursor Set PC To Cursor Run… Step In Step Over Step Out Step… Halt 98 Hitachi Debugging Interface User's Manual O O O O O O O O O O O O X O O O O O O O O O O O O O O This Manual 3.11, 3.17.1, 4.2.4, 6.
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 All Help Menu Index Using Help Search for Help on About HDI Hitachi Debugging Interface User's Manual O O O O O O O O O O O O O O O O O O O O O This Manual — — — — — — — — — — — — 3.5, 4.
4.2 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 sets the emulation conditions of the emulator. Window: Figure 4.1 [Configuration] Dialog Box 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.
Description: The [Configuration] dialog box consists of the [General] page listed in table 4.2. Table 4.2 [Configuration] Dialog Box Page Page Name Description [General] Sets and displays the emulation mode conditions. [Loading flash memory] Sets the download function for the flash memory. Clicking the [OK] button sets the emulation conditions. If the [Cancel] button is clicked, this dialog box is closed without setting the emulation conditions.
(1) [General] Page ([Configuration] Dialog Box) Function: This page sets the emulator operation conditions, displays the device name, sets the emulation mode, UBC mode, and memory area (only for a product that supports a device with the MMU function), sets and displays the AUD clock (AUDCK) and JTAG clock (TCK), and selects the driver. Window: Figure 4.2 [General] Page ([Configuration] Dialog Box) Note: The items and displayed contents that can be set in this window differ according to the product.
Description: Table 4.3 [General] Page Options Option Description [Mode] combo box Displays the device name. [Emulation mode] combo box Selects the execution mode. Select Normal to perform normal emulation. Select No Break to disable breakpoint settings. Select Sequential break Condition 2-1, etc. to use the sequential *1 break function . (For Sequential break Condition 2-1, execution stops when conditions are satisfied in the order of Break Condition 2 and Break Condition 1.
When a driver is to be changed with the [Change..] button, the following message is displayed. Figure 4.3 Warning Message Box When the [Yes] button is clicked, the [E10A Driver Details] dialog box is displayed. When the [No] button is clicked, the display returns to the [Configuration] dialog box.
(2) [E10A 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 Details] Dialog Box Description: Table 4.4 Options for the [E10A Driver Details] Dialog Box Option Description [Driver] combo box Selects the driver to connect the HDI with the emulator. Selects [E10A PC Card Driver] to use the PCMCIA card emulator.
(3) [Loading flash memory] Page ([Configuration] Dialog Box) Function: Downloading to the flash memory is set on the [Loading flash memory] page. Window: Figure 4.
Description: Table 4.5 [Loading flash memory] Page Options Option Description [Loading flash memory] radio button Sets Enable for flash memory downloading. [Erasing flash memory] radio button Sets Enable for erasing before the flash memory is written. [File name] edit box Sets the write/erase module name. The file that has been set is loaded to the RAM area before loading to the flash memory. A maximum of 128 characters can be input for the file name.
4.2.2 [Breakpoints] Window Function: This window lists all break conditions that have been set. Window: Figure 4.
Description: The [Breakpoints] window displays breakpoint setting information. The items listed in the following tables are displayed. Table 4.6 [Breakpoints] Window Display Items Item Description [Enable] Displays whether the break condition is enabled or disabled. BREAKPOINT: ! Break Condition: " (If the address is the same as the one that has been set to the BREAKPOINT, the mark is !.) [File/Line] Displays the file name and line number where the breakpoint is set.
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.7 [Breakpoints] Window Pop-up Menu Operation Menu Name Description [Add] Sets break conditions. Clicking this button will display the [Break] dialog box, enabling break conditions to be set. [Edit] Changes break conditions.
4.2.3 [Break] Dialog Box Function: This dialog box displays the break condition settings. Window: Figure 4.
Description: The [Break] dialog box consists of the pages listed in table 4.8. Table 4.8 [Break] Dialog Box Pages Page Name Description [Point] Displays software breakpoint settings. [Condition] Displays Break Condition settings. The dialog boxes which set or modify break conditions can be displayed from the pages above. Clicking the [OK] button (or [Close] button in some emulator products) will close this dialog box.
(1) [Point] 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.
Description: Table 4.9 [Point] Page Options Option Description [Break point] list box Lists the software breakpoints currently being set. The display contents are and . is displayed as follows: • Physical Space • Virtual Space ASID = D’xxx (xxx is the ASID value displayed in decimal form.) [Add...] button Sets software breakpoints. Clicking this button displays the [Break Point] dialog box. [Edit...
(2) [Condition] 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.9 [Condition] Page ([Break] Dialog Box) Note: The number of hardware break conditions differs according to the product. For the number that can be specified for each product, refer to the online help.
Description: Table 4.10 [Condition] Page Options Option Description [Break Condition] list box Displays the Break Condition settings. The display at system initiation is as follows: When conditions are set, Enable is displayed. When no conditions are set, Empty is displayed. 1 Empty (setting of Break Condition 1) 2 Empty (setting of Break Condition 2) : [Edit...] button Changes the Break Condition settings selected in the [Break Condition] list box.
4.2.4 [Break Point] Dialog Box Function: This dialog box sets software breakpoints. Window: Figure 4.10 [Break Point] Dialog Box 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.
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.11 [Address] Page Options Option Description [Value] edit box Sets a breakpoint address with a number or a symbol. [Normal] radio button Does not set an address area.* [Physical Space] radio button Shows that the break condition is the physical area.
4.2.5 [Break Condition] Dialog Box Function: This dialog box sets hardware break conditions. Window: Figure 4.11 [Break Condition] Dialog Box 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.
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 the [OK] button sets the hardware break conditions. If the [Cancel] button is clicked, the dialog box is closed without setting the hardware break conditions.
4.2.6 [Break 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 the dialog box name in table 4.12. For details, refer to section 6.5.2, Break Condition Functions. Table 4.
Table 4.13 shows all the [Break Condition] dialog box pages. Table 4.13 [Break Condition] Dialog Box Pages Page Name Function [Address] Sets the address conditions of Break Condition 1 and Break Condition 2. (Address condition is not displayed in the [Break Condition 3] dialog box page.) [Data] Sets the data conditions of Break Condition 1. (Data condition is not displayed in the [Break Condition 2] and [Break Condition 3] dialog box pages.
(1) [Address] Page ([Break Condition] Dialog Box) Function: This page sets the address bus conditions. Window: Figure 4.12 [Address] Page ([Break Condition 1] Dialog Box) 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.
Description: Table 4.14 [Address] Page Options Option Description [Don’t Care] check box Does not set address conditions. [Address] radio button Sets use of the normal address bus as break conditions. [Only program fetched address] radio button Sets a break before prefetched address execution as break conditions. [Only program fetched address after] radio button Sets a break after prefetched address execution as break conditions.
(2) [Data] Page ([Break Condition] Dialog Box) Function: This page sets the data bus conditions. Window: Figure 4.13 [Data] Page ([Break Condition 1] Dialog Box) 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.
Description: Table 4.16 [Data] Page Options Option Description [Don’t Care] check box Does not set data conditions. [Value] edit box Sets the data bus value with a number. [Byte] radio button Sets byte data access cycles. [Word] radio button Sets word data access cycles. [Long] radio button Sets longword data access cycles. [X-bus data] radio button Sets X-bus data access cycles. [Y-bus data] radio button Sets Y-bus data access cycles.
(3) [ASID] Page ([Break Condition] Dialog Box) Function: This page sets the ASID conditions. Window: Figure 4.14 [ASID] Page ([Break Condition] Dialog Box) Description: Table 4.17 [ASID] Page Options Option Description [Don’t Care] check box Does not set ASID conditions. [ASID] edit box Sets the ASID condition value. The default is 0. Note: This page is displayed when the conditions of Break Condition 1 and Break Condition 2 are set.
(4) [Bus State] Page ([Break Condition] Dialog Box) Function: This page sets bus state conditions and read/write cycle conditions. Window: Figure 4.15 [Bus State] Page ([Break Condition] Dialog Box) 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.
Description: Table 4.18 [Bus State] Page Options Group Box Option Description [Bus State] group box [All] radio button Sets the bus state conditions as break conditions. [Data] radio button Sets the execution cycle as break conditions. [DMA] radio button Sets DMA cycles as a break condition. [Read/Write] radio button Sets the read/write cycle conditions as break conditions. [Read/Write] group box [Read] radio button Sets read cycles as break conditions.
(5) [Count] Page ([Break Condition] Dialog Box) Function: This page sets the conditions for Break Condition 1. Window: Figure 4.16 [Count] Page ([Break Condition] Dialog Box) Table 4.19 [Count] Page Options Option Description [Don’t Care] check box Sets no satisfaction count conditions. Input area Sets the satisfaction count as a break condition. The maximum count is 4,095. Breaks when the conditions set by the [Break Condition] dialog box for the specified times are satisfied. The default is D’1.
(6) [General] Page ([Break Condition] Dialog Box) Function: This page sets the conditions for Break Condition 3. Window: Figure 4.
Description: Table 4.20 [General] Page Options Group Box Option Description [LDTLB] group box [Don’t Care] radio button Does not set break conditions when the LDTLB instruction is executed. [Stop after executing LDTLB instruction] radio button Sets the LDTLB instruction execution as break conditions. [DMA] radio button Sets the DMA cycle as break conditions. [Don’t Care] radio button Does not set break conditions when the internal I/O area is accessed.
4.2.7 [Trace] Window Function: This window displays the trace buffer contents. Window: Figure 4.18 [Trace] 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.
Description: This window displays the trace buffer contents. The items listed in table 4.21 are displayed. Table 4.21 [Trace] Window Display Items Item Description [No.] Displays the number in ascending order as the trace stop point is 0 (signed decimal). [IP] Displays the instruction pointer (signed decimal). [TYPE] For the branch instruction trace, displays the information type, that is, branch source or branch destination.
4.2.8 [Trace 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 box is displayed. Table 4.22 [Trace Acquisition] Dialog Box Page Options Page Name Description [Trace Mode] Sets the conditions of trace mode.
(1) [Trace Mode] Page ([Trace Acquisition] Dialog Box) Function: This page sets the conditions for trace mode. Window: Figure 4.19 [Trace mode] Page ([Trace Acquisition] Dialog Box) Note: This function differs according to the product. For the specifications of each product, refer to the section related to the trace functions in section 6, SHxxxx E10A Emulator Specifications, or to the online help.
Description: Table 4.23 [Trace mode] Page Options Option Description [AUD trace] radio button Uses AUD trace functions. By default, this box is not checked. [Internal trace] radio button Uses the internal trace functions. By default, this box is checked. [Realtime trace] radio button When the next branch occurs while the trace information is being output, the information is stopped and the next trace information is output.
4.2.9 [System Status] Window Function: This window lists information, such as conditions that have been set to the emulator and execution results. Window: Figure 4.20 [System Status] Window Note: The items that can be displayed in this window differ according to the product. For the items that can be displayed, refer to the online help.
The items listed in the following table are displayed in the [System Status] window. Table 4.24 [System Status] Window Display Items Page Item Description [Session] Target System Always displays Connected. Session Name Displays the session file name. Program Name Displays the load module file name. Connected To Displays the name of the connected emulator and the selected driver name. CPU Displays the target device name.
140
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 is as follows. Characters shown in bold-italics are to be input. [] : Parameters enclosed by [ ] can be omitted. < > : Contents shown in < > are set. < >=: The parameter to the left of the "=" sign is input in the format shown to the right.
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 4, Descriptions of Windows.
5.2 Command Descriptions The command list of the E10A emulator is shown below. Table 5.1 E10A HDI Commands No. Command Abb. Function 1 AUD_CLOCK AUCL Sets the AUD clock (AUDCK). 2 AUD_MODE AUM Sets AUD trace conditions. 3 AUD_TRACE AUT Displays trace information. 4 BREAKCONDITION_ CLEAR BCC Clears hardware breakpoints that have been set. 5 BREAKCONDITION_ DISPLAY BCD Displays hardware breakpoints that have been set.
Table 5.1 E10A HDI Commands (cont) No. Command Abb. Function 16 REFRESH RF Updates the HDI memory information to the latest contents. 17 RESTART RST Restarts the emulator. 18 STATUS STS Displays emulator state information. 19 STEP_INTERRUPT SI Displays or sets the enable or disable status of interrupts during step execution. 20 TRACE_DISPLAY TD Displays acquired trace buffer information. 21 UBC_MODE UM Displays or sets UBC use states.
5.2.1 AUD_CLOCK:AUCL Description: Sets or displays the AUD clock (AUDCK) values that have been set. Format: aucl [
Examples: To set AUD clock (AUDCK) to 15 MHz: >AUD_CLOCK 2 (RET) AUD CLOCK = 15MHz The AUD clock (AUDCK) is displayed: >AUD_CLOCK (RET) AUD CLOCK = 15MHz Related Item: [Configuration] dialog box 146
5.2.2 AUD_MODE:AUM Description: Sets or displays AUD trace acquisition conditions. Format: aum [] [] = mode = full Table 5.3 AUD_MODE Command Parameter Parameter Type Description Keyword Selects the trace mode. N: Internal trace F: Non realtime trace R: Realtime trace Keyword Continues or stops emulation when the trace memory is full. C: Always overwrites the oldest information to acquire the latest information.
Examples: To select realtime trace mode and set continue option: >aum mode R full c (RET) To display settings: >aum (RET) mode = Realtime trace, continue To use internal trace mode: >aum (RET) mode = Internal trace Related Item: [Trace Acquisition] dialog box 148
5.2.3 AUD_TRACE:AUT Description: Displays the trace information. Format: aut [] [] = start = end Table 5.4 AUD_TRACE Command Parameter Parameter Type Description Numerical value (-n) Start pointer value for trace display. Numerical value (-m) End pointer value for trace display. Notes: 1. In the PCMCIA card emulator, –D’8191 to D’0 can be set to the trace pointer.
Related Item: [Trace] dialog box 150
5.2.4 BREAKCONDITION_CLEAR: BCC Description: Clears hardware breakpoints that have been set. Format: bcc [] = channel Table 5.5 BREAKCONDITION_CLEAR Command Parameter Parameter Type Description Numerical value Hardware break channel number Note: When is omitted, all hardware breakpoints that have been set are cleared.
5.2.5 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 Table 5.
5.2.6 BREAKCONDITION_ENABLE: BCE Description: Enables or disables hardware breakpoints that have been set. Format: bce [] = channel Table 5.7 BREAKCONDITION_ENABLE Command Parameters Parameter Type Description Numerical value Hardware break channel number Keyword Enables or disables hardware break settings. Set either of the following keywords: enable: Enables hardware break settings. disable: Disables hardware break settings.
5.2.7 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, Break Condition Functions. Format: bcs
Table 5.8 BREAKCONDITION_SET Command Parameters Parameter Type Description Numerical value Hardware break condition channel number Specifiable options change depending on the channel number. For details, refer to section 6.5.2, Break Condition Functions. 1: , , , , and can be set. 2: , , , and can be set. 3: and can be set.
Table 5.8 BREAKCONDITION_SET Command Parameters (cont) Parameter Type Description Keyword Data bus access conditions Set one of the following keywords: byte: byte access word: word access long: longword access x: X-Bus data bus access y: Y-Bus data bus access Numerical value ASID value from 0 to H'FF.
Examples: To set the following conditions for channel 1 hardware breakpoint: item: An address bus value of H'1000000, item: D0 bit of the byte access data is 0, item: write cycle.
5.2.8 BREAKPOINT: BP Description: Sets software breakpoints. Note: The function will differ according to the devices used. Format: bp
[ []] = space = asid Table 5.9 BREAKPOINT Command Parameters Parameter Type Description Numerical value Breakpoint address When an odd address is set, the address is rounded down to an even address.Examples: To set a software breakpoint at physical address H'10002C8: >bp H'10002C8 space physical (RET) To set a software breakpoint at logical address H'1000000, whose ASID value is H'10: >bp H'1000000 space virtual asid H'10 (RET) Related Items: BC, BD, BE, VC, VD, VE, and VS commands [Breakpoints] window [Break] dialog box 159
5.2.9 BREAKPOINT_CLEAR: BC Description: Clears software breakpoints that have been set. Format: bc [
[ []]] = space = asid Table 5.Examples: To clear all breakpoints: >bc (RET) To clear all software breakpoints whose address value is H'1000000: >bc H'1000000 (RET) To clear a software breakpoint whose virtual address is H'1000000, according to the ASID value at command input: >bc H'1000000 space virtual (RET) To clear the software breakpoint at virtual address H’1000000, whose ASID value is H'10: >bc H'1000000 space virtual asid H'10 (RET) Related Items: BP, BD, BE, VC, VD, VE, and VS commands [Breakpoints] window [Break] dialog box
5.2.10 BREAKPOINT_DISPLAY: BD Description: Displays software breakpoints that have been set. Format: bd Table 5.11 BREAKPOINT_DISPLAY Command Parameter Parameter Type Description None Example: To display the software breakpoints that have been set: >bd (RET) H'00000110 physical enable H'0000011c virtual asid H'0 disable H'00000250 physical enable Note: The items displayed with this command differ according to the product. For the display specifications of each product, refer to the online help.
5.2.11 BREAKPOINT_ENABLE: BE Description: Enables or disables software breakpoints that have been set. Format: be
= space = asid Table 5.Related Items: BC, BD, BP, VC, VD, VE, and VS commands [Breakpoints] window [Break] dialog box 164
5.2.12 DEVICE_TYPE: DE Description: Displays the currently selected device. Format: de Table 5.
5.2.13 GO_OPTION: GP Description: Displays or sets the emulation mode. Format: Displays emulation mode. gp Sets emulation mode. gp = eml_mode Table 5.14 GO_OPTION Command Parameter Parameter Type Keyword Description Specifies the emulation mode. normal: Normal execution sequence1: Stops the user program only when the conditions are satisfied in the order of hardware breakpoints 2 to 1. Hardware breakpoints 1 and 2 must be set.
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) Note: The items displayed with this command differ according to the product. For the display specifications of each product, refer to the online help.
5.2.14 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 Table 5.15 JTAG_CLOCK Command Parameter Parameter Type Description Numerical value Sets one of the JTAG clock (TCK) frequency. (PCMCIA used: 3.75 MHz, 7.5 MHz, or 15 MHz) 3: 3.75 MHz 7: 7.5 MHz 15: 15 MHz (PCI used: 4.125 MHz, 8.25 MHz, or 16.5 MHz) 4: 4.125 MHz 8: 8.25 MHz 16: 16.
JTAG Clock 15MHz (when PCI used): To set the JTAG clock (TCK) frequency: >jck 16 (RET) JTAG Clock 16.5MHz To display the JTAG clock (TCK) frequency: >jck (RET) JTAG Clock 16.
5.2.15 MEMORYAREA_SET: MAS Description: Displays and sets memory area at command input, such as load, verify, save, memory display, or memory change. Format: Displays memory area. mas Sets memory area. mas [] = asid Table 5.16 MEMORYAREA_SET Command Parameters Parameter Type Keyword Description Sets memory area. normal: Does not set memory area. physical: Sets physical address area. virtual: Sets virtual address area.
Examples: To display a memory area for command input, such as load, verify, save, memory display, and memory change: >mas (RET) memoryarea_set virtual asid H'10 To set a memory area for command input, such as load, verify, save, memory display, and memory change, to a physical address area: >mas physical (RET) To set a memory area for command input, such as load, verify, save, memory display, and memory change, to a virtual address area whose ASID value is H'10: >mas virtual asid H'10 (RET) 171
5.2.16 REFRESH: RF Description: Updates the HDI memory information. Format: rf Table 5.
5.2.17 RESTART: RST Description: Restarts the emulator. The settings of breakpoints or trace acquisition conditions are not reset here. Format: rst Table 5.
5.2.18 STATUS: STS Description: Displays status information of the emulator. Format: sts Table 5.
5.2.19 STEP_INTERRUPT: SI Description: Sets or displays the enable or disable status of interrupts during step execution. If enabled, interrupts occur and stop at the top address in the interrupt routine. Format: Displays the enable or disable status of interrupts during step execution. si Sets the enable or disable status of interrupts during step execution. si Table 5.
5.2.20 TRACE_DISPLAY: TD Description: Displays the acquired trace information. The information to be acquired is the branch source and branch destination addresses when a branch is made during the user program execution. Format: td Table 5.21 TRACE_DISPLAY Command Parameter Parameter Type Description None Notes: 1. In some cases, the emulator address may be acquired. In such a case, the following message will be displayed at the place where the mnemonic or operand is displayed.
Example: To display trace information according to information acquired during user program execution: >td (RET) IP -D’xxxxxx (a) TYPE BRANCH DESTINATION ADDR 01000010 01000020 MNEMONIC JSR MOV.
5.2.21 UBC_MODE:UM Description: Sets or displays the current UBC state. Format: um [] Table 5.22 UBC_MODE Command Parameter Parameter Type Description Keyword Selects the UBC mode. EML: Uses the UBC as Break Condition by the emulator. USER: Releases the UBC to the user. (Break Condition cannot be used.) Note: When
5.2.22 VPMAP_CLEAR: VC Description: Clears the address translation (VP_MAP) table that is set in the emulator. Format: vc [
] Table 5.23 VPMAP_CLEAR Command Parameter Parameter Type Description Numerical value Sets the virtual start address of the VP_MAP table range to be cleared. Note: All contents in the VP_MAP table are cleared if is omitted.5.2.23 VPMAP_DISPLAY: VD Description: Displays the address translation (VP_MAP) table set in the emulator. Format: vd Table 5.24 VPMAP_DISPLAY Command Parameter Parameter Type Description None Example: To display the VP_MAP table: >vd (RET) 01000000 01010000 ENABLE 0100ffff 0101ffff 02000000 03000000 , , and represent the virtual start address, the virtual end address, and the physical start address, respectively.
5.2.24 VPMAP_ENABLE: VE Description: Enables or disables the setting of the address translation (VP_MAP) table in the emulator. Format: ve Table 5.25 VPMAP_ENABLE Command Parameter Parameter Type Description Keyword Enables or disables the setting of the VP_MAP table. enable: Enables the setting of the VP_MAP table. disable: Disables the setting of the VP_MAP table. Note: The setting of the VP_MAP table is disabled at the emulator initiation.
5.2.25 VPMAP_SET: VS Description: Sets the address translation (VP_MAP) table in the emulator. Format: vs Table 5.26 VPMAP_SET Command Parameters Parameter Type Description Numerical value Specifies the virtual start address to be set in the VP_MAP table in the page size units supported by the MMU. Setting a physical fixed area or an internal I/O area as a virtual address will result in an error.
Section 6 SH7641 E10A Emulator Specifications 6.1 Components of the Emulator The SH7641 E10A emulator supports the SH7641. Table 6.1 lists the components of the emulator.
Table 6.1 Components of the Emulator (HS7641KCM01H, HS7641KCM02H, HS7641KCI01H, or HS7641KCI02H) Classification Component Hardware Card emulator Appearance Insert PC Card Emulator H-UDI Micro Computer Development System PC Card Quantity 1 HITACHI (PCMCIA) Remarks HS7641KCM01H (PCMCIA: 14-pin type): Depth: 85.6 mm, Width: 54.0 mm, Height: 5.0 mm, Mass: 27.0 g HS7641KCM02H (PCMCIA: 36-pin type): Depth: 85.6 mm, Width: 54.0 mm, Height: 5.0 mm, Mass: 28.
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) User system E10A emulator Insert PC Card Emulator H-UDI Micro Computer Development System PC Card HITACHI User system connector Ferrite core PC card slot User interface cable Figure 6.
6.2 Pin Arrangement of the H-UDI Port Connector Figure 6.2 shows the pin arrangement of the H-UDI port connector (14 pins). CAUTION Note that the pin number assignment of the H-UDI differs from that of the connector manufacturer. Pin 1 mark H-UDI port connector 25.0 23.0 6 x 2.54 = 15.24 (2.54) Pin 8 Pin 1 Pin 14 Pin 7 0.45 Unit: mm Pin 1 mark Top view Pin No.
Notes: 1. Handling of the TCK, TMS, TDI, /TRST, /ASEBRKAK, and /ASEMD0 pins depends on the use conditions of the H-UDI as follows: (a) When the user system is used by connecting the emulator, the /ASEMD0 pin must be grounded. The TCK, TMS, TDI, /TRST, and /ASEBRKAK pins must be pulled up by a resistance of several kilo-ohms to protect the devices.
Figure 6.3 shows the pin arrangement of the H-UDI port connector (36 pins). Edge of the board (connected to the connector) +0.2 0 2 4 0.7 +0.1 0 36 1.905 1.1 H-UDI port connector 35 3 1 1.27 4.09 21.59 37.61 43.51 : Pattern inhibited area (Pin 1 mark) Unit: mm Top view Pin No. Signal Input/ Output *1 SH7641 Pin No.
Notes: 1. Handling of the TCK, TMS, TDI, /TRST, /ASEBRKAK, and /ASEMD0 pins depends on the use conditions of the H-UDI as follows: (a) When the user system is used by connecting the emulator, the /ASEMD0 pin must be grounded. The TCK, TMS, TDI, /TRST, and /ASEBRKAK pins must be pulled up by a resistance of several kilo-ohms to protect the devices.
6.3 User System Interface Circuit The emulator is connected to the user system via the user interface cable. Figure 6.4 shows the user system interface circuit of the emulator (HS7641KCM01H). 3Vcc JTAG controller (EPF6016ATC144-2) 74LVT244 4.7 k Y A TDI 3Vcc 4.7 k TDO 3Vcc 74LVT244 4.7 k A Y TCK 4.7 k 22 74LVT244 4.7 k 22 A Y TMS TMS 3Vcc 3Vcc 4.7 k TCK 3Vcc 3Vcc TDO To user system 74LVT244 4.7 k A Y 22 TDI 3Vcc 74LVT244 TRST 4.7 k 22 A Y TRST 3Vcc 74LVT244 URESET 4.
The user system interface circuits of the emulator (HS7641KCM02H) are shown. Figures 6.5 and 6.6 show the circuits of the H-UDI pin and AUD pin, respectively. JTAG controller (EPF6024ATC144-2) 3Vcc To user system 10 kΩ TDI TDO TCK TCK TMS TMS TDO TDI TRST TRST 3Vcc 10 kΩ URESET RESETP 3Vcc 10 kΩ ASEBRKAK ASEBRKAK Figure 6.
AUD logic circuit (EPF6024ATC144-2) 3Vcc To user system 10 kΩ AUDATA[3:0] AUDATA[3:0] 3Vcc 10 kΩ AUDSYNC AUDSYNC CLKIN 3Vcc 74LVT125 AUDCK A Y CLKOUT OE 10 kΩ AUDCK A Y Figure 6.
Figure 6.7 shows the user system interface circuit of the emulator (HS7641KCI01H). JTAG controller (EPF10K20RC208-3) 3Vcc 74LVT244 TDI To user system 4.7 kΩ Y A TDO 3Vcc 74LVT244 TCK A Y 22 Ω 4.7 kΩ TCK 3Vcc 74LVT244 TMS A Y 22 Ω 4.7 kΩ TMS 3Vcc 74LVT244 TDO A Y 22 Ω 4.7 kΩ TDI 3Vcc 74LVT244 TRST A Y 22 Ω 4.7 kΩ TRST 3Vcc 74LVT244 URESET Y A 22 Ω 4.7 kΩ RESETP 3Vcc 74LVT125 BRK A Y ACK Y A 22 Ω 4.7 kΩ ASEBRKAK Figure 6.
The user system interface circuits of the emulator (HS7641KCI02H) are shown. Figures 6.8 and 6.9 show the circuits of the H-UDI pin and AUD pin, respectively. JTAG controller (EPF10K10AQC208-3) To user system 74LVT244 22 Ω TCK A TCK Y 74LVT244 TRST A Y 22 Ω TRST 74LVT244 3Vcc A URESET Y Y A 4.7 kΩ RESETP 22 Ω 74LVT244 TDO A Y TDI Y A 22 Ω TDI 3Vcc 4.7 k 22 TDO 74LVT244 A Y 74LVT244 22 Ω TMS A TMS Y 3Vcc 74LVT125 22 BRK A Y ACK Y A 4.7 k ASEBRKAK Figure 6.
AUD logic circuit 3Vcc 74LVT244 AUDATA_I[3:0] To user system 4.7 kΩ AUDATA[3:0] Y A 74LVT125 AUDATA_O[3:0] A Y 3Vcc 74LVT244 AUDI 4.7 kΩ AUDSYNC Y A 74LVT125 AUDO A Y 3Vcc CDC351 CLKOUT OE A Y 4.7 kΩ AUDCK 74LVT125 Y A CLKIN OE Figure 6.
6.4 Differences between the SH7641 and the Emulator • When the emulator system is initiated, it initializes the general registers and part of the control registers as shown in table 6.2. The initial values of the actual SH7641 registers are undefined. Table 6.
Note: The memory must not be accessed or modified in sleep state. • Reset Signals The SH7641 reset signals are only valid during emulation started with clicking the GO or STEPtype button. If these signals are input from the user system in command input wait state, they are not sent to the SH7641. 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.
• 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.
6.5 Specific Functions for the SH7641 E10A Emulator The SH7641 E10A emulator supports the following useful function: • Performance measurement function Measures several performances, such as the cache-miss count. The SH7641 E10A emulator does not support the following functions: • MMU-related functions (The SH7641 does not mount the MMU.
6.5.2 Break Condition Functions In addition to BREAKPOINT functions, the emulator has Break Condition functions. In the HDI, three types of conditions can be set under Break Condition 1, 2, 3. Table 6.5 lists these conditions of Break Condition. Table 6.5 Types of Break Conditions Break Condition Type Description Address bus condition (Address) Breaks when the SH7641 address bus value or the program counter value matches the specified value.
Table 6.6 lists the combinations of conditions that can be set under Break Condition 1, 2, 3. Table 6.6 Dialog Boxes for Setting Break Conditions Type Dialog Box Address Data Bus Bus Condition Condition (Address) (Data) Bus State Condition (Bus Status) Count Condition (Count) Internal I/O Break [Break Condition 1] dialog box O O O O X [Break Condition 2] dialog box O X O X X [Break Condition 3] dialog box X X X X O Note: O: Can be set in the dialog box.
AUD Trace Functions: This function is operational when the AUD pin of the device is connected to the emulator. Table 6.9 shows the AUD trace acquisition mode that can be set in each trace function. Table 6.9 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.
To set the AUD trace acquisition mode, click the [Trace] window with the right mouse button and select [Acquisition] from the pop-up menu to display the [Trace 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 [Trace acquisition] dialog box. Figure 6.10 [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.
(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 6.11 [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.
Figure 6.12 [Window trace] Page Notes: 1. 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 ‘*’.
(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.
Table 6.10 [Trace] Window Display Contents Trace Type TYPE Column ADDR Column DATA Column Branch trace BRANCH Branch source address No display DESTINATION Branch destination address No display Window trace RD_MEMORY, WR_MEMORY Memory access address Memory access data Software trace S_TRACE Address at which the Trace (x) function is executed Register value Information LOST None None CPU-WAIT None None Notes: 1.
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. This function traces and displays the branch instructions. The branch source address and branch destination address for the eight latest branch instructions are displayed. See figure 6.10, [Trace mode] 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.
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 the [Configuration] dialog box, 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. If these commands are used, the message box shown in figure 6.14 is displayed. Figure 6.14 [HDI] Message Box 6.5.9 Performance Measurement Function The SH7641 E10A emulator supports the performance measurement function. 1.
Figure 6.15 [Performance 1] Dialog Box Measurement range One of the following ranges can be specified. This depends on the item selected for [Mode] in the [Performance 1] 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.
3. 212 When Break condition 1->2 or Break condition 2->1 is selected in [Mode] of the [Performance 1] 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 1] dialog box. Maximum four conditions can be specified at the same time. Table 6.12 shows the measurement items (Option names in table 6.12 are parameters for of the PERFORMANCE_SET command. They are displayed for CONDITION in the [Performance Analysis] window). Table 6.
Table 6.12 Measurement Item (cont) Selected Name Option URAM access stall US (Devices incorporating the U memory can only be measured.
2. Displaying the measured result The measured result is displayed in the [Performance Analysis] window or the PERFORMANCE_ANALYSIS command with hexadecimal (32 bits). Figure 6.16 [Performance Analysis] Window 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.
2. Functions that cannot be used while the profile function is being used (a) Performance measurement function The profile function is implemented by using the performance measurement function described in section 6.5.9, Performance Measurement Function. This function cannot be used when the profile function is enabled. (b) Step function When the profile function is enabled, do not use the step function. The profile data cannot be measured correctly.
6.5.11 Downloading to the Flash Memory Examples of connecting with and downloading to the flash memory (DA28F640J5-150) manufactured by Intel Corporation are described below. Note that a sample is provided in the \Fmtool folder within the folder in which the SH7641 E10A is installed. File configuration of the sample program is as follows: Table 6.
Figure 6.17 shows a connection of the flash memory using the sample program. SH7641 DA28F640J5-150 A0 A0 A22 to A1 A22 to A1 D15 to D0 DQ15 to DQ0 CE0 CS0 CE2 and CE1 RD OE# WE# WE0 5V BYTE# GND Figure 6.
6.5.12 Notes on HDI 1. 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 debugging of the created load module. Select the corresponding source file and click the [Open] button. 2. Source-level Execution Source file Do not display source files that do not correspond to the load module in the program window.
Variable name specification When a name other than a variable name, such as a symbol name or function name, is specified, no data is displayed. Example: The function name is main. main = 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 download. It is recommended that the File Load function ([Load Program...
File specification by commands The current directory may be altered by file specifications in commands. Absolute paths are recommended to be used to specify the files in a command file so that the current directory alteration is not affected. Example: FILE_LOAD C:\\HEW\\HDI5\\E10A\\7641\\TUTORIAL\\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.
14. 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 of each record. 15. [Memory] Window If the following memory contents are displayed, they will be incorrect. Word access from address 2n + 1 Longword access from address 4n + 1, 4n + 2, or 4n + 3 16.
• Verify In the [I/O Registers] window, the verify function of the input value is disabled. 18. Note on [Registers] Window Operation During Program Execution Although a dialog box is displayed in which the register contents can be changed by doubleclicking the [Registers] window, do not change the register contents during program execution. 19. Note on Radix in the [Register] Dialog Box The default input radix in the [Register] dialog box is hexadecimal irrespective of the Radix display.
[Breakpoints] window During user program execution, it is impossible to jump from the breakpoint to the source or address line on the [Source] or [Disassembly] window by using [Go to Source] in the popup menu displayed on the [Breakpoints] window. 21. Number of BREAKPOINT and [Stop At] Settings in the [Run...] Menu The maximum number of BREAKPOINTs and [Stop At] settings allowed in the [Run...] menu is 255. Therefore, when 255 BREAKPOINTs are set, specification by [Stop At] in the [Run...
27. Note on Using the [Run program] Dialog Box When [Run...] is selected from the [Run] menu to specify the stop address, there is the following note: When the breakpoint that has been set as Disable is specified as the stop address, note that the breakpoint becomes Enable when the user program stops. 28. Memory Test Function This product does not support the memory test function, which is used by selecting [test] from the [memory] menu. 29.
226
SH7641 E10A Emulator User's Manual Publication Date: Rev.1.00, June 26, 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.
SH7641 E10A Emulator User’s Manual 1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa 211-8668 Japan REJ10B0010-0100H
