Renesas Emulation Pod M3062NT3-RPD-E User Manual

Loading...

To our customers,

Old Company Name in Catalogs and Other Documents

On April 1st, 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 1st, 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.

Manual User’s

M3062NT3-RPD-E

User’s Manual

Emulation Pod for M16C/62 Group M16C/62N and M16C/30 Group M16C/30L

Rev.1.00 2003.06

*IC61-1004-051 is a trademark of Yamaichi Electronics Co., Ltd.

*NQPACK, YQPACK, YQSOCKET, YQ-GUIDE, HQPACK, TQPACK and TQSOCKET are trademarks of Tokyo Eletech Corporation.

Keep safety first in your circuit designs!

Renesas Technology Corporation and Renesas Solutions Corporation put 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

These materials are intended as a reference to assist our customers in the selection of the Renesas Technology 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 Corporation, Renesas Solutions Corporation or a third party.

Renesas Technology Corporation and Renesas Solutions Corporation assume 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.

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 Corporation and Renesas Solutions Corporation without notice due to product improvements or other reasons. It is therefore recommended that customers contact

Renesas Technology Corporation, Renesas Solutions Corporation or an authorized Renesas Technology 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 Corporation and Renesas Solutions Corporation assume 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 Corporation and Renesas Solutions Corporation by various means, including the Renesas home page (http://www.renesas.com).

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 Corporation and Renesas Solutions Corporation assume no responsibility for any damage, liability or other loss resulting from the information contained herein.

Renesas Technology 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 Corporation, Renesas Solutions Corporation or an authorized Renesas Technology 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.

The prior written approval of Renesas Technology Corporation and Renesas Solutions Corporation is necessary to reprint or reproduce in whole or in part these materials.

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.

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

Precautions to be taken when using this product

This product is a development supporting unit for use in your program development and evaluation stages. In mass-producing your •

This product is a development supporting unit for use in your program development and evaluation stages. In mass-producing your program you have finished developing, be sure to make a judgment on your own risk that it can be put to practical use by performing integration test, evaluation, or some experiment else.

In no event shall Renesas Solutions Corporation be liable for any consequence arising from the use of this product.

Renesas Solutions Corporation strives to renovate or provide a workaround for product malfunction at some charge or without charge.

However, this does not necessarily mean that Renesas Solutions Corporation guarantees the renovation or the provision under any circumstances.

This product has been developed by assuming its use for program development and evaluation in laboratories. Therefore, it does not fall under the application of Electrical Appliance and Material Safety Law and protection against electromagnetic interference when used in

Japan.

For inquiries about the contents of this document or product, fill in the text file the installer of the emulator debugger generates in the following directory and email to your local distributor.

\SUPPORT\Product-name\SUPPORT.TXT

Renesas Tools Homepage http://www.renesas.com/en/tools

( 2 / 84 )

Preface

The M3062NT3-RPD-E is an emulation pod for the M16C/62 Group M16C/62N and M16C/30 Group M16C/30L of 16-bit MCUs. It is used with a PC4701 emulator.

This user's manual mainly describes specifications of the M3062NT3-RPD-E emulation pod and how to setup it. For details on the following products, which are used with M3062NT3-RPD-E, refer to each product's user's manual.

• Emulator:

PC4701 User's Manual

• Emulator debugger:

M3T-PD30 User's Manual

All the components of this product are shown in "2.1 Package Components" (page 22) of this user's manual. If there is any question or doubt about this product, contact your local distributor.

To use the product properly

Precautions for Safety

In both this user's manual and on the product itself, several icons are used to insure proper handling of this product and also to prevent injuries to you or other persons, or damage to your properties.

The icons' graphic images and meanings are given in "Chapter 1. Precautions for Safety". Be sure to read this chapter before using the product.

When using outside Japan

When using in Europe, the United States, or Canada, be sure to use both the emulator and the emulation pod which meet local standards. EMI standards are not met when the M3062NT3-RPD-E is used with the PC4700H emulator.

( 3 / 84 )

Contents

Chapter 1. Precautions for Safety ......................................................................................................

9

1.1 Safety Symbols and Meanings .......................................................................................

10

WARNINGS

 

Warning for Installation .................................................................................................

11

Warnings for Use Environment ......................................................................................

11

CAUTIONS

 

Caution to Be Taken for Modifying This Product ..........................................................

11

Cautions to Be Taken for Handling This Product ..........................................................

11

Cautions to Be Taken for Turning On the Power ...........................................................

11

IMPORTANT

 

Note on Malfunctions in the PC4701 System ................................................................

12

Notes on Downloading Firmware ..................................................................................

12

Notes on the Self-check ..................................................................................................

12

Note on Quitting the Emulator Debugger ......................................................................

12

Note on Final Evaluation ................................................................................................

12

Notes on Power Supply to the Target System ................................................................

12

Note on Clock Supply to the MCU ................................................................................

13

Note on RESET* Input ...................................................................................................

13

Note on NMI* Input .......................................................................................................

13

Note on RDY* Input ......................................................................................................

13

Notes on HOLD* Input ..................................................................................................

13

Notes on Setting the Work Area When Starting Up the Emulator Debugger ................

13

Note on Stack Area .........................................................................................................

14

Notes on MAP References and Settings .........................................................................

14

Note on Operation When Not Executing the User Program ..........................................

15

Note on Making an MCU file .........................................................................................

15

Notes on Maskable Interrupts .........................................................................................

15

Notes on Address-Match Interrupt .................................................................................

15

Note on BRK Instruction and BRK Interrupt .................................................................

15

Notes on Software and Hardware Breaks .......................................................................

16

Note on Stop and Wait Modes ........................................................................................

16

Note on Watchdog Function ...........................................................................................

16

Note on DMA Transfer ..................................................................................................

16

Note on Pullup Control ...................................................................................................

16

Note on Reading Internal Resources of the MCU ..........................................................

17

Note on Protect Register (PRC2) ...................................................................................

17

Note on Accessing Address 00000h ...............................................................................

17

Note on Differences Between the Actual MCU and Emulator ......................................

18

Note on Debugging Operations After Releasing a Reset from the Target .....................

19

Note on Emulating External Area ..................................................................................

19

Chapter 2. Preparation .....................................................................................................................

21

2.1 Package Components .....................................................................................................

22

2.2 Other Tool Products Required for Development ...........................................................

22

( 4 / 84 )

2.3

Name of Each Part .........................................................................................................

23

 

(1)

System Configuration ...............................................................................................

23

 

(2)

Inside of the Emulation Pod ......................................................................................

24

2.4

When Using This Product for the First Time .................................................................

25

 

(1) Making an MCU File ................................................................................................

25

 

(2)

Setting the Work Area ..............................................................................................

25

 

(3)

Downloading Firmware ............................................................................................

26

 

(4)

Self-check .................................................................................................................

26

Chapter 3. Setting Up ......................................................................................................................

27

3.1

Removing and Closing the Upper Cover .......................................................................

28

3.2

Each Setting ...................................................................................................................

29

3.3

Selecting Clock Supply and Replacing Oscillator Circuit Boards .................................

30

 

(1)

Clock Supply to the MCU ........................................................................................

30

 

(2)

Using the Oscillator Circuit on the Target System ...................................................

31

 

(3)

Changing the Internal Oscillator Circuit of the Emulation Pod ................................

32

 

(4)

Replacing Oscillator Circuit Boards .........................................................................

33

3.4

Switch Settings ...............................................................................................................

34

 

(1)

Toggle Switches SW1 to SW5 on the M30620T3-PRT Board (MCU-dependent 1) ...

34

 

(2)

Jumper Switches JP1 and JP2 on the M30620T3-PRT Board (MCU-dependent 1) ....

36

3.5

Installing and Removing Pullup Resistors .....................................................................

37

3.6

A-D Conversion Bypass Capacitors ...............................................................................

38

3.7

Connecting the PC4701 ..................................................................................................

39

 

(1)

Connecting the Cable to the PC4701 ........................................................................

39

 

(2)

Connecting the Cable to the Emulation Pod .............................................................

40

3.8

Connecting the Target System .......................................................................................

41

 

(1)

Connecting to a 100-pin LCC Socket .......................................................................

42

 

(2)

Connecting to an 80-pin 0.65-mm-pitch Foot Pattern (Part 1) .................................

43

 

(3)

Connecting to an 80-pin 0.65-mm-pitch Foot Pattern (Part 2) .................................

44

 

(4)

Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 1) .................................

