RENESAS M16C-65C Integrated Circuits User Guide

RENESAS M16C-65C Integrated Circuits User Guide

RX Family and M16C Family
Guide for Migration from the M16C to the RX: Clocks

Abstract
This document describes migration from the clocks in the M16C Family to the clocks in the RX Family.

Products
RX Family
M16C Family
When this document explains migration from the M16C Family to the RX Family, the M16C/65C Group MCU is used as an example of the M16C Family MCU, and the RX231 Group and RX660 Group MCUs are used as examples of the RX Family MCU. When using this application note with other Renesas MCUs, careful evaluation is recommended after making modifications to comply with the alternate MCU.

There are differences in the terminology between the M16C Family and RX Family.
The table below shows the differences in terminology related to clocks.

Differences in Terminology Between the RX Family and the M16C Family

module clock stop mode Software standby modeDeep software standby mode
Registers for peripheralfunctions| Special function registers (SFRs)| I/O registers

General Differences in the Clock Generation Circuit

This chapter describes the general differences in the clock generation circuit between the RX Family MCU
and the M16C Family MCU.
There are differences in the frequencies of the clocks used in the RX Family and M16C Family. Table 1.1 shows General Differences in the Frequencies of Various Clocks.
In the RX Family, settings to divide the following clocks can be done individually.

• System clock
• Peripheral module clock
• Flash interface clock
• External bus clock

In addition, the system clock, peripheral module clock, flash interface clock, and external bus clock are the same clock.

Figure 1.1 shows an Illustration of Selecting Various Clocks.

Table 1.1 General Differences in the Frequencies of Various Clocks

Item| M16C (in the case of the M16C/65C)| RX (in the case of the RX231)| RX (in the case of the RX660)
---|---|---|---
Maximum operating frequencies| System clock| 32 MHz| 54 MHz| 120 MHz
Peripheral module clock| 32 MHz| 32 MHz| 60 MHz
External bus clock| 32 MHz 1| 32 MHz| 60 MHz
Frequency| Main clock| 2 MHz to 20 MHz| 1 MHz to 20 MHz (VCC ≥ 2.4 V)1 MHz to 8 MHz(VCC < 2.4 V)| 8 MHz to 24 MHz
Sub-clock| 32.768 kHz to 50 kHz| 32.768 kHz| 32.768 kHz
PLL clock| 10 MHz to 32 MHz| 24 MHz to 54 MHz| 120 MHz to 240 MHz
High-speed on-chip oscillator (HOCO)| 40 MHz| 32 MHz/54 MHz| 16 MHz/18 MHz/20MHz
Low-speed on-chip oscillator (LOCO)| 125 kHz| 125 kHz| 240 kHz
IWDT-dedicated on- chip oscillator| —| 15 kHz| 120 kHz
WDT cycle period| Approx. 16.384 ms to33.6 sec 2| Approx. 75.85 μs to 4,096 sec 3| Approx. 34.13 μs to 4,096 sec 4
Clock after a reset is released| LOCO| LOCO| LOCO
Oscillation status after a reset| Main clock| Operating| Stopped| Stopped
Sub-clock| Stopped| Operating 5| Operating 5
High-speed on-chip oscillator (HOCO)| Stopped| Operating/Stopped 6| Operating/Stopped 6
Low-speed on-chip oscillator (LOCO)| Operating| Operating| Operating
Clock for flash memory| CPU clock| FlashIF clock| FlashIF clock

1. Notes: 1. Note that if the frequency goes higher than 25 MHz, the data output hold time becomes 0 ns or less. (when VCC = 5 V)
2. The WDT cycle period is shortest when the operating clock of the CPU is 32 MHz of the PLL clock, and longest when the LOCO clock is 125 kHz.
3. The WDT cycle period is shortest when the operating clock of the CPU is 54 MHz of the PLL clock, and longest when the sub-clock is 32.768 kHz.
4. The WDT cycle period is shortest when the operating clock of the CPU is 120 MHz of the PLL clock, and longest when the sub-clock is 32.768 kHz.
5. The sub-clock must be stopped when not in use.
6. The state of the HOCO clock after a reset can be set using the HOCO oscillation enable bit in option function select register 1 (OFS1.HOCOEN bit).

