Renesas Single-Chip Microcomputer M32180T2-PTC Technical information

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.
2.
3.
4.
5.
6.
7.
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.
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.
You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part.
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.
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.
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.
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”:
8.
9.
10.
11.
12.
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.
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.
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.
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.
This document may not be reproduced or duplicated, in any form, in whole or in part, without prior written consent of Renesas
Electronics.
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.
M3T-PD32RM V.3.01 Release 00 Release Notes
Be sure to read this note.
M3T-PD32RM V.3.01 Release 00
Release Notes
1st Edition
Renesas Solutions Corporation
October 1, 2006
Abstract
Welcome to M3T-PD32RM V.3.01 Release 00 (hereafter referred to as PD32RM).
This material explains the contents of the software, installation procedure, and supplements to the PD32RM Help.
When using this software, take a look at the release note as well as the PD32RM Help.
Also, this document contains a License Agreement in the last. Read it before using. By using the software, you are
accepting and agreeing to such terms.
* You can get the latest version of this document from our homepage: (http://www.renesas.com/en/tools)
Contents
Components of the Product................................................................................................................................ 3
Operating Environment ..................................................................................................................................... 4
Installation........................................................................................................................................................... 4
3.1. INSTALLING OF PD32RM................................................................................................................................. 4
3.2. USER REGISTRATION ........................................................................................................................................ 4
3.3. INSTALLING OF ACROBAT READER .................................................................................................................. 5
3.4. INSTALLING OF HTML HELP UPDATE COMPONENT...................................................................................... 5
3.5. INSTALLING OF USB DEVICE DRIVER .............................................................................................................. 5
4. Technical Support ............................................................................................................................................... 6
4.1. TECHNICAL SUPPORT BY E-MAIL...................................................................................................................... 6
4.2. TECHNICAL SUPPORT BY HOMEPAGE .............................................................................................................. 6
5. Notes..................................................................................................................................................................... 7
5.1. ANALYSIS OF REAL TIME TRACE RESULTS ........................................................................................................ 7
5.2. ZONE TIME MEASUREMENT ERROR .................................................................................................................. 7
5.3. ZONE TIME MEASUREMENT EVENT .................................................................................................................. 9
5.4. PRECAUTIONS ON DOWNLOAD (1) .................................................................................................................. 10
5.5. PRECAUTIONS ON DEBUGGING ...................................................................................................................... 11
5.6. PRECAUTIONS WHEN USING TW32R (V.1.00 RELEASE 1 TO V.3.00 RELEASE 1) ....................................... 12
5.7. CHANGING MEMORY CONTENTS OF AN EXTERNAL FLASH ROM AREA ......................................................... 13
5.8. ABOUT THE SCOPE .......................................................................................................................................... 13
5.9. ABOUT WATCHING THE LOCAL C VARIABLES ................................................................................................. 13
5.10.
PRECAUTIONS ON DEBUGGING FUNCTIONS IN THE EXTERNAL AND EXTENDED EXTERNAL AREAS ......... 14
5.11.
ABOUT USING CAST OPERATORS FOR THE MEMBER VARIABLE ................................................................. 14
5.12.
ON THE BREAK FUNCTION USING THE PRE-EXECUTION PC BREAK .......................................................... 15
6. Supplements of User’s Manual........................................................................................................................ 16
1.
2.
3.
Rev.1.00 10.01.2006 page 1 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
6.1. MCU FILE LIST PROVIDED WITH THE PD32RM PRODUCT ........................................................................... 16
6.2. LIST OF FLASH DEVICE DEFINITION FILES (FDD FILES) PROVIDED WITH THE PD32RM PACKAGE ........... 19
6.3. SECURITY CODE CHECK FUNCTION ................................................................................................................ 21
7. Version Report................................................................................................................................................... 22
7.1. PD32RM V.3.01 RELEASE 00........................................................................................................................ 22
7.2. PD32RM V.3.00 RELEASE 01........................................................................................................................ 22
7.3. PD32RM V.3.00 RELEASE 00........................................................................................................................ 22
7.4. PD32RM V.2.10 RELEASE 1.......................................................................................................................... 23
7.5. PD32RM V.2.00 RELEASE 1.......................................................................................................................... 24
8. License Agreement ........................................................................................................................................... 25
Active X, Microsoft, MS-DOS, Visual Basic, Visual C++, Windows and Windows NT are either registered trademarks or trademarks of
Microsoft Corporation in the United States and other countries.
IBM and AT are registered trademarks of International Business Machines Corporation.
Intel and Pentium are registered trademarks of Intel Corporation.
Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated.
All other brand and product names are trademarks, registered trademarks or service marks of their respective holders.
Rev.1.00 10.01.2006 page 2 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
1.
Components of the Product
PD32RM V.3.01 Release 00 comprises the following:
!
Contents of the CD-ROM
1. PD32RM installer files
The following files are installed after running the PD32RM installer.
(1) Programs and files
" PD32RM.EXE
" PD_LITE.EXE V. 8.50.01
" xxxxxx.dll
P32RMEDLL.DLL
V. 1.40.01
P32REMUWIN.DLL
V. 1.40.01
COMMUNI.DLL
V. 2.01.05
P32RRRAMWIN.DLL
V. 1.40.01
P32REGUI.DLL
V. 1.40.01
FFW32R.DLL
V. 2.02.00
P32REVENTSETTING.DLL
V. 1.40.01
MFC42.DLL
P32RMERESOURCE.DLL
V. 1.40.01
ATL.DLL
P32RGUIIOWIN.DLL
V. 1.40.01
MSVCRT.DLL
P32RRTOSWIN.DLL
V. 1.40.01
MSVCP60.DLL
" M32RCPE0.S (Firmware file) V 1.03.00
" M32RCPE1.S (Firmware file) V 2.03.00
" M32RMEZ.HWC, M32RMT3_2.HWC, M32RMT3_3_4.HWC, M32RMT3_3_8.HWC,
M32RMT4_2.HWC, M32RMT4_3_4.HWC, M32RMT4_3_8.HWC,
M32RMT5_2.HWC,
M32RMT5_3_4.HWC,
M32RMT5_3_8.HWC,
M32RMT5_3_8_C0.HWC
" PDHELP.CHM
" PD32RMDLL.DEF
" PD32RM.FEF
" R.RDF, RF.RDF, RV.RDF, RX.RDF
" DEFAULT.SCK
" LOAD.SCR (sample download script file for M32121)
" FLASHWRITER.EXE
" PD_LITE.TLB
The following file is stored in the ‘drivers’ directory under the directory that has PD32RM installed
(eg: c:¥renesas¥pd32rm¥drivers).
(a) The device drivers for the USB interface.
The installer copies the files under the target directory. And you need to install them when
you use the USB interface.
2. HTML Help Update Component
You may need HTML Help Update Component (provided by Microsoft Co. Ltd.) to browse HTML
Help Files (.CHM). If you can’t open the help file for PD32RM, install and update this component in
your system (NOTE: You need to restart your system after the installing).
!
Release Note for PD32RM V.3.01 Release 00 (“Software User License Agreement” included.)
Rev.1.00 10.01.2006 page 3 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
2.
Operating Environment
PD32RM runs on the operating environments given below.
Table 1: The Host Machine Requirements
Host Machine
Operating System
CPU
Memory
3.
IBM PC/AT and its compatibles
Windows Me
Windows 98
Windows XP
Windows 2000
Pentium 3 500MHz or higher CPU is recommended.
192MB or more system memory is recommended.
Installation
[Notes for Windows XP/2000]
When using Windows XP/2000 as an operating system, make sure that the installer is executed by an
authorized user as an Administrator. No one but the user with administrator rights can install the
PD32RM.
3.1.
Installing of PD32RM
Register the PD32RM to the Windows Me/98/XP/2000 by installing it to the hard disk using the
installer.
1.
Start of the installer
Use the Windows Explorer to view the CD-ROM. Navigate to the “setup.exe” file in the
¥PD32RM¥W95E folder, and open the file to start the PD32RM installer.
2.
Entering user information
In the “Customer Information” dialog box, enter customer information (License User, Belong To,
Your Addresses, and PC types). Entered information becomes a format of a customer support by
mail.
3.
Selection of component
In the "Select Components" dialog box, select the component to be installed. In the dialog box,
installation folder can be changed.
4.
End of the installer
The installation of PD32RM is completed, when the “Setup is complete” dialog box appears.
3.2.
User Registration
The text file for the user registration is created to the start menu. Enter the necessary information to the
text file and send it to our registration desk (regist_tool@renesas.com). To open the text file for the user
registration, select the following menu:
Windows Menu [Start]->[Program]->[Renesas]->[PD32RM V.3.01 Release 00]->[User Registration Sheet]
Rev.1.00 10.01.2006 page 4 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
3.3.
Installing of Acrobat Reader
The manual of PD32RM is provided as an electronic file. Acrobat Reader is necessary to browse the
electronic file. The latest version of Acrobat Reader can be downloaded from the home page of the
Adobe Systems.
URL for Adobe Systems: http://www.adobe.com/
3.4.
Installing of HTML Help Update Component
The Help for PD32RM is provided as HTML Help file. Internet Explorer 4.0 or later is necessary to browse
HTML Help files.
If you can’t browse HTML Help files, you need to install Internet Explorer 4.0 or later, HTML Help
Update Component, or both of them.
HTML Help Update Component (HHUPD.exe) is stored in the “Utility” folder, which is created within the
folder that PD32RM is installed (eg:c:¥renesas¥pd32rm¥Utility¥Hhupd.exe). Install it, if necessary (you
need to restart your system after installing). The latest version of this component can be downloaded from
the home page of Microsoft Co. Ltd.
URL for MSDN: http://msdn.microsoft.com/
3.5.
Installing of USB device driver
Install the USB device driver when you first use USB interfaces of Renesas emulators. The following
shows the procedure for installing it.
1. Connect the host computer and the emulator with USB cable.
2. Turn on the emulator.
3. Windows’ Plug & Play function detects the USB devices connected. The wizard for the USB device
installation starts.
Go on following the wizard, and a dialog box for specifying the setup information file (inf file) is displayed.
Specify the musbdrv.inf file stored in a location below the directory where the PD32RM is installed (e.g.,
c:¥renesas¥pd32rm¥drivers).
[NOTES]
" Before USB device drivers can be installed, the PD32RM you use must already be installed. Install
the PD32RM first.
" When using Windows XP/2000, make sure a user who installs the USB device driver needs
administrator rights.
" During installation, a message may be output indicating that the device driver proper musbdrv.sys
cannot be found. In this case, specify the musbdrv.sys which is stored in the same directory as is the
musbdrv.inf file.
Rev.1.00 10.01.2006 page 5 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
4.
Technical Support
4.1.
Technical support by E-mail
The text file for the technical support is created based on the information provided at installation. Write
your inquiry in it and send it to our technical support (support_tool@renesas.com). To open the text file for
technical support, select the following menu:
Windows Menu [Start]->[Program]->[Renesas]->[PD32RM V.3.01 Release 00]->[Technical Support Sheet]
[Notes on technical support]
We designate the types of host machines (IBM PC/AT and compatibles, for example) as an operation
environment for using our software tools. This does not guarantee operation of the host machines of any
kind or in any environment (such as device drivers, peripheral units), but merely for indicating an
operation environment we assume (to be put to our support). If a trouble should occur in using the
software tools in the operation environment we designate, we offer a technical support to solve the trouble
(defective correction and information for avoiding the trouble, and so forth).
If a trouble that occurred in your environment cannot be reproduced in our operation environment, we
may ask for your cooperation (we may borrow your equipment with your approval). We would like your
prior approval.
4.2.
Technical support by Homepage
Our homepage in the following URL provides datasheets, toolnews, FAQ and the other various
information of our products.
Home Page: http://www.renesas.com/en/tools
Another access is:
Windows Menu [Start]->[Program]->[RENESAS-TOOLS]
-> [(Link Page for) RENESAS Tools HomePage]
Rev.1.00 10.01.2006 page 6 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
5.
Notes
5.1.
Analysis of real time trace results
When the trace type is Branch or Mix, observe the following restriction on the result of real time
trace, depending on the setup condition or the occurred breakpoint setting.
"
When tracing up to the time point when the breakpoint occurs
When the real time trace result is displayed in the bus mode, the trace data at occurrence of the
breakpoint is listed as below. The trace data at Address: FFFF9000 indicates that a break
function has occurred. It does not indicate an occurrence of branch caused by the user program.
Trace data indicating break occurrence
The trace data at Address: FFFF9000 indicates that a break
function has occurred.
For the bus mode display, Address, ST and other fields, see the PD32RM Help.
5.2.
Zone time measurement error
The zone time measurement function is implemented based on the trace data output from The MCU.
To output a unit of trace data information, the MCU operation clock frequency count shown below is
required. Thus, the zone time measurement result generates a measurement error from the actual
MCU execution time.
A unit of trace data refers to the following information:
(a) Single branch information arising during program execution
(b) Single data access information
According to the trace mode setting, the trace data output from the MCU are described below:
Trace Mode Setting
Trace Data Output from MCU
Branch
(a) Only branch information
Data
(b) Only data access information
Mix(Branch Priority)
(a)Branch information and (b) Data access information
Mix(Data Priority)
(b)Branch information and (b) Data access information
Rev.1.00 10.01.2006 page 7 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
"
Clock count required to output a unit of information
Emulator model, Patterns of connection
MCU
group
MCU operation
frequency
A unit of
information
outputted (a) Branch
information
(b) Data access
information
32102
-
3212x
-
3217x
-
3218x
MCU clock
<= 66MHz
MCU clock
> 66MHz
MCU clock
<= 66MHz
66MHz <
MCU clock
<= 108MHz
108MHz <
MCU clock
<= 132MHz
MCU clock
> 132MHz
MCU clock
<= 66MHz
66MHz <
MCU clock
<= 108MHz
108MHz <
MCU clock
<= 132MHz
MCU clock
> 132MHz
(a)
(b)
(a)
(b)
(a)
(b)
(a)
(b)
(a)
(b)
(a)
(b)
(a)
32104
3219x
Rev.1.00 10.01.2006 page 8 of 28
REJ10J1494-0100
(b)
M32100T3-SDI-E
When
M32xxxT2-PTC
is not used
Number of
trace output
clocks
When
M32xxxT2-PTC
is used
Number of
trace output
clocks
12
18
6
9
6
9
6
9
12
18
6
9
6
9
12
6
18
9
(a)
12
(b)
18
(a)
(b)
(a)
(b)
(a)
24
36
12
18
12 (max)
6 (max)
(b)
18 (max)
9 (max)
6 (max)
9 (max)
(a)
12 (max)
(b)
18 (max)
(a)
(b)
24 (max)
36 (max)
12 (max)
18 (max)
M3T-PD32RM V.3.01 Release 00 Release Notes
The zone time measurement error shown below is generated when Event Type except Chip Event is
specified for the event setup function -- one of the zone time measurement functions.
"
Time measurement error (clock count required to output a unit of information x 2)
Emulator model, Patterns of connection
MCU
group
MCU operation
frequency
A unit of
information
outputted (a) Branch
information
(b) Data access
information
32102
-
3212x
-
3217x
-
3218x
MCU clock
<= 66MHz
MCU clock
> 66MHz
MCU clock
<= 66MHz
66MHz <
MCU clock
<= 108MHz
108MHz <
MCU clock
<= 132MHz
MCU clock
> 132MHz
MCU clock
<= 66MHz
66MHz <
MCU clock
<= 108MHz
108MHz <
MCU clock
<= 132MHz
MCU clock
> 132MHz
(a)
(b)
(a)
(b)
(a)
(b)
(a)
(b)
(a)
(b)
(a)
(b)
(a)
32104
3219x
(b)
M32100T3-SDI-E
When
M32xxxT2-PTC
is not used
Number of time
measurement
error clocks
When
M32xxxT2-PTC
is used
Number of time
measurement
error clocks
24
36
12
18
12
18
12
18
24
36
12
18
12
18
24
12
36
18
(a)
24
(b)
36
(a)
(b)
(a)
(b)
(a)
48
72
24
36
24 (max)
12 (max)
(b)
36 (max)
18 (max)
12 (max)
18 (max)
(a)
24 (max)
(b)
36 (max)
(a)
(b)
48 (max)
72 (max)
24 (max)
36 (max)
5.3.
Zone time measurement event
Setup of zone time measurement events has the following restrictions:
" Set the start event and end event at interval of more than 200 ns in-between.
Rev.1.00 10.01.2006 page 9 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
5.4.
Precautions on download (1)
When one of the following applies, the target microcomputer is reset, and the registers which sets
the memory wait count and clock frequency are initialized.
(1) Immediately after the PD32RM gets started
(2) When pressing the RESET button on the PD32RM (or when executing the Reset instruction)
(3) When downloading is completed (when the reset operation is enabled after downloading)
You can select the reset operation after downloading by using the "Download Behavior tab" in
the Init dialog box. For details, see the "Setup" section in the PD32RM Help.
If you try to download the target program in such a state, the download speed may drastically
become slow. It is highly recommended that you should download the target program after setting
the memory wait count and clock frequency.
The following shows an example to download the program to the flash memory built in the target
microcomputer M32121.
When using a target microcomputer of other model, set the parameters referring to the given
example.
(Example: When using M32121)
Set the parameters to the register using the PD32RM memory rewrite function.
Register
Address
Access size
Setting value
Setting data
Built-in ROM wait
H'FFFFC023
Byte
H'00
Built-in ROM wait
control register
count 0
Clock mode register
H'00F74000
Word
BCLKSEL=B'0000
System clock f (XIN)
The PD32RM script instruction executes the following:
MB FFFC023, 0
MW 00F74000, 0
A script file LOAD.SCR in which the above data is described is attached.
Immediately after starting PD32RM, it is automatically executed by specifying "Init File" on
"Resume tab" in "Init" dialog.
Download speed to the built-in flash memory is influenced by the setting data in the register above
(built-in ROM wait control register/clock mode register).
To download a target program to an external device, be sure to set the parameters of the built-in
chip select controller before starting downloading.
And, if you use microcomputer with a data caching function, you have to disable the function before
downloading a program.
Rev.1.00 10.01.2006 page 10 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
5.5.
5.5.1.
Precautions on Debugging
When using CC32R
" If the target program contains multiple object files with the same file name, debug
information on those objects cannot be handled correctly.
" Variables that are named “bool” can be referred neither with C Watch Window nor with print
command in Script Window.
5.5.2.
When using D-CC
" If the target program has typedef declarations internally used, pay attention to the following:
(1) When displaying type definition names, respective tag names are displayed.
(2) When using type definition names to write C language expressions, be sure to use
respective tag names.
5.5.3.
Common precautions
" In the first line of a function, the stack frame for the function is not fully formed. When
referencing function parameters or auto variables, execute as many lines in the function as
can be executed.
" If a variable is declared with the same name as the type definition name declared by typedef,
you cannot reference that variable.
Rev.1.00 10.01.2006 page 11 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
5.6.
Precautions when using TW32R (V.1.00 Release 1 to V.3.00 Release 1)
When you are using TW32R version from V.1.00 Release 1 to V.3.00 Release 1, the program header
information of the load module created by the linker may not be correctly generated. This may cause
a problem that a part of the section cannot be correctly downloaded by the emulator debugger.
[Condition which triggers this problem]
It has been proved that the problem occurs when a linker script is described where the
relationship between the section execution address (VMA) and the load address (LMA) meets the
two conditions given below. In the following example, section .secB is not downloaded correctly.
(1) Any three sections are allocated to the continuous load addresses (LMA) (Figure A).
(2) Only the execution address (VMA) of the section allocated in the middle (.secB) is allocated to
the low address (Figure B).
LMA
VMA
Low address
.secB
.secA
.secB
.secC
.secA
Figure A
Figure B
.secC
High address
[Corrective action]
Try one of the following methods:
(1) Changing the section allocation sequence
When allocating the load address (LMA) of each section, change the linker script description so
that a section whose execution address (VMA) is allocated to low address (.secB) will not be
placed between the sections whose execution address is the same as the load address
(.secA, .secC).
For example, change the section allocation sequence as shown in Figure C and Figure D.
LMA
VMA
Low address
.secB
.secA
.secC
.secB
.secA
.secC
Figure C
Figure D
High address
(2) Creating a program header using the PHDRS instruction
As shown in the following example, change the linker script.
Then, the system will create the program header for each section.
[1] In each section definition, define the name to be referenced in the PHDRS instruction. Be
sure to select the different name for each section. The defined name is used to be identified in
the PHDRS instruction. You can specify any name. (It could be the same as the symbol name,
Rev.1.00 10.01.2006 page 12 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
file name or section name.) However, you cannot specify an instruction name (NETRY,
STARTUP) for the name.
[2] Use the name defined in [1] to define the program header using the PHDRS instruction so
that all the sections will be used as individual segments.
---------------------------------------------------------/* [2] */
PHDRS
{
secA PT_LOAD;
secB PT_LOAD;
secC PT_LOAD;
}
.secA Execution address : Load address
{
...
} :secA
/* [1] */
.secB Execution address : Load address
{
...
} :secB
/* [1] */
.secC Execution address : Load address
{
...
} :secC
/* [1] */
----------------------------------------------------------
5.7.
Changing memory contents of an external flash ROM area
Memory contents of an external flash ROM area can only be changed during download processing.
The memory contents of this area cannot be changed by operating directly on memory. Here, the
external flash ROM area refers to one that was registered from the "Init" dialog box using its Target
Dependence Memory setup page.
5.8.
About the scope
The scope setting function is available only when the compiler CC32R is used. When D-CC or
TW32R is used, the scope setting function is unavailable.
5.9.
About watching the local C variables
For the sake of optimization, the C compiler may place different variables at the same address. In
this case, values of the C variable may not be displayed correctly on the c watch window or other
function.
Rev.1.00 10.01.2006 page 13 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
5.10. Precautions on debugging functions in the external and extended external areas
The following debugging functions may not properly be performed in the external and extended
external areas:
(a) Storing target program to memory after downloading
(b) Rewriting memory
This problem occurs if the following three conditions are all satisfied:
(1) The target MCU belongs to any of the following MCU groups:
* the 3212x groups
* the 3217x groups
* the 3218x groups
* the 3219x group
(2) The chip operation mode of the target MCU is either of the following:
* processor mode
* MPU mode
(3) The external or extended external area concerned overlaps with the internal ROM area, as
denoted by A in the memory map below.
Internal ROM Area
In single-chip,
extended external,
and MCU modes
A
In processor and
MPU modes
Memory map figure
5.11. About using cast operators for the member variable
When you use cast operators for the member variable to refer to it as the pointer of the structure,
you would not refer to it correctly.
Rev.1.00 10.01.2006 page 14 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
5.12. On the break function using the pre-execution PC break
[Description]
When the pre-execution PC break is used as an event of a breakpoint, the break function may not be
performed properly.
[Conditions]
This problem occurs if the following four conditions are satisfied:
(1) The target MCU belongs to any of the following groups:
32170, 32171, 32172, 32173, 32174, and 32176
(2) The pre-execution PC break is used as an event of a breakpoint.
(3) The pre-execution PC break is used as an event of a chip event.
(4) The breakpoint and the chip event in (2) and (3) above are set at the same address.
[Example]
If the target program is started with a breakpoint being set in the procedure shown below, no
program break occurs when the instruction at the specified address (1000H, for example) is
executed:
(1) Open the Program window and double-click the mouse's left button in the area for setting a
breakpoint at address 1000H. A breakpoint is set at that address. In Single Chip and External
Expansion Modes of the M3217x group, address 1000H is within the internal ROM area, so the
pre-execution PC break is used as a breakpoint and "b"s are displayed in the breakpoint display
area.
(2) Follow these steps in the Trace-point setting window:
1. Click the CE0 button in the Set Chip Event area. The CE0-Set Chip Event dialog box appears.
2. Perform the following in the CE0-Set Chip Event dialog box:
2.1 Check the Enable check box.
2.2 Select "Preexe-PC 0" in the Event Type combo box.
2.3 Type H'1000 in the Address text box.
2.4 Click the OK button.
3. Click the Set button.
[Workaround]
Don't set a breakpoint and a chip event that use the pre-execution PC break as their events at the
same address.
Rev.1.00 10.01.2006 page 15 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
6.
Supplements of User’s Manual
6.1.
MCU file list provided with the PD32RM product
MCU files provided with PD32RM V.3.01 Release 00 are listed below.
Use the MCU file corresponding to your emulator system.
For the 32102 group
MCU file name
Emulator model
MCU
32102.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T5-SDI-E
M32102S6FP
MCU file name
Emulator model
MCU
32104.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32104T2-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32104T2-PTC
M32104S6FP
M32104S6WG
MCU file name
Emulator model
MCU
32121.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T5-SDI-E
M32121FCWG
For the 32104 group
For the 32121 group
For the 32170 group
MCU file name
Emulator model
MCU
32170.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32170T-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32170T-PTC
M32170F3VFP
M32170F4VFP
M32170F6VFP
For the 32171 group
MCU file name
Emulator model
MCU
32171.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32171T-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32171T-PTC
M32171F2VFP
M32171F3VFP
M32171F4VFP
For the 32172 group
MCU file name
Emulator model
MCU
32172.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32173T-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32173T-PTC
M32172F2VFP
Rev.1.00 10.01.2006 page 16 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
For the 32173 group
MCU file name
Emulator model
MCU
32173.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32173T-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32173T-PTC
M32173F2VFP
M32173F2VWG
For the 32174 group
MCU file name
Emulator model
MCU
32174.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32170T-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32170T-PTC
M32174F3VFP
M32174F4VFP
MCU file name
Emulator model
32176.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32170T-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32170T-PTC
MCU
M32176F2VFP/TFP
M32176F2VWG/TWG
M32176F3VFP/TFP
M32176F3VWG/TWG
M32176F4VFP/TFP
M32176F4VWG/TWG
For the 32176 group
For the 32180 group
MCU file name
Emulator model
MCU
32180.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32180T2-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32180T2-PTC
M32180F8TFP/VFP
M32180F8VWG
For the 32182 group
MCU file name
Emulator model
MCU
32182.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32182T2-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32182T2-PTC
M32182F3TFP/VFP
M32182F8TFP/VFP
For the 32185 group
MCU file name
Emulator model
MCU
32185.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32186T2-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32186T2-PTC
M32185F4VFP
Rev.1.00 10.01.2006 page 17 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
For the 32186 group
MCU file name
Emulator model
MCU
32186.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32186T2-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32186T2-PTC
M32186F8VFP
MCU file name
Emulator model
MCU
32192.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32192T2-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32192T2-PTC
M32192F8TFP/UFP/VFP
M32192F8VWG/UWG/TWG
MCU file name
Emulator model
MCU
32195.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32192T2-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32192T2-PTC
M32195F4VFP/UFP/TFP
For the 32192 group
For the 32195 group
For the 32196 group
MCU file name
Emulator model
MCU
32196.mcu
M32100T-EZ-E
M32100T3-SDI-E
M32100T3-SDI-E + M32192T2-PTC
M32100T5-SDI-E
M32100T5-SDI-E + M32192T2-PTC
M32196F8VFP/UFP/TFP
(Note)
When PD32RM is installed, these MCU files are stored under "MCUfiles" folder, which is created
within the folder that contains PD32RM.EXE.
Rev.1.00 10.01.2006 page 18 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
6.2.
List of flash device definition files (FDD files) provided with the PD32RM package
Before the target program can be downloaded into an external flash area, a flash target definition file
(FTD file) must be registered from the "Init" dialog box using its Target Dependence Memory tab.
This FTD file can be created using the FDD files provided with the PD32RM package. To create an FTD
file, select Flash ROM for Type: on the "Init" dialog box’s Target Dependence Memory tab and click the
Create button to open the "External Flash ROM Define" dialog box. Use this dialog box to create an FTD file.
When working on this dialog box, be sure to use the FDD file that suits the flash device used.
The table below lists the currently supported flash device type names and the flash device definition files
(FDD files) provided with PD32RM V.3.01 Release 00.
(Notes)
1. To download the target program into an external flash area, check to be sure that it can be
read from and written into the flash memory. After that, download the target program into an
external flash area.
2. The operations of some flash memory are not verified due to patterns of connection.
FDD files for Atmel flash devices
FDD file name
AT49BV1614.FDD
Flash device type name (not
including the package shape)
AT49BV1614
Remarks
FDD files for Fujitsu flash devices
FDD file name
MBM29BL160D.FDD
MBM29BL161D.FDD
MBM29BL162D.FDD
MBM29DL16XBE.FDD
MBM29DL16XTE.FDD
MBM29DL32XBE.FDD
MBM29DL32XTE.FDD
MBM29DL640E.FDD
MBM29F400BC.FDD
MBM29F400TC.FDD
MBM29F800BA.FDD
MBM29F800TA.FDD
MBM29LV160BE.FDD
MBM29LV160TE.FDD
MBM29PL160BD.FDD
MBM29PL160TD.FDD
MBM29PL3200BE.FDD
Flash device type name (not
including the package shape)
MBM29BL160D
MBM29BL161D
MBM29BL162D
MBM29DL16XBx
MBM29DL16XTx
MBM29DL32XBx
MBM29DL32XTx
MBM29DL640x
MBM29F400Bx
MBM29F400Tx
MBM29F800Bx
MBM29F800Tx
MBM29LV160Bx
MBM29LV160Tx
MBM29PL160Bx
MBM29PL160Tx
MBM29PL3200Bx
MBM29PL32TE.FDD
MBM29PL32BE.FDD
MBM29PL65LM.FDD
MBM29LV800BA.FDD
MBM29LV800TA.FDD
MBM29LV320BE.FDD
MBM29LV320TE.FDD
MBM29LV640UE.FDD
MBM29PL32Tx
MBM29PL32Bx
MBM29PL65LM
MBM29LV800Bx
MBM29LV800Tx
MBM29LV320Bx
MBM29LV320Tx
MBM29LV640Ux
Remarks
x : 1, 2, 3, 4
x : 1, 2, 3, 4
x : 1, 2, 3, 4
x : 1, 2, 3, 4
------
available only when DW/W#
pin’s logic level is low
FDD files for Intel flash devices
FDD file name
E28F016SV.FDD
E28F320J5.FDD
E28F640J5.FDD
Flash device type name (not
including the package shape)
E28F016SV
E28F320J5
E28F640J5
Rev.1.00 10.01.2006 page 19 of 28
REJ10J1494-0100
Remarks
M3T-PD32RM V.3.01 Release 00 Release Notes
FDD files for Renesas flash devices
FDD file name
M5M29FB160.FDD
M5M29FT160.FDD
M5M29GB320.FDD
M5M29GT320.FDD
M5M29KB331.FDD
M5M29KT331.FDD
M5M29KB331_WP.FDD
M5M29KT331_WP.FDD
M5M29KB641AVP.FDD
M5M29KT641AVP.FDD
Flash device type name (not
including the package shape)
M5M29FB160
M5M29FT160
M5M29GB320
M5M29GT320
M5M29KB331
M5M29KT331
M5M29KB331
M5M29KT331
M5M29KB64
M5M29KT641
Remarks
available only when WP#
pin’s logic level is high
available only when WP#
pin’s logic level is low
available only when WP#
pin’s logic level is high
FDD files for Toshiba flash devices
FDD file name
TC58FVB160.FDD
Flash device type name (not
including the package shape)
TC58FVB160
Remarks
FDD files for Macronix flash devices
FDD file name
MX29LV160B.FDD
MX29LV160T.FDD
MX29LV320B.FDD
MX29LV320T.FDD
MX29LV800T.FDD
MX29LV800B.FDD
MX26L6420.FDD
Flash device type name (not
including the package shape)
MX29LV160B
MX29LV160T
MX29LV320B
MX29LV320T
MX29LV800T
MX29LV800B
MX26L6420
Remarks
FDD files for SPANSION flash devices
FDD file name
S29GL128N.FDD
S29GL256N.FDD
S29PL032J.FDD
S29PL064J.FDD
Flash device type name (not
including the package shape)
S29GL128N
S29GL256N
S29PL032J
S29PL064J
Remarks
(Note)
When PD32RM is installed, these FDD files are stored under "FddFiles" folder, which is created
within the folder that contains PD32RM.EXE.
Rev.1.00 10.01.2006 page 20 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
6.3.
Security code check function
When starting PD32RM in which a security code is stored, the following dialog appears. Enter the
security code here. If the entered security code does not match the stored one, PD32RM will not get
started until the data in the built-in flash memory is deleted.
Enter the security code in the edit box.
Select the security code format by using a radio button in the Format group.
When checking the Save check box, the entered security code is saved.
When you try to start PD32RM at next time, the system uses the saved security code to verify
conformance to the stored security code.
Rev.1.00 10.01.2006 page 21 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
7.
Version Report
This section describes the changes in the specification.
7.1.
PD32RM V.3.01 Release 00
In this version, the following changes have been made to the previous version PD32RM V.3.00 Release 01.
7.1.1. Revisions of Restrictions
" A limitation has been corrected: If a mixed representation of source and disassembled code is saved on a text
file, a part of the disassembled code may not be saved on the file.
"
(for details, refer the RENESAS TOOL NEWS, June 16, 2006 (RSO-M3T-PD32RM-060616D))
A limitation has been corrected: When structure member variables, union member variables, or class member
variables are displayed in such a window as the C Watch window, which is capable of referencing variables, a
message may appear saying "not active", resulting in no variables being referenced.
(for details, refer the RENESAS TOOL NEWS, January 16, 2006 (RSO-M3T-PD32RM-060116D))
7.1.2. Extended Functions and Modified Specifications
" Window-related Functions
- Debugging Information tab of Init Dialog Box
# Unsupported compiler Green Hills M32R has been unavailable on the Compiler's list box.
" Others
- It has been available to prevent MCU from accepting the reset signal from outside while changing
from halt to executing of target program.
- The following MCU-files have been added.
32185.mcu
32186.mcu
32195.mcu
32196.mcu
7.2.
PD32RM V.3.00 Release 01
In this version, the following changes have been made to the previous version PD32RM V.3.00 Release 00.
7.2.1. Revisions of Restrictions
The problem that the emulator M32100T5-SDI-E might break down was fixed. (for details, refer the
RENESAS TOOL NEWS, February 16, 2006 (RSO-M32100T5-SDI-E-060216D))
7.3.
PD32RM V.3.00 Release 00
In this version, the following changes have been made to the previous version PD32RM V.2.10 Release 1.
7.3.1. Revisions of Restrictions
" A limitation has been corrected: In the C Watch window, expanding a global variable in a structure,
a union, or an array of structures or unions may cause the emulator debugger to terminate
unsuccessfully.
(for details, refer the RENESAS TOOL NEWS, September 1, 2004 (RSO-M3T-PD32RM-040901D))
" A limitation has been corrected: Information on time in real-time tracing may be displayed
incorrectly.
(for details, refer the RENESAS TOOL NEWS, August 1, 2004 (RSO-M3T-PD32RM_2-040801D))
" A limitation has been corrected: If structures, unions, classes, arrays, and pointers are expanded,
the emulator debugger may hang up.
(for details, refer the RENESAS TOOL NEWS, August 1, 2004 (RSO-M3T-PD32RM_1-040801D))
7.3.2. Extended Functions and Modified Specifications
" Renesas C/C++ Compiler for M32R Family Support
PD32RM newly supports ELF/DWARF2 format from M3T-CC32R, the Renesas C/C++ Compiler for
M32R Family, V.5.00 Release 00 and the later versions. It makes source level debugging of C++
programs available.
To debug a target program in ELF/DWARF2 format from M3T-CC32R, operate that as follows.
(1) Init Dialog Box
Rev.1.00 10.01.2006 page 22 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
Select “CC32R(M32R)” or “CC32R(M32Rx) for “Compiler”, and ELF/DWARF2.0 for Object
Format in the Debugging Information Tag.
(2) Specifying file when loading
Select an object file with “elf” extension.
" Renesas uITRON-specification V.4.0 real-time OS Support
PD32RM newly supports M3T-MR32R/4, the Renesas real-time OS for M32R Family, V.4.00
Release 00 and the later versions. It makes debugging of programs using M3T-MR32R/4 available.
" Others
- The following FDD-files have been added.
MBM29DL640E.FDD
MBM29PL65LM.FDD
M5M29KT331.FDD
M5M29KB641AVP.FDD
S29GL128N.FDD
-
MBM29PL3200BE.FDD
MBM29F800BA.FDD
M5M29KB331_WP.FDD
M5M29KT641AVP.FDD
S29PL032J.FDD
MBM29PL32TE.FDD
MBM29F800TA.FDD
M5M29KT331_WP.FDD
MX29LV800T.FDD
S29PL064J.FDD
MBM29PL32BE.FDD
M5M29KB331.FDD
M5M29KB641AVP.FDD
MX29LV800B.FDD
The following MCU-file has been added.
32192.mcu
7.4.
PD32RM V.2.10 Release 1
In this version, the following changes have been made to the previous version PD32RM V.2.00 Release 1.
7.4.1. Revisions of Restrictions
" A limitation has been corrected: A member of a struct or union may not correctly be referenced. If
you try referencing it, the debugger will unsuccessfully terminate in some cases.
(for details, refer the RENESAS TOOL NEWS, November 1, 2003
(RSO-M3T-PD32RSIM-031101D))
" A limitation has been corrected: If the Memory window remains minimized immediately after
launching the debugger, restoring or maximizing it causes the debugger to terminate
unsuccessfully.
(for details, refer the RENESAS TOOL NEWS, December 1, 2003 (RSO-M3T-PD32RM-031201D))
7.4.2. Extended Functions and Modified Specifications
" Window-related Functions
−
Trace Window
# A function has been added which displays the trace measurement results in mixed
format with two or more display modes.
# A function has been added which displays the trace measurement results distinguished
by using different colors.
−
MR Window
# A function has been added which allows the state of the following objects to be displayed
in the MR window.
Message buffers, Rendezvous ports, Mail-boxes with priority
# A function has been added which allows the state of the objects to be displayed in the MR
window during the target program running.
−
Data Trace Window
# A window has been added which allows data access information to be graphically displayed
after analyzing real-time trace measurement results.
−
Script Window
# ADDPATH command is added. This command adds the search path.
" Others
−
M32100T5-SDI-E has been available.
Rev.1.00 10.01.2006 page 23 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
7.5.
PD32RM V.2.00 Release 1
In this version, the following changes have been made to the previous version PD32RM V.1.00 Release 1.
7.5.1. Revisions of Restrictions
" A limitation has been corrected: Target programs (load modules) may not be downloaded.
(for details, refer to the MAEC TOOL NEWS, May 1, 2003)
7.5.2. Extended Functions and Modified Specifications
" Window-related Functions
- Memory Window
#Memory Window, RAM Monitor Window and Dump Window have been integrated into a new
Window.
#Memory contents can be modified by using In-Place edit function.
#The modified data are displayed hi-lighted with color.
#The splitter view has become available.
#The column numbers can be modified (1-256).
#Memory contents can be saved in the file as a text file.
- ASM Watch Window
#Memory contents, symbols, radixes and data length can be modified by using In-Place edit function.
#The modified data are displayed hi-lighted with color.
#Data can be sorted by each column.
- C Watch Window
#C Watch Window, Local Window, File Local Window, and Global Window have been integrated into
a new window.
#The display style has changed to list variable names and values.
#Memory contents can be modified by using In-Place edit function.
#The modified data are displayed hi-lighted with color.
- Program / Source Window
#Back scroll in Dis-Assemble Mode has become available.
- Time Measurement Window
#The average time can be displayed.
#The measurement results on display can be updated while the target program in operation.
- Download BehaviorTab on the “Init” dialog box
#It can be specified whether the target MCU is reset before downloading.
#The script file to be executed can be specified before downloading.
" Others
- The function, to output the information for technical support, has become available.
- The script command called “OpenWindow” has been added to open a specified window from the
Script Window.
- The file, which is opened in Program/Source window, can be opened witin the HEW, when PD32RM
started up as the external debugger of HEW.
- The time value in the measurement result of the real time trace can be displayed with the elapsed
time since the target program starts.
- The following FDD-files have been added.
MBM29LV320BE.FDD
MBM29LV800TA.FDD
MX29LV320B.FDD
-
MBM29LV320TE.FDD
MX26L6420.FDD
MX29LV320T.FDD
A function, Flash Writer, has been newly added.
Rev.1.00 10.01.2006 page 24 of 28
REJ10J1494-0100
MBM29LV640UE.FDD
MX29LV160B.FDD
MBM29LV800BA.FDD
MX29LV160T.FDD
M3T-PD32RM V.3.01 Release 00 Release Notes
8.
License Agreement
IMPORTANT
This contract is a legally valid agreement concluded regarding our software products between the
purchaser (limited to corporations) and Renesas Solutions Corporation. This contract is assumed to
have been effected upon installation of the software product by the purchaser, an act by which the
purchaser is assumed to have accepted the conditions set forth herein.
Software User License Agreement
The purchaser (hereafter called the "Purchaser") and Renesas Solutions Corporation (hereafter
referred to as "Licensor") do hereby agree to the terms and conditions as specified in this Software User
License Agreement (hereafter referred to as "Agreement") concerning the enclosed software and its
explanatory manuals.
ARTICLE 1. Definition of Terms
1. The terms used in this contract shall be construed as defined below.
(1) The "Software Product" refers to the software product provided by Licensor (product name:
M3T-PD32RM as called by Licensor) that is comprised of the following:
(a) The "Program" refers to the program that has the functions to control the Licensor's emulator
system.
(b) The "Manual" refers to technical data (including user's manuals, etc.) associated with the
program, which are provided by means of electronic documents or printed material.
(2) The "Emulator" refers to the Licensor's emulator systems whose type numbers are given below.
• M32100T-EZ-E, M32100T3-SDI-E, M32100T5-SDI-E
(3) The "Designated System" refers to the computer system managed and owned by the Purchaser, in
which the Software Product is installed and run.
Article 2. Granting of License
1. Licensor grants the Purchaser the following non-transferable, non-exclusive rights free of charge:
(1) To install the Software Product in the Designated System for the purpose of controlling the
Emulator. However, no limitations are imposed on the quantity of the Software Product that the
Purchaser can use at the same time.
(2) To print the electronic documents included with the Manual to a printing device for the purpose
of using the Software Product in conformity with paragraphs (1) above.
(3) The Purchaser can duplicate the Software Product to produce one and only one copy of it for
backup purposes.
2. When the Purchaser has installed or duplicated the Software Product in accordance with the
foregoing, the Purchaser shall keep an appropriate record describing the number of duplicates of all
of the Software Product owned, the location where they are stored, and the Designated System in
which the Software Product was installed. When requested by Licensor, the Purchaser must
promptly disclose said record to Licensor.
3. For only the rights explicitly stipulated under this contract, Licensor grants use of the Software
Product to the Purchaser. Except the rights for the Software Product that are expressly granted
under this contract, Licensor does not grant the Purchaser the license or the right of using or
Rev.1.00 10.01.2006 page 25 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
utilizing anything based on Licensor's patent rights, utility models, design rights, trademark rights,
copyrights, semiconductor circuit arrangement utilization rights, and trace secrets.
Article 3. Limitations
1. Unless granted under this contract, the Purchaser cannot transfer the right of using the Software
Product under this contract, nor can the Purchaser use, duplicate, transfer, rent or otherwise dispose
the Software Product or grant sublicenses to any third parties. However, if handling of the Software
Product in ways other than granted under this contract is wished by the Purchaser and Licensor
recognizes it as necessary, such handling may be determined separately from this contract by
consultation between the two parties.
2. The Purchaser cannot remove copyright indications from the Software Product and its duplicates.
3. The Purchaser cannot reverse-engineer, decompile, or disassemble the Software Product.
4. The Purchaser cannot print the electronic documents included with the Software Product to a
printing device in an attempt to use printout for commercial purposes.
5. The provisions set forth in this article remain effective even after this contract terminates.
Article 4. Rights to the Software Product
1. All copyrights to the Software Product belong to Licensor. No articles and clauses in this contract
convey the whole or part of said copyrights to the Purchaser.
2. The provisions set forth in this article remain effective even after this contract terminates.
Article 5. Support
1. Regarding the Software Product, Licensor provides technical support to the Purchaser in the manner
deemed appropriate by Licensor.
2. When the Purchaser wishes to upgrade the Software Product, the Purchaser will be notified of
upgrading procedures separately from this contract through Licensor's home page or by other means
deemed appropriate by Licensor. Licensor may claim payment for the cost needed for upgrading
from the Purchaser.
Article 6. Exemption Clause for Licensor
1. What is stipulated in Article 5 of this contract is the only responsibility Licensor shall assume under
this contract. Article 5 only explicitly stipulates the responsibility of Licensor under this contract, so
that whatever damages the Purchaser may suffer from the Software Product or use of it by the
Purchaser, Licensor will not provide the Purchaser with any guarantee or any warrant at all. It is
expected that the Purchaser assumes responsibility and bears the cost for problems that may occur
with respect to the Software Product.
2. The provisions set forth in this article remain effective even after this contract terminates.
Article 7. Secrecy
1. Regarding the Software Product and this contract, the Purchaser shall keep in secret the
information that has been disclosed to the Purchaser by Licensor after designating it to be secret
(which includes the Software Product, hereafter called the "Secret Information") and shall not
disclose or leak the whole or part of it to any third parties. It can only be used to control the
Licensor's emulator system, and not for any other purpose.
2. The forgoing obligation does not apply to the following:
(1) The information that the Purchaser already owned when it received the Secret Information
(2) The information that was already known when the Purchaser received the Secret Information
(3) The information that became known for reasons for which the Purchaser is not responsible after
Rev.1.00 10.01.2006 page 26 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
the Purchaser received the Secret Information
(4) The information that the Purchaser originally developed without any references to the Secret
Information
(5) The information that the Purchaser is requested to disclose by administrative agencies or courts
of law. In this case, however, the Purchaser shall, prior to disclosure, inform Licensor in writing
in order to provide Licensor with opportunities to make a compliant against the said disclosure.
3. The provisions set forth in this article remain effective for three years after this contract terminates.
Article 8. Contract Period and Termination
1. This contract becomes effective at the time the Purchaser has installed the Software Product and
remains effective until it terminates for reasons stipulated below.
2. When the Purchaser terminated the right of use under this contract by notifying Licensor of it in
writing one month earlier.
3. When the Purchaser violates one of the clauses in this contract, and said violation remains
uncorrected more than 30 days after the Purchaser received a written notice from Licensor
requesting that said violation be corrected.
4. When the Purchaser or Licensor falls under the application of any one of the following:
(a) When the Purchaser or Licensor received a petition for attachment, provisional attachment,
provisional disposition, compulsory execution, or public auction, or a petition for the
commencement of bankruptcy, special liquidation, civil resuscitation, corporate liquidation, or
company reorganization and rehabilitation procedures, or Purchaser or Licensor themselves
plead for the above.
(b) When the Purchaser or Licensor received an administrative disposition from the competent
authorities to the effect that its business be closed or its business license or business
registration be canceled.
(c) When the Purchaser or Licensor adopted a resolution to discontinue or change business or
dissolve the company.
(d) When the Purchaser or Licensor received a disposition from a relevant clearinghouse to the
effect that its transactions of bills in that clearinghouse be stopped.
(e) When the Purchaser or Licensor committed a breach of faith, has had its financial situation
worsened, or had a good reason to justify the doubt about that.
5. Notwithstanding the above provisions, even when this contract has terminated, if any different
period is stipulated in one of the clauses of this contract, it shall have priority.
Article 9. Obligations after Termination of This Contract
1. When this contract has terminated, the Purchaser must discard the Software Product, the duplicates
of the Software Product created based on this contract, and all instances of the Software Product
installed in the Designated System within 15 days from the date of termination. When requested by
Licensor, the Purchaser shall supply a document attesting to that effect to Licensor within one
month after the request.
Article 10. Other
1. Matters not stipulated in this contract and doubts arising between the Purchaser and Licensor shall
be settled by consultation between the two parties.
2. If an attempt to solve the foregoing by mutual consultation fails, giving rise to a dispute between the
Purchaser and Licensor, it shall be solved through a legal procedure before a court that is designated
as the competent court by Licensor.
3. The provisions set forth in this article remain effective even after this contract terminates.
Rev.1.00 10.01.2006 page 27 of 28
REJ10J1494-0100
M3T-PD32RM V.3.01 Release 00 Release Notes
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT
AND AGREES TO ALL TERMS AND CONDITIONS STATED HEREIN.
Rev.1.00 10.01.2006 page 28 of 28
REJ10J1494-0100