Renesas H8S/2378F User Manual
  1. Manuals
  2. Brands
  3. Renesas Manuals
  4. Software
  5. H8S/2378F
  6. User manual
Renesas H8S/2378F User Manual

Renesas H8S/2378F User Manual

Emulator
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
To our customers,
Old Company Name in Catalogs and Other Documents
st
On April 1
, 2010, NEC Electronics Corporation merged with Renesas Technology
Corporation, and Renesas Electronics Corporation took over all the business of both
companies. Therefore, although the old company name remains in this document, it is a valid
Renesas Electronics document. We appreciate your understanding.
Renesas Electronics website:
Issued by: Renesas Electronics Corporation (http://www.renesas.com)
Send any inquiries to http://www.renesas.com/inquiry.
http://www.renesas.com
st
April 1
, 2010
Renesas Electronics Corporation

Advertisement

Table of Contents
loading

Related Manuals for Renesas H8S/2378F

Summary of Contents for Renesas H8S/2378F

  • Page 1 On April 1 , 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding.
  • Page 2 Renesas Electronics. Renesas Electronics shall not be in any way liable for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for an application categorized as “Specific”...
  • Page 3 Accordingly, although Hitachi, Hitachi, Ltd., Hitachi Semiconductors, and other Hitachi brand names are mentioned in the document, these names have in fact all been changed to Renesas Technology Corp. Thank you for your understanding. Except for our corporate trademark, logo and corporate statement, no changes whatsoever have been made to the contents of the document, and these changes do not constitute any alteration to the contents of the document itself.
  • Page 4 (iii) prevention against any malfunction or mishap. Notes regarding these materials 1. These materials are intended as a reference to assist our customers in the selection of the Renesas Technology Corporation product best suited to the customer's application; they do not convey any license under any intellectual property rights, or any other rights, belonging to Renesas Technology Corporation or a third party.
  • Page 5 H8S/2378F E10A Emulator User’s Manual Rev.1.0 2002.10...
  • Page 6 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.

  • Page 7: Important Information

    IMPORTANT INFORMATION • READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference. Do not attempt to use the emulator product until you fully understand its mechanism. Emulator Product: Throughout this document, the term "emulator product" shall be defined as the following products produced only by Hitachi, Ltd.

  • Page 8: Limited Warranty

    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.
  • Page 9 State Law: Some states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages, so the above limitation or exclusion may not apply to you. This warranty gives you specific legal rights, and you may have other rights which may vary from state to state.

  • Page 10: 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.
  • Page 11 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.
  • Page 12 Warnings on Emulator Usage Be sure to read and understand the warnings below before using this emulator. Note that these are the main warnings, not the complete list. Always switch OFF the host computer and user system before connecting or 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.
  • Page 13 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.
  • Page 14 VIII...
  • Page 15 Thank you for purchasing the E10A emulator. READ section 2, Preparation before Use, of this User’s Manual before using the emulator product. Incorrect operation will damage the user system and the emulator product. This emulator is an efficient development tool for software and hardware of user systems based on Hitachi’s original microprocessor.
  • Page 16 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.

  • Page 17: Table Of Contents

    Section 1 Overview... 1 Warnings ... 3 Environmental Conditions ... 4 Components ... 6 Section 2 Preparation before Use ... 7 Emulator Preparation ...7 HDI Installation... 8 2.2.1 Installing under Windows 98 and Windows Me Operating Systems... 8 2.2.2 Installing under Windows NT 4.0 Operating System... 9 2.2.3 Installing under Windows 2000 Operating System ...
  • Page 18 3.15 Break Function... 51 3.15.1 Software Break Function ... 51 3.16 Hardware Break Function ... 57 3.17 Trace Function ... 64 3.18 What Next? ... 65 Section 4 Descriptions of Windows...67 HDI Windows ... 67 Descriptions of Each Window ... 70 4.2.1 [Configuration] Dialog Box...
  • Page 19 Section 6 H8S/2378F E10A Emulator Specifications... 119 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 ... 126 6.4.1 Emulator Driver Selection ... 126 6.4.2...
  • Page 20 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...
  • Page 21 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.18 [Memory] Window...40 Figure 3.19 [Instant Watch] Dialog Box... 41 Figure 3.20 [Watch] Window (Displaying the Array)...42 Figure 3.21 [Add Watch] Dialog Box ...
  • Page 22 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 ... 94 Figure 6.1 Pin Arrangement of the Hitachi-UDI Port Connector ... 120 Figure 6.2 Example of Emulator Connection ... 121 Figure 6.3 Connection of Emulator ...
  • Page 23 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 ... 25 Table 3.2 Setting the [Configuration] Dialog Box...29 Table 3.3 Contents of the [System Status] Window ...38 Table 3.4 Step Option ...44 Table 4.1 HDI Window Menus and Related Manual Entries ...
  • Page 24 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 ... 126 Table 6.5 Hardware Break Condition Specification Items ...

  • Page 25: Section 1 Overview

    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.

  • Page 26: Figure 1.2 System Configuration With The Emulator (Pci Card Emulator Used)

    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.

  • Page 27: Warnings

    Warnings 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.

  • Page 28: Environmental Conditions

    Environmental Conditions 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:...

  • Page 29: Table 1.2 Operating Environments

    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. Windows Minimum memory 32 Mbytes or more (double of the load module size recommended) capacity Hard-disk capacity Installation disk capacity: 10 Mbytes or more.

  • Page 30: Components

    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.

  • Page 31: Section 2 Preparation Before Use

    Section 2 Preparation before Use Emulator Preparation READ the reference sections shaded in figure 2.1 before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. Unpack the emulator and prepare it for use as follows: Unpack the emulator Check the components against the component list Turn on the host computer...

  • Page 32: Hdi Installation

    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.

  • Page 33: Installing Under Windows Nt 4.0 Operating System

    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.

  • Page 34: Installing Under Windows 2000 Operating System

    2.2.3 Installing under Windows 2000 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.

  • Page 35: Connecting The Host Computer With The Card Emulator

    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.4, to connect the emulator to the user system with the...

  • Page 36: Connecting The Card Emulator With The User System

    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. Connecting the Card Emulator with the User System (1) The connector must be installed to the user system.
  • Page 37 Notes: To connect the signals output from the connector, refer to the MCU pin alignment. To remove the user system interface cable from the user system, pull the tab on the connector upward. The range of communications that the emulator operates at is different according to the MCUs used.

  • Page 38: System Check

    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.

  • Page 39: Figure 2.6 [Select Session] Dialog Box

    5. Power on the user system and select the setting to be used. Figure 2.6 [Select Session] Dialog Box...

  • Page 40: Figure 2.7 [E10A Driver Details] Dialog Box

    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.

  • Page 41: 2.5.1 H8S/Xxxx E10A Emulator Mode

    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.

  • Page 42: Figure 2.11 [H-Udi Connector Disconnected] Dialog Box

    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.

  • Page 43: Figure 2.13 [Check The Connection] Dialog Box

    (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.

  • Page 44: 2.5.2 Writing H8S/Xxxx E10A Flash Memory Mode

    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.

  • Page 45: Figure 2.18 [Load Program] Dialog Box

    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.

  • Page 46: Figure 2.21 [Continue?] Window

    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.

  • Page 47: Ending The Hdi

    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. 2. Then, the [Save session] dialog box is displayed. If necessary, click the [Yes] button to save session.

  • Page 48: Uninstalling The Hdi

    Uninstalling the HDI Follow this procedure to remove the installed HDI from the user’s host computer. Open [Add/Remove Programs Properties] from the control panel. Select the HDI program from the list and click the [Add/Remove…] button. The setup program is executed again and the installed application can be changed, modified, or removed.

  • Page 49: Section 3 Tutorial

    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.

  • Page 50: Running The Hdi

    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.

  • Page 51: Hdi] Window

    [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.

  • Page 52: Setting Up The Emulator

    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. Setting the [Configuration] Dialog Box Select [Configure Platform...] from the [Setup] menu to set configuration.

  • Page 53: Table 3.2 Setting The [Configuration] Dialog Box

    Set options as follows: Table 3.2 Setting the [Configuration] Dialog Box Option Mode Emulation mode Step option (Disables interrupt during single step execution) JTAG clock Operating Mode Flash memory synchronization Click the [OK] button to set any changes in the configuration. Value H8S/xxxx (default) Normal (normal execution, default)

  • Page 54: Downloading The Tutorial Program

    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.

  • Page 55: Displaying The Source Program

    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.6 [Open] Dialog Box...

  • Page 56: Figure 3.7 [Program] Window (Displaying The Source Program)

    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.

  • Page 57: Setting The Software Breakpoint

    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.

  • Page 58: Setting Registers

    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. To change the value of the program counter (PC), double-click the value area in the [Registers] window with the mouse.

  • Page 59: Figure 3.11 [Register] Dialog Box (Er7)

    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.

  • Page 60: Executing The Program

    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. Or, select [Reset Go] from the [Run] menu or click the [Reset Go] button on the toolbar. The program will be executed up to the breakpoint that has been inserted, and a statement will be highlighted in the [Program] window to show the position that the program has halted, with the message [Break=BREAKPOINT] in the status bar.

  • Page 61: Figure 3.15 [System Status] Window

    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.

  • Page 62: Table 3.3 Contents Of The [System Status] Window

    The [System Status] window displays the following items in each page. Table 3.3 Contents of the [System Status] Window Page Item [Session] Target System Session Name Program Name [Platform] Connected To: Run status Cause of last break Run time count Emulator mode [Memory] Loaded Memory...

  • Page 63: Reviewing Breakpoints

    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. 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.

  • Page 64: Viewing Memory

    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.

  • Page 65: Watching Variables

    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.

  • Page 66: Figure 3.20 [Watch] Window (Displaying The Array)

    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.

  • Page 67: Figure 3.22 [Watch] Window (Displaying The Variable)

    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.23 [Watch] Window (Displaying Array Elements)

  • Page 68: Stepping Through A Program

    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.

  • Page 69: Executing [Step In] Command

    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.

  • Page 70: Executing [Step Out] Command

    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.

  • Page 71: Figure 3.28 [Program] Window (Step In Step In)

    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.

  • Page 72: Executing [Step Over] Command

    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.

  • Page 73: Figure 3.31 [Program] Window (Step Over)

    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.

  • Page 74: Displaying Local Variables

    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.

  • Page 75: Break Function

    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.

  • Page 76: Figure 3.34 [Point] Page ([Break] Dialog Box)

    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.

  • Page 77: Figure 3.35 [Breakpoint] Dialog Box

    Enter H'10a4 to the [Value] edit box. Figure 3.35 [Breakpoint] Dialog Box Click the [OK] button.

  • Page 78: Figure 3.36 [Point] Page ([Break] Dialog Box) (After Software Breakpoint Setting)

    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.

  • Page 79: Figure 3.37 [Breakpoints] Window (Software Breakpoint Setting)

    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.

  • Page 80: Figure 3.39 Displayed Contents Of The [System Status] Window (Software Break)

    The [System Status] window displays the following contents. Figure 3.39 Displayed Contents of the [System Status] Window (Software Break) Note: The items that can be displayed in this window differ according to the product. For the items that can be displayed, refer to the on-line help.

  • Page 81: Hardware Break Function

    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.

  • Page 82: Figure 3.41 [Condition] Page ([Break] Dialog Box)

    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.

  • Page 83: Figure 3.42 [Condition] Page ([Break Condition 1] Dialog Box)

    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.

  • Page 84: Figure 3.43 [Break] Dialog Box (After Hardware Break Condition Setting)

    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.

  • Page 85: Figure 3.44 [Breakpoints] Window ([Break Condition 1] Setting)

    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.

  • Page 86: Figure 3.45 [Program] Window At Execution Stop (Break Condition 1)

    The program runs then stops at the condition specified under Break condition 1. Figure 3.45 [Program] Window at Execution Stop (Break condition 1)

  • Page 87: Figure 3.46 Displayed Contents Of The [System Status] Window (Break Condition 1)

    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.

  • Page 88: Trace Function

    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.

  • Page 89: What Next

    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.

  • Page 91: Section 4 Descriptions Of Windows

    Section 4 Descriptions of Windows 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.
  • Page 92 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 Reset Go Go to Cursor Set PC To Cursor...
  • Page 93 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...

  • Page 94: Descriptions Of Each Window

    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.

  • Page 95: Table 4.2 [Configuration] Dialog Box Page

    Description: The [Configuration] dialog box consists of the [General] page listed in table 4.2. Table 4.2 [Configuration] Dialog Box Page Page Name [General] Clicking the [OK] button sets the emulation conditions. If the [Cancel] button is clicked, this dialog box is closed without setting the emulation conditions. Description Sets the emulator operation conditions.

  • Page 96: Figure 4.2 [General] Page ([Configuration] Dialog Box)

    (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.

  • Page 97: Table 4.3 [General]

    Description: Table 4.3 [General] Page Options Option [Mode] combo box [Emulation mode] combo box [Step option] combo box [JTAG clock] combo box [Operating mode] combo box [Flash memory synchronization] combo box [Driver] group box Note: The range of frequencies that the JTAG operates at is different according to the devices used.

  • Page 98: Figure 4.3 Warning Message Box

    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. Related Items: [Configuration] dialog box GO_OPTION command...

  • Page 99: [E10A Driver Details] 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.

  • Page 100: Breakpoints] Window

    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.

  • Page 101: Table 4.5 [Breakpoints] Window Display Items

    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.

  • Page 102: Break] Dialog Box

    4.2.4 [Break] Dialog Box Function: This dialog box displays the break condition settings. Window: Figure 4.6 [Break] Dialog Box...

  • Page 103: Table 4.7 [Break] Dialog Box Pages

    Description: The [Break] dialog box consists of the pages listed in table 4.7. Table 4.7 [Break] Dialog Box Pages Page Name [Point] [Condition] The dialog boxes which set or modify break conditions can be displayed from the pages above. Clicking the [Close] button will close this dialog box. The [Apply] button is not supported. Description Displays software breakpoint settings.

  • Page 104: Figure 4.7 [Point] Page ([Break] 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.7 [Point] Page ([Break] Dialog Box)

  • Page 105: Table 4.8 [Point]

    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: <breakpoint address> [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.

  • Page 106: Figure 4.8 [Condition] Page ([Break] 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.

  • Page 107: Table 4.9 [Condition]

    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...

  • Page 108: Breakpoint] Dialog 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.

  • Page 109: Table 4.10 [Address] Page Options

    Description: The [Address] page options are as follows: Table 4.10 [Address] Page Options Option [Value] edit box Clicking the [OK] button enables breakpoints to be set. If the [Cancel] button is clicked, this dialog box is closed without setting breakpoints. Related Items: [Point] page BREAKPOINT command...

  • Page 110: Break Condition] Dialog Box

    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.
  • Page 111 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.

  • Page 112: [Break Condition] Dialog Box

    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.11 Setting Conditions in [Break condition] Dialog Box Type Address Bus...

  • Page 113: Figure 4.11 [Condition]

    (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.

  • Page 114: Table 4.13 [Address] Group Box Options

    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 Sets a break after prefetched address execution as break conditions.

  • Page 115: Table 4.16 [Read/Write] Group Box Options

    The [Read/Write] group box sets the read/write cycle conditions. Table 4.16 [Read/Write] Group Box Options Option [Read/Write] radio button [Read] radio button [Write] radio button Related Items: [Condition] page BREAKCONDITION_CLEAR command BREAKCONDITION_DISPLAY command BREAKCONDITION_ENABLE command BREAKCONDITION_SET command Description Sets the read/write cycle conditions as break conditions. Sets read cycles as break conditions.

  • Page 116: Trace] Window

    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.

  • Page 117: Table 4.17 [Trace] Window Display Items

    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.

  • Page 118: System Status] Window

    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.

  • Page 119: Table 4.18 [System Status] Window Display Items

    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 [Session] Target System Session Name Program Name [Platform] Connected To Run status Cause of last break Run time count Emulator mode [Memory]...

  • Page 121: Section 5 Command-Line Functions

    Section 5 Command-line Functions 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.

  • Page 122: Examples

    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.)

  • Page 123: Command Descriptions

    Command Descriptions The command list of the E10A emulator is shown below. Table 5.1 E10A HDI Commands No Command BREAKCONDITION_ CLEAR BREAKCONDITION_ DISPLAY BREAKCONDITION_ ENABLE BREAKCONDITION_ BREAKPOINT BREAKPOINT_CLEAR BREAKPOINT_DISPLAY BREAKPOINT_ENABLE DEVICE_TYPE GO_OPTION JTAG_CLOCK REFRESH RESET STATUS STEP_INTERRUPT TRACE_DISPLAY Note: Support for these commands varies with the product. For the specifications of each product, refer to the on-line help.

  • Page 124: Breakcondition_Clear: Bcc

    5.2.1 BREAKCONDITION_CLEAR: BCC Description: Clears hardware breakpoints that have been set. Format: bcc [<channel>] <channel> = channel <channel_number> Table 5.2 BREAKCONDITION_CLEAR Command Parameter Parameter Type None Examples: To clear all hardware breakpoints: > bcc (RET) To clear all hardware breakpoints set at channel 2: >...

  • Page 125: Breakcondition_Display: Bcd

    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>] <channel> = channel <channel_number> Table 5.3 BREAKCONDITION_DISPLAY Command Parameter Parameter Type None Examples: To display all hardware breakpoint settings: >...

  • Page 126: Breakcondition_Enable: Bce

    5.2.3 BREAKCONDITION_ENABLE: BCE Description: Enables or disables hardware breakpoints that have been set. Format: bce [<channel>] <mode> <channel> = channel <channel_number> Table 5.4 BREAKCONDITION_ENABLE Command Parameter Parameter Type <mode> Keyword Examples: To enable all hardware breakpoints: > bce enable (RET) To disable the hardware breakpoints set at channel 1: >...

  • Page 127: Breakcondition_Set: Bcs

    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 <channel> <option> [<option> ... ] <channel> = channel <channel_number> <option>...

  • Page 128: Table 5.5 Breakcondition_Set Command Parameters

    Table 5.5 BREAKCONDITION_SET Command Parameters Parameter Type <address> Numerical value, character string <addrcycle> Keyword <maskdata> Keyword <data> Numerical value <size> Keyword <direction> Keyword Note: The parameters for this command vary with the product. For the specifications of each product, refer to the on-line help. Description Numerical value or symbol representing an address bus value...
  • Page 129 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.

  • Page 130: Breakpoint: Bp

    5.2.5 BREAKPOINT: BP Description: Sets software breakpoints. Note: The function will be different according to the MCUs used. Format: bp <address> Table 5.6 BREAKPOINT Command Parameter Parameter Type <address> Numerical value, character string Note: The parameters for this command vary with the product. For the specifications of each product, refer to the on-line help.

  • Page 131: Breakpoint_Clear: Bc

    5.2.6 BREAKPOINT_CLEAR: BC Description: Clears software breakpoints that have been set. Format: bc [<address>] Table 5.7 BREAKPOINT_CLEAR Command Parameter Parameter Type <address> Numerical value, character string 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.

  • Page 132: Breakpoint_Display: Bd

    5.2.7 BREAKPOINT_DISPLAY: BD Description: Displays software breakpoints that have been set. Format: Table 5.8 BREAKPOINT_DISPLAY Command Parameter Parameter Type 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...

  • Page 133: Breakpoint_Enable: Be

    5.2.8 BREAKPOINT_ENABLE: BE Description: Enables or disables software breakpoints that have been set. Format: be <address> <mode> Table 5.9 BREAKPOINT_ENABLE Command Parameters Parameter Type <address> Numerical value, character string <mode> Keyword Examples: To enable software breakpoints that have been set: >...

  • Page 134: Device_Type: De

    5.2.9 DEVICE_TYPE: DE Description: Displays MCU type currently selected. Format: Table 5.10 DEVICE_TYPE Command Parameter Parameter Type None Example: To display the currently selected MCU: > de (RET) The display format is as follows: >de Current device = H8S/xxxx Description...

  • Page 135: Go_Option: Gp

    5.2.10 GO_OPTION: GP Description: Sets or displays the emulation mode during user program execution. Format: Displays emulation mode for user program execution. gp <eml_opt> <eml_opt> = eml_mode <eml_mode> Sets emulation mode for user program execution. Table 5.11 GO_OPTION Command Parameter Parameter Type <eml_mode>...

  • Page 136: Jtag_Clock: Jck

    5.2.11 JTAG_CLOCK: JCK Description: Displays or sets the JTAG clock (TCK) frequency. Format: Displays the JTAG clock (TCK). JCK <jck_opt> Sets the JTAG clock (TCK). Table 5.12 JTAG_CLOCK Command Parameter Parameter Type <jck_opt> Numerical value Note: The range of the frequency that the Hitachi-UDI operates at differs according to the MCU to be supported.
  • Page 137 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: >...

  • Page 138: Refresh: Rf

    5.2.12 REFRESH: RF Description: Updates the HDI memory information to the latest contents. Format: Table 5.13 REFRESH Command Parameter Parameter Type Description None Example: To update the HDI memory information: > rf (RET)

  • Page 139: Reset: Re

    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: Table 5.14 RESET Command Parameter Parameter Type Description None Example: To reset the H8S/xxxx: >...

  • Page 140: Status: Sts

    5.2.14 STATUS: STS Description: Displays emulator status information. Format: Table 5.15 STATUS Command Parameter Parameter Type None Example: To display status information of the emulator: > sts (RET) The display format is as follows: >sts Emulator Status Connected to: Run status Cause of last break Run time count Emulator mode...

  • Page 141: Step_Interrupt: Si

    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: Displays the enable or disable status of interrupts during step execution. si <mode>...

  • Page 142: Trace_Display: Td

    5.2.16 TRACE_DISPLAY: TD Description: Displays acquired trace information. Format: Table 5.17 TRACE_DISPLAY Command Parameter Parameter Type None Example: To display acquired trace information: > td (RET) The display format is as follows: >td TYPE -D’xxxx BRANCH -D’xxxx BRANCH (a) Instruction pointer (signed decimal) (b) Type of branch source BRANCH: Branch source (c) Address of instruction word...

  • Page 143: Section 6 H8S/2378F E10A Emulator Specifications

    Section 6 H8S/2378F E10A Emulator Specifications 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.

  • Page 144: Pin Arrangement Of The Hitachi-Udi Port Connector

    Pin Arrangement of the Hitachi-UDI Port Connector Figure 6.1 shows the pin arrangement of the Hitachi-UDI port connector. Note that the pin number assignment of the Hitachi-UDI port connector differs from that of the connector manufacturer. Pin 1 mark Hitachi-UDI port connector 8 pin 1 pin Top view...

  • Page 145: Figure 6.2 Example Of Emulator Connection

    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) 8 to 10 12 to 14 E10A pin No. · #RES of pin 4 of the Hitachi-UDI port connector is a signal line in which the emulator outputs signals to the MCU. An AND operation must be performed between #RES (pin 4) and the user system reset circuit for the signal line connected to the MCU.

  • Page 146: Figure 6.3 Connection Of Emulator

    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. Hitachi-UDI port connector Pins 1, 2, 3, 5, and 6...

  • Page 147: Figure 6.5 Connection Of #Res Pin

    #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.

  • Page 148: Table 6.2 Unavailable Pin Functions

    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 P53 and PG4 to PG6 #WDTOVF #IRQ3 #ADTRG #BREQ, #BACK, and #BREQ0 Note: The symbol “#” means that the signal is active-low. H8S/2367F P53 and PG4 to PG6 #WDTOVF...

  • Page 149: Differences Between The Mcus And The Emulator

    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 ER0 to ER6 ER7 (SP) 2.

  • Page 150: The H8S/2378F E10A Emulator Functions

    HS2378KCM01H HS2378KCI01H 6.4.2 Hardware Break Functions Hardware Break Conditions: In the H8S/2378F E10A emulator, two break conditions can be set (Break Condition 1,2). Table 6.5 lists the items that can be specified. Table 6.5 Hardware Break Condition Specification Items Items...

  • Page 151: Table 6.6 Conditions Set In [Break Condition] Dialog Box

    Table 6.6 Conditions Set in [Break condition] Dialog Box Condition Address Bus Dialog Box Condition [Break condition 1] [Break condition 2] 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.

  • Page 152: Notes On Setting The [Breakpoint] Dialog Box

    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.

  • Page 153: Trace Function

    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.

  • Page 154: Table 6.9 Items In The [Trace] Window

    (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.9 Items in the [Trace] Window Item Description [IP/Cycle] Instruction pointer or bus cycle pointer (signed decimal) [Address] The value of the address bus [Label]...

  • Page 155: Table 6.10 Trace Search Function

    (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.

  • Page 156: Table 6.13 [Bus Status] Group Box Options

    Table 6.13 [Bus status] Group Box Options Option [Don’t care] check box [DMAC] check box [DTC] check box [PROG] check box [DATA] check box [REFRESH] check box Table 6.14 [Area] Group Box Options Option [Don’t care] check box [ROM] check box [RAM] check box [IO-8] check box [IO-16] check box...

  • Page 157: Table 6.17 Commands For The Trace Function

    (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.
  • Page 158 Example: To display the acquired trace information: td (RET) The display format of the branch trace information is as follows: >td TYPE -D’xxxx BRANCH -D’xxxx BRANCH (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:...

  • Page 159: Table 6.19 Trace_Mode Command Parameter

    (ii) TRACE_MODE: TM Description: Displays or sets the acquisition mode of the trace information. Format: Displays the acquisition mode of the trace information. tm <option1> [<option2>] [<option3>] [<option4>] Sets the acquisition mode of the trace information. <option1> = type <type> <option2>...
  • Page 160 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...
  • Page 161 (iii) TRACE_SEARCH: TS Description: Searches and displays the trace information with the specified condition. Format: ts [<addropt>] [<dataopt>] [<statusopt>] [<areaopt>] [<rwopt>] [<irqopt>] [<fromopt>] <addropt> = address <address> <dataopt> = data <data> <size> <statusopt> = status <status> <areaopt> = area <area> <rwopt>...

  • Page 162: Table 6.20 Trace_Search Command Parameter

    Table 6.20 TRACE_SEARCH Command Parameter Parameter Type <address> Numerical value, character string <data> Numerical value <size> Keyword <status> Keyword <area> Keyword <rw> Keyword <irq> Keyword <from> Numerical value (-n) Description Sets the address value as a numeric or a symbol. Sets a value of the data bus.
  • Page 163 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 *-D'0075 xxxxxxxx *-D'0074 xxxxxxxx *-D'0073 xxxxxxxx *-D'0072 xxxxxxxx...

  • Page 164: Notes On Hdi

    6.4.5 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.
  • Page 165 Example: Array display When array elements exceed 1000, elements from after 1000 will not be displayed. 6. Memory Load Function When [Load...] is selected from the [Memory] menu, the Memory Load function can be used although it takes time to download. It is recommended that the File Load function ([Load Program...] selected from the [File] menu) is used to load the S-type file.
  • Page 166 Example: 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.
  • Page 167 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).
  • Page 168 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.
  • Page 169 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.
  • Page 170 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: An internal reset signal is generated when the internal LSI is reset.

This manual is also suitable for:

Hs2378kci01hHs2378kcm01hH8s/2378f e10a

Table of Contents