**RX Family

**

• In the RX Family, settings to divide the following clocks can be done individually.
• System clock
• Peripheral module clock
• Flash interface clock
• External bus clock

**M16C Family

**

In the M16C Family, the system clock, flash interface clock, and external bus clock are a common clock. The peripheral function clock can different from the system clock.

Functional Differences in Clocks

This chapter describes functional differences in clocks between the RX Family MCU and the M16C Family MCU.
In the RX Family has wait control registers for adjusting the time from when clock oscillation starts to when the clock is supplied to the CPU. This will allow a stable clock to be supplied to the CPU, prevent the MCU from operating erroneously. After entering a low power consumption mode, the wait control registers function after exiting the mode.
The concept between the wait control registers and oscillation stabilization wait time is described in section

Concept of the Main Clock Oscillation Stabilization Wait Time.

This section describes the concept of the main clock oscillation stabilization wait time in the RX Family.
A “stabilization time value that is greater than the resonator-vendor- recommended value” is set to the wait control register for the main clock (MOSCWTCR register).
The user must use software to wait for the main clock oscillation stabilization wait time. Create a software loop or the like and wait for an adequate amount of time. When using an MCU with oscillation stabilization flag registers, read the corresponding oscillation stabilization flags to determine if oscillation has stabilized.
The recommended main clock oscillation stabilization wait time is “at least twice the clock cycles set in the MOSCWTCR register”

**Figure 2.1 shows the Concept of the Main Clock Oscillation Stabilization Wait Time.

**

Note The oscillation stabilization time for the crystal resonator will differ depending on conditions like the wiring pattern and oscillation constants in the user system. The user should evaluate their system with oscillation stabilization times obtained from the resonator manufacturer.

Differences in Low Power Consumption Modes

The RX Family has several low power consumption modes to reduce power consumption. There are five modes available on RX Family MCUs as follows: Sleep mode and software standby mode on the RX231 and RX660 MCUs; deep sleep mode on the RX231 MCU; all-module clock stop mode and deep software standby mode on the RX660 MCU. This chapter describes the differences between the five modes available on the RX Family MCUs and the two modes (wait mode and stop mode) available on the M16C Family MCUs.
Table 3.1 shows Differences in Low Power Consumption Modes Between the RX and the M16C

Sleep Mode
The RX Family sleep mode is similar to the M16C Family wait mode in that the CPU is stopped. The RX  Family has a function for automatically switching the clock source when exiting sleep mode.
Deep Sleep Mode
In this mode, as well as the CPU is stopped as in sleep mode, the clocks for the DMAC, DTC, ROM, and RAM are stopped. Peripheral functions are not stopped.
Software Standby Mode
The RX Family software standby mode is similar to the M16C Family stop mode in that the CPU, all peripheral functions, and oscillators are stopped.
All-Module Clock Stop Mode
In this mode, the CPU and all peripheral functions are stopped. Use the module stop function to stop all peripheral functions before entering this mode. In normal operation mode, peripheral functions can be stopped independently. Refer to section 9.1.3 Module Stop Function for details.
Deep Software Standby Mode
In this mode, power supplies to the CPU, peripheral functions, and oscillators are stopped. Because power supplies are stopped, power consumption can be greatly reduced. In addition, the realtime clock (RTC) can be operated in this mode. The MCU must be reset to exit this mode.

Table 3.1 Differences in Low Power Consumption Modes Between the RX and the M16C

