Old Company Name in Catalogs and Other Documents

Transcription

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.
APPLICATION NOTE
R8C/27
Consumer IR (CIR) & Consumer Electronics Control (CEC) function sample code
Introduction
This sample code demonstrates CIR and CEC functions in R8C/27 RSK. In the R8C/27, it adopts timer RC to handle
CIR and CEC functions. For timer RC, CIR and CEC data are received in input capture mode. As CEC data
transmission, the timer RC is in output compare mode. In the document, section 1 describes the hardware and software
environment. For section 2, it describes the CIR introduction and program flow chart. Lastly, description of CEC
function is shown in the section 3.
Target Devices
R8C/26, 27
Contents
1.
Introduction ....................................................................................................................................... 2
2.
CIR Receiver Function...................................................................................................................... 3
2.1 CIR function Program flow ................................................................................................................ 6
2.2 CIR data monitor............................................................................................................................... 7
3.
CEC introduction............................................................................................................................... 8
3.1 CEC API Function........................................................................................................................... 10
3.2 Receive from UART ........................................................................................................................ 12
3.3 Transfer CEC Data by UART.......................................................................................................... 16
Website and Support............................................................................................................................... 20
RET05B0006-0100/Rev.1.00
March 2010
Page 1 of 21
R8C/27
1.
Introduction
The application is applied to the following configuration:
R8C/27
The R8C/27, part name R5F21276, is a group of the R8C Series based on the R8C CPU core used in the application
system with a maximum operating frequency at 40MHz.
ROM: (32k + 1k*2) bytes
RAM: 1.5k bytes
ROM Type: Flash Memory
Timer RC: Timer RC is a 16-bit timer with four I/O pins: TRCIOA, TRCIOB, TRCIOC, and TRCIOD.
R8C/27 RSK Platform
R8C/27 RSK is used as a main processor which incorporates R8C operating at a maximum frequency of 40MHz.
The basic functions of the R8C/27 RSK, Part Name R0K330879000BE, are as following.
z
Input Clock Main: 20MHz
z
Sub: 32.768 kHz
z
Switch Reset x 1 User/Boot x 1 User x 2
z
Potentiometer Single-turn, 10kΩ
z
Power indicator LED: green x 1
z
Boot indicator LED: orange x 1
z
User LED: green x 1, orange x 1, red x 2
z
Input E8 Header 14-pin box header
z
RS232 Serial Connector 9-pin DSUB
z
LCD Display Connector 14-pin socket
z
Reset circuit
C Compiler
High Performance Embedded Workshop V4.05 by Renesas Technology Corp.
M16C standard tool chain V.5.41.01 by Renesas Technology Corp.
RET05B0006-0100/Rev.1.00
March 2010
Page 2 of 21
R8C/27
2.
CIR Receiver Function
In the section, it describes the CIR introduction in RSK and shows which protocol is adopted, what is the IR receiver
API function and how to use the function. Besides, the sample code provides a monitor to present the CIR function
status.
In the sample code, CIR protocol adopts NEC protocol. Below shows some information about NEC protocol.
z
8 bit address and 8 bit command length
z
Address and command are transmitted twice for reliability
z
Pulse distance modulation
z
Carrier frequency of 38kHz
z
Bit time of 1.12ms or 2.25ms
The following picture presents the logical 0 and how to send a command. The NEC protocol uses pulse distance
encoding of the bits. Each pulse is a 560µs long 38kHz carrier burst (about 21 cycles). A logical "1" takes 2.25ms to
transmit, while a logical "0" is only half of that, being 1.125ms. The recommended carrier duty-cycle is 1/4 or 1/3.
The picture above shows a typical pulse train of the NEC protocol. With this protocol the LSB is transmitted first. In
this case Address $59 and Command $16 is transmitted. A message is started by a 9ms AGC burst, which was used to
set the gain of the earlier IR receivers. This AGC burst is then followed by a 4.5ms space, which is then followed by the
Address and Command. Address and Command are transmitted twice. The second time all bits are inverted and can be
used for verification of the received message. The total transmission time is constant because every bit is repeated with
its inverted length. If you're not interested in this reliability you can ignore the inverted values, or you can expand the
Address and Command to 16 bits each! In here, please notice that a command is transmitted only once, even when the
key on the remote control pressed. Every 110 ms a repeat code is transmitted for as long as the key remained. This
repeat code is simply a 9ms AGC pulse followed by a 2.25ms space and burst. The repeat command is as shown in
below.
RET05B0006-0100/Rev.1.00
March 2010
Page 3 of 21
R8C/27
A command is transmitted only once, even when the key on the remote control remains pressed. Every 110ms a repeat
code is transmitted for as long as the key remains down. This repeat code is simply a 9ms AGC pulse followed by a
2.25ms space and a 560µs burst.
Hardware circuit:
For the R8C/27 RSK, please sets P5_3 be a CIR input pin. Below show the block diagram.
RET05B0006-0100/Rev.1.00
March 2010
Page 4 of 21
R8C/27
R8C27
CIR Receiver
P5_3
Software API:
Below are the functions calls contained in the ir.h and ir.c C source code files.
Function Type
Function name
Initialization functions
void ir_rece3_sfr(void)
void IR_Struct_Reset(void);
void IR_Timer_RC_initital(void);
Receive functions
void IR_Receiver(void)
Process receive data
void IR_Verify_data(void)
void IR_Verify_Leader(void)
void Check_Level(unsigned short count_ir)
Interrupt handle
void timer_rc_int_func3(void)
RET05B0006-0100/Rev.1.00
note
March 2010
Page 5 of 21
R8C/27
2.1
CIR function Program flow
1
Initial IR function: the initial method is IR_Timer_RC_initital() function. The method includes two functions.
1.1
ir_rece3_sfr (); the ir_rece3_sfr () function is used to initial MCU register,
1.2
IR_Struct_Reset(); the IR_Struct_Reset() function is used to reset some structure about IR function.
2
And then IR_Receiver() is used to receive the IR command which receives from interrupt handle:
timer_rc_int_func3() function.
3
When the interrupt occurs, the MCU starts to receive remote controller data. That is, MCU gets the CIR data from
timer_rc_int_fun3() function. In the function, it will receive the CIR data and determine the data is from whether
CEC or CIR module.
4
After MCU gets IR data, the IR_Receiver() processes the data. In the function, it includes two functions
4.1
IR_Verify_data(); the IR data includes some dummy data, like repeat code.
4.2
IR_Verify_Leader(); the IR data needs to verify the format whether correct or not.
5
Finally, the CIR data will be saved in “IR_flag.irdata” parameter. The lead code and the address code saves in the
“IR_flag.customer_data” parameter
start
In the start, it execute
ir_rece3_sfr (),
IR_Struct_Reset(), and
IR_Timer_RC_initital()
IR_Receiver():
When interrupt occurs,
the interrupt routine will
call timer_rc_int_fun3()
When interrupt occurs:
z
Determine the data
whether high or low
z
Determine leader code
and data code
After receive, the
program flow enters to
IR_Receiver(). It will
parse the IR data
While(1)
RET05B0006-0100/Rev.1.00
March 2010
Page 6 of 21
R8C/27
2.2
CIR data monitor
In the sample code provides CIR data monitor, if you want to monitor the CIR data status, please follow below
environment setting into your terminal and R8C/27.
ENVIORNMENT
In R8C/27:
P3_7 pin is TXD
P4_5 pin is RXD
In Terminal:
Baud rate: 9600
Data: 8 bits
Parity: none
Stop: 1 bit
Flow control: none
Below picture shows the monitor:
In the red block, “IR_Receiver” means function name in the program.
In the blue block, “IR_flag.irdata:” means the parameter name which stores the CIR data in the program.
In the yellow block, the number means the CIR data which receives from CIR module.
RET05B0006-0100/Rev.1.00
March 2010
Page 7 of 21
R8C/27
3.
CEC introduction
Consumer Electronics Control (CEC) wiring is mandatory, although implementation of CEC in a product is optional.
CEC uses the industry-standard AV Link protocol, is used for remote control functions, is a one-wire bidirectional
serial bus, and was defined in HDMI Specification 1.0 and updated in HDMI 1.2, HDMI 1.2a, and HDMI 1.3a (added
timer and audio commands). The CEC feature is designed to allow the user to command and control multiple CECenabled boxes with one remote control and for individual CEC-enabled devices to command and control each other
without user intervention.
Alternative names for CEC are Anynet (Samsung); Aquos Link (Sharp); BRAVIA Theatre Sync (Sony); Kuro Link
(Pioneer); CE-Link and Regza Link (Toshiba); RIHD (Remote Interactive over HDMI) (Onkyo); Simplink (LG);
HDAVI Control, EZ-Sync, and VIERA Link (Panasonic); EasyLink (Philips); and NetCommand for HDMI
(Mitsubishi).
For the CEC frame protocol is as shown in below, it is easy to understand the protocol which includes start bit,
header block, and option data blocks. Besides, the sample code not only handles the protocol frame parsing, but also
provides test function by UART in the sample code.
RET05B0006-0100/Rev.1.00
March 2010
Page 8 of 21
R8C/27
Hardware circuit:
For the R8C/27RSK, please sets P5_4 as a CEC line. Below shows the block diagram.
R8C27
RET05B0006-0100/Rev.1.00
CEC device
P5_4
March 2010
Page 9 of 21
R8C/27
3.1
CEC API Function
In the sample code, CEC command can be transmitted by two methods:
1.
Receive predefine function from UART and then transmit CEC data by CEC line.
2.
CEC line.
For the first method, the sample code provides some predefine CEC function to use. User can use some predefine
function to send CEC command. The predefine function which is received from UART used to determine what CEC
command will be transmitted. In the second method, when some devices (like player, etc.) in the CEC line, the sample
code of R8C/27 can receive the CEC command from the device and then responses it. Below figure shows the block
diagram.
Terminal:
Receive some predefine
keys and select predefine
function by the key
R8C/27
UART channel
Predefine Key
CEC line
Other CEC
devices
CEC data
Method 1
CEC data
Method 2
Response CEC data
After receiving the command (may be from above 1. or 2. source), there are three operations to process the command
in the program.

