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 H8/3664 E6000 Emulator User’s Manual Renesas Microcomputer Development Environment System H8 Family / H8/300H Tiny Series HS3664EPI62HE-U2 Rev.6.00 2007.02...
Page 5 Please be sure to implement safety measures to guard against the possibility of physical injury, and injury or damage caused by fire in the event of the failure of a Renesas product, such as safety design for hardware and software including but not limited to redundancy, fire control and malfunction prevention, appropriate treatment for aging degradation or any other applicable measures.
Page 7 Renesas sales company. Such use includes, but is not limited to, use in life support systems. Buyers of this emulator product must notify the relevant Renesas sales offices before planning to use the product in such applications.
Page 8 This warranty extends only to you, the original Purchaser. It is not transferable to anyone who subsequently purchases the emulator product from you. Renesas is not liable for any claim made by a third party or made by you for a third party.
Page 9 This user's manual and emulator product are copyrighted and all rights are reserved by Renesas. No part of this user's manual, all or part, may be reproduced or duplicated in any form, in hard-copy or machine-readable form, by any means available without Renesas' prior written consent.
Page 10 SAFETY PAGE READ FIRST • READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference. Do not attempt to use the emulator product until you fully understand its mechanism. DEFINITION OF SIGNAL WORDS This is the safety alert symbol.
Page 11 WARNING Observe the precautions listed below. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emulator product or will result in PERSONAL INJURY. The USER PROGRAM will be LOST. 1. Do not repair or remodel the emulator product by yourself for electric shock prevention and quality assurance.
Page 12 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 13 High-performance Embedded Workshop is a Graphical User Interface intended to ease the development and debugging of applications written in C/C++ programming language and assembly language for Renesas microcomputers. Its aim is to provide a powerful yet intuitive way of accessing, observing and modifying the debugging platform in which the application is running.
Page 14 It indicates that the text to its immediate right is describing “how to” (The “how to” symbol) do something. Components Check all the components described in the component list unpacking. If the components are not complete, contact a Renesas sales office.
Page 15: Table Of Contents
Contents Emulator Debugger Part Section 1 Overview................... 1 Features ..........................1 Warnings ...........................2 Environmental Conditions ....................3 Emulator External Dimensions and Mass .................3 Section 2 Preparation before Use..............5 Emulator Preparation ......................5 Installing Emulator’s Software ..................5 Connecting to the User System ..................6 2.3.1 Example of Connecting the User System Interface Cable Head to the User System....................6...
Page 16 3.3.3 Probes ........................23 3.4 Stack Trace Function ......................23 3.5 Online Help.......................... 23 Section 4 Preparation before Use ..............25 Method for Activating High-performance Embedded Workshop........25 4.1.1 Creating a New Workspace (Toolchain Not Used)..........26 4.1.2 Creating a New Workspace (Toolchain Used)............30 4.1.3 Selecting an Existing Workspace................
Page 17 5.7.12 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 Viewing the Trace Information ..................74 5.8.1 Opening the [Trace] Window ................74 5.8.2 Acquiring Trace Information ................74 5.8.3 Specifying Trace Acquisition Conditions ............76 5.8.4...
Page 18 6.16.2 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 6.19 Monitor Function .......................
Page 19 System Set-Up for Test Program Execution ..............241 Diagnostic Test Procedure Using Test Program ...............242...
Page 20 viii...
Page 21: Emulator Debugger Part
Emulator Debugger Part...
Page 23: Section 1 Overview
Section 1 Overview 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, USB interface, or LAN interface can be used for connecting to the host computer.
Page 24: Warnings
Warnings CAUTION READ the following warnings before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. 1. Check all components against the component list after unpacking the emulator. 2.
Page 25: Environmental Conditions
Environmental Conditions CAUTION Observe the conditions listed in table 1.1 when using the emulator. Failure to do so will cause illegal operation in the user system, the emulator product, and the user program. Table 1.1 Environmental Conditions Item Specifications Temperature Operating: +10°C to +35°C Storage: –10°C to +50°C...
Page 27: Section 2 Preparation Before Use
Section 2 Preparation before Use Emulator Preparation Unpack the emulator and prepare it for use as follows: WARNING READ the reference sections shaded in figure 2.1 before using the emulator product. Incorrect operation will damage the user system and the emulator product. The USER PROGRAM will be LOST. Reference Component list Unpack the emulator...
Page 28: Connecting To The User System
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 cable body into the cable head. For details of these steps, refer to the User System Interface Cable User’s Manual.
Page 29: Plugging The User System Interface Cable Body Into The Emulator
• 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 the screws as this may result in contact failure on the user system or damage the cable head.
Page 30: Power Supply
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. 5 V (outside) GND (inside) Figure 2.6 Polarity of Power Supply Plug 2.4.3 Power Supply Monitor Circuit The emulator incorporates a power supply monitor circuit which only lights the green LED when a voltage...
Page 31: Hardware Interface
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 are over/under voltage protected by use of diode arrays. The only exceptions being the AV and Vref.
Page 32: External Probe 2 (Ext2)/Trigger Output
The interface circuit for the external probe 1 is shown in figure 2.8. Ω 10 k External probe 1, 2, 3, 4 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 is available as either T5V (within the range from 2.5 V to 5 V;...
Page 33: Voltage Follower Circuit
2.6.6 Voltage Follower Circuit CAUTION 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 which allows the user system voltage level from the user system to be monitored.
Page 34: System Check
2.7 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 Emulator, for the other activating method to create a new project or use a workspace for the High-performance Embedded Workshop of the old version.
Page 35 Note: The directory mentioned above cannot be specified depending on the version of the software. In such cases, specify the following directory instead. High-performance Embedded Workshop installation destination directory \Tools\Renesas\DebugComp\Platform\E6000\xxxx\Tutorial After the directory has been specified, select the following file and click the [Open] button. Figure 2.13 [Open Workspace] Dialog Box...
Page 36 When no compiler package or that of a different version is installed, the following message box will be displayed. Figure 2.14 Message Box 6. The [E6000 Driver Details] dialog box is displayed. This dialog box is only displayed at the first initiation. When only one of interface drivers is selected, this dialog box is not displayed.
Page 37 7. Set up the emulator. During this process, the following dialog box is displayed. Figure 2.16 [Connecting] Dialog Box...
Page 38 8. 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...
Page 39: Communication Problems
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. Figure 2.18 Error Message For information on other errors, refer to the Setup Guide for the E6000 Emulator. 2.9 Other Methods for Activating the Emulator Refer to section 4, Preparation before Use.
Page 41: Section 3 E6000 Emulator Functions
Section 3 E6000 Emulator Functions 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: Up to 12 break conditions can be defined using the event and range channels in the complex event system (CES).
Page 42: Bus Monitoring
3.1.5 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. Up to eight blocks of 256 bytes can be monitored. In addition, the emulator can output trigger signals from external probe 2 (EXT2) when specified addresses (four points max.) are accessed.
Page 43: Range Channels
3.2.2 Range Channels The range channels can be set up to be 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 an optional mask •...
Page 44: Hardware Features
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 emulation memory is disabled. When debugging with only the emulator and the user program and data are stored in an external address space, an optional SIMM memory module must be used.
Page 45: Clocks
3.3.2 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 Product. 3.3.3 Probes External probes 1 and 2 (EXT1 and EXT2) can be connected to the emulator, to make use of signals on the user...
Page 47: Section 4 Preparation Before Use
Section 4 Preparation before Use 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 connector of the emulator if you use the user system interface cable.
Page 48: Creating A New Workspace (Toolchain Not Used)
4.1.1 Creating a New Workspace (Toolchain Not Used) 1. In 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. Figure 4.2 [Welcome!] Dialog Box...
Page 49 2. 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 project name is the same as the workspace name, it needs not be entered.
Page 50 3. 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 be selected here. Check the box against the target platform and then click the [Next] button.
Page 51 4. 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 file for each of them, each time pressing the [Next] button to proceed to the next target.
Page 52: Creating A New Workspace (Toolchain Used)
4.1.2 Creating a New Workspace (Toolchain Used) 1. In 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. Figure 4.6 [Welcome!] Dialog Box...
Page 53 2. 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 name. When the project name is the same as the workspace name, it needs not be entered.
Page 54 3. 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 Embedded Workshop is activated must be selected here.
Page 55 4. 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 file for each of them, each time pressing the [Next] button to proceed to the next target.
Page 56: Selecting An Existing Workspace
4.1.3 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. Figure 4.10 [Welcome!] Dialog Box 2. The [Open Workspace] dialog box is displayed. Select a directory in which you have created a workspace. After that, select the workspace file (.hws) and press the [Open] button.
Page 57: Connecting The Emulator
4.2 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. It is possible to register the download module or the command chain that is automatically executed at activation.
Page 58: Reconnecting The Emulator
4.3 Reconnecting the Emulator When the emulator is disconnected, use the following way for reconnection: Select [Debug -> Connect] or click the [Connect] toolbar button ( ). The emulator is connected. Note: Before reconnecting the emulator, a load module must be registered to the High-performance Embedded Workshop.
Page 59: Section 5 Debugging
Section 5 Debugging 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 ⎯...
Page 60: Setting The Environment For Emulation
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 ( ) opens the Configuration Properties] dialog box. Figure 5.1 [Configuration Properties] Dialog Box ([General] Page) This dialog allows the user to set conditions for the target MCU before downloading a program to the emulator.
Page 61 [General] page [Device] Selects the MCU to be emulated. To use an MCU not included in the list, select CUSTOM to specify the functions required for this MCU. See the hardware manual for details. [Mode] Selects the MCU's operating mode. [Clock] Selects the speed of the MCU’s clock and sub-clock.
Page 62: Selecting An Mcu Not Included In The List
5.1.2 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 to specify functions for an MCU not included in the list of MCUs. The items are adopted by the device last selected.
Page 63: Selecting The Interface To Be Connected
5.1.3 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 driver that connects the High-performance Embedded Workshop and the emulator. [Details]: Sets the details of the driver being connected.
Page 64: Opening The [Memory Mapping] Dialog Box
5.1.4 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 the current memory map. The E6000 H8S or H8/300 series supports four blocks of user memory.
Page 65: Changing The Memory Map Setting
5.1.5 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 box. Figure 5.5 [Edit Memory Mapping] Dialog Box Use this dialog box to change the address range and attributes of a memory map.
Page 66: Downloading A Program
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 editor. In most cases, for example if an Elf/Dwarf2 based project is moved from its original path (at the build), the source file may not be automatically found.
Page 67: Viewing The Source Code
5.2.2 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. Figure 5.6 [Editor] Window In this window, the following items are shown on the left as information on lines.
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 the following items: : Address condition break by an event or a range channel : Starts time measurement by an event channel : Ends time measurement by an event channel...
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. 4. A check box indicates whether the column is enabled or not. If it is checked, the column is enabled. If the check box is gray, the column is enabled in some files and disabled in others.
Page 70: Viewing The Assembly-Language Code
5.2.3 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. It is also possible to view the disassembly using the new integrated [Disassembly view] in the source file. If you do not have a source file, but wish to view code at assembly-language level, then select one of the following operations: Click on the View Disassembly toolbar button (...
Page 71: Modifying The Assembly-Language Code
5.2.4 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. Figure 5.9 [Assembler] Dialog Box The address, instruction code, and mnemonic are displayed. Enter the new instruction or edit the old instruction in the [Mnemonics] field.
Page 72: Viewing The Current Status
Viewing the Current Status Choose [View -> CPU -> Status] or click the [View Status] toolbar button ( ) to open the [Status] window and see the current status of the debugging platform. Figure 5.11 [Status] Window The [Status] window has three sheets: •...
Page 73: Reading And Displaying The Emulator Information Regularly
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 of the user program since it monitors the user system or the signal output from the MCU in the emulator by using the emulator’s hardware circuit.
Page 74: Selecting Items To Be Displayed
5.4.2 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 the [Extended Monitor] window. Note: The items that can be set in this dialog box vary according to the emulator in use.
Page 75: Displaying Memory Contents In Realtime
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 of the MCU as a trigger and holds the address bus and data bus values to update the displayed contents of the memory.
Page 76 [Name]: Decides the name of the monitor window. [Options]: Sets monitor conditions. [Address]: Sets the start address for monitoring. [Size]: Sets the range for monitoring. [Access]: Sets the access size to be displayed in the monitor window. [Auto-Refresh at rate (ms)]: Sets the interval for acquisition by monitoring (500 ms at minimum).
Page 77: Changing The Monitor Settings
Figure 5.15 [Monitor] Window 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 the Monitor Settings Selecting [Monitor Setting…] from the popup menu of the [Monitor] window displays the [Monitor Setting]...
Page 78: Hiding The [Monitor] Window
5.5.6 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 submenu when selecting [Display -> CPU -> Monitor]. The list consists of the [Monitor] window name and the address to start monitoring.
Page 79: Managing The [Monitor] Window
5.5.7 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 succession. Selecting multiple monitoring conditions enables a temporary stop of update, hiding, and deletion.
Page 80: Viewing The Variables
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. Figure 5.18 [Watch] Window The [R] mark shows that the value of the variable can be updated during user program execution. For updating of the content of the variable that has been registered in the [Watch] window, there are the following three methods: 1.
Page 81 2. 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 is disabled because the CPU stops operation.
Page 82: Using The Event Points
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 instruction of the specified address is fetched, the user program is stopped. Up to 256 points can be set. Note that, however, only one software breakpoint can be set in the ROM area of the user system.
Page 83: Signals To Indicate Bus States And Areas
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 channels. The range channel can be defined as a combination of one or more of the followings: •...
Page 84: Opening The [Event] Window
Table 5.2 Area Signals Acquired by the Emulator Area Trace Display (Status) Description On-chip ROM On-chip RAM On-chip I/O 16bit I/O-16 16-bit I/O On-chip I/O 8bit I/O-8 8-bit I/O External I/O 16bit EXT-16 16-bit EXT (external) External I/O 8bit EXT-8 8-bit EXT (external) DTC RAM RAM/DTC...
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 the address condition to set software breakpoints. [Type]: Select the type of a breakpoint.
Page 86: Setting Event Points
5.7.7 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 popup menu to display the [Breakpoint/Event Properties] dialog box.
Page 87 (1) [General] page 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 points. Selecting a particular type of breakpoint enables or disables other pages and parts of the dialog according to the options available to that type of breakpoint.
Page 88 [Data 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 be selected (available when [Compare] has been selected).
Page 89 (2) [Bus/Area] page 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 is checked, the event will be satisfied with any bus status.
Page 90 (3) [Signals] page 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 the low level of the input probe signal [Don’t care]: The status of the input probe signal is not detected [Probe3]:...
Page 91 [Probe1]: 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 not detected (4) [Action] page Use this page to decide what action the emulator takes when the defined event occurs.
Page 92 [Required number of event occurrences]: 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 to take part in a sequence of events (setting this requires the event to use an event detector).
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 satisfied again. If you want the action to be taken again, reset the event point so that the state transits to that where no condition is satisfied.
Page 94: Setting Trigger Points
5.7.8 Setting Trigger Points The trigger point is an event to output a trigger when the specified address has been accessed. Up to four trigger points can be set by using the trigger outputs (four channels) on the bus monitoring circuit of the emulator. The settings of the trigger point are displayed and modified on the [Trigger] sheet.
Page 95: Editing Event Points
Notes: 1. When the condition set for the trigger output (1 to 4) is satisfied, the high-level signal will be output from the corresponding pin (1 to 4) of the external probe 2 (EXT2) during reading or writing. 2. Some emulators may not support the trigger point. For details, refer to section 8, Software Specifications Specific to This Product, or the online help.
Page 96: Viewing The Trace Information
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 [Trace Acquisition] dialog box. Since trace information in bus-cycles is acquired by the hardware circuit and stored in the trace buffer, the realtime operation is retained.
Page 97 [Status]: 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 to 8. To indicate more clock cycles, “OVR” is displayed (not available when a time stamp is acquired).
Page 98: Specifying Trace Acquisition Conditions
5.8.3 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 trace buffer. The condition is enabled by the event point to control starting, stopping, and ending the trace acquisition.
Page 99 [Suppress]: 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 us, or 100 us as the resolution for time stamping.
Page 100 (2) [Stop] page Sets trace stop conditions. It is 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]: Checking this box enables a trace stop.
Page 101 (3) [Delayed Stop] page Sets trace stop conditions. It is 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 condition. [Enable]: Checking this box enables a trace stop.
Page 102 (4) [1] to [4] pages 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. Figure 5.33 Range Trace Setting (Disabled)
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 event sequencing is configured so that the events reset themselves which causes tracing to be restarted when the start event occurs after the stop event.
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 event point. Only acquires trace information from all bus cycles that matches the condition set in the selected event.
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. [Stop Event]: Selects the event point for which the condition to stop trace acquisition has been set.
Page 106: Searching For A Trace Record
5.8.4 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 [Trace Find] Dialog Box Pages Page Description...
Page 107 (1) [General] page Set the range for searching. Figure 5.37 [Trace Find] Dialog Box ([General] Page) [Trace search range]: Sets the range for searching. [Not designation]: Searches for information that does not match the conditions set in other pages when this box is checked. [Upward search]: Searches upwards when this box is checked.
Page 108 (2) [Address] page 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] has been checked).
Page 109 (3) [Data] page 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] has been checked).
Page 110 (4) [R/W] page 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 available when [Don’t care] has been checked). RD: Read cycle WR: Write cycle...
Page 111 (5) [Area] page 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 the specified area condition. [String]: Select an area condition (not available when [Don’t care] has been checked).
Page 112 (6) [Status] page 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]: Detects the specified bus condition.
Page 113 (7) [Probes] page 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 checked. [Setting]: Detects the specified probe signal condition.
Page 114 (8) [IRQ7-0] page 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. [Setting]: Detects the specified IRQ input condition.
Page 115: Clearing The Trace Information
(9) [Timestamp] page 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 is checked. [Setting]: Detects the specified time stamp value.
Page 116: Viewing The [Editor] Window
5.8.7 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 The [Editor] or [Disassembly] window opens and the selected line is marked with a cursor.
Page 117: Extracting Records From The Acquired Information
5.8.12 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 made in the [Trace Acquisition] dialog box for acquiring trace information by conditions, changing the settings for filtering several times to filter the acquired trace information allows easy extraction of necessary information, which is useful for analysis of data.
Page 118 (1) [General] page 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 this box is checked. [No]: Filters information that does not match the conditions set in those pages when this box is checked.
Page 119 (2) [Address] page 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 been checked). [Range]: Specifies an address range (not available when [Don’t care] has been checked).
Page 120 (3) [Data] page 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 been checked). [Range]: Specifies a data range (not available when [Don’t care] has been checked).
Page 121 (4) [R/W] page 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. Detects read cycles when this box is checked (not available when [Don’t care] has been checked).
Page 122 (5) [Area] page 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 the specified area condition (not available when [Don’t care] has been checked). Note: Available area conditions vary according to the emulator in use.
Page 123 (6) [Status] page 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]: Detects the specified bus condition (not available when [Don’t care] has been checked).
Page 124 (7) [Probes] page 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 checked. [Setting]: Detects the specified probe signal condition.
Page 125 (8) [IRQ7-0] page 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. [Setting]: Detects the specified IRQ input condition.
Page 126 (9) [Timestamp] page 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 is checked. [Setting]: Detects the specified time stamp value.
Page 127: Calculating The Difference In Time Stamping
5.8.13 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 Box [Select 2 line]: Select trace records to calculate the time stamp difference.
Page 128: Analyzing Statistical Information
5.8.14 Analyzing Statistical Information Choose [Statistic] from the popup menu to open the [Statistic] dialog box and analyze statistical information under the specified conditions. Figure 5.56 [Statistic] Dialog Box [Statistic Analysis]: Setting required for analysis of statistical information. [Default]: Sets a single input value or character string. [Range]: Sets the input value or character string as a range.
Page 129: Extracting Function Calls From The Acquired Trace Information
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 by pressing the [New] or [Add] button to analyze the statistical information and display its result in the [Result] list.
Page 130: Analyzing Performance
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 circuit for measurement of hardware performance included in the emulator. Select either of the following five modes according to the purpose of measurement.
Page 131 Table 5.8 Mode Settings for Measurement Point Page Ο Ο Ο Ο Ο Ο Ο Ο Time Of Specified Range Measurement Ο Ο Ο Ο Ο Ο Ο Ο Start Point To End Point Measurement Ο ⎯ Ο ⎯ Ο ⎯...
Page 132: Opening The [Performance Analysis] Window
5.9.1 Opening the [Performance Analysis] Window Choose [View -> Performance -> Performance Analysis] or click the [PA] toolbar button ( ) to open the [Select Performance Analysis Type] dialog box. Figure 5.58 [Select Performance Analysis Type] Window Select [E6000 Performance Analysis] and then click the [OK] button to open the [Performance Analysis] window.
Page 133: Setting Conditions For Measurement
5.9.2 Setting Conditions for Measurement Conditions for measurement can be displayed and changed in the [Performance Analysis] window. Select a point where a condition is to be set, and then select [Set…] from the popup menu to display the [Performance Analysis Properties] dialog box.
Page 134 (1) 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]: Address to start measurement [End Address]: Address to end measurement Measures the execution time and the execution count in the range between the start address and end address.
Page 135 (2) 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]: Address to start measurement [End Address]: Address to end measurement [Time Out]:...
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 of the user program (performance break).
Page 137 (3) 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 Address]: Start address [End Address]: End address...
Page 138 (4) 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]: Start address [End Address]: End address [Access Area Range]:...
Page 139 (5) 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]: Start address [End Address]: End address [Call Range]:...
Page 140: Selecting The Address Detection Mode And Resolution
5.9.3 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 mode in use. The resolution can also be selected here. To select an address detection mode and resolution, click the [Settings…] button on the [Performance Analysis Properties] dialog box.
Page 141: Section 6 Tutorial
Section 6 Tutorial 6.1 Introduction The following describes the main functions of the emulator by using a tutorial program. The tutorial program is based on the C++ program that sorts ten random data items in ascending or descending order. The tutorial program performs the following actions: •...
Page 142: Running The High-Performance Embedded Workshop
6.2 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 section 8.2.4, Environment for Execution of the Tutorial Program.
Page 143: Downloading The Tutorial Program
6.3 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 Tutorial Program...
Page 144: Displaying The Source Program
6.3.2 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 and size that are legible if necessary. For details, refer to the High-performance Embedded Workshop user’s manual.
Page 145: Setting A Software Breakpoint
6.4 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 the sort function call: •...
Page 146: Setting Registers
6.5 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. Figure 6.5 [Register] Window • To change the value of the program counter (PC), double-click the value area in the [Register] window with the mouse.
Page 147: Executing The Program
The directory mentioned above cannot be specified depending on the version of the software. In such cases, specify the following directory instead. High-performance Embedded Workshop installation destination directory \Tools\Renesas\DebugComp\Platform\E6000\2646\Source The file path differs depending on the product. If necessary, replace \2646 with another name.
Page 148 Figure 6.8 [Editor] Window (Break Status)
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 the Status of Cause of last break. Figure 6.9 [Status] Window Note: The items that can be displayed in this window differ depending on the product.
Page 150: Reviewing Breakpoints
6.7 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. Figure 6.10 [Event] Window The popup menu, opened by clicking the [Event] window with the right-hand mouse button, allows the user to set or change breakpoints, define new breakpoints, and delete, enable, or disable breakpoints.
Page 151: Referring To Symbols
6.8 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 the addresses of symbols in modules. Figure 6.11 [Label] Window...
Page 152: Viewing Memory
6.9 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: • Select [Memory …] from the [CPU] submenu of the [View] menu or click the [View Memory] toolbar button ( ) to open the [Display Address] dialog box.
Page 153: Watching Variables
6.10 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: •...
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. Figure 6.16 [Add Watch] Dialog Box •...
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)
Page 156: Displaying Local Variables
6.11 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: a, j, i, and p_sam. • Select [Locals] from the [Symbol] submenu of the [View] menu. The [Locals] window is displayed. The [Locals] window shows the local variables in the function currently pointed to by the program counter, along with their values.
Page 157: Stepping Through A Program
6.12 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 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 158 Figure 6.21 [Editor] Window (Step In) • The highlighted line moves to the first statement of the sort function in the [Editor] window.
Page 159: Executing The [Step Out] Command
6.12.2 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 Out] from the [Debug] menu, or click the [Step Out] button in the toolbar.
Page 160: Executing The [Step Over] Command
6.12.3 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 step, select [Step Over] from the [Debug] menu, or click the [Step Over] button in the toolbar.
Page 161: Forced Breaking Of Program Executions
6.13 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] menu or the [Go] button on the toolbar.
Page 162: Break Function
6.15 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 are described below. 6.15.1 Software Break Function The emulator can set up to 256 software breakpoints.
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 this address in the [Address Lo] edit box of the [Address] group box. In this example, enter H’00001082.
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 be displayed, refer to section 8, Software Specifications Specific to This Product, or the online help.
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 Stop (Software Break)
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 to section 8, Software Specifications Specific to This Product, or the online help.
Page 167: Breaking Execution At Event Points
6.15.2 Breaking Execution at Event Points Setting up of an 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 use of event points. •...
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 the product. For the items that can be displayed, refer to section 8, Software Specifications Specific to This Product, or the online help.
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...
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 satisfied five times. Note: The items that can be displayed in this window differ depending on the product.
Page 171: Trace Functions
6.16 Trace Functions The trace functions of the emulator use the realtime trace buffer, which is able to store the information on up to 32,768 bus cycles. The content of this buffer, which is constantly updated during execution, is displayed in the [Trace] window.
Page 172: Displaying A Trace (When Time Stamping Is Not Available)
6.16.1 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 on the [Trace] window displays a popup menu. Select [Acquisition…] from this menu to display the [Trace Acquisition] dialog box.
Page 173 (2) 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 the [Editor] window to refer to the address on the line that has ‘a[i]=j;’ within the tutorial function and enter this address in the [Address Lo] edit box of the [Address] group box on the [General] page of the [Breakpoint/Event Properties] dialog box.
Page 174 (4) 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 (5) 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 Added)
Page 176 (6) 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])
Page 177 (7) 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 that the break occurs after the instruction at the address on the line that has ‘a[i]=j;’ within the tutorial function (H’0000105C in this example) has been executed five times (for details on this, refer to section 6.15.2, Breaking Execution at Event Points).
Page 178: Displaying A Trace (When Time Stamping Is Available)
(10) 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 points that have been set. Click the right-hand mouse button on the [Trace] window to display a further popup menu.
Page 179 (5) 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) To enable time stamping, select 125ns from the [Clock] combo box of the [Time Stamp] group box. Figure 6.51 [Trace Acquisition] Dialog Box (Time Stamping is Available)
Page 180 (7) 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 the [Range] radio button in the [Conditions] group box. This will display the [Range Event] combo box and the [Edit…] button (see figure 6.46, [Trace Acquisition] dialog box).
Page 181 (11) 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 the header (vertical) bars below the title bar to adjust the width of the column.
Page 182: Statistics
6.16.3 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 the tutorial function (H’00001082 in this example) (for details on this, refer to section 6.15.1, Software Break Function).
Page 183 (4) 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 (New Condition)
Page 184 (5) 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] list box, so that it now shows “R/W=WR & Area=RAM”. This completes setting of the condition. Figure 6.56 [Statistic] Dialog Box (Condition Added)
Page 185 (6) 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 [Close] button to close the [Statistic] dialog box. (8) Remove the event points that have been set and clear the trace information.
Page 186: Function Calls
6.16.4 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 this example) (for details on this, refer to section 6.15.1, Software Break Function).
Page 187: Stack Trace Function
6.17 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 module is supported in H8S, H8/300 C/C++ compiler V4.0 or later. 2.
Page 188 Figure 6.61 [Stack Trace] Window 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 in the sort function again.
Page 189: Performance Measurement Function
6.18 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 Measurement •...
Page 190 (3) 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 box. Figure 6.64 [Performance Analysis Properties] Dialog Box (4) Select Time Of Specified Range Measurement from the [Measurement Method PA1] combo box.
Page 191 (6) 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. PC is now displayed in the [Address Control Mode] text field of the [Common Setting of Performance(PA1-8)] dialog box.
Page 192: Monitor Function
6.19 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 stored. (1) Select the [CPU] submenu from the [View] menu.
Page 193 (2) 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 address on the line where variable a, which is defined within the tutorial function, is allocated and enter this address in the [Address] edit box.
Page 194: What Next
(3) Click the [OK] button to open the [Monitor] window. Figure 6.71 [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 the [Foreground] and [Background] combo boxes).
Page 195: Section 7 Hardware Specifications Specific To This Product
Section 7 Hardware Specifications Specific to This Product This section describes the hardware specifications on the H8/3664 E6000 emulator. H8/3664 E6000 Emulator Specifications The H8/3664 E6000 emulator supports the system development using the following microcomputers: • H8/3664 group • H8/3664N •...
Page 196: Operating Voltage And Frequency Specifications
7.1.2 Operating Voltage and Frequency Specifications Table 7.1 shows the MCU operating voltage and frequency specifications supported by the E6000 emulator. If the emulator is used in an environment that exceeds the operating voltage range and operating frequency range guaranteed for the MCU operation, normal emulator operation is not guaranteed. Note that the operation with low voltage or high frequency is not supported in some MCUs.
Page 197: User System Interface
7.2 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 • /RES • OSC1 •...
Page 198 PB0 to PB7 (pins used for AN0 to AN7), AVcc and AVss: Figure 7.3 User System Interface Circuit for PB0 to PB7, AVcc and AVss Signals and TEST: When V is connected to GND or the TEST pin is connected to the Vcc level, a warning message to indicate that the pin connections are incorrect will be displayed when the emulator is connected.
Page 199: Differences Between Mcu And Emulator
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 shown in table 7.2. Table 7.2 Initial Value Differences between MCU and Emulator Status...
Page 200: Handling Serial Eeprom Board
Handling Serial EEPROM Board WARNING Always switch OFF the emulator and user system before connecting or disconnecting the serial EEPROM board and make sure that the pin 1 on both sides are correctly aligned. 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 201: Host Pc Interface
Serial EEPROM board Serial EEPROM socket Pin 1 Figure 7.6 Installing Serial EEPROM Board Host PC Interface This emulator (HS3664EPI62H) incorporates a USB interface circuit as the host PC interface. The specifications of this emulator comply with USB 1.1 (full speed) and can also be connected to a USB 2.0 host computer. Connecting the attached USB interface cable to the host computer enables a direct connection between the host computer and the emulator.
Page 203: Section 8 Software Specifications Specific To This Product
Section 8 Software Specifications Specific to This Product This section describes the software specifications of the H8/3664 E6000 emulator. Software Specifications of the H8/3664 E6000 Emulator Information specific to this emulator is given below. 8.1.1 Target Hardware This emulator software conforms to the H8/3664 E6000 (HS3664EPI61H, HS3664EPI62H) emulator. 8.1.2 Selectable Platforms The debugging platforms selectable in this emulator are listed below.
Page 204: [Configuration Properties] Dialog Box ([General] Page)
8.1.3 [Configuration Properties] Dialog Box ([General] Page) Items that can be set in this dialog box are listed below. Figure 8.1 [Configuration Properties] Dialog Box ([General] Page)
Page 205 [General] page [Device] Selects the MCU to be emulated. To use an MCU not included in the list, select [Custom] to specify the functions required for this MCU. See the hardware manual for details. [Clock] Selects the speed of the MCU’s clock. [SubClock] Selects the speed of the MCU’s sub-clock.
Page 206 [General] page (cont) [Break on access error] When this box is checked, a break (the user program stops) occurs if your program accesses an access-prohibited area or writes to a write- protected area. [Enable internal ROM area write] When this box is checked, writing to the internal ROM area is enabled. For the result of writing, see the [Extended Monitor] window.
Page 207 Table 8.2 Environment for the H8/3664 E6000 Emulator CPU 300H Debugging Platform [Device] Option [Clock] Option [SubClock] Option Expansion Hardware Custom The MCU previously selected 32.768 kHz H8/3664 1 MHz None Target H8/3663 10 MHz H8/3662 16 MHz H8/3661 Target H8/3660 H8/3664F H8/3664N...
Page 208 Table 8.3 Environment for the H8/36037 E6000 Emulator CPU 300H Debugging Platform [Device] Option [Clock] Option [SubClock] Option Expansion Hardware Custom The MCU previously selected 32.768 kHz H8/36037 1 MHz HS36037EIO61H Target H8/36036 10 MHz H8/36035 16 MHz H8/36034 Target H8/36033 H8/36032 H8/36037F...
Page 209: Configuration Properties] Dialog Box ([Custom] Page)
8.1.4 [Configuration Properties] Dialog Box ([Custom] Page) Items that can be set in this dialog box are listed below. Figure 8.2 [Configuration Properties] Dialog Box ([Custom Device] Page)
Page 210 [Custom Device] page [ROM] Specify the internal ROM area size. 8kB: Sets the internal ROM area to be 8 kbytes (H’000000 to H’001FFF). 12kB: Sets the internal ROM area to be 12 kbytes (H’000000 to H’002FFF). 16kB: Sets the internal ROM area to be 16 kbytes (H’000000 to H’003FFF).
Page 211 [Custom Device] page (cont) [Modules] Check this box to validate on-chip peripherals. Enable TimerB1: Enables timer B1. Enable TimerB2: Enables timer B2. Enable TimerB3: Enables timer B3. Enable TimerV: Enables timer V. Enable TimerW: Enables timer W. Enable TimerX: Enables timer X. Enable TimerZ0: Enables timer Z0.
Page 212: Memory Mapping Function
8.1.5 Memory Mapping Function The memory map cannot be changed with this emulator. 8.1.6 [Status] Window Selecting [View -> CPU -> Status] or clicking the [Status Display] toolbar button displays the [Status] window. The [Status] window has three sheets. This emulator displays the following items. (1) [Memory] Sheet Selecting the [Memory] tab on the [Status] window displays this sheet.
Page 213 (2) [Platform] Sheet Selecting the [Platform] tab on the [Status] window displays this sheet. Table 8.7 [Platform] Sheet Items [Item] Column [Status] Column Connected To: Displays emulator name (driver used). Displays the target MCU name. Clock source Displays the selected clock. Subclock source Displays the selected sub-clock.
Page 214: Extended Monitor Function
8.1.7 Extended Monitor Function Selecting [View -> CPU -> Extended Monitor] or clicking the [Extended Monitor] toolbar button displays the [Extended Monitor] window. This emulator displays the following items. Table 8.9 [Extended Monitor] Window Items [Item] Column [Value] Column User NMI Displays the status of the NMI pin.
Page 215: Signals To Indicate Bus States And Areas
8.1.8 Signals to Indicate Bus States and Areas The following tables show examples of signals to indicate the bus states and areas that can be acquired by the emulator. Table 8.10 Bus State Signals Acquired by the Emulator Bus State Trace Display (Status) Description CPU Prefetch...
Page 216: Trace Information
8.1.11 Trace Information Selecting [View -> Code -> Trace] or clicking the [Trace] toolbar button displays the [Trace] window. Trace information that can be acquired by the emulator and trace information items to be displayed are as listed below. [PTR] Cycle number in the trace buffer.
Page 217: Searching For A Trace Record
8.1.12 Searching for a Trace Record While using the emulator, the [Trace Find] dialog box has the following pages: Table 8.12 [Trace Find] Dialog Box Pages Page Description [General] Sets the range for searching. [Address] Sets an address condition. [Data] Sets a data condition.
Page 218: Reading From And Writing To The Eeprom
8.1.14 Reading from and Writing to the EEPROM With this emulator, users can view and write to memory areas in the EEPROM. This section describes how to look at memory areas and how to fill and move a memory block. (1) Viewing a Memory Area in the EEPROM To look at a memory area in the EEPROM, choose [View ->...
Page 219 Figure 8.4 [EEPROM] Window The [EEPROM] window has [ID], [Address], [Value], and data columns. The number of data columns is that selected in the [Column count] combo box. Each of the columns is displayed in hexadecimal. [ID]: Slave address of the EEPROM. [Address]: Address of the first item in the data columns of this row.
Page 220 (3) Modifying the Memory Contents The memory contents can be modified via the [Edit] dialog box. The contents of the EEPROM are changed in byte or page units, depending on the mode selected in the [Write mode] combo box of the [Properties] dialog box.
Page 221 (6) Copying a Memory Area You can copy a memory area using the memory copy function. The following three types are available: • From EEPROM to EEPROM • From EEPROM to normal memory • From normal memory to EEPROM (a) From EEPROM to EEPROM Selecting a memory range and then [Copy…] from the popup menu opens the [Copy] dialog box (figure 8.7).
Page 222 (b) From EEPROM to normal memory Selecting a memory range and then [Copy…] from the popup menu opens the [Copy] dialog box (figure 8.8). Select the [EEPROM -> MEMORY] toggle button in the [Copy Direction] group box. Figure 8.8 [Copy] Dialog Box (EEPROM -> MEMORY) The start slave address and end slave address as the source selected in the [EEPROM] window will be displayed in the [Start ID] and [End ID] combo boxes.
Page 223 (c) From normal memory to EEPROM Selecting a memory range and then [Copy…] from the popup menu opens the [Copy] dialog box (figure 8.9). Select the [MEMORY -> EEPROM] toggle button in the [Copy Direction] group box. Figure 8.9 [Copy] Dialog Box (MEMORY -> EEPROM) Enter the source start address and end address in normal memory in the [Start address] and [End address] fields.
Page 224: Notes On Usage Of The H8/3664 E6000 Emulator
8.2 Notes on Usage of the H8/3664 E6000 Emulator There are the following notes on usage of the emulator. 8.2.1 I/O Register In the E6000 emulator, one evaluation chip emulates several types of MCU. Therefore, there are some differences in I/O registers between an actual MCU and the emulator. Note these differences when accessing the I/O registers.
Page 225 (2) Warnings that Apply to H8/3672 Group Programming (a) The description given in the hardware manual is “Initial value: 1. Reserved. These bits are always read as 1”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”.
Page 226 Table 8.20 Differences between the Evaluation Chip and the H8/3664, H8/3672 Group Products Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 H'FFE0 PMR1 IRQ3 IRQ2 IRQ1 IRQ0 TXD2 TMOW H'FFE1 PMR5 POF57 POF56...
Page 227 Warnings that Apply to H8/3687, H8/36077, H8/36079 Group Programming (a) The description given in the hardware manual is “Initial value: 0. Reserved. These bits are always read as 1, and cannot be modified”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”.
Page 228 Table 8.24 Differences between the Evaluation Chip and the H8/3687 Registers Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 H'F72C RTCCR2 12/24 H'F730 H'F731 H'F732 H’FFDE PDRC PDRC7 PDRC6 PDRC5 PDRC4 PDRC3 PDRC2...
Page 229 (4) Warnings that Apply to H8/3694 Group Programming (a) The description given in the hardware manual is “Initial value: 1. Reserved. These bits are always read as 1, and cannot be modified”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”.
Page 230 Table 8.29 Differences between the Evaluation Chip and the H8/3694 Registers Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ H'F730 ⎯ ⎯...
Page 231 (5) Warnings that Apply to H8/36014, H8/36024 Group Programming (a) The description given in the hardware manual is “Initial value: 0. Reserved. These bits are always read as 0”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”.
Page 232 (f) While emulating the H8/36024 group, note that the register specifications at address H’F608 in the actual device and expansion I/O board (HS36024EIO61H) are different. Table 8.32 lists the specifications and note on them. Table 8.33 Register Specifications and Note Item Register Specifications Note...
Page 233 Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 ⎯ ⎯ ⎯ H'F730 LVDCR LVDE LVDSEL LVDRE LVDDE LVDUE ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ H'F731 LVDSR LVDDF LVDUF ⎯ ⎯ ⎯...
Page 234 (e) While emulating the H8/36037, H8/36057 group, set PCR9 to ‘0’ if you want to use TinyHCAN or SSU. Table 8.38 Differences between the Evaluation Chip and the H8/36037, H8/36057 Registers Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1...
Page 235 (7) Warnings that Apply to H8/36049 Group Programming (a) The description given in the hardware manual is “Initial value: 0. Reserved. These bits are always read as 0”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”.
Page 236 (f) While emulating the H8/36049 group, note that the register specifications at address H’F608 in the actual device and expansion I/O board (HS36024EIO61H) are different. Table 8.41 lists the specifications and note on them. Table 8.42 Register Specifications and Note Item Register Specifications Note...
Page 237 Table 8.43 Differences between the Evaluation Chip and the H8/36049 Registers Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ H'F730 ⎯ ⎯...
Page 238 (b) The description given in the hardware manual is “Reserved”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”. Table 8.45 Differences between the H8/36109 Group Products (2) Target Address Register Name Bits ⎯...
Page 239 Table 8.47 Differences between the Evaluation Chip and the H8/36109 Registers Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ H'F730 ⎯ ⎯...
Page 240 (9) Warnings that Apply to H8/36902, H8/36912 Group Programming (a) The description given in the hardware manual is “Initial value: 0. Reserved. These bits are always read as 0”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”.
Page 241 Table 8.51 Differences between the Evaluation Chip and the H8/36902, H8/36912 Registers Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ H'F730 ⎯...
Page 242 Table 8.51 Differences between the Evaluation Chip and the H8/36902, H8/36912 Registers(cont) Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 ⎯ H'F730 LVDCR LVDE BGRE VDDII LVDSEL LVDRE LVDDE LVDUE ⎯...
Page 243 (10) Warnings that Apply to H8/36064 Group Programming (a) The description given in the hardware manual is “Initial value: 0. Reserved. These bits are always read as 0”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”.
Page 244 Table 8.56 Differences between the Evaluation Chip and the H8/36064 Registers Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ H'F730 ⎯ ⎯...
Page 245 (11) Warnings that Apply to H8/36094 Group Programming (a) The description given in the hardware manual is “Initial value: 1. Reserved. These bits are always read as 1, and cannot be modified”. However, the description in the emulator manual is “Always specify 0. These bits are always read as the specified values”.
Page 246 (e) Although the hardware manual says that an initial value is 1, the compact emulator’s initial value is “0”. These bits must always be set to 1, when counting up the watchdog timer. Table 8.61 Differences between the H8/36094 Group Products (5) Target Address Register Name Bits...
Page 247 Table 8.62 Differences between the Evaluation Chip and the H8/36094 Registers Address Register Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ ⎯ H'F730 ⎯ ⎯...
Page 248: Notes On Mode Transitions
(2) To execute the tutorial program, specify “Tutorial.hws” stored in the following directory: OS installation drive \Workspace\Tutorial\E6000\3664 The directory mentioned above cannot be specified depending on the version of the software. In such cases, specify the following directory instead. High-performance Embedded Workshop installation destination directory \Tools\Renesas\DebugComp\Platform\E6000\3664\Tutorial...
Page 249: Note On Emulation Of The H8/36912 Group And H8/36902 Group
8.2.5 Note on Emulation of the H8/36912 Group and H8/36902 Group The ROM/RAM capacity for the H8/36911 of the H8/36912 group and the H8/36901 and H8/36900 of the H8/36902 group is different in the MCU and the emulator. When you create a user program, be careful of the ROM/RAM usage because the size of the ROM/RAM in the emulator is larger than that of the MCU.
Page 251: Appendix A I/O File Format
Appendix A I/O File Format High-performance Embedded Workshop formats the [IO] window based on information it finds in an I/O Register definition file. When you select a debugging platform, High-performance Embedded Workshop will look for a “<device>.IO” file corresponding to the selected device and load it if it exists. This file is a formatted text file that describes the I/O modules and the address and size of their registers.
Page 252 Example: Comment ; H8S/2655 Series I/O Register Definitions File [Modules] BaseAddress=0 Module Module1=Power_Down_Mode_Registers definition Module2=DMA_Channel_Common Module3=DMA_Channel_0 Module42=Bus_Controller Module43=System_Control Module44=Interrupt_Controller [DMA_Channel_Common] DMAWER=0xffff00 B A DMATCR=0xffff01 B A Register DMACR0A=0xffff02 B A definition DMACR0B=0xffff03 B A DMACR1A=0xffff04 B A DMACR1B=0xffff05 B A DMABCRH=0xffff06 B A DMABCRL=0Xffff07 B A [DMA_Channel_0]...
Page 253: File Format (Bit Field Supported)
File format (Bit Field Supported) Each module name must be defined in the [Modules] definition section and the numbering of each module must be sequential. Each module corresponds to a register definition section and within the section each entry defines an I/O register.
Page 254 Example: Comment ; H8S/2655 Series I/O Register Definitions File [Modules] FileVersion=2 BaseAddress=0 Module1=Power_Down_Mode_Registers Module2=DMA_Channel_Common Module3=DMA_Channel_0 Module Module42=Bus_Controller Module43=System_Control Module44=Interrupt_Controller [DMA_Channel_Common] reg0=regDMAWER reg1=regDMATCR Module reg2=regDMACR0A definition reg3=regDMACR0B reg4=regDMACR1A reg5=regDMACR1B reg6=regDMABCRH reg7=regDMABCRL dep= regMSTPCRH 7 0 Register name Value Register [regDMAWER] definition id=DMAWER 0xffff00 B A H dmawer_bitfields Register name Address...
Page 255: Appendix B Menus
Appendix B Menus Table B.1 shows GUI menus. Table B.1 GUI Menus Toolbar Menu Option Shortcut Button Remarks View Difference Opens the [Difference] window. Command Line Ctrl + L Opens the [Command Line] window. TCL toolkit Shift + Opens the [Console] window. Ctrl + L Workspace Alt + K...
Page 256 Table B.1 GUI Menus (cont) Toolbar Menu Option Shortcut Button Remarks View Gra- Image… Shift + Opens the [Image] window. (cont) phic Ctrl + G Waveform… Shift + Opens the [Waveform] Ctrl + V window. Per- Performance Shift + Opens the [Performance form- Analysis Ctrl + P...
Page 257 Table B.1 GUI Menus (cont) Toolbar Menu Option Shortcut Button Remarks Debug Step In Executes a block of user (cont) program before breaking. Step Over Executes a block of user program before breaking. If a subroutine call is reached, then the subroutine will not be entered.
Page 258 Table B.1 GUI Menus (cont) Toolbar Menu Option Shortcut Button Remarks Setup Customize… Customize the High-performance Embedded Workshop application. Options… Sets option of the High- performance Embedded Workshop application. Format Views… Configure fonts, colors, keywords and so on, for the window.
Page 259: Appendix C Command Lines
Appendix C Command Lines Table C.1 lists the High-performance Embedded Workshop commands. Table C.1 High-performance Embedded Workshop Commands No. Command Name Abbreviation Function Comment ADD_FILE Adds a file to the current project ANALYSIS Enables or disables performance analysis ANALYSIS_RANGE Sets or displays a performance analysis range ANALYSIS_RANGE_ Deletes a performance analysis range DELETE...
Page 260 Table C.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function EXMONITOR_ EXMSR Sets the time to update the expansion monitor during SETRATE emulation or a break FILE_LOAD Loads an object (program) file FILE_SAVE Saves memory to a file FILE_UNLOAD Unloads a file FILE_VERIFY...
Page 261 Table C.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function STEP Steps program (by instructions or source lines) STEP_MODE Sets the step mode STEP_OUT Steps out of the current function STEP_OVER Steps program, not stepping into functions STEP_RATE Sets or displays rate of stepping SUBMIT Executes a command file...
Page 263: Appendix D Diagnostic Test Procedure
Appendix D Diagnostic Test Procedure This section describes the diagnostic test procedure using the E6000 test program. System Set-Up for Test Program Execution To execute the test program, use the following hardware; do not connect the user system interface cable, user system, or expansion I/O board.
Page 264 Diagnostic Test Procedure Using Test Program The CD-R includes a test program for this emulator (HS3664EPI62H) and that for the previous version of the emulator (HS3664EPI61H) that does not incorporate the USB interface. Usually refer to the descriptions for the HS3664EPI62H below.
Page 265 (approximately 2 to 10 minutes). Message Description Test program start E6000 H8/3664 Emulator Tests Vx.x message. Vx.x shows the Copyright (c) 2001, 2003 Renesas Technology Corp. version number. Shows that the PC Loading driver .......OK interface board is Initializing driver ....OK correctly installed in Searching for interface card ..OK...
Page 266 Shows the results of 03) Test Firmware RAM : decoding test for the A) Decode Test page [H'700 - H'71f] ..OK firmware RAM in the E6000 (normal completion). Shows the results of B) Marching Test page [H'700 - H'71f] ..OK marching test for the firmware RAM in the E6000 (normal completion).
Page 267 Shows the check results 11) Test Internal ROM Write Protect : for the internal ROM A) Write Protect .......OK write-protection B) Write Not Protect ....OK controlling circuits in the E6000 (normal completion). Shows the check results 12) Test Hardware Break : for the hardware break A) Break Point Initialized .....OK control circuits in the...
Page 268 Shows the check results 18) Test Parallel Access : for the parallel access A) Internal ROM Parallel Read Access(WORD) ...OK controlling circuits in B) Internal ROM Parallel Write Access(WORD) ..OK the E6000 (normal C) Internal ROM Parallel Write Access(High Byte) ..OK completion).
Page 269 H8/3664 E6000 Emulator Publication Date: Rev.6.00, February 5, 2007 Published by: Sales Strategic Planning Div. Renesas Technology Corp. Edited by: Customer Support Department Global Strategic Communication Div. Renesas Solutions Corp. © 2007. Renesas Technology Corp., All rights reserved. Printed in Japan.
Page 270 Nippon Bldg., 2-6-2, Ohte-machi, Chiyoda-ku, Tokyo 100-0004, Japan http://www.renesas.com RENESAS SALES OFFICES Refer to "http://www.renesas.com/en/network" for the latest and detailed information. Renesas Technology America, Inc. 450 Holger Way, San Jose, CA 95134-1368, U.S.A Tel: <1> (408) 382-7500, Fax: <1> (408) 382-7501 Renesas Technology Europe Limited Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K.
Page 272 H8/3664 E6000 Emulator User’s Manual 1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa 211-8668 Japan REJ10J1133-0600...

This manual is also suitable for:

H8/300h tiny series H8/3664 e6000

Renesas H8 Series User Manual

Quick Links

Need help?

Questions and answers

Related Manuals for Renesas H8 Series

Summary of Contents for Renesas H8 Series

This manual is also suitable for:

Table of Contents