Renesas HS1653ECN61H User Manual

H8SX E6000H Emulator User’s Manual Renesas Microcomputer Development Environment System H8SX Family / H8SX/1650 Group H8SX/1520 Group H8SX/1544 Grou

VI Warnings on Emulator Usage Warnings described below apply as long as you use this emulator. Be sure to read and understand the warnings below befo

25 3.4 Support of the Target MCU 3.4.1 Memory Space The architecture of the MCU allows for a 16-Mbyte memory space. (1) On-Chip I/O Area If an att

26 3.4.4 Control Input Signals (/RES and /NMI) The MCU control input signals are /RES and /NMI. The /RES and /NMI signals are only valid when emulat

27 3.4.7 Emulator State and Internal Modules Operation of some internal modules depends on the emulator’s state. Tables 3.3 and 3.4 show the relati

28 3.4.8 Differences in Values of Registers Note that certain general and control registers of both emulators are initialized whenever the system is

29 3.5 Notes Specific to the H8SX/1527 E6000H and H8SX/1527R E6000H Emulators 3.5.1 Custom Device Function The maximum value selectable for the on-

30

31 Section 4 Diagnostic Test Procedure This section describes the diagnostic test procedure using the E6000H diagnostic program. 4.1 System Set-Up

32 Figure 4.1 [Misc] Page 5. Turn on the E6000H emulator switch. Note: To execute the diagnostic program, firstly turn on the power of the emula

33 4.2 Test Item of the Diagnostic Program (HS1527KEPH60H) Table 4.1 shows the test items of this diagnostic program. Table 4.1 Test Items of the

34 4.3 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS1650EPH60SR supplied with the emulator) into the CD-ROM drive of th

VII CAUTION Place the emulator station and evaluation chip board so that the trace cables are not bent or twisted. A bent or twisted cable

35 The following messages are displayed during the test. There are 15 steps in this test. Message Description H8SX/1527 E6000H Emulator Tests V*.* T

36 11) EMU 35.7Mhz MPU 35.7Mhz Sampling 20ns ...OK 12) EMU 35.9Mhz MPU 35.9Mhz Sampling 20ns ...OK 13) E

37 4.4 Test Item of the Diagnostic Program (HS1527REPH60H) Table 4.2 shows the test items of this diagnostic program. Table 4.2 Test Items of the

38 4.5 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS1650EPH60SR supplied with the emulator) into the CD-ROM drive of th

39 The following messages are displayed during the test. There are 15 steps in this test. Message Description H8SX/1527R E6000H Emulator Tests V*.*

40 11) EMU 35.7Mhz MPU 35.7Mhz Sampling 20ns ...OK 12) EMU 35.9Mhz MPU 35.9Mhz Sampling 20ns ...OK 13) E

H8SX/1544 Hardware Part

1 Section 1 Overview 1.1 Notes on Usage CAUTION READ the following warnings before using the emulator product. Incorrect operation will damag

2 1.2 Emulator Hardware Components The emulator consists of an E6000H station and the E6000H’s front-end unit. By installing a user system interface

VIII 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

3 1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances) The names of the components on the front/rear panel of t

