Renesas SH7641 Technical information

Add to my manuals
42 Pages

advertisement

Renesas SH7641 Technical information | Manualzz

To our customers,

Old Company Name in Catalogs and Other Documents

On April 1 st

, 2010, NEC Electronics Corporation merged with Renesas Technology

Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid

Renesas Electronics document. We appreciate your understanding.

Renesas Electronics website: http://www.renesas.com

April 1 st

, 2010

Renesas Electronics Corporation

Issued by: Renesas Electronics Corporation ( http://www.renesas.com

)

Send any inquiries to http://www.renesas.com/inquiry .

Notice

1. All information included in this document 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 Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website.

2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document.

No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others.

3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part.

4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples. You are fully responsible for the incorporation of these circuits, software, and information in the design of your equipment. Renesas Electronics assumes no responsibility for any losses incurred by you or third parties arising from the use of these circuits, software, or information.

5. When exporting the products or technology described in this document, you should comply with the applicable export control laws and regulations and follow the procedures required by such laws and regulations. You should not use Renesas

Electronics products or the technology described in this document for any purpose relating to military applications or use by the military, including but not limited to the development of weapons of mass destruction. Renesas Electronics products and technology may not be used for or incorporated into any products or systems whose manufacture, use, or sale is prohibited under any applicable domestic or foreign laws or regulations.

6. Renesas Electronics has used reasonable care in preparing the information included in this document, but Renesas Electronics does not warrant that such information is error free. Renesas Electronics assumes no liability whatsoever for any damages incurred by you resulting from errors in or omissions from the information included herein.

7. Renesas Electronics products are classified according to the following three quality grades: “Standard”, “High Quality”, and

“Specific”. The recommended applications for each Renesas Electronics product depends on the product’s quality grade, as indicated below. You must check the quality grade of each Renesas Electronics product before using it in a particular application. You may not use any Renesas Electronics product for any application categorized as “Specific” without the prior written consent of Renesas Electronics. Further, you may not use any Renesas Electronics product for any application for which it is not intended without the prior written consent of Renesas Electronics. Renesas Electronics shall not be in any way liable for any damages or losses incurred by you or third parties arising from the use of any Renesas Electronics product for an application categorized as “Specific” or for which the product is not intended where you have failed to obtain the prior written consent of Renesas Electronics. The quality grade of each Renesas Electronics product is “Standard” unless otherwise expressly specified in a Renesas Electronics data sheets or data books, etc.

“Standard”: Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment; home electronic appliances; machine tools; personal electronic equipment; and industrial robots.

“High Quality”: Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems; anticrime systems; safety equipment; and medical equipment not specifically designed for life support.

“Specific”: Aircraft; aerospace equipment; submersible repeaters; nuclear reactor control systems; medical equipment or systems for life support (e.g. artificial life support devices or systems), surgical implantations, or healthcare intervention (e.g. excision, etc.), and any other applications or purposes that pose a direct threat to human life.

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

9. Although Renesas Electronics endeavors to improve the quality and reliability of its products, semiconductor products have specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Further,

Renesas Electronics products are not subject to radiation resistance design. Please be sure to implement safety measures to guard them against the possibility of physical injury, and injury or damage caused by fire in the event of the failure of a

Renesas Electronics 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 appropriate measures. Because the evaluation of microcomputer software alone is very difficult, please evaluate the safety of the final products or system manufactured by you.

10. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas Electronics product. Please use Renesas Electronics products in compliance with all applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS

Directive. Renesas Electronics assumes no liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations.

11. This document may not be reproduced or duplicated, in any form, in whole or in part, without prior written consent of Renesas

Electronics.

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

(Note 1) “Renesas Electronics” as used in this document means Renesas Electronics Corporation and also includes its majorityowned subsidiaries.

(Note 2) “Renesas Electronics product(s)” means any product developed or manufactured by or for Renesas Electronics.

SuperH™ Family

E10A-USB Emulator

Additional Document for User’s Manual

SH7641 E10A-USB

HS7641KCU01HE

Renesas Microcomputer

Development Environment

System

SuperH™ Family / SH7600 Series

Supplementary Information on

Using the SH7641

Rev.1.0 2003.12

Cautions

Keep safety first in your circuit designs!

1. Renesas Technology Corp. puts the maximum effort into making semiconductor products better and more reliable, but there is always the possibility that trouble may occur with them.

Trouble with semiconductors may lead to personal injury, fire or property damage.

Remember to give due consideration to safety when making your circuit designs, with appropriate measures such as (i) placement of substitutive, auxiliary circuits, (ii) use of nonflammable material or (iii) prevention against any malfunction or mishap.

Notes regarding these materials

1. These materials are intended as a reference to assist our customers in the selection of the

Renesas Technology Corp. product best suited to the customer's application; they do not convey any license under any intellectual property rights, or any other rights, belonging to

Renesas Technology Corp. or a third party.

2. Renesas Technology Corp. assumes no responsibility for any damage, or infringement of any third-party's rights, originating in the use of any product data, diagrams, charts, programs, algorithms, or circuit application examples contained in these materials.

3. All information contained in these materials, including product data, diagrams, charts, programs and algorithms represents information on products at the time of publication of these materials, and are subject to change by Renesas Technology Corp. without notice due to product improvements or other reasons. It is therefore recommended that customers contact

Renesas Technology Corp. or an authorized Renesas Technology Corp. product distributor for the latest product information before purchasing a product listed herein.

The information described here may contain technical inaccuracies or typographical errors.

Renesas Technology Corp. assumes no responsibility for any damage, liability, or other loss rising from these inaccuracies or errors.

Please also pay attention to information published by Renesas Technology Corp. by various means, including the Renesas Technology Corp. Semiconductor home page