MCU responses by CEC line.
MCU responses by UART.
MCU do some operations and do not response anything to CEC line or UART.
Therefore, in the section 3.1, it will show the sample code how to receive the command by UART and response method,
and then the section 3.2 describes the CEC line send data to MCU and MCU and how to response it. Finally, in the last
section, it shows how to transmit CEC command in CEC line by UART.
In the function “CEC_Fun_Init()”, it sets some initial status. Ex. Physical address, virtual address, initiator, follower,
power status and etc. Of course you can modify by yourself.
RET05B0006-0100/Rev.1.00
March 2010
Page 10 of 21
R8C/27
Below are the functions calls contained in the cec_ap.h, cec_ap.c, cec_drv.c, and cec_drv.h source code
files.
Function Type
Initialization functions
Receive functions
Transmit function
Test function
Interrupt handle
Function name
note
void CecInitialize(void)
void CEC_Fun_Init(void)
void CyclicCec (void)
unsigned char Chk_CEC_Rxdata(unsigned char
*cecdata,unsigned char num)
void Chk_CEC_Txdata(void)
void R8C_send_to_CEC_from_UART(void)
void CEC_Send_Command(void)
unsigned char CEC_UART_Test(unsigned char uart_cec_test)
void timer_rc_int_func3(void)
RET05B0006-0100/Rev.1.00
March 2010
The function in the Ir.c
Page 11 of 21
R8C/27
3.2
Receive from UART
Below shows the flow chart about the receive function.
Start
Receive data from UART
Determine the CEC
command by UART:
Void cec_uart_test(void)
CEC_Send_Command()
1.
When user sends some
key to MCU by terminal,
the MCU determines the
key and then sets some
parameter and let
“cec_p.ready=1”. The
flag is decided to send
the command by CEC
line and then send by the
cec_uart_test() function
2.
Implementing more
commands by modifying
the function
Enter
CEC_Send_Command() in
while(1) of main()
The function handles CEC
sending operation:
1.Command from CEC line
2.Command from UART
RET05B0006-0100/Rev.1.00
March 2010
Page 12 of 21
R8C/27
CEC_Send_Command()
If retry_flag=1:
command from
CEC line
Receive CEC command
from CEC line, and then
use SetCecData() function
to send the CEC data by
CEC line.
If CEC_p.ready=1:
command from
UART
Receive CEC command from
UART, and then use
SetCecData() function to
send the CEC data by CEC
line
In CEC_Send_Command()
PS. In the sample code, it always adapts Tx parameter to store the CEC data which will be
transmitted by CEC line
RET05B0006-0100/Rev.1.00
March 2010
Page 13 of 21
R8C/27
4.2
Receive from CEC Line
Below shows the flow chart about the receive function.
Start
Receive data from CEC line
timer_rc_int_func3()
R8C/27 adapts
P5_4/TRCIOD to be CEC
line, and Timer RC function
is input capture
int_TimerRC_CEC();
Here, it determines CEC
status whether input or
output. If it is in the input
mode, the sample code will
be into the CECinput()
function
int_TimerRC_CEC();
CyclicCec();
RET05B0006-0100/Rev.1.00
March 2010
In the function, it is used to
determine what is CEC data
from CEC line.
In the Timer RA interrupt
handle, it executes
CyclicCec() to handle the
CEC data
Page 14 of 21
R8C/27
1. If opcode is 0x44, 36, 45,8d,
it will be send to UART (send
to main processor)
Chk_CEC_Txdata();
If in the last time,
“RspSFTFlag” flag is set 1. It
enters the function, and
responde the CEC command
by CEC line. If the operation
is fail, it retries and sets
retry_flag=1. Finally, the
CEC_send_command sends
it to CEC line by the flag
Chk_CEC_Rxdata()
If the CEC line receives data,
the sample code enters into
the “Chk_CEC_Rxdata()”
function.
2. Else, the code may be response to CEC line, and set the
RspSFTFlag =1. And then in the next time, the MCU enters
to cyclicCEC function, the Chk_CEC_Txdata checks the
flag, and sends to CEC line. If the operation is fail, il retries
and sets retry_flag=1. Finally, the CEC_send_command send
s it to CEC line by the flag. Of course, if you want do other
operation and do not respond to CEC line or UART, you can
add what you want in the “switch(*(CECdata+1))” of
“Chk_CEC_Rxdata()”
In Chk_CEC_Rxdata()
RET05B0006-0100/Rev.1.00
March 2010
Page 15 of 21
R8C/27
3.3
Transfer CEC Data by UART
In the sample code, it provides CEC test function. The function predefines some key which receives from UART and
then sends the CEC command. Finally, you can see the result in the terminal. In order to enable the function, please set
some parameters into your terminal and R8C/27
ENVIORNMENT
In R8C/27:
P3_7 pin is TXD
R4_5 pin is RXD
In Terminal:
Baud rate: 9600
Data: 8 bits
Parity: none
Stop: 1 bit
Flow control: none
In the Workspace:
Please modify some information of device depends on your environment in Cec_ap.h file.
Default setting:
#define phyaddr 0x1234
#define device_typ 0x00
#define cec_v 0x04
#define langu01 0xff
#define power_status_cec 0x00
#define UART_CEC_Test 1
Below table presents the definition
Define item
Definition
#define phyaddr 0x1234
Define physical address
#define device_typ 0x00
Define device type (Default is TV)
#define cec_v 0x04
Define CEC version
Define item
RET05B0006-0100/Rev.1.00
Definition
March 2010
Page 16 of 21
R8C/27
Define language
Define language
Define language
#define power_status_cec 0x00
Define power status of the device
#define UART_CEC_Test 1
Define test function on/off
In the default setting, the R8C/27 could be TV, and the physical address is 0x1234. Besides, if you do not want to use
the function please set UART_CEC_Test 0.
Below picture shows the CEC test function
RET05B0006-0100/Rev.1.00
March 2010
Page 17 of 21
R8C/27
Figure 1.
In the red block of figure 1, “f:” means the predefine key (in your key board) which receives from UART.
In the blue block, “User Control Pressed: Power on:” means the CEC command which is transmitted to other device by
CEC line (User can see the command from CEC spec)
Figure 2.
In the yellow block of figure 2, “ ””” send beg ” means CEC transmit operation is beginning.
“header: 0004” means the header block is 0004 in the CEC command frame
“op code: 44” means the op code data is 44 in the CEC command frame
“OPL: 6D” means the parameter data is 6D in the CEC command frame
“num: 03” means the number of transmission byte is 3 in the CEC command frame
RET05B0006-0100/Rev.1.00
March 2010
Page 18 of 21
R8C/27
Figure 3.
In the red block of figure 3, “ RECEIVE++beg ” means R8C/27 receives CEC command from CEC line.
“header 40 ” means the header block is 40 in the CEC command frame
“op code: 00” means the op code data is 00 in the CEC command frame
“ RECEIVE++end” means the command finish..
“num: 02” means the number of transition byte is 3 in the CEC command frame
In the test function, it provides some commands.
Predefine Key (receives from UART)
CEC command
“z”
Abort
“x”
Stand By
“a”
Text View ON
“s”
Active Source
“d”
Give Device Power Status
“f”
User Control Pressed <power on>
“g”
User Control Pressed <power off>
“q”
User Control Pressed <play forward>
“w”
User Control Pressed <play min forward>
“e”
User Control Pressed <play min forward >
“r”
User Control Pressed <play reverse >
“c”
Deck Control<stop>
“v”
Deck Control<eject>
RET05B0006-0100/Rev.1.00
March 2010
Page 19 of 21
R8C/27
Website and Support
Renesas Technology Website
http://www.renesas.com/
Inquiries
http://www.renesas.com/inquiry
csc@renesas.com
Revision Record of R8C/27 CIR & CEC function ample code
Rev.
1.00
Date
Mar.31.10
Description
Page
Summary
First edition issued
All trademarks and registered trademarks are the property of their respective owners.
RET05B0006-0100/Rev.1.00
March 2010
Page 20 of 21
R8C/27
Notes regarding these materials
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
This document is provided for reference purposes only so that Renesas customers may select the appropriate
Renesas products for their use. Renesas neither makes warranties or representations with respect to the
accuracy or completeness of the information contained in this document nor grants any license to any intellectual
property rights or any other rights of Renesas or any third party with respect to the information in this document.
Renesas shall have no liability for damages or infringement of any intellectual property or other rights arising out
of the use of any information in this document, including, but not limited to, product data, diagrams, charts,
programs, algorithms, and application circuit examples.
You should not use the products or the technology described in this document for the purpose of military
applications such as the development of weapons of mass destruction or for the purpose of any other military
use. When exporting the products or technology described herein, you should follow the applicable export
control laws and regulations, and procedures required by such laws and regulations.
All information included in this document such as product data, diagrams, charts, programs, algorithms, and
application circuit examples, 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 products listed in this
document, please confirm the latest product information with a Renesas sales office. Also, please pay regular
and careful attention to additional and different information to be disclosed by Renesas such as that disclosed
through our website. (http://www.renesas.com)
Renesas has used reasonable care in compiling the information included in this document, but Renesas
assumes no liability whatsoever for any damages incurred as a result of errors or omissions in the information
included in this document.
When using or otherwise relying on the information in this document, you should evaluate the information in light
of the total system before deciding about the applicability of such information to the intended application.
Renesas makes no representations, warranties or guaranties regarding the suitability of its products for any
particular application and specifically disclaims any liability arising out of the application and use of the
information in this document or Renesas products.
With the exception of products specified by Renesas as suitable for automobile applications, Renesas products
are not designed, manufactured or tested for applications or otherwise in systems the failure or malfunction of
which may cause a direct threat to human life or create a risk of human injury or which require especially high
quality and reliability such as safety systems, or equipment or systems for transportation and traffic, healthcare,
combustion control, aerospace and aeronautics, nuclear power, or undersea communication transmission. If you
are considering the use of our products for such purposes, please contact a Renesas sales office beforehand.
Renesas shall have no liability for damages arising out of the uses set forth above.
Notwithstanding the preceding paragraph, you should not use Renesas products for the purposes listed below:
(1) artificial life support devices or systems
(2) surgical implantations
(3) healthcare intervention (e.g., excision, administration of medication, etc.)
(4) any other purposes that pose a direct threat to human life
Renesas shall have no liability for damages arising out of the uses set forth in the above and purchasers who
elect to use Renesas products in any of the foregoing applications shall indemnify and hold harmless Renesas
Technology Corp., its affiliated companies and their officers, directors, and employees against any and all
damages arising out of such applications.
You should use the products described herein within the range specified by Renesas, especially with respect to
the maximum rating, operating supply voltage range, movement power voltage range, heat radiation
characteristics, installation and other product characteristics. Renesas shall have no liability for malfunctions or
damages arising out of the use of Renesas products beyond such specified ranges.
Although Renesas endeavors to improve the quality and reliability of its products, IC products have specific
characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions.
Please be sure to implement safety measures to guard against the possibility of physical injury, and injury or
damage caused by fire in the event of the failure of a Renesas 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 applicable measures. Among others, since the evaluation of microcomputer
software alone is very difficult, please evaluate the safety of the final products or system manufactured by you.
In case Renesas products listed in this document are detached from the products to which the Renesas products
are attached or affixed, the risk of accident such as swallowing by infants and small children is very high. You
should implement safety measures so that Renesas products may not be easily detached from your products.
Renesas shall have no liability for damages arising out of such detachment.
This document may not be reproduced or duplicated, in any form, in whole or in part, without prior written
approval from Renesas.
Please contact a Renesas sales office if you have any questions regarding the information contained in this
document, Renesas semiconductor products, or if you have any other inquiries.
© 2010. Renesas Technology Corp., All rights reserved.
RET05B0006-0100/Rev.1.00
March 2010
Page 21 of 21