45

 

(5)

Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 2) .................................

46

 

(6)

Connecting to a 100-pin 0.65-mm-pitch Foot Pattern (Part 3) .................................

47

 

(7)

Connecting to a 100-pin 0.5-mm-pitch Foot Pattern (Part 1) ...................................

48

 

(8)

Connecting to a 100-pin 0.5-mm-pitch Foot Pattern (Part 2) ...................................

49

 

(9)

Connecting to a 100-pin 0.5-mm-pitch Foot Pattern (Part 3) ...................................

50

 

(10) Connecting to a 100-pin 0.4-mm-pitch Foot Pattern ..............................................

51

Chapter 4. Usage .............................................................................................................................

53

4.1

Turning On the Power ....................................................................................................

54

 

(1)

Checking Connections of the Emulator System .......................................................

54

 

(2)

Turning ON/OFF the Power .....................................................................................

54

 

(3)

LED Display When the PC4701 Starts Up Normally ...............................................

55

4.2

Downloading Firmware .................................................................................................

56

 

(1)

When It is Necessary to Download Firmware ..........................................................

56

 

(2)

Downloading Firmware in Maintenance Mode ........................................................

56

( 5 / 84 )

4.3

Self-check .......................................................................................................................

57

 

(1)

Self-check Procedure ................................................................................................

