R01an0474eg rx62n

APPLICATION NOTE
R01AN0474EG0100 Rev.1.00 Page 1 of 18

J an 23, 2011
RX62N
RX62N USB Bootloader with XModem Transfer
Introduction
This Application Note introduces a User Mode Flash Programming Bootloader operating on the Renesas RX62N
microcontroller.
Target Device
RX62N
Contents
1. Application Note Overview................................................................................................................ 2
2. Application Note Hardware ............................................................................................................... 3
3. USB Bootloader HEW Workspace.................................................................................................... 4
4. Bootloader Overview......................................................................................................................... 5
5. Bootloader Menus............................................................................................................................. 6
6. Bootloader System Resource ........................................................................................................... 9
7. RX600 FLASH Programming.......................................................................................................... 11
8. Creating an Bootloader Compliant Application............................................................................... 12

R01AN0474EG0100
Rev 1.00
J an 23, 2011
RX62N RX62N USB Bootloader with XModem Transfer
R01AN0474EG0100 Rev.1.00 Page 2 of 18
J an 23, 2011
1. Application Note Overview
The RX62N microcontroller is a member of the RX600 series of high performance 32-bit CISC microcontrollers from
Renesas. The RX62N incorporates many peripheral functions that are essential for embedded devices, such as 16-bit &
8-bit Timers, Ethernet controller, USB 2.0 host/function modules, serial communications interfaces, I
2
C bus interfaces,
CAN modules, an A/D converter, and a D/A converter.
The RX62N also incorporates up to 512kBytes of High Speed (100MHz) single cycle execution FLASH memory,
32kBytes of Data FLASH and up to 96Kbytes of SRAM.
The FLASH memory on the RX62N may be programmed in many ways. These are:
Off-board programming
A PROM programmer can be used to program the FLASH memory.
On-board programming
Boot mode: On Boot, the FLASH memory is programmable via the SCI (UART) interface
USB boot mode: On Boot, the FLASH memory is programmable via USB Function interface
User program: Programming of FLASH memory occurs as part of the user application.
The On-board programming modes are selected by mode pins MD0 and MD1.
It is a common requirement in User Applications for the firmware to be upgraded. Typically, this would require access
to the mode pins to specify one of the Boot Modes. This may not be possible, or desirable.
An alternative method is to have a User Application running a Bootloader that in response to a set of commands
(whether this be via I/O, SCI Comms, USB Comms) allows FLASH memory programming using User Program mode.
This Application Note details how such a Bootloader can be implemented.
The Bootloader is menu driven, allowing the user to erase the FLASH memory, Program the FLASH memory and then
Execute the newly programmed code.
Communication between the RX62N and the host PC is via USB. The USB peripheral on the RX62N enumerates using
the CDC class. This allows communication to be achieved using a terminal emulator such a Hyperterminal.
Data for Menu Commands are transmitted with no specified protocol.
Data for FLASH programming is transmitted via the XModem protocol.
R01AN0474EG0100 Rev.1.00 Page 3 of 18
J an 23, 2011
2. Application Note Hardware
The Application Note was developed on the RX62N RSK development board, using the HEW IDE and E1 On-Chip
Emulator. Figure 1. shows a graphical representation of the development environment.
PC running HEW4 IDE.
Figure 1.
E1 Emulator.
Used for Application Note development.
Not required for normal Bootloader execution.
USB Cable.
PC - E1 Connection.
Bootloader USB Cable.
PC - RSK Connection.
R01AN0474EG0100 Rev.1.00 Page 4 of 18
J an 23, 2011