Item| M16C (in the case of the M16C/65C)| RX (in the case of the RX231/RX660)
---|---|---
Power consumption| More| Less| More| | | | Less
Mode| Wait mode| Stop mode| Sleep mode| Deep sleep mode| All-module clock stop mode| Software standby mode| Deep software standby mode
CPU| Stopped| Stopped| Stopped| Stopped| Stopped| Stopped| Stopped 1
Main clockOther clocks| Operating| Stopped| Operating| Operating| Operating| Stopped| Stopped
Sub-clock| Operating| Stopped| Operating| Operating| Operating| Operating| Operating
RAM| Operating| Operating| Operating| Stopped| Stopped| Stopped| Stopped 1
Flash memory| Operating| Stopped| Operating| Stopped| Stopped| Stopped| Stopped
Watchdog timer (WDT)| Operating| Stopped| Stopped| Stopped| Stopped| Stopped| Stopped 1
Independent watchdog timer(IWDT)| N/A| N/A| Operating| Operating| Operating| Operating| Stopped 1
RTC| Operating| Stopped| Operating| Operating| Operating| Operating| Operating
8-bit timer| N/A| N/A| Operating| Operating| Operating| Stopped| Stopped 1
Other peripheralfunctions| Operating| Stopped| Operating| Operating| Stopped| Stopped| Stopped 1
Outline| This mode stops the CPU.| This mode stops the CPU, all peripheral functions, and oscillators.| This mode stops the CPU.| This mode stops the CPU, DMAC, DTC,ROM, and RAM.| This mode stops the CPU and all peripheral functions. (Some peripheral functions areexcepted.)| This mode stops the CPU, all peripheral functions, and oscillators. (Only the sub- clock, IWDT, and RTC canoperate.)| This mode stops supplying power to all modules.(Only the sub- clock and RTC can operate.)

Note: In order to stop supplying power, register values for the CPU and internal peripheral functions
(excluding the RTC alarm, RTC period, SCL-DS, and SDA-DS) become undefined, and data in the   RAM becomes undefined.

Information Regarding the Function for Lower Operating Power Consumption

The RX231 MCU is equipped with the function for lower operating power consumption. This function reduces power consumption while the MCU is operating.
The function for lower operating power consumption has a high-speed operating mode, middle-speed operating modes, and low-speed operating modes. The slower the mode, the more power consumption can be reduced. As the power supply voltage, clocks, and frequencies differ for each mode, select an appropriate mode based on the conditions of use. When slowing down and speeding up clocks, the procedure for  changing the operating power control mode differs.

Slowing the clock to reduce CPU power consumption

1.  Set the clock source and switch the division ratio.
2. Change the operating power control mode.

Speeding up the clock to quicken CPU operation

1.  Change the operating power control mode.
2. Set the clock source and switch the division ratio.

The names of the above shown modes available on the RX Family MCU resemble high-speed mode, medium-speed mode, and low-speed mode available on the M16C Family MCU. However, the modes available on the M16C Family MCU simply specify the differences in the operating clock of the CPU.

Information Regarding the Clock Frequency Accuracy Measurement Circuit

The RX Family is equipped with functions for monitoring the clock frequencies and detecting abnormal frequencies. The RX231 and RX660 MCUs are equipped with a clock frequency accuracy measurement circuit (CAC).
The CAC monitors the clock frequency based on a reference signal input to the MCU externally or another clock source, and generates interrupts when measurement ends or the frequency is outside the set range.
For example, when monitoring the sub-clock frequency by the on-chip oscillator, if an abnormal frequency is detected and the sub-clock stops, an interrupt can be generated.

Information Regarding the Oscillation Stop Detection Function

This chapter describes the differences in the clock oscillation stop function.
There are differences in some functions (such as the clocks after oscillation stop is detected) between the RX and the M16C.
Table 6.1 shows Differences in the Oscillation Stop Detection Function

Clocks When Oscillation is Stopped| Clocks After an Oscillation Stop is Detected
---|---
M16C (in the case of the M16C/65C)| RX (in the case of the RX231/RX660)
Main clock| LOCO| LOCO
Sub-clock| No change(remains as sub-clock)
LOCO clock| No change(remains as LOCO)
HOCO clock| No change(remains as HOCO)
PLL clock| No change(remains as PLL clock 1)| No change(remains as PLL clock 1)

