Renesas HS0005KCU04HE, SuperH E10A-USB User Manual

REJ10J1766-0100

SuperHTM Family E10A-USB Multi-core Emulator

Renesas Microcomputer Development Environment System

User’s Manual

SuperH™ Family E10A-USB HS0005KCU04HE

Rev.1.00
Revision Date: Nov. 26, 2007

Notes regarding these materials

1. This document is provided for reference purposes only so that Renesas customers may select the appropriate
Renesas products for their use. Renesas neither makes warranties or representations with respect to the
accuracy or completeness of the information contained in this document nor grants any license to any
intellectual property rights or any other rights of Renesas or any third party with respect to the information in
this document.

2. Renesas shall have no liability for damages or infringement of any intellectual property or other rights arising
out of the use of any information in this document, including, but not limited to, product data, diagrams, charts,
programs, algorithms, and application circuit examples.

3. You should not use the products or the technology described in this document for the purpose of military
applications such as the development of weapons of mass destruction or for the purpose of any other military
use. When exporting the products or technology described herein, you should follow the applicable export
control laws and regulations, and procedures required by such laws and regulations.

4. All information included in this document such as product data, diagrams, charts, programs, algorithms, and
application circuit examples, is current as of the date this document is issued. Such information, however, is
subject to change without any prior notice. Before purchasing or using any Renesas products listed in this
document, please confirm the latest product information with a Renesas sales office. Also, please pay regular
and careful attention to additional and different information to be disclosed by Renesas such as that disclosed
through our website. (http://www.renesas.com )

5. Renesas has used reasonable care in compiling the information included in this document, but Renesas
assumes no liability whatsoever for any damages incurred as a result of errors or omissions in the information
included in this document.

6. When using or otherwise relying on the information in this document, you should evaluate the information in
light of the total system before deciding about the applicability of such information to the intended application.
Renesas makes no representations, warranties or guaranties regarding the suitability of its products for any
particular application and specifically disclaims any liability arising out of the application and use of the
information in this document or Renesas products.

7. With the exception of products specified by Renesas as suitable for automobile applications, Renesas
products are not designed, manufactured or tested for applications or otherwise in systems the failure or
malfunction of which may cause a direct threat to human life or create a risk of human injury or which require
especially high quality and reliability such as safety systems, or equipment or systems for transportation and
traffic, healthcare, combustion control, aerospace and aeronautics, nuclear power, or undersea communication
transmission. If you are considering the use of our products for such purposes, please contact a Renesas
sales office beforehand. Renesas shall have no liability for damages arising out of the uses set forth above.

8. Notwithstanding the preceding paragraph, you should not use Renesas products for the purposes listed below:
(1) artificial life support devices or systems
(2) surgical implantations
(3) healthcare intervention (e.g., excision, administration of medication, etc.)
(4) any other purposes that pose a direct threat to human life
Renesas shall have no liability for damages arising out of the uses set forth in the above and purchasers who
elect to use Renesas products in any of the foregoing applications shall indemnify and hold harmless Renesas
Technology Corp., its affiliated companies and their officers, directors, and employees against any and all
damages arising out of such applications.

9. You should use the products described herein within the range specified by Renesas, especially with respect
to the maximum rating, operating supply voltage range, movement power voltage range, heat radiation
characteristics, installation and other product characteristics. Renesas shall have no liability for malfunctions or
damages arising out of the use of Renesas products beyond such specified ranges.

10. Although Renesas endeavors to improve the quality and reliability of its products, IC products have specific
characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use
conditions. Please be sure to implement safety measures to guard against the possibility of physical injury, and
injury or damage caused by fire in the event of the failure of a Renesas product, such as safety design for
hardware and software including but not limited to redundancy, fire control and malfunction prevention,
appropriate treatment for aging degradation or any other applicable measures. Among others, since the
evaluation of microcomputer software alone is very difficult, please evaluate the safety of the final products or
system manufactured by you.

11. In case Renesas products listed in this document are detached from the products to which the Renesas
products are attached or affixed, the risk of accident such as swallowing by infants and small children is very
high. You should implement safety measures so that Renesas products may not be easily detached from your
products. Renesas shall have no liability for damages arising out of such detachment.

12. This document may not be reproduced or duplicated, in any form, in whole or in part, without prior written
approval from Renesas.

13. Please contact a Renesas sales office if you have any questions regarding the information contained in this
document, Renesas semiconductor products, or if you have any other inquiries.

IMPORTANT INFORMATION

READ FIRST

• READ this user's manual before using this emulator product.

• KEEP the user's manual handy for future reference.

Do not attempt to use the emulator product until you fully understand its mechanism.

Emulator Product:

Throughout this document, the term "emulator product" shall be defined as the following
products produced only by Renesas Technology Corp. excluding all subsidiary products.

• Emulator

• User system interface cable

The user system or a host computer is not included in this definition.

Purpose of the Emulator Product:

This emulator product is a software and hardware development tool for systems employing the
Renesas microcomputer. This emulator product must only be used for the above purpose.

Limited Applications:

This emulator product is not authorized for use in MEDICAL, atomic energy, aeronautical or
space technology applications without consent of the appropriate officer of a Renesas sales
company. Such use includes, but is not limited to, use in life support systems. Buyers of this
emulator product must notify the relevant Renesas sales offices before planning to use the product
in such applications.

Improvement Policy:

Renesas Technology Corp. (including its subsidiaries, hereafter collectively referred to as
Renesas) pursues a policy of continuing improvement in design, performance, and safety of the
emulator product. Renesas reserves the right to change, wholly or partially, the specifications,
design, user's manual, and other documentation at any time without notice.

Target User of the Emulator Product:

This emulator product should only be used by those who have carefully read and thoroughly
understood the information and restrictions contained in the user's manual. Do not attempt to use
the emulator product until you fully understand its mechanism.

It is highly recommended that first-time users be instructed by users that are well versed in the
operation of the emulator product.

Rev. 1.00 Nov. 26, 2007 Page I of VI

REJ10J1766-0100

LIMITED WARRANTY

Renesas warrants its emulator products to be manufactured in
accordance with published specifications and free from defects in
material and/or workmanship. Renesas, at its option, will replace any
emulator products returned intact to the factory, transportation charges
prepaid, which Renesas, upon inspection, shall determine to be defective
in material and/or workmanship. The foregoing shall constitute the sole
remedy for any breach of Renesas’ warranty. See the Renesas warranty
booklet for details on the warranty period. This warranty extends only
to you, the original Purchaser. It is not transferable to anyone who
subsequently purchases the emulator product from you. Renesas is not
liable for any claim made by a third party or made by you for a third
party.

DISCLAIMER

RENESAS MAKES NO WARRANTIES, EITHER EXPRESS OR
IMPLIED, ORAL OR WRITTEN, EXCEPT AS PROVIDED
HEREIN, INCLUDING WITHOUT LIMITATION THEREOF,
WARRANTIES AS TO MARKETABILITY, MERCHANTABILITY,
FITNESS FOR ANY PARTICULAR PURPOSE OR USE, OR
AGAINST INFRINGEMENT OF ANY PATENT. IN NO EVENT
SHALL RENESAS BE LIABLE FOR ANY DIRECT, INCIDENTAL
OR CONSEQUENTIAL DAMAGES OF ANY NATURE, OR
LOSSES OR EXPENSES RESULTING FROM ANY DEFECTIVE
EMULATOR PRODUCT, THE USE OF ANY EMULATOR
PRODUCT, OR ITS DOCUMENTATION, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES. EXCEPT AS
EXPRESSLY STATED OTHERWISE IN THIS WARRANTY,
THIS EMULATOR PRODUCT IS SOLD "AS IS ", AND YOU
MUST ASSUME ALL RISK FOR THE USE AND RESULTS
OBTAINED FROM THE EMULATOR PRODUCT.

Rev. 1.00 Nov. 26, 2007 Page II of VI

REJ10J1766-0100

State Law:

Some states do not allow the exclusion or limitation of implied warranties or liability for
incidental or consequential damages, so the above limitation or exclusion may not apply to you.
This warranty gives you specific legal rights, and you may have other rights which may vary from
state to state.

The Warranty is Void in the Following Cases:

Renesas shall have no liability or legal responsibility for any problems caused by misuse,
abuse, misapplication, neglect, improper handling, installation, repair or modifications of the
emulator product without Renesas’ prior written consent or any problems caused by the user
system.

All Rights Reserved:

This user's manual and emulator product are copyrighted and all rights are reserved by
Renesas. No part of this user's manual, all or part, may be reproduced or duplicated in any form,
in hard-copy or machine-readable form, by any means available without Renesas’ prior written
consent.

Other Important Things to Keep in Mind:

1. Circuitry and other examples described herein are meant merely to indicate the characteristics
and performance of Renesas’ semiconductor products. Renesas assumes no responsibility for
any intellectual property claims or other problems that may result from applications based on
the examples described herein.

2. No license is granted by implication or otherwise under any patents or other rights of any third
party or Renesas.

Figures:

Some figures in this user's manual may show items different from your actual system.

Device names:

This user’s manual uses SHxxxx as an example of the device names.

Limited Anticipation of Danger:

Renesas cannot anticipate every possible circumstance that might involve a potential hazard.
The warnings in this user's manual and on the emulator product are therefore not all inclusive.
Therefore, you must use the emulator product safely at your own risk.

Rev. 1.00 Nov. 26, 2007 Page III of VI

REJ10J1766-0100

SAFETY PAGE

READ FIRST

• READ this user's manual before using this emulator product.

• KEEP the user's manual handy for future reference.

Do not attempt to use the emulator product until you fully understand its mechanism.

DEFINITION OF SIGNAL WORDS

This is the safety alert symbol. It is used to alert you to potential personal

injury hazards. Obey all safety messages that follow this symbol to avoid

possible injury or death.

DANGER

avoided, will result in death or serious injury.

WARNING

avoided, could result in death or serious injury.

CAUTION

avoided, may result in minor or moderate injury.

CAUTION

potentially hazardous situation which, if not avoided, may result
in property damage.

DANGER indicates an imminently hazardous situation which, if not

WARNING indicates a potentially hazardous situation which, if not

CAUTION indicates a potentially hazardous situation which, if not

CAUTION used without the safety alert symbol indicates a

NOTE emphasizes essential information.

Rev. 1.00 Nov. 26, 2007 Page IV of VI

REJ10J1766-0100

WARNING

Observe the precautions listed below. Failure to do so
will result in a FIRE HAZARD and will damage the user
system and the emulator product or will result in
PERSONAL INJURY. The USER PROGRAM will be
LOST.

1. Do not repair or remodel the emulator product by
yourself for electric shock prevention and quality
assurance.

2. Always switch OFF the host computer and user system
before connecting or disconnecting any CABLES or
PARTS.

3. Connect the connectors in the user system and in the

user interface cable by confirming the correct direction.

Rev. 1.00 Nov. 26, 2007 Page V of VI

REJ10J1766-0100

Warnings on Emulator Usage

Be sure to read and understand the warnings below before using this emulator. Note that these are
the main warnings, not the complete list.

WARNING

Always switch OFF the host computer and user system
before connecting or disconnecting any CABLES or PARTS.
Failure to do so will result in a FIRE HAZARD and will
damage the user system and the emulator product or will
result in PERSONAL INJURY. The USER PROGRAM will be
LOST.

CAUTION

Place the host computer and user system so that no
cable is bent or twisted. A bent or twisted cable will impose
stress on the user interface leading to connection or contact
failure.
Make sure that the host computer and the user system
are placed in a secure position so that they do not move
during use nor impose stress on the user interface.

Rev. 1.00 Nov. 26, 2007 Page VI of VI

REJ10J1766-0100

Introduction

The High-performance Embedded Workshop is a powerful development environment for
embedded applications targeted at Renesas microcontrollers. The main features are:

• A configurable build engine that allows you to set-up compiler, assembler and linker options

via an easy to use interface.

• An integrated text editor with user customizable syntax coloring to improve code readability.

• A configurable environment to run your own tools.

• An integrated debugger which allows you to build and debug in the same application.

• Version control support.

The High-performance Embedded Workshop has been designed with two key aims; firstly to
provide you, the user, with a set of powerful development tools and, secondly, to unify and present
them in a way that is easy to use.

Rev. 1.00 Nov. 26, 2007 Page i of x

REJ10J1766-0100

About This Manual

This manual describes preparation before using the emulator, emulator functions, debugging
functions specific to the emulator, tutorial, and emulator's hardware and software specifications.

Refer to the High-performance Embedded Workshop User's Manual for details on the information
on the basic usage of the High-performance Embedded Workshop, customization of the
environment, build functions, and debugging functions common to each High-performance
Embedded Workshop product.

This manual does not intend to explain how to write C/C++ or assembly language programs, how
to use any particular operating system or how best to tailor code for the individual devices. These
issues are left to the respective manuals.

Microsoft

®

and Windows® are registered trademarks of Microsoft Corporation.

Visual SourceSafe is a trademark of Microsoft Corporation.

IBM is a registered trademark of International Business Machines Corporation.

All brand or product names used in this manual are trademarks or registered trademarks of their
respective companies or organizations.

Document Conventions

This manual uses the following typographic conventions:

Table 1 Typographic Conventions

Convention Meaning

[Menu->Menu Option] Bold text with ‘->’ is used to indicate menu options

(for example, [File->Save As...]).

FILENAME.C Uppercase names are used to indicate filenames.

“enter this string” Used to indicate text that must be entered (excluding the “” quotes).

Key + Key Used to indicate required key presses. For example, CTRL+N means

press the CTRL key and then, whilst holding the CTRL key down,
press the N key.

(The “how to” symbol)

When this symbol is used, it is always located in the left hand margin.
It indicates that the text to its immediate right is describing “how to”
do something.

Rev. 1.00 Nov. 26, 2007 Page ii of x

REJ10J1766-0100

User Registration

When you have purchased the emulator represented in this user's manual, be sure to register it. As
the H/W Tool Customer Registration Sheet is included with this product, fill it in and send the
same contents to the following address by an email. Your registered information is used for only
after-sale services, and not for any other purposes. Without user registration, you will not be able
to receive maintenance services such as a notification of field changes or trouble information. So
be sure to carry out the user registration.

For more information about user registration, send an email to the following address.

[e-mail]

Rev. 1.00 Nov. 26, 2007 Page iii of x

REJ10J1766-0100

Rev. 1.00 Nov. 26, 2007 Page iv of x

REJ10J1766-0100

Contents

Section 1 Overview..............................................................................................1

1.1 Warnings ........................................................................................................................... 3

1.2 Environmental Conditions ................................................................................................4

1.3 Components ......................................................................................................................5

Section 2 Emulator Functions..............................................................................7

2.1 Overview........................................................................................................................... 7

2.2 Trace Functions.................................................................................................................10

2.2.1 Internal Trace Function........................................................................................ 10

2.2.2 AUD Trace Function............................................................................................10

2.2.3 Memory Output Function of Trace Data.............................................................. 14

2.2.4 Useful Functions of the [Trace] Window.............................................................14

2.3 Break Function..................................................................................................................15

2.4 Performance Measurement Function ................................................................................15

2.4.1 Function for Measuring the Number of Cycles from Point to Point ....................15

2.5 Memory Access Functions................................................................................................ 16

2.6 Stack Trace Function ........................................................................................................ 18

2.7 User-interrupt Open Function during User Program Break .............................................. 18

2.8 Online Help .......................................................................................................................18

Section 3 Preparation before Use.........................................................................19

3.1 Emulator Preparation ........................................................................................................19

3.2 Emulator Hardware Configuration.................................................................................... 20

3.3 CD-R ................................................................................................................................. 25

3.4 Installing Emulator’s Software ......................................................................................... 25

3.5 Connecting the Emulator to the Host Computer ............................................................... 26

3.6 Connecting the Emulator to the User System ...................................................................28

3.7 Connecting System Ground ..............................................................................................33

3.8 Interface Circuits in the Emulator ..................................................................................... 34

3.9 Setting up the Emulator..................................................................................................... 37

3.10 System Check....................................................................................................................38

3.11 Uninstalling the Emulator’s Software............................................................................... 50

Section 4 Preparations for Debugging .................................................................55

Rev. 1.00 Nov. 26, 2007 Page v of x

REJ10J1766-0100

4.1

Method for Activating High-performance Embedded Workshop..................................... 55

4.1.1 Creating the New Workspace (Toolchain Not Used)...........................................56

4.1.2 Creating the New Workspace (Toolchain Used) ................................................. 60

4.1.3 Selecting an Existing Workspace......................................................................... 65

4.2 Setting at Emulator Activation.......................................................................................... 67

4.2.1 Setting at Emulator Activation............................................................................. 67

4.2.2 Downloading a Program ...................................................................................... 69

4.3 Debug Sessions ................................................................................................................. 70

4.3.1 Selecting a Session .............................................................................................. 70

4.3.2 Adding and Removing Sessions .......................................................................... 71

4.3.3 Saving Session Information................................................................................. 74

4.4 Connecting the Emulator .................................................................................................. 75

4.5 Reconnecting the Emulator............................................................................................... 76

4.6 Ending the Emulator .........................................................................................................77

Section 5 Debugging ...........................................................................................79

5.1 Setting the Environment for Emulation ............................................................................79

5.1.1 Opening the [Configuration] Dialog Box ............................................................79

5.1.2 [General] Page ..................................................................................................... 79

5.1.3 Downloading to the Flash Memory ..................................................................... 84

5.2 Downloading a Program ...................................................................................................87

5.2.1 Downloading a Program ...................................................................................... 87

5.2.2 Viewing the Source Code .................................................................................... 87

5.2.3 Viewing the Assembly-Language Code .............................................................. 90

5.2.4 Modifying the Assembly-Language Code........................................................... 91

5.2.5 Viewing a Specific Address................................................................................. 92

5.2.6 Viewing the Current Program Counter Address.................................................. 92

5.3 Displaying Memory Contents in Realtime........................................................................ 93

5.3.1 Opening the [Monitor] Window .......................................................................... 93

5.3.2 Changing the Monitor Settings............................................................................ 96

5.3.3 Temporarily Stopping Update of the Monitor .....................................................96

5.3.4 Deleting the Monitor Settings.............................................................................. 96

5.3.5 Monitoring Variables........................................................................................... 97

5.3.6 Hiding the [Monitor] Window............................................................................. 97

5.3.7 Managing the [Monitor] Window........................................................................ 98

5.4 Viewing the Current Status ............................................................................................... 99

5.5 Using the Event Points...................................................................................................... 100

5.5.1 PC Breakpoints .................................................................................................... 100

5.5.2 Event Conditions .................................................................................................100

5.5.3 Opening the [Event] Window.............................................................................. 101

Rev. 1.00 Nov. 26, 2007 Page vi of x

REJ10J1766-0100

5.5.4 Setting PC Breakpoints........................................................................................ 101

5.5.5 Add ......................................................................................................................102

5.5.6 Edit....................................................................................................................... 102

5.5.7 Enable .................................................................................................................. 102

5.5.8 Disable ................................................................................................................. 102

5.5.9 Delete................................................................................................................... 102

5.5.10 Delete All ............................................................................................................. 103

5.5.11 Go to Source ........................................................................................................103

5.5.12 [Breakpoint] Dialog Box...................................................................................... 103

5.5.13 Setting Break Conditions .....................................................................................104

5.5.14 Edit....................................................................................................................... 105

5.5.15 Enable ..................................................................................................................105

5.5.16 Disable .................................................................................................................105

5.5.17 Delete ................................................................................................................... 105

5.5.18 Delete All ............................................................................................................. 105

5.5.19 Go to Source ........................................................................................................105

5.5.20 Sequential Conditions .......................................................................................... 106

5.5.21 Editing Break Conditions..................................................................................... 106

5.5.22 Modifying Break Conditions ...............................................................................106

5.5.23 Enabling Break Conditions .................................................................................. 106

5.5.24 Disabling Break Conditions ................................................................................. 106

5.5.25 Deleting Break Conditions................................................................................... 106

5.5.26 Deleting All Break Conditions............................................................................. 106

5.5.27 Viewing the Source Line for Break Conditions ................................................... 107

5.6 Viewing the Trace Information ......................................................................................... 107

5.6.1 Opening the [Trace] Window .............................................................................. 107

5.6.2 Acquiring Trace Information ............................................................................... 107

5.6.3 Specifying Trace Acquisition Conditions............................................................ 111

5.6.4 Searching for a Trace Record...............................................................................124

5.6.5 Clearing the Trace Information............................................................................ 131

5.6.6 Saving the Trace Information in a File ................................................................131

5.6.7 Viewing the [Editor] Window..............................................................................131

5.6.8 Trimming the Source ........................................................................................... 131

5.6.9 Temporarily Stopping Trace Acquisition.............................................................132

5.6.10 Extracting Records from the Acquired Information ............................................132

5.6.11 Analyzing Statistical Information ........................................................................ 139

5.6.12 Extracting Function Calls from the Acquired Trace Information ........................ 141

5.7 Analyzing Performance..................................................................................................... 142

5.7.1 Opening the [Performance Analysis] Window ....................................................142

5.7.2 Setting Conditions for Measurement ................................................................... 143

Rev. 1.00 Nov. 26, 2007 Page vii of x

REJ10J1766-0100

5.7.3

Starting Performance Data Acquisition ...............................................................143

5.7.4 Deleting a Measurement Condition ..................................................................... 143

5.7.5 Deleting All Measurement Conditions ................................................................144

5.8 Synchronizing Multiple Debugging Platforms ................................................................. 144

5.8.1 Distinguishing Two Emulators ............................................................................ 145

Section 6 Tutorial ................................................................................................147

6.1 Introduction....................................................................................................................... 147

6.2 Running the High-performance Embedded Workshop..................................................... 148

6.3 Setting up the Emulator .................................................................................................... 148

6.4 Setting the [Configuration] Dialog Box............................................................................ 149

6.5 Checking the Operation of the Target Memory for Downloading.................................... 150

6.6 Downloading the Tutorial Program .................................................................................. 152

6.6.1 Downloading the Tutorial Program ..................................................................... 152

6.6.2 Displaying the Source Program ........................................................................... 153

6.7 Setting a PC Breakpoint.................................................................................................... 155

6.8 Setting Registers ............................................................................................................... 157

6.9 Executing the Program...................................................................................................... 159

6.10 Reviewing Breakpoints..................................................................................................... 162

6.11 Referring to Symbols ........................................................................................................ 163

6.12 Viewing Memory.............................................................................................................. 164

6.13 Watching Variables........................................................................................................... 165

6.14 Displaying Local Variables............................................................................................... 168

6.15 Stepping Through a Program............................................................................................ 169

6.15.1 Executing [Step In] Command............................................................................. 169

6.15.2 Executing [Step Out] Command .......................................................................... 171

6.15.3 Executing [Step Over] Command ........................................................................ 173

6.16 Forced Breaking of Program Executions.......................................................................... 175

6.17 Break Function.................................................................................................................. 176

6.17.1 PC Break Function............................................................................................... 176

6.18 Hardware Break Function ................................................................................................. 180

6.18.1 Setting the Sequential Break Condition ............................................................... 186

6.19 Trace Functions................................................................................................................. 190

6.19.1 Displaying the [Trace] Window........................................................................... 190

6.19.2 Internal Trace Function........................................................................................ 190

6.19.3 AUD Trace Function ........................................................................................... 192

6.20 Stack Trace Function ........................................................................................................196

6.21 Performance Measurement Function ................................................................................ 198

6.21.1 Performance Measurement Function ...................................................................198

6.22 Download Function to the Flash Memory Area................................................................ 200

Rev. 1.00 Nov. 26, 2007 Page viii of x

REJ10J1766-0100

6.23 What Next? .......................................................................................................................207

Section 7 Maintenance and Guarantee.................................................................209

7.1 User Registration .............................................................................................................. 209

7.2 Maintenance ...................................................................................................................... 209

7.3 Guarantee .......................................................................................................................... 209

7.4 Repair Provisions .............................................................................................................. 210

7.4.1 Repair with Extra-Charge .................................................................................... 210

7.4.2 Replacement with Extra-Charge .......................................................................... 210

7.4.3 Expiration of the Repair Period ...........................................................................210

7.4.4 Transportation Fees at Sending Your Product for Repair.................................... 210

7.5 How to Make a Request for Repair................................................................................... 211

Appendix A Troubleshooting ............................................................................213

Appendix B Menus ............................................................................................215

Appendix C Command-Line Functions.............................................................219

Appendix D Notes on High-performance Embedded Workshop ......................221

Appendix E Diagnostic Test Procedure.............................................................225

Appendix F Repair Request Sheet .....................................................................227

Rev. 1.00 Nov. 26, 2007 Page ix of x

REJ10J1766-0100

Rev. 1.00 Nov. 26, 2007 Page x of x

REJ10J1766-0100

Section 1 Overview

Section 1 Overview

The High-performance Embedded Workshop provides a graphical user interface that eases the
development and debugging of applications written in the C/C++ programming languages or
assembly language for Renesas microcomputers. Its aim is to provide a powerful yet intuitive way
of accessing, observing and modifying the debugging platform on which the application is
running.

The E10A-USB Multi emulator (hereafter referred to as the emulator) is a support tool for
developing the hardware and software of application systems running on Renesas original
microcomputers.

The main unit of the emulator is connected, through the dedicated debugging interface, to the user
system. The user system can be debugged under the conditions similar to the actual application
conditions. The emulator enables debugging anywhere indoors or out. The host computer for
controlling the emulator must be an IBM PC compatible machine with USB 1.1/2.0 (Full-Speed).

Figure 1.1 shows the system configuration using the emulator.

Host computer (with USB interface)

CD-R

High-performance
Embedded Workshop

Connected to
the USB connector

Connected to
the USB connector

USB cable (1.5 m)

E10A

E10A-USB Multi emulator

User system connector

User system interface cable

R

ENESAS

/F

USB I

(38 pins or 14 pins)

Multi-core microcomputer

User system

Figure 1.1 System Configuration with the Emulator

Rev. 1.00 Nov. 26, 2007 Page 1 of 230

REJ10J1766-0100

Section 1 Overview

The emulator provides the following features:

 Excellent cost-performance emulator

Compactness and connection to the USB are implemented.

 Realtime emulation

Realtime emulation of the user system is enabled at the maximum operating frequency of the
CPU.

 Excellent operability

Using the High-performance Embedded Workshop on the Microsoft
Microsoft

®

Windows® XP operating system enables user program debugging using a pointing

®

Windows® 2000, or

device such as a mouse. The High-performance Embedded Workshop enables high-speed
downloading of load module files.

 Various debugging functions

Various break and trace functions enable efficient debugging. Breakpoints and break
conditions can be set by the specific window, trace information can be displayed on a window,
and command-line functions can be used.

 Debugging of the user system in the final development stage

The user system can be debugged under conditions similar to the actual application conditions.

 Compact debugging environment

When the emulator is used, a laptop computer can be used as a host computer, creating a
debugging environment in any place.

 AUD trace function*

The AUD trace function enables realtime trace.

Note: The AUD is an abbreviation of the Advanced User Debugger. Support for the AUD varies

with the product.

Rev. 1.00 Nov. 26, 2007 Page 2 of 230

REJ10J1766-0100

1.1 Warnings

Section 1 Overview

CAUTION

READ the following warnings before using the emulator
product. Incorrect operation will damage the user system and
the emulator product. The USER PROGRAM will be LOST.

1. Check all components against the component list after unpacking the emulator.

2. Never place heavy objects on the casing.

3. Protect the emulator from excessive impacts and stresses. For details, refer to section 1.2,
Environmental Conditions.

4. When moving the host computer or user system, take care not to vibrate or damage it.

5. After connecting the cable, check that it is connected correctly. For details, refer to section 3,
Preparation before Use.

6. Supply power to the connected equipment after connecting all cables. Cables must not be
connected or removed while the power is on.

Rev. 1.00 Nov. 26, 2007 Page 3 of 230

REJ10J1766-0100

Section 1 Overview

1.2 Environmental Conditions

CAUTION

Observe the conditions listed in tables 1.1 and 1.2 when
using the emulator. Failure to do so will cause illegal
operation in the user system, the emulator product, and the
user program.

Table 1.1 Environmental Conditions

Item Specifications

Temperature

Humidity

Vibration

Ambient gases No corrosive gases may be present

Operating: +10°C to +35°C
Storage: –10°C to +50°C

Operating: 35% RH to 80% RH, no condensation
Storage: 35% RH to 80% RH, no condensation

Operating: 2.45 m/s
Storage: 4.9 m/s
Transportation: 14.7 m/s

2

max.

2

max.

2

max.

Rev. 1.00 Nov. 26, 2007 Page 4 of 230

REJ10J1766-0100

Section 1 Overview

Table 1.2 lists the acceptable operating environments.

Table 1.2 Operating Environments

Item Description

Host computer Built-in Pentium® III or higher-performance CPU (1 GHz or higher

recommended); IBM PC or compatible machine with USB 1.1/2.0 (Full­Speed).

Operating system Windows® 2000 or Windows® XP

Minimum memory
capacity

Hard-disk capacity Installation disk capacity: 600 Mbytes or more. (Prepare an area at

Pointing device such as
mouse

Display Monitor resolution: 1024 x 768 or higher

Power voltage 5.0 ± 0.25 V (USB-bus power type)

Current consumption HS0005KCU04H: 500 mA (max.)

CD-ROM drive Required to install the High-performance Embedded Workshop for the

128 Mbytes or more (512 Mbytes recommended)

least double the memory capacity (four-times or more recommended)
as the swap area.)

Connectable to the host computer; compatible with Windows® 2000 or
Windows

emulator or refer to the emulator user’s manual.

®

XP.

1.3 Components

Check that all of the components are present when unpacking the product. For details on the
emulator components, refer to section 1.1 in the additional document, Supplementary Information
on Using the SHxxxx. If all of the components are not present, contact your nearest Renesas sales
office or contact center ([e-mail]).

Rev. 1.00 Nov. 26, 2007 Page 5 of 230

REJ10J1766-0100

Section 2 Emulator Functions

Rev. 1.00 Nov. 26, 2007 Page 6 of 230

REJ10J1766-0100

Section 2 Emulator Functions

Section 2 Emulator Functions

This section describes the emulator functions. They differ according to the device supported by
the emulator. For the usage of each function, refer to section 6, Tutorial.

2.1 Overview

Table 2.1 gives a functional overview of the emulator.

For details on the functions of each product, refer to the online help.

Rev. 1.00 Nov. 26, 2007 Page 7 of 230

REJ10J1766-0100

Section 2 Emulator Functions

Table 2.1 Emulator Functions

No. Item Function

1 User program execution

function

2 Reset function

3 Trace functions

4 Break functions

 Executes a program with the operating frequency within a

range guaranteed by devices.

 Reset emulation
 Step functions:

Single step (one step: one instruction)
Source-level step (one step: one-line source)
Step over (a break did not occur in a subroutine)
Step out (when the PC points to a location within a
subroutine, execution continues until it returns to the calling
function)

 Synchronized functions:

Synchronized execution functions.(Execution at the same

time with synchronizing CPU0 and CPU1.)

Synchronized step functions. (All of the CPUs execute with

synchronizing the one of stepping for the CPU.)

Synchronized break functions. (All of the CPUs break by

synchronizing the one of a break for the CPU.)

 Issues a power-on reset from the High-performance

Embedded Workshop to the device during break.

 Trace function incorporated in the device
 AUD trace:

Branch trace or memory access trace

 Memory output function of trace data
 Hardware break condition (conditions and the number of

conditions differ according to the device)

 PC break condition (255 points)
 Forced break function

Rev. 1.00 Nov. 26, 2007 Page 8 of 230

REJ10J1766-0100

Section 2 Emulator Functions

Table 2.1 Emulator Functions (cont)

No. Item Function

5 Performance

measurement function

6 Memory access functions

7 General/control register

access function

8 Internal I/O register

access function

9 Source-level debugging

function

10 Command line function  Supports command input.

11 Help function  Describes the usage of each function or command syntax

Note: The [IO] window displays the contents defined in [SHxxxx.io]. Editing those contents adds

or deletes the registers to be displayed. For the contents to be described as [SHxxxx.io],
refer to reference 5, I/O File Format, in the High-performance Embedded Workshop V.4.00
User’s Manual.
The following directory contains [SHxxxx.io] (xxxx means the name of emulator device
group.):
<High-performance Embedded Workshop folder>:
\Tools\Renesas\DebugComp\Platform\E10A-USBM\xxxx\IOFiles

 Uses a counter in the device to measure the number of

cycles that passes during point-to-point execution.

 Downloading to RAM
 Downloading to flash memory
 Single-line assembly
 Reverse assembly (disassembly)
 Reading of memory
 Writing to memory
 Automatic updating of a display of selected variables during

user program execution

 Fill
 Search
 Move
 Copy
 Monitor (physical address)
 Reads or writes the general/control registers.

 Reads or writes the internal I/O registers.*

 Various source-level debugging functions.

 Batch processing is enabled when a file is created by

arranging commands in input order.

input from the command line window.

The specific functions of the emulator are described in the next section.

Rev. 1.00 Nov. 26, 2007 Page 9 of 230

REJ10J1766-0100

Section 2 Emulator Functions

2.2 Trace Functions

The emulator has two trace functions.

2.2.1 Internal Trace Function

The branch source and branch destination addresses, mnemonics, operands, and source lines are
displayed. This function uses the trace buffer built into the device.

Notes: 1. The number of branch instructions that can be acquired by a trace differs according to

the product. For the number that can be specified for each product, refer to the online
help.

2. The internal trace function is not supported for all products. For details on the
specifications of each product, refer to the online help.

3. The internal trace function is extended for some products. For details on the
specifications of each product, refer to the online help.

2.2.2 AUD Trace Function

This is the large-capacity trace function that is enabled when the AUD pins are connected to the
emulator. If an event occurs to acquire a trace, trace information is output in realtime from the
AUD pins.

When a set of the branch source and branch destination instructions is one branch, the maximum
amount of information acquired by a trace is 32,767.

(1) Trace acquisition event

The following events can be acquired by the AUD trace function.

(a) Branch generation information

The branch source and branch destination addresses are acquired.

(b) Memory access information within the specified range

Memory access in the specified range can be acquired by trace.

Two memory ranges can be specified for channels A or B. The read, write, or read/write cycle
can be selected as the bus cycle for trace acquisition.

This function is called the window trace function.

Rev. 1.00 Nov. 26, 2007 Page 10 of 230

REJ10J1766-0100

Section 2 Emulator Functions

(c) Software trace

When a specific instruction is executed, the PC value at execution and the contents of one
general register are acquired by trace. Describe the Trace(x) function (x is a variable name) to
be compiled and linked beforehand. For details, refer to the SHC/C++ compiler manual.

When the load module is loaded on the emulator and a valid software trace function is
executed, the PC value that has executed the Trace(x) function, the variable for x, and the
source lines are displayed.

Note: The types of events acquired by a trace differ depending on the product. For details on the

specifications of each product, refer to the online help.

(2) Trace acquisition mode

The AUD trace function has the following modes to acquire a trace.

Table 2.2 shows the AUD trace acquisition mode that can be set in each trace function.

Table 2.2 AUD Trace Acquisition Mode

Type Mode Description

Continuous
trace occurs

Non realtime

Trace buffer
full

Trace stop After the trace buffer becomes full, the trace information is no

Realtime trace When the next branch occurs while the trace information is

being output, all the information may not be output. The user
program can be executed in realtime, but some trace
information will be lost.

When the next branch occurs while the trace information is

trace

Trace continue This function overwrites the latest trace information to store

being output, the CPU stops operations until the information
is output. The user program is not executed in realtime.

the oldest trace information.

longer acquired. The user program is continuously executed.

Rev. 1.00 Nov. 26, 2007 Page 11 of 230

REJ10J1766-0100

Section 2 Emulator Functions

(3) Trace display contents

When the program breaks, the following trace results are displayed in the [Trace] window.

 PTR: The trace-buffer pointer (+0 from the last instruction to have been executed)
 IP: Indicates the number of cycles that have elapsed since the latest trace information was

gathered. For branch instructions, the branch source and destination are counted together as
one.

 Type: Displays the type of trace acquisition information.
 Address: Displays the addresses from which the trace data was acquired.
 Data: Displays the data acquired in the trace. For information without data, displays

‘********’.

 Instruction, Source, Label: Displays the mnemonic of the instruction at the trace acquisition

address, along with the corresponding source code and label information. Double-clicking on
the [Source] column moves the cursor to the corresponding position in the [Editor] window.

The Type, Address, and Data columns have different meanings according to the type of AUD
trace that has been selected.

Table 2.3 [Trace Window] Display Contents

Trace Type Type Column Address Column Data Column

Branch trace BRANCH Branch source address No display

DESTINATION Branch destination address No display

Window trace*1 MEMORY Memory access address Memory access data

Software trace*1 S_TRACE Trace(x) function execution

address

Data lost

CPU wait
generation

Notes: 1. Not displayed in the internal trace.

*1, *2

LOST No display No display

*1, *2

2. According to the device being debugged, there may be no output for the [Lost] or

CPU-WAIT No display No display

[CPU-WAIT] type. In such a case, it is not possible to clarify whether the trace data
was not output in time or the CPU generated a wait state for the output trace data.

Variable x data

Rev. 1.00 Nov. 26, 2007 Page 12 of 230

REJ10J1766-0100

Section 2 Emulator Functions

The following items will be displayed, according to the device to be debugged.

For specifications of the individual products, refer to the additional document, Supplementary
Information on Using the SHxxxx, or the online help.

 PTR: The trace-buffer pointer (+0 from the last instruction to have been executed)
 IP: Indicates the number of cycles that have elapsed since the latest trace information was

gathered. For branch instructions, the branch source and destination are counted together as
one.

 Master: Type of bus master that accessed the memory.
 Type: Displays the type of trace acquisition information.
 Branch Type: Branch type (only displayed for a branch trace)

For an AUD trace, this item is only displayed if the PPC option has been enabled.

 Bus: Displays which bus was accessed.
 R/W: Displays whether the access involved reading or writing.
 Address: Displays the addresses from which the trace data was acquired.
 Data: Displays the data acquired in the trace.
 PPC: Output from a performance counter
 Instruction, Source, Label: Displays the mnemonic of the instruction at the trace acquisition

address, along with the corresponding source code and label information. Double-clicking on
the [Source] column moves the cursor to the corresponding position in the [Editor] window.

The Type, BUS, R/W, Address, and Data columns have different meanings according to the type
of AUD trace that has been selected.

Rev. 1.00 Nov. 26, 2007 Page 13 of 230

REJ10J1766-0100

Section 2 Emulator Functions

Table 2.4 [Trace Window] Display Contents

Trace Type Type Column BUS Column R/W Column Address Column Data Column

*1

Branch trace BRANCH

DESTINATION No display No display Branch destination

Memory-

MEMORY No display Read/write Memory access
range access
trace

Software

S_TRACE No display No display Trace(x) function
trace

System bus

MEMORY No display Read/write Memory access
trace

Data lost*2 LOST No display No display No display No display

CPU wait
generation

CPU-WAIT No display No display No display No display

*2

Notes: 1. Not displayed when the PPC option is in use.

2. According to the device being debugged, there may be no output for the [Lost] or

[CPU-WAIT] type. In such a case, it is not possible to clarify whether the trace data
was not output in time or the CPU generated a wait state for the output trace data.

No display No display Branch source

address

*1

address

address

execution address

address

No display

No display

Memory
access data

Variable x
data

Memory
access data
(write only)

*1

*1

2.2.3 Memory Output Function of Trace Data

In some devices to be debugged, trace data can be written to the specified memory range. The
data is read from the memory range written in the [Trace] window and the result is then displayed.

Note: Do not specify the program area as the memory in the specified range is overwritten.

2.2.4 Useful Functions of the [Trace] Window

The trace window provides the following useful functions.

(1) Searches for the specified data.

(2) Extracts the specified data.

(3) Filters and displays again the specified data.

(4) Supplements the information from the branch destination address to the next branch source

address.

For the usage of those functions, refer to section 5.6, Viewing the Trace Information.

Rev. 1.00 Nov. 26, 2007 Page 14 of 230

REJ10J1766-0100

Section 2 Emulator Functions

(5) Changes the trace settings during user program execution.

In some devices to be debugged, trace settings can be changed during user program execution.
For details on the specifications of each product, refer to the online help.

2.3 Break Function

The emulator has the following three break functions.

(1) Hardware break function

Uses a break controller incorporated in the device.

The access address, instruction fetch address, data, or bus cycle condition can be set. The
logical address is the address condition.

This function can be also set from the [Event] column in the [Editor] or [Disassembly] window.
For the setting, refer to section 5.2, Downloading a Program.

Note: In some devices to be debugged, hardware break settings can be changed during user

program execution. For details on the specifications of each product, refer to the online
help.

(2) PC break function (BREAKPOINT)

Breaks when the dedicated instruction at the specified address that has been replaced is
executed. This function cannot be set at a place other than RAM or internal flash memory area
since a memory write occurs.

It can also be set when the [S/W breakpoint] column for the line to be set is double-clicked in
the [Editor] or [Disassembly] window.

(3) Forced break function

Forcibly breaks the user program.

2.4 Performance Measurement Function

The emulator has a following performance measurement function.

2.4.1 Function for Measuring the Number of Cycles from Point to Point

This function applies a counter in the device to measure the number of cycles from one specified
condition being satisfied until a next specified condition is satisfied.

Not only the number of cycles but also various items such as the number of cache misses or of
TLB misses can be measured according to the supported devices.

Rev. 1.00 Nov. 26, 2007 Page 15 of 230

REJ10J1766-0100

Section 2 Emulator Functions

This function is hereafter called the performance measurement function or PA1.

Note: Items to be measured differ according to the product and some products do not support

this function. For details on the specifications of each product, refer to the online help.

2.5 Memory Access Functions

The emulator has the following memory access functions.

(1) Memory read/write function

[Memory] window: The memory contents are displayed in the window. Only the amount

specified when the [Memory] window is opened can be read. Since there is
no cache in the emulator, read cycles are always generated. If the memory is
written in the [Memory] window, read cycles in the range displayed in the
[Memory] window will occur for updating the window. When the [Memory]
window is not to be updated, change the setting in [Lock Refresh] from the
popup menu.

me command: A command line function that reads or writes the specified amount of

memory at the specified address.

(2) User program downloading function

A load module registered in the workspace can be downloaded. Such module can be selected
from [Download Module] in the [Debug] menu. Downloading is also possible by a popup menu
that is opened by right-clicking on the mouse at the load module in the workspace. The user
program is downloaded to the RAM or internal flash memory.

When downloading to the flash memory that has not been within the MPU, select [Emulator] from
the [Setup] menu, open the [Configuration] window, and perform required settings on the
[Loading flash memory] page.

This function also downloads information required for source-level debugging such as debugging
information.

(3) Memory data uploading function

The specified amount of memory from the specified address can be saved in a file.

(4) Memory data downloading function

The memory contents saved in a file can be downloaded. Select [Load] from the popup menu in
the [Memory] window.

Rev. 1.00 Nov. 26, 2007 Page 16 of 230

REJ10J1766-0100

Section 2 Emulator Functions

(5) Displaying the variable contents

The variable contents specified in the user program are displayed.

(6) Monitoring function

In some devices to be debugged, memory contents can be monitored during user program
execution. For details on the specifications of each product, refer to the online help.

(7) Other memory operation functions

Other functions are as follows:

 Memory fill
 Memory copy
 Memory save
 Memory verify
 Memory search
 Internal I/O display
 Cache table display and edit (only for devices incorporating caches)
 TLB table display or edit (only for devices incorporating MMU)
 Displaying label and variable names and their contents

For details, refer to the online help.

Notes:

1. Memory access during user program execution:
When memory is accessed from the memory window, etc. during execution of the
user program, execution stops for the memory access and is then resumed. Therefore,
realtime emulation cannot be performed.

The stopping time of the user program is as follows:

Environment:

Host computer: 3 GHz (Pentium® 4)

SH7265: CPU clock 66.6 MHz

JTAG clock: 2.5 MHz

When a one-byte memory is read from the command-line window, the stopping time

will be about 8 ms.

2. Memory access during user program break:

The program can also be downloaded for the flash memory area by the emulator.
Other memory write operations are enabled for the RAM area and the internal flash

Rev. 1.00 Nov. 26, 2007 Page 17 of 230

REJ10J1766-0100

Section 2 Emulator Functions

memory. Therefore, an operation such as memory write or BREAKPOINT should be
set only for the RAM area and the internal flash memory. When the memory area can
be read by the MMU, do not perform memory write, BREAKPOINT setting, or
downloading.

3. Cache operation during user program break:

When cache is enabled in the device incorporating a cache, the emulator accesses the
memory by the following methods:
 At memory write: Writes through the cache, then writes to the memory or uses the
OCBWB instruction.

 At memory read: Does not change the cache write mode that has been set.
 At memory verify: Disables the cache for verification read.

Therefore, when memory read or write is performed during user program break, the
cache state will be changed.
In some devices to be debugged, the emulator accesses the memory by the following
methods:
 At memory write: Writes to the cache, then issues an external single write. The
LRU is not updated.
 At memory read: Reads memory from the cache. The LRU is not updated.

2.6 Stack Trace Function

The emulator uses the information on the stack to display the names of functions in the sequence
of calls that led to the function to which the program counter is currently pointing. This function
can be used only when the load module that has the Dwarf2-type debugging information is loaded.
For the usage of this function, refer to section 6.20, Stack Trace Function.

2.7 User-interrupt Open Function during User Program Break

Some devices to be debugged open all interrupts while executing emulation to users. During a user
program break, it is possible to specify the mode whether or not the interrupt processing is
executed.

2.8 Online Help

An online help explains the usage of each function or the command syntax that can be entered
from the command line window.

Select [Emulator Help] from the [Help] menu to view the emulator help.

Rev. 1.00 Nov. 26, 2007 Page 18 of 230

REJ10J1766-0100

Section 3 Preparation before Use

3.1 Emulator Preparation

Unpack the emulator and prepare it for use as follows:

Section 3 Preparation before Use

WARNING

READ the reference sections shaded in figure 3.1 before
using the emulator product. Incorrect operation will damage
the user system and the emulator product. The USER
PROGRAM will be LOST.

Reference

Unpack the emulator

Check the components against the component list

Set up the emulator

- Install the emulator's software
(Check the components and register the user information.)

- Insert the emulator

- Set up the main unit of the emulator

Start the High-performance Embedded Workshop

Turn on the user system

Component list

When the emulator
is used first.

Section 3

Section 4

When the emulator
is used for second
time or later.

Input the user system reset signal

Figure 3.1 Emulator Preparation Flow Chart

Rev. 1.00 Nov. 26, 2007 Page 19 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

3.2 Emulator Hardware Configuration

As shown in figure 3.2, the emulator consists of an emulator, a USB cable, and a user system
interface cable. The emulator is connected to the host computer via USB 1.1, and also to the USB
port conforming to USB 2.0.

Figure 3.2 Emulator Hardware Configuration (when the 38-pin Type Cable is Used)

Rev. 1.00 Nov. 26, 2007 Page 20 of 230

REJ10J1766-0100

The names of each section of the emulator are explained next.

Emulator Top View:

Section 3 Preparation before Use

Figure 3.3 Emulator Top View

(a) E10A-USB Multi logo plate: A black plate is dedicated for the emulator is provided to be

easily distinguished from other E-series emulators.

(b) ACTION LED: A circled LED. Marked ‘ACT’. When this LED is lit, the E10A-USB

Multi control software is in operation.

(c) RUN LED: Marked ‘1’. When this LED is lit, the user program is in operation.
(d) ACT LED Marked ‘2’. When this LED is lit, the E10A-USB Multi is connecting

to the micro computer.

Rev. 1.00 Nov. 26, 2007 Page 21 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

(e) Core switch LED Marked ‘3’. When this LED is lit, the E10A-USB Multi switches the

micro computer to be controled.

(f) UVCC LED Marked ‘4’. When this LED is lit, the E10A-USB Multi is supplied

the UVCC .

(g) Host connector: Marked ‘

’. A connector for the host computer is provided at the

side of this mark.

(h) User connector: Marked ‘USER I/F’. A connector for the user system interface cable

is provided at the side of this mark.

.

Note: Even if the LED is not lit, the USB is not disconnected or malfunctioned.

Emulator Host-side View:

Figure 3.4 Emulator Host-side View

(a) Host-side connector: A USB connector for the host computer. Be sure to connect the

provided USB cable.

Rev. 1.00 Nov. 26, 2007 Page 22 of 230

REJ10J1766-0100

Section 3 Preparation before Use

Emulator User-side View:

Figure 3.5 Emulator User-side View

(a) User-side connector: A user system interface cable is connected.

Rev. 1.00 Nov. 26, 2007 Page 23 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

Emulator Bottom View:

This device complies with Part 15 of the FCC Rules.
Operation is s ubject to the fol low ing t wo conditions:
(1) This device may not cause harmful interference, and
(2) This device must accept any interference received, including

(a)

MODEL : HS0005KCU04H

ޓޓޓޓ

SERIAL No. : 00001A

interference that may cause undesired opera tion.

MADE IN JAPAN

Figure 3.6 Emulator Bottom View

(a) Label for product management: The serial number, revision, and safety standard, etc. of the

emulator are written to. The contents differ depending on the
time when you purchased the product.

Rev. 1.00 Nov. 26, 2007 Page 24 of 230

REJ10J1766-0100

Section 3 Preparation before Use

3.3 CD-R

The root directory of the CD-R contains a setup program for installing the emulator’s software.
The folders contain the files and programs listed below.

Table 3.1 Contents of the CD-R Directories

Directory Name Contents Description

Dlls Microsoft runtime library A runtime library for the High-performance

Embedded Workshp. The version is checked
at installation and this library is copied to the
hard disk as part of the installation process.

Drivers E10A-USB Multi emulator

driver

Help Online help for the E10A-USB

Multi emulator

Manuals E10A-USB Multi emulator

manuals

USB drivers for the E10A-USB Multi emulator.

An online help file. This is copied to the hard
disk as part of the installation process.

E10A-USB Multi emulator user’s manuals.
They are provided as PDF files.

3.4 Installing Emulator’s Software

Follow the cues given by the installation manager to install the software.

The two of separated High-performance Embedded Workshop for the CPU0 and CPU1 will be needed to
install.

(1) Install the High-performance Embedded Workshop for the CPU0. Activate the

HewInstMan.exe from the CD-R root directory, start up the installation manager and select the
[Install the HEW to another directory], select the [change] button from the installation
destination and name the folder name. Perform the Install following the Installation manager.

(2) Install the High-performance Embedded Workshop for the CPU1. Activate the

HewInstMan.exe from the CD-R root directory, start up the installation manager and select the
[Install the HEW to another directory], select the [change] button from the installation
destination and name the folder name. Perform the Install following the Installation manager.

Note: When a driver is installed in Windows



XP, a warning message on the Windows logo
test may be displayed, but it is not a problem. Select [Continue Anyway] to proceed with
driver installation.

Rev. 1.00 Nov. 26, 2007 Page 25 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

3.5 Connecting the Emulator to the Host Computer

This section describes how to connect the emulator to the host computer. For the position of each
connector of the emulator, refer to section 3.2, Emulator Hardware Configuration.

Notes: 1. When [Add New Hardware Wizard] is displayed, select the [Search for the best driver

for your device. (Recommended)] radio button and then the [Specify a location] check
box to select the path to be searched for drivers. The location must be specified as
<Drive>:\DRIVERS. (<Drive> is the CD drive letter.)

2. Be sure to install the software for the emulator before putting the emulator in place.

WARNING

Always switch OFF the emulator product and the user
system before connecting or disconnecting any CABLES
except for the USB interface cable. Failure to do so will result
in a FIRE HAZARD and will damage the user system and the
emulator product or will result in PERSONAL INJURY.
The USER PROGRAM will be LOST.

Rev. 1.00 Nov. 26, 2007 Page 26 of 230

REJ10J1766-0100

Section 3 Preparation before Use

The emulator is connected to the host computer via the USB 1.1, and also to the USB port
conforming to USB 2.0. Figure 3.7 shows the system configuration.

Host comuputer

E10A-USB Multi emulator

USB cable (1.5 m)

Figure 3.7 System Configuration when Connecting the Emulator to the Host Computer

Rev. 1.00 Nov. 26, 2007 Page 27 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

3.6 Connecting the Emulator to the User System

Use the procedure below to connect the emulator to the user system with the user system interface
cable, or to disconnect them when moving the emulator or the user system.

1. Check that the host computer is turned off or the emulator is not connected to the host
computer with the USB cable.

2. Connect the user system interface cable to the user-side connector of the emulator.

3. Connect the USB cable to the host-side connector of the emulator.

Figure 3.8 shows the position of the connector.

User interface cable connector

Figure 3.8 Position of the Connector

Rev. 1.00 Nov. 26, 2007 Page 28 of 230

REJ10J1766-0100

Section 3 Preparation before Use

(1) The connector must be installed to the user system. Table 3.2 shows the recommended

connector for the emulator.

Table 3.2 Recommended H-UDI Port Connector

Connector Type Number Manufacturer Specifications

14-pin connector 2514-6002 Minnesota Mining &

Manufacturing Ltd.

36-pin connector DX10M-36S Hirose Electric Co., Ltd. Screw type

DX10M-36SE,

DX10GM-36SE

Lock-pin type

14-pin straight type

Notes: 1. When designing the 14-pin connector layout on the user board, do not place any

components within 3 mm of the H-UDI port connector.
When designing the 36-pin connector layout on the user board, do not connect other
signal lines to the H-UDI port connector.

2. The H-UDI is an interface compatible with the Joint Test Action Group (JTAG)
specifications.

(2) The pin assignments of the connector are shown in section 2 in the additional document,

Supplementary Information on Using the SHxxxx.

(3) Connect pins 5 and GND bus read located in the center of the H-UDI port connector (when

using the 38-pin user system interface cable) and pins 9, 10, 12, 13, and 14 (when using the 14­pin user system interface cable) of the H-UDI port connector to GND firmly on the PCB.
These pins are used as electrical GND and to monitor the connection of the H-UDI port
connector. Note the pin assignments of the H-UDI port connector.

Rev. 1.00 Nov. 26, 2007 Page 29 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

User Interface Cable

User System

Figure 3.9 Connecting the User System Interface Cable to the User System

Pin 1

Figure 3.10 Connecting the User System Interface Cable to the User System

when the 38-pin Type Connector is Used

User system interface cable

User system

H-UDI port connector

when the 14-pin Type Connector is Used

H-UDI Port Connector

Rev. 1.00 Nov. 26, 2007 Page 30 of 230

REJ10J1766-0100

Section 3 Preparation before Use

CAUTION

Note that the pin number assignments of the connector
differ from those of the connector manufacturer.

Notes: 1. Connection of the signals differs depending on the package. For details, refer to the

MPU’s pin assignments.

2. The range of communication that the emulator operates at is different depending on

the MPU used.

3. To connect the signals from the connector, refer to section 1 in the additional

document, Supplementary Information on Using the SHxxxx.

4. When developing user systems, do not connect the TDI and TDO signals of the

device to the boundary scan loop, or separate them by using a switch (figure 3.11).

Rev. 1.00 Nov. 26, 2007 Page 31 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

H-UDI
port

JTAG
port

TDI
TDO

IC

TDI TDO

TAP

Figure 3.11 User System Example

SHxxxx

H-UDI

IC

TAP

Boundary scan loop

User system

IC

TDI

TAP

TDI: Test data input
TDO: Test data output
TAP: Test access port

TDOTDI TDO

Rev. 1.00 Nov. 26, 2007 Page 32 of 230

REJ10J1766-0100

3.7 Connecting System Ground

Section 3 Preparation before Use

WARNING

Separate the frame ground from the signal ground at the
user system. Failure to do so will result in a FIRE HAZARD
and will damage the user system and the emulator product or
will result in PERSONAL INJURY.

The emulator's signal ground is connected to the user system's signal ground. In the emulator, the
signal ground and frame ground are connected. In the user system, connect the frame ground only;
do not connect the signal ground to the frame ground (figure 3.12).

If it is difficult to separate the frame ground from the signal ground in the user system, set the
GND for DC power input (AC adapter) of the host computer and the frame ground of the user
system as the same potential. If the GND potential is different between the host computer and the
target system, an overcurrent will flow in the low-impedance GND line and thin lines might be
burned.

Signal ground

Host
computer

E10A-USB Multi emulator

USB

Power
supply

Logic

Signal

Signal ground

Signal

Signal ground

User system

Logic

Frame ground

Figure 3.12 Connecting System Ground

Rev. 1.00 Nov. 26, 2007 Page 33 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

3.8 Interface Circuits in the Emulator

Figures 3.13 and 3.14 show interface circuits in the emulator. Use them as a reference to
determine the value of the pull-up resistance.

Note: The 74LVC2G125 and 74LVC2T45 operate at VCC (1.8 to 5.0 V) from the H-UDI port

connector.

Rev. 1.00 Nov. 26, 2007 Page 34 of 230

REJ10J1766-0100

Section 3 Preparation before Use

Emulator control circuit

3.3V

74LVC2T45
VccB VccA

BA

74LVC2T45
VccB VccA

BA

74LVC2T45
VccA VccB

AB

74LVC2T45
VccA VccB

AB

74LVC2G125

A Y

74LVC2T45
VccB VccA

BA

74LVC2T45
VccB VccA

BA

Vcc

22 Ω

22 Ω

22 Ω

22 Ω

22 Ω

22 Ω

H-UDI port connector

UVCC

10 kΩ

TCK

10 kΩ

TRST

10 kΩ

TDO

10 kΩ

ASEBRKAK

10 kΩ

TMS

10 kΩ

TDI

74LVC2T45
VccA VccB
AB

74LVC2G125

Vcc
OE
A Y

22 Ω

10 kΩ

RESET

Figure 3.13 Interface Circuits in the Emulator (H-UDI)

Rev. 1.00 Nov. 26, 2007 Page 35 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

Emulator control circuit

SN65LVDS33

SN65LVDS33

SN65LVDS33

Reference voltage

22 Ω

22 Ω

22 Ω

H-UDI port connector

UVCC_AUD

10 kΩ

AUDCK

10 kΩ

AUDATA[3:0]

10 kΩ

AUDSYNC

SN65LVDS33

22 Ω

10 kΩ

AUDATA[7:4]

Figure 3.14 Interface Circuits in the Emulator (AUD)

Rev. 1.00 Nov. 26, 2007 Page 36 of 230

REJ10J1766-0100

Section 3 Preparation before Use

3.9 Setting up the Emulator

Set up the emulator’s firmware using the following procedures. The emulator will be set up for the
first device group to be started.

Note: Only one device group can be set up after the initial purchase of the emulator

emulator for another device group after set up, purchase the license tool to add a device
group.

CAUTION

Do not disconnect the USB cable unless instructed to do
so by an on-screen message. Incorrect operation will damage
the emulator product.

. To use the

Rev. 1.00 Nov. 26, 2007 Page 37 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

3.10 System Check

When the software is executed, use the procedure below to check that the emulator is connected
correctly. Here, use the workspace for a tutorial provided on the product.

Refer to section 4, Preparations for Debugging, for the other activating method to create a new
project or use an existing workspace.

1. Connect the emulator to the host computer.

2. Connect the user system interface cable to the connector of the emulator.

3. Connect the user system interface cable to the connector in the user system.

4. Double-click on the ”HEW2.exe” from the folder that is installed for CPU0 in section 3.4,

Installing Emulators Software.

5. [Welcome!] dialog box is displayed.

Figure 3.15 [Welcome!] Dialog Box

[Create a new project workspace] radio button: Creates a new workspace.

[Open a recent project workspace] radio button: Uses an existing workspace and displays

the history of the opened workspace.

[Browse to another project workspace] radio button: Uses an existing workspace; this radio

button is used when the history of the
opened workspace does not remain.

To use a workspace for the tutorial, select the [Browse to another project workspace] radio button
and click the [OK] button.

Rev. 1.00 Nov. 26, 2007 Page 38 of 230

REJ10J1766-0100

Section 3 Preparation before Use

When the [Open workspace] dialog box is opened, specify the following directory:
<Drive where the OS has been installed\WorkSpace\Tutorial\E10A-USBM\SH2A-
DUAL\SH2A-DUAL\Tutorial_SH2A-DUAL\CPU0

After the directory has been specified, select the following file and click the [Open] button.

Figure 3.16 [Open The Workspace] Dialog Box

Rev. 1.00 Nov. 26, 2007 Page 39 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

6. The [Select Emulator mode] dialog box is displayed.

Figure 3.17 [Select Emulator mode] Dialog Box

Select <name of the device in use>_CPU0 from the [Device] drop-down list box. The following
item is selected in the [Mode] group box.

 E10A-USB Multi Emulator

The E10A-USB Multi emulator for the specified MCU is activated. Debugging the
program is enabled.

7. The [Connecting] dialog box is displayed and connection of the emulator starts.

Rev. 1.00 Nov. 26, 2007 Page 40 of 230

REJ10J1766-0100

Figure 3.18 [Connecting] Dialog Box

Section 3 Preparation before Use

8. The dialog box shown in figure 3.19 is displayed if no product groups have been installed in
the emulator at the time of purchase or if the SHxxxx license has been installed in the emulator
but the emulator firmware has been set up for a different device group. The dialog box shown
in figure 3.20 is displayed if an old version of the emulator firmware has been set up in the
emulator. Clicking the [OK] button sets up the emulator firmware.

Figure 3.19 Dialog Box to Confirm Setting up of the Emulator Firmware

Rev. 1.00 Nov. 26, 2007 Page 41 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

Figure 3.20 Dialog Box to Confirm Updating of the SHxxxx Emulator Firmware

CAUTION

The USB cable must not be disconnected until writing is
complete.
Early disconnection may damage the emulator.

9. The dialog box shown in figure 3.21 is displayed.

Figure 3.21 Dialog Box of the RESET Signal Input Request Message

10. Power on the user system.

11. Input the reset signal from the user system, and click the [OK] button.

12. If no reset signal is detected, the following dialog box is displayed.

Rev. 1.00 Nov. 26, 2007 Page 42 of 230

REJ10J1766-0100

Section 3 Preparation before Use

Figure 3.22 [Can not find /RESET signal] Dialog Box

When the [Ignore] button is clicked, the emulator issues a reset in the CPU for initiation.
However, this method is unavailable for some products. For details, refer to section 2.2,
Specific Functions for the Emulator when Using the SHxxxx, in the additional document,
Supplementary Information on Using the SHxxxx.

13. If the "Connected" is displayed in the [Output] window of the High-performance Embedded
Workshop for CPU0, starting up the emulator is completed.

Figure 3.23 [Output] Window

14. Double-click on the filename ”HEW.exe” in the folder that was installed for CPU0 in section

3.4, Installing Emulator’s Software.

Rev. 1.00 Nov. 26, 2007 Page 43 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

15. The [Welcome!] dialog box is displayed.

Figure 3.24 [Welcome!] Dialog box

To use a workspace for the tutorial, select the [Browse to another project workspace] radio button
and click the [OK] button.

When the [Open workspace] dialog box is opened, specify the following directory:
<Drive where the OS has been installed\WorkSpace\Tutorial\E10A-USBM\SH2A-
DUAL\SH2A-DUAL\Tutorial_SH2A-DUAL\CPU0

Rev. 1.00 Nov. 26, 2007 Page 44 of 230

REJ10J1766-0100

Section 3 Preparation before Use

After specifying the directory, select the following file and click on the [Open] button

Figure 3.25 [Open the workspace] Dialog box

(16) The [Select Emulator mode] dialog box is displayed.

Figure 3.26 [Select Emulator mode] Dialog box

Select <name of the device in use>_CPU1 from the [Device] drop-down list box.

Rev. 1.00 Nov. 26, 2007 Page 45 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

The following item is selected in the [Mode] group box.

 E10A-USB Multi Emulator
 The E10A-USB Multi Emulator is activated for the selected device. Debugging of

programs can proceed.

(17) [Connecting] dialog box is displayed, and the emulator connection will be started up.

Figure 3.27 [Connecting] Dialog box

(18) If the Connected is displayed in the [Output] window of the High-performance

Embedded Workshop for the CPU1, starting up for the emulator is completed.

Rev. 1.00 Nov. 26, 2007 Page 46 of 230

REJ10J1766-0100

Section 3 Preparation before Use

Figure 3.28 [Output] Window

Notes: If the emulator is not initiated, the following dialog boxes shown in figures 3.29 through

3.35 will be displayed.

(a) If the following dialog box is displayed and the method 11 above is unavailable, the

power of the user system may not be input or the RESET signal may not be input to
the device. Check the input circuits for the power of the user system and the reset pin.

Figure 3.29 [Can not find /RESET signal] Dialog Box

(b) If the following dialog box is displayed, check that the H-UDI port connector on the

user system is correctly connected.

Rev. 1.00 Nov. 26, 2007 Page 47 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

Figure 3.30 [Check the connection] Dialog Box

(c) If the following dialog box is displayed, the emulator’s firmware may not be set up

correctly. Set up the firmware of the device group that is used for the license tool.

Figure 3.31 [The product currently connected] Dialog Box

(d) If the following dialog box is displayed, the device may not correctly operate. Check

if there are reasons for illegal device operation.

Figure 3.32 [COMMUNICATION TIMEOUT ERROR] Dialog Box

Rev. 1.00 Nov. 26, 2007 Page 48 of 230

REJ10J1766-0100

Section 3 Preparation before Use

Figure 3.33 [INVALID ASERAM FIRMWARE!] Dialog Box

Figure 3.34 [Error JTAG boot] Dialog Box

(e) The following dialog box is displayed when the MCU cannot communicate with the

emulator. The MCU may not operate correctly; check the MCU settings.

Figure 3.35 [Boot Failed!] Dialog Box

Rev. 1.00 Nov. 26, 2007 Page 49 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

2. If an incorrect driver has been selected, the following dialog box will appear.

Figure 3.36 [Unable to restore the previous driver settings] Dialog Box

3. If the emulator is not activated due to other reasons, a message box corresponding to
the status is displayed. Use the message as a reference to check the wiring on the
board.

3.11 Uninstalling the Emulator’s Software

Follow this procedure to remove the installed emulator’s software from the user’s host computer.
As the installed product is registered with the High-performance Embedded Workshop, uninstall
the product on the High-performance Embedded Workshop screen.

It is also possible to uninstall the emulator’s software by using [Add/Remove Programs] in the
control panel. In this case, however, note that all the tools (including the compiler) in the High­performance Embedded Workshop will be removed.

1. Activate the High-performance Embedded Workshop.

2. Click the [Administration…] button in the [Welcome!] dialog box.

Rev. 1.00 Nov. 26, 2007 Page 50 of 230

REJ10J1766-0100

Figure 3.37 [Welcome!] Dialog Box

3. The [Tools Administration] dialog box is opened.

Section 3 Preparation before Use

Figure 3.38 [Tools Administration] Dialog Box

Rev. 1.00 Nov. 26, 2007 Page 51 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

4. Click the [+] mark at the left of [Debugger Components] in the [Registered components] list

box to list the installed components. Then, highlight the product name to be uninstalled.

Figure 3.39 Highlighting the Product to be Uninstalled

5. Click the [Unregister] button. After the following message box is displayed, click the [Yes]

button.

Figure 3.40 [Unregistering this tool] Message Box

This is the end of canceling the High-performance Embedded Workshop registration. Then,
remove the file for the emulator from the host computer.

Rev. 1.00 Nov. 26, 2007 Page 52 of 230

REJ10J1766-0100

Section 3 Preparation before Use

6. Click the [Uninstaller…] button in the [Tools Administration] dialog box to open the

[Uninstall HEW Tool] dialog box.

Figure 3.41 [Uninstall HEW Tool] Dialog Box

Rev. 1.00 Nov. 26, 2007 Page 53 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

7. Click the [Start] button to list the installed components.

Figure 3.42 Highlighting the Product to be Uninstalled

Highlight the product name to be uninstalled and click the [Uninstall] button. This is the end
of uninstallation.

CAUTION

A shared file may be detected while the program is being
removed. If another product may be using the shared file, do
not remove the file. If another product does not start up after
the removal process, re-install that product.

Rev. 1.00 Nov. 26, 2007 Page 54 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

Section 4 Preparations for Debugging

4.1 Method for Activating High-performance Embedded Workshop

To activate the High-performance Embedded Workshop, follow the procedure listed below.

1. Connect the emulator to the host computer and the user system, then turn on the user system.

2. Select [High-performance Embedded Workshop] from [Renesas] -> [High-performance
Embedded Workshop] of [Programs] in the [Start] menu.

3. The [Welcome!] dialog box is displayed.

Figure 4.1 [Welcome!] Dialog Box

[Create a new project workspace] radio button: Creates a new workspace.

[Open a recent project workspace] radio button: Uses an existing workspace and displays

the history of the opened workspace.

[Browse to another project workspace] radio button: Uses an existing workspace; this radio

button is used when the history of the
opened workspace does not remain.

Rev. 1.00 Nov. 26, 2007 Page 55 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

The following describes how to activate the High-performance Embedded Workshop when
selecting [Create a new project workspace] without any toolchain, [Create a new project
workspace] with a toolchain, and [Browse to another project workspace]. The [Open a recent
project workspace] radio button is used to omit the operation for specifying the workspace file
when [Browse to another project workspace] is selected.

4.1.1 Creating the New Workspace (Toolchain Not Used)

1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded
Workshop is activated, select [Create a new project workspace] radio button and click the
[OK] button.

Figure 4.2 [Welcome!] Dialog Box

Rev. 1.00 Nov. 26, 2007 Page 56 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

2. The Project Generator is started. In this section, we omit description of the settings for the
toolchain.
If you have not purchased the toolchain, the following dialog box is displayed.

Figure 4.3 [New Project Workspace] Dialog Box

[Workspace Name] edit box: Enter the new workspace name. Here, for example, enter ‘test’.

[Project Name] edit box: Enter the project name. When the project name is the same as

the workspace name, it needs not be entered.

Other list boxes are used for setting the toolchain; the fixed information is displayed when the
toolchain has not been installed.

Rev. 1.00 Nov. 26, 2007 Page 57 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

3. Make the required setting for the toolchain. When the setting has been completed, the
following dialog box is displayed.

Figure 4.4 [Setting the Target System for Debugging] Dialog Box

Check the target emulator and click the [Next] button.

Rev. 1.00 Nov. 26, 2007 Page 58 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

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

Figure 4.5 [Setting the Debugger Options] Dialog Box

This is the end of the emulator setting.

Click the [Finish] button to exit the Project Generator. The High-performance Embedded
Workshop is activated.

5. After the High-performance Embedded Workshop has been activated, the emulator is
automatically connected. For operation during connection, refer to section 3.10, System
Check.

Rev. 1.00 Nov. 26, 2007 Page 59 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

4.1.2 Creating the New Workspace (Toolchain Used)

1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded
Workshop is activated, select [Create a new project workspace] radio button and click the
[OK] button.

Figure 4.6 [Welcome!] Dialog Box

Rev. 1.00 Nov. 26, 2007 Page 60 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

2. The Project Generator is started.
If you have purchased the toolchain, the following dialog box is displayed.

Figure 4.7 [New Project Workspace] Dialog Box

[Workspace Name] edit box: Enter the new workspace name. Here, for example, enter

‘test’.

[Project Name] edit box: Enter the project name. When the project name is the

same as the workspace name, it needs not be entered.

[CPU family] drop-down list box: Select the target CPU family.

[Tool chain] drop-down list box: Select the target toolchain name when using the toolchain.

Otherwise, select [None].

[Project type] list box: Select the project type to be used.

Note: When [Demonstration] is selected in the emulator, note the following:

The [Demonstration] is a program for the simulator. When the generated program is used
by the emulator, delete the Printf statement.

Rev. 1.00 Nov. 26, 2007 Page 61 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

3. Make the required setting for the toolchain. When the setting has been completed, the
following dialog box is displayed.

Figure 4.8 [New Project –7/9– Setting the Target System for Debugging] Dialog Box

Check the target emulator and click the [Next] button. Mark other products as required.

Rev. 1.00 Nov. 26, 2007 Page 62 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

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

Figure 4.9 [New Project –8/9– Setting the Debugger Options] Dialog Box

This is the end of the emulator setting.

Exit the Project Generator according to the instructions on the screen. The High-performance
Embedded Workshop is activated.

5. After the High-performance Embedded Workshop has been activated, connect the emulator.
However, it is not needed to connect the emulator immediately after the High-performance
Embedded Workshop has been activated.
To connect the emulator, use one of the methods (a) and (b) below. For operation during
connection, refer to section 3.10, System Check.

Rev. 1.00 Nov. 26, 2007 Page 63 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

(a) Connecting the emulator after the setting at emulator activation

Select [Debug settings] from the [Debug] menu to open the [Debug Settings] dialog box. It is
possible to register the download module or the command chain that is automatically executed
at activation. For details on the [Debug Settings] dialog box, refer to section 4.2, Setting at
Emulator Activation.

After the [Debug Settings] dialog box has been set, when the dialog box is closed, the emulator
is connected.

(b) Connecting the emulator without the setting at emulator activation

The emulator can be easily connected by switching the session file that the setting for the
emulator use has been registered.

Figure 4.10 Selecting the Session File

In the list box that is circled in figure 4.10, select the session file name including the character
string that has been set in the [Target name] text box in figure 4.9, [New Project –8/9– Setting the

Rev. 1.00 Nov. 26, 2007 Page 64 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

Debugger Options] dialog box. The setting for using the emulator has been registered in this
session file.

After selected, the emulator is automatically connected.

4.1.3 Selecting an Existing Workspace

1. In the [Welcome!] dialog box that is displayed when the High-performance Embedded
Workshop is activated, select [Browse to another project workspace] radio button and click the
[OK] button.

Figure 4.11 [Welcome!] Dialog Box

2. The [Open Workspace] dialog box is displayed. Select a directory in which you have created a
workspace.
After that, select the workspace file (.hws) and press the [Open] button.

Rev. 1.00 Nov. 26, 2007 Page 65 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

Figure 4.12 [Open Workspace] Dialog Box

3. This activates the High-performance Embedded Workshop and recovers the state of the
selected workspace at the time it was saved.
When the saved state information of the selected workspace includes connection to the
emulator, the emulator will automatically be connected. To connect the emulator when the
saved state information does not include connection to the emulator, refer to section 4.4,
Connecting the Emulator.

Rev. 1.00 Nov. 26, 2007 Page 66 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

4.2 Setting at Emulator Activation

4.2.1 Setting at Emulator Activation

When the emulator is activated, the command chain can be automatically executed. It is also
possible to register multiple load modules to be downloaded. The registered load modules are
displayed on the workspace window.

1. Select [Debug settings] from the [Debug] menu to open the [Debug Settings] dialog box.

Figure 4.13 [Debug Settings] Dialog Box ([Target] Page)

2. Select the product name to be connected in the [Target] drop-down list box.

3. Select the format of the load module to be downloaded in the [Default Debug Format] drop­down list box, then register the corresponding download module in the [Download Modules]
list box.

Note: Here, no program has been downloaded. For downloading, refer to section 5.2,

Downloading a Program.

4. Click the [Options] tab.

Rev. 1.00 Nov. 26, 2007 Page 67 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

Figure 4.14 [Debug Settings] Dialog Box ([Options] Page)

The command chain that is automatically executed at the specified timing is registered. The
following four timings can be specified:

 At connecting the emulator
 Immediately after reset
 Immediately before downloading
 Immediately after downloading

Specify the timing for executing the command chain in the [Command batch file load timing]
drop-down list box. In addition, register the command-chain file that is executed at the specified
timing in the [Command Line Batch Processing] list box.

Rev. 1.00 Nov. 26, 2007 Page 68 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

4.2.2 Downloading a Program

A download module is added under [Download modules] in the [Workspace] window.

Open the load module of [Download modules] in the [Workspace] window by clicking the right­hand mouse button and select [Download module] to start downloading the module.

Figure 4.15 Download Menu of the [Workspace] Window ([Projects])

Notes: 1. When load modules are downloaded, select [Debug] -> [Download] -> [All DownLoad

Modules].

2. To proceed with source-level debugging with the High-performance Embedded

Workshop for CPU0 or the High performance Embedded Workshop for CPU1,
download the debugging information file for the corresponding CPU.

Rev. 1.00 Nov. 26, 2007 Page 69 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

4.3 Debug Sessions

The High-performance Embedded Workshop stores all of your builder options into a
configuration. In a similar way, the High-performance Embedded Workshop stores your debugger
options in a session. The debugging platforms, the programs to be downloaded, and each
debugging platform’s options can be stored in a session.

Sessions are not directly related to a configuration. This means that multiple sessions can share
the same download module and avoid unnecessary program rebuilds.

Each session’s data should be stored in a separate file in the High-performance Embedded
Workshop project. Debug sessions are described in detail below.

4.3.1 Selecting a Session

The current session can be selected in the following two ways:

 From the toolbar

Select a session from the drop-down list box (figure 4.16) in the toolbar.

Figure 4.16 Toolbar Selection

Rev. 1.00 Nov. 26, 2007 Page 70 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

 From the dialog box

1. Select [Debug -> Debug Sessions…]. This will open the [Debug Sessions] dialog box

(figure 4.17).

Figure 4.17 [Debug Sessions] Dialog Box

2. Select the session you want to use from the [Current session] drop-down list.

3. Click the [OK] button to set the session.

4.3.2 Adding and Removing Sessions

A new session can be added by copying settings from another session or removing a session.

 To add a new empty session

1. Select [Debug -> Debug Sessions…] to display the [Debug Sessions] dialog box (figure

4.17).

2. Click the [Add…] button to display the [Add new session] dialog box (figure 4.18).

3. Check the [Add new session] radio button.

4. Enter a name for the session.

Rev. 1.00 Nov. 26, 2007 Page 71 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

5. Click the [OK] button to close the [Debug Sessions] dialog box.

6. This creates a file with the name entered in step 4. If a file with this name already exists,
an error is displayed.

Figure 4.18 [Add new session] Dialog Box

 To import an existing session into a new session file

1. Select [Debug -> Debug Sessions…] to display the [Debug Sessions] dialog box (figure

4.17).

2. Click the [Add…] button to display the [Add new session] dialog box (figure 4.18).

3. Check the [Use an existing session file] radio button.

4. Enter a name for the session.

5. Enter the name of an existing session file that you would like to import into the existing
project or click the [Browse] button to select the file location.

If the [Open and maintain link to session file] check box is not checked, the imported new
session file is generated in the project directory.

If the [Open and maintain link to session file] check box is checked, a new session file is
not generated in the project directory but is linked to the existing session file.

If the [Make session file link read only] check box is checked, the linked session file is
used as read-only.

6. Click the [OK] button to close the [Debug Sessions] dialog box.

Rev. 1.00 Nov. 26, 2007 Page 72 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

 To remove a session

1. Select [Debug -> Debug Sessions…] to display the [Debug Sessions] dialog box (figure

4.17).

2. Select the session you would like to remove.

3. Click the [Remove] button.

Note that the current session cannot be removed.

4. Click the [OK] button to close the [Debug Sessions] dialog box.

 To view the session properties

1. Select [Debug -> Debug Sessions…] to display the [Debug Sessions] dialog box (figure

4.17).

2. Select the session you would like to view the properties for.

3. Click the [Properties] button to display the [Session Properties] dialog box (figure 4.19).

Figure 4.19 [Session Properties] Dialog Box

 To make a session read-only

1. Select [Debug -> Debug Sessions…] to display the [Debug Sessions] dialog box (figure

4.17).

2. Select the session you would like to make read-only.

3. Click the [Properties] button to display the [Session Properties] dialog box (figure 4.19).

4. Check the [Read only] check box to make the link read-only. This is useful if you are
sharing debugger-setting files and you do not want data to be modified accidentally.

5. Click the [OK] button.

 To save a session with a different name

1. Select [Debug -> Debug Sessions…] to display the [Debug Sessions] dialog box (figure

4.17).

2. Select the session you would like to save.

3. Click the [Save as…] button to display the [Save Session] dialog box (figure 4.20).

Rev. 1.00 Nov. 26, 2007 Page 73 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

4. Specify the location to save the new file.

5. If you want to export the session file to another location, leave the [Maintain link] check
box unchecked. If you would like the High-performance Embedded Workshop to use this
location instead of the current session location, check the [Maintain link] check box.

6. Click the [Save] button.

Figure 4.20 [Save Session] Dialog Box

4.3.3 Saving Session Information

 To save a session

Select [File -> Save Session].

Rev. 1.00 Nov. 26, 2007 Page 74 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

4.4 Connecting the Emulator

Select either of the following two ways to connect the emulator:

(a) Connecting the emulator after the setting at emulator activation

Select [Debug settings] from the [Debug] menu to open the [Debug Settings] dialog box. It is
possible to register the download module or the command chain that is automatically executed
at activation. For details on the [Debug Settings] dialog box, refer to section 4.2, Setting at
Emulator Activation.

After the [Debug Settings] dialog box has been set, when the dialog box is closed, the emulator
is connected.

(b) Connecting the emulator without the setting at emulator activation

The emulator can be easily connected by switching the session file that the setting for the
emulator use has been registered.

Figure 4.21 Selecting the Session File

Rev. 1.00 Nov. 26, 2007 Page 75 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

In the list box that is circled in figure 4.21, select the session file name including the character
string that has been set in the [Target name] text box in figure 4.9, [New Project –8/9– Setting the
Debugger Options] dialog box. The setting for using the emulator has been registered in this
session file.

After the session file name is selected, the emulator will automatically be connected. For details
on the session file, refer to section 4.3, Debug Sessions.

4.5 Reconnecting the Emulator

When the emulator is disconnected, use the following way for reconnection:

Select [Debug -> Connect] or click the [Connect] toolbar button (

). The emulator is connected.

Note: The emulator must be selected in the [Target] drop-down list box of the [Debug Settings]

dialog box (see figure 4.13, [Debug Settings] Dialog Box ([Target] Page)) that is opened
by selecting [Debug settings] from the [Debug] menu.

Rev. 1.00 Nov. 26, 2007 Page 76 of 230

REJ10J1766-0100

Section 4 Preparations for Debugging

4.6 Ending the Emulator

When using the toolchain, the emulator can be exited by using the following two methods:

 Canceling the connection of the emulator being activated
 Exiting the High-performance Embedded Workshop

(1) Canceling the connection of the emulator being activated

Select [Disconnect] from the [Debug] menu or click the [Disconnect] toolbar button (

(2) Exiting the High-performance Embedded Workshop

Select [Exit] from the [File] menu.

A message box is displayed. If necessary, click the [Yes] button to save a session. After
saving a session, the High-performance Embedded Workshop exits. If not necessary, click the
[No] button to exit the High-performance Embedded Workshop.

).

Figure 4.22 [Session has been modified] Message Box

Rev. 1.00 Nov. 26, 2007 Page 77 of 230

REJ10J1766-0100

Section 5 Debugging

Rev. 1.00 Nov. 26, 2007 Page 78 of 230

REJ10J1766-0100

Section 5 Debugging

Section 5 Debugging

This section describes the debugging operations and their related windows and dialog boxes.

5.1 Setting the Environment for Emulation

5.1.1 Opening the [Configuration] Dialog Box

Selecting [Setup -> Emulator -> System…] or clicking the [Emulator System] toolbar button
opens the [Configuration] dialog box.

5.1.2 [General] Page

Sets the emulator operation conditions. These settings will apply to the High-performance
Embedded Workshops for both CPU0 and CPU1.

(

)

Rev. 1.00 Nov. 26, 2007 Page 79 of 230

REJ10J1766-0100

Section 5 Debugging

Figure 5.1 [Configuration] Dialog Box ([General] Page)

Items that can be displayed in the sheet are listed below.

Rev. 1.00 Nov. 26, 2007 Page 80 of 230

REJ10J1766-0100