3. USB Bootloader HEW Workspace
The Bootloader App Note is a fully working demonstration, with full source code being available as an accompanying
download. To view the source code and projects, it is recommended that you use HEW4.
The Workspace consists of 2 projects, USB_Bootloader, and TestCode.
USB_Bootloader is the Bootloader.
TestCode is an example project that is built for the Bootloader.
When developing an application for the Bootloader, the user has
to be aware of some design constraints. Please refer to section 7
of this Application Note for details.
The following briefly describes the purpose of each file.
command.c:
- Command handler for the Bootloader menu system
dbsct.c
- Section initialization. This differs from the standard dbsct.c
generated by the HEW project wizard as we use the segment
initialization to copy the FLASH programming routines
from FLASH to RAM
fixed_interrupt.c
- The RX62N has 2 interrupt vector tables, a fixed vector
table and a relocatable table.
- The fixed vector table contains 5 vectors, 4 of which have to
either map to ISR handlers in the User App, or if they
occur during Bootloader operation, be handled by the
Bootloader.
- This provides the mechanism for doing this.
Flash_API_RX62N.c
- The FLASH erasing / programming routines.
hwsetup.c
- Configures the System, Peripheral and Bus Clocks of the
RX62N.
main.c
- Called as part of PowerON_Reset()
mtu2.c
- Code for the control of MTU2 Channel 8. Used to generate
1ms timeouts.
resetprg.c
- Code that is executed after a Reset. Calls Segment
Initialisation, Hardware Setup and main().
XModem
- Code for handling data (transmit & receive) following the
XModem protocol.

R01AN0474EG0100 Rev.1.00 Page 5 of 18
J an 23, 2011
4. Bootloader Overview
The Bootloader enables the user to manage the erasing & programming of the RX62N FLASH memory, and the
execution of any downloaded application.
This is achieved by a basic 5 option menu that can be viewed in a terminal emulator program, such as HyperTerminal.
The USB Function peripheral is used and is configured as CDC Class, thus making the USB Function peripheral appear
as a COM port on a PC.
** Please note that you will have to provide the CDC inf file for the PC, the first time the application is run. **
** This is provided in the source code at the following location .. \USB_Bootloader\USB_Bootloader\Host\Driver\ **

The basic operation of the Bootloader is detailed by the flow diagram in figure 2.

VBUS interrupt?
(USB cable attached?)
time ==5s ?
Character detected
from Host PC?
Initialise the USB peripheral.
Initialise the MTU peripheral
Start MTU
time =0s
PowerOn Reset
Display Bootloader Menu.
Is User App
programmed into
Device?
Run User App. while(1);
No No
No
No
Yes
Yes Yes
Yes
Figure 2.
R01AN0474EG0100 Rev.1.00 Page 6 of 18
J an 23, 2011
5. Bootloader Menus
If a USB cable is connected to the RSK within 5 seconds of Power-On, the RX62N will enumerate with the PC,
configure the USB Function peripheral as a CDC Class device and then wait for a character to be received on the USB-
Comm port.
When this is received it will display the menu as shown in figure 3.

5.1 Menu Explanation
1. . . . . Blank Check User Area
Reports back the status of the User Area: Flash Blocks EB1 to EB35.

2 . . . . . Erase User Area
Erases the entire User Area: Flash Blocks EB1 to EB35.

3. . . . . Erase User Block
Allows the User to Erase a specific block, allowable blocks being 01 to 35.

4. . . . . Program Flash via XModem Download
Transfer the binary image file of the User Application to the RX62N and program the FLASH memory.

5. . . . . Start User Program
Allows the User to start execution of the User Application, if code is detected in the User Area.
Figure 3.

R01AN0474EG0100 Rev.1.00 Page 7 of 18
J an 23, 2011

5.2 Transferring a file in Hyperterminal via XModem Protocol
For Bootloader menu options 1, 2, 3 & 5, the User only need to enter data via the keyboard responses.
Bootloader menu option 4 requires data from the keyboard and then for data to be transmitted via the XModem protocol.
When using Hyperterminal, this is achieved by the Transfer menu option.

When Option 4 is entered, the User will be prompted to enter the address to program code to, followed by a prompt to
confirm the programming process.

When Start XModem Download is displayed, select Send File from the Transfer menu option.

R01AN0474EG0100 Rev.1.00 Page 8 of 18
J an 23, 2011

From the Send File dialogue, select XModem from the Protocol list box and then Browse to the required file.
Note that this file has to be a binary file. Please see section 7 for details.
After pressing Send the progress dialogue is displayed.

When complete, the Bootloader will report back the status of the FLASH programming process.

Press any key on the Keyboard to display the Bootloader menu.
It is now possible to execute the new code using option 5.