Note: However, the frequency becomes the self-oscillation frequency.

Information on Accessing I/O Registers

This chapter describes accessing the I/O registers in the RX Family.
On an RX Family MCU, while data is being written to I/O registers, the CPU can execute the subsequent instructions without waiting for the write operation to finish. In addition, when accessing I/O registers, the operating clock for peripheral functions is used. Therefore, in cases such as when the peripheral function clock for the I/O registers to be accessed is slower than the CPU clock, before the settings programmed on I/O registers are applied, the subsequent instructions may be executed.
There may be situations where the changes to I/O registers must be applied before executing subsequent instructions. These situations include when interrupt requests should be disabled by clearing the interrupt request enable bit (ICU.IERn.IENj bit) before executing subsequent instructions, and when the preprocessing to enter the power-down state occurs before executing a WAIT instruction. In such a situation, make sure that the CPU waits for the write operation to finish and then executes the subsequent instructions.

Table 7.1 shows Instructions That Wait for the I/O Register Write Value to be Reflected

[R1].UB, R1
2| Values written to I/O registers are read togeneral-purpose registers
3| Use the values read to perform calculations
4| Execute subsequent instructions

Chapters Associated With the RX User’s Manual: Hardware (UMH)

When migrating from the M16C Family to the RX Family, refer to the following chapters in the UMH.

• I/O registers
• Clock generation circuit
• Low power consumption
• Register write protection function
• RTC

Appendix

Points on Migration From the M16C Family to the RX Family
This section explains points on migration from the M16C Family to the RX Family

Interrupts
For the RX Family, when an interrupt request is received while all of the following conditions are met, the interrupt occurs.

• The I flag (PSW.I bit) is 1.
• Registers IER and IPR in the ICU are set to enable interrupts.
• The interrupt request is enabled by the interrupt request enable bits for the peripheral function

Table 9.1 shows Comparison of Conditions for Interrupt Generation Between the RX and the M16C.
Table 9.1 Comparison of Conditions for Interrupt Generation Between the RX and the M1

can be accepted.
Interrupt request flag| When there is an interrupt request from a peripheral function, the interrupt request flag becomes 1 (interrupt requested).
Interrupt priority level| Selected by setting bits ILVL2 to ILVL0.| Selected by setting the IPR[3:0] bits.
Interrupt request enable| ―| Specified by setting the IER register.
Interrupt enable forperipheral functions| ―| Interrupt enable or disable can bespecified in each peripheral function.

For more information, refer to sections Interrupt Controller (ICU), CPU, and sections for other peripheral
functions used in the UMH.

I/O Ports

In the RX Family, the MPC must be configured in order to assign I/O signals of peripheral functions to pins.
Before controlling the input and output pins in the RX Family, the following two items must be set.

• In the MPC.PFS register, select the peripheral functions that are assigned to the appropriate pins.
• In the PMR register for I/O ports, select the function for the pin to be used as a general I/O port or I/O port for a peripheral function.

Table 9.2 shows Comparison of I/O Settings for Peripheral Function Pins Between the RX and the M16C.
Table 9.2 Comparison of I/O Settings for Peripheral Function Pins Between the RX and the M16C

Function| M16C (in the case of the M16C/65C)| RX (in the case of the RX660/RX231)
---|---|---
Select the pin function| These are not available in the M16C. *1 When a mode is set for a peripheral function, appropriate pins are assigned as I/O pins for the peripheral function.| With the PFS register, I/O ports for peripheral functions can be assigned by selecting from multiple pins.
Switch between general I/O port and peripheral function| With the PMR register, the corresponding pin function can be selected as a general I/O port or a peripheral function.

Note: 1. Register for similar functions are available in the M32C Series and R32C Series.

For more information, refer to the Multi-Function Pin Controller (MPC) and I/O port sections in the UMH.

