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.
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 1st 2003. These operations include microcomputer, logic, analog and discrete devices, and memory chips other than DRAMs (flash memory, SRAMs etc.) Accordingly, although Hitachi, Hitachi, Ltd.
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.
User’s Manual H8S/2378F E10A Emulator User’s Manual Rev.1.0 2002.
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 with third party’s rights, including intellectual property rights, in connection with use of the information contained in this document. 2. Products and product specifications may be subject to change without notice.
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 Hitachi, Ltd. excluding all subsidiary products.
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, which Hitachi, upon inspection, shall determine to be defective in material and/or workmanship. The foregoing shall constitute the sole remedy for any breach of Hitachi's 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.
CAUTION This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
VIII
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 Hitachi’s original microprocessor.
Related Manuals: • Supplementary Informations • Hitachi Debugging Interface User's Manual (HS6400DIIW5SE) • H8S, H8/300 Series C/C++ Compiler, Assembler, Optimizing Linkage Editor User's Manual • Hardware Manual for each MCU • Programming Manual for each MCU Notes: 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.15 Break Function.................................................................................................................. 51 3.15.1 Software Break Function ..................................................................................... 51 3.16 Hardware Break Function ................................................................................................. 57 3.17 Trace Function .........................................................................................................
Section 6 H8S/2378F E10A Emulator Specifications........................................ 119 6.1 6.2 6.3 6.4 Overview of the Emulator.................................................................................................119 Pin Arrangement of the Hitachi-UDI Port Connector....................................................... 120 Differences between the MCUs and the Emulator............................................................ 125 The H8S/2378F E10A Emulator Functions ....................
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 into the Host Computer............................... 11 Figure 2.3 Inserting the PCI Card Emulator into the Host Computer......................
Figure 3.14 [Program] Window (Break Status) ......................................................................... 36 Figure 3.15 [System Status] Window ........................................................................................ 37 Figure 3.16 [Breakpoints] Window ........................................................................................... 39 Figure 3.17 [Open Memory Window] Dialog Box....................................................................40 Figure 3.
Figure 4.10 [Break condition 1] Dialog Box ............................................................................. 86 Figure 4.11 [condition] Page ..................................................................................................... 89 Figure 4.12 [Trace] Window ..................................................................................................... 92 Figure 4.13 [System Status] Window .......................................................................................
Tables Table 1.1 Environmental Conditions ......................................................................................... 4 Table 1.2 Operating Environments............................................................................................ 5 Table 2.1 Recommended Connector.......................................................................................... 12 Table 3.1 Tutorial Program: Configuration and Parts ...............................................................
Table 5.17 TRACE_DISPLAY Command Parameter............................................................... 118 Table 6.1 Components of the Emulator (HS2378KCM01H or HS2378KCI01H) .................... 119 Table 6.2 Unavailable Pin Functions......................................................................................... 124 Table 6.3 Register Initial Values at Emulator Power-On .......................................................... 125 Table 6.4 Type Name and Driver ...............................
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 Hitachi, 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 Hitachi-UDI (user debug interface) port*, to the user system.
User system interface cable PCI card emulator H8S/xxxx Insert into the PCI slot User system Host computer (PC with 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 interface. • Realtime emulation Realtime emulation of the user system is enabled at the maximum operating frequency of the CPU.
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. Protect the emulator from excessive impacts and stresses. For details, refer to section 1.2, Environmental Conditions. 4.
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 damage the user system and the emulator product. The USER PROGRAM will be LOST. 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 NT , or Windows 2000 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 Hitachi 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 Check the components against the component list Component list Turn on the host computer Install the HDI When the emulator is used first. Section 2.
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 NT 4.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 Host Computer with the Card Emulator. 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 Host Computer with the Card Emulator. 5.
2.3 Connecting the Host Computer with the Card Emulator Insert the card emulator into the PCMCIA TYPE II slot or the PCI slot of the host computer (figures 2.2 and 2.3). Note: Be sure to install the HDI before the card emulator is inserted. Figure 2.2 Inserting the PCMCIA Card Emulator into the Host Computer Figure 2.3 Inserting the PCI Card Emulator into the Host Computer Use the procedure, described in section 2.
Note: When installing the PCI card emulator, note the following: 1. Turn off the host computer. 2. Insert the emulator into the PCI slot in parallel. 3. Screw in the emulator after confirming the connector and cable positions. 2.4 Connecting the Card Emulator with the User System (1) The connector must be installed to the user system. Table 2.1 shows the recommended connector for the emulator. Table 2.
Notes: 1. To connect the signals output from the connector, refer to the MCU pin alignment. 2. To remove the user system interface cable from the user system, pull the tab on the connector upward. 3. The range of communications that the emulator operates at is different according to the MCUs used. 4. Connect the signals from the connector as shown in section 6.2, Pin Arrangement of the Hitachi-UDI Port Connector.
2.5 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 the connector of the card emulator. 3. Connect the user system interface cable to the Hitachi-UDI port connector. 4. Power on the host computer and select [HDI for E10A H8Sxxxx] -> [Hitachi Debugging Interface] from the [Start] menu. Figure 2.
5. Power on the user system and 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 MCUs.) Figure 2.
7. Supply power to the user system. The subsequent procedures depend on the activation mode that was selected in step 5. 2.5.1 H8S/xxxx E10A Emulator Mode This mode is used for debugging in the emulator. 1. After the [System Clock] window appears, input the system clock frequency. This frequency value is used when writing and erasing flash memory in the emulator. Figure 2.8 [System Clock] Dialog Box 2. Set an eight-digit hexadecimal ID code as a security code for the flash memory.
Notes: 1. When the HDI is not linked up even if the above procedure has been executed, the driver will not be set correctly. Install drivers provided with the \SETUP directory in the CD-R according to the screen instructions. 2. If the user system interface cable is disconnected to the Hitachi-UDI port connector on the user system during user program execution, the following dialog box will be displayed. Figure 2.11 [H-UDI Connector Disconnected] Dialog Box 3.
(b) If the following dialog box is displayed, check that the Hitachi-UDI port connector on the user system is correctly connected. Figure 2.13 [Check the connection] Dialog Box (c) If the following dialog box is displayed, the MCU may not correctly operate. Check if there are reasons for illegal MCU operation. Figure 2.14 [COMMUNICATION TIMEOUT ERROR] Dialog Box Figure 2.
4. If the driver is not correctly connected, the following dialog box will be displayed. Figure 2.16 [Unable to restore the previous driver settings] Dialog Box The [E10A Driver Details] dialog box is displayed when the [OK] button is clicked. Select the correct driver. For details, refer to section 6.4.1, Emulator Driver Selection. 2.5.2 Writing H8S/xxxx E10A Flash memory Mode In this mode the emulator is used as a flash memory writer.
2. When the [Load Program] window appears, specify a user program to be downloaded. Click the [Open] button to start downloading. Figure 2.18 [Load Program] Dialog Box 3. When the program has been downloaded, the memory area that the checksum value and the program code have been written appears. Figure 2.19 Checksum Value after Downloading the Program Figure 2.
4. The [Continue] window appears. When the [OK] button is clicked, a message is displayed to request that power be supplied. Turn off the power, exchange the MCU, and supply power. Repeat operations 1 to 3 until the [Exit] button is clicked. When the [Exit] button is clicked, the HDI is terminated. Figure 2.21 [Continue?] Window Notes: 1. When the HDI does not link up, and the above procedures have been executed, the driver setting must be incorrect.
2.6 Ending the HDI Power off the emulator 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.24 [Exit HDI] Dialog Box 2. Then, the [Save session] dialog box is displayed. If necessary, click the [Yes] button to save session. After saving session, the HDI ends. If not necessary, click the [No] button to end the HDI. Figure 2.25 [Save session] Dialog Box 3. Turn the user system off.
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.
Section 3 Tutorial 3.1 Introduction The following describes the main functions of the emulator 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.
3.2 Running the HDI To run the HDI, select [HDI for E10A H8Sxxxx] -> [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. Program 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 following MCU conditions must be set up on the emulator before downloading the program: • Device type • Execution mode The following describes how to set up the emulator for the tutorial programs. 3.5 Setting the [Configuration] Dialog Box • Select [Configure Platform...] from the [Setup] menu to set configuration. The [Configuration] dialog box is displayed. Figure 3.
Set options as follows: Table 3.2 Setting the [Configuration] Dialog Box Option Value Mode H8S/xxxx (default) Emulation mode Normal (normal execution, default) Step option (Disables interrupt during single step execution) Disables interrupts during single step execution (default) JTAG clock 4.125 MHz (default) Operating Mode Operating mode determined by setting the mode pin (default) Flash memory synchronization Disable (default) • Click the [OK] button to set any changes in the configuration.
3.6 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 the [Offset] edit box and [File name] list box as shown in figure 3.4 and click the [Open] button. Figure 3.4 [Load Program] Dialog Box When the file has been loaded, the following dialog box displays information about the memory areas that have been filled with the program code.
3.6.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.
• Select [Sort.c] and click the [Open] button. The [Program] window is displayed. Figure 3.7 [Program] Window (Displaying the Source Program) • If necessary, select the [Font...] option from the [Customize] submenu on the [Setup] menu to select a clear font and size. Initially the [Program] window shows the start of the main program, but the user can use the scroll bar to scroll through the program to see the other statements.
3.7 Setting the Software Breakpoint A breakpoint is one of the easy debugging functions. The [Program] 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.8 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 • 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. Figure 3.
keyboard, or double-click the value area with the mouse. The following dialog box is then displayed. Figure 3.11 [Register] Dialog Box (ER7) • Set the value of the stack pointer to H’FFFC00 in this tutorial program, and click the [OK] button.
3.9 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.12 [Go] Button • Or, select [Reset Go] from the [Run] menu or click the [Reset Go] button on the toolbar. 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 on-line help.
The [System Status] window displays the following items in each page. Table 3.3 Contents of the [System Status] Window 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 MCU name.
3.10 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.11 Viewing Memory The user can view the contents of a memory block 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.12 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 [Program] window to position the cursor. • Click the [Program] 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 popup 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 long-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.13 Stepping Through a Program The HDI provides a range of step menu commands that allow efficient program debugging. Table 3.4 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.13.1 Executing [Step In] Command The [Step In] steps into the called function and stops at the first statement of the called function. • To step through the sort function, select [Step In] from the [Run] menu, or click the [Step In] button in the toolbar. Figure 3.24 [Step In] Button Figure 3.25 [Program] Window (Step In) • The highlighted line moves to the first statement of the sort function in the [Program] window.
3.13.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. Figure 3.26 [Step Out] Button Figure 3.27 [Program] 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 [Program] Window (Step In −> Step In) • The value of max displayed in the [Watch] window is changed to the maximum data value.
3.13.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 [Program] 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.31 [Program] Window (Step Over) When the last statement of the change function is executed, the data of variable a, which is displayed in the [Watch] window, is sorted in descending order.
3.14 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. • Select [Step In] from the [Run] menu to execute a single step.
3.15 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 1] dialog box. An overview and setting of the break function are described below. 3.15.1 Software Break Function The emulator can set up to 255 software breakpoints. Setting a software breakpoint is described below. • Select [Breakpoints] from the [View] menu.
The [Break] dialog box is displayed. The [Point] page is displayed as a default. Figure 3.34 [Point] Page ([Break] Dialog Box) • Click the [Add...] button to display the [Breakpoint] dialog box.
• Enter H'10a4 to the [Value] edit box. Figure 3.35 [Breakpoint] Dialog Box • Click the [OK] button.
The [Break] dialog box is displayed. The address set in the value field of [Breakpoint] is displayed. Figure 3.36 [Point] Page ([Break] Dialog Box) (After Software Breakpoint Setting) • Click the [Close] button.
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. • Click the [Reset Go] button. The program runs, and stops at the set breakpoint. Figure 3.
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 to the product. For the items that can be displayed, refer to the on-line help.
3.16 Hardware Break Function A method is given below in which the address bus condition and the read cycles for the state 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.41 [Condition] Page ([Break] Dialog Box) Up to two breakpoints can be set independently for the hardware break condition. In this example, set the hardware break condition for Break condition 1. Note: Note that the number of hardware break conditions differs according to the product.
• Highlight the first point in the [Break condition] list box. • Click the [Edit...] button. The [Break condition 1] dialog box is displayed. • Clear the [Don't care] check box in the [Address] page. • Select the [Only program fetched address after] radio button and enter H'108C as the value in the [Address] edit box. Figure 3.42 [condition] Page ([Break condition 1] Dialog Box) Note: The items that can be set in this window differ according to the product.
Figure 3.43 [Break] Dialog Box (After Hardware Break Condition Setting) Note: Note that the number of hardware break conditions differs according to the product. For the number that can be specified for each product, refer to the on-line help. • Click the [Close] 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'108C is accessed in a read cycle. Figure 3.44 [Breakpoints] Window ([Break condition 1] Setting) • Close the [Breakpoints] window. • Click the [Reset Go] button.
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.46 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 on-line help.
3.17 Trace Function The trace function of the E10A emulator is described. The branch source 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. Run the program as shown in the example of section 3.15.1, Software Break Function. The trace results are displayed in the [Trace] window after the program execution is completed. Figure 3.
3.18 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.
66
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, an 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 Registers Labels Locals Memory... Performance Analysis Profile-List Profile-Tree Registers Source… Status Trace Watch Localized Dump Window Run Menu Reset CPU Go Reset Go Go to Cursor Set PC To Cursor Run… Step In Step Over Step Out Step… Halt 68 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 O O O O O O This Manual 3.10, 3.
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, H8S/xxxx 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.
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 the emulator operation conditions. 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 operational conditions for the emulator. The MCU name is displayed, the emulation mode and interrupts during step execution are set, the JTAG clock (TCK) is displayed and set, and the driver is selected. Window: Figure 4.2 [General] Page ([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 on-line help.
Description: Table 4.3 [General] Page Options Option Description [Mode] combo box Displays the MCU name. [Emulation mode] combo box Selects the emulation mode at user program execution. Select Normal to perform normal emulation. Select No Break to disable breakpoint settings. [Step option] combo box Enables or disables interrupts during step execution. Disables interrupts during single step execution: Interrupts during step execution are masked.
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.
4.2.2 [E10A Driver Details] Dialog Box When the [OK] button is clicked, the [E10A Driver Details] dialog box will appear to select the driver software used by the interface to the emulator. Since the emulator is reinitialized after this dialog box is closed, it cannot be cancelled. Figure 4.4 [E10A Driver Details] Dialog Box Table 4.4 shows each option. Table 4.4 [E10A Driver Details] Dialog Box Option Option Description [Driver] combo box Selects the driver to connect the HDI with the emulator.
When the PCMCIA card emulator is used, [E10A PC Card Driver 5] is selected. When the PCI card emulator is used, [E10A PCI Card Driver 5] is selected. Note: When the HDI is not linked up even if the above procedure has been executed, the driver may not be set correctly. Install drivers provided with the \SETUP directory in the CD-R according to the screen instructions. Related Items: [Configuration] dialog box [General] page 4.2.
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] Indicates whether the break condition is enabled or disabled. Symbol l or m shows that the break condition is enabled. [File/Line] Displays the file name and line number where the breakpoint is set. [Symbol] Displays the symbol corresponding to the breakpoint address.
4.2.4 [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.7. Table 4.7 [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 [Close] button will close this dialog box. The [Apply] button is not supported.
(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.8 [Point] Page Options Option Description [Breakpoint] list box Lists the software breakpoints currently being set. The display contents are as follows: [Add...] button Sets software breakpoints. Clicking this button displays the [Breakpoint] dialog box. [Edit...] button Changes the software breakpoint selected in the [Breakpoint] list box. Clicking this button displays the [Breakpoint] dialog box.
(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.8 [Condition] Page ([Break] Dialog Box) Note: Note that the number of hardware break conditions differs according to the product. For the number that can be specified for each product, refer to the on-line help.
Description: Table 4.9 [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.5 [Breakpoint] Dialog Box Function: This dialog box sets software breakpoints. Window: Figure 4.9 [Breakpoint] 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 on-line help.
Description: The [Address] page options are as follows: Table 4.10 [Address] Page Options Option Description [Value] edit box Sets a breakpoint address with a number or a symbol. Clicking the [OK] button enables breakpoints to be set. If the [Cancel] button is clicked, this dialog box is closed without setting breakpoints.
4.2.6 [Break condition] Dialog Box Function: This dialog box sets hardware break conditions. Window: Figure 4.10 [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 on-line help.
Description: The [Break condition] dialog box consists of the [condition] page. Sets the conditions for halting the program. Contents to be set by this page are described in section 4.2.7, [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.7 [Break condition] Dialog Box Pages The [Break condition] dialog box page allows 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 those in table 4.11. For details, refer to section 6.5.2, Hardware Break Functions. Table 4.
(1) [condition] Page Function: This page sets the address bus, data bus, and read/write cycle conditions. Window: Figure 4.11 [condition] Page Note: The items that can be set in this window differ according to the product. For the settings for each product, refer to the on-line help.
Description: The [Address] group box sets the address bus conditions. Table 4.13 [Address] Group Box 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 after] radio button Sets a break after prefetched address execution as break conditions. [Address] edit box Sets the address bus value with a number or a symbol.
The [Read/Write] group box sets the read/write cycle conditions. Table 4.16 [Read/Write] Group Box Options Option Description [Read/Write] radio button Sets the read/write cycle conditions as break conditions. [Read] radio button Sets read cycles as break conditions. [Write] radio button Sets write cycles as break conditions.
4.2.8 [Trace] Window Function: This window displays the trace buffer contents. The contents are displayed in both C and assembly languages to simplify debugging. Window: Figure 4.12 [Trace] Window Note: This function differs according to the product. For the number that can be specified for each product, refer to the on-line help.
Description: This window displays the trace buffer contents. The items listed in table 4.17 are displayed. Table 4.17 [Trace] Window Display Items Item Description [IP] Displays the instruction pointer (signed decimal). [TYPE] Displays the branch source. BRANCH: Branch source [ADDR] Displays the branch source address. [MNEMONIC] Displays the execution instruction mnemonic. [OPERAND] Displays the execution instruction operand.
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.13 [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 on-line help.
Description: The items listed in the following table are displayed in the [System Status] window. Table 4.18 [System Status] Window Display Items Page Item Description [Session] Target System Displays whether the emulator is 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 MCU name.
96
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.
5.1.3 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 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 BREAKCONDITION_ CLEAR BCC Clears hardware breakpoints that have been set. 2 BREAKCONDITION_ DISPLAY BCD Displays hardware breakpoints that have been set. 3 BREAKCONDITION_ ENABLE BCE Enables or disables hardware breakpoints that have been set. 4 BREAKCONDITION_ SET BCS Sets hardware breakpoints. 5 BREAKPOINT BP Sets software breakpoints.
5.2.1 BREAKCONDITION_CLEAR: BCC Description: Clears hardware breakpoints that have been set. Format: bcc [] = channel Table 5.
5.2.2 BREAKCONDITION_DISPLAY: BCD Description: Displays hardware breakpoints that have been set. The display contents include enable or disable of the setting, and setting conditions. Format: bcd [] = channel Table 5.
5.2.3 BREAKCONDITION_ENABLE: BCE Description: Enables or disables hardware breakpoints that have been set. Format: bce [] = channel Table 5.4 BREAKCONDITION_ENABLE Command Parameter Parameter Type Description Keyword Enables or disables hardware breakpoint settings. Set either of the following: enable: Enables hardware break settings. disable: Disables hardware break settings.
5.2.4 BREAKCONDITION_SET: BCS Description: Sets hardware breakpoints. Note: The function will be different according to the MCUs used. For functions of each emulator product, refer to section 6.4.2, Hardware Break Functions. Format: bcs
Table 5.5 BREAKCONDITION_SET Command Parameters Parameter Type Description
Numerical value, character string Numerical value or symbol representing an address bus value Keyword Address bus access conditions pcafter: The address bus is targeted during instruction fetch cycles. Breaks after the instruction at the address set by the parameter is executed.Examples: To set the following conditions as a hardware breakpoint: Address condition: An address bus value of H'1000, Data condition: A data bus value of H'55 and lower 8-bit byte access, Read/write cycle condition: Read cycle. >bcs address 1000 data 55 lbyte direction read (RET) To set the following conditions as a hardware breakpoint: Address condition: An address bus value of H'2000 and instruction fetch cycle.
5.2.5 BREAKPOINT: BP Description: Sets software breakpoints. Note: The function will be different according to the MCUs used. Format: bp
Table 5.6 BREAKPOINT Command Parameter Parameter Type Description Numerical value, character string Breakpoint value set by numerical value or symbol When an odd address is set, the address is rounded down to an even address. Note: The parameters for this command vary with the product.5.2.6 BREAKPOINT_CLEAR: BC Description: Clears software breakpoints that have been set. Format: bc [
] Table 5.7 BREAKPOINT_CLEAR Command Parameter Parameter Type Description Numerical value, character string Breakpoint value set by numerical value or symbol Note: When no parameters are set, all software breakpoints are cleared. Note: The parameters for this command vary with the product. For the specifications of each product, refer to the on-line help.5.2.7 BREAKPOINT_DISPLAY: BD Description: Displays software breakpoints that have been set. Format: bd Table 5.8 BREAKPOINT_DISPLAY Command Parameter Parameter Type Description None Example: To display the software breakpoints that have been set: >bd (RET) The display format is as follows: >bd H'00000110 Enable H'0000011c Disable H'00000250 Enable Note: The items displayed with this command vary with the product. For the display specifications of each product, refer to the on-line help.
5.2.8 BREAKPOINT_ENABLE: BE Description: Enables or disables software breakpoints that have been set. Format: be
Table 5.9 BREAKPOINT_ENABLE Command Parameters Parameter Type Description Numerical value, character string Breakpoint value set by numerical value or symbol Keyword Enables or disables breakpoints. Set either of the following: enable: Enables breakpoints. disable: Disables breakpoints.5.2.9 DEVICE_TYPE: DE Description: Displays MCU type currently selected. Format: de Table 5.
5.2.10 GO_OPTION: GP Description: Sets or displays the emulation mode during user program execution. Format: gp Displays emulation mode for user program execution. gp = eml_mode Sets emulation mode for user program execution. Table 5.11 GO_OPTION Command Parameter Parameter Type Keyword Description Specifies the emulation mode.
5.2.11 JTAG_CLOCK: JCK Description: Displays or sets the JTAG clock (TCK) frequency. Format: JCK Displays the JTAG clock (TCK). JCK Sets the JTAG clock (TCK). Table 5.12 JTAG_CLOCK Command Parameter Parameter Type Description Numerical value Sets one of the JTAG clock (TCK) frequency. (PCMCIA used: 0.937 MHz, 1.875 MHz, 3.75 MHz, 7.5 MHz, or 15 MHz) 1: 15 MHz 2: 7.5 MHz 3: 3.75 MHz 4: 1.875 MHz 5: 0.937 MHz (PCI used: 1.031 MHz, 2.062 MHz, 4.125 MHz, 8.25 MHz, or 16.
Examples: (when PCMCIA used): To set the JTAG clock (TCK) frequency: >JCK 1 (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) frequency: >JCK 1 (RET) JTAG Clock 16.5MHz To display the JTAG clock (TCK) frequency: >JCK (RET) JTAG Clock 16.
5.2.12 REFRESH: RF Description: Updates the HDI memory information to the latest contents. Format: rf Table 5.
5.2.13 RESET: RE Description: Resets the H8S/xxxx. The breakpoint settings are retained. After the reset, the registers will be in the same state as when power is supplied. Format: re Table 5.
5.2.14 STATUS: STS Description: Displays emulator status information. Format: sts Table 5.
5.2.15 STEP_INTERRUPT: SI Description: Sets or displays the enable or disable status of interrupts during step execution. When interrupts occur when they are disabled, execution stops at the top address of the interrupt routine. Format: si Displays the enable or disable status of interrupts during step execution. si Sets the enable or disable status of interrupts during step execution. Table 5.
5.2.16 TRACE_DISPLAY: TD Description: Displays acquired trace information. Format: td Table 5.
Section 6 H8S/2378F E10A Emulator Specifications 6.1 Overview of the Emulator The H8S/2378F E10A emulator supports the H8S/2377F and H8S/2367F. The MCU operating modes 4 and 7 are supported and realtime emulation can be performed. Table 6.1 lists the components of the emulator. Table 6.
6.2 Pin Arrangement of the Hitachi-UDI Port Connector Figure 6.1 shows the pin arrangement of the Hitachi-UDI port connector. CAUTION Note that the pin number assignment of the Hitachi-UDI port connector differs from that of the connector manufacturer. Signal Pin No.
Figure 6.2 shows an example of connecting the user system to the emulator. 14-pin connector with a 2.54-mm pitch (3M Limited: 2514-6002) Vcc Pulls-up at 4.7 k H8S/2377F, H8S/2367F 11 EMLE 1 PG4 2 P53 3 #WDTOVF 5 PG5 6 PG6 4 User logic 7 #RES 8 to 10 12 to 14 E10A pin No. User system · #RES of pin 4 of the Hitachi-UDI port connector is a signal line in which the emulator outputs signals to the MCU.
Notes: 1. The emulator uses #WDTOVF, P53, and PG4 to PG6 in the H8S/2377F and H8S/2367F. Pull up the emulator and MCU pins and connect them to the user system. Peripheral functions that are shared by these pins cannot be used. H8S/2377F, H8S/2367F Hitachi-UDI port connector Vcc 4.7 k Pins 1, 2, 3, 5, and 6 Figure 6.3 Connection of Emulator 2. The EMLE pin in the H8S/2377F and H8S/2367F must be pulled up when connecting with the emulator, and connected to GND when not connecting with the emulator.
3. #RES of pin 4 of the Hitachi-UDI port connector is a signal line in which the emulator outputs signals to the MCU. #RES of pin 7 of the Hitachi-UDI port connector is a signal line in which the emulator monitors the #RES signal of the MCU. The #RES must be pulled up before it is connected to pin 7 of the Hitachi-UDI port connector. Vcc 4.7 k User logic H8S/2377F, H8S/2367F Hitachi-UDI port connector Vcc Pin 4 4.7 k Pin 7 Figure 6.5 Connection of #RES Pin 4.
7. When H8S/2377F and H8S/2367F are connected to the emulator, the following pin functions cannot be used. Table 6.2 Unavailable Pin Functions H8S/2377F H8S/2367F P53 and PG4 to PG6 P53 and PG4 to PG6 #WDTOVF #WDTOVF #IRQ3 #IRQ3 #ADTRG #ADTRG #BREQ, #BACK, and #BREQ0 #BREQ, #BACK, and #BREQ0 − #CS4 Note: The symbol “#” means that the signal is active-low.
6.3 Differences between the MCUs and the Emulator 1. When the emulator system is initiated, it initializes the general registers and part of the control registers as shown in table 6.3. Table 6.3 Register Initial Values at Emulator Power-On Register When Using H8S/2377F and H8S/2367F PC Reset vector value in the vector address table ER0 to ER6 Undefined ER7 (SP) H'FFC000 CCR 1 for I mask, and others undefined EXR H’07 2.
6.4 The H8S/2378F E10A Emulator Functions Notes: 1. Do not use an MCU that has been used for debugging. 6.4.1 2. If the flash memory is rewritten many times, and the emulator is left for a few days, data may be lost due to retention problems. 3. If the flash memory is rewritten many times, the data will not be erased. If an error message is displayed, exchange the MCU for a new one. Emulator Driver Selection Table 6.4 shows drivers which can be selected in the [E10A Driver Details] dialog box.
Table 6.6 Conditions Set in [Break condition] Dialog Box Condition Dialog Box Address Bus Condition O O [Break condition 1] [Break condition 2] Data Condition Read or write condition O O O O Note: O: Can be set by checking the radio button in the dialog box. Table 6.7 lists the combinations of conditions that can be set by the BREAKCONDITION_SET command. Table 6.
6.4.3 Notes on Setting the [Breakpoint] Dialog Box 1. When an odd address is set, the address is rounded down to an even address. 2. A software break is accomplished by replacing instructions. Accordingly, it can be set only to the flash memory or the RAM area. However, a software break cannot be set to the following addresses: • An area other than flash memory or RAM • An instruction in which Break Condition is satisfied 3. During step execution, a software breakpoint is disabled. 4.
6.4.4 Trace Function The emulator uses the branch-instruction trace and bus trace functions in the MCU, and acquires a trace by operating the user program in realtime. The branch-instruction trace function displays the branch-source address, the mnemonic, and the operand. The bus trace function displays and searches the information on the address bus, data bus, memory access, interrupt, and bus cycle, the mnemonic, and the operand. The acquisition conditions can also be set.
(2) Displaying a Trace in the Bus Trace Function The contents of the trace buffer in table 6.9 are displayed in the [Trace] window. Table 6.
(3) Searching a Trace in the Bus Trace Function The emulator supports two types of trace search function listed in table 6.10. Table 6.10 Trace Search Function Function Description Trace Filter Displays all the information that matches the conditions specified by all the trace data. Trace Find Jumps to the information that matches the conditions specified by all the trace data.
Table 6.13 [Bus status] Group Box Options Option Description [Don’t care] check box Indicates that no bus condition is set. [DMAC] check box Sets a DMAC bus cycle as a display condition. [DTC] check box Sets a DTC bus cycle as a display condition. [PROG] check box Sets a CPU instruction fetch cycle as a display condition. [DATA] check box Sets a CPU data access cycle as a display condition. [REFRESH] check box Sets a refresh cycle as a display condition. Table 6.
(ii) Trace Find Function The emulator jumps to the information that matches the conditions specified by all the trace data on the [Trace] window. The search function is set in the [Trace Filter] dialog box. The conditions to be set are the same as those of the Trace Filter function. (4) Commands for the Trace Function The emulator supports the commands for the trace function listed in table 6.17. The contents of the trace buffer are displayed in the [Trace] window. Table 6.
Example: To display the acquired trace information: td (RET) The display format of the branch trace information is as follows: >td IP -D’xxxx -D’xxxx TYPE BRANCH BRANCH ADDR 00100100 00100200 MNEMONIC JSR JMP OPERAND @ER0 @ER1 (a) (b) (c) (d) (e) (a) Instruction pointer (signed decimal) (b) Type of branch source BRANCH: Branch source (c) Address of instruction word (d) Instruction mnemonic (e) Instruction operand The display format of the bus trace information is as follows: >td start -10 end –5
(ii) TRACE_MODE: TM Description: Displays or sets the acquisition mode of the trace information. Format: tm Displays the acquisition mode of the trace information. tm [] [] [] Sets the acquisition mode of the trace information. = type = bus mode = cycle = address Table 6.19 TRACE_MODE Command Parameter Parameter Type Description Keyword Sets a type of traces to be acquired.
Example: To disable acquiring the DMAC cycle in the bus trace: tm type bus cycle dmac (RET) The display format of the setting state of the trace acquisition mode is as follows: >tm (RET) type = bus cycle dmac 136
(iii) TRACE_SEARCH: TS Description: Searches and displays the trace information with the specified condition.
Table 6.20 TRACE_SEARCH Command Parameter Parameter Type Description
Numerical value, character string Sets the address value as a numeric or a symbol. Numerical value Sets a value of the data bus. Keyword Sets the access condition of the data bus. byte: Byte access word: Word access Keyword Sets the bus condition. dmac: The DMAC bus cycle is the search condition. dtc: The DTC bus cycle is the search condition.Example: To search and display the trace data of address H’00FF8000: ts address H’ff8000 (RET) When the data exists in the –70 cycle, the display format is as follows: >ts address H’ff8000 CYCLE ADDRESS LABEL MNEMONIC OPERAND DATA R/W AREA STATUS CLOCK IRQ *-D'0075 xxxxxxxx xxx xxxxx xxx xxxx xx xxxx xxxxx x x *-D'0074 xxxxxxxx xxx xxxxx xxx xxxx xx xxxx xxxxx x x *-D'0073 xxxxxxxx xxx xxxxx xxx xxxx xx xxxx xxxxx x x *-D'0072 xxxxxxxx xxx xxxxx xxx xxxx xx
6.4.5 1. Notes on HDI 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 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.
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...] selected from the [File] menu) is used to load the S-type file.
Example: FILE_LOAD C:\\HEW\\HDI5\\E10A\\2378F\\TUTORIAL \\TUTORIAL.ABS 9. Note on Initiating HDI When the emulator is initiated by using another card emulator after it has been initiated by using the PCI card emulator, delete the [TARGET] line from the C:\windows\HDI.INI file. 10. Usage with Another HDI Automatic load of session files Since the emulator cannot use another HDI, re-install this HDI whenever another HDI has been previously installed is used.
16. [I/O Registers] window Display and modification Do not change values in the [I/O Registers] window because the emulator uses the address break controller. Note that the E10A emulator does not support the display of the invalid module or bit information in the [I/O Registers] window (described in section 8, Displaying Variables, in the Hitachi Debugging Interface User's Manual). Verify In the [I/O Registers] window, the verify function of the input value is invalid. 17.
20. Number of Software Breakpoint and [Stop At] Settings in the [Run...] Menu The maximum number of software breakpoints and [Stop At] settings allowed in the [Run...] menu is 255. Therefore, when 255 software breakpoints are set, specification by [Stop At] in the [Run...] menu becomes invalid. Use the software breakpoints and [Stop At] in the [Run...] menu with 255 or less total settings. 21.
28. Note on Starting or Halting User Program When the user program execution is started or halted, the program for the H8S/2378F E10A emulator will write or read the flash memory. The write or read processing will take about a maximum of 40 seconds. 29.
33. Watchdog Timer When the emulator is connected to operate the watchdog timer (WDT) during using the H8S/2377F and H8S/2367F, the WDT continues operation during a break. • When a counter value overflows during a break in the watchdog timer mode: • When a counter value overflows during a break in the interval timer mode: An internal reset signal is generated when the internal LSI is reset. An interrupt request is generated, but it is suspended during a break.
