e 2 studio ISDE v6.2.0

Transcription

1 Release Note e 2 studio ISDE v6.2.0 Release Note Renesas Synergy Platform Synergy Tools & Kits Renesas Synergy e 2 studio All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website ( Rev.1.01 Mar 2018

2 Notice 1. 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 or any other use of the circuits, software, and information in the design of your product or system. Renesas Electronics disclaims any and all liability for any losses and damages incurred by you or third parties arising from the use of these circuits, software, or information. 2. Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other claims involving 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, including but not limited to, the product data, drawings, charts, programs, algorithms, and application examples. 3. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 4. You shall not alter, modify, copy, or reverse engineer any Renesas Electronics product, whether in whole or in part. Renesas Electronics disclaims any and all liability for any losses or damages incurred by you or third parties arising from such alteration, modification, copying or reverse engineering. 5. Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The intended applications for each Renesas Electronics product depends on the product s quality grade, as indicated below. "Standard": Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment; home electronic appliances; machine tools; personal electronic equipment; industrial robots; etc. "High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control (traffic lights); large-scale communication equipment; key financial terminal systems; safety control equipment; etc. Unless expressly designated as a high reliability product or a product for harsh environments in a Renesas Electronics data sheet or other Renesas Electronics document, Renesas Electronics products are not intended or authorized for use in products or systems that may pose a direct threat to human life or bodily injury (artificial life support devices or systems; surgical implantations; etc.), or may cause serious property damage (space system; undersea repeaters; nuclear power control systems; aircraft control systems; key plant systems; military equipment; etc.). Renesas Electronics disclaims any and all liability for any damages or losses incurred by you or any third parties arising from the use of any Renesas Electronics product that is inconsistent with any Renesas Electronics data sheet, user s manual or other Renesas Electronics document. 6. When using Renesas Electronics products, refer to the latest product information (data sheets, user s manuals, application notes, "General Notes for Handling and Using Semiconductor Devices" in the reliability handbook, etc.), and ensure that usage conditions are within the ranges specified by Renesas Electronics with respect to maximum ratings, operating power supply voltage range, heat dissipation characteristics, installation, etc. Renesas Electronics disclaims any and all liability for any malfunctions, failure or accident arising out of the use of Renesas Electronics products outside of such specified ranges. 7. Although Renesas Electronics endeavors to improve the quality and reliability of Renesas Electronics products, semiconductor products have specific characteristics, such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Unless designated as a high reliability product or a product for harsh environments in a Renesas Electronics data sheet or other Renesas Electronics document, Renesas Electronics products are not subject to radiation resistance design. You are responsible for implementing safety measures to guard against the possibility of bodily injury, injury or damage caused by fire, and/or danger to the public in the event of a failure or malfunction of Renesas Electronics products, 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 and impractical, you are responsible for evaluating the safety of the final products or systems manufactured by you. 8. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas Electronics product. You are responsible for carefully and sufficiently investigating applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive, and using Renesas Electronics products in compliance with all these applicable laws and regulations. Renesas Electronics disclaims any and all liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations. 9. Renesas Electronics products and technologies shall 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. You shall comply with any applicable export control laws and regulations promulgated and administered by the governments of any countries asserting jurisdiction over the parties or transactions. 10. It is the responsibility of the buyer or distributor of Renesas Electronics products, or any other party who distributes, disposes of, or otherwise sells or transfers the product to a third party, to notify such third party in advance of the contents and conditions set forth in this document. 11. This document shall not be reprinted, 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. (Note 1) "Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its directly or indirectly controlled subsidiaries. (Note 2) "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics. (Rev November 2017)

3 Scope Release Note This document describes the release notes for the Renesas Synergy support in the e 2 studio ISDE (Integrated Solution Development Environment) v This version of e 2 studio supports SSP v1.4.z software, executing on hardware platforms DK-S124, DK-S128, DK-S3A7, DK-S7G2, SK-S7G2, PK-S5D9, TB-S3A6, TB-S3A3, TB-S3A1, TB-S5D5, and PE-HMI1Synergy MCU Groups. Release information e 2 studio Release Version Supported SSP Versions v6.2.0 v1.4.0 R20UT4243EU0101 Rev.1.01 Contents 1. Installing e 2 studio ISDE v Using the Synergy Platform Installer Using the individual e 2 studio Installer Summary of New Features and Updates from the previous e 2 studio release from the Renesas Synergy Gallery (v ) Updated SEGGER J-Link Arm DLL Support for Upgrading Projects from SSP v1.2.z/v1.3.z to SSP v New Launch Bar Updated Smart Browser Improved Stack Usage display in the RTOS Resources view Added XML Comparator Option to close debug views that are not supported by the current debug session Synergy Hardware Platform Support Issues fixed in Release v Transform configuration to another device button not functional Wrong symbol information when re-downloading while connected Renaming a Thread does not migrate user edits to new thread_entry.c file Problem with cleaning IAR projects Trace View non-functional for S124/S Issues on some dialogs when using high-definition displays e 2 studio fails to auto-upgrade an imported project if the imported project has no.module_descriptions folder and its original SSP version is not installed Compiler warnings in the auto-generated code e 2 studio ID Codes Connection string needs Endian change Known Issues in Release v Multiple definition Linker errors when using both Library and Source for Express Logic components. 8 R20UT4243EU0101 Rev.1.01 Page 1 of 12

4 5.2 Problems with Synergy Expressions showing incorrect values IAR Error Parser does not recognize errors triggered by the #error directive Switching Board/Device on the BSP tab changes project settings immediately, even if Synergy configuration is not saved Repeated setting of Trace Start and Stop Eventpoints can lead to a situation where the Eventpoints fail to set Default Core Clock for SWV usage needs to be set manually Trace find and filter functionality not supported Using a placeholder in the Synergy license dialog causes an exception Headless build issue with respect to Synergy license file Trace view can sometimes fail with 0 records for Synergy S3 devices Enabling BSD sockets in ThreadX source corrupts data in RTOS Resources view and Debug view ALeRASE ID code unlock does not work correctly e2 studio allows importing projects with spaces in the project name RTOS Resources View can cause e 2 studio to hang (stacks tab) GCC newlib-nano library does not support C++ exception Memory Usage view show no information of Memory Usage Build fails with secure builder required error after Migrating IAR v7.x tool chain project to IAR v8.x Synergy project editor crashes on attempt to migrate a project with no module _description and old SSP version in the tool with only a new major version of SSP Fails to Run program into TB-S1JA at the first time download IAR v8.21 has issues while running the projects with SSP v R20UT4243EU0101 Rev.1.01 Page 2 of 12

5 1. Installing e 2 studio ISDE v Using the Synergy Platform Installer The easiest way to install e 2 studio v6.2.0 along with SSP v1.4.0 and the GNU Arm compiler v4.9.3 (GCC_4.9_2015q3) is to use the associated Synergy Platform Installer. Go to and download the Synergy Platform Installer by clicking the Download Platform Installer button and selecting the option e2 studio. Unzip it, then double-click the installer and follow the directions on the screen. The Synergy Platform Installers allows you to either do a 'Quick' or a 'Custom' installation. The quick installation option installs all the mandatory components with no user input required, while the custom installation option provides options for you to select the optional components that you would like to install along with the mandatory components. The following components will be installed with the Synergy Platform Installer with e 2 studio: Renesas Synergy Software Package (SSP) v1.4.0 (mandatory component) e 2 studio ISDE v6.2.0 with support for Renesas Synergy (mandatory component) GCC v4.9.3 (optional, but recommended component) SSP v1.4.0 User manual (optional, but recommended component) Express Logic GUIX Studio v (optional component) Express Logic TraceX v5.2.0 (optional component) Other add-ons as required After the installation is complete, run e 2 studio to get started with Renesas Synergy. 1.2 Using the individual e 2 studio Installer To install e 2 studio v6.2.0 individually (without SSP), download the individual e 2 studio v6.2.0 installer (.zip) from Unzip it, then double-click the installer and follow the directions on the screen. Notes: If you already have an older version of e 2 studio installed on your PC, it is highly recommended to make a clean installation of e 2 studio v6.2.0 into a different location. (This will allow you to start an older version later if required, for example, for upgrading Synergy projects.) Make sure to include Synergy in the Device Family section of the installer. Do not deselect any of the optional components the installer presents to you in the Components section of the installer. These components are required for proper Synergy support. The latest GNU Arm compiler that the Renesas Synergy Software Platform (SSP) has been tested (GCC_4.9_2015q3) is also part of the installer. Unless you already have this compiler installed, it is highly recommended that you check the box to install this toolchain since the Renesas Synergy Software Package (SSP) has been tested with this version of GCC. Make sure to select Add path to the environment variables during the GCC Arm installation. This ensures easy registration of the toolchain with e 2 studio. The individual e 2 studio v6.2.0 installer does NOT include the Renesas Synergy Software Package (SSP). There are separate SSP installers available for download as Download Standalone Installer on Make sure to close e 2 studio before running the SSP installer. After you install SSP, your SSP Evaluation License will be located in the following directory: <e2_studio_base_dir>\internal\projectgen\arm\licenses\ After the installation is complete, run e 2 studio. R20UT4243EU0101 Rev.1.01 Page 3 of 12

6 2. Summary of New Features and Updates from the previous e 2 studio release from the Renesas Synergy Gallery (v ) 2.1 Updated SEGGER J-Link Arm DLL The Segger J-Link Arm dll distributed with e 2 studio has been updated to v6.20h. 2.2 Support for updating projects from SSP v1.2.z/v1.3.z to SSP v1.4.0 SSC v6.2.0 includes automated support for updating projects from SSP v1.2.z/v1.3.z to SSP v Projects are updated by changing the SSP version on the BSP tab from SSP v1.2.z / v1.3.z to SSP v1.4.0, re-generating the project content, and re-building the project. 2.3 New Launch Bar e 2 studio v6.2.0 features a new Launch Bar. This launch bar makes it easier to understand what happens when the build and debug buttons are pressed. The selected project and debug configuration in the drop list will provide the context for the operation. 2.4 Updated Smart Browser The Smart Browser view has been enhanced to show when updates are available for items shown within the user interface. When items such as updates to documents or new tool news information are available, a notification bubble will be displayed informing you that new items are available. R20UT4243EU0101 Rev.1.01 Page 4 of 12

7 2.5 Improved Stack Usage display in the RTOS Resources view Stack usage is now shown in a graphical way when using the Partner OS plugin and ThreadX. 2.6 Added XML Comparator e 2 studio now has an XML file comparison tool built into the UI. This can be used for the configuration.xml files in the Synergy Configuration Editor. Right click on the file in the project tree that needs comparison and select Compare With->Local History The following dialog is then displayed: This is the list of revisions of the file that was selected in the project tree. Double clicking an instance of the file will then compare it with the current version on disk. A difference window is shown showing the differences: R20UT4243EU0101 Rev.1.01 Page 5 of 12

8 2.7 Option to close debug views that are not supported by the current debug session e 2 studio v6.2.0 includes a new option to close any debug views that are not supported by the current Synergy debug session. This is available from the Window menu under the Perspective menu. Selecting the device will close all windows not supported by that device. Note this menu item is only available in the debug perspective. 3. Synergy Hardware Platform Support Platform Version Description PE-HMI1 2.0 or later Product Example Human Machine Interface 1 for S7G2 DK-S7G2 3.1 or later Development Kit for S7G2 DK-S3A7 2.0 or later Development Kit for S3A7 DK-S or later Development Kit for S124 DK-S or later Development Kit for S128 PK-S5D9 1.0 or later Promotion Kit for S5D9 SK-S7G2 3.1 or later Starter Kit for S7G2 TB-S5D5 1.0 or later Target Board for S5D5 TB-S3A6 1.0 or later Target Board for S3A6 TB-S3A3 1.0 or later Target Board for S3A3 TB-S3A1 1.0 or later Target Board for S3A1 4. Issues fixed in Release v Transform configuration to another device button not functional In e 2 studio v , the Transform configuration to another device button in the Pin Configurator was not functional yet. Issue ID: 9793 This issue is fixed in e 2 studio v R20UT4243EU0101 Rev.1.01 Page 6 of 12

9 4.2 Wrong symbol information when re-downloading while connected In e 2 studio v , if you are running a debug session and you are connected to a target, if you then modify a source file and rebuild, the code re-flashes, but the debug symbol information is incorrect. Issue ID: 6859 This issue is fixed in e 2 studio v Renaming a Thread does not migrate user edits to new thread_entry.c file In e 2 studio v /ssp v1.3.z, when renaming a thread symbol using the Synergy configurator and re-generating the project content, a new thread_entry.c file will be created with template content, and the old thread_entry.c file will remain in the project. If you have edited thread_entry.c, your changes are not moved to the new file. The old file remains in the project but will not be called. Issue ID: 6945 In e 2 studio v6.2.0/ssp v1.4.0, when renaming a thread symbol using the Synergy configurator and saving the configuration.xml file (before re-generating the project content), a Refactoring wizard will be presented. After previewing and agreeing to the suggested changes, the project will be refactored and the thread entry file will be renamed according to the new thread symbol. You can then re-generate the project content and re-build the project. 4.4 Problem with cleaning IAR projects In e 2 studio v , Synergy IAR compiler projects fail to clean when USBX and other deep file paths are used. Issue ID: 7597 This issue is fixed in e 2 studio v Trace View non-functional for S124/S128 In e 2 studio v , the Trace View is nonfunctional when debugging S1-based projects. Issue ID: 8848 This issue is fixed in e 2 studio v6.2.0/ssp v Issues on some dialogs when using high-definition displays In e 2 studio v , when using high-definition displays, e 2 studio can have issues on some dialogs. In particular, when using the Synergy project wizard, you cannot see the link to change the license file. Issue ID: This issue is fixed in e 2 studio v e 2 studio fails to auto-upgrade an imported project if the imported project has no.module_descriptions folder and its original SSP version is not installed In e 2 studio v5.4.0, if you import a project that was exported without the.module_descriptions folder, and the SSP version the project was originally created with is not installed (only a newer one), then the Synergy Configuration Editor crashes on opening configuration.xml (during the attempt to upgrade the project). Issue ID: This issue is fixed in e 2 studio v6.2.0 for minor version updates of SSP as described in the reproduction steps, but still an issue with SSP major version update. 4.8 Compiler warnings in the auto-generated code. The ISDE Messaging Configurator generates a type casting (uint16_t) for event class which is not required and leads to a warning in IAR builds. Issue ID: This issue is fixed in e 2 studio v R20UT4243EU0101 Rev.1.01 Page 7 of 12

10 4.9 e 2 studio ID Codes Connection string needs Endian change. When ID Codes have been provided in an executable and then downloaded into ROM, following a reset the ID Code information must be provided in order to connect via JLink. When entering the ID code the endian of the data must be reversed. Issue ID: This issue is fixed in e 2 studio v Known Issues in Release v Multiple definition Linker errors when using both Library and Source for Express Logic components By default, libraries are added to a project when adding an Express Logic X-Ware component (for example, ux for USBX ). But a user also has the option to add the source code for an X-Ware module to the project (for example, ux_src for USBX ). Projects using both the source and the library may experience multiple definition Linker errors during build. Issue ID: 9808 To make users aware of this, e 2 studio displays an error marker after adding source code for an X-Ware module to your project: If your project builds fine after adding the source (that is, you don't get those linker errors), you can turn off the error marker in the Properties for the source module by following the steps below: 1. Click on the X-Ware source module in the Threads tab. 2. Go to the Properties View. 3. Scroll all the way down to the bottom of the properties. 4. Set the Show linkage warning property to Disabled. If you do encounter these linker errors, perform the following steps to resolve them: 1. Access the linker settings in e 2 studio at Project > Properties > C/C++ Build > Settings > Tool Settings > Cross ARM C Linker > Libraries. 2. On the Libraries pane, remove the library for which you also included source code from the list so it won t get linked. 3. Click Apply and OK. 4. Rebuild your project. The build errors related to multiple definitions should be gone. Note: You will have to do this each time a clean build is attempted or whenever project content is re-generated. 5.2 Problems with Synergy Expressions showing incorrect values In some cases, when you are debugging with Synergy, the Expressions View can disagree with the underlying value of the variable in the memory view. To avoid this, enable the real-time refresh feature in the Expressions View, or remove and add the variable back into the Expressions View. Issue ID: IAR Error Parser does not recognize errors triggered by the #error directive The IAR Error Parser does not recognize errors triggered by the #error directive and cannot be configured to do so by the user. This can be resolved by enabling the GCC error parser. Issue ID: 7551 R20UT4243EU0101 Rev.1.01 Page 8 of 12

11 5.4 Switching Board/Device on the BSP tab changes project settings immediately, even if Synergy configuration is not saved When using the Synergy configurator, if the board and/or the device is changed on the BSP tab, the project options will change immediately if the core type was changed (for example, from a Cortex-M4 (S3A7, S7G2) to a Cortex-M0+ (for example, S124). These project option changes will be retained even if the Synergy configuration is not saved. Issue ID: Repeated setting of Trace Start and Stop Eventpoints can lead to a situation where the Eventpoints fail to set On Synergy devices, repeated setting of Trace Start and Stop Eventpoints can lead to a situation where the Eventpoints fail to set. Workaround: Disconnect from the target and reconnect. Issue ID: Default Core Clock for SWV usage needs to be set manually On Synergy devices, the default Core Clock value for SWV usage must be manually set to the same as the system clock (in MHz). For S7 devices (where the trace clock is halved), this should be set at half the system clock. Issue ID: Trace find and filter functionality not supported Trace find and filter functionality in the Trace view is currently not supported for Arm -based devices. Issue ID: Using a placeholder in the Synergy license dialog causes an exception Using a placeholder in the Synergy license dialog causes an exception. Use a full path to the file instead. Issue ID: Headless build issue with respect to Synergy license file When using the headless build functionality with Synergy, the build will not execute unless the license file for the SSP is defined correctly. Issue ID: Trace view can sometimes fail with 0 records for Synergy S3 devices On Synergy S3-based devices, the trace data display in the Trace view can sometimes fail with 0 records. Issue ID: Enabling BSD sockets in ThreadX source corrupts data in RTOS Resources view and Debug view When enabling BSD sockets in the ThreadX source code (via the Threads tab in the Synergy Project Editor, the Properties view), updates to the RTOS Resources view and the e 2 studio Debug view will no longer work correctly. Issue ID: ALeRASE ID code unlock does not work correctly Currently the use of the special ALeRASE ID code unlock does not work correctly with e 2 studio. The device will remain locked. The workaround is to use the ALeRASE code in the RFP tool instead. See: Issue ID: R20UT4243EU0101 Rev.1.01 Page 9 of 12

12 5.13 e2 studio allows importing projects with spaces in the project name e 2 studio v6.2.0 allows importing projects with spaces (that is, blank characters) in the project name, that may lead to build errors. Workaround: Don't rename an existing project with a project name that includes spaces. (e 2 studio does not allow the creation of projects with spaces in the project name.) Issue ID: RTOS Resources View can cause e 2 studio to hang (stacks tab) When viewing the Stacks tab in the RTOS Resources view while debugging projects that include threads with large stack sizes, the RTOS Resources view may stop working, causing e 2 studio to stop responding. Workaround: If you experience this issue, close and restart e 2 studio. In your next debug session, avoid navigating to the Stacks tab in the RTOS Resources view. Issue ID: GCC newlib-nano library does not support C++ exception Users cannot make C++ exception handling work with libc_nano library (if '--specs==nano-specs' specified in GCC linker option). The exception ends up in the default handler gnu_cxx:: verbose_terminate_handler() instead of users' catch(...) handler. Workaround: Do not use '--specs==nano-specs' option for C++ project, or refer to a post to the GNU ARM Embedded Toolchain community to find out another solution. Issue ID: Memory Usage view show no information of Memory Usage Memory usage view of diagnostic perspective in e 2 studio v6.2.0 shows no information on memory usage for any Synergy project. Issue ID: Build fails with secure builder required error after Migrating IAR v7.x tool chain project to IAR v8.x Importing an existing project with IAR v7.x toolchain to e 2 studio v6.2.0 with IAR toolchain v8.x updates the command line by removing the isde call causing the build to fail with the errors secure build required to build the file. Workaround: Go to Properties of the project: 1. Add environment variable if missing: SECURE_BUILD_COMMAND: ${renesas.support.targetloc:synergy-build} /isdebuild 2. Update Command Line pattern IAR C/C++ Compiler for ARM setting if following command is missing: ${SECURE_BUILD_COMMAND} 3. Update Command Line pattern IAR C/C++ Assembler for ARM if following command is missing: ${SECURE_BUILD_COMMAND} Issue ID: Synergy project editor crashes on attempt to migrate a project with no module _description and old SSP version in the tool with only a new major version of SSP In e 2 studio v6.2.0, if you import a project that was exported without the.module_descriptions folder, and the SSP version the project was originally created with, is not installed (only a new major version is installed), then the Synergy Configuration Editor crashes on opening configuration.xml (during the attempt to upgrade the project). Issue ID: R20UT4243EU0101 Rev.1.01 Page 10 of 12

13 5.19 Fails to Run program into TB-S1JA at the first time download Download an application for the first time into the TB-S1JA Kit and run, the program will halt in default exception handler. Workaround: There are two workarounds available: 1. Download the same application again and run. 2. Download and install the latest version of Segger v6.30g where the issue has been fixed. Issue ID: SWIOT IAR v8.21 has issues while running the projects with SSP v1.4.0 The newly introduced support for ID Codes may cause an error when using the IAR Flash loader to program a board. It will also cause very large (around 1 gigabyte).bin files to be generated. Workaround: Open the linker script file (*.icf) in notepad and comment out or remove the lines that contain the text "ID_CODE" and save the file. Issue ID: SWIOT R20UT4243EU0101 Rev.1.01 Page 11 of 12

14 Website and Support Support: Technical Contact Details: America: Europe: Japan: All trademarks and registered trademarks are the property of their respective owners. R20UT4243EU0101 Rev.1.01 Page 12 of 12

15 Revision History Rev. Date Description Page Summary 1.00 Dec 13, Initial version Updates for 1.4.0

16 Publication Date: Rev.1.01 Published by: Renesas Electronics Corporation

17 SALES OFFICES Refer to " for the latest and detailed information. Renesas Electronics America Inc Murphy Ranch Road, Milpitas, CA 95035, U.S.A. Tel: , Fax: Renesas Electronics Canada Limited 9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3 Tel: Renesas Electronics Europe Limited Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K Tel: , Fax: Renesas Electronics Europe GmbH Arcadiastrasse 10, Düsseldorf, Germany Tel: , Fax: Renesas Electronics (China) Co., Ltd. Room 1709 Quantum Plaza, No.27 ZhichunLu, Haidian District, Beijing, P. R. China Tel: , Fax: Renesas Electronics (Shanghai) Co., Ltd. Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, P. R. China Tel: , Fax: Renesas Electronics Hong Kong Limited Unit , 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong Tel: , Fax: Renesas Electronics Taiwan Co., Ltd. 13F, No. 363, Fu Shing North Road, Taipei 10543, Taiwan Tel: , Fax: Renesas Electronics Singapore Pte. Ltd. 80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore Tel: , Fax: Renesas Electronics Malaysia Sdn.Bhd. Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, Petaling Jaya, Selangor Darul Ehsan, Malaysia Tel: , Fax: Renesas Electronics India Pvt. Ltd. No.777C, 100 Feet Road, HAL 2nd Stage, Indiranagar, Bangalore , India Tel: , Fax: Renesas Electronics Korea Co., Ltd. 17F, KAMCO Yangjae Tower, 262, Gangnam-daero, Gangnam-gu, Seoul, Korea Tel: , Fax: Renesas Electronics Corporation. All rights reserved. Colophon 5.0

18 R20UT4243EU0101