Renesas H8S/2276 Manual do Utilizador

Revision Date: Feb. 21, 2006 Renesas Microcomputer Development Environment SystemH8S Family / H8S/2200 Series HS2214EPI62HE-U2 Rev.

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

80 (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: [

81 • Point to Point Acquires trace information in the specified range. Figure 5.34 Range Trace Setting (Point to Point) [Start Address]: Addre

82 • Range Only acquires the trace information that satisfies the specified condition. Figure 5.35 Range Trace Setting (Range) [Range Event]: S

83 • Event Acquires trace information, controlling the start and end of trace acquisition with the specified condition. Figure 5.36 Range Trace S

84 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 t

85 (1) [General] page Set the range for searching. Figure 5.37 [Trace Find] Dialog Box ([General] Page) [Trace search range]: Sets the range for

86 (2) [Address] page Set an address condition. Figure 5.38 [Trace Find] Dialog Box ([Address] Page) [Don't care]: Detects no address when t

87 (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 ch

88 (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 con

89 (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 B

i Introduction The E6000 emulator is an advanced realtime in-circuit emulator, which allows programs to be developed and debugged for the H8S family

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

91 (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 Fin

92 (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] Dial

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

94 5.8.7 Viewing the [Editor] Window The [Editor] window corresponding to the selected trace record can be displayed in the following two ways: • S

95 5.8.12 Extracting Records from the Acquired Information Use the filtering function to extract the records you need from the acquired trace inform

96 (1) [General] page Set the range for filtering. Figure 5.46 [Trace Filter] Dialog Box ([General] Page) [Don't care other pages]: Only sel

97 (2) [Address] page Set address conditions. Figure 5.47 [Trace Filter] Dialog Box ([Address] Page) [Don't care]: Detects no address when t

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

99 (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 c

ii About This Manual This manual contains the following information. Emulator Debugger Part: Preparation before use, E6000 emulator functions, debu

100 (5) [Area] page Select the area being accessed. The selection is not available when a time stamp is acquired. Figure 5.50 [Trace Filter] Dialo

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

102 (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 Fi

103 (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] D

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

105 5.8.13 Calculating the Difference in Time Stamping Select [Timestamp Difference…] from the popup menu to calculate the time difference between t

106 5.8.14 Analyzing Statistical Information Choose [Statistic] from the popup menu to open the [Statistic] dialog box and analyze statistical infor

107 This dialog box allows the user to analyze statistical information concerning the trace information. Set the target of analysis in [Item] and the

108 5.9 Analyzing Performance Use the performance analysis function to measure the rate of execution time. The performance analysis function does not

109 Table 5.8 Mode Settings for Measurement Point Page 1 2 3 4 5 6 7 8 Time Of Specified Range Measurement Ο Ο Ο Ο Ο Ο Ο Ο Start Point To En

iii Contents Emulator Debugger Part Section 1 Overview...

110 5.9.1 Opening the [Performance Analysis] Window Choose [View -> Performance -> Performance Analysis] or click the [PA] toolbar button () t

111 5.9.2 Setting Conditions for Measurement Conditions for measurement can be displayed and changed in the [Performance Analysis] window. Select a

112 (1) Time Of Specified Range Measurement Figure 5.61 Time Of Specified Range Settings [Range Name]: The name of the range to be measured [Rang

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

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

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

116 (4) Access Count Of Specified Range Measurement Figure 5.64 Access Count Of Specified Range Measurement Settings [Range Name]: The name of th

117 (5) Called Count Of Specified Range Measurement Figure 5.65 Called Count Of Specified Range Measurement Settings [Range Name]: The name of th

118 5.9.3 Selecting the Address Detection Mode and Resolution In measurement of hardware performance, there are two types of address detection modes

119 Section 6 Tutorial 6.1 Introduction The following describes the main functions of the emulator by using a tutorial program. The tutorial prog

iv 3.3.3 Probes ... 23 3.4 Stack Trac

120 6.2 Running the High-performance Embedded Workshop Open a workspace by following the procedure listed in section 4.1.3, Selecting an Existing W

121 6.3 Downloading the Tutorial Program 6.3.1 Downloading the Tutorial Program Download the object program to be debugged. • Select [Download m

122 6.3.2 Displaying the Source Program The High-performance Embedded Workshop allows the user to debug a user program at the source level. • Doub

123 6.4 Setting a Software Breakpoint A software breakpoint is a simple debugging function. The [Editor] window provides a very simple way of setti

124 6.5 Setting Registers Set a value of the program counter before executing the program. • Select [Registers] from the [CPU] submenu of the [Vie

125 6.6 Executing the Program Execute the program as described in the following: • To execute the program, select [Go] from the [Debug] menu, or c

126 Figure 6.8 [Editor] Window (Break Status)

127 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] m

128 6.7 Reviewing Breakpoints The user can see all the breakpoints set in the program in the [Event] window. • Select [Eventpoints] from the [Code

129 6.8 Referring to Symbols The [Label] window can be used to display the information on symbols in modules. Select [Label] from the [Symbol] subm

v 5.7.12 Disabling an Event Point...73 5.7.13 Deleting an Event

130 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] w

131 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

132 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 s

133 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 (Displayin

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

135 6.12 Stepping Through a Program The High-performance Embedded Workshop provides a range of step menu commands that allow efficient program debu

136 Figure 6.21 [Editor] Window (Step In) • The highlighted line moves to the first statement of the sort function in the [Editor] window.

137 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

138 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

139 6.13 Forced Breaking of Program Executions The High-performance Embedded Workshop can force a break in the execution of a program. • Cancel al

vi 6.16.2 Displaying a Trace (when Time Stamping is Available) ...156 6.16.3 Statistics...

140 6.15 Break Function The emulator’s break functions are of two types: software breaks and breaks at event points. software breakpoints and even

141 Figure 6.31 [Breakpoint/Event Properties] Dialog Box • Check the [Software Break] radio button in the [Type] group box. • Use the [Editor]

142 The software breakpoint that has been set is displayed in the [Event] window. Figure 6.32 [Event] Window (Software Breakpoint Setting) Note:

143 • Close the [Event] window. • To stop the tutorial program at the breakpoint, select [Reset Go] from the [Debug] menu. The program runs until i

144 The [Status] window displays the following contents: Figure 6.34 Displayed Contents of the [Status] Window (Software Break) Note: The items t

145 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 p

146 Figure 6.36 [General] Page ([Breakpoint/Event Properties] Dialog Box) • Click the [OK] button. The [Event] window is displayed, as shown bel

147 Select [Reset Go] from the [Debug] menu to stop the tutorial program at breakpoints. The program runs then stops at the condition specified under

148 The [Status] window displays the following contents. Figure 6.39 Displayed Contents of the [Status] Window Refer to the [Watch] window for the

149 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

vii Appendix D Diagnostic Test Procedure ... 209 D.1 System Set-Up for Test Program Execu

150 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

151 (2) Register an address as an event condition for trace acquisition. Click the [Add…] button in the [Trace Events] group box on the [General] pag

152 (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 Acq

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

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

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

156 (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 displ

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

158 (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] (se

159 (11) Select [Reset Go] from the [Debug] menu. Processing stops when the break condition is satisfied, and the [Trace] window then displays the f

viii

160 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 setti

161 (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 th

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

163 (6) To start statistical analysis of the specified condition, press the [Result] button. The number of write operations that satisfy the conditi

164 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 occ

165 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

166 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() f

167 6.18 Performance Measurement Function Performance measurement by the emulator is in the following modes: • Time Of Specified Range Measurement

168 (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 m

169 (6) Click the [Settings…] button in the [Common Settings of Performance(PA1-8)] group box to display the [Common Settings of Performance(PA1-8)]

Emulator Debugger Part

170 6.19 Monitor Function The emulator allows monitoring of the content of specified addresses in memory during execution of the user program. In t

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

172 (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 con

173 Section 7 Hardware Specifications Specific to This Product This section describes the hardware specifications on the H8S/2214 E6000 emulator. 7

174 7.1.2 Operating Voltage and Frequency Specifications Table 7.1 shows the MCU operating voltage and frequency specifications supported by the E60

175 7.2 User System Interface All user system interface signals are directly connected to the MCU in the emulator with no buffering except for tho

176 RESET and NMI: The RESET and NMI signals are input to the MCU through the emulator control circuit. The rising/falling time of these signals must

177 7.3 Differences between MCU and Emulator When the emulator is turned on or initialized, or the system is reset, there are some differences in th

178

179 Section 8 Software Specifications Specific to This Product This section describes the software specifications of the H8S/2214 E6000 emulator. 8

180 8.1.3 [Configuration Properties] Dialog Box ([General] Page) Items that can be set in this dialog box are listed below. Figure 8.1 [Configura

181 [General] page [Device] Selects the MCU to be emulated. To use an MCU not included in the list, select [Custom] to specify the functions require

182 [General] page (cont) [Break on access error] When this box is checked, a break (the user program stops) occurs if your program accesses an acce

183 Table 8.2 Environment for the H8S/2214 E6000 Emulator CPU 2000 Debugging Platform [Device] Option [Mode] Option [Clock] Option Expansion Hardw

184 8.1.4 [Configuration Properties] Dialog Box ([Custom] Page) Items that can be set in this dialog box are listed below. Figure 8.2 [Configurat

185 [Custom Device] page [ROM] Specify the internal ROM area size. None: - 32kB: Sets the internal ROM area to be 32 kbytes (H’000000 to H’007FFF).

186 [Custom Device] page (cont) [Modules] Check this box to validate on-chip peripherals. Enable DTC: Uses a part of the internal RAM as DTCRAM. Ena

187 8.1.5 Memory Mapping Function This emulator supports four blocks of user memory. These can be 256 kbytes or 1 Mbyte each, depending on the SIMM

188 (2) [Platform] Sheet Selecting the [Platform] tab on the [Status] window displays this sheet. Table 8.4 [Platform] Sheet Items [Item] Column [

189 8.1.7 Extended Monitor Function Selecting [View -> CPU -> Extended Monitor] or clicking the [Extended Monitor] toolbar button displays the

1 Section 1 Overview 1.1 Features • The breakpoint, memory map, performance, and trace can be set through the dialog box. ⎯ Intuitive user interf

190 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 ac

191 8.1.11 Trace Information Selecting [View -> Code -> Trace] or clicking the [Trace] toolbar button displays the [Trace] window. Trace inform

192 8.1.12 Searching for a Trace Record While using the emulator, the [Trace Find] dialog box has the following pages: Table 8.9 [Trace Find] Dialo

193 [Don't care]: Detects no IRQ input condition when this box is checked. [Setting]: Detects the specified IRQ input condition. [IRQ7] to [IR

194 • [IRQ7-0] page Select the status of IRQ signals. The selection is not available when a time stamp is acquired. Figure 8.4 [Trace Filter] Dia

195 8.2 Notes on Usage of the H8S/2214 E6000 Emulator There are the following notes on usage of the emulator. 8.2.1 Environment for Execution of th

196 8.2.4 Using the Internal RAM Area as External Addresses When the RAME bit in SYSCR is 0, the internal RAM area can be used external addresses. N

197 Appendix A I/O File Format High-performance Embedded Workshop formats the [IO] window based on information it finds in an I/O Register definiti

198 Example: ; H8S/2655 Series I/O Register Definitions File [Modules] BaseAddress=0 Module1=Power_Down_Mode_Registers Module2=DMA_Channel_Common

199 A.2 File format (Bit Field Supported) Each module name must be defined in the [Modules] definition section and the numbering of each module must

2 1.2 Warnings CAUTION READ the following warnings before using the emulator product. Incorrect operation will damage the user system and the emu

200 Example: ; H8S/2655 Series I/O Register Definitions File [Modules] FileVersion=2 BaseAddress=0 Module1=Power_Down_Mode_Registers Module2=DMA_

201 Appendix B Menus Table B.1 shows GUI menus. Table B.1 GUI Menus Menu Option Shortcut Toolbar Button Remarks View Difference Opens the

202 Table G.1 GUI Menus (cont) Menu Option Shortcut Toolbar Button Remarks View (cont) Gra-phic Image… Shift + Ctrl + G Opens the [Image] wind

203 Table G.1 GUI Menus (cont) Menu Option Shortcut Toolbar Button Remarks Debug (cont) Step In F11 Executes a block of user program before b

204 Table G.1 GUI Menus (cont) Menu Option Shortcut Toolbar Button Remarks Setup Customize… Customize the High-performance Embedded Workshop

205 Appendix C Command Lines Table C.1 lists the High-performance Embedded Workshop commands. Table C.1 High-performance Embedded Workshop Command

206 Table H.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function 34 GENERATE_MAKE_ FILE GM Creates a makefi

207 Table H.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function 73 SUBMIT SU Executes a command file 74

208

209 Appendix D Diagnostic Test Procedure This section describes the diagnostic test procedure using the E6000 test program. D.1 System Set-Up for

3 1.3 Environmental Conditions CAUTION Observe the conditions listed in table 1.1 when using the emulator. Failure to do so will cause illegal o

210 D.2 Diagnostic Test Procedure Using Test Program Insert the CD-R (HS2214EPI62SR supplied with the emulator) into the CD-ROM drive of the host co

211 The following messages are displayed during test. This test consists of steps 1 to 18. Message Description E6000 H8S/2214_62 Emulator Tests Vx.x

212 04) Testing Trace memory : A) Decode Test page [H'000 - H'04f] (Lower 32 K) ...OK B) Marching Test page [H'000 - H'04f] (

213 13) Testing Emulation RAM Trace : A) Free Trace ...OK B) Range Trace ...OK C) Point to Point Trace .

Renesas Microcomputer Development Environment System User's Manual H8S/2214 E6000 EmulatorPublication Date: 1st

Sales Strategic Planning Div. Nippon Bldg., 2-6-2, Ohte-machi, Chiyoda-ku, Tokyo 100-0004, Japanhttp://www.renesas.comRefer to

H8S/2214 E6000 Emulator User's Manual

4

5 Section 2 Preparation before Use 2.1 Emulator Preparation Unpack the emulator and prepare it for use as follows: WARNING READ the reference s

6 2.3 Connecting to the User System To connect the emulator to a user system, proceed as follows: • Connect the user system interface cable head to

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

8 2.4 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

9 2.6 Hardware Interface All signals are directly connected to the MCU in the emulator with no buffering with the exception of those listed in sectio

1. These materials are intended as a reference to assist our customers in the selection of the Renesas Technology Corp. product best suited to the

10 The interface circuit for the external probe 1 is shown in figure 2.8. 10 kExternal probe 1, 2, 3, 4HD15101522VccΩΩ Figure 2.8 Interface Circuit

11 2.6.6 Voltage Follower Circuit CAUTION 1. Do not connect the user system interface cable to the emulator without user system connection.

12 2.7 System Check When the software is executed, use the procedure below to check that the emulator is connected correctly. Here, use the worksp

13 5. The [Welcome!] dialog box is displayed. Figure 2.12 [Welcome!] Dialog Box To use a workspace for the tutorial, select the [Browse to anoth

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

15 7. Set up the emulator. During this process, the following dialog box is displayed. Figure 2.16 [Connecting] Dialog Box

16 8. When "Connected" is displayed in the [Output] window of the High-performance Embedded Workshop, the emulator initiation is completed

17 2.8 Communication Problems The following message box will be displayed when the emulator power is turned off or the PC interface cable is not corr

18

19 Section 3 E6000 Emulator Functions 3.1 Debugging Features 3.1.1 Breakpoints The emulator provides a comprehensive range of alternative types of

20 3.1.5 Bus Monitoring The emulator incorporates a bus monitoring function that monitors and displays the contents of the accessed area in High-perf

21 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 rang

22 3.3 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

23 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 interna

24

25 Section 4 Preparation before Use 4.1 Method for Activating High-performance Embedded Workshop To activate the High-performance Embedded Worksho

26 4.1.1 Creating a New Workspace (Toolchain Not Used) 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Worksho

27 2. Creation of a new workspace is started. The following dialog box is displayed. Figure 4.3 [New Project Workspace] Dialog Box [Workspace Na

28 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 t

29 4. Set the configuration file name. Figure 4.5 [New Project – Step 8] Dialog Box If multiple target platforms were selected in the [New Proje

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

30 4.1.2 Creating a New Workspace (Toolchain Used) 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop i

31 2. Creation of a new workspace is started. The following dialog box is displayed. Figure 4.7 [New Project Workspace] Dialog Box [Workspace Na

32 3. Make the required setting for the toolchain. When the setting has been completed, the following dialog box is displayed. Figure 4.8 [New

33 4. Set the configuration file name. Figure 4.9 [New Project – Step 8] Dialog Box If multiple target platforms were selected in the [New Proje

34 4.1.3 Selecting an Existing Workspace 1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded Workshop is activate

35 4.2 Connecting the Emulator Select either of the following two ways to connect the emulator: (a) Connecting the emulator after the setting at em

36 4.3 Reconnecting the Emulator When the emulator is disconnected, use the following way for reconnection: Select [Debug -> Connect] or click t

37 Section 5 Debugging This section describes the debugging operations and their related windows and dialog boxes. Refer to the High-performance Em

38 5.1 Setting the Environment for Emulation 5.1.1 Opening the [Configuration Properties] Dialog Box Selecting [Setup -> Emulator -> System…]

39 [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 f

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

40 5.1.2 Selecting an MCU Not Included in the List Selecting [Custom] in [Device] of the [Configuration Properties] dialog box adds the [Custom Devi

41 5.1.3 Selecting the Interface to be Connected Checking [Change driver in start up] on the [Configuration Properties] dialog box allows a selectio

42 5.1.4 Opening the [Memory Mapping] Dialog Box Selecting [Setup -> Emulator -> Memory Resource…] or clicking the [Emulator Memory Resource]

43 5.1.5 Changing the Memory Map Setting Clicking the [Add…] button on the [Memory Mapping] dialog box or clicking the [Modify…] button after select

44 5.2 Downloading a Program This section describes how to download a program and view it as source code or assembly-language mnemonics. Note: Afte

45 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 sele

46 Source Address column When a program is downloaded, an address for the current source file is displayed on the Source address column. These addres

47 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 Forma

48 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] op

49 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 chang

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

50 5.3 Viewing the Current Status Choose [View -> CPU -> Status] or click the [View Status] toolbar button ( ) to open the [Status] window and

51 5.4 Reading and Displaying the Emulator Information Regularly Use the [Extended Monitor] window to know the changing information on the emulator

52 5.4.2 Selecting Items to be Displayed Selecting [Properties…] from the popup menu displays the [Extended Monitor Configuration] dialog box. Figu

53 5.5 Displaying Memory Contents in Realtime Use the [Monitor] window to monitor the memory contents during user program execution. In the Monitor

54 [Name]: Decides the name of the monitor window. [Options]: Sets monitor conditions. [Address]: Sets the start address for monitoring. [Siz

55 Figure 5.15 [Monitor] Window During user program execution, the display is updated according to the setting value of the auto-update interval.

56 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]

57 5.5.7 Managing the [Monitor] Window Selecting [Display -> CPU -> Monitor -> Windows Select…] displays the [Windows Select] dialog box. I

58 5.6 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

59 2. Read the memory content directly from the High-performance Embedded Workshop to update the values without halting the user program since the b

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

60 5.7 Using the Event Points The emulator has the event point function that performs breaking, tracing, and execution time measurement by specifyi

61 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

62 Table 5.2 Area Signals Acquired by the Emulator Area Trace Display (Status) Description On-chip ROM ROM ROM On-chip RAM RAM RAM On-chip I/O

63 Select [Add...] or the software breakpoint displayed in this window and then select [Edit...] from the popup menu to display the [Breakpoint/Event

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

65 (1) [General] page The address and data conditions are set. Figure 5.22 [Breakpoint/Event Properties] Dialog Box ([General] Page) [Type]: Se

66 [Data Compare]: Sets the data condition. [Compare]: Checking this box compares data. [Use Mask]: Sets a mask condition (available when [Compar

67 (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 B

68 (3) [Signals] page Use this page to set external signals. Figure 5.24 [Breakpoint/Event Properties] Dialog Box ([Signals] Page) [Probe4]: De

69 [Probe1]: Detects the status of the input probe signal 1 [High]: Detects the high level of the input probe signal [Low]: Detects the low le

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 emula

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

71 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 ev

72 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 po

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

74 5.8 Viewing the Trace Information The emulator acquires the results of each instruction execution into the trace buffer as trace information and

75 [Status]: Bus status during this cycle; DTC operation, PROG (prefetch), Data (CPU data access cycle), Refresh (refresh cycle), or DMAC (DMAC cycl

76 5.8.3 Specifying Trace Acquisition Conditions The capacity of the trace buffer is limited. When the buffer becomes full, the oldest trace informa

77 [Suppress]: Acquires no trace information of the specified types of bus cycle. [Time Stamp]: Sets a condition for time stamping. [Clock]: Selec

78 (2) [Stop] page Sets trace stop conditions. It is possible to set trace stop conditions with and without delay, with both allowed simultaneously.

79 (3) [Delayed Stop] page Sets trace stop conditions. It is possible to set trace stop conditions with and without delay, with both allowed simultan