Renesas User System Interface Board HS7047ECH61H Manuel d'utilisateur

SH7046 E6000H EmulatorUser’s ManualRenesas Microcomputer Development Environment System SuperH™ Family / SH7046 Series SuperH™ Family / SH7047 Series

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

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

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. [Mode] Selects the operating mode of the tar

17 3.1.2 Settings Associated with the Pin Function Controller The [Pin Select Registers] page of the [Configuration Properties] dialog box allows se

18 [Pin Select Registers] page Option Description [IRQ0] Sets the pins (PA2, PB2, PD16, HIGH) that correspond to the IRQ0 signal. [IRQ1] Sets the p

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

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

21 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

22 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

23 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

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

24 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

25 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

26 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

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

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

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

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

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

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

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

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

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

35 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

36 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

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

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

39 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

40 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

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

42 [Address]: Sets address bus conditions. [Don’t Care]: Selects no address bus condition. [Address]: Sets an address bus value. It is also po

43 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

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

44 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

45 [Address]: Sets address conditions. It is also possible to specify a label as the address value. [Don’t Care]: Selects no address bus condit

46 [External]: Selects an external area where no emulation memory is allocated as the condition. [Emulator]: Selects an external area where emulati

47 3.7.9 Deleting All Event Points Choose [Delete All] from the popup menu to remove all event points. 3.7.10 Viewing the Source Line for an Event

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

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

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

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

52 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

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

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

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

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