(http://www.renesas.com).

4. When using any or all of the information contained in these materials, including product data, diagrams, charts, programs, and algorithms, please be sure to evaluate all information as a total system before making a final decision on the applicability of the information and products.

Renesas Technology Corp. assumes no responsibility for any damage, liability or other loss resulting from the information contained herein.

5. Renesas Technology Corp. semiconductors are not designed or manufactured for use in a device or system that is used under circumstances in which human life is potentially at stake.

Please contact Renesas Technology Corp. or an authorized Renesas Technology Corp. product distributor when considering the use of a product contained herein for any specific purposes, such as apparatus or systems for transportation, vehicular, medical, aerospace, nuclear, or undersea repeater use.

6. The prior written approval of Renesas Technology Corp. is necessary to reprint or reproduce in whole or in part these materials.

7. If these products or technologies are subject to the Japanese export control restrictions, they must be exported under a license from the Japanese government and cannot be imported into a country other than the approved destination.

Any diversion or reexport contrary to the export control laws and regulations of Japan and/or the country of destination is prohibited.

8. Please contact Renesas Technology Corp. for further details on these materials or the products contained therein.

Contents

Section 1 Connecting the Emulator with the User System ............................... 1

1.1

Components of the Emulator ............................................................................................ 1

1.2

Connecting the Emulator with the User System ............................................................... 2

1.3

Installing the H-UDI Port Connector on the User System ................................................ 3

1.4

Pin Assignments of the H-UDI Port Connector ................................................................ 3

1.5

Recommended Circuit between the H-UDI Port Connector and the MPU ....................... 6

1.5.1

Recommended Circuit (36-Pin Type) .................................................................. 6

1.5.2

Recommended Circuit (14-Pin Type) .................................................................. 9

Section 2 Software Specifications when Using the SH7641 ............................ 13

2.1

Differences between the SH7641 and the Emulator ......................................................... 13

2.2

Specific Functions for the Emulator when Using the SH7641.......................................... 17

2.2.1

Break Condition Functions .................................................................................. 17

2.2.2

Trace Functions.................................................................................................... 19

2.2.3

Notes on Using the JTAG (H-UDI) Clock (TCK) and

AUD Clock (AUDCK)......................................................................................... 25

2.2.4

Notes on Setting the [Breakpoint] Dialog Box .................................................... 25

2.2.5

Notes on Setting the [Break Condition] Dialog Box and the BREAKCONDITION_ SET Command ........................................................ 26

2.2.6

Note on Setting the UBC_MODE Command ...................................................... 27

2.2.7

Performance Measurement Function ................................................................... 27 i

ii

Section 1 Connecting the Emulator with the User System

1.1

Components of the Emulator

Table 1.1 lists the components of the emulator.

Table 1.1 Components of the Emulator

Classification Component

Hardware

Emulator box

Appearance

User system interface cable

User system interface cable

USB cable

Quantity

1

1

1

1

Remarks

HS0005KCU01H:

Depth: 65.0 mm, Width: 97.0 mm,

Height: 20.0 mm, Mass: 72.9 g or

HS0005KCU02H:

Depth: 65.0 mm, Width: 97.0 mm,

Height: 20.0 mm, Mass: 73.7 g

14-pin type:

Length: 20 cm, Mass: 33.1 g

36-pin type:

Length: 20 cm, Mass: 49.2 g

(only for HS0005KCU02H)

Length: 150 cm, Mass: 50.6 g

Software

SH7641 E10A-USB emulator setup program,

SuperH

TM

Family

E10A-USB Emulator

User’s Manual,

Supplementary

Information on Using the SH7641*, and

Test program manual for HS0005KCU01H and HS0005KCU02H

1 HS0005KCU01SR,

HS0005KCU01HJ,

HS0005KCU01HE,

HS7641KCU01HJ,

HS7641KCU01HE,

HS0005TM01HJ, and

HS0005TM01HE

(provided on a CD-R)

Note: Additional document for the MPUs supported by the emulator is included. Check the target

MPU and refer to its additional document.

1

1.2

Connecting the Emulator with the User System

To connect the E10A-USB emulator (hereinafter referred to as the emulator), the H-UDI port connector must be installed on the user system to connect the user system interface cable. When designing the user system, refer to the recommended circuit between the H-UDI port connector and the MPU. In addition, read the E10A-USB emulator user's manual and hardware manual for the related device.

Table 1.2 shows the type number of the emulator, the corresponding connector type, and the use of

AUD function.

Table 1.2 Type Number, AUD Function, and Connector Type

Type Number

HS0005KCU02H

HS0005KCU01H, HS0005KCU02H

Connector

36-pin connector

14-pin connector

AUD Function

Available

Not available

The H-UDI port connector has the 36-pin and 14-pin types as described below. Use them according to the purpose of the usage.

1. 36-pin type (with AUD function)

The AUD trace function is supported. A large amount of trace information can be acquired in realtime. The window trace function is also supported for acquiring memory access in the specified range (memory access address or memory access data) by tracing.

2. 14-pin type (without AUD function)

The AUD trace function cannot be used because only the H-UDI function is supported. For tracing, only the internal trace function is supported. Since the 14-pin type connector is smaller than the 36-pin type (1/2.5), the area where the connector is installed on the user system can be reduced.

2

1.3

Installing the H-UDI Port Connector on the User System

Table 1.3 shows the recommended H-UDI port connectors for the emulator.

Table 1.3 Recommended H-UDI Port Connectors

Connector

36-pin connector

Type Number

DX10M-36S

DX10M-36SE,

DX10G1M-36SE

14-pin connector 2514-6002

Manufacturer

Hirose Electric Co., Ltd.

Minnesota Mining &

Manufacturing Ltd.

Specifications

Screw type

Lock-pin type

14-pin straight type

Note: When the 36-pin connector is used, do not connect any components under the H-UDI connector. When the 14-pin connector is used, do not install any components within 3 mm of the H-UDI port connector.

1.4

Pin Assignments of the H-UDI Port Connector

Figures 1.1 and 1.2 show the pin assignments of the 36-pin and 14-pin H-UDI port connectors, respectively.

Note: Note that the pin number assignments of the H-UDI port connector shown on the following pages differ from those of the connector manufacturer.

3

4

Pin

No.

Signal

1

2

3

4

5

6

AUDCK

GND

AUDATA0

GND

AUDATA1

GND

13

14

15

16

7

8

9

10

11

*2

12

AUDATA2

GND

AUDATA3

GND

/AUDSYNC

GND

NC

GND

NC

GND

Input/

Output *1

SH7641

Pin No.

Note

Output N1

Pin

No.

Signal

Output

Output

N4

P1

19

23

24

TMS

20

21

*2

22

*5

GND

/TRST

(GND)

TDI

GND

Output N3

Output

Output

N2

P4

Input/

Output

Input

Input

Input

25

26

27

*2

28

29

*4

30

31

*2

TDO

GND

/ASEBRKAK

GND

UVCC

GND

/RESETP

Output

Output

Output

Output

32

33

34

*3

GND

GND

GND

Output

*1

SH7641

Pin No.

R4

P2

P3

T1

N17

N20

Note

User reset

17

18

TCK

GND

Input R1 35

36

NC

GND

Notes: 1. Input to or output from the user system.

2. The slash (/) means that the signal is active-low.

3. The emulator monitors the GND signal of the user system and detects

whether or not the user system is connected.

4. If the VccQ pin is not connected to the UVCC, the I/O voltage of the user system

interface will be fixed to 3.3 V.

5. The /ASEMD0 pin must be 0 when the emulator is connected and 1 when the emulator

is not connected, respectively.

(1) When the emulator is used: /ASEMD0 = 0 (ASE mode)

(2) When the emulator is not used: /ASEMD0 = 1 (normal mode)

To allow the /ASEMD0 pin to be GND by connecting the user system interface cable,

connect pin 22 directly to the /ASEMD0 pin. Do not ground the pin.

φ

2.8

+0.2

0

2

4

Edge of the board

(connected to the connector)

φ

0.7

+0.1

0

36

H-UDI port connector (top view)

4.09

1

3

1.27

21.59

37.61

43.51

: Pattern inhibited area

H-UDI port connector (top view)

35

(Pin 1 mark)

M2.6 x 0.45

H-UDI port connector (front view)

Unit: mm

Figure 1.1 Pin Assignments of the H-UDI Port Connector (36 Pins)

6

7

4

5

8

Pin No.

Signal

1 TCK

2

3

/TRST

TDO

/ASEBRKAK

TMS

TDI

/RESETP

N.C.

9

11

10, 12, and 13

14

(GND)

UVCC

GND

GND

*2

*2

*2

*5

*4

*3

Input/

Output* 1

Input

Input

Output

Output

Input

Input

I/O

Output

Output

SH7641

Pin No.

R1

P2

T1

N17

R4

P3

N20

Note

User reset

Notes: 1. Input to or output from the user system.

2. The slash (/) means that the signal is active-low.

3. The emulator monitors the GND signal of the user

system and detects whether or not the user system

is connected.

4. If the VccQ pin is not connected to the UVCC, the I/O voltage

of the user system interface will be fixed to 3.3 V.

5. The /ASEMD0 pin must be 0 when the emulator is connected

and 1 when the emulator is not connected, respectively.

(1) When the emulator is used: /ASEMD0 = 0 (ASE mode)

(2) When the emulator is not used: /ASEMD0 = 1 (normal mode)

To allow the /ASEMD0 pin to be GND by connecting the user system

interface cable, connect pin 9 directly to the /ASEMD0 pin. Do not ground the pin.

Pin 1 mark

H-UDI port connector (top view)

25.0

23.0

6 x 2.54 = 15.24

(2.54)

H-UDI port connector

(top view)

0.45

Pin 1 mark

Unit: mm

Figure 1.2 Pin Assignments of the H-UDI Port Connector (14 Pins)

5

1.5

Recommended Circuit between the H-UDI Port Connector and the

MPU

1.5.1

Recommended Circuit (36-Pin Type)

Figure 1.3 shows a recommended circuit for connection between the H-UDI and AUD port connectors (36 pins) and the MPU when the emulator is in use. Figure 1.4 shows a circuit for connection when UVCC is not connected.

Notes: 1. Do not connect anything to the N.C. pins of the H-UDI port connector.

2.

The /ASEMD0 pin must be 0 when the emulator is connected and 1 when the emulator is not connected, respectively.

(1) When the emulator is used: /ASEMD0 = 0 (ASE mode)

(2) When the emulator is not used: /ASEMD0 = 1 (normal mode)

Figures 1.3 and 1.4 show examples of circuits that allow the /ASEMD0 pin to be

GND (0) whenever the emulator is connected by using the user system interface cable.

When the /ASEMD0 pin is changed by switches, etc., ground pin 22. Do not connect this pin to the /ASEMD0 pin.

3.

When a network resistance is used for pull-up, it may be affected by a noise. Separate

TCK from other resistances.

4.

The pattern between the H-UDI port connector and the MPU must be as short as possible. Do not connect the signal lines to other components on the board.

5.

When the power supply of the user system is turned off, supplying VccQ of the user system to the UVCC pin reduces the leakage current from the emulator to the user system. A level shifter that is activated by the internal power supply or user power supply (changed by the switch) is installed in the interface circuit of the emulator. If the user power is supplied to the UVCC pin, the level shifter is not activated as long as no user power is supplied. When the power supply of the user system is turned off, no current flows from the user interface. The I/O voltage level of the user system interface can be the same as that of the VccQ. To operate the emulator with low voltage (lower than 3.3 V), the VccQ must be supplied to the UVCC pin. Make the emulator’s switch settings so that the VccQ will be supplied (SW2 = 1 and SW3 = 1)

(as shown in figure 1.3).

6.

The resistance values shown in the figures are recommended.

7.

For the pin processing in cases where the emulator is not used, refer to the hardware manual of the related MPU.

6

When the circuit is connected as shown in figure 1.3, the switches of the emulator are set as SW2

= 1 and SW3 = 1. For details, refer to section 3.8, Setting the DIP Switches, in the Debugger Part of the SuperH TM Family E10A-USB Emulator User’s Manual.

H-UDI port connector

(36-pin type)

2

4

6

8

10

12

14

16

18

20

22

24

26

28

30

32

34

36

1

GND AUDCK

3

GND AUDATA0

5

GND AUDATA1

7

GND AUDATA2

9

GND AUDATA3

11

GND AUDSYNC

GND N.C.

13

N.C.

15

GND

17

GND TCK

GND TMS

19

(GND)

GND

GND

GND

GND

GND

GND

GND

21

TRST

TDI

23

TDO

ASEBRKAK

27

29

UVCC

25

31

RESET

33

GND

35

N.C.

VccQ

VccQ = 3.3 V (I/O power supply)

Pulled-up at 4.7 k

or more (all)

VccQ VccQ VccQ VccQ VccQ

SH7641

AUDCK

AUDATA0

AUDATA1

AUDATA2

AUDATA3

AUDSYNC

1 k

Reset signal

TCK

TMS

TRST

TDI

TDO

ASEBRKAK

RESETP

ASEMD0

User system

Figure 1.3 Recommended Circuit for Connection between the H-UDI Port Connector and

MPU (36-Pin Type)

7

When the circuit is connected as shown in figure 1.4, the switches of the emulator are set as SW2

= 0 and SW3 = 1. For details, refer to section 3.8, Setting the DIP Switches, in the Debugger Part of the SuperH TM Family E10A-USB Emulator User’s Manual.

H-UDI port connector

(36-pin type)

2

4

6

8

10

12

14

16

18

20

22

24

26

28

30

32

34

36

GND AUDCK

1

GND

3

AUDATA0

AUDATA1

5

GND

GND AUDATA2

7

GND AUDATA3

9

11

GND AUDSYNC

GND

N.C.

13

GND N.C.

15

GND TCK

17

GND TMS

19

(GND)

GND

GND

GND

GND

GND

GND

GND

TRST

21

TDI

23

TDO

N.C.

25

ASEBRKAK

27

29

31

RESET

33

GND

N.C.

35

VccQ = 3.3 V (I/O power supply)

Pulled-up at 4.7 k

or more (all)

VccQ VccQ VccQ VccQ VccQ

SH7641

AUDCK

AUDATA0

AUDATA1

AUDATA2

AUDATA3

AUDSYNC

1 k

Reset signal

TCK

TMS

TRST

TDI

TDO

ASEBRKAK

RESETP

ASEMD0

User system

Figure 1.4 Circuit for Connection between the H-UDI Port Connector and MPU when the

Emulator is in Use (36-Pin Type UVCC Not Connected*)

Note: When UVCC is not connected and the user system is turned off, note that the leakage current flows from the emulator to the user system.

8

1.5.2

Recommended Circuit (14-Pin Type)

Figure 1.5 shows a recommended circuit for connection between the H-UDI and AUD port connectors (14 pins) and the MPU when the emulator is in use. Figure 1.6 shows a circuit for connection when UVCC is not connected.

Notes: 1. Do not connect anything to the N.C. pins of the H-UDI port connector.

2.

The /ASEMD0 pin must be 0 when the emulator is connected and 1 when the emulator is not connected, respectively.

(1) When the emulator is used: /ASEMD0 = 0 (ASE mode)

(2) When the emulator is not used: /ASEMD0 = 1 (normal mode)

Figures 1.5 and 1.6 show examples of circuits that allow the /ASEMD0 pin to be

GND (0) whenever the emulator is connected by using the user system interface cable.

When the /ASEMD0 pin is changed by switches, etc., ground pin 9. Do not connect this pin to the /ASEMD0 pin.

3.

When a network resistance is used for pull-up, it may be affected by a noise. Separate

TCK from other resistances.

4.

The pattern between the H-UDI port connector and the MPU must be as short as possible. Do not connect the signal lines to other components on the board.

5.

When the power supply of the user system is turned off, supplying VccQ of the user system to the UVCC pin reduces the leakage current from the emulator to the user system. A level shifter that is activated by the internal power supply or user power supply (changed by the switch) is installed in the interface circuit of the emulator. If the user power is supplied to the UVCC pin, the level shifter is not activated as long as no user power is supplied. When the power supply of the user system is turned off, no current flows from the user interface. The I/O voltage level of the user system interface can be the same as that of the VccQ. To operate the emulator with low voltage (lower than 3.3 V), the VccQ must be supplied to the UVCC pin. Make the emulator’s switch settings so that the VccQ will be supplied (SW2 = 1 and SW3 = 1)

(as shown in figure 1.5).

6.

The resistance values shown in the figures are recommended.

7.

For the pin processing in cases where the emulator is not used, refer to the hardware manual of the related MPU.

9

When the circuit is connected as shown in figure 1.5, the switches of the emulator are set as SW2

= 1 and SW3 = 1. For details, refer to section 3.8, Setting the DIP Switches, in the Debugger Part of the SuperH TM Family E10A-USB Emulator User’s Manual.

VccQ

VccQ = 3.3 V (I/O power supply)

Pulled-up at 4.7 k

or more (all)

VccQ VccQ VccQ VccQ VccQ

9

H-UDI port connector

(14-pin type)

TCK

1

(GND) TRST

2

10

GND TDO

3

4

ASEBRKAK

12

GND TMS

5

13

GND TDI

6

14

GND RESET

7

N.C.

8

UVCC

11 1 k

SH7641

TCK

TRST

TDO

ASEBRKAK

TMS

TDI

RESETP

Reset signal

ASEMD0

User system

Figure 1.5 Recommended Circuit for Connection between the H-UDI Port Connector and

MPU when the Emulator is in Use (14-Pin Type UVCC Connected)

10

When the circuit is connected as shown in figure 1.6, the switches of the emulator are set as SW2

= 0 and SW3 = 1. For details, refer to section 3.8, Setting the DIP Switches, in the Debugger Part of the SuperH TM Family E10A-USB Emulator User’s Manual.

VccQ = 3.3 V (I/O power supply)

Pulled-up at 4.7 k

or more (all)

VccQ VccQ VccQ VccQ VccQ

9

H-UDI port connector

(14-pin type)

TCK

1

(GND) TRST

2

10

GND TDO

3

4

ASEBRKAK

12

GND TMS

5

13

GND TDI

6

14

GND RESET

7

8

N.C.

N.C.

11

1 k

SH7641

TCK

TRST

TDO

ASEBRKAK

TMS

TDI

RESETP

Reset signal

ASEMD0

User system

Figure 1.6 Circuit for Connection between the H-UDI Port Connector and MPU when the

Emulator is in Use (14-Pin Type UVCC Not Connected*)

Note: When UVCC is not connected and the user system is turned off, note that the leakage current flows from the emulator to the user system.

11

12

Section 2 Software Specifications when Using the SH7641

2.1

Differences between the SH7641 and the Emulator

1. When the emulator system is initiated, it initializes the general registers and part of the control registers as shown in table 2.1. The initial values of the actual SH7641 registers are undefined.

When the emulator is initiated from the workspace, a value to be entered is saved in a session.

Table 2.1 Register Initial Values at Emulator Link Up

MACH

MACL

PR

SPC

SSR

RS

RE

MOD

Register

R0 to R14

R15 (SP)

R0_BANK to R7_BANK

PC

SR

GBR

VBR

A0G, A1G

A0, A1

X0, X1

Y0, Y1

M0, M1

DSR

Emulator at Link Up

H'00000000

H'A0000000

H'00000000

H'A0000000

H'700000F0

H'00000000

H'00000000

H'00000000

H'00000000

H'00000000

H'00000000

H'000000F0

H'00000000

H'00000000

H'00000000

H'00000000

H'00000000

H'00000000

H'00000000

H'00000000

H'00000000

2. The emulator uses the H-UDI; do not access the H-UDI.

13

3. Low-Power States (Sleep, Software Standby, and Module Standby)

For low-power consumption, the SH7641 has sleep, software standby, and module standby states.

The sleep, software standby, and module standby states are switched using the SLEEP instruction. When the emulator is used, only the sleep state can be cleared with either the normal clearing function or with the [STOP] button, and a break will occur.

Note: The memory must not be accessed or modified in sleep state.

4. Reset Signals

The SH7641 reset signals are only valid during emulation started with clicking the GO or

STEP-type button. If these signals are enabled on the user system in command input wait state, they are not sent to the SH7641.

Note: Do not break the user program when the /RESETP, /BREQ, or /WAIT signal is being low.

A TIMEOUT error will occur. If the /WAIT or /BREQ signal is fixed to low during break, a TIMEOUT error will occur at memory access.

5. Direct Memory Access Controller (DMAC)

The DMAC operates even when the emulator is used. When a data transfer request is generated, the DMAC executes DMA transfer.

6. Memory Access during User Program Execution

When a memory is accessed from the memory window, etc. during user program execution, the user program is resumed after it has stopped in the E10A-USB emulator to access the memory. Therefore, realtime emulation cannot be performed.

The stopping time of the user program is as follows:

Environment:

Host computer: 800 MHz (Pentium

®

III)

SH7641: 60 MHz (CPU clock)

JTAG clock: 10 MHz (TCK clock)

When a one-byte memory is read from the command-line window, the stopping time will be about 45 ms.

7. Memory Access during User Program Break

The emulator can download the program for the flash memory area (refer to section 6.22,

Download Function to the Flash Memory Area, in the Debugger Part of the SuperH

TM

Family

E10A Emulator User’s Manual). Other memory write operations are enabled for the RAM area. Therefore, an operation such as memory write or BREAKPOINT should be set only for the RAM area.

14

8. Cache Operation during User Program Break

When cache is enabled, the emulator accesses the memory by the following methods:

At memory write: Writes through the cache, then writes to the memory.

At memory read: Does not change the cache write mode that has been set.

Therefore, when memory read or write is performed during user program break, the cache state will be changed.

9. Ports C and J

The AUD and H-UDI pins are multiplexed as shown below.

Table 2.2 Multiplex Functions

Port

C

J

J

J

J

Function 1

PTC13 (input/output)

*1

PTJ12 (input/output)

*2

PTJ11 (input/output)

*2

PTJ10 (input/output)

*2

PTJ9 (input/output)

*2

PTJ8 (input/output)

*2

Function 2

/ASEBRKAK (H-UDI)

AUDSYNC (AUD)

AUDATA3 (AUD)

AUDATA2 (AUD)

AUDATA1 (AUD)

J AUDATA0 (AUD)

Notes: 1. PTC13 cannot be used when the emulator is used.

2. Function 1 can be used when the AUD pins of the device are not connected to the emulator. Note that the emulator setting should be made so that function 2 would be forcibly used during activation. If function 1 is to be used, the setting should be made by the pin function controller.

10. UBC

When [User] is specified in the [UBC mode] list box in the [Configuration] dialog box, the

UBC can be used in the user program.

Do not use the UBC in the user program as it is used by the emulator when [EML] is specified in the [UBC mode] list box in the [Configuration] dialog box.

11. MFI Boot Mode

When the MFI boot mode is used, be sure to allocate the boot program from the top of

MFRAM.

12. Loading Sessions

Information in [JTAG clock] of the [Configuration] dialog box cannot be recovered by loading sessions. Thus the TCK value will be as follows:

When HS0005KCU01H or HS0005KCU02H is used: TCK = 2.5 MHz

15

13. [IO] Window

Display and modification

Do not change values of the User Break Controller because it is used by the emulator.

For each watchdog timer register, there are two registers to be separately used for write and read operations.

Table 2.3 Watchdog Timer Register

Register Name

WTCSR(W)

WTCNT(W)

WTCSR(R)

WTCNT(R)

Usage

Write

Write

Read

Read

Register

Watchdog timer control/status register

Watchdog timer counter

Watchdog timer control/status register

Watchdog timer counter

The watchdog timer operates only when the user program is executed. Do not change the value of the frequency change register in the [IO] window or [Memory] window.

The internal I/O registers can be accessed from the [IO] window. However, note the following when accessing the SDMR register of the bus-state controller. Before accessing the SDMR register, specify addresses to be accessed in the I/O-register definition file

(SH7641.IO) and then activate the HEW. After the I/O-register definition file is created, the MPU’s specification may be changed. If each I/O register in the I/O-register definition file differs from addresses described in the hardware manual, change the I/O-register definition file according to the description in the hardware manual. The I/O-register definition file can be customized depending on its format. Note that, however, the E10A emulator does not support the bit-field function.

Verify

In the [IO] window, the verify function of the input value is disabled.

14. Illegal Instructions

If illegal instructions are executed by STEP-type commands, the emulator cannot go to the next program counter.

16

2.2

Specific Functions for the Emulator when Using the SH7641

The SH7641 does not support the following functions:

MMU-related functions (The SH7641 does not mount the MMU.)

VPMAP-related command

Virtual and Physical specification in the [Configuration] window

Virtual and Physical specification on the command-line function

Virtual and Physical specification in the [Breakpoint] window

LDTLB instruction execution break function

MEMORYAREA_SET command

In the SH7641, a reset must be input when the emulator is activated. Do not use the activation method described in section 3.11 in the SuperH TM Family E10A-USB Emulator User’s Manual.

2.2.1

Break Condition Functions

In addition to BREAKPOINT functions, the emulator has Break Condition functions. Three types of conditions can be set under Break Condition 1, 2, 3. Table 2.4 lists these conditions of Break

Condition.

17

Table 2.4 Types of Break Conditions

Break Condition Type

Address bus condition (Address)

Data bus condition (Data)

X-Bus or Y-Bus condition (Address and data)

Bus state condition

(Bus State)

Internal I/O break condition

Count

Description

Breaks when the SH7641 address bus value or the program counter value matches the specified value.

Breaks when the SH7641 data bus value matches the specified value. Byte, word, or longword can be specified as the access data size.

Breaks when the X-Bus or Y-Bus address bus or data bus matches the specified value.

There are two bus state condition settings:

Read/Write condition: Breaks when the SH7641 RD or

RDWR signal level matches the specified condition.

Bus state condition: Breaks when the operating state in an

SH7641 bus cycle matches the specified condition.

Types of buses that can be specified are listed below.

L-bus (CPU-ALL): Indicates an instruction fetch and data access, including a hit to the cache memory.

L-bus (CPU-Data): Indicates a data access by the CPU, including a hit to the cache memory.

I-bus (CPU.DMA): Indicates a CPU cycle when the cache memory is not hit, and a data access by the

DMA.

Breaks when the SH7641 accesses the internal I/O.

Breaks when the conditions set are satisfied the specified number of times.

Note: When U-RAM or X/Y-RAM is accessed from the P0 space, the I-bus must be selected, and when accessed from the P2 space, the L-bus must be selected. When cache fill cycle is acquired, the I-bus must be selected.

18

Table 2.5 lists the combinations of conditions that can be set under Break Condition 1, 2, 3.

Table 2.5 Dialog Boxes for Setting Break Conditions

Type

Dialog Box

[Break Condition 1] dialog box

Address

Bus Condition

Data Bus

Condition

(Address) (Data)

O O

[Break Condition 2] dialog box

O

X

Bus State

Condition

(Bus Status)

O

O

Count

Condition

(Count)

O

X

[Break Condition 3] dialog box

X X X X

Notes: 1. O: Can be set in the dialog box.

X: Cannot be set in the dialog box.

2. For Break Condition 2, X-bus and Y-bus conditions cannot be specified.

Internal

I/O Break

X

X

O

2.2.2

Trace Functions

The emulator supports the trace functions listed in table 2.6.

Table 2.6 Trace Functions

Function

Branch trace

Range memory access trace

Software trace

Internal Trace

Supported (eight branches)

Not supported

Not supported

Table 2.7 shows the type numbers that the AUD function can be used.

Table 2.7 Type Number and AUD Function

Type Number

HS0005KCU01H

HS0005KCU02H

AUD Function

Not supported

Supported

AUD Trace

Supported

Supported

Supported

19

AUD Trace Functions: This function is operational when the AUD pin of the device is connected to the emulator. Table 2.8 shows the AUD trace acquisition mode that can be set in each trace function.

Table 2.8 AUD Trace Acquisition Mode

Type

Continuous trace occurs

Trace buffer full

Mode Description

Realtime trace

Non realtime trace When the next branch occurs while the trace information is being output, the CPU stops operations until the information is output. The user program is not executed in realtime.

Trace continue

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.

Trace stop

This function overwrites the latest trace information to store the oldest trace information.

After the trace buffer becomes full, the trace information is no longer acquired. The user program is continuously executed.

20

To set the AUD trace acquisition mode, click the [Trace] window with the right mouse button and select [Setting] from the pop-up menu to display the [Acquisition] dialog box. The AUD trace acquisition mode can be set in the [AUD mode1] or [AUD mode2] group box in the [Trace mode] page of the [Acquisition] dialog box.

Figure 2.1 [Trace mode] Page

When the AUD trace function is used, select the [AUD function] radio button in the [Trace type] group box of the [Trace mode] page.

21

(a) Branch Trace Function

The branch source and destination addresses and their source lines are displayed.

Branch trace can be acquired by selecting the [Branch trace] check box in the [AUD function] group box of the [Trace mode] page.

The branch type can be selected in the [AUD Branch trace] page.

22

Figure 2.2 [AUD Branch trace] Page

(b) Window Trace Function

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

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

[Setting Method]

(i) Select the [Channel A] and [Channel B] check boxes in the [AUD function] group box of the [Trace mode] page. Each channel will become valid.

(ii) Open the [Window trace] page and specify the bus cycle and memory range that are to be

set for each channel.

Figure 2.3 [Window trace] Page

Notes: 1. When the [L-bus] or [I-bus] radio button is selected, the following bus cycles will be traced.

L-bus: A bus cycle generated by the CPU is acquired. A bus cycle is also acquired when the cache has been hit.

I-bus: A bus cycle generated by the CPU or DMA is acquired. A bus cycle is not acquired when the cache has been hit. The address information acquired by the Ibus is 28 bits and the upper 4 bits are displayed as ‘*’. The source cannot be displayed in the [Trace] window.

When U-RAM or X/Y-RAM is accessed from the P0 space, the I-bus must be selected, and when accessed from the P2 space, the L-bus must be selected. When a cache fill cycle is acquired, I-bus must be selected.

2. Address setting when X/Y-bus is selected

To trace both the X/Y-bus when the X/Y-bus is accessed at the same time, the X-bus condition must be set in channel A, and the Y-bus condition must be set in channel B.

23

(c) Software Trace Function

Note: This function can be supported with SHC/C++ compiler (manufactured by Renesas

Technology Corp.; including OEM and bundle products) V7.0 or later.

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

When the load module is downloaded on the target system and is executed while a software trace function is valid, the PC value that has executed the Trace(x) function, the general register value for x, and the source lines are displayed.

To activate the software trace function, select the [Software trace] check box in the [AUD function] group box of the [Trace mode] page.

Notes on AUD Trace:

1. When the trace display is performed during user program execution, the mnemonics, operands, or source is not displayed.

2. The AUD trace function outputs the differences between newly output branch source addresses and previously output branch source addresses. The window trace function outputs the differences between newly output addresses and previously output addresses. If the previous branch source address is the same as the upper 16 bits, the lower 16 bits are output. If it matches the upper 24 bits, the lower 8 bits are output. If it matches the upper 28 bits, the lower

4 bits are output.

The emulator regenerates the 32-bit address from these differences and displays it in the

[Trace] window. If the emulator cannot display the 32-bit address, it displays the difference from the previously displayed 32-bit address.

3. If the 32-bit address cannot be displayed, the source line is not displayed.

4. In the emulator, when multiple loops are performed to reduce the number of AUD trace displays, only the IP counts up.

5. In the emulator, the maximum number of trace displays is 65534 lines (32767 branches).

However, the maximum number of trace displays differs according to the AUD trace information to be output. Therefore, the above pointers cannot be always acquired.

6. The AUD trace acquisition is not available when [User] is selected in the [UBC mode] list box of the [Configuration] dialog box. In this case, close the [Trace] window.

7. Do not use the AUD full-trace mode for the VIO function.

8. If a completion-type exception occurs during exception branch acquisition, the next address to the address in which an exception occurs is acquired.

24

Internal Trace Function: This function is activated by selecting the [Internal trace] radio button in the [Trace type] group box of the [Trace mode] page. This function traces and displays the branch instructions. The branch source address and branch destination address for the eight latest branch instructions are displayed. See figure 2.1, [Trace mode] Page.

Notes: 1. If an interrupt is generated at the program execution start or end, including a step operation, the emulator address may be acquired. In such a case, the following message will be displayed. Ignore this address because it is not a user program address.

*** EML ***

2. If a completion-type exception occurs during exception branch acquisition, the next address to the address in which an exception occurs is acquired.

3. Trace information cannot be acquired for the following branch instructions:

The BF and BT instructions whose displacement value is 0

Branch to H'A0000000 by reset

4. The internal trace acquisition is not available when [User] is selected in the [UBC mode] list box of the [Configuration] dialog box. In this case, close the [Trace] window.

2.2.3

Notes on Using the JTAG (H-UDI) Clock (TCK) and AUD Clock (AUDCK)

1. Set the JTAG clock (TCK) frequency to lower than the frequency of the SH7641 peripheral module clock (CKP).

2. Set the AUD clock (AUDCK) frequency to 50 MHz or lower. If the frequency is higher than

50 MHz, the emulator will not operate normally.

2.2.4

Notes on Setting the [Breakpoint] Dialog Box

1. When an odd address is set, the next lowest even address is used.

2. A BREAKPOINT is accomplished by replacing instructions of the specified address.

Accordingly, it can be set only to the internal RAM area. However, a BREAKPOINT cannot be set to the following addresses:

An area other than CS0 to CS6 and the internal RAM

An instruction in which Break Condition 2 is satisfied

A slot instruction of a delayed branch instruction

3. During step operation, BREAKPOINTs are disabled.

4. Conditions set at Break Condition 2 are disabled when an instruction to which a

BREAKPOINT has been set is executed. Do not set a BREAKPOINT to an instruction in which Break Condition 2 is satisfied.

25

5. When execution resumes from the address where a BREAKPOINT is specified, single-step operation is performed at the address before execution resumes. Therefore, realtime operation cannot be performed.

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

7. When a BREAKPOINT is set to the cacheable area, the cache block containing the

BREAKPOINT address is filled immediately before and after user program execution.

8. Note on DSP repeat loop:

A BREAKPOINT is equal to a branch instruction. In some DSP repeat loops, branch instructions cannot be set. For these cases, do not set BREAKPOINTs. Refer to the hardware manual of the target MPU for details.

9. If an address of a BREAKPOINT cannot be correctly set in the ROM or flash memory area, a mark l will be displayed in the [BP] area of the address on the [Source] or [Disassembly] window by refreshing the [Memory] window, etc. after Go execution. However, no break will occur at this address. When the program halts with the break condition, the mark l disappears.

2.2.5

Notes on Setting the [Break Condition] Dialog Box and the BREAKCONDITION_

SET Command

1. When [Go to cursor], [Step In], [Step Over], or [Step Out] is selected, the settings of Break

Condition 2 are disabled.

2. Break Condition 2 is disabled when an instruction to which a BREAKPOINT has been set is executed. Accordingly, do not set a BREAKPOINT to an instruction which satisfies Break

Condition 2.

3. When a Break Condition is satisfied, emulation may stop after two or more instructions have been executed.

4. If a PC break address condition is set to the slot instruction after a delayed branch instruction, user program execution cannot be terminated before the slot instruction execution; execution stops before the branch destination instruction.

5. Break Condition 1,2 is used as the measurement range in the performance measurement function when [PA-1 start point] and [PA-1 end point] are displayed on the [Action] part in the

[Break condition] sheet of the [Eventpoint] window. This applies when the Break Condition is displayed with the BREAKCONDITION_DISPLAY command in the command-line function.

In this case, a break does not occur when Break Condition 1,2 is satisfied.

6. A break will not occur with the execution counts specified on the execution of the multi-step instruction.

26

2.2.6

Note on Setting the UBC_MODE Command

In the [Configuration] dialog box, if [User] is set while the [UBC mode] list box has been set, the

STEP-type commands that use Break Condition 2 for implementation cannot be used.

2.2.7

Performance Measurement Function

The emulator supports the performance measurement function.

1. Setting the performance measurement conditions

To set the performance measurement conditions, use the [Performance Analysis] dialog box and the PERFORMANCE_SET command. When any line on the [Performance Analysis] window is clicked with the right mouse button, the popup menu is displayed and the

[Performance Analysis] dialog box is displayed by selecting [Setting].

Note: For the command line syntax, refer to the online help.

(a) Specifying the measurement start/end conditions

The measurement start/end conditions are specified in the [Mode] drop-down list box in the

[Performance Analysis] dialog box. Three conditions can be set as shown in table 2.9.

Table 2.9 Conditions Specified in [Mode]

Item

Normal break

Description

Measurement is started by executing a program and ended when a break condition is satisfied.

Break Condition 1 -> 2 Measurement is started from the satisfaction of the condition set in

Break Condition 1 to the satisfaction of the condition set in Break

Condition 2.

Break Condition 2 -> 1 Measurement is started from the satisfaction of the condition set in

Break Condition 2 to the satisfaction of the condition set in Break

Condition 1.

27

Figure 2.4 [Performance Analysis] Dialog Box

(b) Measurement range

One of the following ranges can be specified. This depends on the item selected for [Mode] in the [Performance Analysis] dialog box.

1. From the start to the end of the user program execution (When Normal Break is selected for [Mode])

2. From the satisfaction of the condition set in Break Condition 1 to the satisfaction of the condition set in Break Condition 2 (When Break condition 1->2 is selected for [Mode])

3. From the satisfaction of the condition set in Break Condition 2 to the satisfaction of the condition set in Break Condition 1 (When Break condition 2->1 is selected for [Mode])

(In the second and third ranges, [PA-1 start point] and [PA-1 end point] are displayed on the

[Action] part in the [Break condition] sheet of the [Eventpoint] window.)

For measurement tolerance,

The measured value includes tolerance.

Tolerance will be generated before or after a break.

For details, see table 2.11.

28

Notes: 1. When the second and third ranges are specified, execute the user program after the measurement start condition is set to Break Condition 1 (or Break Condition 2) and the measurement end condition to Break Condition 2 (or Break Condition 1).

2.

Step operation is not possible when Break condition 1->2 or Break condition 2->1 is selected for the PERFORMANCE_SET command or in [Mode] of the [Performance

Analysis] dialog box.

3.

When Break condition 1->2 or Break condition 2->1 is selected in [Mode] of the

[Performance Analysis] dialog box, specify one or more items for measurement.

When there is no item, the error message “Measurement item does not have specification. Please set up a measurement item.” will be displayed. When no item is specified for the PERFORMANCE_SET command, the settings of Break condition 1

->2 or Break condition 2->1 will be an error.

(c) Measurement item

Items are measured with [Channel 1 to 4] in the [Performance Analysis] dialog box.

Maximum four conditions can be specified at the same time. Table 2.10 shows the measurement items (Options in table 2.10 are parameters for <mode> of the

PERFORMANCE_SET command. They are displayed for CONDITION in the [Performance

Analysis] window).

29

Table 2.10 Measurement Item

Selected Name

Disabled

Elapsed time

Number of execution states

Branch instruction counts

Number of execution instructions

DSP-instruction execution counts

Instruction/data conflict cycle

Other conflict cycles than instruction/data

Exception/interrupt counts

Data-TLB miss cycle

Instruction-TLB miss cycle

Interrupt counts

Number of BL=1 instructions

Number of MD=1 instructions

Instruction cache-miss counts

Data cache-miss counts

Instruction fetch stall

Data access stall

Instruction cache-miss stall

Data cache-miss stall

Cacheable access stall

X/Y-RAM access stall

URAM access stall

Instruction/data access stall cycle

Other access cycles than instruction/data

Non-cacheable area access cycle

Non-cacheable area instruction access cycle

Non-cacheable area data access cycle

Cacheable area access cycle

Option

None

AC

VS

I

BT

DI (Devices incorporating the DSP function can only be measured.)

MAC

OC

EA

MTS (Devices incorporating the MMU function can only be measured.)

ITS (Devices incorporating the MMU function can only be measured.)

INT

BL1

MD1

IC

DC

IF

DA

ICS

DCS

CS

XYS (Devices incorporating the X/Y memory can only be measured.)

US (Devices incorporating the U memory can only be measured.)

MA

NMA

NCC

NCI

NCD

CC

30

Table 2.10 Measurement Item (cont)

Selected Name

Cacheable area instruction access cycle

Cacheable area data access cycle

Access counts other than instruction/data

Non-cacheable area access counts

Non-cacheable area instruction access counts

Non-cacheable area data access counts

Cacheable area access counts

Cacheable area instruction access counts

Cacheable area data access counts

Option

CIC

CDC

NAM

NCN

NCIN

NCDN

CN

CIN

CDN

Each measurement condition is also counted when conditions in table 2.11 are generated.

Table 2.11 Performance Measurement Conditions to be Counted

Measurement Condition Notes

Cache-on counting

Branch count

Accessing the non-cacheable area is counted less than the actual number of cycles and counts. Accessing the cacheable, X/Y-RAM, and U-RAM areas is counted more than the actual number of cycles and counts.

The counter value is incremented by 2. This means that two cycles are valid for one branch.

Notes: 1. In the non realtime trace mode of the AUD trace, normal counting cannot be performed because the generation state of the stall or the execution cycle is changed.

2. Since the clock source of the counter is the CPU clock, counting also stops when the clock halts in the sleep mode.

2. Displaying the measured result

The measured result is displayed in the [Performance Analysis] window or the

PERFORMANCE_ANALYSIS command with hexadecimal (32 bits).

Note: If a performance counter overflows as a result of measurement, “********” will be displayed.

31

3. Initializing the measured result

To initialize the measured result, select [Initialize] from the popup menu in the [Performance

Analysis] window or specify INIT with the PERFORMANCE_ANALYSIS command.

32

SuperH

Family E10A-USB Emulator

Additional Document for User's Manual

Supplementary Information on Using the SH7641

Publication Date: Rev.1.00, December 3, 2003

Published by: Sales Strategic Planning Div.

Renesas Technology Corp.

Edited by: Technical Documentation & Information Department

Renesas Kodaira Semiconductor Co., Ltd.

2003 Renesas Technology Corp. All rights reserved. Printed in Japan.

SuperH™ Family E10A-USB Emulator

Additional Document for User’s Manual

1753, Shimonumabe, Nakahara-ku, Kawasaki-shi, Kanagawa 211-8668 Japan

REJ10B0070-0100H

advertisement

Was this manual useful for you? Yes No
Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project