Module Stop Function
The RX Family has the ability to stop peripheral modules individually.
By transitioning unused peripheral modules to the module stop state, power consumption can be reduced.
After a reset is released, all modules (with a few exceptions) are in the module stop state. Registers for modules in the module stop state cannot be written to or read.
For more information, refer to the Low Power Consumption section in the UMH.

I/O Register Macros
Macro definitions listed in Table 9.3 can be found in the RX I/O register definitions (iodefine.h).
The readability of programs can be achieved with these macro definitions.
Table 9.3 shows Macro Usage Examples.

corresponding to MTU0.TGIA0 is cleared to 0 (no interrupt request is generated).
DTCE(“module name”, “bit name”)| DTCE (MTU0, TGIA0) = 1 ;The DTCE bit corresponding to MTU0.TGIA0 is set to 1 (DTC activation is enabled).
IEN(“module name”, “bit name”)| IEN(MTU0, TGIA0) = 1 ;The IEN bit corresponding to MTU0.TGIA0 is set to 1 (interrupt enabled).
IPR(“module name”, “bit name”)| IPR(MTU0, TGIA0) = 0x02 ;The IPR bit corresponding to MTU0.TGIA0 is set to 2 (interrupt priority level 2).
MSTP(“module name”)| MSTP(MTU) = 0 ;The MTU0 Module Stop bit is set to 0 (module stop state is canceled).
VECT(“module name”, “bit name”)| #pragma interrupt (Excep_MTU0_TGIA0 (vect = VECT(MTU0, TGIA0) )The interrupt function is declared for the corresponding MTU0.TGIA0 register.

Intrinsic Functions

The RX Family has intrinsic functions for setting control registers and special instructions. When using intrinsic functions, include machine.h.
Table 9.4 shows Examples of Differences in the Settings of Control Registers and Descriptions of Special Instructions Between the RX and the M16C.

Table 9.4 Examples of Differences in the Settings of Control Registers and Descriptions of Special Instructions Between the RX and the M16C

Note: 1. The machine.h file must be included.

Reference Documents

User’s Manual: Hardware
RX230/RX231 Group User’s Manual: Hardware (R01UH0496EJ)
RX660 Group User’s Manual: Hardware (R01UH0037EJ)
M16C/65C Group User’s Manual: Hardware (R01UH0093EJ)
If you are using a product that does not belong to the RX231, RX660, or M16C/65C Group, refer to the applicable user’s manual for hardware.
The latest versions can be downloaded from the Renesas Electronics website.
Technical Update/Technical News
The latest information can be downloaded from the Renesas Electronics website.
User’s Manual: Development Tools
RX Family CC-RX Compiler User’s Manual (R20UT3248) M16C Series, R8C Family C Compiler Package (M3T-NC30WA)
The latest versions can be downloaded from the Renesas Electronics website.

REVISION HISTORY

was changed:From RX210 to RX231/RX660

General Precautions in the Handling of Micro processing Unit and

Microcontroller  Unit Products

The following usage notes are applicable to all Microprocessing unit and Microcontroller unit 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. Precaution against Electrostatic Discharge (ESD)
   A strong electrical field, when exposed to a CMOS device, can cause destruction of the gate oxide and ultimately degrade the device operation. Steps must be taken to stop the generation of static electricity as much as possible, and quickly dissipate it when it occurs. Environmental control must be adequate. When it is dry, a humidifier should be used. This is recommended to avoid using insulators that can easily build up static electricity. Semiconductor devices must be stored and transported in an anti-static container, static shielding bag or conductive material. All test and measurement tools including work benches and floors must be grounded. The operator must also be grounded using a wrist strap. Semiconductor devices must not be touched with bare hands. Similar precautions must be taken for printed circuit boards with mounted semiconductor devices.

2. Processing at power-on
   The state of the product is undefined at the time 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 time 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 time 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 time when power is supplied until the power reaches the level at which resetting is specified.