57

 

(2)

If an Error is Detected in the Self-check ...................................................................

57

Chapter 5. Specifications .................................................................................................................

59

5.1

Specifications .................................................................................................................

60

5.2

Operation Timing in Memory Expansion and Microprocessor Modes .........................

61

 

(1)

Separate Bus, No-Wait .............................................................................................

61

 

(2)

Separate Bus, With Wait, Accessing External Memory Area ..................................

63

 

(3)

Multiplex Bus Timing ...............................................................................................

65

 

(4)

Timing Requirements ...............................................................................................

67

5.3

Connection Diagram ......................................................................................................

68

5.4

External Dimensions ......................................................................................................

70

 

(1)

External Dimensions of the Emulation Pod ..............................................................

70

 

(2)

External Dimensions of the Converter Board M30800T-PTC .................................

71

 

(3)

External Dimensions of the Converter Board M3T-F160-100NSD .........................

72

 

(4)

External Dimensions of the Converter Board M3T-F160-100NSE .........................

72

Chapter 6. Troubleshooting .............................................................................................................

73

6.1

Flowchart to Remedy the Troubles ................................................................................

74

6.2

When the Emulator Debugger Does Not Start Up Properly ..........................................

75

 

(1)

When the LED Display of the PC4701 is Abnormal ................................................

75

 

(2)

Program Window is Not Displayed at Debugger Startup (Target Connected) .............

76

 

(3)

Program Window is Not Displayed at Debugger Startup (Target Not Connected) ......

77

6.3

How to Request for Support ...........................................................................................

77

Chapter 7. Maintenance and Guarantee ...........................................................................................

79

7.1

Maintenance ...................................................................................................................

80

7.2

Guarantee .......................................................................................................................

80

7.3

Repair Provisions ...........................................................................................................

80

7.4

How to Request for Repair .............................................................................................

81

( 6 / 84 )

Terminology

Some specific words used in this user's manual are defined as follows:

Emulator system

This means an emulator system built around the PC4701 emulator. The PC4701 emulator system is configured with an emulator main unit, emulation pod, host machine and emulator debugger.

Emulator main unit (Hereafter PC4701)

This means a generic name for emulators for M16C, 7700, 740 Families. Take note of the fact that the M3062NT3-RPD-E (this product) does not support the PC4701L and PC4700L emulators. For details on specific models of PC4701, visit the Renesas Tools Homepage at http://www.renesas.com/ en/tools

Emulation pod

This means M3062NT3-RPD-E (this product). This emulation pod is for the M16C/62 Group M16C/ 62N and M16C/30 Group M16C/30L. It is used with the emulator main unit PC4701.

Emulator debugger

This means a software tool M3T-PD30 for M16C/60, M16C/20 and M16C/10 Series MCUs. The M3T-PD30 controls the emulator from the host machine through various interfaces.

Host machine

This means a personal computer used to control the emulator and emulation pod.

Firmware

Program that analyzes contents of communication with the emulator debugger and controls the emulator hardware. This program is installed in the EEPROM. This program is downloadable from the emulator debugger to upgrade the firmware or to support other MCUs.

Target MCU

This means the microcomputer you are going to debug.

Target system

This means a user's application system using the microcomputer to be debugged.

User program

This means an application program to be debugged.

Evaluation MCU

This means the microcomputer mounted on the emulation pod which is operated in the specific mode for tools.

*

In this user's manual, this symbol is used to show active LOW (e.g. RESET*: Reset signal).

( 7 / 84 )

MEMO

( 8 / 84 )

Chapter 1. Precautions for Safety

This chapter describes precautions for using this product safely and properly. For precautions for the emulator main unit and the emulator debugger, refer to each user's manual included with your product.

1.1 Safety Symbols and Meanings ...................................................................................................

10

WARNING

CAUTION

IMPORTANT

Warning for Installation .............................................................................................

11

Warnings for Use Environment .................................................................................

11

Caution to Be Taken for Modifying This Product .....................................................

11

Cautions to Be Taken for Handling This Product ......................................................

11

Cautions to Be Taken for Turning On the Power ......................................................

11

Note on Malfunctions in the PC4701 System ............................................................

12

Notes on Downloading Firmware ..............................................................................

12

Notes on the Self-check .............................................................................................

12

Note on Quitting the Emulator Debugger ..................................................................

12

Note on Final Evaluation ...........................................................................................

12

Notes on Power Supply to the Target System ...........................................................

12

Note on Clock Supply to the MCU ............................................................................

13

Note on RESET* Input ..............................................................................................

13

Note on NMI* Input ...................................................................................................

13

Note on RDY* Input ..................................................................................................