56 [Start]: Set the start address. [End]: Set the end address. [f()…]: The address range of a function can be set by [Start] and [End]. [Outp

57 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

58 [Status]: Selects the status of a bus as the condition. [Don't care]: Detects no bus condition when this box is checked. [Setting]: D

59 3.8.6 Saving the Trace Information in a File Select [Save...] from the popup menu to open the [Save As] file dialog box, which allows the user to

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

61 [Point]: Specifies a single address. [Range]: Specifies an address range. [From]: Enter a single address value or the start value of the addres

62 High: The status of the IRQ signal is high. Low: The status of the IRQ signal is low. [Timestamp]: Sets the time stamp condition. [Don't car

63 3.8.12 Calculating the Difference in Time Stamping Select [Timestamp Difference…] from the popup menu to calculate the time difference between th

iii Contents Hardware Part Section 1 Overview... 1 1.1 No

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

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

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

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

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

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

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

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

72 [Count]: The count-up value used in measurement of the execution count. A break occurs every time the execution count exceeds the count-up value.

73 (3) Start Range To End Range Measurement Figure 3.40 Start Range To End Range Measurement Settings [Range Name]: The name of the range to be m

iv Debugger Part Section 1 Overview ...1 Section 2 Prepar

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

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

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

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

78 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

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

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

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

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

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

v 3.8.1 Opening the [Trace] Window ... 48 3.8.2 Acquiring Trace Informa

84 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

85 4.3 Downloading the Tutorial Program 4.3.1 Downloading the Tutorial Program Download the object program to be debugged. • Select [Download modu

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

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

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

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

90 Figure 4.8 [Editor] Window (Break Status)

91 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

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

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

vi 4.16.2 Displaying Trace Information by the Trace Stop Function... 115 4.16.3 Displaying Trace Information by the

94 4.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] wi

95 4.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 c

96 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

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

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

99 4.12 Stepping Through a Program The High-performance Embedded Workshop provides a range of step menu commands that allow efficient program debug

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

101 4.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

102 4.12.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

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

Hardware Part

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

105 Figure 4.31 [Breakpoint Properties] Dialog Box

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

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

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

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

110 4.15.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

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

112 4.16 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

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

114 (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.15.1, Sof

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

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

117 (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 [

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

119 4.16.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

120 (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 [

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

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

123 4.16.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

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

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

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

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

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

128 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

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

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

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

132

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

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

134 Notes: 1. If the setting in the [Watch] window allows a realtime update of a value by reading the normal data, access types will be different d

135 5.4 Executing Your Program 5.4.1 Step Execution Break conditions are ignored during step execution, but trigger pulses will be output. 5.5 Event

136 5.5.3 On-Emulator Break • A break will occur several cycles after a condition is satisfied. • The address bus and data bus conditions are satis

137 5.6 Trace Functions 5.6.1 Displaying the Trace Information • The same hardware resource is used for acquisition of time stamps and the IRQ sign

138 5.7 Monitor Function The foreground and background colors cannot be changed in some operating systems. 5.8 Performance Analysis Function 5.8.1 E

139 5.9 Profiling Function • If there is no stack information file (extension is ‘.sni’) that is output from the optimizing linkage editor, only the

140 5.11 Tutorial Program 5.11.1 Notes on Operating the Tutorial Program To operate the High-performance Embedded Workshop according to the descript

141 Memory map for on-chip ROM invalid modeH'00000000H'001FFFFFH'00000000H'0001FFFFH'00100000H'0011FFFFH'00120000H

142 H'00100000H'001FFFFFH'00000000H'000FFFFFH'00200000H'0021FFFFH'00300000H'0031FFFFH'00320000H'003

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

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

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

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

146

147 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

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

149 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

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

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

152 Table B.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function 31 DEFAULT_OBJECT_ FORMAT DO Sets the def

153 Table B.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function 68 PINSEL PSL Displays the current sett

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

154 Table B.1 High-performance Embedded Workshop Commands (cont) No. Command Name Abbreviation Function 104 TRACE_FILTER TF Filters trace infor

Renesas Microcomputer Development Environment System User's ManualSH7046 E6000H EmulatorPublication Date: Rev.

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

SH7046 E6000H Emulator User’s Manual

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

6 1.2.3 Configuration of User System Interface Board The names of the components of the user system interface board are given below. Figure 1.5 C

7 1.3 System Configuration The emulator must be connected to a host computer (via the selected PC interface board). 1.3.1 System Configuration Using

8 Figure 1.8 System Configuration Using a USB Adapter

9 Section 2 Preparation before Use 2.1 Description on Emulator Usage This section describes the preparation before use of the emulator. Figure 2.1

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

10 2.2 Emulator Connection 2.2.1 Connecting the User System WARNING Always switch OFF the emulator and user system before connecting or discon

11 2.2.2 Connecting the User System Interface Board WARNING Always switch OFF the emulator and user system and check pin numbers on the connect

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

13 2.2.4 Selecting the Clock This emulator supports three types of clock for the target MCU: a crystal oscillator attached on the evaluation chip bo

14 Evaluation chip boardCrystal oscillator terminalsCrystaloscillatorEnlarged viewX1 X2 Figure 2.4 Installing the Crystal Oscillator External

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

16 Figure 2.6 Connecting the Frame Ground 2.2.6 PC Interface Board Specifications For details on the PC interface board, LAN adapter, or USB adap

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 D

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 CKVOHVOLA17 to A0_CSnT1tADtCSD1tCSD2tRSD1tOEtRSD2tACCtRDStRDHtWSD1tWSD2tWRtWDHtWDDtASTw T2_RD (When read)_WRx (When written)Note: tRDH: Specifie

21 HD151015MD3MD2MD1MD0MD3MD2MD1MD0EPM7512AEALVCH16244AEPM7256AEHD151015 EPM7512AEFWP FWPMCU in the emulatorUser system Figure 3.3 User System Inte

22 PA13/TDO/_BREQPA10/TCKPA15/_TRST/_BACKPA12/TDIPA14/TMSPA13/TDO/_BREQ_ASEBRKAK_DBGMD_WDTOVF _WDTOVFPA10/TCKPA15/_TRST/_BACKPA12/TDIPA14/TMSPD4/_AUD

23 LVTH16374LVTH16374EPM7256AEHD151015AHC14 AHC14NMI NMI_RES _RES_HSTBY _HSTBYPVccPVccHD151015HD151015ALVCH16244AEPM7256AEALVTC16244AAHC14 AHC14PVccH

24 PLLVccPLLCAPPLLVssPLLVcLPLLCAPPLLVssVss3VccUPVccUVccVccHD15015 EPM7256AE3 kΩ1 kΩ22 kΩ470 pF1000 pF3VccVccNCNCXTALEXTAL EXTALAVref AVrefXTALNCNCEPM

25 PA (19:17), PA (9:7), PA5, PA2PA (23:20), PA16, PA11, PA6, PA4, PA3, PA1, PA0PA (23:20), PA16, PA11, PA6, PA4, PA3, PA1, PA0PB (9:2)EPM7256AEEPM72

26 PE17PE (21:18), PE (16:14), PE (12:0)PE (21:18), PE (16:14), PE (12:0)PF (15:0), PG (3:0) PF (15:0), PG (3:0)SN74S1053NSPE17VHC244PVccUser systemM

27 3.4 Connecting the Emulator to the User System 3.4.1 Connecting to the User System WARNING Always switch OFF the emulator and user system be

28 Installing IC Socket 1. Installing IC Socket Install the IC socket for each package to the user system. After checking the location of pin 1 on

29 Evaluation chip boardUser system interface boardPin 1IC socketUser systemScrews (M2.0 × 12 mm) with flat washersSpacer Figure 3.9 Connection Usi

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

30 0.350.65 × 19 = 12.35 ± 0.1+ 0.1- 0.050.65 ± 0.050.65 × 19 = 12.35 ± 0.114.70 max20.50 min0.65 ± 0.05Unit: mm Figure 3.11 Recommended Mount Pad

31 Connection Using the HS7047ECH61H WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABLES.

32 Evaluation chip boardUser system interface boardPin 1IC socketUser systemScrews (M2.6 × 12 mm) with flat washersSpacer Figure 3.12 Connection Us

33 0.50 ± 0.050.30 ± 0.050.50 × 24 = 12.00 ± 0.050.50 × 24 = 12.00 ± 0.0513.80 max17.10 min0.50 ± 0.05Unit: mm Figure 3.14 Recommended Mount Pad Di

34 Connection Using the HS7144ECH61H WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABLES.

35 Evaluation chip boardUser system interface boardPin 1IC socketUser systemScrews (M2.0 × 12 mm) with flat washersSpacer Figure 3.15 Connection Us

36 ×× Figure 3.17 Recommended Mount Pad Dimensions of the User System IC Socket

37 Connection Using the HS7145ECH61H WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABLES.

38 BoardEvaluation chip boardPin 1IC socketUser systemScrews (M2.0 × 10 mm)Spacer Figure 3.18 Connection Using the HS7145ECH61H 33.912.056.611.4

39 Unit: mmTolerance: ±0.10 mm0.500.257.0023.0019.000.5 × 35 = 17.57.02.003 - Ø1.00.5 × 35 = 17.5Ø3.2SL-type0.50 Figure 3.20 Recommended Mount Pad

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

40 Connection Using the Dedicated Connector WARNING Always switch OFF the emulator and user system before connecting or disconnecting any CABL

41 83.0140.0116.0UCN1UCN21212199200199200WD-200P-VF85-NHole for a connector (NTH) × 4Unit: mmTolerance: ±0.1 mm Figure 3.23 Location for Mounting t

42 3.4.2 Pin Arrangement on the User System Interface Connector Table 3.5 lists the pin arrangement on the user system interface connector of HS7046

43 Table 3.5 Pin Arrangement on HS7046EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No. Signal Name 49 N.C. 75 N.C. 50 N.C. 7

44 Table 3.5 Pin Arrangement on HS7046EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No. Signal Name 101 3VCC 127 GND 102 PE5/TI

45 Table 3.5 Pin Arrangement on HS7046EPH60H (cont) User I/F 1 Pin No. Signal Name User I/F 1 Pin No. Signal Name 153 PB0/A16/HTxD0/HTxD1/-/-/

46 Table 3.5 Pin Arrangement on HS7046EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name 1 GND 31 N.C. (SAB1_P) 2 GN

47 Table 3.5 Pin Arrangement on HS7046EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name 61 N.C. (SVID3_N) 90 N.C.

48 Table 3.5 Pin Arrangement on HS7046EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name 119 N.C. 140 GND 120 AVSS

49 Table 3.5 Pin Arrangement on HS7046EPH60H (cont) User I/F 2 Pin No. Signal Name User I/F 2 Pin No. Signal Name 161 GND 181 GND 162 PG0/AN

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

50 3.4.3 Precautions on Connecting the User System When connecting the evaluation chip board to the user system, note the followings: 1. Secure the

51 3.5 Support of the Target MCU 3.5.1 Memory Space The MCU has a 4-Gbyte memory space in its architecture. On-Chip ROM Area • Access to the on-chi

52 3.5.2 Low Power-Consumption Mode (Sleep, Software Standby, and Hardware Standby) For reduced power consumption, the MCU has sleep, software stand

53 3.5.7 A/D Converter The A/D converter has AVcc, AVss, Avref, and _ADTRG pins as well as the analog input pins. As the A/D converter operates with

54 3.5.9 Pin Functions This emulator supports the extended functions that are not included in the product MCU. Therefore, the pin status, which does

55 3.5.10 Different Initial Values of Registers in the Emulator Note that the emulator initializes some general or control registers whenever the sy

56

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

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

59 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

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 4.3 Diagnostic Test Procedure Using the Diagnostic Program Insert the CD-R (HS7046EPH60SR supplied with the E6000H) into the CD-ROM drive of the

61 The following messages are displayed during the test. There are 14 steps in this test (when a PCI interface board is used, the time for the test w

62 3. Evaluation Board Access 01) Registers Initial Value Check ...OK 02) Registers Write/Verify ...

63 7. G/A Break Function 01) Address Condition ...OK 02) Data Condition ...

64 12. Combination 01) B to A Time Measurement( FPGA counter ) ...OK 02) B to A Time Measurement( G

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

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

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

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