4 Rear Panel: Figure 1.3 E6000H Station: Rear Panel (a) Power switch: Turning this switch to I (input) supplies power to the emulator (E600

5 1.2.2 Front-end Unit Configuration The names of the components on the front-end unit are listed below. 1812. 55. 543. 612430. 6162. 8PCN2UCN1XTAL(

6 1.3 System Configuration The emulator must be connected to a host computer via the selected PC interface board (PCI bus or PC card bus), LAN adapte

7 (3) USB Adapter Figure 1.7 shows the configuration of a system in which the USB adapter is used. A USB adapter can be used to connect the emulator

8

9 Section 2 Preparation before Use 2.1 Description on Emulator Usage This section describes the preparation before emulator usage. Figure 2.1 is a

10 2.2 Emulator Connection The following description covers connection of the emulator. 2.2.1 Connecting the Emulator to the User System WARNING

11 2.2.3 Precautions on Connecting the User System When connecting the emulator to the user system, note the following: 1. Secure the E6000H statio

12 2.2.4 Connecting the External Probe CAUTION Check the external probe direction and connect the external probe to the emulator station correc

i Preface Thank you for purchasing the E6000H emulator. CAUTION Read this manual before using the emulator product. Incorrect operation or con

13 2.2.5 Selecting the Clock This emulator supports three types of clock for the MCU: a crystal oscillator attached on the emulator’s front-end unit

14 XTALUCN1Crystal oscillator terminalsCrystaloscillatorEnlarged viewX1 X2PCN2 Figure 2.3 Installing the Crystal Oscillator External Clock: Fo

15 2.2.6 Connecting the System Ground CAUTION Separate the frame ground from the signal ground at the user system. When the frame ground is co

16 The user system must be connected to an appropriate ground so as to minimize noise and the adverse effects of ground loops. When connecting the em

17 Section 3 Hardware Specifications 3.1 Environmental Conditions CAUTION Observe the conditions listed in table 3.1 when using the emulator.

18 3.2 Emulator External Dimensions and Mass Figures 3.1 shows the external dimensions and mass of the E6000H emulator. Figure 3.1 External Dimen

19 3.3 User System Interface Circuit 3.3.1 User System Interface Circuit The circuits that interface the MCU in the emulator to the user system inc

20 MCUMD controlcircuitMonitorcircuitVHC14MD0MD1MD2MD0MD1MD2Vcc4.7 kΩVHC244 EPM7256VHC244_RES_NMI_STBY_RES_NMI_STBYVcc4.7 kΩUser systeminterface cabl

21 MCUVccUser systeminterface cableVssEXTALXTALVccVssEXTALXTALVCLEMLENCNCNCNCVHC244 EPM7256Voltage-followercircuitVcc4.7 kΩLPT24423 kΩVHC2443.3 V Fig

22 Avcc Avss AVref VHCT125 VHC125 Sub-MCU P56, P57 P11 to P13 P30 to P33 P61, P62PA3 to PA7 PD0 to PD7 PE0 to

ii About This Manual This manual is comprised of two parts: Hardware Part and Debugger Part. Hardware Part: Preparation before use, hardware specif

23 MCU VHCT125 VHC125 CB3Q3306 P24 to P27 P10 P60 MCU VHCT125 VHC125 CB3Q3306 P10 P60 MCU VHCT125 VHC125 PCA9306 P14 to P17

24 P20, P21, P23P34 to P37P63 to P67PA0 to PA2PI0 to PI3PJ0 to PJ7PK0 to PK7 MCU VHCT125 VHC125 PF0 to PF4, PF6, PF7 MCU

25 PF5 MCU VHCT125 VHC125 PF5 Sub-MCU PF5 CB3Q3306 LVC07 VCC 1 kΩ3 VUser systeminterface cable47 kΩCB3Q3306 Figure 3.2 User Syste

26 3.4 Support of the Target MCU 3.4.1 Memory Space The architecture of the MCU allows for a 16-Mbyte memory space. (1) On-Chip I/O Area If an att

27 3.4.4 Control Input Signals (/RES, /NMI, and /STBY) The MCU control input signals are /RES, /NMI, and /STBY. The /RES, /NMI, and /STBY signals ar

28 3.4.7 Emulator State and Internal Modules Operation of some internal modules depends on the emulator’s state. Table 3.3 shows the relation betwe

29 3.4.8 Differences in Values of Registers Note that certain general and control registers of both emulators are initialized whenever the system is

30 3.5.5 Port Registers (PORTx) ⎯Restriction (1) When the module pins are used as inputs In the emulator, undefined values are read from PORTx corre

31 Section 4 Diagnostic Test Procedure This section describes the diagnostic test procedure using the E6000H diagnostic program. 4.1 System Set-Up

32 Figure 4.1 [Misc] Page 5. Turn on the E6000H emulator switch. Note: To execute the diagnostic program, firstly turn on the power of the emula

iii Contents H8SX/1650 Hardware Part Section 1 Overview...

33 4.2 Test Item of the Diagnostic Program Table 4.1 shows the test items of this diagnostic program. Table 4.1 Test Items of the Diagnostic Progr

34 4.3 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS1650EPH60SR supplied with the emulator) into the CD-ROM drive of th

35 The following messages are displayed during the test. There are 15 steps in this test. Message Description H8SX/1544 E6000H Emulator Tests V*.* T

36 10) EMU 4MHz MPU 32MHz Sampling 20ns ...OK 11) EMU 35.7MHz MPU 35.7MHz Sampling 20ns ...

Debugger Part

1 Section 1 Overview The Debugger Part includes the following information. Table 1.1 Debugger Part Contents Section Title Content 2 Preparation

2

3 Section 2 Preparation before Use 2.1 Method for Activating High-performance Embedded Workshop To activate the High-performance Embedded Workshop

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

iv H8SX/1527 and H8SX/1527R Hardware Part Section 1 Overview ...