13

Notes on HOLD* Input ..............................................................................................

13

Notes on Setting the Work Area When Starting Up the Emulator Debugger ...........

13

Note on Stack Area ....................................................................................................

14

Notes on MAP References and Settings ....................................................................

14

Note on Operation When Not Executing the User Program ......................................

15

Note on Making an MCU file ....................................................................................

15

Notes on Maskable Interrupts ....................................................................................

15

Notes on Address-Match Interrupt .............................................................................

15

Note on BRK Instruction and BRK Interrupt ............................................................

15

Notes on Software and Hardware Breaks ..................................................................

16

Note on Stop and Wait Modes ...................................................................................

16

Note on Watchdog Function ......................................................................................

16

Note on DMA Transfer ..............................................................................................

16

Note on Pullup Control ..............................................................................................

16

Note on Reading Internal Resources of the MCU .....................................................

17

Note on Protect Register (PRC2) ...............................................................................

17

Note on Accessing Address 00000h ..........................................................................

17

Note on Differences Between the Actual MCU and Emulator ..................................

18

Note on Debugging Operations After Releasing a Reset from the Target ................

19

Note on Emulating External Area ................................................................................

19

( 9 / 84 )

Chapter 1. Precautions for Safety

In both the user's manual and on the product itself, several icons are used to insure proper handling of this product and also to prevent injuries to you or other persons, or damage to your properties.

This chapter describes the precautions which should be taken in order to use this product safely and properly. Be sure to read this chapter before using this product.

1.1 Safety Symbols and Meanings

WARNING

CAUTION

IMPORTANT

If the requirements shown in the "WARNING" sentences are ignored, the equipment may cause serious personal injury or death.

If the requirements shown in the "CAUTION" sentences are ignored, the equipment may malfunction.

It means important information on using this product.

In addition to the three above, the following are also used as appropriate. means WARNING or CAUTION.

Example: CAUTION AGAINST AN ELECTRIC SHOCK

means PROHIBITION.

Example: DISASSEMBLY PROHIBITED

means A FORCIBLE ACTION.

Example: UNPLUG THE POWER CABLE FROM THE RECEPTACLE.

The following pages describe the symbols "WARNING", "CAUTION", and "IMPORTANT".

( 10 / 84 )

WARNING

Warning for Installation:

Do not set this product in water or areas of high humidity. Make sure that the main unit does not get wet. Spilling water or some other liquid into the main unit can cause an unrepairable damage.

Warnings for Use Environment:

The emulation pod is air-cooled with the ventilation slot. Therefore, do not block the ventilation slot. When heated to high temperatures, the emulation pod may not work properly.

This equipment is to be used in an environment with a maximum ambient temperature of 35°C. Care should be taken that this temperature is not exceeded.

CAUTION

Caution to Be Taken for Modifying This Product:

Do not disassemble or modify this product. Disassembling or modifying this product can cause damage. Disassembling and modifying the product will void your warranty.

Cautions to Be Taken for Handling This Product:

Use caution when handling the main unit. Be careful not to apply a mechanical shock.

Do not touch the connector pins of the emulator main unit and the target MCU connector pins. Static electricity may damage the internal circuits.

Do not pull the emulation pod main unit by the flexible cable (FLX120-RPD) for connecting to the emulator main unit or the flexible cable (FLX64, FLX100, FLX160 or M3T-FLX160C) for connecting the target system. The cable may cause a break.

Flexible cable (FLX120-RPD) for connecting to the emulator main unit and the flexible cable (FLX64, FLX100, FLX160 or M3T-FLX160C) for connecting the target system are different from earlier models. The slits make them more flexible. However, excessive flexing or force may break conductors.

Do not use inch-size screws for this equipment. The screws used in this equipment are all ISO (meter-size) type screws. When replacing screws, use same type screws as equipped before.

Cautions to Be Taken for Turning On the Power:

Turn on the power of the emulator and target system as simultaneously as possible.

Turn off the power of the emulator and target system as simultaneously as possible.

Do not leave either the emulator or target system powered on, because of leakage current the internal circuits may be damaged.

When turning on the power again after shutting off the power, wait about 10 seconds.

( 11 / 84 )

IMPORTANT

Note on Malfunctions in the PC4701 System:

If the emulator malfunctions because of interference like external noise, do the following to remedy the trouble.

(1)Press the system reset switch on the emulator front panel.

(2)If normal operation is not restored after step (1), shut OFF power to the emulator once and then reactivate it.

Notes on Downloading Firmware:

Before using this product for the first time, it is necessary to download the dedicated firmware. Please note that, to do this, it is necessary to start up the emulator main unit in maintenance mode. For firmware download procedures, see "4.2 Downloading Firmware" (page 56). Once the firmware has been downloaded, the product can be used by simply turning on the power.

