Transcript
APPLICATION NOTE
Renesas USB MCU
R01AN2293EJ0102 Rev.1.02 Dec 28, 2015
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules Introduction This document describes the following sample firmware: USB Host Communication Devices Class Driver for USB Mini Firmware using Firmware Integration Technology. The sample firmware is referred to below as the HCDC. During actual software development, make sure to refer to the USB Host Communication Devices Class Driver for USB Mini Firmware using Firmware Integration Technology application note (document No. R01AN2167EJ) in combination with the USB Basic Mini Host and Peripheral Driver using Firmware Integration Technology application note (document No. R01AN2166EJ) and the user’s manual (hardware) of the microcontroller used.
Target Device RX111 Group RX113 Group RX231 Group The operation of this program has been confirmed using the Renesas Starter Kit (RSK).
Contents 1. Introduction ..................................................................................................................................... 2 2. Software Configuration................................................................................................................... 6 3. Sample Application ......................................................................................................................... 7 4. Class Driver Overview .................................................................................................................. 15 5. Using the e2 studio project with CS+ ........................................................................................... 16
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 1 of 17
Renesas USB MCU 1.
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Introduction
1.1
Functions
The HCDC conforms to the Abstract Control Model of the USB communication device class (CDC) specification and implements communication with CDC devices. The HCDC provides the following functionality: ・ Performs communication class data transfer when a CDC device is connected.
1.2
FIT Module Configuration
The HCDC comprises the following FIT modules and a sample application: Table 1-1
FIT Module Configuration
FIT Module
Board Support Package Module Using Firmware Integration Techology Renesas USB MCU USB Basic Host and Peripheral firmware
using Firmware Integration Techology Renesas USB MCU USB Host Communication Devices Class Driver (CDC) using Firmware Integration Techology RX Family DTC Module Using Firmware Integration Techology
Folder Name
Version
r_bsp
2.90
r_usb_basic_mini
1.02
r_usb_hcdc_mini
1.02
r_dtc_rx
2.03
Refer to the related documentation for details of each FIT module. Note that the latest versions of the FIT modules used by the sample firmware are available for download from the following website: Renesas Electronics website: http://www.renesas.com/
1.3
Operating Environment
The environment required for the HCDC to operate is described below: 1)
Evaluation Board a) Using a RX111 Group microcontroller Renesas Starter Kit for RX111 (RSKRX111): Product No: R0K505111C001BR RX111 Group Renesas Microcontroller Development Starter Kit from Renesas Electronics b) Using a RX113 Group microcontroller Renesas Starter Kit for RX113 (RSKRX113): Product No: R0K505113C010BR RX113 Group Renesas Microcontroller Development Starter Kit from Renesas Electronics c) Using a RX231 Group microcontroller Renesas Starter Kit for RX231 (RSKRX231): Product No: R0K505231C010BR RX231 Group Renesas Microcontroller Development Starter Kit from Renesas Electronics
2)
Development Environment a) b) c)
3)
e studio integrated development environment, from Renesas Electronics RX Family C/C++ compiler package, version 2.03.00, from Renesas Electronics E1 or E20 emulator from Renesas Electronics 2
Other a) b) c) d) e)
Host PC for emulator (Microsoft Windows® 7, Windows® 8, or Windows® 8.1)* CDC device USB cable User cable (packaged with E1 or E20 emulator) Emulator cable (packaged with E1 or E20 emulator)
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 2 of 17
Renesas USB MCU 1.4
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Setup
1.4.1
Hardware
Figure 1-1 shows an example operating environment for the HCDC. Refer to the associated instruction manuals for details on setting up the evaluation board and using the emulator, etc.
Host Communications Device Class Driver (HCDC)
+ USB Basic Host Driver Serial port communication target device (PC with built-in serial port)
CDC device
CDC Host
Enumeration and Class request (PIPE0 Control Transfer)
Evaluation Board
USB Port
Data transfer (PIPE1,2 Bulk transfer) Class notification (PIPE6 Interrupｔ transfer)
USB Port
RS232C-USB converter etc
Serial port communication target device
Serial Port
RS232C cable
USB cable
Emulator Host PC for emulator
OS:Windows 7、Windows 8、Windows 8.1 Integrated development environment:e2studio
C/C++ Compiler Package for RX Family
Figure 1-1
Example Operating Environment
Table 1-2 shows the evaluation board on which operation has been confirmed. Table 1-2
R01AN2293EJ0102 Dec 28, 2015
Evaluation Board on which HCDC Operation Has Been Verified
Rev.1.02
MCU
Evalulation Board
RX111 RX113
RSKRX111 RSKRX113
RX231
RSKRX231
Page 3 of 17
Renesas USB MCU 1.4.2
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Software Setup e2 studio
1) a)
Start e2 studio
b)
If you start up e2 studio at first, the following dialog is displayed. Specify the folder to store the project in this dialog.
c)
Click Workbench icon
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 4 of 17
Renesas USB MCU 2)
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Import the project to the workspace a)
Select [File] > [Import]
b)
Select “General => Rename & Import Existing C/C++ Project into Workspace””
Select the root directory of the project, that is, the folder containing the “.cproject” file.
c)
Click “Finish”. You have now imported the project into the workspace. Note that you can import other projects into the same workspace.
3)
Generate the binary target program by clicking the “Build” button.
4)
Connect the target board to the debug tool and download the executable. The target is run by clicking the “Run” button.
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 5 of 17
Renesas USB MCU 2. 2.1
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Software Configuration Module Configuration
The HCDC transfers data to and from a device via the HCD and reports the results to the APL. Also, it reports data transfer requests from the APL to devices via HCDC and HCD. Figure 2-1 shows the module configuration of the HCDC, and Table 2-1 lists the functions of the modules.
User application（APL）
USB Host Communication device driver（HCDC）
USB Host control driver（HCD）
USB Host controller（H/W）
Figure 2-1
Module Configuration
Table 2-1
Functions of Modules
Module Name
Function
APL
Sample application program
HCDC (r_usb_hcdc_mini)
CDC Class Driver ・ Sends CDC-related requests from the APL and data transfer requests to the HCD. USB host hardware control driver
HCD (r_usb_basic_mini)
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 6 of 17
Renesas USB MCU 3.
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Sample Application
3.1
Application Specifications
The HCDC sample application (APL) uses the switches and liquid crystal display (LCD) mounted on the RSK. The main functions of the APL are as follows: 1. 2. 3. 4.
5. 6.
3.1.1
Sends receive (Bulk In transfer) requests to the CDC device and receives data. Transfers received data to the CDC device by means of Bulk Out transfers (loopback). Makes RTS and DTR settings by means of the class request SET_CONTROL_LINE_STATE. Makes communication speed and other settings when switches on the evaluation board are operated. The communication speed and other settings are made by transmitting the class request SET_LINE_CODING to the CDC device. This class request can be used to set the communication speed, number of data bits, number of stop bits, and the parity bit. Acquires the communication setting values of the CDC device by sending the class request GET_LINE_CODING to the CDC device. Reports changes in the line status to the application program.
Data Transfer Image
Figure 3-1 shows the data transfer image. Terminal software Text input/output monitor
CDC Host
CDC device
USB communication
Text data "ABCDefgh"
Text data "ABCDefgh"
Evaluation Board
USB PORT
Text data "ABCDefgh"
Serial communication
USB PORT Text data "ABCDefgh"
RS232C-USB convertor, etc.
Serial PORT
Serial PORT Text data "ABCDefgh"
PC with built-in serial port
Host Communications Device Class Driver (HCDC)
+ USB Basic Host Driver
Figure 3-1 Data Transfer (Loopback) Image
3.1.2
Switch
The method of changing the communication speed by operating the switches is as follows: 1. 2.
Press the communication speed select switch to choose the communication speed After choosing the communication speed, press the communication speed setting switch to perform data communication at the selected communication speed.
Table 3-1 shows the switch input specification. Table 3-1 Switch Name
Switch Number
Switch input specification Function
Communication speed selection switch
Switch2
Selects the communication speed. The available communication speeds (bps) are: 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, 115200
Communication speed setting switch
Switch3
Changes the communication speed to the value chosen using the communication speed select switch.
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 7 of 17
Renesas USB MCU 3.2
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Application Processing
The application comprises two parts: initial settings and main loop. An overview of the processing in these two parts is provided below.
3.2.1
Initial setting
Initial settings consist of MCU pin settings, USB driver settings, and initial settings to the USB controller.
3.2.2
Main Loop
The main loop performs the following processing: 1.
The APL manages the states and the events associated with them. The APL first checks the state of the connected device (see Table 3-2). This state is stored in a member of a structure managed by the APL (see 3.2.3 State and Event Management).
2.
Next, the APL checks the events related to the state (see Table 3-3) and performs the associated processing. After processing an event, the APL changes the state if necessary. These events are stored in members of a structure managed by the APL. (see 3.2.3 State and Event Management )
An overview of the processing performed by the APL is shown below: HCDC APL (usb_main)
Initial setting
STATE_ATTACH ?
Y
Attach processing
Y
Class request processing
Y
Data transfer processing
N STATE_CLASS_ REQUEST ?
N STATE_DATA _TRANSFER ?
N STATE_DETACH ?
Y
Detach processing
N
Figure 3-2
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Main Loop processing
Page 8 of 17
Renesas USB MCU
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Table 3-2 List of States State Processing Overview
State
Related Event
STATE_ATTACH
Attach processing
EVENT_CONFIGURD
STATE_CLASS_REQUEST
Class request processing
EVENT_CLASS_REQUEST_START EVENT_CLASS_REQUEST_COMPLETE
STATE_DATA_TRANSFER
Data transfer processing
EVENT_READ_START EVENT_READ_COMPLETE EVENT_WRITE_START EVENT_WRITE_COMPLETE EVENT_NOTIFY_READ_START EVENT_NOTIFY_READ_COMPLETE
STATE_DETACH
EVENT_SW_INPUT --
Detach processing
Table 3-3 List of Events Event
3.2.3
Outline
EVENT_CONFIGURD EVENT_CLASS_REQUEST_START
USB device connecting completion Request of sendig the class request
EVENT_CLASS_REQUEST_COMPLETE EVENT_READ_START
Class request complete Data read request
EVENT_READ_COMPLETE EVENT_WRITE_START
Data read complete Data write request
EVENT_WRITE_COMPLETE EVENT_NOTIFY_READ_START
Data write complete Notification receive request
EVENT_NOTIFY_READ_COMPLETE EVENT_SWITCH_INPUT
Notification receive complete Switch Input
EVENT_NONE
No event
State and Event Management
Members (state, event[]) of the following structure are used to manage states and events. This structure is prepared by the APL. typedef struct DEV_INFO { uint16_t state; uint16_t event_cnt; uint16_t event[EVENT_MAX]; uint16_t class_request; } DEV_INFO_t;
/* Structure for CDC device control */ /* State for application */ /* Event count */ /* Event */ /* Class Request Type. */
[Note] If the processing to get the event determines that the event to be fetched is not present, the event is set to “EVENT_NONE.”
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 9 of 17
Renesas USB MCU
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
An overview of the processing associated with each state is provided below.
1.
Attach Processing (STATE_ATTACH )
== Outline == In this state, processing is performed to notify the APL that a CDC device has attached to the RSK board and that enumeration has finished, and the state changes to STATE_CLASS_REQUEST. == Description == ① ②
③
In the APL, first the initialization function sets the state to STATE_ATTACH and the event to EVENT_NONE. The state continues to be STATE_ATTACH until an CDC device is connected, and cdc_connect_wait() is called. When an CDC device is connected and enumeration completes, the function cdc_configured is called by the callback function usb_hsmpl_device_state, this function cdc_configured issues the event EVENT_CONFIGURD. Note that this callback function usb_hsmpl_device_state is specified in the member statediagram of structure usb_hcdreg_t. In event EVENT_CONFIGURD, the state changes to STATE_CLASS_REQUEST and the event EVENT_CLASS_REQUEST_START is issued.
Attach processing
Callback function (cdc_configured)
CDC device connected?
N Y EVENT_CONFIGURED ?
N
Y
Enumeration in progress
Set event to EVENT_CONFIGURED
Enumeration comleted
End
Change state to STATE_CLASS_REQUEST
Issue EVENT_CLASS_REQUEST_ START
End
Figure 3-3
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Flowchart of Attach Processing
Page 10 of 17
Renesas USB MCU 2.
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Class Request Processing (STATE_CLASS_REQUEST)
== Outline == In this state, processing is performed to transmit class requests to the CDC device. When transmission of a separately specified class requests finishes, the state changes to STATE_DATA_TRANSFER. == Description == ① ② ③ ④
In this state, first EVENT_CLASS_REQUEST_START is processed, and a class request transmit request is sent to the USB driver. When class request transmit processing completes, the callback function cdc_class_request_complete is called. This callback function issues EVENT_CLASS_REQUEST_COMPLETE. The processing described in ① and ② is repeated, and the class requests SetControlLineState, SetLineCoding and GetLineCoding are transmitted to the CDC device in sequence. When transmission of the class request GetLineCoding finishes, the state changes to STATE_DATA_TRANSFER, and the event is set to EVENT_USB_READ_START. Note that the event can also be set to EVENT_COM_NOTIFY_RD_START by making the following definition: == r_usb_hcdc_mini_config.h == #define USB_HCDC_IF_CLASS USB_IFCLS_CDCC Class request processing (cdc_class_request)
Callback function (cdc_class_request_complete)
EVENT acquisition processing (cdc_event_get)
Set event to EVENT_CLASS_REQUEST_ COMPLETE
EVENT_CLASS_ REQUEST_START?
End
N
Y N
EVENT_CLASS_ REQUEST_COMPLETE?
Y
Send class request transmit requests to send the following class requests in sequence: 1. SetControlLineState 2. SetLineCoding 3. GetLineCoding
Is the finished class request GetLineCoding?
Y
N
Set event to EVENT_CLASS_REQUEST_ START (Transmit other class request)
Change state to STATE_DATA_TRANSFER
Set event to EVENT_USB_READ_START
End
Figure 3-4
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Flowchart of Class Request Processing
Page 11 of 17
Renesas USB MCU 3.
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Data Transfer Processing (STATE_DATA_TRANSFER)
== Outline == This loopback processing routine receives data from the CDC device and then transmits the same data, unmodified, back to the CDC device. In addition, processing is performed to change the transfer speed when switches are pressed. == Description == ①
② ③ ④ ⑤ ⑥ ⑦
When transmission of the class request to the CDC device completes, the state transitions to STATE_DATA_TRANSFER. In this state, EVENT_USB_READ_START is processed and a data transfer processing request is sent to the USB driver. When data read processing completes, the callback function cdc_read_complete is called. This callback function issues EVENT_USB_READ_COMPLETE. In EVENT_USB_READ_COMPLETE, EVENT_USB_WRITE_START is set to the event. In EVENT_USB_WRITE_START, a data write request is sent to the USB driver in order to transmit the data received in ① above to the CDC device. When the data write finishes, the callback function cdc_write_complete is called. This callback function issues the event EVENT_USB_WRITE_COMPLETE. In EVENT_USB_WRITE_COMPLETE the event EVENT_USB_READ_START is issued, and in the next loop ① is processed again and steps ① to ⑥ are repeated. If a switch on the RSK board is pressed while the data transfer described in ① to ⑥ is in progress, the event EVENT_SW_INPUT is issued, and the function cdc_sw_process is called. The function cdc_sw_process performs processing, according to which switches are pressed. Pressing switch 2 initiates processing to select the transfer speed, and pressing switch 3 initiates processing to notify the CDC device of the selected transfer speed. Note that the transfer speed notification to the CDC device is implemented by transmitting the class request SetControlLineState to the CDC device. For this reason, the state is set to STATE_CLASS_REQUEST and the event EVENT_CLASS_REQUEST_START is issued. Data transfer processing (cdc_data_transfer)
Callback function (cdc_write_complete)
Callback function (cdc_read_complete)
Get read data size EVENT acquisition processing (cdc_event_get)
Issue EVENT_USB_WRITE_COMPLETE Issue EVENT_USB_READ_COMPLETE
End
End
EVENT = EVENT_USB_READ _COMPLETE
= EVENT_USB_READ _START
Issue EVENT_USB_WRITE _START
Data read request (R_usb_hcdc_ receive_data)
= EVENT_USB_WRITE _START
Data write request (R_usb_hcdc_ send_data)
= EVENT_USB_WRITE _COMPLETE
Issue EVENT_USB_READ _START
= EVENT_SWITCH _INPUT
= EVENT _NONE
Communication speed switching processing
End
Figure 3-5 R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Flowchart of Data Transfer Processing Page 12 of 17
Renesas USB MCU
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
== Note == The definition below causes receive requests for notifications transmitted from the CDC device to be sent to the USB driver. Note that the callback function cdc_serial_state_trans_complete is called to notify the APL when the RSK board receives a notification. == r_usb_hcdc_mini_config.h == #define USB_HCDC_IF_CLASS USB_IFCLS_CDCC
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 13 of 17
Renesas USB MCU 4.
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Detach Processing (STATE_DETACH)
When the connected CDC device is detached, the USB driver calls the callback function usb_hsmpl_device_state. The function cdc_detach called from this callback function changes the state to STATE_DETACH. Note that this callback function usb_hsmpl_device_state is specified in the member statediagram of structure usb_hcdreg_t. In STATE_DETACH, processing is performed to clear the designated variable (cdc_dev_info) and change the state to STATE_DETACH, among other things. Detach processing (cdc_detach_device)
Processing to clear specified external variable, etc.
Change to STATE_ATTACH
End
Figure 3-6
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Flowchart of Detach Processing
Page 14 of 17
Renesas USB MCU 4. 4.1
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Class Driver Overview Class Request
Table 4-1 shows the class requests supported by HCDC. Table 4-1
Supported Basic Requests and CDC Class Requests
Request
Code
SendEncapsulatedCommand GetEncapsulatedResponse
0x00 0x01
SetCommFeature
0x02
GetCommFeature
0x03
ClearCommFeature
0x04
SetLineCoding
0x20
GetLineCoding SetControlLineState
0x21 0x22
SendBreak
0x23
4.2
Description
Sends protocol-defined commands such as AT. Requests response to command sent in SendEncapsulatedCommand. Sets enable/disable for device-specific 2-byte code and country code. Sets enable/disable for device-specific 2-byte code and country code. Returns enable/disable status for device-specific 2-byte code and country code to default settings. Sets transmission line coding (transmission speed, data length, parity bit, stop bit length) Obtains transmission line coding status. Sets control signals RTS and DTR for transmission line. Sends break signal.
Suppoted
YES YES YES YES YES YES YES YES YES
Class Notification（Notification from CDC device to USB Host）
Table 4-2 shows class notifications supported by the HCDC. Table 4-2 Notification
Code
NETWORK_CONNECTION RESPONSE_AVAILABLE
0x00 0x01
SERIAL_STATE
0x20
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
CDC Class Specific Notification Description
Notifies network connection state. Response to GET_ENCAPSLATED_RESPONSE. Notifies serial line status.
Supported
NO NO YES
Page 15 of 17
Renesas USB MCU 5.
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Using the e2 studio project with CS+
The HCDC contains a project only for e2 studio. When you use the HCDC with CS+, import the project to CS+ by following procedures.
Launch CS+ and click “Start”. Select [Open Exsisting e2studio/CS/High-performance Embedded Workshop/PM+ project] in Start menu.
Select the file with the extension [.rcpc] and click Open button.
Select [project file for e2studio]
Select the device used in the project. Select the used project e.g. Sample The project name depends on the AN.
Select Project type, and specify the project name and its location. Click OK button if they are OK.
Figure 5-1
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Using the e2 studio project with CS+
Page 16 of 17
Renesas USB MCU
USB Host Communications Device Class Driver for USB Mini Firmware Using Firmware Integration Technology Modules
Website and Support Renesas Electronics Website http://www.renesas.com/ Inquiries http://www.renesas.com/inquiry/
All trademarks and registered trademarks are the property of their respective owners.
R01AN2293EJ0102 Dec 28, 2015
Rev.1.02
Page 17 of 17
Revision Record Rev. 1.00 1.01 1.02
Date Dec 1, 2014 Jun 1, 2015 Dec 28, 2015
Description Page — — —
Summary First Edition Issued. RX231 is added in Target Device. Upgrading of this USB driver by upgrading of "USB Basic Mini Firmware (R01AN2166)".
A-1
General Precautions in the Handling of MPU/MCU Products The following usage notes are applicable to all MPU/MCU products from Renesas. For detailed usage notes on the products covered by this document, refer to the relevant sections of the document as well as any technical updates that have been issued for the products. 1. Handling of Unused Pins Handle unused pins in accordance with the directions given under Handling of Unused Pins in the manual. The input pins of CMOS products are generally in the high-impedance state. In operation with an unused pin in the open-circuit state, extra electromagnetic noise is induced in the vicinity of LSI, an associated shoot-through current flows internally, and malfunctions occur due to the false recognition of the pin state as an input signal become possible. Unused pins should be handled as described under Handling of Unused Pins in the manual. 2. Processing at Power-on The state of the product is undefined at the moment when power is supplied. The states of internal circuits in the LSI are indeterminate and the states of register settings and pins are undefined at the moment when power is supplied. In a finished product where the reset signal is applied to the external reset pin, the states of pins are not guaranteed from the moment when power is supplied until the reset process is completed. In a similar way, the states of pins in a product that is reset by an on-chip power-on reset function are not guaranteed from the moment when power is supplied until the power reaches the level at which resetting has been specified. 3. Prohibition of Access to Reserved Addresses Access to reserved addresses is prohibited. The reserved addresses are provided for the possible future expansion of functions. Do not access these addresses; the correct operation of LSI is not guaranteed if they are accessed. 4. Clock Signals After applying a reset, only release the reset line after the operating clock signal has become stable. When switching the clock signal during program execution, wait until the target clock signal has stabilized. When the clock signal is generated with an external resonator (or from an external oscillator) during a reset, ensure that the reset line is only released after full stabilization of the clock signal. Moreover, when switching to a clock signal produced with an external resonator (or by an external oscillator) while program execution is in progress, wait until the target clock signal is stable. 5. Differences between Products Before changing from one product to another, i.e. to a product with a different part number, confirm that the change will not lead to problems. The characteristics of an MPU or MCU in the same group but having a different part number may differ in terms of the internal memory capacity, layout pattern, and other factors, which can affect the ranges of electrical characteristics, such as characteristic values, operating margins, immunity to noise, and amount of radiated noise. When changing to a product with a different part number, implement a system-evaluation test for the given product.
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 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.
2.
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
3.
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
assumes no liability whatsoever for any damages incurred by you resulting from errors in or omissions from the information included herein.
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. 4.
You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. Renesas Electronics assumes no responsibility for any losses incurred by you or
5.
Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The recommended applications for each Renesas Electronics product depends on
third parties arising from such alteration, modification, copy or otherwise misappropriation of Renesas Electronics product.
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; and industrial robots etc. "High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems; anti-crime systems; and safety equipment etc. Renesas Electronics products are neither intended nor 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 damages (nuclear reactor control systems, military equipment etc.). 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 for which it is not intended. 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 which the product is not intended by Renesas Electronics. 6.
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.
7.
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 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. 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.
9.
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. You should not use Renesas Electronics products or 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. When exporting the Renesas Electronics 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.
10. It is the responsibility of the buyer or distributor of Renesas Electronics products, who distributes, disposes of, or otherwise places the product with a third party, to notify such third party in advance of the contents and conditions set forth in this document, Renesas Electronics assumes no responsibility for any losses incurred by you or third parties as a result of unauthorized use of Renesas Electronics products.
11. This document may not be reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas Electronics. 12. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas Electronics products, or if you have any other inquiries. (Note 1)
"Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its majority-owned subsidiaries.
(Note 2)
"Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics.
http://www.renesas.com
SALES OFFICES Refer to "http://www.renesas.com/" for the latest and detailed information.
Renesas Electronics America Inc. 2801 Scott Boulevard Santa Clara, CA 95050-2549, U.S.A. Tel: +1-408-588-6000, Fax: +1-408-588-6130 Renesas Electronics Canada Limited 9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3 Tel: +1-905-237-2004 Renesas Electronics Europe Limited Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K Tel: +44-1628-585-100, Fax: +44-1628-585-900 Renesas Electronics Europe GmbH Arcadiastrasse 10, 40472 Düsseldorf, Germany Tel: +49-211-6503-0, Fax: +49-211-6503-1327 Renesas Electronics (China) Co., Ltd. Room 1709, Quantum Plaza, No.27 ZhiChunLu Haidian District, Beijing 100191, P.R.China Tel: +86-10-8235-1155, Fax: +86-10-8235-7679 Renesas Electronics (Shanghai) Co., Ltd. Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, P. R. China 200333 Tel: +86-21-2226-0888, Fax: +86-21-2226-0999 Renesas Electronics Hong Kong Limited Unit 1601-1611, 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong Tel: +852-2265-6688, Fax: +852 2886-9022 Renesas Electronics Taiwan Co., Ltd. 13F, No. 363, Fu Shing North Road, Taipei 10543, Taiwan Tel: +886-2-8175-9600, Fax: +886 2-8175-9670 Renesas Electronics Singapore Pte. Ltd. 80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore 339949 Tel: +65-6213-0200, Fax: +65-6213-0300 Renesas Electronics Malaysia Sdn.Bhd. Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, 46050 Petaling Jaya, Selangor Darul Ehsan, Malaysia Tel: +60-3-7955-9390, Fax: +60-3-7955-9510 Renesas Electronics India Pvt. Ltd. No.777C, 100 Feet Road, HALII Stage, Indiranagar, Bangalore, India Tel: +91-80-67208700, Fax: +91-80-67208777 Renesas Electronics Korea Co., Ltd. 12F., 234 Teheran-ro, Gangnam-Gu, Seoul, 135-080, Korea Tel: +82-2-558-3737, Fax: +82-2-558-5141
© 2015 Renesas Electronics Corporation. All rights reserved. Colophon 5.0
