AN3259
Application note
RS232 communications with a terminal
using the STM8S-DISCOVERY
Application overview
This application note describes how to control the STM8S-DISCOVERY from a terminal
window running on a PC which is connected to the STM8S105C6T6 microcontroller UART
through an RS232 cable.
After adding the required components to the board and downloading the application
software, you will be able to use a terminal to manage STM8S GPIOs and TIM3 timer, and
to configure the beeper output.
Reference documents
●
STM8S-DISCOVERY evaluation board user manual (UM0817).
●
Developing and debugging your STM8S-DISCOVERY application code (UM0834).
●
ST232B-ST232C datasheet
All these documents are available at http://www.st.com.
December 2010
Doc ID 17835 Rev 1
1/25
www.st.com
Contents
AN3259
Contents
1
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2
Configuring the STM8S-DISCOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3
Application description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4
3.1
Hardware required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2
Application schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3
Application principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3.1
Running the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3.2
Communication sequence between the STM8S-DISCOVERY
and the terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Software description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1
STM8S peripherals used by the application . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2
Configuring STM8S standard firmware library . . . . . . . . . . . . . . . . . . . . . . 9
4.3
Application software flowcharts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3.1
Application main routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3.2
App_menu function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3.3
GetInputString function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3.4
Get_key function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3.5
SerialPutString and SerialPutChar functions . . . . . . . . . . . . . . . . . . . . . 16
4.3.6
GetIntegerInput function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Appendix A Standard ASCII character codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Appendix B Configuring your terminal window. . . . . . . . . . . . . . . . . . . . . . . . . . 20
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2/25
Doc ID 17835 Rev 1
AN3259
List of tables
List of tables
Table 1.
Table 2.
Table 3.
Table 4.
List of passive components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
List of packaged components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Standard ASCII character codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Doc ID 17835 Rev 1
3/25
List of figures
AN3259
List of figures
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
Figure 11.
Figure 12.
Figure 13.
Figure 14.
4/25
Application schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Terminal window menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Main routine flowchart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
App_menu flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
GetInputString flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Get_key function flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
SerialPutChar flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
SerialPutString flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GetIntegerInput flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Launching Windows HyperTerminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Selecting communication port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring connection properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Checking communication settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
ASCII Setup parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Doc ID 17835 Rev 1
AN3259
1
Prerequisites
Prerequisites
The material required to run the STM8S-DISCOVERY terminal demonstration application is
the following:
2
●
A terminal window running on a PC: the terminal emulator software can be Windows
Hyperterminal (see Appendix B), TeraTerm Pro, or any terminal software.
●
An RS232 null-modem cable (transmit and receive line crosslinked).
Configuring the STM8S-DISCOVERY
Prior to running the application, the STM8S-DISCOVERY must be configured to enable the
beeper output. The beeper output is an STM8S105C6T6 alternate function. It is enabled by
setting the alternate function remap option bit AFR7 in OPT2 option byte to ‘1’.
For details on alternate function remapping and on option bytes, refer to user manual
“Developing and debugging your STM8S-DISCOVERY application code” (UM0834), and to
the STM8S105xx datasheet, respectively.
3
Application description
3.1
Hardware required
This application uses STM8S-DISCOVERY on-board LED (LD1) together with its associated
resistor (R1).
The external passive components required by the application are listed inTable 1.
The application also makes use of a 5 V powered ST232B RS232 driver/receiver (see
Table 2). This extra component is essential since the COM port of the PC operates from a
nominal 12 V power supply. This is not compatible with the STM8S UART input/outputs
operating at 5 V. This component is available in an SO16 package which fits the STM8SDISCOVERY footprint. For more information on the ST232B refer to the ST232B datasheet.
Table 1.
List of passive components
Component description
Value
B1 buzzer
-
C1,C2,C3,C4,C5 capacitors
100 nF
DB9 connector
-
Doc ID 17835 Rev 1
5/25
Application description
Table 2.
3.2
AN3259
List of packaged components
Part name
Component description
Package
ST232B
Very-high speed ultralow-power consumption 5 V
RS232 driver/receiver used for UART 5/12 V level
shifter.
SO16
Application schematics
Figure 1 shows the application electrical schematics.
If the RS232 cable is not a null-modem cable (transmit and receive lines not crosslinked),
connect U1 pin14 to DB9 pin2 and U1 pin13 to DB9 pin3.
Figure 1.
Application schematics
6
#
N&
#
NF
5
#
N&
4OUT
2IN
2OUT
4IN
#
N&
#
N&
$"
34"
0$
"%%0%2
2
'0)/
4)-
,$
5!24
6
0$
0$
0$
"
0IEZOBUZZER
34-3#
AIB
6/25
Doc ID 17835 Rev 1
AN3259
3.3
Application description
Application principle
This application sets up a standard communication interface between the STM8S105C6T6
microcontroller and a terminal window running on a PC. Communications are performed
thanks to STM8S UART using the RS232 protocol. Both terminal window and UART must
be configured in the same way (see Appendix B: Configuring your terminal window).
This document only describes the communications and data processing from the STM8S
UART side. For more information about Windows HyperTerminal or similar software, refer to
Microsoft® Help or suppliers web pages.
3.3.1
Running the application
To run the application, perform the following steps:
1.
Launch and configure a terminal window on your PC (see Appendix B: Configuring
your terminal window for an example regarding Windows HyperTerminal).
2.
Compile and run the application firmware using the ST Visual Develop (STVD).
3.
Connect your PC to the STM8S-DISCOVERY through an RS232 cable.
4.
When the application has started, a menu is displayed on the Windows HyperTerminal
(Figure 2.: Terminal window menu). It allows to:
–
Switch LD1 on or off.
–
Configure LD1 blinking speed.
–
Enable/disable the beeper and select the beep frequency)
All the information displayed on this menu are sent by the STM8S microcontroller.
When a key is struck on the HyperTerminal, the corresponding ASCII value is sent to
the microcontroller and decoded.
Figure 2.
Terminal window menu
Doc ID 17835 Rev 1
7/25
Application description
3.3.2
8/25
AN3259
Communication sequence between the STM8S-DISCOVERY
and the terminal
1.
The STM8S microcontroller sends the character string ‘Enter your choice’ to the PC
terminal emulator software.
2.
The terminal displays the string ‘Enter your choice’.
3.
The user strikes key 2 on his keyboard.
4.
The terminal emulator software sends back the corresponding ASCII code (0x52) to the
microcontroller (see Appendix A: Standard ASCII character codes).
5.
The microcontroller decodes the data received, sends back the code 0x52 for it to be
displayed on the terminal, and stores the value ‘2’ in memory.
6.
The terminal emulator software receives the code 0x52 and displays ‘2’.
7.
The user strikes the Return key.
8.
The terminal emulator software send back the code 0x0D corresponding to carriage
return (see Appendix A: Standard ASCII character codes).
9.
The STM8S105C6T6 microcontroller decode the data received, sends back the code
0x0D for it to be displayed it on the terminal, and performs the action associated to
option 2.
Doc ID 17835 Rev 1
AN3259
Software description
4
Software description
4.1
STM8S peripherals used by the application
This application example uses the STM8S standard firmware library to control general
purpose functions. It makes use of the following STM8S peripherals:
UART2
UART2 is used to communicate with the terminal window running on the PC. It must be
configured as follows:
●
Baud rate = 9600 baud
●
Word length = 8 bits
●
One stop bit
●
No parity
●
Receive and transmit enabled
●
UART2 clock disabled
The communications are managed by polling each receive and transmit operation.
Note:
The terminal window and the STM8S UART peripheral must be configured with the same
baud rate, word length, number of stop bits, and parity.
Timer 3 (TIM3)
TIM3 timer is configured as a timebase with interrupt enabled to control LD1 blinking speed.
GPIOs
The GPIOs are used to interface the MCU with external hardware. Port PD0 is configured as
output push-pull low to drive LD1.
BEEPER
To drive the buzzer, the BEEPER peripheral outputs a signal of 1, 2, or 4 KHz on the BEEP
output pin.
4.2
Configuring STM8S standard firmware library
The stm8s_conf.h file of the STM8S standard firmware library allows to configure the library
by enabling the peripheral functions used by the application.
The following define statements must be present:
#define
#define
#define
#define
_GPIO 1 enables the GPIOs
_TIM3 1 enables TIM3
_BEEPER 1 enables the BEEPER
_UART2 1 enables UART2
Doc ID 17835 Rev 1
9/25
Software description
4.3
AN3259
Application software flowcharts
This section describes the application software main loop and the function that controls data
reception/transmission from/to the terminal window:
●
App_Menu
This function is used to display a menu on the terminal, and manage the information
entered by the user.
●
SerialPutString
This function is used to transmit a string to the terminal.
●
SerialPutChar
This function is used to transmit a character to the terminal.
●
GetInputString
This function is used to receive a string from the terminal.
●
GetIntegerInput
This function is used to receive an integer from the terminal.
●
Get_Key
When a key is stroke, this function returns the corresponding hexadecimal code.
10/25
Doc ID 17835 Rev 1
AN3259
4.3.1
Software description
Application main routine
The application main routine configures the STM8S peripherals and enables all the
standard interrupts used by the application. When the initialization is complete, the main
routine displays the application menu on the terminal window (see Figure 3).
Figure 3.
Main routine flowchart
ªªªªª
34!24
(3)CONFIGURATION
(3)CLOCKPRESCALERSETTO
'0)/INITIALIZATION
ªªªªªªªªªªªªªªªªªªªªªªªªª
0$CONFIGUREDASOUTPUTPUSHPULLLOW
4)-INITALIZATION
4)-PRESCALERSETTO
4)-!22SETTO&&&
4)-UPDATEINTERRUPTENABLEDª
ªªªªªªªªªªªªªªªªªªªªªªªªªªªª
ªªªªªªªªªªªªªªªª
"AUDRATEBAUDS
ªªªªªªªªªªªªªªªªªªªª
7ORDLENGTHBITS
ªªªªªªªªªªªª
0ARITYNONE
2ECEIVEANDTRANSMITENABLED
ªªªªªªªªªªªªªªªªªªªªªªªªªªªª
5!24CLOCKDISABLEDªªªªªªªªªªªªªªªªªª
ªªªªªªªªªªªªªªªªªªªª
5!24INITALIZATION
"%%0%2CALIBRATION
%NABLEGENERALINTERRUPT
!PP?-ENU
%.$
AI
Doc ID 17835 Rev 1
11/25
Software description
4.3.2
AN3259
App_menu function
The App_menu function is the main application routine. It displays a menu on the terminal
through which the GPIOs, TIM2 and BEEPER can be configured. App_menu calls
GetInputString, GetIntegerInput and SerialPutString to send and receive data through the
RS232 interface.
Figure 4.
App_menu flowchart
34!24
3UCCESSIONOF'ET)NPUT3TRINGCALLSTODISPLAY
ªTHEMENUOFTHETERMINAL
ªªªªªªªªªªªªª
0RINT-ENU
'ET)NPUT3TRING#HOICE
#HOICE
9ES
ªªª
,$BLINKING/&&
.O
,$/.
ª
#HOICE
9ES
,$BLINKING/&&
ª.O
ª
ª,$/&&
ªªªªªª
#HOICE
9ES
ªªªªªªªªªªªªª
,$BLINKING/.
ªª
.O
#HOICE
9ES
&REQ'ET)NTEGER)NPUT
ªª
.O
"EEP?FREQFREQ
"EEPER/.
#HOICE
9ES
ª"EEPER/&&
ªªªªªªªªª
ªª
.O
3ERIAL0UT3TRING#HOICE%RROR
%.$
AIB
12/25
Doc ID 17835 Rev 1
AN3259
4.3.3
Software description
GetInputString function
The GetInputString function is used to receive and store the character strings sent through
the terminal window. This function relies on the Get_key function to acquire and decode
each character (see Section 4.3.4). Different actions can be performed according to the
value of the character ASCII code:
●
If ASCII code = ‘\b’
A backspace has been sent by the terminal. The last character of the string is erased if
the string is not empty.
●
If ASCII code belongs to {0...1 or a...Z}
The character is stored.
●
If ASCII code = ‘\r’
The GetInputString function stores the “end of string” value, '\0', at the end of the string.
The maximum number of ASCII codes stored in the buffP[bytes_read] buffer has been
reached
The software erases the recorded string and waits for another input from the terminal.
For more information on ASCII codes refer to Appendix A: Standard ASCII character codes.
Doc ID 17835 Rev 1
13/25
Software description
Figure 5.
AN3259
GetInputString flowchart
34!24
BYTES?READ
ªª
ª ªªªªªªªª
'ET?+EY
+EY<B
9ES
.O
BYTES?READ
.O
9ES
BYTES?READ
ª
BYTES?READ
ªªªªªªªªªªªªªª
ª
≥
ª -AX
.O
ªª
9ES
ªªªªªª
ª
3ERIAL0UT3TRING3IZEOVERFLOW
ª ªªª
ªªª
ªªª
ªªªªªª ªªª
BYTES?READ
ªªª ªªªªªª
KEY
ORA:
.O
ªª
ªª
ªª
9ES
ªª
ª
3TORE!3#))CODEIN
ªªªªªªªªªªªªªªª
BUFF0;BYTES?READ=
ªªªªª
BYTES?READ
3ERIAL0UT#HAR!3#))CODE
.O
KEY@<R
ªª
BYTES?READ@<
ªªª
%.$
AIB
14/25
Doc ID 17835 Rev 1
AN3259
4.3.4
Software description
Get_key function
The Get_key function is used to detect a key stroke on the terminal by polling the UART
RXNE flag. This function returns the received value.
Figure 6.
Get_key function flowchart
34!24
+EY
5!2428.%
FLAGSET
.O
9ES
+EY5!24DATAREGISTER
2ETURN+EY
AIB
Doc ID 17835 Rev 1
15/25
Software description
4.3.5
AN3259
SerialPutString and SerialPutChar functions
The SerialPutString function is used to send a character string through the UART. The string
characters are sent one by one by the SerialPutChar function as described in the flowcharts
shown in Figure 8 and Figure 9.
Figure 7.
SerialPutChar flowchart
Figure 8.
SerialPutString flowchart
34!24
34!24
I
5!24?SEND$ATACHAR
3TRING;I=
<
CHARSENT
9ES
34/0
.O
.O
3ERIAL0UT#HAR3TRING;I=
9ES
34/0
AIB
I
AI
16/25
Doc ID 17835 Rev 1
AN3259
4.3.6
Software description
GetIntegerInput function
The GetIntegerInput function is used to check that incoming data correspond to an integer. If
so, the data are stored in the memory. Otherwise the user is prompted to enter new data.
Figure 9.
GetIntegerInput flowchart
34!24
'ET)NPUT3TRING
3TR@<
9ES
.O
3TR@AOR
3TR@!
9ES
3ERIAL0UT3TRING5SERCANCELLED
.O
2ETURN
3TRIS
ANINTEGER
.O
3ERIAL0UT3TRING%RRORINPUTAGAIN
9ES
6ALUESTORED
2%452.
AI
Doc ID 17835 Rev 1
17/25
Standard ASCII character codes
Appendix A
Table 3.
18/25
AN3259
Standard ASCII character codes
Standard ASCII character codes
Hex
Char
Hex
Char
Hex
Char
Hex
Char
0x00
NULL
0x20
Space
0x40
@
0x60
‘
0x01
Start of heading
0x21
!
0x41
A
0x61
a
0x02
Start of text
0x22
“
0x42
B
0x62
b
0x03
End of text
0x23
#
0x43
C
0x63
c
0x04
End of transmit
0x24
$
0x44
D
0x64
d
0x05
Enquiry
0x25
%
0x45
E
0x65
e
0x06
Ack
0x26
&
0x46
F
0x66
f
0x07
Audible bell
0x27
‘
0x47
G
0x67
g
0x08
Backspace
0x28
(
0x48
H
0x68
h
0x09
Horizontal tab
0x29
)
0x49
I
0x69
i
0x0A
line feed
0x2A
*
0x4A
J
0x6A
j
0x0B
Vertical tab
0x2B
+
0x4B
K
0x6B
k
0x0C
Form feed
0x2C
,
0x4C
L
0x6C
l
0x0D
carriage return
0x2D
-
0x4D
M
0x6D
m
0x0E
Shift out
0x2E
.
0x4E
N
0x6E
n
0x0F
Shift in
0x2F
/
0x5F
O
0x6F
o
0x10
Data link escape
0x30
0
0x50
P
0x70
p
0x11
Device control 1
0x31
1
0x51
Q
0x71
q
0x12
Device control 2
0x32
2
0x52
R
0x72
r
0x13
Device control 3
0x33
3
0x53
S
0x73
s
0x14
Device control 4
0x34
4
0x54
T
0x74
t
0x15
Neg. Ack
0x35
5
0x55
U
0x75
u
0x16
Synchronous idle
0x36
6
0x56
V
0x76
v
0x17
End trans. block
0x37
7
0x57
W
0x77
w
0x18
Cancel
0x38
8
0x58
X
0x78
x
0x19
End of medium
0x39
9
0x59
Y
0x79
y
Doc ID 17835 Rev 1
AN3259
Standard ASCII character codes
Table 3.
Standard ASCII character codes (continued)
Hex
Char
Hex
Char
Hex
Char
Hex
Char
0x1A
Substitution
0x3A
:
0x5A
Z
0x7A
z
0x1B
Escape
0x3B
;
0x5B
[
0x7B
{
0x1C
File sep.
0x3C
<
0x5C
\
0x7C
|
0x1D
Group sep.
0x3D
=
0x5D
]
0x7D
}
0x1E
Record sep.
0x3E
>
0x5E
^
0x7E
~
0x1F
Unit sep.
0x3F
?
0x5F
_
0x7F
<DEL>
Doc ID 17835 Rev 1
19/25
Configuring your terminal window
Appendix B
AN3259
Configuring your terminal window
The terminal window connected to the STM8S-DISCOVERY must be configured with the
following settings valid for all terminal types:
●
Communication port: COM1 or other available
●
Bits per second: 9600
●
Data bits: 8
●
Parity: none
●
Stop bits: 1
●
Flow control: none
To provide a ready-to-use application example, a preconfigured terminal using Windows
HyperTerminal and COM1 port is provided within the project folder. To launch it, simply
execute the .ht file included in the project.
However, you can also set up a new connection with the STM8S-DISCOVERY based on
Windows HyperTerminal and related to this example by following the steps below:
1.
Open Windows HyperTerminal application and choose a connection name, such as
“MyConnection” and validate it by clicking OK.
Figure 10. Launching Windows HyperTerminal
20/25
Doc ID 17835 Rev 1
AN3259
Configuring your terminal window
2.
Select COM1 or any available port on your computer and validate your choice by
clicking OK. Other fields can remain set to the default value.
Figure 11. Selecting communication port
3.
Configure the communication port properties as shown in Figure 12. Windows
HyperTerminal is launched and communications can start.
Figure 12. Configuring connection properties
Doc ID 17835 Rev 1
21/25
Configuring your terminal window
4.
AN3259
To check communication settings:
a)
Disconnect the HyperTerminal by choosing Call > Disconnect from the
HyperTerminal main menu.
b)
Once communications are stopped, go to the Settings tab in MyConnection
Properties menu. The parameters should be as shown below.
Figure 13. Checking communication settings
22/25
Doc ID 17835 Rev 1
AN3259
Configuring your terminal window
c)
Finally, click ASCII Setup in MyConnection properties menu, check that the
ASCII parameters match those shown in Figure 14, and modify them if needed.
Figure 14. ASCII Setup parameters
d)
Close MyConnection Properties menu, and restart communications by choosing
Call > Call from the HyperTerminal main menu. Your STM8S-DISCOVERY
application is now ready to start.
Doc ID 17835 Rev 1
23/25
Revision history
AN3259
Revision history
Table 4.
Document revision history
Date
06-Dec-2010
24/25
Revision
1
Changes
Document migrated from UM0884 rev 1.
Document extended to all terminal windows.
Added Section 1: Prerequisites. Updated Figure 1: Application
schematics and added case of not null-modem RS232 cable.
Removed section “Description of the application package.
Updated Section 3.3.1: Running the application.
Updated Section 4.1: STM8S peripherals used by the application.
Renamed SerialGetString and SerialGetInterger, SerialInputString
and SeriaIntegerInput, respectively.
Updated Section 4.3.1: Application main routine overview.
Updated Section 4.3.2: App_menu function overview.
Updated Section 4.3.3: GetInputString function, Section 4.3.4:
Get_key function, Section 4.3.5: SerialPutString and SerialPutChar
functions, and Section 4.3.6: GetIntegerInput function.
Doc ID 17835 Rev 1
AN3259
Please Read Carefully:
Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the
right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any
time, without notice.
All ST products are sold pursuant to ST’s terms and conditions of sale.
Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no
liability whatsoever relating to the choice, selection or use of the ST products and services described herein.
No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this
document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products
or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such
third party products or services or any intellectual property contained therein.
UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS
OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS EXPRESSLY APPROVED IN WRITING BY AN AUTHORIZED ST REPRESENTATIVE, ST PRODUCTS ARE NOT
RECOMMENDED, AUTHORIZED OR WARRANTED FOR USE IN MILITARY, AIR CRAFT, SPACE, LIFE SAVING, OR LIFE SUSTAINING
APPLICATIONS, NOR IN PRODUCTS OR SYSTEMS WHERE FAILURE OR MALFUNCTION MAY RESULT IN PERSONAL INJURY,
DEATH, OR SEVERE PROPERTY OR ENVIRONMENTAL DAMAGE. ST PRODUCTS WHICH ARE NOT SPECIFIED AS "AUTOMOTIVE
GRADE" MAY ONLY BE USED IN AUTOMOTIVE APPLICATIONS AT USER’S OWN RISK.
Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void
any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any
liability of ST.
ST and the ST logo are trademarks or registered trademarks of ST in various countries.
Information in this document supersedes and replaces all information previously supplied.
The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.
© 2010 STMicroelectronics - All rights reserved
STMicroelectronics group of companies
Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan Malaysia - Malta - Morocco - Philippines - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America
www.st.com
Doc ID 17835 Rev 1
25/25