Renesas SH7641 Informations techniques

To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology C

VI Warnings on Emulator Usage Be sure to read and understand the warnings below before using this emulator. Note that these are the main warnings, no

78 The following is an example of the display in the SH7751 E10A emulator. Figure 3.57 [Trace] Window in the SH7751 E10A Emulator

79 3.19.3 VP_MAP Translation The MCU, which has an MMU, translates internal addresses (virtual addresses) to actual memory addresses (physical addres

80Virtual address Physical addressH'10000H'10FFFH'11000H'11FFFH'12000H'12FFFH'12000H'12FFFH'4000000H&apos

81 Table 3.5 Address Translation Tables VP_MAP MMU Radio Button* Enabled/Disabled Within/ Outside the range Enabled/Disabled Within/Outsi

82 3.20 Stack Trace Function The emulator uses the stack’s information to display the name of the calling function for a function at which the progr

83 Figure 3.60 [Stack Trace] Window Figure 3.60 shows that the position of the program counter is currently at the selected line of the sort() fun

84 3.21 Profiling Function The profile function can measure performance for each function. Notes: 1. Realtime operation is not possible while this

85 • The profile function is now enabled. Place the mouse cursor on an entry in the [Profile-List] window, click the right-hand mouse button, then s

86 • Data to be measured for the selected function is now set. Select [Select Data] from the pop-up menu by clicking with the right mouse button.

87 Figure 3.64 [Source] Window (Software Break Setting) • Set the same program counter and stack pointer values (PC = H’0c00006c and R15 = H’0c00

i Preface Thank you for purchasing the E10A emulator. CAUTION READ section 2, Preparation before Use, of this User’s Manual before using the e

88 • Figures 3.66 and 3.67 show the [Profile-Tree] and [Profile-Chart] windows, respectively. Figure 3.66 [Profile-Tree] Window Figure 3.67 [P

89 3.22 Download Function to the Flash Memory Area The E10A emulator enables downloading to the flash memory area. This function requires a progra

90  Flash memory download method It is required to perform necessary settings on the [Loading flash memory] page in the [Configuration] window for

91 Table 3.7 shows the options for the [Loading flash memory] page. Table 3.7 [Loading flash memory] Page Options Option Description [Loading flash

92  Examples of downloading to the flash memory The following shows examples of downloading to the flash memory manufactured by Intel Corporation (

93 Table 3.9 Sample Program Specifications Item Contents RAM area to be used H'0C001000 to H'0C0015BF Write module start address H&apos

94 Notes: 1. When the data has already been written in the flash memory, be sure to select [Enable] for [Erasing flash memory]. If [Disable] is se

95 3.23 What Next? This tutorial has described the major features of the emulator and the use of the HDI. Sophisticated debugging can be carried out

96

97 Section 4 Descriptions of Windows 4.1 HDI Windows HDI window menu bars and the corresponding pull-down menus are listed in table 4.1. Where a

ii Related Manuals: • SuperH RISC Engine C/C++ Compiler, Assembler, Optimizing Linkage Editor User's Manual • Hitachi Debugging Interface Use

98 Table 4.1 HDI Window Menus and Related Manual Entries (cont) Menu Bar Pull-Down Menu Hitachi Debugging Interface User's Manual T

99 Table 4.1 HDI Window Menus and Related Manual Entries (cont) Menu Bar Pull-Down Menu Hitachi Debugging Interface User's Manual

100 4.2 Descriptions of Each Window This section describes each window. Figures in this section are used as examples. Each E10A emulator type ha

101 Description: The [Configuration] dialog box consists of the [General] page listed in table 4.2. Table 4.2 [Configuration] Dialog Box Page Pag

102 (1) [General] Page ([Configuration] Dialog Box) Function: This page sets the emulator operation conditions, displays the device name, sets the

103 Description: Table 4.3 [General] Page Options Option Description [Mode] combo box Displays the device name. [Emulation mode] combo box Sele

104 When a driver is to be changed with the [Change..] button, the following message is displayed. Figure 4.3 Warning Message Box When the [Ye

105 (2) [E10A Driver Details] Dialog Box Function Function: When the [Change] button in the [Driver] group box is clicked on the [General] page in

106 (3) [Loading flash memory] Page ([Configuration] Dialog Box) Function: Downloading to the flash memory is set on the [Loading flash memory] pag

107 Description: Table 4.5 [Loading flash memory] Page Options Option Description [Loading flash memory] radio button Sets Enable for flash memor

iii Contents Section 1 Overview...1 1.1 Warnings...

108 4.2.2 [Breakpoints] Window Function: This window lists all break conditions that have been set. Window: Figure 4.6 [Breakpoints] Window

109 Description: The [Breakpoints] window displays breakpoint setting information. The items listed in the following tables are displayed. Table 4

110 The pop-up menu, which is opened by clicking the right mouse button, can be used to set, change, and clear breakpoints, and to enable or disabl

111 4.2.3 [Break] Dialog Box Function: This dialog box displays the break condition settings. Window: Figure 4.7 [Break] Dialog Box

112 Description: The [Break] dialog box consists of the pages listed in table 4.8. Table 4.8 [Break] Dialog Box Pages Page Name Description [Poi

113 (1) [Point] Page ([Break] Dialog Box) Function: This page displays software breakpoint settings. In this page, software breakpoints can be set

114 Description: Table 4.9 [Point] Page Options Option Description [Break point] list box Lists the software breakpoints currently being set. Th

115 (2) [Condition] Page ([Break] Dialog Box) Function: This page displays the Break Condition settings. These conditions can also be set or clear

116 Description: Table 4.10 [Condition] Page Options Option Description [Break Condition] list box Displays the Break Condition settings. The d

117 4.2.4 [Break Point] Dialog Box Function: This dialog box sets software breakpoints. Window: Figure 4.10 [Break Point] Dialog Box Note: The

iv 3.14.3 Executing [Step Over] Command...50 3.15 Forced Breaking of Program E

118 Description: The [Break Point] dialog box consists only of the [Address] page. This dialog box sets address conditions and address areas. The

119 4.2.5 [Break Condition] Dialog Box Function: This dialog box sets hardware break conditions. Window: Figure 4.11 [Break Condition] Dialog B

120 Description: The [Break Condition] dialog box consists of multiple pages. A condition to halt the program can be set in each page. Contents to

121 4.2.6 [Break Condition] Dialog Box Pages Function: The [Break Condition] dialog box pages allow a number of hardware break conditions to be se

122 Table 4.13 shows all the [Break Condition] dialog box pages. Table 4.13 [Break Condition] Dialog Box Pages Page Name Function [Address] Set

123 (1) [Address] Page ([Break Condition] Dialog Box) Function: This page sets the address bus conditions. Window: Figure 4.12 [Address] Page ([

124 Description: Table 4.14 [Address] Page Options Option Description [Don’t Care] check box Does not set address conditions. [Address] radio bu

125 (2) [Data] Page ([Break Condition] Dialog Box) Function: This page sets the data bus conditions. Window: Figure 4.13 [Data] Page ([Break Con

126 Description: Table 4.16 [Data] Page Options Option Description [Don’t Care] check box Does not set data conditions. [Value] edit box Sets t

127 (3) [ASID] Page ([Break Condition] Dialog Box) Function: This page sets the ASID conditions. Window: Figure 4.14 [ASID] Page ([Break Conditi

v 5.2.8 BREAKPOINT: BP ...158 5.2.9 BREAKPOINT_CLEAR: BC...

128 (4) [Bus State] Page ([Break Condition] Dialog Box) Function: This page sets bus state conditions and read/write cycle conditions. Window: Fig

129 Description: Table 4.18 [Bus State] Page Options Group Box Option Description [Bus State] group box [All] radio button Sets the bus state

130 (5) [Count] Page ([Break Condition] Dialog Box) Function: This page sets the conditions for Break Condition 1. Window: Figure 4.16 [Count] P

131 (6) [General] Page ([Break Condition] Dialog Box) Function: This page sets the conditions for Break Condition 3. Window: Figure 4.17 [General

132 Description: Table 4.20 [General] Page Options Group Box Option Description [LDTLB] group box [Don’t Care] radio button Does not set break

133 4.2.7 [Trace] Window Function: This window displays the trace buffer contents. Window: Figure 4.18 [Trace] Window Note: The types of inform

134 Description: This window displays the trace buffer contents. The items listed in table 4.21 are displayed. Table 4.21 [Trace] Window Display

135 4.2.8 [Trace Acquisition] Dialog Box Function: This dialog box sets trace acquisition conditions. When the [Acquisition] menu is selected fro

136 (1) [Trace Mode] Page ([Trace Acquisition] Dialog Box) Function: This page sets the conditions for trace mode. Window: Figure 4.19 [Trace mo

137 Description: Table 4.23 [Trace mode] Page Options Option Description [AUD trace] radio button Uses AUD trace functions. By default, this bo

vi Figures Figure 1.1 System Configuration with the Emulator (PCMCIA Card Emulator Used)...1 Figure 1.2 System Configuration with the E

138 4.2.9 [System Status] Window Function: This window lists information, such as conditions that have been set to the emulator and execution resu

139 The items listed in the following table are displayed in the [System Status] window. Table 4.24 [System Status] Window Display Items Page Ite

140

141 Section 5 Command-line Functions 5.1 Table and Symbol Description This section describes the format used in section 5.2, Command Descriptions

142 These are actual input examples. For commands whose execution results in a specific display output, an example of the display is given. 5.1.

143 5.2 Command Descriptions The command list of the E10A emulator is shown below. Table 5.1 E10A HDI Commands No. Command Abb. Function 1 A

144 Table 5.1 E10A HDI Commands (cont) No. Command Abb. Function 16 REFRESH RF Updates the HDI memory information to the latest contents.

145 5.2.1 AUD_CLOCK:AUCL Description: Sets or displays the AUD clock (AUDCK) values that have been set. Format: aucl [<option>] <option&g

146 Examples: To set AUD clock (AUDCK) to 15 MHz: >AUD_CLOCK 2 (RET) AUD CLOCK = 15MHz The AUD clock (AUDCK) is displayed: >AUD_CL

147 5.2.2 AUD_MODE:AUM Description: Sets or displays AUD trace acquisition conditions. Format: aum [<option1>] [<option2>] <option1

vii Figure 3.21 [Add Watch] Dialog Box...44 Figure 3.22 [Wat

148 Examples: To select realtime trace mode and set continue option: >aum mode R full c (RET) To display settings: >aum (RET) mode

149 5.2.3 AUD_TRACE:AUT Description: Displays the trace information. Format: aut [<option1>] [<option2>] <option1> = start<st

150 Related Item: [Trace] dialog box

151 5.2.4 BREAKCONDITION_CLEAR: BCC Description: Clears hardware breakpoints that have been set. Format: bcc [<channel>] <channel> = c

152 5.2.5 BREAKCONDITION_DISPLAY: BCD Description: Displays hardware breakpoints that have been set. The display contents include a hardware break

153 5.2.6 BREAKCONDITION_ENABLE: BCE Description: Enables or disables hardware breakpoints that have been set. Format: bce [<channel>] <mo

154 5.2.7 BREAKCONDITION_SET: BCS Description: Sets hardware breakpoints. Note: The function will differ according to the devices used. For funct

155 Table 5.8 BREAKCONDITION_SET Command Parameters Parameter Type Description <channel_number> Numerical value Hardware break conditio

156 Table 5.8 BREAKCONDITION_SET Command Parameters (cont) Parameter Type Description <datawidth> Keyword Data bus access conditions Se

157 Examples: To set the following conditions for channel 1 hardware breakpoint: <addropt> item: An address bus value of H'1000000,

viii Figure 3.64 [Source] Window (Software Break Setting)...87 Figure 3.65 [Profile-List]

158 5.2.8 BREAKPOINT: BP Description: Sets software breakpoints. Note: The function will differ according to the devices used. Format: bp <addr

159 Examples: To set a software breakpoint at physical address H'10002C8: >bp H'10002C8 space physical (RET) To set a software breakp

160 5.2.9 BREAKPOINT_CLEAR: BC Description: Clears software breakpoints that have been set. Format: bc [<address> [<address_space> [<

161 Examples: To clear all breakpoints: >bc (RET) To clear all software breakpoints whose address value is H'1000000: >bc H'10000

162 5.2.10 BREAKPOINT_DISPLAY: BD Description: Displays software breakpoints that have been set. Format: bd Table 5.11 BREAKPOINT_DISPLAY Comman

163 5.2.11 BREAKPOINT_ENABLE: BE Description: Enables or disables software breakpoints that have been set. Format: be <address> <address_

164 Related Items: BC, BD, BP, VC, VD, VE, and VS commands [Breakpoints] window [Break] dialog box

165 5.2.12 DEVICE_TYPE: DE Description: Displays the currently selected device. Format: de Table 5.13 DEVICE_TYPE Command Parameter Parameter T

166 5.2.13 GO_OPTION: GP Description: Displays or sets the emulation mode. Format: Displays emulation mode. gp Sets emulation mode. gp <eml_o

167 Examples: To display the currently set emulation mode for user program execution: >gp (RET) Emulator execution mode = Sequential break C

ix Figure 6.10 [Trace mode] Page...203 Figure 6.11

168 5.2.14 JTAG_CLOCK: JCK Description: Displays or sets the JTAG clock (TCK) frequency. Format: Displays the JTAG clock (TCK) frequency. jck Se

169 JTAG Clock 15MHz (when PCI used): To set the JTAG clock (TCK) frequency: >jck 16 (RET) JTAG Clock 16.5MHz To display the JTAG cloc

170 5.2.15 MEMORYAREA_SET: MAS Description: Displays and sets memory area at command input, such as load, verify, save, memory display, or memory c

171 Examples: To display a memory area for command input, such as load, verify, save, memory display, and memory change: >mas (RET) memoryar

172 5.2.16 REFRESH: RF Description: Updates the HDI memory information. Format: rf Table 5.17 REFRESH Command Parameter Parameter Type Descrip

173 5.2.17 RESTART: RST Description: Restarts the emulator. The settings of breakpoints or trace acquisition conditions are not reset here. Format

174 5.2.18 STATUS: STS Description: Displays status information of the emulator. Format: sts Table 5.19 STATUS Command Parameter Parameter Ty

175 5.2.19 STEP_INTERRUPT: SI Description: Sets or displays the enable or disable status of interrupts during step execution. If enabled, interrup

176 5.2.20 TRACE_DISPLAY: TD Description: Displays the acquired trace information. The information to be acquired is the branch source and branch

177 Example: To display trace information according to information acquired during user program execution: >td (RET) IP TYPE ADDR MNEMONIC

Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to chang

x Tables Table 1.1 Environmental Conditions...4 Table 1.2 O

178 5.2.21 UBC_MODE:UM Description: Sets or displays the current UBC state. Format: um [<ubc_mode>] Table 5.22 UBC_MODE Command Parameter

179 5.2.22 VPMAP_CLEAR: VC Description: Clears the address translation (VP_MAP) table that is set in the emulator. Format: vc [<address>] T

180 5.2.23 VPMAP_DISPLAY: VD Description: Displays the address translation (VP_MAP) table set in the emulator. Format: vd Table 5.24 VPMAP_DISPL

181 5.2.24 VPMAP_ENABLE: VE Description: Enables or disables the setting of the address translation (VP_MAP) table in the emulator. Format: ve <

182 5.2.25 VPMAP_SET: VS Description: Sets the address translation (VP_MAP) table in the emulator. Format: vs <lsaddress> <leaddress>

183 Section 6 SH7641 E10A Emulator Specifications 6.1 Components of the Emulator The SH7641 E10A emulator supports the SH7641. Table 6.1 lists t

184 Table 6.1 Components of the Emulator (HS7641KCM01H, HS7641KCM02H, HS7641KCI01H, or HS7641KCI02H) Classi-fication Component Appearance Quan-

185 For EMI countermeasure, use the ferrite core by connecting the user interface cable. When the user interface cable is connected with the emul

186 6.2 Pin Arrangement of the H-UDI Port Connector Figure 6.2 shows the pin arrangement of the H-UDI port connector (14 pins). CAUTION Note t

187 Notes: 1. Handling of the TCK, TMS, TDI, /TRST, /ASEBRKAK, and /ASEMD0 pins depends on the use conditions of the H-UDI as follows: (a) When t

xi Table 5.6 BREAKCONDITION_DISPLAY Command Parameter ...152 Table 5.7 BREAKCONDITION_ENABLE Command Param

188 Figure 6.3 shows the pin arrangement of the H-UDI port connector (36 pins). H-UDI port connector(Pin 1 mark)1. Input to or output from the use

189 Notes: 1. Handling of the TCK, TMS, TDI, /TRST, /ASEBRKAK, and /ASEMD0 pins depends on the use conditions of the H-UDI as follows: (a) When

190 6.3 User System Interface Circuit The emulator is connected to the user system via the user interface cable. Figure 6.4 shows the user system

191 The user system interface circuits of the emulator (HS7641KCM02H) are shown. Figures 6.5 and 6.6 show the circuits of the H-UDI pin and AUD pi

192 AUD logic circuit (EPF6024ATC144-2) To user systemAUDATA[3:0]AUDSYNC3Vcc10 kΩCLKOUTCLKINAUDATA[3:0]3Vcc10 kΩAUDSYNCA Y74LVT1253Vcc10 kΩAUDCKOE

193 Figure 6.7 shows the user system interface circuit of the emulator (HS7641KCI01H). TDITCKTMSTDOJTAG controller (EPF10K20RC208-3)To user systemY

194 The user system interface circuits of the emulator (HS7641KCI02H) are shown. Figures 6.8 and 6.9 show the circuits of the H-UDI pin and AUD pi

195 AUDATA_I[3:0]AUDIAUDOAUD logic circuitTo user systemA Y74LVT1253Vcc4.7 kΩAUDATA[3:0]Y A74LVT244AUDATA_O[3:0]A Y74LVT1253Vcc4.7 kΩAUDSYNCY A

196 6.4 Differences between the SH7641 and the Emulator • When the emulator system is initiated, it initializes the general registers and part of

197 Note: The memory must not be accessed or modified in sleep state. • Reset Signals The SH7641 reset signals are only valid during emulation s

xii

198 • Cache Operation during User Program Break When cache is enabled, the emulator accesses the memory by the following methods:  At memory w

199 6.5 Specific Functions for the SH7641 E10A Emulator The SH7641 E10A emulator supports the following useful function: • Performance measuremen

200 6.5.2 Break Condition Functions In addition to BREAKPOINT functions, the emulator has Break Condition functions. In the HDI, three types of c

201 Table 6.6 lists the combinations of conditions that can be set under Break Condition 1, 2, 3. Table 6.6 Dialog Boxes for Setting Break Condit

202 AUD Trace Functions: This function is operational when the AUD pin of the device is connected to the emulator. Table 6.9 shows the AUD trace

203 To set the AUD trace acquisition mode, click the [Trace] window with the right mouse button and select [Acquisition] from the pop-up menu to di

204 (a) Branch Trace Function The branch source and destination addresses and their source lines are displayed. Branch trace can be acquired by sel

205 Figure 6.12 [Window trace] Page Notes: 1. When the [L-bus] or [I-bus] radio button is selected, the following bus cycles will be traced.

206 (c) Software Trace Function Note: This function can be supported with SHC compiler V7.0 and later. When a specific instruction is executed, th

207 Table 6.10 [Trace] Window Display Contents Trace Type TYPE Column ADDR Column DATA Column BRANCH Branch source address No display Branch

1 Section 1 Overview The E10A emulator (hereafter referred to as the emulator) is a software and hardware development support tool for application

208 Internal Trace Function: This function is activated by selecting the [Internal trace] radio button in the [Trace type] group box of the [Trace

209 6. When a BREAKPOINT is set to the slot instruction of a delayed branch instruction, the PC value becomes an illegal value. Accordingly, do n

210 In the [Configuration] dialog box, if [User] is set while the [UBC mode] list box has been set, the STEP-type commands that use Break Condition

211 Figure 6.15 [Performance 1] Dialog Box  Measurement range One of the following ranges can be specified. This depends on the item selected

212 3. When Break condition 1->2 or Break condition 2->1 is selected in [Mode] of the [Performance 1] dialog box, specify one or more item

213  Measurement item Items are measured with [Channel 1 to 4] in the [Performance 1] dialog box. Maximum four conditions can be specified at th

214 Table 6.12 Measurement Item (cont) Selected Name Option URAM access stall US (Devices incorporating the U memory can only be measured.) In

215 2. Displaying the measured result The measured result is displayed in the [Performance Analysis] window or the PERFORMANCE_ANALYSIS command wi

216 2. Functions that cannot be used while the profile function is being used (a) Performance measurement function The profile function is impleme

217 6.5.11 Downloading to the Flash Memory Examples of connecting with and downloading to the flash memory (DA28F640J5-150) manufactured by Intel

2 Figure 1.2 System Configuration with the Emulator (PCI Card Emulator Used) The emulator provides the following features: • Excellent cost-perf

218 Figure 6.17 shows a connection of the flash memory using the sample program. SH7641 DA28F640J5-150A0D15 to D0A22 to A1CS05 VRDWE0A0DQ15 to DQ0

219 6.5.12 Notes on HDI 1. Moving Source File Position after Creating Load Module When the source file is moved after creating the load module, t

220  Variable name specification When a name other than a variable name, such as a symbol name or function name, is specified, no data is display

221  File specification by commands The current directory may be altered by file specifications in commands. Absolute paths are recommended to b

222 14. Load of Motorola S-type Files This HDI does not support Motorola S-type files with only the CR code (H'0D) at the end of each record.

223 • Verify In the [I/O Registers] window, the verify function of the input value is disabled. 18. Note on [Registers] Window Operation During Pr

224  [Breakpoints] window During user program execution, it is impossible to jump from the breakpoint to the source or address line on the [Sourc

225 27. Note on Using the [Run program] Dialog Box When [Run...] is selected from the [Run] menu to specify the stop address, there is the followin

226

SH7641 E10A Emulator User's ManualPublication Date: Rev.1.00, June 26, 2003Published by: Sales Strateg

3 • AUD trace function* The AUD trace function enables realtime trace. Note: The AUD is an abbreviation of the Advanced User Debugger. Support for

1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa 211-8668 JapanSH7641 E10A EmulatorREJ10B0010-0100HUser’s Manual

4 1.2 Environmental Conditions CAUTION Observe the conditions listed in tables 1.1 and 1.2 when using the emulator. Failure to do so will cause

5 Table 1.2 Operating Environments Item Description Host computer Built-in Pentium or higher-performance CPU (200 MHz or higher recommended); IBM

6 1.3 Components Check all the components unpacking. For details on the E10A emulator components, refer to section 6.1, Components of the Emulator.

7 Section 2 Preparation before Use 2.1 Emulator Preparation WARNING READ the reference sections shaded in figure 2.1 before using the emulat

SH7641 E10A EmulatorUser’s ManualUser’s Manual Rev.1.0 2003.06SH7641 E10A HS7641KCM01HERenesas Microcomputer Development Environment System

8 2.2 HDI Installation When the CD-R is inserted in the host computer’s CD-ROM drive, the HDI installation wizard is automatically activated (hol

9 2.2.2 Installing under Windows NT4.0 Operating System (1) When the emulator is a PCI card: 1. Shut the operating system down and turn off

10 2.2.3 Installing under Windows2000 Operating System (1) When the emulator is a PCI card: 1. Log-on with an administrator-level user nam

11 2.3 Connecting the Card Emulator to the Host Computer Insert the card emulator, according to its type, in a PCMCIA TYPE II slot or PCI slot on

12 WARNING When inserting the PCI-card emulator, note the following. Failure to do so will damage the host computer. 1. Turn off the host co

13 User system interface cableH-UDI port connectorUser system GNDconnection User systemGND lineTabPin 1Pin 8 Figure 2.4 Connecting the User Syste

14 SHxxxxH-UDITDI TDOTDITDOTDI TDOH-UDIportJTAGportBoundary scan loopUser systemTDI: Test data inputTDO: Test data outputTAP: Test access portICTAP

15 2.5 System Check When the HDI program is executed, use the procedure below to check that the emulator is operating correctly. 1. Check that t

16 5. Select the setting to be used. Figure 2.7 [Select Session] Dialog Box

17 6. The [E10A Driver Details] dialog box is displayed. With the [Driver] combo box, select the driver to connect the HDI with the emulator. [Int

Cautions Keep safety first in your circuit designs! 1. Renesas Technology Corporation puts the maximum effort into making semiconductor products bett

18 • Click the [Close] button. 7. The HDI window is displayed, and the dialog box is displayed as shown in figure 2.9. Figure 2.9 Dialog Box o

19 Figure 2.11 [JTAG Connector Disconnected] Dialog Box 3. If the emulator is not initiated, the following dialog boxes shown in figures 2.12

20 Figure 2.14 [COMMUNICATION TIMEOUT ERROR] Dialog Box Figure 2.15 [INVALID ASERAM FIRMWARE!] Dialog Box Figure 2.16 [Error JTAG boot] D

21 The [E10A Driver Details] dialog box is displayed when the [OK] button is clicked. Select the correct driver. For details, refer to section 6.

22 2.7 Uninstalling the HDI Follow this procedure to remove the installed HDI from the user’s host computer. 1. Open [Add/Remove Programs Proper

23 2.8 CD-R 2.8.1 Configuration of the CD-R The root directory of the CD-R contains a setup program for HDI installation. The folders contain

24

25 Section 3 Tutorial 3.1 Introduction The following describes the main functions of the HDI by using a tutorial program. The tutorial program is ba

26 Notes: 1. Operation of tutorial.abs is big endian. For little-endian operation, tutorial.abs must be recompiled. After recompilation, the addre

27 3.2 Running the HDI To run the HDI, select the [HDI for E10A SHxxxx] -> [Hitachi Debugging Interface] from the [Start] menu. Figure 3.1 [St

I IMPORTANT INFORMATION READ FIRST • READ this user's manual before using this emulator product. • KEEP the user's manual handy for future

28 3.3 [HDI] Window Figure 3.2 [HDI] Window The key functions of the HDI are described in section 4, Descriptions of Windows. Numbers in figure 3

29 3.4 Setting up the Emulator The clocks which are used for data communications must be set up on the emulator before the program is downloaded. •

30 3.5 Setting the [Configuration] Dialog Box • Select [Configure Platform...] from the [Setup] menu to set a communication clock. The [Configurat

31 3.6 Checking the Operation of the Target Memory for Downloading Check that the destination memory area for downloading is operating correctly. Wh

32 • Placing the mouse cursor on a point in the display of data in the [Memory] window and double clicking allows the values at that point to be cha

33 3.7 Downloading the Tutorial Program 3.7.1 Downloading the Tutorial Program Download the object program to be debugged. • Select [Load Program.

34 3.7.2 Displaying the Source Program The HDI allows the user to debug a program at the source level. • Select [Source...] from the [View] menu.

35 Figure 3.9 [Source] Window (Displaying the Source Program) • If necessary, select the [Font] option from the [Customise] submenu on the [Setup

36 3.8 Setting a Software Breakpoint A breakpoint is a simple debugging function. The [Source] window provides a very simple way of setting a softwa

37 3.9 Setting Registers Set values of the program counter and the stack pointer before executing the program. • Select [Registers] from the [View]

II LIMITED WARRANTY Renesas warrants its emulator products to be manufactured in accordance with published specifications and free from de

38 • To change the value of the program counter (PC), double-click the value area in the [Registers] window with the mouse. The following dialog bo

39 3.10 Executing the Program Execute the program as described in the following: • To execute the program, select [Go] from the [Run] menu, or clic

40 The user can see the cause of the break that occurred last time in the [System Status] window. • Select [Status] from the [View] menu. After the

41 3.11 Reviewing Breakpoints The user can see all the breakpoints set in the program in the [Breakpoints] window. • Select [Breakpoints] from the [

42 3.12 Viewing Memory When the label name is specified, the user can view the memory contents that the label has been registered in the [Memory] win

43 3.13 Watching Variables As the user steps through a program, it is possible to watch that the values of variables used in the user program are cha

44 • Click [Add Watch] button to add a variable to the [Watch] window. Figure 3.20 [Watch] Window (Displaying the Array) The user can also add a

45 The [Watch] window will now also show the int-type variable max. Figure 3.22 [Watch] Window (Displaying the Variable) The user can double-click

46 3.14 Stepping Through a Program The HDI provides a range of step menu commands that allow efficient program debugging. Table 3.2 Step Option Me

47 Figure 3.25 [Source] Window (Step In) • The highlighted line moves to the first statement of the sort function in the [Source] window.

III State Law: Some states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages,

48 3.14.2 Executing [Step Out] Command The [Step Out] steps out of the called function and stops at the next statement of the calling statement in t

49 • To execute two steps, use [Step In] twice. Figure 3.28 [HDI] Window (Step In −>−>−>−> Step In) • The value of max displayed in

50 3.14.3 Executing [Step Over] Command The [Step Over] executes a function call as a single step and stops at the next statement of the main progra

51 Figure 3.31 [HDI] Window (Step Over)

52 3.15 Forced Breaking of Program Executions The HDI can force a break in the execution of a program. • To execute the remaining sections of the m

53 3.16 Displaying Local Variables The user can display local variables in a function using the [Locals] window. For example, we will examine the l

54 3.17 Break Function The emulator has software and hardware break functions. With the HDI, a software breakpoint can be set using the [Breakpoints

55 • Click the [Breakpoints] window with the right mouse button and select [Add] from the pop-up menu. The [Break] dialog box is displayed. The [Po

56 • Click the [Add...] button to display the [Breakpoint] dialog box. • Enter H'0c0000c2 to the [Value] edit box. Figure 3.37 [Break Point

57 The [Break] dialog box is displayed. The address set in the value field of [Breakpoint] and the memory space are displayed. Figure 3.38 [Point

IV SAFETY PAGE READ FIRST • READ this user's manual before using this emulator product. • KEEP the user's manual handy for future reference

58 The software breakpoint that has been set is displayed in the [Breakpoints] window. Figure 3.39 [Breakpoints] Window (Software Breakpoint Setti

59 The [System Status] window displays the following contents. Figure 3.41 Displayed Contents of the [System Status] Window (Software Break) Note:

60 3.18 Hardware Break Function A method is given below in which the address bus condition and the read cycles for the bus status condition are set

61 The [Break] dialog box is displayed. To set hardware break conditions, select [Condition] in the [Break] dialog box to display the [Condition] pa

62 • Clear the [Don't Care] check box in the [Address] page. • Select the [Address] radio button and enter H'0c0000b2 as the value in the

63 • Select [Bus State] to display the [Bus State] page. • Select the [Read] radio button in the [Read/Write] group box. Figure 3.45 [Bus State

64 • Click the [OK] button. • The [Break] dialog box is displayed, and the first point display in the [Break Condition] list box changes from Empty

65 The newly set hardware breakpoint is displayed in the [Breakpoints] window. With this setting, Break Condition 1 is displayed in [Type] in the [B

66 The program runs then stops at the condition specified under Break Condition 1. Figure 3.48 [Source] Window at Execution Stop (Break Condition

67 The [System Status] window displays the following contents. Figure 3.49 Displayed Contents of the [System Status] Window (Break Condition 1) No

V WARNING Observe the precautions listed below. Failure to do so will result in a FIRE HAZARD and will damage the user system and the emul

68 3.18.1 Setting the Sequential Break Condition The emulator has sequential break functions. When the hardware break conditions listed in table 3.

69 Figure 3.50 [Configuration] Dialog Box (Sequential Break Setting) Note: The items that can be set in this window differ according to the produ

70 Set hardware break conditions as follows: Break condition 1: When address H'0c0000c6 is accessed in a read cycle, a break condition is satis

71 The program runs then stops at the condition specified under Break Condition 1. Figure 3.52 [Source] Window at Execution Stop (Sequential Break

72 The [System Status] window displays the following contents. Figure 3.53 Displayed Contents of the [System Status] Window (Sequential Break) Not

73 3.19 Trace Functions The E10A emulator has two branch-instruction trace functions. (1) Internal Trace Function The branch source and branch destin

74 Table 3.4 AUD Trace Functions Type Mode Description Realtime trace When the next branch occurs while the trace information is being output, th

75 3.19.1 Internal Trace Function The branch source and branch destination information for the latest several branch instructions are displayed. T

76 Run the program as shown in the example of section 3.17.1, Software Break Function. The trace results are displayed in the [Trace] window after t

77 3.19.2 AUD Trace Function This function is operational when the AUD pin of the MCU is connected to the emulator. The following is the procedure