R01AN0474EG0100 Rev.1.00 Page 9 of 18
J an 23, 2011
6. Bootloader System Resource
The Bootloader application is a User Application itself, and as such requires a certain amount of ROM and RAM to
operate. The Bootloader application memory map is shown in figure 9.
It can be seen that the Bootloader application code is located in 2 areas of FLASH memory, between addresses
HFFF80000 and HFFF87FF, and HFFFFF000 H FFFFFFFF.
Therefore, this leaves FLASH memory from HFFF88000 to HFFFFEFFF available to the User Application.
This leaves 47696kB of internal Flash memory available to the User Application.
When the Bootloader is executing it uses the internal RAM, typically as storage areas for the data received prior to
programming the FLASH, which is in 256byte lines.
When the Bootloader is not executing then the entire internal RAM is available to the User Application.
Additionally, the Bootloader uses the USB0 peripheral and 1 of MTU timer channels.
The USB peripheral is obviously used to enable USB communications, the MTU timer is to provide a time out when
running the menu handler and USB comms.
These peripherals are available to the User Application.

R01AN0474EG0100 Rev.1.00 Page 10 of 18
J an 23, 2011
The Bootloader uses FLASH blocks EB0, EB36 & EB37.
This leaves FLASH blocks EB01 EB35 available to the User Application.

EB37
EB36
EB35
EB34
EB33
EB32
EB31
EB30
EB29
EB28
EB27
EB26
EB25
EB24
EB23
EB22
EB21
EB20
EB19
EB18
EB17
EB16
EB15
EB14
EB13
EB12
EB11
EB10
EB09
EB08
EB07
EB06
EB05
EB04
EB03
EB02
EB01
EB00
On-chip RAM
Reserved
Peripheral I/O Registers
Data FLASH
Reserved
FCU RAM
Reserved
Reserved
Reserved

FLASH Memory
(Write)
Reserved
FCU ROM
Reserved
USB Boot Mode ROM
Reserved

FLASH Memory
(Read)
H 00000000
H00017fff
H 00800000
H000fffff
H 00100000
H00107fff
H 007f 8000
H007f9fff
H 007f c000
H007fc4ff
H 007f f c00
H007fffff
H 00f 80000
H00ffffff
H f ef f e000
Hfeffffff
H f f 7f c000
Hff80bfff
H f f f 80000
Hffffffff
EB00 - EB07: 4kByte Blocks
EB08 - EB37: 16kByte Blocks
Figure 9.
R01AN0474EG0100 Rev.1.00 Page 11 of 18
J an 23, 2011
7. RX600 FLASH Programming
The Bootlader application has to be able to erase and program the FLASH memory of the RX600.
The routines for these procedures are detailed in the file Flash_API_RX62N.c, which are part of the RX600 FLASH
API.
Please refer to the Application Note Simple Flash API for RX600, which is Application Note Number
REU05B0131-0141.
A copy of Application Note Simple Flash API for RX600 (file name: reu05b0131_rxap.pdf) is included in the Source
Code download of this Application Note, in the Documents folder.

Figure 10.
R01AN0474EG0100 Rev.1.00 Page 12 of 18
J an 23, 2011
8. Creating a Bootloader Compliant Application
The Bootloader application allows a user to easily program a User Application into the RX62N. However, this User
Application has to be developed with the following constraints.
a) Reduced Code Space
The user has access to FLASH blocks EB01 to EB35
b) Interrupt handling of the fixed vector table
The Bootloader expects the User Application to provide ISR handlers for the
Privileged Instruction Exception,
Undefined Instruction Exception,
Floating Point Exception,
NMI Exception,
at specific addresses.
If not, then these Exceptions will not be handled correctly, causing the User Application to fail.
c) The output of the project has to be a binary file (.bin), not an absolute file (.abs)
The project TestCode supplied with the source code download shows how to create a Bootloader compliant application.

The Reduced Code Space is handled by the linker settings.
As the Bootloader uses FLASH blocks 37 and 36, the first available address for the User App is HFFF88000.
It is at this address that the Bootloader expects the Fixed Vector Table to be located.
This can be seen in the Link/Library Section dialogue, at address 0xFF88000 FIXEDVECT.

R01AN0474EG0100 Rev.1.00 Page 13 of 18
J an 23, 2011
The User Application Fixed Vector table is created in the file vecttbl.c

#i ncl ude " vect . h"