Do not shut off the power while downloading the firmware. If this happens, the product will not start up properly. If power is shut off unexpectedly, redownload the firmware in maintenance mode.

Be sure to disconnect the target system before downloading the firmware.

Notes on the Self-check:

If the self-check does not result normally (except target status errors), the product may be damaged. Then, contact your local distributor.

Be sure to disconnect the target system before executing the self-check. For details on the selfcheck, see "4.3 Self-check" on page 57.

Note on Quitting the Emulator Debugger:

To restart the emulator debugger after it ends, always shut power to the emulator module off once and then on again.

Note on Final Evaluation:

Be sure to evaluate your system with an evaluation MCU. Before starting mask production, evaluate your system and make final confirmation with a CS (Commercial Sample) version MCU.

Notes on Power Supply to the Target System:

Pin Vcc of the emulator is connected to the target system to observe the voltage of the target system. Therefore design your system so that the target system is powered by an external power supply.

The voltage of the target system should be within the MCU's specified range.

Do not change the voltage of the target system after turning on the power.

( 12 / 84 )

Renesas Emulation Pod M3062NT3-RPD-E User Manual

IMPORTANT

Note on Clock Supply to the MCU:

Clock can be supplied to the evaluation MCU in one of the following two ways. This is determined by emulator debugger clock selection.

(1)When Internal is selected:

A clock generated by the oscillation circuit in the emulation pod is supplied to the evaluation MCU. The clock is continually supplied to the evaluation MCU regardless of "target system clock status" and "user program execution status".

(2)When External is selected:

Clock supply to the evaluation MCU depends on oscillation status (oscillate/off) of the target system.

Note on RESET* Input:

