HS2214EPI62H-U Renesas Electronics America, HS2214EPI62H-U Datasheet
HS2214EPI62H-U
Specifications of HS2214EPI62H-U
Related parts for HS2214EPI62H-U
HS2214EPI62H-U Summary of contents
Page 1
To our customers, Old Company Name in Catalogs and Other Documents st On April 1 , 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the ...
Page 2
All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm ...
Page 3
... H8S/2214 E6000 Emulator User’s Manual Renesas Microcomputer Development Environment System H8S Family / H8S/2200 Series HS2214EPI62HE-U2 Rev.4.00 2006.02 ...
Page 4
...
Page 5
Keep safety first in your circuit designs! 1. Renesas Technology Corp. 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 ...
Page 6
...
Page 7
IMPORTANT INFORMATION • READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference. Do not attempt to use the emulator product until you fully understand its mechanism. Emulator Product: Throughout this document, ...
Page 8
LIMITED WARRANTY Renesas warrants its emulator products to be manufactured in accordance with published specifications and free from defects in material and/or workmanship. Renesas, at its option, will repair or replace any emulator products returned intact to the factory, transportation ...
Page 9
State Law: Some states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages, so the above limitation or exclusion may not apply to you. This warranty gives you specific legal rights, and ...
Page 10
READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference. Do not attempt to use the emulator product until you fully understand its mechanism. DEFINITION OF SIGNAL WORDS This is the ...
Page 11
Observe the precautions listed below. Failure will result in a FIRE HAZARD and will damage the user system and the emulator product or will result in PERSONAL INJURY. The USER PROGRAM will be LOST not ...
Page 12
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 ...
Page 13
The E6000 emulator is an advanced realtime in-circuit emulator, which allows programs to be developed and debugged for the H8S family microcomputers. The E6000 emulator can either be used without a user system, for developing and debugging software, or connected ...
Page 14
This manual contains the following information. Emulator Debugger Part: Preparation before use, E6000 emulator functions, debugging function, tutorial, and hardware and software specifications of the E6000 emulator. Refer to the High-performance Embedded Workshop User's Manual for details on the information ...
Page 15
Emulator Debugger Part Section 1 Overview........................................................................................... 1 1.1 Features .............................................................................................................................1 1.2 Warnings ...........................................................................................................................2 1.3 Environmental Conditions ................................................................................................3 1.4 Emulator External Dimensions and Mass .........................................................................3 Section 2 Preparation before Use...................................................................... 5 2.1 Emulator Preparation ........................................................................................................5 2.2 Installing Emulator’s Software .........................................................................................5 2.3 ...
Page 16
Probes .................................................................................................................. 23 3.4 Stack Trace Function ........................................................................................................ 23 3.5 Online Help....................................................................................................................... 23 Section 4 Preparation before Use ......................................................................25 4.1 Method for Activating High-performance Embedded Workshop..................................... 25 4.1.1 Creating a New Workspace (Toolchain Not Used).............................................. 26 4.1.2 Creating a ...
Page 17
Disabling an Event Point......................................................................................73 5.7.13 Deleting an Event Point .......................................................................................73 5.7.14 Deleting All Event Points ....................................................................................73 5.7.15 Viewing the Source Line for an Event Point........................................................73 5.8 Viewing the Trace Information .........................................................................................74 5.8.1 Opening the [Trace] Window ..............................................................................74 5.8.2 Acquiring ...
Page 18
Displaying a Trace (when Time Stamping is Available) ..................................... 156 6.16.3 Statistics ............................................................................................................... 160 6.16.4 Function Calls ...................................................................................................... 164 6.17 Stack Trace Function ......................................................................................................... 165 6.18 Performance Measurement Function ................................................................................. 167 6.18.1 Time Of Specified Range Measurement .............................................................. 167 ...
Page 19
Appendix D Diagnostic Test Procedure ........................................................... 209 D.1 System Set-Up for Test Program Execution .....................................................................209 D.2 Diagnostic Test Procedure Using Test Program ...............................................................210 vii ...
Page 20
viii ...
Page 21
Emulator Debugger Part ...
Page 22
...
Page 23
Features • The breakpoint, memory map, performance, and trace can be set through the dialog box. ⎯ Intuitive user interface ⎯ Online help ⎯ Common display and operability • Supported host interfaces The PCI interface, PC card (PCMCIA) interface, ...
Page 24
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. ...
Page 25
Environmental Conditions Observe the conditions listed in table 1.1 when using the emulator. Failure will cause illegal operation in the user system, the emulator product, and the user program. Table 1.1 Environmental Conditions Item Specifications Temperature ...
Page 26
4 ...
Page 27
Section 2 Preparation before Use 2.1 Emulator Preparation Unpack the emulator and prepare it for use as follows: READ the reference sections shaded in figure 2.1 before using the emulator product. Incorrect operation will damage the user system and the ...
Page 28
Connecting to the User System To connect the emulator to a user system, proceed as follows: • Connect the user system interface cable head to the user system. • Plug the cable body into the emulator. • Plug the ...
Page 29
Screw the cable head to the socket with the screws provided. Progressively tighten the screws in the sequence shown in figure 2.4 until all are ‘finger tight’. Figure 2.4 Sequence of Screw Tightening Note: Be careful not to over-tighten ...
Page 30
Power Supply 2.4.1 AC Adapter The AC adapter supplied with the emulator must be used at all times. 2.4.2 Polarity Figure 2.6 shows the polarity of the power-supply plug. Figure 2.6 Polarity of Power Supply Plug 2.4.3 Power Supply ...
Page 31
Hardware Interface All signals are directly connected to the MCU in the emulator with no buffering with the exception of those listed in section 7, Hardware Specifications Specific to This Product. 2.6.1 Signal Protection on the emulator All signals ...
Page 32
The interface circuit for the external probe 1 is shown in figure 2.8. HD151015 Figure 2.8 Interface Circuit for External Probe 1 The trigger output is controlled by event channel 8 and is an active low signal. The trigger output ...
Page 33
Voltage Follower Circuit 1. Do not connect the user system interface cable to the emulator without user system connection. 2. Turn on the user system before starting up the emulator. A voltage follower circuit is implemented on the emulator ...
Page 34
System Check When the software is executed, use the procedure below to check that the emulator is connected correctly. Here, use the workspace for a tutorial provided on the product. Refer to section 2.9, Other Methods for Activating the ...
Page 35
The [Welcome!] dialog box is displayed. To use a workspace for the tutorial, select the [Browse to another project workspace] radio button and click the [OK] button. When the [Open Workspace] dialog box is opened, specify the following directory: ...
Page 36
When no compiler package or that of a different version is installed, the following message box will be displayed. 6. The [E6000 Driver Details] dialog box is displayed. This dialog box is only displayed at the first initiation. When only ...
Page 37
Set up the emulator. During this process, the following dialog box is displayed. Figure 2.16 [Connecting] Dialog Box 15 ...
Page 38
When "Connected" is displayed in the [Output] window of the High-performance Embedded Workshop, the emulator initiation is completed. Figure 2.17 High-performance Embedded Workshop Window 16 ...
Page 39
Communication Problems The following message box will be displayed when the emulator power is turned off or the PC interface cable is not correctly connected. For information on other errors, refer to the Setup Guide for the E6000 Emulator. ...
Page 40
18 ...
Page 41
Section 3 E6000 Emulator Functions 3.1 Debugging Features 3.1.1 Breakpoints The emulator provides a comprehensive range of alternative types of breakpoints, to give you the maximum flexibility in debugging applications and user system. Hardware Break Conditions break ...
Page 42
Bus Monitoring The emulator incorporates a bus monitoring function that monitors and displays the contents of the accessed area in High-performance Embedded Workshop windows without stopping the program execution eight blocks of 256 bytes can be monitored. ...
Page 43
Range Channels The range channels can be set triggered on a combination of one or more of the following: • Address or address range (inside the range) • Read or Write or either • Data, with ...
Page 44
Hardware Features 3.3.1 Memory The emulator provides standard emulation memory as the substitute for on-chip ROM memory and on-chip RAM memory. When a device type or device mode without an on-chip ROM or on-chip RAM is selected, the standard ...
Page 45
Clocks The clock can be specified as emulator internal clock or target clock. The frequencies that can be specified as the emulator internal clock depend on the MCU. For details, refer to section 8, Software Specifications Specific to This ...
Page 46
24 ...
Page 47
Section 4 Preparation before Use 4.1 Method for Activating High-performance Embedded Workshop To activate the High-performance Embedded Workshop, follow the procedure listed below. 1. Connect the emulator to the host computer. 2. Connect the user system interface cable to the ...
Page 48
Creating a New Workspace (Toolchain Not Used the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select [Create a new project workspace] radio button and click the [OK] button. 26 Figure 4.2 ...
Page 49
Creation of a new workspace is started. The following dialog box is displayed. Figure 4.3 [New Project Workspace] Dialog Box [Workspace Name] edit box: Enter the new workspace name. [Project Name] edit box: Enter the project name. When the ...
Page 50
Select the target platform of the session file. The following dialog box is displayed. Figure 4.4 [New Project – Step 7] Dialog Box The target platform for the session file used when the High-performance Embedded Workshop is activated must ...
Page 51
Set the configuration file name. Figure 4.5 [New Project – Step 8] Dialog Box If multiple target platforms were selected in the [New Project – Step 7] dialog box shown in figure 4.5, set the name of a configuration ...
Page 52
Creating a New Workspace (Toolchain Used the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select [Create a new project workspace] radio button and click the [OK] button. 30 Figure 4.6 [Welcome!] ...
Page 53
Creation of a new workspace is started. The following dialog box is displayed. Figure 4.7 [New Project Workspace] Dialog Box [Workspace Name] edit box: Enter the new workspace name. Here, enter ‘test’. [Project Name] edit box: Enter the project ...
Page 54
Make the required setting for the toolchain. When the setting has been completed, the following dialog box is displayed. Figure 4.8 [New Project – Step 7] Dialog Box The target platform for the session file used when the High-performance ...
Page 55
Set the configuration file name. Figure 4.9 [New Project – Step 8] Dialog Box If multiple target platforms were selected in the [New Project – Step 7] dialog box shown in figure 4.9, set the name of a configuration ...
Page 56
Selecting an Existing Workspace 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activated, select [Browse to another project workspace] radio button and click the [OK] button. 2. The [Open Workspace] dialog box ...
Page 57
Connecting the Emulator Select either of the following two ways to connect the emulator: (a) Connecting the emulator after the setting at emulator activation Select [Debug -> Debug Settings…] to open the [Debug Settings] dialog box possible ...
Page 58
Reconnecting the Emulator When the emulator is disconnected, use the following way for reconnection: Select [Debug -> Connect] or click the [Connect] toolbar button ( Note: Before reconnecting the emulator, a load module must be registered to the High-performance ...
Page 59
This section describes the debugging operations and their related windows and dialog boxes. Refer to the High-performance Embedded Workshop user's manual about High-performance Embedded Workshop common functions as below. ⎯ Preparations for Debugging ⎯ Viewing a Program ⎯ Operating Memory ...
Page 60
Setting the Environment for Emulation 5.1.1 Opening the [Configuration Properties] Dialog Box Selecting [Setup -> Emulator -> System…] or clicking the [Emulator System] toolbar button ( Configuration Properties] dialog box. Figure 5.1 [Configuration Properties] Dialog Box ([General] Page) This ...
Page 61
Resolution] [Enable read and write on the fly] [Break on access error] [Enable internal ROM area write] [User VCC Threshold] [User Signals] [Driver] [Change driver in start up] Note: The items that can be ...
Page 62
Selecting an MCU Not Included in the List Selecting [Custom] in [Device] of the [Configuration Properties] dialog box adds the [Custom Device] page to the dialog box. Figure 5.2 [Configuration Properties] Dialog Box ([Custom Device] Page) Use this page ...
Page 63
Selecting the Interface to be Connected Checking [Change driver in start up] on the [Configuration Properties] dialog box allows a selection of the driver next time the emulator is connected. Figure 5.3 [Driver Details] Dialog Box [Driver]: Selects the ...
Page 64
Opening the [Memory Mapping] Dialog Box Selecting [Setup -> Emulator -> Memory Resource…] or clicking the [Emulator Memory Resource] toolbar button ( ) opens the [Memory Mapping] dialog box. Figure 5.4 [Memory Mapping] Dialog Box This dialog box displays ...
Page 65
Changing the Memory Map Setting Clicking the [Add…] button on the [Memory Mapping] dialog box or clicking the [Modify…] button after selecting the information on the memory map setting you want to change opens the [Edit Memory Mapping] dialog ...
Page 66
Downloading a Program This section describes how to download a program and view it as source code or assembly-language mnemonics. Note: After a break occurs, the High-performance Embedded Workshop displays the location of the program counter (PC) on the ...
Page 67
Viewing the Source Code To view a source file’s code, double-click on its icon in the file tree, or right-click on the source file and select the [Open] option on the pop-up menu. The [Editor] window is displayed. In ...
Page 68
Source Address column When a program is downloaded, an address for the current source file is displayed on the Source address column. These addresses are helpful when setting the PC value or a breakpoint. Event column The Event column displays ...
Page 69
To switch off a column in all source files 1. Right-click on the [Editor] window or select the [Edit] menu. 2. Click the [Define Column Format…] menu item. 3. The [Global Editor Column States] dialog box is displayed ...
Page 70
Viewing the Assembly-Language Code If you have a source file open, right-click to open the pop-up menu and select the [View Disassembly] option to open a Disassembly view at the same address as the current Source view ...
Page 71
Modifying the Assembly-Language Code You can modify the assembly-language code by double-clicking on the instruction that you want to change. The [Assembler] dialog box will be opened. The address, instruction code, and mnemonic are displayed. Enter the new instruction ...
Page 72
Viewing the Current Status Choose [View -> CPU -> Status] or click the [View Status] toolbar button ( see the current status of the debugging platform. The [Status] window has three sheets: • [Memory] sheet Contains information about the ...
Page 73
Reading and Displaying the Emulator Information Regularly Use the [Extended Monitor] window to know the changing information on the emulator no matter the user program is running or halted. Note: The Extended Monitor function does not affect the execution ...
Page 74
Selecting Items to be Displayed Selecting [Properties…] from the popup menu displays the [Extended Monitor Configuration] dialog box. Figure 5.13 [Extended Monitor Configuration] Dialog Box This dialog box allows the user to set the items to be displayed in ...
Page 75
Displaying Memory Contents in Realtime Use the [Monitor] window to monitor the memory contents during user program execution. In the Monitor function, the realtime operation is retained since the bus monitoring circuit of the emulator sets the read/write signal ...
Page 76
Decides the name of the monitor window. [Options]: Sets monitor conditions. [Address]: [Size]: [Access]: [Auto-Refresh at rate (ms)]: [Reading the Initial Value]: [Color]: Sets the method to update monitoring and the attribute of colors. [Change Indicator]: [Foreground]: [Background]: [Mayfly]: ...
Page 77
During user program execution, the display is updated according to the setting value of the auto-update interval. Note: Select [Refresh] from the popup menu when data is not displayed correctly after changing the address or content of memory. 5.5.2 Changing ...
Page 78
Hiding the [Monitor] Window When using the Monitor function to monitor the value of a variable from the [Watch] window, hide the [Monitor] window for the effective use of the screen. The current monitoring information is listed as the ...
Page 79
Managing the [Monitor] Window Selecting [Display -> CPU -> Monitor -> Windows Select…] displays the [Windows Select] dialog box. In this window, the current monitoring condition is checked and the new monitoring condition is added, edited, and deleted in ...
Page 80
Viewing the Variables This section describes how you can look at variables in the source program. 5.6.1 [Watch] Window You can view any value in the [Watch] window. The [R] mark shows that the value of the variable can ...
Page 81
Read the memory content directly from the High-performance Embedded Workshop to update the values without halting the user program since the bus mastership is owned by the emulator Note: While the emulator reserves the bus mastership, the realtime operation ...
Page 82
Using the Event Points The emulator has the event point function that performs breaking, tracing, and execution time measurement by specifying higher-level conditions along with the software breakpoints standard for the High-performance Embedded Workshop. 5.7.1 Software Breakpoints When the ...
Page 83
A maximum of eight points can be used as a combination in a sequence. The program is activated or halted by an occurrence of the previous event in each sequence. Range Channels (Ch9 to Ch12): The emulator has 4 range ...
Page 84
Table 5.2 Area Signals Acquired by the Emulator Area Trace Display (Status) On-chip ROM ROM On-chip RAM RAM On-chip I/O 16bit I/O-16 On-chip I/O 8bit I/O-8 External I/O 16bit EXT-16 External I/O 8bit EXT-8 DTC RAM RAM/DTC Note: The signals ...
Page 85
Select [Add...] or the software breakpoint displayed in this window and then select [Edit...] from the popup menu to display the [Breakpoint/Event Properties] dialog box. Figure 5.20 [Breakpoint/Event Properties] Dialog Box (Setting a Software Break) In this dialog box, select ...
Page 86
Setting Event Points On the [Event] sheet, the settings for event points are displayed, modified, and added. Figure 5.21 [Event] Window ([Event] Sheet) Select [Add...] or the event point displayed in this window and then select [Edit...] from the ...
Page 87
The address and data conditions are set. Figure 5.22 [Breakpoint/Event Properties] Dialog Box ([General] Page) [Type]: Select the type of a breakpoint. Note that the [Breakpoint/Event Properties] dialog box is used for setting software breakpoints and event ...
Page 88
Compare]: Sets the data condition. [Compare]: Checking this box compares data. [Use Mask]: Sets a mask condition (available when [Compare] has been selected). [Value]: Specifies the data bus value as numerics. The size of data for access can also ...
Page 89
Use this page to set the bus status and the memory area being accessed. Figure 5.23 [Breakpoint/Event Properties] Dialog Box ([Bus/Area] Page) [Bus State]: Sets the bus status as the condition. When the [Don't care] check box ...
Page 90
Use this page to set external signals. Figure 5.24 [Breakpoint/Event Properties] Dialog Box ([Signals] Page) [Probe4]: Detects the status of the input probe signal 4 [High]: Detects the high level of the input probe signal [Low]: Detects ...
Page 91
Detects the status of the input probe signal 1 [High]: Detects the high level of the input probe signal [Low]: Detects the low level of the input probe signal [Don’t care]: The status of the input probe signal is ...
Page 92
Allows a 16-bit pass count to be set. The event must occur the specified number of times before the action is taken. The range of values is D’0 to D’65,535. [Enable Sequencing]: Allows the event ...
Page 93
The state where the condition is satisfied is retained until the user program is stopped or the event point is reset. When the condition on the event point is satisfied, no action will be taken even if the condition is ...
Page 94
Setting Trigger Points The trigger point is an event to output a trigger when the specified address has been accessed four trigger points can be set by using the trigger outputs (four channels) on the bus monitoring ...
Page 95
Notes: 1. When the condition set for the trigger output ( satisfied, the high-level signal will be output from the corresponding pin ( the external probe 2 (EXT2) during reading or writing. 2. Some ...
Page 96
Viewing the Trace Information The emulator acquires the results of each instruction execution into the trace buffer as trace information and displays it in the [Trace] window. The conditions for the trace information acquisition can be specified in the ...
Page 97
Bus status during this cycle; DTC operation, PROG (prefetch), Data (CPU data access cycle), Refresh (refresh cycle), or DMAC (DMAC cycle) (not available when a time stamp is acquired) [Clock]: Number of clock cycles in bus cycle as 1 ...
Page 98
Specifying Trace Acquisition Conditions The capacity of the trace buffer is limited. When the buffer becomes full, the oldest trace information is overwritten. Setting the trace acquisition condition allows acquisition of useful trace information and effective use of the ...
Page 99
Acquires no trace information of the specified types of bus cycle. [Time Stamp]: Sets a condition for time stamping. [Clock]: Select either from Disabled, 125 ns, 250 ns, 500 ns, 1 us, 2 us, 4 us, 8 us, 16 ...
Page 100
Sets trace stop conditions possible to set trace stop conditions with and without delay, with both allowed simultaneously. Figure 5.31 [Trace Acquisition] Dialog Box ([Stop] Page) [Stop Without Delay]: Defines a trace stop condition. [Enable]: ...
Page 101
Stop] page Sets trace stop conditions possible to set trace stop conditions with and without delay, with both allowed simultaneously. Figure 5.32 [Trace Acquisition] Dialog Box ([Delayed Stop] Page) [Stop With Delay]: Defines a trace stop ...
Page 102
Sets a range trace. This is only available when the free trace mode is disabled. Select either of the following four modes: [Disabled], [Point to Point], [Range], and [Event]. • Disabled Disables a range trace. ...
Page 103
Point to Point Acquires trace information in the specified range. Figure 5.34 Range Trace Setting (Point to Point) [Start Address]: Address where trace acquisition starts [Stop Address]: Address where trace acquisition stops [Cyclic]: When this box is checked, the ...
Page 104
Range Only acquires the trace information that satisfies the specified condition. Figure 5.35 Range Trace Setting (Range) [Range Event]: Selects an event point for which a trace acquisition condition has been set. [Edit…]: Changes the setting for the selected ...
Page 105
Event Acquires trace information, controlling the start and end of trace acquisition with the specified condition. Figure 5.36 Range Trace Setting (Event) [Start Event]: Selects the event point for which the condition to start trace acquisition has been set. ...
Page 106
Searching for a Trace Record Use the [Trace Find] dialog box to search for a trace record. To open this dialog box, choose [Find...] from the popup menu. The [Trace Find] dialog box has the following options: Table 5.5 ...
Page 107
Set the range for searching. Figure 5.37 [Trace Find] Dialog Box ([General] Page) [Trace search range]: Sets the range for searching. [Not designation]: [Upward search]: [Start PTR]: [End PTR]: Note: Along with setting the range for searching, ...
Page 108
Set an address condition. Figure 5.38 [Trace Find] Dialog Box ([Address] Page) [Don't care]: Detects no address when this box is checked. [Setting]: Detects the specified address. [Value]: Enter the address value (not available when [Don’t care] ...
Page 109
Set a data condition. Figure 5.39 [Trace Find] Dialog Box ([Data] Page) [Don't care]: Detects no data when this box is checked. [Setting]: Detects the specified data. [Value]: Enter the data value (not available when [Don’t care] ...
Page 110
Select the type of access cycles. Figure 5.40 [Trace Find] Dialog Box ([R/W] Page) [Don't care]: Detects no read/write condition when this box is checked. [Setting]: Detects the specified read/write condition. [String]: Select a read/write condition (not ...
Page 111
Select the area being accessed. The selection is not available when a time stamp is acquired. Figure 5.41 [Trace Find] Dialog Box ([Area] Page) [Don't care]: Detects no area condition when this box is checked. [Setting]: Detects ...
Page 112
Select the status of a bus. The selection is not available when a time stamp is acquired. Figure 5.42 [Trace Find] Dialog Box ([Status] Page) [Don't care]: Detects no bus condition when this box is checked. [Setting]: ...
Page 113
Select the status of four probe signals. The selection is not available when a time stamp is acquired. Figure 5.43 [Trace Find] Dialog Box ([Probes] Page) [Don't care]: Detects no probe signal condition when this box is ...
Page 114
Select the status of IRQ signals. The selection is not available when a time stamp is acquired. Figure 5.44 [Trace Find] Dialog Box ([IRQ7-0] Page) [Don't care]: Detects no IRQ input condition when this box is checked. ...
Page 115
Specify the time stamp value for bus cycles. The specification is not available when a time stamp is acquired. Figure 5.45 [Trace Find] Dialog Box ([Timestamp] Page) [Don't care]: Detects no time stamp value when this box ...
Page 116
Viewing the [Editor] Window The [Editor] window corresponding to the selected trace record can be displayed in the following two ways: • Select a trace record and choose [View Source] from the popup menu. • Double-click a trace record ...
Page 117
Extracting Records from the Acquired Information Use the filtering function to extract the records you need from the acquired trace information. The filtering function allows the trace information acquired by hardware to be filtered by software. Unlike the settings ...
Page 118
Set the range for filtering. Figure 5.46 [Trace Filter] Dialog Box ([General] Page) [Don't care other pages]: Only selects the cycle number when this box is checked. Other options become invalid. [Enable Filter]: Enables the filter when ...
Page 119
Set address conditions. Figure 5.47 [Trace Filter] Dialog Box ([Address] Page) [Don't care]: Detects no address when this box is checked. [Setting]: Detects the specified address. [Point]: Specifies a single address (not available when [Don’t care] has ...
Page 120
Set a data condition. Figure 5.48 [Trace Filter] Dialog Box ([Data] Page) [Don't care]: Detects no data when this box is checked. [Setting]: Detects the specified data. [Point]: Specifies single data (not available when [Don’t care] has ...
Page 121
Select the type of access cycles. Figure 5.49 [Trace Filter] Dialog Box ([R/W] Page) [Don't care]: Detects no read/write condition when this box is checked. [Setting]: Detects the specified read/write condition. RD: Detects read cycles when this ...
Page 122
Select the area being accessed. The selection is not available when a time stamp is acquired. Figure 5.50 [Trace Filter] Dialog Box ([Area] Page) [Don't care]: Detects no area condition when this box is checked. [Setting]: Detects ...
Page 123
Select the status of a bus. The selection is not available when a time stamp is acquired. Figure 5.51 [Trace Filter] Dialog Box ([Status] Page) [Don't care]: Detects no bus condition when this box is checked. [Setting]: ...
Page 124
Select the status of four probe signals. The selection is not available when a time stamp is acquired. Figure 5.52 [Trace Filter] Dialog Box ([Probes] Page) [Don't care]: Detects no probe signal condition when this box is ...
Page 125
Select the status of IRQ signals. The selection is not available when a time stamp is acquired. Figure 5.53 [Trace Filter] Dialog Box ([IRQ7-0] Page) [Don't care]: Detects no IRQ input condition when this box is checked. ...
Page 126
Specify the time stamp value for bus cycles. The specification is not available when a time stamp is acquired. Figure 5.54 [Trace Filter] Dialog Box ([Timestamp] Page) [Don't care]: Detects no time stamp value when this box ...
Page 127
Calculating the Difference in Time Stamping Select [Timestamp Difference…] from the popup menu to calculate the time difference between the two points selected by the result of tracing in acquisition of time stamp information. Figure 5.55 [Timestamp Difference] Dialog ...
Page 128
Analyzing Statistical Information Choose [Statistic] from the popup menu to open the [Statistic] dialog box and analyze statistical information under the specified conditions. [Statistic Analysis]: Setting required for analysis of statistical information. [Default]: Sets a single input value or ...
Page 129
This dialog box allows the user to analyze statistical information concerning the trace information. Set the target of analysis in [Item] and the input value or character string by [Start] and [End]. Click the [Result] button after setting a condition ...
Page 130
Analyzing Performance Use the performance analysis function to measure the rate of execution time. The performance analysis function does not affect the realtime operation because it measures the rate of execution time in the specified range by using the ...
Page 131
Table 5.8 Mode Settings for Measurement Page 1 Ο Time Of Specified Range Measurement Ο Start Point To End Point Measurement Ο Start Range To End Range Measurement Ο Access Count Of Specified Range Measurement Ο Called Count Of Specified ...
Page 132
Opening the [Performance Analysis] Window Choose [View -> Performance -> Performance Analysis] or click the [PA] toolbar button ( [Select Performance Analysis Type] dialog box. Figure 5.58 [Select Performance Analysis Type] Window Select [E6000 Performance Analysis] and then click ...
Page 133
Setting Conditions for Measurement Conditions for measurement can be displayed and changed in the [Performance Analysis] window. Select a point where a condition set, and then select [Set…] from the popup menu to display the [Performance ...
Page 134
Time Of Specified Range Measurement Figure 5.61 Time Of Specified Range Settings [Range Name]: The name of the range to be measured [Range]: The range for the Time Of Specified Range Measurement [Start Address]: [End Address]: Measures the execution ...
Page 135
Start Point To End Point Measurement Figure 5.62 Start Point To End Point Measurement Settings [Range Name]: The name of the range to be measured [Point]: The range for the Start Point To End Point Measurement [Start Address]: [End ...
Page 136
Notes: 1. When [Time Out] is selected in the Start Point To End Point Measurement mode, the execution time will not be measured correctly. 2. When [Time Out] and [Count] are selected, satisfaction of either of these options stops execution ...
Page 137
Start Range To End Range Measurement Figure 5.63 Start Range To End Range Measurement Settings [Range Name]: The name of the range to be measured [Start Range]: The start range for the Start Range To End Range Measurement [Start ...
Page 138
Access Count Of Specified Range Measurement Figure 5.64 Access Count Of Specified Range Measurement Settings [Range Name]: The name of the range to be measured [Range]: The range for the Access Count Of Specified Range Measurement [Start Address]: [End ...
Page 139
Called Count Of Specified Range Measurement Figure 5.65 Called Count Of Specified Range Measurement Settings [Range Name]: The name of the range to be measured [Range]: The range for the Called Count Of Specified Range Measurement [Start Address]: [End ...
Page 140
Selecting the Address Detection Mode and Resolution In measurement of hardware performance, there are two types of address detection modes: prefetch address detection mode and PC address detection mode. Select the appropriate address detection mode according to the measurement ...
Page 141
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 ...
Page 142
Running the High-performance Embedded Workshop Open a workspace by following the procedure listed in section 4.1.3, Selecting an Existing Workspace. Select the following directory: OS installation drive \Workspace\Tutorial\E6000\2646 Note: The file path differs depending on the product. Refer to ...
Page 143
Downloading the Tutorial Program 6.3.1 Downloading the Tutorial Program Download the object program to be debugged. • Select [Download module] from the popupmenu opened by clicking the right-hand mouse button on [Tutorial.abs] of [Download modules]. Figure 6.2 Downloading the ...
Page 144
Displaying the Source Program The High-performance Embedded Workshop allows the user to debug a user program at the source level. • Double-click [Tutorial.cpp] under [C++ source file]. Figure 6.3 [Editor] Window (Displaying the Source Program) • Select a font ...
Page 145
Setting a Software Breakpoint A software breakpoint is a simple debugging function. The [Editor] window provides a very simple way of setting a software breakpoint at any point in a program. For example, to set a software breakpoint at ...
Page 146
Setting Registers Set a value of the program counter before executing the program. • Select [Registers] from the [CPU] submenu of the [View] menu. The [Register] window is displayed. • To change the value of the program counter (PC), ...
Page 147
Executing the Program Execute the program as described in the following: • To execute the program, select [Go] from the [Debug] menu, or click the [Go] button on the toolbar. While the program is executing, the current address bus ...
Page 148
Figure 6.8 [Editor] Window (Break Status) 126 ...
Page 149
The user can see the cause of the break that occurred last time in the [Status] window. • Select [Status] from the [CPU] submenu of the [View] menu. After the [Status] window is displayed, open the [Platform] sheet, and check ...
Page 150
Reviewing Breakpoints The user can see all the breakpoints set in the program in the [Event] window. • Select [Eventpoints] from the [Code] submenu of the [View] menu. The [Event] window is displayed. Select the [Breakpoint] sheet. The popup ...
Page 151
Referring to Symbols The [Label] window can be used to display the information on symbols in modules. Select [Label] from the [Symbol] submenu of the [View] menu. The [Label] window is displayed so that the user can refer to ...
Page 152
Viewing Memory When the label name is specified, the user can view the memory contents that the label has been registered in the [Memory] window. For example, to view the memory contents corresponding to _main in byte size: • ...
Page 153
Watching Variables As the user steps through a program possible to watch that the values of variables used in the user program are changed. For example, set a watch on the long-type array a declared at the ...
Page 154
The user can also add a variable to the [Watch] window by specifying its name. • Click the [Watch] window with the right-hand mouse button and select [Add Watch…] from the popup menu. The following dialog box will be displayed. ...
Page 155
The user can click mark ‘+’ at the left side of array a in the [Watch] window to watch all the elements. Figure 6.18 [Watch] Window (Displaying Array Elements) 133 ...
Page 156
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 tutorial function, which declares four local variables and p_sam. • ...
Page 157
Stepping Through a Program The High-performance Embedded Workshop provides a range of step menu commands that allow efficient program debugging. Table 6.1 Step Option Menu Command Description Step In Executes each statement, including statements within functions. Step Over Executes ...
Page 158
Figure 6.21 [Editor] Window (Step In) • The highlighted line moves to the first statement of the sort function in the [Editor] window. 136 ...
Page 159
Executing the [Step Out] Command The [Step Out] command 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 ...
Page 160
Executing the [Step Over] Command The [Step Over] executes a function call as a single step and stops at the next statement of the main program. • To step through all statements in the change function at a single ...
Page 161
Forced Breaking of Program Executions The High-performance Embedded Workshop can force a break in the execution of a program. • Cancel all the breaks. • To execute the remaining sections of the tutorial function, select [Go] from the [Debug] ...
Page 162
Break Function The emulator’s break functions are of two types: software breaks and breaks at event points. software breakpoints and event points are set in the High-performance Embedded Workshop’s [Event] window. An overview and setting of the break function ...
Page 163
Figure 6.31 [Breakpoint/Event Properties] Dialog Box • Check the [Software Break] radio button in the [Type] group box. • Use the [Editor] window to refer to the address on the line that has ‘p_sam->s0=a[0];’ within the tutorial function and enter ...
Page 164
The software breakpoint that has been set is displayed in the [Event] window. Figure 6.32 [Event] Window (Software Breakpoint Setting) Note: The items that can be displayed in this window differ depending on the product. For the items that can ...
Page 165
Close the [Event] window. • To stop the tutorial program at the breakpoint, select [Reset Go] from the [Debug] menu. The program runs until it stops at the breakpoint that has been set. Figure 6.33 [Editor] Window at Execution ...
Page 166
The [Status] window displays the following contents: Figure 6.34 Displayed Contents of the [Status] Window (Software Break) Note: The items that can be displayed in this window differ depending on the product. For the items that can be displayed, refer ...
Page 167
Breaking Execution at Event Points Setting event point on event channel 1 (Ch1) such that a break is triggered when the event point’s conditions have been satisfied five times is explained as an example of the ...
Page 168
Figure 6.36 [General] Page ([Breakpoint/Event Properties] Dialog Box) • Click the [OK] button. The [Event] window is displayed, as shown below. Figure 6.37 [Event] Window (Setting Completed) Note: The items that can be displayed in this window differ depending on ...
Page 169
Select [Reset Go] from the [Debug] menu to stop the tutorial program at breakpoints. The program runs then stops at the condition specified under Ch1. Figure 6.38 [Editor] Window at Execution Stop 147 ...
Page 170
The [Status] window displays the following contents. Figure 6.39 Displayed Contents of the [Status] Window Refer to the [Watch] window for the value of variable i. The value is 4, indicating that the break occurred after the condition had been ...
Page 171
Trace Functions The trace functions of the emulator use the realtime trace buffer, which is able to store the information 32,768 bus cycles. The content of this buffer, which is constantly updated during execution, is displayed ...
Page 172
Displaying a Trace (when Time Stamping is not Available) The method used to specify an address as an event condition for the tracing of read/write cycles and display the trace is described below. (1) Clicking the right-hand mouse button ...
Page 173
Register an address as an event condition for trace acquisition. Click the [Add…] button in the [Trace Events] group box on the [General] page to display the [Breakpoint/Event Properties] dialog box. Figure 6.42 [Breakpoint/Event Properties] Dialog Box (3) Use ...
Page 174
The event that has been set is now displayed in the [Event] combo box of the [Trace Events] group box on the [General] page of the [Trace Acquisition] dialog box. Figure 6.44 [Trace Acquisition] Dialog Box (Adding an Event) ...
Page 175
To enable the event condition that has been set, uncheck the [Free Trace] check box on the [General] page. This will add pages [1] to [4] to the [Trace Acquisition] dialog box. Figure 6.45 [Trace Acquisition] Dialog Box (Pages ...
Page 176
Select page [1] and click the [Range] radio button in the [Conditions] group box. This will display the [Range Event] combo box and the [Edit…] button. Figure 6.46 [Trace Acquisition] Dialog Box (Displaying Page [1]) 154 ...
Page 177
Select the event you have registered from the [Range Event] combo box. The event is now enabled. Click the [OK] button to complete the trace setting. Figure 6.47 [Trace Acquisition] Dialog Box (Setting Completed) (8) Make the setting such ...
Page 178
Remove the event points that have been set and clear the trace information. Click the right-hand mouse button on the [Event] window to display a popup menu. Select [Delete All] from this menu to remove all of the event ...
Page 179
The event that has been set in the [Event] combo box of the [Trace Events] group box on the [General] page of the [Trace Acquisition] dialog box is displayed. Figure 6.50 [Trace Acquisition] Dialog Box (Adding an Event) (6) ...
Page 180
To enable the event condition that has been set, uncheck the [Free Trace] check box on the [General] page. This will add pages [1] to [4] (see figure 6.45, [Trace Acquisition] dialog box). (8) Select page [1] and click ...
Page 181
Select [Reset Go] from the [Debug] menu. Processing stops when the break condition is satisfied, and the [Trace] window then displays the following content. Figure 6.53 [Trace] Window (Displaying the Result) If you have trouble viewing a column, drag ...
Page 182
Statistics The number of times the internal RAM has been written to can be included in the acquired trace information. (1) Make the setting such that a break occurs at the address on the line that has ‘p_sam->s0=a[0];’ within ...
Page 183
Select R/W in the [Item] combo box and enter WR in the [Start] edit box. After that, click the [New] button. “R/W=WR” is now displayed in the [Condition] column of the [Result] list box. Figure 6.55 [Statistic] Dialog Box ...
Page 184
Then, select Area from the [Item] combo box and enter RAM in the [Start] edit box. After that, click the [Add] button; the new condition is now added to the “R/W=WR” display in the [Condition] column of the [Result] ...
Page 185
To start statistical analysis of the specified condition, press the [Result] button. The number of write operations that satisfy the condition and the PTR values will be displayed. Figure 6.57 [Statistic] Dialog Box (Result of Analysis) (7) Click the ...
Page 186
Function Calls This mechanism is used to only collect trace information on the function calls. (1) Make the setting such that a break occurs at the address on the line that has ‘p_sam->s0=a[0];’ within the tutorial function (H’00001082 in ...
Page 187
Stack Trace Function The emulator uses the information on the stack to display the function call history. Notes: 1. This function can be used only when the load module that has the Dwarf2-type debugging information is loaded. Such load ...
Page 188
Figure 6.61 shows that the position of the program counter is currently at the selected line of the sort() function, and that the sort() function is called from the tutorial() function. To remove the software breakpoint, double-click the [Editor] column ...
Page 189
Performance Measurement Function Performance measurement by the emulator is in the following modes: • Time Of Specified Range Measurement • Start Point To End Point Measurement • Start Range To End Range Measurement • Access Count Of Specified Range ...
Page 190
Select the line of the [Performance Analysis] window that has 1 in its [No] column and click the right-hand mouse button to display a popup menu. Select [Set…] from this popup menu to display the [Performance Analysis Properties] dialog ...
Page 191
Click the [Settings…] button in the [Common Settings of Performance(PA1-8)] group box to display the [Common Settings of Performance(PA1-8)] dialog box. Select [PC] from the [Address Control Mode] combo box and then click the [OK] button now ...
Page 192
Monitor Function The emulator allows monitoring of the content of specified addresses in memory during execution of the user program. In this example, we monitor the content of the address range where variable a of the tutorial function is ...
Page 193
Set the items in the [Monitor Setting] dialog box as follows: • Enter monitor1 in the [Name] edit box. • Set the parameters in the [Options] group box as follows: (a) Use the [Locals] window to refer to the ...
Page 194
Click the [OK] button to open the [Monitor] window. (4) Select [Reset Go] from the [Debug] menu. When the content of the address range changes with execution, the updated values are red (i.e. the color that was selected in ...
Page 195
Section 7 Hardware Specifications Specific to This Product This section describes the hardware specifications on the H8S/2214 E6000 emulator. 7.1 H8S/2214 E6000 Emulator Specifications The H8S/2214 E6000 emulator supports the system development using the following microcomputers: • H8S/2218 group • ...
Page 196
... H8S/2276, H8S/2276R group 2.7-3.6 Note: Only the HS2214EPI62H can support the frequency from MHz. MCUs cannot be operated with the frequency from MHz when the HS2214EPI61H is in use. For details on the operating voltage and frequency specifications, refer to the MCU hardware manual. ...
Page 197
User System Interface All user system interface signals are directly connected to the MCU in the emulator with no buffering except for those listed below which are connected to the MCU through control circuits: • NMI • RESET • ...
Page 198
RESET and NMI: The RESET and NMI signals are input to the MCU through the emulator control circuit. The rising/falling time of these signals must be 8 ns/V or less. Emulator control circuit Figure 7.3 User System Interface Circuit for ...
Page 199
Differences between MCU and Emulator When the emulator is turned on or initialized, or the system is reset, there are some differences in the initial values in some of the general registers between the MCU and the emulator as ...
Page 200
178 ...