#pr agma sect i on C FI XEDVECT
/ *******************************************************************************/
/ * */
/ * DO NOT CHANGE THE LOCATI ON OF THI S VECTOR TABLE I N THE LI NKER SETTI NGS */
/ * */
/ * I F I T DOES NEED TO BE MOVED, THE BOOTLOADER WI LL HAVE TO BE MODI FI ED ALSO */
/ * */
/ *******************************************************************************/
voi d* const Fi xed_Vect or s[ ] =
{
( voi d*) Excep_Super Vi sor I nst , / / ; 0xf f f 88000 Except i on( Super vi sor I nst r uct i on)
Dummy, / / ; 0xf f f 88004 Reser ved
( voi d*) Excep_Undef i nedI nst , / / ; 0xf f f 8800c Except i on( Undef i ned I nst r uct i on)
Dummy, / / ; 0xf f f 8c010 Reser ved
( voi d*) Excep_Fl oat i ngPoi nt , / / ; 0xf f f 88014 Except i on( Fl oat i ng Poi nt )
Dummy, / / ; 0xf f f 8801c Reser ved
( voi d*) NonMaskabl eI nt er r upt , / / ; 0xf f f 88028 NMI
Power ON_Reset _PC / / ; 0xf f f 8802c RESET
};

The example code uses the NMI exception to demonstrate how the Fixed Vectors can be used if required.
Figure 12 shows the interaction between the Bootloader App and the User App when handling the Fixed Vector Table
Exceptions.
R01AN0474EG0100 Rev.1.00 Page 14 of 18
J an 23, 2011

PowerOnReset
Bootloader Superviosr ISR Code
Bootloader FPU ISR Code
Bootloader Undefined ISR Code
Bootloader NMI ISR Code
Address of User App Supervisor ISR Function
Address of User App FPU ISR Function
Address of User App Undefined ISR Function
Address of User App NMI ISR Function

This ISR code reads the memory contents of a fixed location.
This location has to be the address of the User App Fixed
Vector Table.
This ISR handler has a RTIE.
If the contents are not Hffffffff, (not blank) then the
Bootloader ISR Code will call the function.
Extract from file f i xed_i nt er r upt . c ( - Project USB_Bootloader)
/ *******************************************************
Except i on ( NMI )
*******************************************************/
#pr agma i nt er r upt I nt er r upt _NMI
voi d I nt er r upt _NMI ( voi d)
{
unsi gned l ong *p;
voi d ( *f p) ( voi d) ;

p = ( unsi gned l ong *) ( USER_APP_FI XED_VECT_TBL_BASE_ADDR +
NMI E_OFFSET) ;
i f ( *p ! = 0xf f f f f f f f )
{
/ / cal l user pr ogr am
f p = ( voi d ( *) ( voi d) ) *p;
f p( ) ;
}
el se
{
br k( ) ;
}
}

Bootloader
Code
User
App
Code
Supervisor
FPU
Undefined
NMI
Bootloader
Code
User App NMI ISR Function This function is the User App ISR.
This must be returned from as any other function and not
treated as an interrupt with a RTIE at the end of the function.
Therefore, remove the #pragma interrupt language extension
when declaring the ISR in the User App Code.
Extract from file vect . h ( - Project TestCode)
/ / NMI
/ / #pr agma i nt er r upt ( NonMaskabl eI nt er r upt )
/ / Remove #pr agma - not r equi r ed f or User App Fi xed Vect or
voi d NonMaskabl eI nt er r upt ( voi d) ;

Extract from file mai n. c ( - Project TestCode)

voi d NonMaskabl eI nt er r upt ( voi d)
{
/ / Toggl e LED t o show NMI act i vat i on
unsi gned shor t Count ;
f or ( Count =0; Count <100; Count ++)
{
PORT0. DR. BI T. B2 = 1 - PORT0. DR. BI T. B2;
}
}
Address of Bootloader NMI ISR
Figure 12.
R01AN0474EG0100 Rev.1.00 Page 15 of 18
J an 23, 2011

8.1 Creating the User App Fixed Vector ISRs
The RX62N has five fixed vectors:
The User App may wish to use the vectors Super, Und, FPU and NMI. The mechanism for handling these is detailed in
figure 12.
The TestCode User App uses the NMI.
The User App NMI was created by the following steps.

Firstly, the function prototype in file vect.h is changed, by commenting out the #pragma interrupt ( _ )
Then the function declaration is modified to reflect the required usage.
By default, any of the fixed vectors will call the brk() function, which itself generates a break exception, which is the
first entry of the relocatable vector table.
In this example the NMI function is made an extern and the NMI ISR is declared main.c
Extract from intprg.c
/ / NMI
ext er n voi d NonMaskabl eI nt er r upt ( voi d) ; / / { br k( ) ; }