5 2. Creation of a new workspace is started. The following dialog box is displayed. Figure 2.3 [New Project Workspace] Dialog Box [Workspace Nam

6 3. Select the target platform of the session file. The following dialog box is displayed. Figure 2.4 [New Project – Step 7] Dialog Box The ta

7 4. Set the configuration file name. The configuration file saves the state of High-performance Embedded Workshop except for the emulator. Figur

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

9 2. Creation of a new workspace is started. The following dialog box is displayed. Figure 2.7 [New Project Workspace] Dialog Box [Workspace Nam

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

11 4. Set the configuration file name. The configuration file saves the state of High-performance Embedded Workshop except for the emulator. Figu

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

13 2.2 Connecting the Emulator Select either of the following two ways to connect the emulator: (a) Connecting the emulator after the setting at emu

14 2.3 Re-connecting the Emulator When the emulator is disconnected, re-connection is possible by using the following methods. Select [Debug -> C

v H8SX/1544 Hardware Part Section 1 Overview... 1 1.1 Not

15 Section 3 Debugging This section describes the debugging operations and their related windows and dialog boxes. 3.1 Setting the Environment for

16 [General] page [Device] Selects the target MCU to be emulated. See the hardware manual for details. [Custom Device enable] Customizes the target

17 3.1.2 Customizing the Settings for the Target MCU Selecting [Custom Device enable] in the [Configuration Properties] dialog box adds the [Custom

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

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

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

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

22 In this window, the following items are shown on the left as information on lines. • 1st column (Line Number column): A line number for the sourc

23 To switch off a column in all source files 1. Click the right-hand mouse button on the [Editor] window or select the [Edit] menu. 2. Click th

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

vi 4.3 Diagnostic Test Procedure Using the Diagnostic Program ... 34 Debugger Part Section 1 Overview

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

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

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

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

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

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

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

32 3.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]

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

34 3.6 Looking at Variables This section describes how you can look at variables in the source program. 3.6.1 [Watch] Window You can view any value

vii 3.7.10 Viewing the Source Line for an Event Point...46 3.7.11 Setting a Data Condition fo

35 Notes: 1. This function can be set per variable or per element or body for structures of data. 2. The color of an [R] in the [Name] column cha

36 3.7 Using the Event Points The emulator has the event point function to support breakpoints of the following three types. Software breakpoints: E

37 3.7.1 Setting a Software Breakpoint Use the [Software] sheet on the [Event] window to display, change, or add settings for software breakpoints.

38 To add a new software breakpoint, select an empty line from the list box on the [Software Break] page and click the [Edit…] button. To change exis

39 3.7.2 Setting an On-Chip Breakpoint Use the [On Chip] sheet on the [Event] window to display, change, or add settings for on-chip breakpoints. Se

40 List box: Displays the current settings for each of the channels. If no setting has been made for a channel, only the channel number is displayed

41 [Address]: Sets address bus conditions. [Don’t Care]: Selects no address bus condition. [Address]: Sets an address bus value. [Use mask]:

42 3.7.3 Settings an On-Emulator Breakpoint Use the [On Emulator] sheet on the [Event] window to display, change, or add settings for on-emulator br

43 The user can set more complex break conditions in the [On Emulator Break Channel n] dialog box by a combination of conditions provided on pages [A

44 [Address]: Sets address conditions. [Don’t Care]: Selects no address bus condition. [Address]: Select this button to set the address bus va

viii 4.12 Displaying Local Variables... 101 4.13 Steppi

45 [External 32bit]: Selects an external area with the 32-bit width where no emulation memory is allocated as the condition. [External 16bit]: Sele

46 3.7.8 Deleting an Event Point Select an event point and choose [Delete] from the popup menu to remove the selected event point. To retain the eve

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

48 [R/W]: Whether access was read (RD) or write (WR) [SZ]: Selects the size of an access as B (byte), W (word), or L (longword). [Status]:

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

50 (1) [Condition] page Figure 3.27 [Trace Acquisition Properties] Dialog Box ([Condition] Page) [Sequential Trace Stop]: Use this option to set

51 [Back]: Puts the setting back to the previous state at the time the dialog box has been displayed. List box: Displays the current settings for e

52 (2) [Other] page Figure 3.28 [Trace Acquisition] Dialog Box ([Other] Page) [When trace-buffer full]: Selects an action to take when the trace

53 [Clock/8]: Time stamping is in terms of the number of bus-clock cycles, i.e., is synchronized with 1/8 cycle of the system clock signal (φ). [Sel

54 (3) [Trace Acquisition Condition Channel n] dialog box Use this dialog box to set pass points and a reset point for a sequential trace stop, and c

ix Section 6 Error Messages... 153 6.1 Error Messages of the Emula

55 [None]: Select this option if you do not want to take any of the actions listed above. This is useful for a trigger output or execution time meas

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

57 [R/W]: Select the type of access cycles. [Don't care]: Detects no read/write condition when this box is checked. [Setting]: Detects

58 Clicking the [OK] button after setting conditions in those pages stores the settings and starts searching. Clicking the [Cancel] button closes th

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

60 [InstructionAddress]: Set an instruction address condition. [Don't care]: Detects no address when this box is checked. [Value]: Detec

61 [Area]: Select the area being accessed. [Don't care]: Detects no area condition when this box is checked. [Setting]: Detects the specif

62 Set filtering conditions and then press the [OK] button. This starts filtering according to the conditions. Clicking the [Cancel] button closes t

63 3.8.13 Analyzing Statistical Information Choose [Statistic] from the popup menu to open the [Statistic] dialog box and analyze statistical inform

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

H8SX/1650 Hardware Part

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

66 Table 3.2 Mode Settings for Measurement Point Measurement Mode 1 2 3 4 5 6 7 8 Time Of Specified Range Measurement Ο Ο Ο Ο Ο Ο Ο Ο Start

67 3.9.1 Opening the [Performance Analysis] Window Choose [View -> Performance -> Performance Analysis] or click the [PA] toolbar button () to

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

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

70 (2) Start Point To End Point Measurement Figure 3.39 Start Point To End Point Measurement Settings [Range Name]: The name of the range to be m

71 Measures the execution time and the execution count in the range between start address and end address. Starts measurement with a detected program

72 (4) Access Count Of Specified Range Measurement Figure 3.41 Access Count Of Specified Range Measurement Settings [Range Name]: The name of the

73 (5) Called Count Of Specified Range Measurement Figure 3.42 Called Count Of Specified Range Measurement Settings [Range Name]: The name of the

74 3.9.3 Starting Performance Data Acquisition Executing the user program clears the result of previous measurement and automatically starts measuri

75 3.10 Profiling Function 3.10.1 Enabling the Profile Choose [View->Performance->Profile] to open the [Profile] window. Choose [Enable Profil

76 3.10.4 [List] Sheet Figure 3.43 [Profile] Window ([List] Sheet) This window displays the address and size of a function or a global variable, t

77 3.10.5 [Tree] Sheet Figure 3.44 [Profile] Window ([Tree] Sheet) This window displays the relation of function calls in a tree structure. Displa

78 • Not trace the function call Stops tracing function calls while profile data is acquired. This menu is used when acquiring profile data of the p

79 3.11 [Profile-Chart] Window Figure 3.45 [Profile-Chart] Window This window displays the relation of calls for a specific function. This window

80 • Multiple View If the [Profile-Chart] window is going to be opened when it has already been opened, selects whether another window is to be open

81 3.12 RTOS Extension Function The RTOS extension function supports the debugging of RTOS tasks. The function is implemented by setting the IDs of

82 [RTOS Support Function]: Sets up the RTOS extension function. [Don’t Care]: Disables the RTOS extension function. [TASK ID writing area]: Speci

83 3.12.3 Functions Made Available by [TASK Selection] (1) Display of the [TASK Selection] Settings Figure 3.47 [Status] Window [Platform] sheet:

84 3.12.4 Performance Measurement (Conditions for Measurement) The following conditions are included among those selectable under the [Measurement M

1 Section 1 Overview 1.1 Notes on Usage CAUTION READ the following warnings before using the emulator product. Incorrect operation will damag

85 Section 4 Tutorial 4.1 Introduction This section describes the main functions of the emulator by using a tutorial program. The tutorial program i

86 4.2 Running the High-performance Embedded Workshop Open a workspace by following the procedure listed in section 2.1.3, Selecting an Existing Wor

87 4.3 Connecting the Emulator 4.3.1 Selecting a Session The selectable session depends on the emulator. Select the session suitable for the emulato

88 4.4 Downloading the Tutorial Program 4.4.1 Downloading the Tutorial Program Download the object program to be debugged. • Select [Download modu

89 4.4.2 Displaying the Source Program The High-performance Embedded Workshop allows the user to debug a user program at the source level. • Double-

90 4.5 Setting a Software Breakpoint A software breakpoint is a simple debugging function. The [Editor] window provides a very simple way of settin

91 4.6 Setting Registers Set a value in the program counter before executing the program. • Select [Registers] from the [CPU] submenu of the [View

92 4.7 Executing the Program Execute the program as described in the following: • To execute the program, select [Go] from the [Debug] menu, or cl

93 Figure 4.10 [Editor] Window (Break Status)

94 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] me

2 1.2 Emulator Hardware Components The emulator consists of an E6000H station and an evaluation chip board. By installing a user system interface bo

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

96 4.9 Referring to Symbols The [Label] window can be used to display the information on symbols in modules. Select [Label] from the [Symbol] subme

97 4.10 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

98 4.11 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 c

99 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 se

100 The user can click mark ‘+’ at the left side of array a in the [Watch] window to watch all the elements. Figure 4.20 [Watch] Window (Displayin

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

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

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

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

3 1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances) The names of the components on the front/rear panel of t

105 4.13.3 Executing the [Step Over] Command The [Step Over] executes a function call in a single step and stops at the next statement of the main

106 4.14 Forced Breaking of Program Executions The High-performance Embedded Workshop can force a break during the execution of a program. • Cance

107 4.16 Break Function The emulator provides break functions by software breaks, on-chip breaks, and on-emulator breaks. Software breakpoints, on

108 Figure 4.33 [Breakpoint Properties] Dialog Box

109 • Click the [Edit…] button to display the [Software Break] dialog box. Figure 4.34 [Software Break] Dialog Box • Use the [Editor] window to

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

111 The program runs until it stops at the breakpoint that has been set. Figure 4.36 [Editor] Window at Execution Stop (Software Break)

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

113 4.16.2 On-Chip Break Function Setting of an on-chip breakpoint on channel 4 such that a break is triggered when the break condition has been sa

114 • Make the following settings in the group boxes on the [Address] page: Uncheck the [Don’t Care] checkbox. Then use the [Editor] window to refe

4 Rear Panel: Figure 1.3 E6000H Station: Rear Panel (a) Power switch: Turning this switch to I (input) supplies power to the emulator (E600

115 4.17 Trace Functions The trace functions of the emulator use the realtime trace buffer, which can store the information of up to 128-k bus cycl

116 4.17.1 Displaying Trace Information by the Free Trace Function The free trace function allows continuous acquisition of trace information from

117 (2) Set a software breakpoint at the address on the line that has ‘p_sam->s0=a[0];’ within the tutorial function (refer to section 4.16.1, Sof

118 4.17.2 Displaying Trace Information by the Trace Stop Function While the trace stop function is in use, acquisition of trace information stops

119 (3) An address must be set as the condition. Uncheck [Don’t Care] on the [Address] page of the [Trace Acquisition Condition Channel 1] dialog bo

120 (4) Items that have been set are displayed in the list box on the [Condition] page of the [Trace Acquisition Properties] dialog box. Click the [

121 4.17.3 Displaying Trace Information by the Conditional Trace Function The conditional trace function only acquires trace information at the addr

122 4.17.4 Statistics The number of times the on-chip RAM has been written to can be included in the acquired trace information. (1) Delete all the

123 (5) Select [R/W] in the [Item] combo box and enter WR in the [Start] edit box. Then, click the [New] button. “R/W=WR” will be displayed in the [

124 (6) Then, select [Area] from the [Item] combo box and enter INRAM in the [Start] edit box. Then, click the [Add] button; the new condition is no

5 1.2.2 Evaluation Chip Board Configuration The names of the components on the evaluation chip board of the emulator are listed below. Figure 1.4

125 (7) To start statistical analysis of the specified condition, press the [Result] button. The number of write operations that satisfies the condi

126 4.17.5 Function Calls This mechanism is only used to collect trace information on the function calls. (1) Make the setting so that a break occur

127 4.18 Stack Trace Function The emulator uses the information on the stack to display the function call history. Notes: 1. This function can be

128 • Select [Reset Go] from the [Debug] menu. • After the break in program execution, select [Stack Trace] from the [Code] submenu of the [View] m

129 4.19 Performance Analysis Function Performance analysis by the emulator is available in the following modes: • Time Of Specified Range Measure

130 (3) Select the line in the [Performance Analysis] window that has 1 in its [No] column and click the right-hand mouse button to display a popup

131 Note: The addresses figured out in the [Input Function Range] dialog box are just for reference. In some cases, the end address of a function ma

132 4.20 Profiling Function The profiling function allows the user measure the performance for each of the functions. (1) Select [Profile] from the

133 (2) To enable the profiling function, click the right-hand mouse button on the [Profile] window to show the popup menu and select [Enable Profile

134 (3) Set an on-chip breakpoint by an address condition at the line which includes “delete p_sam;” in the tutorial function (see section 4.16.2, On

6 1.3 System Configuration The emulator must be connected to a host computer via the selected PC interface board (PCI bus or PC card bus), LAN adapte

135 (5) The [Profile] window is shown below. Figure 4.65 [Profile] Window ([List] Sheet) (6) Click the [Tree] tab on the [Profile] window to disp

136 (7) Click the right-hand mouse button on the [Profile] window and select [View Profile-Chart] to open the [Profile-Chart] window. Figure 4.67

137 4.21 Monitor Function The emulator allows monitoring of the contents of specified addresses in memory during execution of the user program. In

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

139 (3) Click the [OK] button to open the [Monitor] window. Figure 4.70 [Monitor] Window (4) Select [Reset Go] from the [Debug] menu. When the

140

141 Section 5 Software Specifications and Notes Specific to This Product This section describes the software specifications and notes specific to t

142 5.3 Memory Map • Some emulators may not support the memory mapping function. • Attributes of a memory map can be defined in units of blocks as

143 5.4 Displaying and Modifying the Contents of Memory 5.4.1 Displaying and Modifying the Contents of Memory during Execution The emulator accesse

144 5.4.3 Parallel Access Function The parallel access function is implemented by the DTC channels specialized for the debugger, which are not user

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 cus

7 (3) USB Adapter Figure 1.7 shows the configuration of a system in which the USB adapter is used. A USB adapter can be used to connect the emulator

145 5.6 Event Functions 5.6.1 Software Breakpoints • A software breakpoint is accomplished by replacing the instruction at the specified address wit

146 5.6.3 On-Emulator Break • A break will occur several cycles after a condition is satisfied. • The states of IRQ15 to IRQ0 are ORed and this res

147 Table 5.4 User Bus and Break Setting for an Output of Data (Big Endian) Access sizeByteAddressBreak area bus32 bit 16 bit8 bit 32 bitD31D0DDDDDD

148 Table 5.5 User Bus and Break Setting for an Output of Data (Little Endian) Access sizeByteAddressBreak area bus32 bit 16 bit8 bit 32 bitD31D0DDD

149 5.7 Trace Functions 5.7.1 Displaying the Trace Information • The states of IRQ15 to IRQ0 are ORed and this result is applied as the IRQ conditi

150 5.9 Performance Analysis Function 5.9.1 Errors An error will be included in the measured performance as follows: • ±one-resolution error (±20-n

151 5.11 RTOS Extension Function 5.11.1 Input Values for the [TASK ID writing area] Input Edit Box Specify the address to which the task IDs are wr

152 5.12 Input Format 5.12.1 Entering Masks Address bus conditions and data bus conditions can be input with masks. Addresses can be masked in 1-, 3-

153 Section 6 Error Messages 6.1 Error Messages of the Emulator 6.1.1 Error Messages at Emulator Initiation The emulator displays error messages

154 Table 6.1 Error Messages at Initiation Error Message Description and Solution There is no configuration file. The configuration file that is

8

155 Table 6.1 Error Messages at Initiation (cont) Error Message Description and Solution Can’t find firmware file Firmware open Error Firmware Dow

156

157 Appendix A Menus Table A.1 shows GUI menus. Table A.1 GUI Menus Menu Option Shortcut Toolbar Button Remarks View Command Line Ctrl + L

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

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

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

161 Appendix B Command Lines Table B.1 lists the High-performance Embedded Workshop commands. Table B.1 High-performance Embedded Workshop Command

162 Table B.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function 30 DISASSEMBLE DA Disassembles memory c

163 Table B.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function 69 REFRESH RF Updates windows related t

164 Table B.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function 104 WATCH_ADD WA Adds a watch item 105

9 Section 2 Preparation before Use 2.1 Description on Emulator Usage This section describes the preparation before emulator usage. Figure 2.1 is a

Renesas Microcomputer Development Environment System User's Manual H8SX E6000H EmulatorPublication

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

2-6-2, Ote-machi, Chiyoda-ku, Tokyo,100-0004, JapanH8SX E6000H Emulator User’s Manual

10 2.2 Emulator Connection The following description covers connection of the emulator. 2.2.1 Connecting the Emulator to the User System WARNING

11 2.2.3 Connection by the User System Interface Connectors WARNING Always switch OFF the emulator and user system before connecting or disco

12 Evaluation chip boardConnector: WD-200P-VF85-N(manufactured by Japan Aviation Electronics Industry, Ltd.) Figure 2.2 Connection Using the Ded

13 95.0Hole for a connector (NTH) × 4UCN1UCN22001992001992121Unit: mmTolerance: ±0.1 mmWD-200P-VF85-N Figure 2.4 Location for Mounting the Connecto

14 2.2.4 Pin Arrangement on the User System Interface Connector Table 2.1 lists the pin arrangement on the user system interface connector of HS1650

15 Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No. Signal Name 49 P56 75 VSS_19 50 P57 76

16 Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No. Signal Name 101 PE4 127 VSS_35 102 PE5

17 Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No. Signal Name 153 VSS_38 177 VSS_46 154 V

18 Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name 1 ⎯ 31 ⎯ 2 ⎯ 32 ⎯ 3 ⎯ 33

19 Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name 61 ⎯ 90 ⎯ 62 ⎯ 91 ⎯ 63 ⎯

20 Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name 119 ⎯ 146 ⎯ 120 ⎯ 147 VSS_

21 Table 2.1 Pin Arrangement on HS1650EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name 173 ⎯ 187 MD0 174 ⎯ 188 MD

22 2.2.5 Precautions on Connecting the User System When connecting the evaluation chip board to the user system, note the following: 1. Secure the

23 2.2.6 Connecting the External Probe (Not Supported in this Emulator) CAUTION Check the external probe direction and connect the external probe

24 2.2.7 Selecting the Clock This emulator supports three types of clock for the MCUs listed in table 2.2: a crystal oscillator attached on the eval

25 Evaluation chip boardCrystal oscillator terminalsCrystaloscillatorEnlarged viewX1 X2 Figure 2.6 Installing the Crystal Oscillator External

26 2.2.8 Connecting the System Ground CAUTION Separate the frame ground from the signal ground at the user system. When the frame ground is co

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

27 The user system must be connected to an appropriate ground so as to minimize noise and the adverse effects of ground loops. When connecting the ev

28

29 Section 3 Hardware Specifications 3.1 Environmental Conditions CAUTION Observe the conditions listed in table 3.1 when using the emulator.

30 3.2 Emulator External Dimensions and Mass Figures 3.1 shows the external dimensions and mass of the E6000H emulator. Figure 3.1 External D

31 3.3 User System Interface Circuit 3.3.1 User System Interface Circuit The circuits that interface the evaluation chip in the emulator to the use

32 T1BA23 to A0RD/RD/RD/D15 to D0T2 T3When writtentADtAS1tAH1tRSD1tRDS1tRDH1tRSD2tRDS2tRDH2tASDtASDtRSD1tRSD1tAC6tAC4tAA5tAS2tWDDtWSW2tWDH1tWDS1tWRD1

33 MCUMD controlcircuitMonitorcircuitLPT16244MD0MD1MD2MD0MD1MD2Vcc47 kΩVHC244 EPM7256 VHC14_RES_STBY_NMI_RES_STBY_NMIVcc47 kΩUser system Figure 3.3

34 MCUVccUser systemVssEXTALXTALVccVssEXTALXTALVCLEMLENCNCNC NCVHC244 EPM7256Voltage-followercircuitVcc47 kΩLPT2442.3 kΩ Figure 3.3 User System Int

35 User systemP10 to P17P20 to P27P30 to P37P50 to P57AVccAVssAVrefP10 to P17P20 to P27P30 to P37P50 to P57AVccAVssNC0.022 μF0.022 μFAVrefMCUP40 to P

36 User systemP60 to P65PA0PA2PA1PD0 to PD7PE0 to PE7PF0 to PF7PH0 to PH7PI0 to PI7PB0 to PB3MCUPA3 to PA7LPT16244P60 to P65PA0PA2PA1PD0 to PD7PE0 to

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

37 Sub-MCUMD controlcircuitMonitoringcircuitLPT16244MD_CLKVcc47 kΩPM0-PM4User systemVBUSMD_CLKDrVssDrVssPM0-PM4VBUSDrVcc DrVccUSD-USD-USD+USD+Power-s

38 MCUUser system Sub-MCUP14P14SN74CB3Q3306ATXD SN74CB3Q3306AP23P27P23P27SN74CB3Q3306ASN74CB3Q3306AMCUUser systemMCUVHC244UHC14_RESVccUser systemEPM7

39 Note: The power-supply circuits shown in figures 3.4 and 3.5 are turned on/off by the setting of the SW1 jumper pin on the user system interface

40 3.4.4 Control Input Signals (/RES, /NMI, /BREQ, /WAIT, and /STBY) The H8SX/1600-series MCU control input signals are /RES, /NMI, /BREQ, /WAIT, an

41 3.4.7 Emulator State and Internal Modules Operation of some internal modules depends on the emulator’s state. Table 3.4 shows the relation betwe

42 3.4.8 Differences in Values of Registers Note that certain general and control registers of both emulators are initialized whenever the system is

43 3.5 Notes Specific to the H8SX/1650 E6000H Emulator 3.5.1 Custom Device Function The maximum value selectable for the on-chip ROM with the custom

44

45 Section 4 Diagnostic Test Procedure This section describes the diagnostic test procedure using the E6000H diagnostic program. 4.1 System Set-Up

46 Figure 4.1 [Misc] Page 5. Turn on the E6000H emulator switch. Note: To execute the diagnostic program, firstly turn on the power of the emula

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

47 4.2 Test Item of the Diagnostic Program Table 4.1 shows the test items of this diagnostic program. Table 4.1 Test Items of the Diagnostic Progr

48 4.3 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS1650EPH60SR supplied with the emulator) into the CD-ROM drive of th

49 The following messages are displayed during the test. There are 13 steps in this test. Message Description E6000H H8SX/1650 Emulator Tests V*.* T

50 02) EMU 12Mhz MPU 12Mhz Sampling 20ns ...OK 03) EMU 12Mhz MPU 12Mhz Sampling 1.6us ...OK 04) E

H8SX/1527 and H8SX/1527R Hardware Part

1 Section 1 Overview 1.1 Notes on Usage CAUTION READ the following warnings before using the emulator product. Incorrect operation will damag

2 1.2 Emulator Hardware Components The emulator consists of an E6000H station and the E6000H’s front-end unit. By installing a user system interface

3 1.2.1 E6000H Station Components (A Part of Photos may be Different from Real Appearances) The names of the components on the front/rear panel of t

4 Rear Panel: Figure 1.3 E6000H Station: Rear Panel (a) Power switch: Turning this switch to I (input) supplies power to the emulator (E600

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

5 1.2.2 Front-end Unit Configuration The names of the components on the front-end unit are listed below. 1812. 55. 543. 612430. 6162. 8PCN2UCN1XTAL(

6 1.3 System Configuration The emulator must be connected to a host computer via the selected PC interface board (PCI bus or PC card bus), LAN adapte

7 (3) USB Adapter Figure 1.7 shows the configuration of a system in which the USB adapter is used. A USB adapter can be used to connect the emulator

8

9 Section 2 Preparation before Use 2.1 Description on Emulator Usage This section describes the preparation before emulator usage. Figure 2.1 is a

10 2.2 Emulator Connection The following description covers connection of the emulator. 2.2.1 Connecting the Emulator to the User System WARNING

11 2.2.3 Precautions on Connecting the User System When connecting the emulator to the user system, note the following: 1. Secure the E6000H statio

12 2.2.4 Connecting the External Probe CAUTION Check the external probe direction and connect the external probe to the emulator station correc

13 2.2.5 Selecting the Clock This emulator supports three types of clock for the MCU: a crystal oscillator attached on the emulator’s front-end unit

14 XTALUCN1PCN2Crystal oscillator terminalsCrystaloscillatorEnlarged viewX1 X2Note: The model name of the H8SX/1527R E6000H emulator is HS1527RE

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

15 2.2.6 Connecting the System Ground CAUTION Separate the frame ground from the signal ground at the user system. When the frame ground is co

16 The user system must be connected to an appropriate ground so as to minimize noise and the adverse effects of ground loops. When connecting the em

17 Section 3 Hardware Specifications 3.1 Environmental Conditions CAUTION Observe the conditions listed in table 3.1 when using the emulator.

18 3.2 Emulator External Dimensions and Mass Figure 3.1 shows the external dimensions and mass of the E6000H emulator. Figure 3.1 External Dimens

19 3.3 User System Interface Circuit 3.3.1 User System Interface Circuit The circuits that interface the MCU in the emulator to the user system inc

20 MCUMD controlcircuitMonitorcircuitLPT16244MD0MD1MD0MD1Vcc47 kΩVHC244 EPM7256VHC244_RES_NMIRESNMIVcc47 kΩUser systeminterface cableVHC244 Figure 3.

21 MCUVccUser systeminterface cableVssEXTALXTALVccVssEXTALXTALVCLEMLENCNCNCNCVHC244 EPM7256Voltage-followercircuitVcc47 kΩLPT24423 kΩVHC244Vcc47 kΩ F

22 User system interface cableP10 to P17P30 to P37AVccAVssAVrefP40 to P47AVccAVssAVrefMCUP60 to P67PA0, PA4 to PA7PB0 to PB2PH0 to PH7PJ0 to PJ7PI0 t

23 User systeminterface cableP20, P22 to P27MCUVHCT125VHC125Vcc47 kΩCB3Q3306P20, P22 to P27User systeminterface cableP21MCUVHCT125VHC125Vcc47 kΩCB3Q3

24 User systeminterface cablePA1 to PA3MCUVHCT125VHC125Vcc47 kΩCBTS3306SUB MCUPD0 to PD7PA1 to PA3PD0 to PD7PA1 to PA3PD0 to PD7 Figure 3.2 User Sy