"L" input from the target system to pin RESET* is accepted only while a user program is being executed (only while the RUN status LED on the PC4701's front panel is lit).

Note on NMI* Input:

"L" input from the target system to pin NMI* is accepted only while a user program is being executed (only while the RUN status LED on the PC4701's front panel is lit).

Note on RDY* Input:

Be sure to input "L" to pin RDY* of the target system during the user program execution (only while the RUN status LED on the PC4701's front panel is lit). Inputting "L" to pin RDY* during the user program stopping may cause a malfunction of the emulator.

Notes on HOLD* Input:

Be sure to input HOLD* of the target system during user program execution (only while the RUN status LED on the PC4701's front panel is lit). If "L" is input to pin HOLD*, the emulator will not work normally.

When inputting "L" to pin HOLD* to run into the HOLD state, P00 to P52 will be in the HOLD state delaying by 2.5 cycles than the actual MCU (see Table 5.5 and Figure 5.4).

Notes on Setting the Work Area When Starting Up the Emulator Debugger:

With this product, the emulator uses 32 bytes as a work area in emulation memory. In single-chip mode, set the work area address at 10000h. In memory expansion or microprocessor mode, set the work area address in an area other than SFR area (0000h--003FFh), external area of multiplex bus setting and stack area used by the emulator for reset command execution (0FFF9h--0FFFFh). For more details, see "2.4 (2) Setting the Work Area" (page 25).

The top address of the work area should be an even-numbered address.

Set the work area as MAP=INT.

For example, if the work area is set at 02C00h, the emulator uses 32-byte area of 02C00h to 02C1Fh.

( 13 / 84 )

IMPORTANT

Note on Stack Area:

With this product, a maximum 7 bytes of the user stack is consumed. Therefore, ensure the +7 bytes maximum capacity used by the user program as the user stack area.

If the user stack does not have enough area, do not use areas which cannot be used as stack (SFR area, RAM area which stores data, or ROM area) as a work area. Using areas like this is a cause of user program crashes and destabilized emulator control.

Notes on MAP References and Settings:

For details on referencing and setting MAP information, see the emulator debugger M3T-PD30 user's manual.

Make settings as follows:

(1)MAP = INT

The emulation memory inside this product becomes effective. Set this at MCU internal ROM debugging.

(2)MAP = EXT

The emulation memory inside this product is not used.

Set this where the MCU internal resource (SFR, RAM) or resources on the target system are used.

Be sure to set the SFR area and RAM area of the MCU to EXT, and the reserved area of the MCU to INT.

Be sure to set mappings in word units.

When setting 0FFF9h to 0FFFFh to EXT:

This product uses the 7 byte area 0FFF9h through 0FFFFh as the stack area. If this 7 byte memory cannot be read or written to, reset cannot be properly effected. As a result, you need to alter the map settings if the condition given below is met.

(1)With the system which shifts from the single-chip mode to memory expansion (or microprocessor) mode, using the 7 byte area of 0FFF9h to 0FFFFh set to EXT.

(2)With the system which starts up in microprocessor mode, using the 7 byte area of 0FFF9h to 0FFFFh set to EXT and there is not enough memory to read or write.

The procedures to alter the MAP settings when the conditions (1) or (2) above are met.

(1)Set the 7 byte area of 0FFF9h to 0FFFFh to INT.

(2)Execute the RESET command by use of emulator debugger M3T-PD30.

(3)Set the stack pointer. (Example)

RESET:

FCLR I

 

LDC #0480H, SP --> Set the stack pointer

 

(Stop the program after executing this instruction)

(4) Set the 7 byte area 0FFF9h through 0FFFFh to EXT.

( 14 / 84 )

IMPORTANT

Note on Operation When Not Executing the User Program:

With this product, bit 7 of processor mode register 1 (wait bit PM17) is forcibly set to "1" (with wait) when the user program is not executed (e.g. when the program is stopped or when run-time debugging is being performed). Therefore, if the external area set to 0 wait is accessed by other than the user program (such as debugging operation), one wait is inserted. However, when wait bit PM17 is referenced by the dump window etc. the value set during user program execution is displayed.

Note on Making an MCU file:

To debug an MCU which has any other size of memory (ROM, RAM), be sure to make an MCU file for it. For details on making an MCU file, see "2.4 (1) Making an MCU File" on page 25. For memory maps of each MCU, refer to the datasheet of the MCU.

Notes on Maskable Interrupts:

Even if a user program is not being executed (including when run-time debugging is being performed), the evaluation MCU keeps running so as to control the emulation probe. Therefore, timers and other components do not stop running.

If a maskable interrupt is requested when the user program is not being executed (including when run-time debugging is being performed), the maskable interrupt request cannot be accepted, because the emulator disables interrupts. The interrupt request is accepted immediately after the user program execution is started.

Take note that when the user program is not being executed (including when run-time debugging is being performed), a peripheral I/O interruption is not accepted.

Notes on Address-Match Interrupt:

To debug address-match interrupts, set a software breaks or hardware break at the top address of the address-match interrupt process. If you set a software breaks or hardware break at an address where an address-match interrupt occurs, the program will run out of control.

When an address at which an address-match interrupt occurs is executed in one-step mode, the program stops after executing the first instruction after returning from the address-match interrupt processing.

Note on BRK Instruction and BRK Interrupt:

With this emulator system, a BRK interrupt by a BRK instruction is exclusively used for software break functions. Therefore, you can not use them for your program.

( 15 / 84 )

IMPORTANT

Notes on Software and Hardware Breaks:

The software break is a debugging function which breaks a program immediately before the system executes an instruction at a specified address. The instruction at the preset address will not be executed.

The hardware break is a debugging function which breaks a program by setting the detection of an execution of an instruction at a specified address as a break event. The program will break after the instruction at the specified address is executed.

The software break generates BRK interrupts by substituting the proper instruction to the BRK instruction. Therefore, when referencing the result of a trace in bus mode, "00h" is displayed for the instruction fetch address where a software break is set, and when referencing in disassemble mode, "BRK" instruction is displayed.

It is not possible to use a software break and a hardware break at the same time. If doing so, it may not operate normally.

In the area where the MAP setting is EXTERNAL, software breaks cannot be used.

Note on Stop and Wait Modes:

Do not perform step execution at addresses in the stop or wait mode. It may cause communication errors.

Note on Watchdog Function:

The MCU's watchdog timer can be used only while programs are being executed. To use it otherwise, disable the watchdog timer.

Note on DMA Transfer:

With this product, the program is stopped with a loop program to a specific address. Therefore, if a DMA request is generated by a timer or other source while the program is stopped, a DMA transfer is executed. However, make note of the fact that a DMA transfer while the program is stopped may not be performed correctly. Also note that the below registers have been changed to generate a DMA transfer as explained here even when the program is stopped.

DMA0 transfer counter registers TCR0, TCR1 (M16C/62N only)

Note on Pullup Control:

With this product, ports P0 [7:0] to P5 [7:0] are not pulled up by the pullup control register.

To pull up the ports P0 to P5, apply a resistance to the inside of the emulator. How to apply it, refer to "3.5 Installing and Removing Pullup Resistors" (page 37).

Note: Ports P6 to P10 are pulled up by the pullup control registers.

Note: Pullup control registers themselves can be read and written into properly.

( 16 / 84 )

IMPORTANT

Note on Reading Internal Resources of the MCU:

When the registers that are listed in Table 1.1 are read with an emulator, those results will be the following (the data in the MCU are not effected).

(1)Results of real-time trace

The data values of the cycles read are not displayed correctly.

(2)Real-time RAM monitor

The data values read are not displayed correctly.

Table 1.1 Resisters and symbols not displayed normally (*1: M16C/62N only)

Resister

Symbol

DMA source pointers 0, 1 (*1)

SAR0, SAR1 (*1)

DMA destination pointers 0, 1 (*1)

DAR0, DAR1 (*1)

 

 

DMA transfer counters 0, 1 (*1)

TCR0, TCR1 (*1)

 

 

DMA control resisters 0, 1 (*1)

DM0CON, DM1CON (*1)

Note on Protect Register (PRC2):

Make note of the fact that the protect is not canceled when protect register (PRC2), which enables writing in the port P9 direction register and the SI/Oi control register, is changed with the below procedure.

(1)Step execution of the "instruction for setting ("1") PRC2"

(2)Setting the break point from the instruction for setting ("1") PRC2 to when the port P9 direction register and SI/Oi control register are set.

(3)Setting "("1") PRC2" from the dump window or script window

Note on Accessing Address 00000h:

With M16C/60 Series MCUs, when a maskable interrupt is generated, the interrupt data (interrupt No. and interrupt request level) stored in address 00000h is read out. Also, the interrupt request bit is cleared when address 00000h is read out. Consequently, when the address 00000h readout instruction is executed or when address 00000h is read out in the cause of a program runaway, a malfunction occurs in that the interrupt is not executed despite the interrupt request, because the request bit of the highest priority interrupt factor enabled is cleared.

For this malfunction, when the reading out to the address 00000h is generated excluding the interrupt, the yellow LED lights up to alarm. When this LED lights, there is a possibility of wrong access to address 00000h, therefore check the program. This LED is turned off by the system reset switch of the emulator main unit.

( 17 / 84 )

IMPORTANT

Note on Differences Between the Actual MCU and Emulator:

Operation of the emulator differs from that of the actual MCU as listed below.

(1)Reset condition

Set the time for starting up (0.2 Vcc to 0.8 Vcc) 1 s or less.

(2)Initial values of MCU's internal resources at power-on

(3)Internal memories (ROM and RAM) capacities etc.

With this emulator system, regardless of ROM and RAM of the MCU you use, all the areas other than the SFR area can be read and written into.

(4)Characteristics of ports P0 to P5

Ports P0 to P5 are connected via emulation circuits. The device used for the port emulation circuit is the IC21 (ALTERA EPF6016QC208-2).

(5)Oscillator circuit

Make note that in the oscillator circuit where a resonator is connected between pins XIN and XOUT, oscillation does not occur because a flexible cable, buffer IC and other devices are used between the evaluation MCU and the target system. It is same for sub-clock oscillators (XCIN and XCOUT).

For notes on when using the oscillator circuit on the target system, refer to "3.3 (2) Using the Oscillator Circuit on the Target System" (page 31).

(6)A-D conversion function

As a flexible cable and other devices are used between the evaluation MCU and the target system, some characteristics are slightly different from those of the actual MCU.

(7)DBC, single-step and BRK instruction interrupt vector table addresses

As the emulator uses the DBC, single-step and BRK instruction interrupt vector table addresses, when reading these addresses, the downloaded data cannot be read (see Table 1.2).

Table 1.2 Vector table addresses for the emulator

Factor of interruption

Vector table addresses

Data read

 

 

 

DBC*1

FFFF4h--FFFF7h

Indefinite

 

 

 

Single-step*1

FFFECh--FFFEFh

Indefinite

BRK instruction

FFFE4h--FFFE7h

Indefinite

 

 

 

*1 Interruption for the emulator only

(8)Address and status of BHE*

When the internal RAM or ROM area of the MCU is accessed during user program execution, the actual MCU retains a preceding address and status of BHE*, while this product does not.

(9)Status of a data bus

In stop or wait mode, the actual MCU retains a preceding status of a data bus, while with this product a data bus is floating.

(10)ALE signal

When the internal RAM or SFR area of the MCU is accessed during user program execution, with the actual MCU, ALE output is fixed to Low, while this product outputs ALE signal.

( 18 / 84 )

IMPORTANT

Note on Debugging Operations After Releasing a Reset from the Target:

Do not execute debugging operations such as setting a software or hardware break, runtime debugging after releasing a reset from the target system until an interrupt stack pointer (ISP) is set in the user program.

Note on Emulating External Area:

To emulate the external area using emulation memory in this product, set 0 wait (8 MHz) or less, or 1 wait.

( 19 / 84 )

MEMO

( 20 / 84 )

Chapter 2. Preparation

This chapter describes the package components, the system configuration and the preparation for using this product for the first time.

2.1

Package Components ...................................................................................................................

22

2.2

Other Tool Products Required for Development .........................................................................

22

2.3

Name of Each Part .......................................................................................................................

23

 

(1)

System Configuration ...........................................................................................................

23

 

(2)

Inside of the Emulation Pod ..................................................................................................

24

2.4

When Using This Product for the First Time ..............................................................................

25

 

(1) Making an MCU File ............................................................................................................

25

 

(2)

Setting the Work Area ..........................................................................................................

25

 

(3)

Downloading Firmware ........................................................................................................

26

 

(4)

Self-check .............................................................................................................................

26

( 21 / 84 )

Chapter 2. Preparation

2.1 Package Components

The M3062NT3-RPD-E package consists of the following items. When unpacking, check to see if your M3062NT3-RPD-E contains all of these items.

Table 2.1 Package components

Item

Quantity

 

 

M3062NT3-RPD-E emulation pod main unit

1

 

 

FLX120-RPD flexible cable for connecting PC4701

1

 

 

M3T-F160T3-PRB converter board for M3T-FLX160C (preinstalled)

1

 

 

M30800T-PTC converter board for 100-pin 0.65-mm-pitch QFP

1

 

 

IC61-1004-051 100-pin 0.65-mm-pitch LCC socket (made by Yamaichi Electronics Co., Ltd.)

1

 

 

OSC-3 16 MHz oscillator circuit board for main clock (preinstalled)

1

 

 

OSC-2 oscillator circuit board for main clock (bare board)

1

 

 

Resistor arrays for pulling up ports P0 to P5 (51 kΩ)

6

Hardware tool user registration FAX sheet

1

 

 

Hardware tool user registration FAX sheet (Japanese)

1

 

 

M3062NT3-RPD-E User's Manual (This manual)

1

 

 

M3062NT3-RPD-E User's Manual (Japanese)

1

 

 

*Please keep the M3062NT3-RPD-E's packing box and cushion material in your place for reuse at a later time when sending your product for repair or other purposes. Always use these packing box and cushion material when transporting this product.

*If any of these items are missing or found faulty, please contact your local distributor.

*If there is any question or doubt about the packaged product, contact your local distributor.

*For purchasing the IC61-1004-051 or for technical information, contact Yamaichi Electronics Co., Ltd.

2.2Other Tool Products Required for Development

To bring forward programs development on an M16C/62 Group M16C/62N and M16C/30 Group M16C/30L, the products listed below are necessary in addition to those contained package above. Get them separately.

Table 2.2 Other tool products

Emulator main unit

PC4701 (excluding PC4701L and PC4700L)

 

 

Emulator debugger

M3T-PD30

 

 

Converter board

For 80-pin 0.65-mm-pitch QFP (80P6S-A):

 

M3T-100LCC-DMS + M3T-FLX-DCT613 + M3T-FLX80QSB

 

M3T-100LCC-DMS + M3T-FLX-DCT613 + M3T-DIRECT80S

 

For 100-pin 0.65-mm-pitch QFP (100P6S-A):

 

M3T-100LCC-DMS + M3T-DIRECT100S

 

M3T-100LCC-DMS + M3T-DUMMY100S

 

M3T-100LCC-DMS + M3T-FLX-100NRB

 

For 100-pin 0.5-mm-pitch LQFP (100P6Q-A):

 

M3T-F160-100NSD

 

M3T-100LCC-QSD

 

M3T-100LCC-DMS + M3T-FLX-100NSD

 

For 100-pin 0.4-mm-pitch TQFP (100PFB-A):

 

M3T-F160-100NSE

 

Required according to the foot pattern of the target system (see "3.8

 

Connecting the Target System" on page 41)

 

 

* To purchase these products, contact your local distributor.

( 22 / 84 )

2.3Name of Each Part

(1)System Configuration

Emulator debugger

Interface cable

Host machine

(2) Flexible cable for connecting PC4701

(1) Emulation pod main unit

Emulator main unit

(3) Flexible cable for connecting target system

(4) Pitch converter board for connecting target system

Figure 2.1 System configuration

(1) to (4) in Figure 2.1 are included with this product package.

(1)Emulation pod main unit M3062NT3-RPD-E

This emulation pod contains an evaluation MCU, emulation memory and circuits to feature the debug functions.

(2)Flexible cable FLX120-RPD

This is a 120-conductor flexible cable for connecting the PC4701 emulator and the emulation pod.

(3)Flexible cable M3T-FLX160C

This is a 160-conductor flexible cable for connecting the emulation pod and the target system.

(4)Pitch converter board

This is a pitch converter board for connecting to the target system. For details, refer to "3.8 Connecting the Target System" (page 41).

( 23 / 84 )

(2) Inside of the Emulation Pod

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(1) MCU-dependent board 1

(3) Common board

 

(2) MCU-dependent Board 2

 

 

 

 

 

 

 

 

 

 

 

 

 

(4) Oscillator circuit board

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Figure 2.2 Internal view of the emulation pod

(1)MCU-dependent board 1

This is a board for port emulation.

(2)MCU-dependent board 2

This is a board with the evaluation MCU.

(3)Common board

This is a board controlling the interface with the PC4701 and evaluation MCU.

(4)Oscillator circuit board

This is a board with an oscillator module. You can change the operating frequency by replacing it with other oscillator circuit board included with this product package.

( 24 / 84 )

+ 60 hidden pages