Extract from main.c
voi d NonMaskabl eI nt er r upt ( voi d)
{
unsi gned shor t Count ;
f or ( Count =0; Count <100; Count ++)
{
}
}
R01AN0474EG0100 Rev.1.00 Page 16 of 18
J an 23, 2011
The relocatable vectors are easily moved as the RX62N has an Interrupt Table Register (INTB) that specifies the
address of the where the vector table starts.
The INTB registers is initialized as part of PowerOn_Reset().
voi d Power ON_Reset _PC( voi d)
{
set _i nt b( ( unsi gned l ong) __sect op( " C$VECT" ) ) ;
.
.
.
}

C$VECT is again specified in the Linker Setting, as part of C$* entry.
ISRs are specified using the #pragma language extension.
This can be seen in vect.h.
To demonstrate ISR usage, the example code generates a MTU2 Channel 8 Compare Match B interrupt.
The entry in vect.h has been modified to:
/ / MTU8 TGI B8
#pr agma i nt er r upt ( Excep_MTU8_TGI B8( vect =154) )
ext er n voi d Excep_MTU8_TGI A8( voi d) ;

and the ISR function is declared in main.c

voi d Excep_MTU8_TGI B8( voi d)
{
}

R01AN0474EG0100 Rev.1.00 Page 17 of 18
J an 23, 2011
As mentioned previously, the output of the User Application has to be of binary format.
This is done in the linker settings.

Figure 13.
R01AN0474EG0100 Rev.1.00 Page 18 of 18
J an 23, 2011
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.

A-1
Revision Record
Description
Rev.

Date
Page Summary
1.00 J an.23.11 First edition issued

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 accord 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. 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.
2. 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.
3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part.
4. 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.
5. 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.
6. 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.
7. 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": 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; anti-crime 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.
8. 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.
9. 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.
10. 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.
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
Refer to "http://www.renesas.com/" for the latest and detailed information.
Renesas Electronics America Inc.
2880 Scott Boulevard Santa Clara, CA 95050-2554, U.S.A.
Tel: +1-408-588-6000, Fax: +1-408-588-6130
Renesas Electronics Canada Limited
1101 Nicholson Road, Newmarket, Ontario L3Y 9C3, Canada
Tel: +1-905-898-5441, Fax: +1-905-898-3220
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 Dsseldorf, Germany
Tel: +49-211-6503-0, Fax: +49-211-6503-1327
Renesas Electronics (China) Co., Ltd.
7th Floor, Quantum Plaza, No.27 ZhiChunLu Haidian District, Beijing 100083, P.R.China
Tel: +86-10-8235-1155, Fax: +86-10-8235-7679
Renesas Electronics (Shanghai) Co., Ltd.
Unit 204, 205, AZIA Center, No.1233 Lujiazui Ring Rd., Pudong District, Shanghai 200120, China
Tel: +86-21-5877-1818, Fax: +86-21-6887-7858 / -7898
Renesas Electronics Hong Kong Limited
Unit 1601-1613, 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong
Tel: +852-2886-9318, Fax: +852 2886-9022/9044
Renesas Electronics Taiwan Co., Ltd.
7F, No. 363 Fu Shing North Road Taipei, Taiwan, R.O.C.
Tel: +886-2-8175-9600, Fax: +886 2-8175-9670
Renesas Electronics Singapore Pte. Ltd.
1 harbourFront Avenue, #06-10, keppel Bay Tower, Singapore 098632
Tel: +65-6213-0200, Fax: +65-6278-8001
Renesas Electronics Malaysia Sdn.Bhd.
Unit 906, 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 Korea Co., Ltd.
11F., Samik Lavied' or Bldg., 720-2 Yeoksam-Dong, Kangnam-Ku, Seoul 135-080, Korea
Tel: +82-2-558-3737, Fax: +82-2-558-5141
SALES OFFICES
2010 Renesas Electronics Corporation. All rights reserved.
Colophon 1.0

R01an0474eg rx62n

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

R01an0474eg rx62n

Transféré par

Droits d'auteur :

Formats disponibles

APPLICATION NOTE

R01AN0474EG0100 Rev.1.00 Page 1 of 18

Vous aimerez peut-être aussi