3. Input of signal during power-off state
   Do not input signals or an I/O pull-up power supply while the device is powered off. The current injection that results from input of such a signal or I/O pull-up power supply may cause malfunction and the abnormal current that passes in the device at this time may cause degradation of internal elements. Follow the guideline for input signal during power-off state as described in your product documentation.

4. 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 the 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.

5. Clock signals
   After applying a reset, only release the reset line after the operating clock signal becomes stable. When switching the clock signal during program execution, wait until the target clock signal is 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. Additionally, 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.

6. Voltage application waveform at input pin
   Waveform distortion due to input noise or a reflected wave may cause malfunction. If the input of the CMOS device stays in the area between VIL (Max.) and VIH (Min.) due to noise, for example, the device may malfunction. Take care to prevent chattering noise from entering the device when the input level is fixed, and also in the transition period when the input level passes through the area between VIL (Max.) and VIH (Min.).

7. Prohibition of access to reserved addresses
   Access to reserved addresses is prohibited. The reserved addresses are provided for possible future expansion of functions. Do not access these addresses as the correct operation of the LSI is not guaranteed.

8. Differences between products
   Before changing from one product to another, for example to a product with a different part number, confirm that the change will not lead to problems. The characteristics of a microprocessing unit or microcontroller unit products in the same group but having a different part number might differ in terms of 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 systemevaluation 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 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 be responsible for determining what licenses are required from any third parties, and obtaining such licenses for the lawful import, export, manufacture, sales, utilization, distribution or other disposal of any products incorporating Renesas Electronics products, if required.
5. 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.
6. 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.
7. No semiconductor product is absolutely secure. Notwithstanding any security measures or features that may be implemented in Renesas Electronics hardware or software products, Renesas Electronics shall have absolutely no liability arising out of any vulnerability or security breach, including but not limited to any unauthorized access to or use of a Renesas Electronics product or a system that uses a Renesas Electronics product. RENESAS ELECTRONICS DOES NOT WARRANT OR GUARANTEE THAT RENESAS ELECTRONICS PRODUCTS, OR ANY SYSTEMS CREATED USING RENESAS ELECTRONICS PRODUCTS WILL BE INVULNERABLE OR FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE, HACKING, DATA LOSS OR THEFT, OR OTHER SECURITY INTRUSION (“Vulnerability Issues”). RENESAS ELECTRONICS DISCLAIMS ANY AND ALL RESPONSIBILITY OR LIABILITY ARISING FROM OR RELATED TO ANY VULNERABILITY ISSUES. FURTHERMORE, TO THE EXTENT PERMITTED BY APPLICABLE LAW, RENESAS ELECTRONICS DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, WITH RESPECT TO THIS DOCUMENT AND ANY RELATED OR ACCOMPANYING SOFTWARE OR HARDWARE, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
8. 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
9. 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.
10. 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.
11. 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.
12. 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.
13. This document shall not be reprinted, reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas Electronics.
14. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas Electronics products.
    (Note1) “Renesas Electronics” as used in this document means Renesas Electronics Corporation and also includes its directly or indirectly controlled subsidiaries.
    (Note2) “Renesas Electronics product(s)” means any product developed or manufactured by or for Renesas Electronics.

Corporate Headquarters TOYOSU FORESIA, 3-2-24 Toyosu Koto-ku, Tokyo 135-0061, Japan
www.renesas.com
Trademarks
Renesas and the Renesas logo are trademarks of Renesas Electronics Corporation. All trademarks and registered trademarks are the property of their respective owners.

Contact information
For further information on a product, technology, the most up-to-date version of a document, or your nearest sales office, please visit: www.renesas.com/contact/

Trademarks
Renesas and the Renesas logo are trademarks of Renesas Electronics Corporation. All trademarks and registered trademarks are the property of their respective owners.

References

• Renesas Electronics Corporation
• Distributor Network | Renesas Semiconductors | Renesas

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>