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.
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.
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.
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....................................................................
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.
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.
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.
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.
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.
M3T-PD32RM V.3.
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.
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.
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.
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.
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] */ .
M3T-PD32RM V.3.01 Release 00 Release Notes 5.10.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
