STMicroelectronics-M24SR02-YMN6T-2
| Part # | STMicroelectronics-M24SR02-YMN6T-2 |
Download  | STMicroelectronics-M24SR02-YMN6T-2 |
M24SR02-Y
Dynamic NFC/RFID tag IC with 2-Kbit EEPROM,
NFC Forum Type 4
T
a
g and I²C interface
Datasheet
–
production data
Package
•
8-lead small-outline package (SO8)
ECOPACK2
•
TSSOP8 ECOPACK2
•
UFDFPN8 ECOPACK2
UFDFPN8
SO8
TSSOP8
Digital pad
•
GPO: configurable general purpose output
•
RF disable: activation/deactivation of RF
commands
Wafer
Temperature range
Features
•
From – 40 °C up to 85 °C
I
2
C interface
Description
M24SR02-Y belongs to the ST25 family, which
includes all STMicroelectronics NFC/RFID tag
and reader products.
2
•
Two-wire I
C serial interface supports
1 MHz protocol
•
Single supply voltage: 2.7 V to 5.5 V
Contactless interface
The M24SR02-Y device is a dynamic NFC/RFID
tag IC with a dual interface embedding an
EEPROM. It can be operated from an I
C
interface or by a 13.56 MHz RFID reader or from
an NFC phone.
•
NFC Forum Type 4 Tag
•
ISO/IEC 14443 Type A
•
106 Kbps data rate
2
•
Internal tuning capacitance: 25 pF
2
The I
C interface uses a two-wire serial interface,
consisting of a bidirectional data line and a clock
line. It behaves as a slave in the I
C protocol.
Memory
2
•
256-byte (2-kbit) EEPROM
•
Support of NDEF data structure
•
Data retention: 200 years
The RF protocol is compatible with ISO/IEC
14443 Type A and NFC Forum Type 4
T
a
g.
•
Write endurance:
– 1
million cycles at 25 °C
– 600
k cycles at 85 °C
•
Read: up to 246 bytes in a single command
•
Write: up to 246 bytes in a single command
•
7-byte unique identifier (UID)
•
128-bit passwords protection
April 2019
DS9985 Rev 12
1/88
This is information on a product in full production.
Contents
M24SR02-Y
Contents
Functional description
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Functional modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
I2C mode
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
T
a
g mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Serial clock (SCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
Serial data (SDA)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
Antenna coil (AC0, AC1)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
Ground (VSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
Supply voltage (V
CC
) .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
CC .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
1
2
Power-up conditions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
RF disable
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
2
Memory structure
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
File identifier
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
CC file layout
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2/88
DS9985 Rev 12
M24SR02-Y
Contents
Access right life time
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
NDEF file passwords
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
I2C password
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
Master and slave
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
RF token
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2
I
C token
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32
R-Block format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
S-Block format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
Command set
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
DS9985 Rev 12
3/88
5
Contents
M24SR02-Y
5.10 Specific
I²C command set
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
5.10.1 GetI2Csession
command .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.10.2 KillRFsession
command .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
RF device operation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Open an RF session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
Close an RF session
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
Applicative command set
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
I2C device operation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
Stop condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
I²C timeout on clock period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
Acknowledge bit (ACK)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
Data input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
I²C device address
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
I²C frame format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
60
7.10 Open
an I²C session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62
7.11 Close
the I²C session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62
4/88
DS9985 Rev 12
M24SR02-Y
Contents
Functional procedures
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Locking an NDEF file
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
Unlocking an NDEF file
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
Updating an NDEF file
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
UID: unique identifier
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
11.1 I2C
timing measurement condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
GPO parameters
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Write cycle definition
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
15.1 SO8N
package information
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
15.2 TSSOP8
package information
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
Ordering information
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Revision history
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
DS9985 Rev 12
5/88
5
List of tables
M24SR02-Y
List of tables
Details about the GPO field
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Details about the RF session field
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Read access righ
t
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
6
C-APDU forma
t
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
R-APDU forma
t
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
4
R-Block format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
R-Block detailed format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
S-Block format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Command set overview
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Status code of the M24SR02-Y
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
C-APDU of the Capability Container Select comman
d
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
9
R-APDU of the Capability Container Select comman
d
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
9
C-APDU of the UpdateBinary command
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
R-APDU of the UpdateBinary command
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Change reference data command forma
t
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
4
Enable Verification Requirement command format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
C-APDU of the ExtendedReadBinary command
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
R-APDU of the ExtendedReadBinary command
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6/88
DS9985 Rev 12
M24SR02-Y
List of tables
R-APDU table of the EnablePermanentState command
. . . . . . . . . . . . . . . . . . . . . . . . . . 48
R-APDU of the DisablePermanentState command
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
UpdateFileType command format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
R-APDU of the UpdateFileType comman
d
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
0
SendInterrupt command format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
R-APDU of the SendInterrupt command
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
R-APDU of the StateControl command
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ATS respons
e
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
3
PPS respons
e
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
4
Specific I²C command
s
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
GetI2Csession command format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
KillRFsession command format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
I
C frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
UID format
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
I
C operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
I
C DC characteristics
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2
I
C AC characteristics (400 kHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2
I
C AC characteristics (1 MHz
)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
1
GPO timings measurement
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Write cycle definitio
n
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
RF characteristics
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
package data
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Document revision history
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
DS9985 Rev 12
7/88
7
List of figures
M24SR02-Y
List of figures
M24SR02-Y block diagra
m
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8-pin package connection
s
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
0
GPO configured as Session Open (GPO field = 0xX1 or 0x1X
)
. . . . . . . . . . . . . . . . . . . . .
1
4
GPO configured as I
C answer ready (GPO field = 0xX3) . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 10.
Changing the read access right to an NDEF file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 11.
Changing the write access right to an NDEF file
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 12.
Command and response exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 13.
I²C token release sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 14.
NDEF tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 15.
AC test measurement I/O waveform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 16.
I
C AC waveforms
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 17.
Maximum Rbus value with fC = 400 kHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 18.
Maximum Rbus value with fC = 1 MHz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 19.
I2C bus protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 20.
SO8N – 8-lead plastic small outline, 150 mils body width, package outline . . . . . . . . . . . . 79
package recommended footprint
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
dual flat package outlin
e
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
2
8/88
DS9985 Rev 12
M24SR02-Y
Functional description
1
Functional description
The M24SR02-Y device is a dynamic NFC/RFID tag that can be accessed either from the
2
2
I C
or the RF interface. The RF and I
C host can read or write to the same memory, as only
one host can communicate at a given time with the M24SR02-Y. The management of the
interface selection is controlled by the M24SR02-Y device itself.
The RF interface is based on the ISO/IEC 14443 Type A standard. The M24SR02-Y is
compatible with the NFC Forum Type 4
T
a
g specifications and supports all corresponding
commands.
2
The I
C interface uses a two-wire serial interface consisting of a bidirectional data line and a
clock line. The devices carry a built-in 4-bit device type identifier code in accordance with
the I²C bus definition.
2
The device behaves as a slave in the I
C protocol.
Figure 1
displays the block diagram of the M24SR02-Y device.
Figure 1. M24SR02-Y block diagram
6XSSOꢄYROWDJH
9
&&
ꢁ
IRUꢄ,
ꢄꢄ
&ꢄLQWHUIDFH
h/ꢀꢁΘꢁƐLJƐƚĞŵꢁꢁꢁꢁ
ĂƌĞĂ
3RZHUꢄꢄꢄꢄ
PDQDJHPHQWꢄꢄꢄꢄ
XQLW
$QDORJꢄ)URQWꢋHQGꢄ
EDVHGꢄRQꢄ
5)ꢄLQWHUIDFHꢄꢄ
EDVHGꢄRQꢄ
,62ꢅ,(&ꢄꢂꢆꢆꢆꢀꢄ
7SHꢄ$ꢄVWDQGDUG
$&ꢂ
$&ꢊ
,62ꢅ,(&ꢄꢂꢆꢆꢆꢀꢄ
7SHꢄ$ꢄ
,QWHUQDOꢄWXQLQJ
FDSDFLWDQFHꢄꢄ
VWDQGDUG
1)&ꢄ)RUXPꢄ
7SHꢄꢆꢄ
7
D
Jꢄ
SURWRFRO
5)ꢄ
GLVDEOH
hƐĞƌꢁŵĞŵŽƌLJ
*32
‘LJLWDOꢄXQLW
6&/
6’$
,
ꢁ
&ꢄLQWHUIDFH
ꢁꢇꢈꢄ9ꢄ±ꢄꢉꢇꢉꢄ9
1)&B,ꢁ&
LQWHUIDFH
*1′
06ꢀꢁꢀꢂꢃ9ꢀ
DS9985 Rev 12
9/88
20
Functional description
M24SR02-Y
Table 1. Signal names
Function
Signal name
Direction
SDA
Serial data
I/O
SCL
Serial clock
Input
AC0, AC1
V
CC
Antenna coils
–
–
–
Supply voltage
V
SS
Ground
GPO
Interrupt output
(1)
Disables the RF communication
(2)
Open drain output
Input
RF disable
1. An
external pull-up > 4.7 k
Ω
is required.
2. An
external pull-down is required when the voltage on V
cc
is above its POR level.
Figure 2. 8-pin package connections
ꢂ
ꢁ
ꢀ
ꢆ
ꢃ
ꢈ
ꢌ
ꢉ
5)ꢄGLVDEOH
$&ꢊ
9
&&
*32
6&/
6’$
$&ꢂ
9
66
06ꢀꢊꢈꢆꢆ9ꢁ
1.1
Functional modes
The M24SR02-Y has two functional modes available. The difference between the modes
Table 2. Functional modes
Modes
I
2
C mode
Supply source
Comments
V
cc
The I
2
C interface is available
T
a
g mode
RF field only
The I
2
C interface is disconnected
Both I
2
C and RF interfaces are available
Dual interface mode
RF field or V
cc
2
1.1.1
1.1.2
I C
mode
2
2
M24SR02-Y is powered by V
. The I
C interface is connected to the M24SR02-Y. The I
C
host can communicate with the M24SR02-Y device.
CC
Tag mode
The M24SR02-Y is supplied by the RF field and can communicate with an RF host (RFID
reader or an NFC phone). The User memory can only be accessed by the RF commands.
10/88
DS9985 Rev 12
M24SR02-Y
Functional description
1.1.3
Dual interface mode
2
2
Both interfaces, RF and I
C, are connected to the M24SR02-Y and both RF or I
C host can
communicate with the M24SR02-Y device. The power supply and the access management
DS9985 Rev 12
11/88
20
Description of signals
M24SR02-Y
2
Description of signals
2.1
Serial clock (SCL)
This input signal is used to strobe all data in and out of the device. In applications where this
signal is used by slave devices to synchronize the bus to a slower clock, the bus master
must have an open drain output, and a pull-up resistor must be connected from Serial clock
CC
In most applications, though, this method of synchronization is not employed, and so the
pull-up resistor is not necessary, provided that the bus master has a push-pull (rather than
an open drain) output.
2.2
2.3
Serial data (SDA)
This bidirectional signal is used to transfer data in or out of the device. It is an open drain
output that may be wire-OR’ed with other open drain or open collector signals on the bus. A
CC
the value of the pull-up resistor can be calculated).
Antenna coil (AC0, AC1)
These inputs are used to connect the device to an external coil exclusively. It is advised not
to connect any other DC or AC path to AC0 or AC1.
When correctly tuned, the coil is used to access the device using NFC Forum Type 4
commands.
2.4
Ground (V
SS
)
V
, when connected, is the reference for the V
supply voltage for all pads, including AC0
CC
SS
and AC1.
2.5
Supply voltage (V
CC
)
This pin can be connected to an external DC supply voltage.
Note:
2.5.1
An internal voltage regulator allows the external voltage applied on V
to supply the
M24SR02-Y.
CC
Operating supply voltage V
CC
Prior to selecting the M24SR02-Y and issuing instructions to it, a valid and stable V
CC
voltage within the specified [V
(min), V
(max)] range must be applied.
T
o
m
aintain a
CC
CC
stable DC supply voltage, it is recommended to decouple the V
line with suitable
CC
capacitors (usually of the order of 10 nF and 100 pF) close to the V
/ V
package pins.
CC
SS
This voltage must remain stable and valid until the end of the transmission of the instruction
and, for a writing instruction (UpdateBinary, ChangeReferenceData,
12/88
DS9985 Rev 12
M24SR02-Y
Description of signals
EnableVerificationRequirement, DisableVerificationRequirement, EnablePermanentState,
DisablePermanentState, until the completion of the internal I²C write cycle (t
).
W
2.5.2
2.5.3
Power-up conditions
When the power supply is turned on, V
rises from V
to V
. The V
rise time must not
vary faster than 1 V/µs.
CC
SS
CC
CC
Device reset in I²C mode
In order to prevent inadvertent write operations during power-up, a power-on reset (POR)
circuit is included. At power-up (continuous rise of V
), the M24SR02-Y does not respond
CC
to any I²C instruction until V
has reached the power-on reset threshold voltage (this
CC
threshold is lower than the minimum V
operating voltage defined). When V
passes
CC
CC
over the POR threshold, the device is reset and enters the Standby power mode. However,
the device must not be accessed until V
has reached a valid and stable V
voltage
CC
CC
within the specified [V
(min), V
(max)] range.
CC
CC
In a similar way, during power-down (continuous decrease in V
), as soon as V
drops
CC
CC
below the power-on reset threshold voltage, the M24SR02-Y stops responding to any
instruction sent to it.
2.5.4
Power-down conditions
During power-down (continuous decay of V
), the M24SR02-Y must be in Standby power
CC
mode (mode reached after decoding a Stop condition, assuming that there is no internal
operation in progress).
2.6
RF disable
This input signal is used to disable the RF communication. When the voltage on the V
pin
CC
is below the POR level or not connected, an internal pull-down resistor is connected on this
pad. Thus, the RF disable pad is maintained to the low level and the RF analog front end is
activated. When the voltage on the V
pin is higher than the POR level, the I²C host must
CC
set this pin to enable or disable the RF communication. In Dual interface mode, RF disable
must not be left floating.
2.7
General purpose output (GPO)
The GPO pad is an open drain pad and a external pull-up resistor must be connected to it.
This pad is a configurable output signal. On delivery, GPO is configured as Session opened.
2
Its behavior is consistent with the I
C or RF session activated and with the mode chosen by
2
the user. The GPO pad is enable when an RF or an I
C session is open. When neither an
2
RF nor an I
C session is open, the GPO is high impedance.
DS9985 Rev 12
13/88
20
Description of signals
M24SR02-Y
(a)
The user can select one of these configurations
:
2
•
•
SessionOpen: an RF or I C session is ongoing.
MIP (NDEF Message updating In Progress): the RF host is writing an NDEF length
different from 0x0000. This mode can be used to detect when the RF host changes the
NDEF message as defined by the NFC Forum.
•
•
WIP (Writing In Progress): the M24SR02-Y is executing a writing operation.
2
INT (interrupt): the I C or RF host can force the M24SR02-Y to send a negative pulse
on the GPO pin.
2
2
•
•
I C ready response: an I C response is ready to be read by the I²C host.
2
State mode: the I C or RF host can control the state of the GPO pad during the RF
session.
•
RF busy: an RF host is communicating with the M24SR02-Y.
2.7.1
Session Open configuration (GPO field = 0xX1 or 0x1X)
2
When the GPO is configured as “Session Open”, it goes to the Low state when an RF or I
C
An RF session is taken when M24SR02-Y receives a valid Select Application. The session
is released after M24SR02-Y has received a valid Deselect command, if M24SR02-Y has
2
received a Kill RF session command in I
C or when the RF field became OF
F
.
2
An I
C session is taken when M24SR02-Y receives a valid Get session command or a valid
2
Kill RF session command. The session is released after M24SR02-Y has received I
C token
release sequence or after a power-off.
GPO is driven low after a delay (1) or (3) when the session is open.
GPO is released after a delay (2) or (4) when the session is released.
Figure 3. GPO configured as Session Open (GPO field = 0xX1 or 0x1X)
^ĞƐƐŝŽŶ
Z&ꢁ
^ĞƐƐŝŽŶ
Z&ꢁ^ĞƐƐŝŽŶ
/Ϯꢂꢁ^ĞƐƐŝŽŶ
;ϰͿ
;ϯͿ
;ϭͿ
;ϮͿ
‘WKꢁĂƐꢁ^ĞƐƐŝŽŶꢁKƉĞŶ
D^ϯϬϳϴϰsϮ
1. CmdEOFtoGPlow
(RF command End of frame to GPORF Session pad low)
2. CmdEOFtoGPHZ
(RF command End of frame to GPORF Session pad HZ)
3. CmdSTPtoGPlow
(I2C command stop to GPO low)
4. AnswerlbLBtoGPHZ
(I2C answer last bit of last byte to GPO HZ)
14/88
DS9985 Rev 12
M24SR02-Y
Description of signals
2.7.2
WIP Writing in Progress configuration (GPO field = 0xX2 or 0x2X)
2
When the GPO is configured as “WIP”, it goes to the Low state during an I C or RF writing
operation.
2
During an RF or I
C session, when M24SR02-Y updates a file, GPO is driven low after a
delay (1) or (3) following the beginning of the correspondent UpdateBinary command
execution.
GPO will remain low during the writing time (2) or (4), before being released.
Figure 4. GPO configured as WIP (GPO field = 0xX2 or 0x2X)
;ϭͿꢁ
Z&ꢁŽƌꢁ/Ϯꢂꢁ
ĐŚĂŶŶĞůꢁꢁ
Žƌꢁ
;ϯͿ
hƉĚĂƚĞꢁ
ĐŽŵŵĂŶĚ
ꢄŶĚꢁŽĨꢁǁƌŝƚŝŶŐꢁ
ŽƉĞƌĂƚŝŽŶ
ꢃŶLJꢁŽƚŚĞƌꢁ
ĐŽŵŵĂŶĚ
‘WKꢁĂƐꢁt/W
;ϮͿꢁŽƌꢁ;ϰͿ
D^ϯϬϳϴϲsϯ
1. CmdSTPtoGPlow
(I2C Command Stop to GPO low)
2. Writing
time duration
3. CmdEOFtoGPlow
(RF Command End of frame to GPO low)
4. Writing
time duration
DS9985 Rev 12
15/88
20
Description of signals
2
M24SR02-Y
2.7.3
I C
answer ready configuration (GPO field = 0xX3)
2
When the GPO is configured as I C answer ready, it goes to the low state when the
2
2
M24SR02-Y has finished to treat the I
C command and is ready to send the I C response.
2
2
During an I
C session, after receiving a valid I
C command, GPO pin is driven low after a
2
delay when M24SR02-Y is ready to deliver a response on the I C bus.
GPO is released when M24SR02-Y receives a new command.
2
Figure 5. GPO configured as I C answer ready (GPO field = 0xX3)
/ϸꢂꢁĐŚĂŶŶĞů
KƉĞŶꢁ
^ĞƐƐŝŽŶ
ꢃŶLJꢁ/ϸꢂꢁ
ĐŽŵŵĂŶĚ
DϮϰ^Zdždžꢁ
ƌĞƐƉŽŶƐĞ
ꢃŶLJꢁ/ϸꢂꢁ
ĐŽŵŵĂŶĚ
DϮϰ^Zdždžꢁ
ƌĞƐƉŽŶƐĞ
ꢃŶLJꢁ/ϸꢂꢁ
ĐŽŵŵĂŶĚ
DϮϰ^Zdždžꢁ
ƌĞƐƉŽŶƐĞ
‘WKꢁĂƐꢁ/ϸꢂꢁ
ĂŶƐǁĞƌꢁƌĞĂĚLJ
D^ϯϬϳϴϴsϰ
16/88
DS9985 Rev 12
M24SR02-Y
Description of signals
2.7.4
MIP NDEF Message writing in Progress configuration
(GPO field = 0x3X)
When the GPO is configured as MI
P
,
i
ts state goes to the low state when the RF host writes
the NDEF length to another value than 0x0000.
During an RF session, when M24SR02-Y changes an NDEF file and updates the NDEF
length with a value different from 0x0000, GPO is driven low after a delay (1) following the
beginning of the correspondent UpdateBinary command execution.
GPO will remain low during the writing time (2), before being released.
Figure 6. GPO configured as MIP (GPO field = 0x3X)
Z&ꢁĐŚĂŶŶĞů
hƉĚĂƚĞꢁƚŚĞꢁEꢀꢄ&ꢁ
ůĞŶŐƚŚꢁ͊сꢁϬdžϬϬϬϬ
DϮϰ^Zdždžꢁ
ƌĞƐƉŽŶƐĞ
ꢃŶLJꢁŽƚŚĞƌꢁ
ĐŽŵŵĂŶĚ
‘WKꢁĂƐꢁD/W
;ϭͿ
;ϮͿ
D^ϯϬϳϴϱsϯ
1. CmdEOFtoGPlow
(RF command End of frame to GPO low)
2. Writing
time duration
DS9985 Rev 12
17/88
20
Description of signals
M24SR02-Y
2.7.5
INT interrupt configuration (GPO field = 0xX4 or 0x4X)
2
The I
C or RF host can send a negative pulse on the GPO pad. The GPO pad goes to the
low state at the end of the command and goes to the high state at the end of the M24SR02-
Y response.
2
During an RF or I
C session, when M24SR02-Y receives a valid Interrupt command,
M24SR02-Y GPO pin is driven low after (1) or (3) for a duration of (4) in R
F
,
o
r after
responding in I2C (2). Then GPO pin is released.
Figure 7. GPO configured as INT (GPO field = 0xX4 or 0x4X)
Z&ꢁŽƌꢁ/ϸꢂꢁ
ĐŚĂŶŶĞů
;ϭͿꢁ
Žƌꢁ
;ϯͿ
;ϮͿꢁꢁ
DϮϰ^Zdždžꢁ
ƌĞƐƉŽŶƐĞ
^ĞŶĚꢁ
/ŶƚĞƌƌƵƉƚ
ꢃŶLJꢁŽƚŚĞƌꢁ
ŽƉĞƌĂƚŝŽŶ
‘WKꢁĂƐꢁ/Ed
;ϰͿꢁꢁ
D^ϯϬϳϴϳsϯ
1. CmdSTPtoGPlow
(I2C command Stop to GPO low)
2. After
NewCmdlbFB (new I2C command last bit of first byte)
or
after AnswerlbFB (I2C answer last bit of first byte)
3. CmdEOFtoGPlow
(RF command End of frame to GPO low)
4. GPO
pulse duration
18/88
DS9985 Rev 12
M24SR02-Y
Description of signals
2.7.6
State control configuration (GPO field = 0xX5 or 0x5X)
2
When the GPO is configured as State control, the I
C or RF host can control the state of the
GPO by sending a dedicated command.
2
During an RF or I
C session, the M24SR02-Y can control the GPO pin. After receiving a
valid Set GPO command, GPO pin is driven low after a delay (1) or (3). GPO will be
released after a valid Reset command or after a power-off or upon closing the RF session.
Figure 8. GPO configured as State control (GPO field = 0xX5 or 0x5X)
5)ꢄRUꢄ,ð&ꢄ
FKDQQHO
ꢎꢂꢏꢄ
RUꢄ
ꢎꢀꢏ
ꢎꢁꢏꢄ
RUꢄ
ꢎꢆꢏ
5HVHWꢄ*32ꢄ
FRPPDQGꢄꢄ
$QꢄRWKHUꢄ
FRPPDQG
6HWꢄ*32ꢄ
FRPPDQG
*32ꢄDVꢄ
6WDWH&RQWURO
06ꢀꢊꢈꢃꢍ9ꢆ
1. CmdSTPtoGPlow
(I2C Set GPO command Stop to GPO low)
2. CmdSTPtoGPHZ
(I2C Reset GPO command Stop to GPO HZ)
3. CmdEOFtoGPlow
(RF Set GPO command End of frame to GPO low)
4. CmdEOFtoGPHZ
(RF Reset GPO command End of frame to GPO HZ)
DS9985 Rev 12
19/88
20
Description of signals
M24SR02-Y
2.7.7
RF busy configuration (GPO field = 0x6X)
When the GPO is configured as RF busy, the GPO goes to the low state when the
M24SR02-Y is processing an RF command or when an RF session is ongoing.
When an RF field is present, GPO is driven low after a delay (1) when M24SR02-Y detects
the first command. If the RF session is ongoing and M24SR02-Y receives a not-supported
command, GPO remains low. It will be released only at the end of the RF session, after (2).
Figure 9. GPO configured as RF busy (GPO field = 0x6X)
Z&ꢁĐŚĂŶŶĞů
;ϭͿ
;ϮͿ
;ϭͿ
;ϮͿ
Z&ꢁ
ĐŽŵŵĂŶĚ
^ĞŶƐZĞƋꢁΘꢁ
^ĞŶƐZĞƐ
Z&ꢁĐŽŵŵĂŶĚꢁ
ŶŽƚꢁƐƵƉƉŽƌƚĞĚꢁꢁꢁꢁ
^;ꢀꢄ^Ϳ
‘WKꢁĂƐꢁZ&ꢁďƵƐLJ
D^ϯϬϳϵϬsϯ
1. CmdSOFtoGPlow
(RF command Start of frame to GPO low)
2. CmdEOFtoGPHZ
(RF command End of frame to GPO HZ)
20/88
DS9985 Rev 12
M24SR02-Y
M24SR02-Y memory management
3
M24SR02-Y memory management
3.1
Memory structure
The M24SR02-Y supports the NDEF tag application as defined in the NFC Forum Type 4
T
a
g. The M24SR02-Y is composed of three files:
•
•
•
a CC (capability container) file
an NDEF file
a System file: this is an ST-proprietary file
The System file contains information on the configuration of the M24SR02-Y device. The
CC file gives information about the M24SR02-Y itself and the NDEF file. The NDEF file
contains the User data.
3.1.1
File identifier
The file identifier is the value used in the Select command to select a file.
Table 3. File identifier
File identifier
0xE101
Meaning
System file
CC file
0xE103
0x0001
NDEF file
3.1.2
CC file layout
The CC file gives information about the M24SR02-Y and the NDEF file. This is a read-only
file for the RF or I²C host and cannot be modified by issuing a write command.
The T field, Read Access and Write Access fields can be changed by the RF or I²C host by
DS9985 Rev 12
21/88
29
M24SR02-Y memory management
File offset
M24SR02-Y
Comments
Table 4. CC file layout for 1 NDEF file
Meaning Value
0x0000
0x0002
0x0003
0x0005
0x0007
0x0008
0x0009
Number of bytes of CC file
0x000F
15 bytes
Mapping version
(1)
0x20 or 0x10
0x00F6
V 2.0 or V 1.0
246 bytes
246 bytes
T field
Maximum number of bytes that can be read
Maximum number of bytes that can be written
0x00F6
0x04
(2)
0x06
L field
0x0001
FileID
NDEF file control TLV
0x0100
Maximum NDEF
file size
0x000B
0x000D
0x000E
0x00
(2)
0x00
(2)
Read access
Write access
1. According
to the reader.
2. Delivery
state.
3.1.3
NDEF file layout
The NDEF file contains the NDEF message, which contains the user data. The RF host or
the I²C host can read and write data inside the file. The first two bytes (named NDEF
message length) define the size of the NDEF message. The NDEF message length must be
managed by the application and the M24SR02-Y device does not check if its value is
relevant vs. the data written by the RF or I²C host. The M24SR02-Y device uses the NDEF
message length, e. g. the standard read can be processed only inside the NDEF message;
otherwise, the M24SR02-Y device returns an error code. For more details about the read
22/88
DS9985 Rev 12
M24SR02-Y
M24SR02-Y memory management
Table 5. NDEF file layout
Byte 0
Byte 1
NDEF message length
File offset
Byte 2
Byte 3
0x0000
0x0004
…
User data
User data
User data
User data
User data
User data
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
0x00FC
User data
3.1.4
System file layout
fields.
Table 6. Field list
File
offset
Number
of bytes
Read
access
Write
access
Field name
Delivery state
(1)
0x0000 Length
system file
0x0002 I²C
protect
0x0003 I²C
watchdog
0x0004 GPO
2
1
1
1
1
1
1
7
2
1
I²C or RF
I²C or RF
I²C or RF
I²C or RF
I²C or RF
I²C or RF
I²C or RF
I²C or RF
I²C or RF
I²C or RF
–
0x0012
I²C
(2)
I²C
(2)
I²C
(2)
I²C
(2)
I²C
(2)
none
none
none
none
0x01
0x00
0x11
0x0005 ST
reserved
0x0006 RF
enable
0x0007 NDEF
file number (RFU)
0x0008 UID
0x00
0x xxxx xxx1
(3)
0x00
0x0282 xx xx xx xx xx
(4)
0x000F Memory
size
0x0011 Product
code
0x00FF
0x82
1. The
delivery state for all passwords is 0x00000000000000000000000000000000.
2. The
access is granted when the field I²C protect is set to the state Unprotected or when the right I²C
4. x
values are defined by ST to insure UID unicity.
DS9985 Rev 12
23/88
29
M24SR02-Y memory management
File offset
M24SR02-Y
2
Table 7. Details about I C watchdog
b7- b0
The I
2
C watchdog ensures that the I2C host will not keep the session open while there
is no more activity on the I
2
C bus (between the stop bit of the previous transaction and
the start bit of the next one).
– b7-b3: RFU
– b2-b0
(1)
:
000: watchdog
disabled
001: N
= 1
→
30 ms
010: N
= 2
→
60 ms
011: N
= 4
→
120 ms
100: N
= 8
→
240 ms
101: N
= 16
→
480 ms
110: N
= 32
→
960 ms
111: N
= 64
→
1920 ms
0x0003
1. If
b2-b0 are programmed to a non null value (N), the watchdog is enabled and starts counting for the
indicated (approximate) duration, before releasing the I
2
C session.
Table 8. Details about the GPO field
File offset
0x0004
RFU
b7
b6-b4
b3
b2-b0
When an RF session is open:
0b000: High impedance
0b001: Session opened
0b010: WIP
0b011: MIP
0b100: Interrupt
0b101: State control
0b110: RF busy
0b111: RFU
RFU
When an I²C session is open:
0b000: High impedance
0b001: Session opened
0b010: WIP
0b011: I²C answer ready
0b100: Interrupt
0b101: State control
0b110: RFU
0b111: RFU
24/88
DS9985 Rev 12
M24SR02-Y
M24SR02-Y memory management
Table 9. Details about the RF session field
b7 b6-b4
File offset
0x0004
b3-b0
RFU
When an RF session is open:
0b001: Session opened
RFU
Table 10. Details about the ST reserved field
File offset
b7-b0
0x0005
0x00
Table 11. Details about the RF enable field
b7 b6-b4
b3 b2-b1
File offset
0x0006
b0
0: the RF field is off
(1)
1: the RF field is on
(1)
RFU
0: the RF disable pad is at low state
(1)
1: the RF disable pad is at high state
(1)
RFU
0: the M24SR02-Y does not decode the command received from the RF interface
1: the M24SR02-Y decodes the command received from the RF interface
1. this
field is written by the M24SR02-Y.
3.2
Read and write access rights to the memory
An NDEF file can be locked for read or write accesses. It is also protected by a 128-bit
password that the host must present before accessing the NDEF file. There are two 128-bit
passwords, one for the read access and the other one for the write access.
An NDEF file can be permanently locked for read or write accesses. Thus, the host cannot
access the NDEF file.
The read password must be sent to the M24SR02-Y device before reading a read-locked
NDEF file.
DS9985 Rev 12
25/88
29
M24SR02-Y memory management
M24SR02-Y
The write password must be present on the M24SR02-Y device before writing a write-
locked NDEF file. The write password must be sent to change the read or write access. The
read or write access right is defined for the NDEF file.
3.2.1
State of the Read and Write access rights
Two bytes in the CC file are used to define the Read and Write access rights to the NDEF
Table 12. Read access right
Value
Meaning
0x00
0x80
0xFE
Read access without any security
Locked
(1)
Read not authorized
1. The
read password must be sent before reading in the NDEF file.
Table 13. Write access right
Value
Meaning
0x00
0x80
0xFF
Write access without any security
Locked
(1)
Write not authorized
1. The
write password must be sent before writing in the NDEF file.
The state 0xFF and 0xFE cannot be changed by using the Read or Write passwords.
26/88
DS9985 Rev 12
M24SR02-Y
M24SR02-Y memory management
3.2.2
Changing the read access right to NDEF files
Figure 10. Changing the read access right to an NDEF file
ꢊ[ꢊꢊ
/RFNꢄWKHꢄ1′()ꢄILOHꢄ
ꢎꢂꢏ
3HUPDQHQWOꢄORFNꢄWKHꢄ1′()ꢄILOHꢄ
ꢎꢀꢏ
8QORFNꢄWKHꢄ1′()ꢄILOHꢄ
ꢎꢁꢏ
3HUPDQHQWOꢄORFNꢄWKHꢄ1′()ꢄILOHꢄ
ꢎꢀꢏ
ꢊ[ꢃꢊꢄ
ꢎꢆꢏ
ꢊ[)(ꢄ
ꢎꢆꢏ
3HUPDQHQWOꢄXQORFNꢄWKHꢄ1′()ꢄILOH
06Yꢆꢃꢊꢀꢀ9ꢂ
3. See
the procedure to permanently lock the read access (
Section 8.6: Reaching the read-only state for an
4. Proprietary
state, not defined by NFC Forum Type 4 Tag. For NFC Forum compatible tags, the only
possible value of the read access rights are 0x00 (no restrictions on reads).
DS9985 Rev 12
27/88
29
M24SR02-Y memory management
M24SR02-Y
3.2.3
Changing the write access right to NDEF files
The state diagram on
Figure 1
shows how to change the write access right to an NDEF file.
Figure 11. Changing the write access right to an NDEF file
ꢊ[ꢊꢊ
/RFNꢄWKHꢄ1′()ꢄILOHꢄ
ꢎꢂꢏ
3HUPDQHQWOꢄORFNꢄWKHꢄ1′()ꢄILOHꢄ
ꢎꢀꢏ
8QORFNꢄWKHꢄ1′()ꢄILOHꢄ
ꢎꢁꢏ
3HUPDQHQWOꢄORFNꢄWKHꢄ1′()ꢄILOHꢄ
ꢎꢀꢏ
ꢊ[ꢃꢊꢄ
ꢎꢆꢏ
ꢊ[))
3HUPDQHQWOꢄXQORFNꢄWKHꢄ1′()ꢄILOH
06Yꢆꢃꢊꢀꢆ9ꢂ
1. See
the procedure to lock the write access.
2. See
the procedure to unlock the write access.
3. See
the procedure to permanently lock the write access (
Section 8.6: Reaching the read-only state for an
4. Proprietary
state, not defined by NFC Forum Type 4 Tag. For NFC Forum compatible tags, it is mandatory
that the write access rights are set to either 0x00 (no restrictions on writes) or to 0xFF (permanently
locked). 0x80 might not be fully decoded by some smart phones.
3.3
3.4
Access right life time
The access right life time is validated while the NDEF file is selected or until the end of the
RF or I²C session. Once the read or write access right is granted, the host can send one or
more ReadBinary or UpdateBinary commands.
At the end of a session or when the host selects another file, the read and write access
rights are initialized.
NDEF file passwords
The NDEF file passwords protect the read or write access from an RF or I²C interface
from/to an NDEF file.
Two NDEF file passwords are available for each NDEF file:
•
•
Read password
Write password
The length of a password is 128 bits (16 bytes).
28/88
DS9985 Rev 12
M24SR02-Y
M24SR02-Y memory management
3.5
I
2
C password
The I²C password can be sent only by the I²C host. It activates the SuperUser rights. The I²C
host with the SuperUser rights can:
•
access the NDEF file regardless of the right access and without sending the NDEF file
passwords
•
change the access rights regardless of the current state.
The length of the I²C password is 128 bits (16 bytes).
3.5.1
I²C password and I²C protect field of the System file
The I²C protect field in the system file can be set to:
•
•
0x00: the I²C host has the SuperUser right access without sending the I²C password
0x01: the I²C host has the SuperUser right access after sending the I²C password.
DS9985 Rev 12
29/88
29
Communication mechanism
M24SR02-Y
4
Communication mechanism
2
This section describes the principle of communication between an RF or an I
C host and the
M24SR02-Y device.
4.1
Master and slave
2
The M24SR02-Y acts as a slave device on either the I C-bus or the RF channel and
2
therefore waits for a command from the I
C master or the RF host before sending its
response.
The RF host must generate the RF field and the RF commands.
2
2
The I
C host must supply the M24SR02-Y through the V
pin and must generate the I C
CC
clock on the SCL pad.
4.2
M24SR02-Y session mechanism
2
The M24SR02-Y is a dynamic NFC/RFID tag that can be accessed either from the RF or I
C
interface. The M24SR02-Y implements a token system. This token has two possible values,
2
2
RF or I C. When the token exists and is assigned to one interface (RF or I C), the
M24SR02-Y cannot communicate with the other host.
4.2.1
4.2.2
RF token
The token is given to the RF interface once the anticollision is done. The release condition
can be either an RF field cut-off, or the reception of the command deselect, or when the I²C
host sends the KillRFsession.
2
I C
token
2
2
The token is given to the I
C interface when the I
C host has sent the correct device Select.
The release condition can be either a power down condition on V
pin or the reception of a
CC
2
2
I C token release sequence from the I C host, after which M24SR02-Y goes in Standby
power mode.
30/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
5
I²C and RF command sets
The command sets of the M24SR02-Y can be split in different command families. Most
commands are common between the RF and the I²C interface. Some commands are
specific to the RF interface and some others are specific to the I²C interface. This section
describes the M24SR02-Y command sets that can be issued by the RF or the I²C host.
There are three command families:
•
•
•
the NFC Forum Type 4
T
a
g command set
the ISO/IEC 7816-4 command set
the proprietary command set
The NFC Forum Type 4
T
a
g command set and the ISO/IEC 7816-4 command set use the
Two other command formats exist:
•
•
This section gives a brief description of the RF and I²C host common commands. The
format of these command sets is the I-Block format.
Table 14. RF and I²C command sets
Family
command set
Class Instruction
Command name
Brief description
byte
code
NDEF
T
a
g Application
Select
NDEF
T
a
g Application Select
0x00
0xA4
CC select
0x00
0x00
0x00
0x00
0xA4
0xA4
0xA4
0xB0
Select the CC file
NDEF select
System select
ReadBinary
Select the NDEF file
Select the system file
Read data from file
NFC Forum
Type 4
T
a
g
Write or erase data to a
NDEF file
UpdateBinary
Verify
0x00
0x00
0x00
0xD6
0x20
Checks the right access of
a NDEF file or sends a
password
Change a Read or write
password
ChangeReferenceData
0x24
0x28
0x26
ISO/IEC 7816-4
Activate the password
security
EnableVerificationRequirement 0x00
DisableVerificationRequirement 0x00
Disable the password
security
Enable the Read only or
Write only security state
EnablePermanentState
ExtendedReadBinary
0xA2
0xA2
0x28
0xB0
ST proprietary
Read data from file
DS9985 Rev 12
31/88
78
I²C and RF command sets
M24SR02-Y
5.1
Structure of the command sets
The exchange of data between the RF or the I²C host and the M24SR02-Y uses three kinds
of data formats, called blocks:
•
•
•
I-Block: to exchange the command and the response
R-Block: to exchange positive or negative acknowledgment
S-Block: to use either the Deselect command or the Frame waiting extension (WTX)
command or response.
Note:
Max WTX value = 0x0B
This section describes the structure of the I-Block, R-block and S-Block. This format is used
for the application command set.
5.2
I-Block format
The I-Block is used to exchange data between the RF or the I²C host and the M24SR02-Y.
Table 15. I-Block format
SoD
Payload
0
EoD
CRC
Name
PCB
DID
Length
1 byte
1 byte
1 to 251 bytes
2 bytes
PCB field
DID field (optional)
RF or I²C host to M24SR02-Y: C-APDU
M24SR02-Y to RF or I²C host: R-APDU
2 CRC bytes
32/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
Table 16. PCB field of the I-Block format
b7-b6
0b00
b5
0
b4
0
b3
X
b2
0
b1
1
b0
X
–
I-Block
RFU
Must be set to 0
DID field, if bit is set
Must be set to 0
Must be set to 1
Block number
When the RF or I²C host sends a command to the M24SR02-Y the format of the payload is
the C-APDU.
When the M24SR02-Y sends a command to the RF or I²C host, the format of the payload is
the R-APDU.
5.2.1
C-APDU: payload format of a command
The C-APDU format is used by the RF or the I²C host to send a command to the M24SR02-
Table 17. C-APDU format
Payload field
Name
CLA
INS
P1
P2
LC
Data
Le
Length
1 byte
1 byte
1 byte
1 byte
1 byte
Lc byte
1 byte
Class byte
0x00: standard command
0xA2: ST command
Instruction byte
Parameter Byte 1
Parameter Byte 2
Number of bytes of the Data field
Data bytes
Number of bytes to be read in the M24SR02-Y memory
5.2.2
R-APDU: payload format of a response
The M24SR02-Y uses the I-Block format to reply to a command that used the I-Block
DS9985 Rev 12
33/88
78
I²C and RF command sets
M24SR02-Y
Table 18. R-APDU format
Payload field
Name
Data (optional)
Le byte
SW1
SW2
1 byte
Length
1 byte
Data
Status byte 1
Status byte 2
5.3
R-Block format
The R-Block is used to convey positive or negative acknowledgment between the RF or I²C
host and the M24SR02-Y.
Table 19. R-Block format
PCB
CRC
R(ACK) without the DID field: 0xA2 or 0xA3
R(ACK) with the DID field: 0xAA or 0xAB
R(NAK) without the DID field: 0xB2 0xB3
R(NAK) with the DID field: 0xBA 0xBB
2 CRC bytes
There are two kinds of R-Blocks:
•
•
R(ACK): the acknowledgment block sent by the RF or I²C host or by the M24SR02-Y.
R(
NAK
): the non-acknowledgment block sent by the RF or I²C host or by the
M24SR02-Y.
34/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
Table 20. R-Block detailed format
b7-b6
0b10
b5
1
b4
X
b3
X
b2
0
b1
1
b0
X
–
R-Block
RFU
1: NAK
0: ACK
0: DID field is not present
1: DID field is present
Must be set to 0
Must be set to 1
Block number
5.4
S-Block format
The S-Block is used to exchange control information between a reader and a contactless
tag.
Table 21. S-Block format
SoD
EoD
CRC
NFC frame
Length
PCB
DID
Payload
1 byte
1 byte
1 to 255 bytes
2 bytes
0xC2: for S(DES) when the DID field is not present
0xCA: for S(DES) when the DID field is present
0xF2: for S(WTX) when the DID field is not present
0xFA: for S(WTX) when the DID field is present
DID field (optional)
WTX field
(1)
2 CRC bytes
There are two requests using the S-Block format:
•
•
•
S(DES): the deselect command
S(DES) is only applicable to RF
S(WTX): the Waiting frame extension command or response.
2
A Waiting time extension request occurs, in RF or I
C, when the operating time needed
by M24SRxx is greater than 9.6 ms.
The WTX field indicates the increase time factor to be used in this command execution
(FDTtemp = WTX * 9.6 ms). The max WTX value is equal to 0x0B.
DS9985 Rev 12
35/88
78
I²C and RF command sets
M24SR02-Y
Table 22. S-Block detailed format
b7-b6
0b11
b5-b4
X
b3
X
b2
0
b1
1
b0
0
S-Block
0b00: Deselect
0b11: WTX
0: DID field is not present
1: DID field is present
–
RFU
RFU
Note:
After receiving the deselect command, the session is released and M24SR02-Y enters the
Standby power mode. In I
C, the session is released after executing the I2C token release
2
sequence.
In response to a RATS command, M24SR02-Y returns FWI parameter (default frame waiting
time used); when M24SR02-Y needs more time for a command execution, it requests a
frame waiting time extension by responding 0xF2 0xWTX (request waiting time = FWI *
WTX). If the reader accepts M24SR02-Y request, it acknowledges by sending the command
0xF2 0xWTX. The frame waiting time becomes FWI * WTX for the current command only.
5.5
CRC of the I
2
C and RF frame
The two CRC bytes check the data transmission between the RF host or I²C host and the
M24SR02-Y. For the RF frame, the CRC is computed on all the data bits in the frame,
excluding parity bits, SOF and EO
F
,
a
nd the CRC itself.
For the I²C frames, the CRC is computed on all data bits of the frame excluding Device
select and the CRC itself.
The CRC is as defined in ISO/IEC 13239. The initial register content must be 0x6363 and
the register content must not be inverted after calculation.
36/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
5.6
NFC Forum Type 4 Tag protocol
5.6.1
Command set
With the NFC Forum Type 4
T
a
g protocol, the commands are common to RF and I²C.
Table 23. Command set overview
Command name
Brief description
Select the NDEF
T
a
g Application
NDEF
T
a
g Application Select
Capability Container Select
NDEF Select
Select the capability container (CC) file using the Select command
Select the NDEF file
System File Select
ReadBinary
Select the system file
Read data from a file
UpdateBinary
Write new data to a file
5.6.2
Status and error codes
This section lists the status and the error code of the M24SR02-Y.
Table 24. Status code of the M24SR02-Y
–
SW1
SW2
Comment
Value
0x90
0x00
Command completed successfully
Table 25. Error codes of the M24SR02-Y
–
SW1
SW2
Comment
Length
1 byte
0x62
0x62
0x63
0x63
0x65
0x67
0x69
0x69
0x69
0x6A
0x6A
0x6A
0x6A
1 byte
0x80
0x82
0x00
0xCX
0x81
0x00
0x81
0x82
0x84
0x80
0x82
0x84
0x86
–
Value
Value
Value
Value
Value
Value
Value
Value
Value
Value
Value
Value
Value
File overflow (Le error)
End of file or record reached before reading Le bytes
Password is required
Password is incorrect, X further retries allowed (X = 0, 1, 2)
Unsuccessful updating
Wrong length
Command is incompatible with the file structure
Security status not satisfied
Reference data not usable
Incorrect parameters Le or Lc
File or application not found
File overflow (Lc error)
Incorrect P1 or P2 values
DS9985 Rev 12
37/88
78
I²C and RF command sets
M24SR02-Y
Table 25. Error codes of the M24SR02-Y (continued)
–
SW1
SW2
Comment
Value
Value
0x6D
0x6E
0x00
0x00
INS field not supported
Class not supported
5.6.3
NDEF Tag Application Select command
The RF or the I²C host must send this command to activate the NDEF
T
a
g Application.
To
a
ctivate the NDEF
T
a
g Application, the RF host sends the Select command (see
To
a
ctivate the NDEF
T
a
g Application, the I²C host sends the Select command (see
(called NDEF
T
a
g Application Select).
Table 26. C-APDU of the NDEF Tag Application Select command
Name
Value
Class byte
CLA
INS
P1
P2
Lc
Data
Le
0xD27600
00850101
0x00
0xA4
0x04
0x00
0x07
0x00
Select instruction code
P1 field
P2 field
Number of bytes of data
Application ID
Le field
Table 27. R-APDU of the NDEF Tag Application Select command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
–
–
–
–
1 byte
0x90
0x6A
0x6D
1 byte
0x00
0x82
0x00
–
Command completed
NDEF
T
a
g Application not found
Class not supported
5.6.4
Capability Container Select command
The RF or I²C host uses the Capability Container Select procedure to select the capability
container (CC) file.
38/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
The CC file is selected when this command returns “command completed” in the R-APDU.
Container Select).
Table 28. C-APDU of the Capability Container Select command
Name
Value
Class byte
CLA
INS
P1
P2
Lc
Data
Le
0x00
0xA4
0x00
0x0C
0x02
0xE103
–
Select instruction code
P1 field
P2 field
Number of bytes of data
CC file ID
–
Table 29. R-APDU of the Capability Container Select command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
–
–
–
–
1 byte
0x90
0x6A
0x6D
1 byte
0x00
0x82
0x00
–
Command completed
File or application not found
Class not supported
5.6.5
NDEF Select command
The RF or I²C host uses the NDEF Select command to select the NDEF file.
The NDEF file is selected when this command returns “command completed” in the
(called NDEF Select).
In case of a password is required to access the NDEF file, the NDEF Select command will
disable any previously granted access rights to this file. The Verify command might be
required to access the file.
DS9985 Rev 12
39/88
78
I²C and RF command sets
M24SR02-Y
Table 30. C-APDU of the NDEF Select command
Name
CLA
INS
P1
P2
Lc
Data
Le
Value
0x00
0xA4
0x00
0x0C
0x02
0x000X
–
Class byte
Select instruction code
P1 field
P2 field
Number of bytes of data
0x0001: first NDEF file
–
Table 31. R-APDU of the NDEF Select command
–
Data
SW1
1 byte
SW2
1 byte
Comment
Length
Value
Value
–
–
–
–
0x90
0x6A
0x00
0x82
Command completed
File or application not found
5.6.6
System File Select command
The RF or I²C host uses this command to select the system file.
The System file is selected when this command returns “command completed” in the R-
APDU.
Select).
Table 32. C-APDU of the System File Select command
Name
CLA
INS
P1
P2
Lc
Data
Le
0x00
0xA4
0x00
0x0C
0x02
0xE101
–
Class byte
Select instruction code
P1 field
P2 field
Number of bytes of data
System file ID
–
40/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
Table 33. R-APDU of the System File Select command
–
Data
SW1
SW2
Comment
Length
Value
Value
–
–
–
1 byte
0x90
1 byte
0x00
0x82
–
Command completed
0x6A
Capability container not found, no data is returned
5.6.7
ReadBinary command
On receiving the ReadBinary command, the M24SR02-Y reads the requested memory field
and sends back its value in the R-APDU response.
Before sending a ReadBinary command, a file must be selected by using a Select
command.
The Response of the ReadBinary command is successful when the data to be read is within
(a)
the selected file
; in other words, when the sum of P1-P2 and Le fields is equal to or lower
than the selected file length.
Table 34. C-APDU of the ReadBinary command
Name
CLA
INS
P1 and P2
Lc
Data
Le
–
0x00
0xB0
2 bytes
–
–
1 byte
Class byte
Read instruction code
Offset in the file selected
–
–
Number of bytes to read between
0x01
≤
Le
≤
max(Selected File length, 0xF6)
Table 35. R-APDU of the ReadBinary command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
–
1 byte
0x90
0x67
0x69
1 byte
–
Content read
Don’t care
(1)
Command completed
–
–
0x00
0x82
Wrong length
Security status not satisfied
DS9985 Rev 12
41/88
78
I²C and RF command sets
M24SR02-Y
Table 35. R-APDU of the ReadBinary command (continued)
–
Data
SW1
SW2
Comment
Value
Value
–
–
0x6A
0x6E
0x82
0x00
File or application not found
Class not supported
1. For
more information, please contact your local ST support.
5.6.8
UpdateBinary command
On receiving the UpdateBinary command, the M24SR02-Y writes the data field into the
selected file and sends back a status in the R-APDU response. If needed, the device will
Before sending an UpdateBinary command, a file must be selected by issuing a Select
command.
Table 36. C-APDU of the UpdateBinary command
Name
CLA
INS
P1 and P2
Lc
Data
Le
–
0x00
0xD6
2 bytes
1 byte
Lc bytes
–
Class byte
Write instruction code
Offset in the file selected
Number of bytes of data (0x01
≤
Lc
≤
0xF6)
Data to write in the M24SR02-Y memory
–
Table 37. R-APDU of the UpdateBinary command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
Value
Value
Value
–
–
–
–
–
–
–
1 byte
0x90
0x65
0x67
0x69
0x6A
0x6E
1 byte
0x00
0x81
0x00
0x82
0x82
0x00
–
Command completed
Unsuccessful updating
Wrong length
Security status not satisfied
File or application not found
Class not supported
Note:
Chaining is not supported on “UpdateBinay” command. For further return codes and
42/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
5.7
ISO/IEC 7816-4 commands
The ISO/IEC 7816-4 command set offers some extended features such as the protection of
the NDEF file. This command set is used to manage the right access of the NDEF file.
5.7.1
Verify command
The Verify command has two functions:
1. check
if a password is required to access to the NDEF file (the LC field = 0x00)
2. check
that the password embedded in the Verify command enables the access to the
memory (the Lc field = 0x10 and the password is present).
When the Lc field is equal to 0x00, the verify command returns a success code (0x90 00)
provided that the access to the NDEF file does not require a password. When the access to
the NDEF file is protected, the response to the Verify command returns an error code
(0x63 00).
When the Lc field equals 0x10, on receiving the Verify command, the M24SR02-Y
compares the requested password with the data contained in the request and reports
whether the operation has been successful in the response.
Before sending this command, an NDEF file must be selected by issuing the NDEF Select
command. Thus, this command checks the right access condition of the last NDEF file
selected.
After a successful command, an access is granted for the whole NDEF file.
Table 38. Verify command format
Name
CLA
INS
P1 and P2
Lc
Data
Le
–
0x00
0x20
2 bytes
1 byte
Lc bytes
–
Class byte
Instruction code
Password identification
0x0001: Read NDEF password transmit
0x0002: Write NDEF password transmit
0x0003: I²C password transmit
(1)
Other: RFU
0x00: the password is not present
0x10: the password is present in the data field
Password
–
1. This
code can only be issued by the I²C host.
DS9985 Rev 12
43/88
78
I²C and RF command sets
M24SR02-Y
Table 39. R-APDU of the Verify command
SW1 SW2
Comment
1 byte
1 byte
–
Data
Length
Value
–
–
–
0x90
0x69
0x00
0x85
Command completed, the password is correct
The conditions of use are not satisfied (e.g. no
NDEF file was selected)
Value
–
Value
Value
Value
Value
–
–
–
–
0x69
0x69
0x6A
0x63
0x81
0x82
0x80
0x00
Cmd incompatible with file structure
Security status not satisfied
Incorrect parameter in cmd data field
A password is required
The password transmitted is incorrect and X
encodes the number of further allowed retries.
Value
Value
–
–
0x63
0x6E
0xCX
(1)
0x00
Class not supported
1. At
each session, the RF host can check a password 3 times.
5.7.2
Change Reference Data command
The Change Reference Data command replaces the read or write password related to the
NDEF files previously selected. It can be performed only if the security status satisfies the
security attributes for this command.
Before sending this command, the verify command with the correct NDEF write password
must be issued. Thus, this command changes the reference data of the NDEF file.
Table 40. Change reference data command format
Name
CLA
INS
P1 and P2
Lc
Data
Le
–
0x00
0x24
2 bytes
1 byte
Lc bytes
–
Class byte
Instruction code
Password identification
0x0001: Read password transmit
0x0002: Write password transmit
0x0003: I²C password transmit
(1)
Other: RFU
0x10: the password is present in the data field
NDEF file or I²C Password
–
1. This
code can only be issued by the I²C host.
44/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
Table 41. R-APDU of the Change Reference Data command
–
Data
SW1
SW2
Comment
Length
0
1 byte
1 byte
–
Command completed, the access right has
been changed
Value
–
0x90
0x00
Value
Value
Value
Value
Value
Value
Value
–
–
–
–
–
–
–
0x69
0x65
0x69
0x6A
0x6A
0x6A
0x6E
0x81
0x81
0x82
0x80
0x82
0x86
0x00
Command is incompatible with the file structure
Unsuccessful updating
Security status not satisfied
CC file or System file selected
File or application not found
Incorrect P1 or P2 values
Class not supported
5.7.3
Enable Verification Requirement command
The Enable Verification Requirement command activates the protection by password of the
NDEF file. When this command is successful, the read or write access to the NDEF file is
protected by a 128-bit password. It can be performed only if the security status satisfies the
security attributes for this command.
This command can update the right access of the NDEF file by writing into the EEPROM. In
this case, the response timing will be around 5 ms.
Before sending this command, the verify command with the correct NDEF write password
must be issued. Thus, this command changes the access right of the NDEF file.
Table 42. Enable Verification Requirement command format
Name
CLA
INS
P1 and P2
Lc
Data
Le
–
0x00
0x28
2 bytes
–
–
–
Class byte
Instruction code
New security attributes
0x0001: Enable the read protection of the NDEF file
0x0002: Enable the write protection of the NDEF file
Other: RFU
–
–
–
The last five bits identify the password sent in the Verify command.
DS9985 Rev 12
45/88
78
I²C and RF command sets
M24SR02-Y
Table 43. R-APDU of the Enable Verification Requirement command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
Value
Value
Value
0
–
–
–
–
–
–
1 byte
0x90
0x69
0x69
0x6A
0x6A
0x6A
1 byte
0x00
0x81
0x82
0x80
0x82
0x86
–
Command completed, the password is correct
Command is incompatible with the file structure
Security status not satisfied
CC file or System file selected
File or application not found
Incorrect P1 or P2 values
5.7.4
Disable Verification Requirement command
The Disable Requirement command deactivates the protection by password of the NDEF
file. When this command is successful, the read or write access to the NDEF file is granted
without security requirements. It can be performed only if the security status satisfies the
security attributes for this command.
Before sending this command, the verify command with the correct NDEF write password
must be issued. Thus, this command changes the access right of the NDEF file.
This command can update the right access of the NDEF file by writing into the EEPROM. In
this case, the response timing will be around 6 ms.
Table 44. Disable Verification Requirement command format
Name
CLA
INS
P1 and P2
Lc
Data
Le
–
0x00
0x26
2 bytes
–
–
–
Class byte
Instruction code
New security attributes
0x0001: Disable the read protection of the NDEF file
0x0002: Disable the write protection of the NDEF file
Other: RFU
–
–
–
46/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
Table 45. R-APDU of the Disable Verification Requirement command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
Value
Value
Value
Value
Value
0
–
–
–
–
–
–
–
–
1 byte
0x90
0x69
0x69
0x6A
0x6A
0x6A
0x6E
0x65
1 byte
0x00
0x81
0x82
0x80
0x82
0x86
0x00
0x81
–
Command completed, the password is correct
Command is incompatible with the file structure
Security status not satisfied
CC file or System file selected
File or application not found
Incorrect P1 or P2 values
Class not supported
Update failed
5.8
ST proprietary command set
The RF or I²C host can be issued with the command set described in this section.
5.8.1
ExtendedReadBinary command
On receiving the ExtendedReadBinary command, the M24SR02-Y reads the requested
memory field and sends back its value in the R-APDU response.
Before sending an ExtendedReadBinary command, a file must be selected by issuing an
NDEF select command.
The response of the ExtendedReadBinary command will be successful even if the data to
be read is beyond the NDEF message. The command returns an error code if the data to be
read goes beyond the end of the file.
Table 46. C-APDU of the ExtendedReadBinary command
Name
Length
ST Class byte
CLA
INS
P1 and P2
Lc
Data
Le
0xA2
0xB0
2 bytes
–
–
1 byte
Read instruction code
Offset in the file selected
–
–
–
Number of bytes to read between 0x01
≤
Le
≤
0xF6
DS9985 Rev 12
47/88
78
I²C and RF command sets
M24SR02-Y
Table 47. R-APDU of the ExtendedReadBinary command
Data SW1 SW2
Comment
Length Le
bytes 1
byte
–
1 byte
0x90
0x67
0x69
0x6A
0x6A
0x6E
–
Value
Value
Value
Value
Value
Value
Content read
Don’t care
(1)
Command completed
Wrong length
–
–
–
–
–
0x00
0x82
Security status not satisfied
File or application not found
Incorrect P1 or P2 values
Class not supported
0x82
0x86
0x00
1. For
more information, please contact your local ST support.
5.8.2
EnablePermanentState command
The command configures the NDEF file to the ReadOnly or to the WriteOnly State.
This command can update the right access to the NDEF file by writing into the EEPROM. In
this case, the response timing will be around 6 ms.
Table 48. EnablePermanentState command format
Name
Length
CLA
INS
P1 and P2
Lc
Data
Le
0xA2
0x28
2 bytes
–
–
–
Class byte
Instruction code
New security attributes
0x0001: Enable the read protection of the NDEF file
0x0002: Enable the write protection of the NDEF file
Other: RFU
–
–
–
–
Table 49. R-APDU table of the EnablePermanentState command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
–
–
–
–
1 byte
0x90
0x65
0x67
1 byte
0x00
0x81
0x00
–
Command completed
Update failed
Wrong length
48/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
Table 49. R-APDU table of the EnablePermanentState command (continued)
–
Data
SW1
SW2
Comment
Value
Value
Value
Value
Value
–
–
–
–
–
0x69
0x6A
0x6A
0x6A
0x6E
0x82
0x80
0x82
0x86
0x00
Security status not satisfied
CC file or System file selected
File or application not found
Incorrect P1 or P2 values
Class not supported
5.8.3
DisablePermanentState command
The command configures the NDEF file to the Lock state.
This command can update the right access of the NDEF file by writing into the EEPROM. In
2
this case, the response timing will be around 6 ms. This command is only valid in I
C. The
SuperUser rights must have been granted to execute the command.
Before sending this command, an NDEF file must be selected by issuing the NDEF Select
command.
Table 50. DisablePermanentState command format
Name
Length
CLA
INS
P1 and P2
Lc
Data
Le
0xA2
0x26
2 bytes
–
–
–
Class byte
Instruction code
New security attributes
0x0001: Disable the read protection of the NDEF file
0x0002: Disable the write protection of the NDEF file
Other: RFU
–
–
–
Table 51. R-APDU of the DisablePermanentState command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
Value
–
–
–
–
–
1 byte
0x90
0x65
0x67
0x69
1 byte
0x00
0x81
0x00
0x82
–
Command completed
Update failed
Wrong length
Security status not satisfied
DS9985 Rev 12
49/88
78
I²C and RF command sets
M24SR02-Y
Table 51. R-APDU of the DisablePermanentState command (continued)
–
Data
SW1
SW2
Comment
Value
Value
Value
Value
–
–
–
–
0x6A
0x6A
0x6A
0x6E
0x80
0x82
0x86
0x00
CC file or System file selected
File or application not found
Incorrect P1 or P2 values
Class not supported
5.8.4
UpdateFileType command
This command allows to modify the file type of a selected file to Proprietary file (0x05) or
NDEF file (0x04).
NFC Forum compatible tags must configure the file as NDEF file (0x04).
This command is granted only, when application and file are selected and if the file length
and access right have previously been set to 0X00h (message invalid, all access rights
granted).
This command will update the file type located in the CC file by writing into the EEPROM. In
this case, the response timing will be around 6 ms.
Table 52. UpdateFileType command format
Name
Value
Class byte
CLA
INS
P1
P2
Lc
Data
Le
0x04 or
0x05
0xA2
0xD6
0x00
0x00
0x01
–
Select instruction code
P1 field
P2 field
Number of bytes of data
File type
–
Table 53. R-APDU of the UpdateFileType command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
–
–
–
–
1 byte
0x90
0x69
0x6A
1 byte
0x00
0x82
0x80
–
Command completed
Security status not satisfied
CC file or System file selected
50/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
Table 53. R-APDU of the UpdateFileType command (continued)
–
Data
SW1
SW2
Comment
File or application not found
Incorrect P1 or P2 values
Value
Value
–
–
0x6A
0x6A
0x82
0x86
5.8.5
SendInterrupt command
On receiving the SendInterrupt command, the M24SR02-Y generates a negative pulse on
the GPO pin. It starts at the end of the command and ends at the end of the RF response.
Before sending this command, the system file must be selected by issuing the System
Select command.
Table 54. SendInterrupt command format
–
CLA
INS
P1&P2
Lc
Data
Le
Length
Value
1 byte
0xA2
1 byte
0xD6
2 bytes
0x001E
1 byte
0x00
–
–
–
–
Table 55. R-APDU of the SendInterrupt command
Data
SW1
SW2
Comment
Length
Value
Value
Value
Value
Value
–
–
–
–
–
–
1 byte
0x90
0x6A
0x6A
0x6A
0x6E
1 byte
0x00
0x80
0x82
0x86
0x00
–
The interrupt has been sent
The GPO is not configured as an interrupt mode
File or application not found
Incorrect P1 or P2 values
Class not supported
5.8.6
StateControl command
On receiving the StateControl command with reset value: data 0x00, the M24SR02-Y drives
the GPO pin low. On receiving the StateControl command with set value: data 0x01, the
M24SR02-Y releases the GPO pin, which returns to HZ.
Before sending this command, the system file must be selected by issuing the System
Select command.
DS9985 Rev 12
51/88
78
I²C and RF command sets
M24SR02-Y
Le
Table 56. StateControl command format
–
CLA
INS
P1&P2
Lc
Data
Length
1 byte
0xA2
0xA2
1 byte
0xD6
0xD6
2 bytes
0x001F
0x001F
1 byte
0x01
0x01
–
–
–
–
Reset value
Set value
0x00
0x01
Table 57. R-APDU of the StateControl command
–
Data
SW1
SW2
Comment
Length
Value
Value
Value
Value
Value
–
–
–
–
–
–
1 byte
0x90
0x6A
0x6A
0x6A
0x6E
1 byte
0x00
0x80
0x82
0x86
0x00
–
The set or reset has been sent
The GPO is not configured in StateControl mode
File or application not found
Incorrect P1 or P2 values
Class not supported
5.9
Specific RF command set
This section describes the command set that can be issued only by the RF host.
5.9.1
Anticollision command set
commands is described in the NFC Forum Digital Protocol specification.
Table 58. Commands issues by the RF host
Family command set
Command name
Instruction code
0x52
(1)
ALL_REQ
SENS_REQ
SDD_REQ
SEL_REQ
SLP_REQ
NFC-A technology
1. Coded
on 7 bits.
0x93 or 0x95 or 0x97
0x93 or 0x95 or 0x97
0x50
5.9.2
RATS command and ATS response
RATS command and ATS response are used for NFC Forum Type 4A
T
a
g Platform Device
Activation (as defined in NFC Forum Digital Protocol specification).
process.
52/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
Table 59. RATS command
Param
Name
Byte field
Bit field
INS
0xE0
–
CRC
1 byte
b7-b4
2 bytes
b3-b0
–
Instruction code
FSDI
DID (0
≤
DID
≤
14)
2 CRC bytes
The FSDI field codes the FSD that defines the maximum size that an RF or I²C host is able
Table 60. Conversion from FDSI to FSD
0x9h-
FSDI
0x0
0x1
0x2
0x3
0x4
0x5
0x6
0x7
0x8
0xF
0xE
FSD
16
24
32
40
48
64
96
128
256
RFU
256
The DID field defines the value of the addressed M24SR02-Y.
Table 61. ATS response
Name
Byte field
Bit field
TL
0x05
–
T0
0x78
–
TA(1)
1 byte
–
TB(1)
TC(1)
CRC
2 bytes
–
1 byte
0x02
–
b8-b5
b4-b1
Length of the ATS
response
FSCI = 256 bytes
The maximum ascending data rate is 106 kbps
The maximum descending data rate is 106 kbps
FWI field (9.6 ms when TB = 0x50)
SFGI field (302 µs when TB = 0x50)
The DID is supported
2 CRC bytes
The FSCI codes the FSC, which stands for the maximum frame size that the M24SR02-Y is
able to receive. The M24SR02-Y is able to receive up to 256 bytes of command. If the RF or
I²C host sends a command with more than 256 bytes, the M24SR02-Y will not be able to
treat the command and will not reply.
The FWI, which stands for the frame waiting time integer codes the FW
T
.
T
his time
corresponds to the maximum duration while an RF or I²C host must wait before sending the
next command.
DS9985 Rev 12
53/88
78
I²C and RF command sets
M24SR02-Y
The SFGI, which stands for the start-up frame guard time is the minimum time that the
reader must wait after receiving the response of the M24SR02-Y.
5.9.3
PPS command and response
PPS (protocol and parameter selection) command and response are defined in ISO/IEC
14443-4, in the protocol activation of PICC Type A.
The PPS command makes possible to change the data rates of the ascending (RF host to
M24SR02-Y) and descending (M24SR02-Y to RF host) data rates.
Table 62. PPS command
Name
Byte field
Bit field
INS
PPS0
0x11
–
PPS1
1 byte
b3-b2
CRC
2 bytes
–
–
0xDX
b7-b4
b3-b0
0b0000
b1-b0
Instruction code
DID
INS
–
PPS1 is present
RFU
PPS1 Descending
data rate
Ascending data rate
–
2 CRC bytes
Table 63. Ascending and descending data rate coding
Value
0b00
0b01
0b10
0b11
Data rate
106 kbps
RFU
RFU
RFU
When the M24SR02-Y is able to change both data rates, it returns the following response.
The data rate of this response is 106 kbps; then, the M24SR02-Y changes the ascending
and descending data rates.
Table 64. PPS response
Name
Byte field
Bit field
INS
–
–
PPS0
0x11
0xDX
b8-b5
b4-b1
Response code
DID field
2 CRC bytes
54/88
DS9985 Rev 12
M24SR02-Y
I²C and RF command sets
5.10
Specific I
²
C command set
Table 65. Specific I
²
C commands
Command name
Format Class
byte Instruction
code
Brief description
Open an I
²
C session when the
RF session is not ongoing
GetI2Csession
KillRFsession
–
–
–
–
0x26
0x52
Kill the RF session and open an
I
²
C session
5.10.1
GetI2Csession command
The GetI2Csession command opens an I²C session if an RF session is not ongoing.
Table 66. GetI2Csession command format
–
INS
Length
Value
1 byte
0x26
The GetI2Csession command does not create a reply.
When an RF session is ongoing, the M24SRxx will not acknowledge the command.
When no RF session is ongoing, the M24SRxx will acknowledge the command and open an
I²C session.
5.10.2
KillRFsession command
The KillRF session command closes the RF session and opens an I²C session.
Table 67. KillRFsession command format
–
INS
Length
Value
1 byte
0x52
The KillRFsession command does not create a reply. The RF session is closed when the
device acknowledges the command.
Caution:
A successful completion of the RF command is not certain.
DS9985 Rev 12
55/88
78
RF device operation
M24SR02-Y
6
RF device operation
6.1
Anticollision and Device activation command set for the RF
interface
The M24SR02-Y device supports the command set defined in the NFC-A
T
e
chnology and
the Type 4A
T
a
g Platform chapters of the NFC Digital Protocol V1.0 specification.
6.2
Open an RF session
Once the RF host has terminated the anticollision procedure and retrieve the ATS response,
it must send the SelectApplication command. The M24SR02-Y will open an RF session. At
this point, the RF host can send the applicative command set and the I²C cannot
2
communicate with the M24SR02-Y without closing first the RF session using the I C
KillRFsession command.
6.3
6.4
Close an RF session
The RF host can close the RF session through one of these methods:
•
•
send an S(DES) command
turn off the RF field.
Applicative command set
The applicative command set is composed of the following command sets:
•
•
•
the NFC Forum Type 4
T
a
g command set
the ISO/IEC 7816-4 command set
the proprietary command set.
56/88
DS9985 Rev 12
M24SR02-Y
I2C device operation
2
7
I C
device operation
2
The M24SR02-Y device supports the I
C protocol. The device that controls the data transfer
is known as the bus master, and the other one as the slave device. A data transfer can only
be initiated by the bus master, which also provides the serial clock for synchronization. The
M24SR02-Y device is a slave in all communications.
7.1
I
2
C communication protocol
2
2
The I C communication is built on a system of command and reply exchange. The I
C host
starts the communication by sending a request. Once a valid request is received by the
M24SR02-Y device, it carries out an internal operation and creates its answer.
As defined in this document, and except for the GetI2C session and Kill RF session
commands, the definition of a valid request is a command with a right CRC value.
Figure 12
shows an exchange of a command and a response between the I²C host and the
M24SR02-Y. Once the I²C session is open, the I²C host can send a command. The
command is composed of:
•
•
a Device Select field with the R/W bit set to 0
the command field.
The M24SR02-Y acknowledges on the reception of each byte.
Once the M24SR02-Y is ready to send the answer, the I²C host must:
•
•
send a Device Select field with the R/W bit set to 1
release the SDA line and send an SCL clock.
The I²C host must acknowledge on the reception of each byte.
Figure 12. Command and response exchange
,ꢁ&ꢄEXV
5ꢅ:ꢄ ꢄꢊ
5ꢅ:ꢄ ꢄꢂ
‘HYLFH6HOHFW
&RPPDQG
3
6
‘HYLFH6HOHFW
5HVSRQVH
3
6
06ꢀꢊꢈꢍꢁ9ꢂ
Legend:
2
S is the I C Start bit sequence
P is the I C Stop bit sequence
R/W is the 8
bit of Device Select.
2
th
Note:
A restart during a command and response exchange is not supported by the M24SR02-Y.
2
After a command, the I
C host can execute a Polling sequence to determine when the
response is available.
Polling sequence: Loop on
< START (S) + DeviceSelect with RW=0 + read NACK/ACK
+ STOP (P) >
The response is available as soon as the M24SR02-Y sends an ACK ( host read will a
‘0’).
DS9985 Rev 12
57/88
78
I2C device operation
M24SR02-Y
7.2
Start condition
A Start condition is identified by a falling edge of serial data (SDA) while the serial clock
(SCL) is stable in the high state. A Start condition must precede any data transfer command.
The device continuously monitors (except during an instruction processing) the SDA and the
SCL for a Start condition, and does not respond unless one is given.
7.3
7.4
Stop condition
A Stop condition is identified by a rising edge of serial data (SDA) while the serial clock
(SCL) is stable and driven high. A Stop condition terminates a command between the device
and the bus master.
I²C token release sequence
As explained in the M24SR02-Y session mechanism, the I²C communication is reserved to
the I²C host when the session token has the I²C value.
The following sequence explains how to release the I²C value of the session token.
I²C communication with the M24SR02-Y starts with a valid Start condition, followed by a
device select code.
If the delay between the Start condition and the following rising edge of the Serial Clock
(SCL) that samples the most significant of the Device Select exceeds the t
START_OUT_MAX
until the next valid Start condition.
Figure 13. I²C token release sequence
ꢄ
!ꢄW
67$57B287BPD[ꢄ
6&/
6’$
0ꢁꢆ65ꢄ’HYLFHꢄ
6HOHFWꢄFRGH
6WDUWꢄ
FRQGLWLRQ
6WRSꢄ
FRQGLWLRQ
06Yꢆꢀꢊꢍꢈ9ꢂ
2
Note:
If the above delay is below t
unmodified.
START_OUT_min
2
If the delay is between t
and t
, I C session token might or not
START_OUT_min
START_OUT_max
be released. This range of delay is not authorized for safe operation.
58/88
DS9985 Rev 12
M24SR02-Y
I2C device operation
7.5
I²C timeout on clock period
2
During a data transfer on the I
C bus, if the serial clock high pulse or serial clock low pulse
2
exceeds t
CL_RESET
condition.
If the serial clock high pulse is under the maximum value of
t
CHCL
and the serial clock low
2
pulse is under the maximum value of t
CLCH
For proper operation, the serial clock high pulse must not be higher than
t
CHCL
and lower
than t
, and the serial clock low pulse must not be higher than
t
CHCH
and lower
CL_RESET
t
.
CL_RESET
7.6
Acknowledge bit (ACK)
The acknowledge bit is used to indicate a successful byte transfer. The bus transmitter,
whether a bus master or a slave device, releases the serial data (SDA) after sending eight
bits of data. During the 9th clock pulse period, the receiver pulls the SDA low to
acknowledge the receipt of the eight data bits.
7.7
7.8
Data input
During data input, the device samples serial data (SDA) on the rising edge of the serial clock
(SCL). For a correct device operation, the SDA must be stable during the rising edge of the
SCL, and the SDA signal must change only when the SCL is driven low.
I²C device address
2
The device address is the concatenation of the group number coded on 4 bits and the I C
2
Table 68. I
C device address format
b7-b4
b3
1
b2
1
b1
0
b0
–
0b1010
0bx
Group number
E2 bit
E1 bit
E0 bit
0 = Request
1 = Answer
DS9985 Rev 12
59/88
78
I2C device operation
M24SR02-Y
7.9
I²C frame format
2
The I
C frame is composed of three fields:
1. SOD
field: contains the device select and the PCB. The PCB field is detailed in
2
2. Payload
field: contains the command and its parameter, as defined in the I
C command
set.
3. EOD
field: contains the two CRC bytes computed on the SOD but excluding the device
select byte field.
2
2
Table 69. I C frame format
SOD
Payload
EOD
I
2
C frame
0xAC or 0xAD
1 byte
1 to 251 bytes
2 bytes
Device select
0xAC: to send a request to the M24SR02-Y
0xAD: to read a response of the M24SR02-Y
PCB field
I
2
C command or I
2
C answer
2 CRC bytes
7.9.1
Example of I²C frame commands
NDEF Tag Application command
2
2
This example presents the I
C frame of an NDEF
T
a
g Application Select command. The I
C
2
Table 70. I C host to M24SR02-Y
Field
SOD
Payload
EOD
Value
0xAC
0x02 or 0x03
Command field
35 C0 or DF BE
Device select
PCB field
0x00 A4 04 00 07 D2 76 00 00 85 01 01 00
2 CRC bytes
2
2
Before sending a new command, the I
C host can send an I C frame to read the
M24SR02-Y answer to the NDEF tag Application Select command.
60/88
DS9985 Rev 12
M24SR02-Y
I2C device operation
2
Table 71. M24SR02-Y to I C host
SOD
Payload
M24SR02-Y to I
2
C host
EOD
Field
I
2
C host to M24SR02-Y
0xAD
Value
0x02 or 0x03
0x90 00
F1 09 or 2D 53
Device select
PCB field
I
2
C command
2 CRC bytes
2
Figure 14. NDEF tag Application Select command
6WDUWꢄRIꢄWKHꢄ
WUDQVPLVVLRQꢄ
RIꢄWKHꢄUHTXHVW
,ð&ꢄEXV
6
$&.
$&.
$&.
$&.
$&.
$&.
$&.
$&.
$&.
$&.
$&.
$&.
$&.
$&.
͘͘͘
Ϭdžꢃꢂ
džϬϮ ϬdžϬϬ Ϭdžꢃϰ ϬdžϬϰ ϬdžϬϬ ϬdžϬϳ ϬdžꢀϮ Ϭdžϳϲ ϬdžϬϬ ϬdžϬϬ Ϭdžϴϱ ϬdžϬϭ ϬdžϬϭ
(QGꢄRIꢄWKHꢄ
WUDQVPLVVLRQꢄ
RIꢄWKHꢄUHTXHVW
,ð&ꢄEXV
$&.
$&.
$&.
͘͘͘
ꢊ[ꢊꢊ
[ꢀꢉ
ꢊ[&ꢊ
W
6WDUWꢄRIꢄWKHꢄ
WUDQVPLVVLRQꢄ
RIꢄWKHꢄDQVZHU
ꢄŶĚꢁŽĨꢁƚŚĞꢁ
ƚƌĂŶƐŵŝƐƐŝŽŶꢁ
ŽĨꢁƚŚĞꢁƌĞƋƵĞƐƚ
,ð&ꢄEXV
^
ꢃꢂ< ꢃꢂ< ꢃꢂ< ꢃꢂ< ꢃꢂ< ꢃꢂ<
͘͘͘
Ϭdžꢃꢀ ϬdžϬϮ ϬdžϵϬ ϬdžϬϬ Ϭdž&ϭ ϬdžϬϵ
W
$&.
$&.
/HJHQG
$FNQRZOHGJHꢄEꢄWKHꢄ,ð&ꢄKRVW
$FNQRZOHGJHꢄEꢄ0ꢁꢆ65[[ꢋ<
%WHꢄVHQWꢄEꢄWKHꢄ,ð&ꢄKRVW
%WHꢄVHQWꢄEꢄWKHꢄ0ꢁꢆ65[[ꢋ<
ꢊ[ꢊꢁ
ꢊ[ꢊꢊ
6
6WDUWꢄVHQWꢄEꢄWKHꢄ,ð&ꢄKRVW
6WRSꢄVHQWꢄEꢄWKHꢄ,ð&ꢄKRVW
3
06ꢀꢀꢃꢆꢀ9ꢂ
DS9985 Rev 12
61/88
78
I2C device operation
M24SR02-Y
7.10
Open an I²C session
To
o
pen an I²C session, the I²C host must send either the GetSession command or the
KillRFsession command. The GetSession Command opens an I²C session if an RF session
in not currently opened.
A KillRFsession command closes the current RF session if it exists, and opens an I²C
session.
When an I²C session is opened, the RF host cannot communicate with the M24SR02-Y and
cannot close the I²C session.
7.11
Close the I²C session
There are four ways to close an I²C session:
•
•
•
•
turn off the Vcc power supply
send the I²C token release sequence
wait for the I²C watchdog when it is enabled
wait for the I²C timeout on clock period.
62/88
DS9985 Rev 12
M24SR02-Y
Functional procedures
8
Functional procedures
This section describes some procedure to access the memory or manage its protection.
8.1
Selection of an NDEF message
The RF or I²C host must use this procedure to detect the NDEF message inside an
M24SR02-Y.
The NDEF detection procedure is as follows:
1. Open
an RF or an I²C session
2. Send
the SelectNDEF
T
a
gApplication command
3. Select
the CC file
4. Read
the CC file
5. Select
the NDEF file
8.2
Reading of an NDEF message
The RF or I²C host executes the NDEF read procedure to read the NDEF file.
1. Detect
successfully the NDEF file using the NDEF detection procedure
2. Check
that the read access without any security is granted for the NDEF file from the
information provided by the CC file
3. Select
the NDEF file
4. Read
the NDEF file
Note:
Reading the NDEF file must not go beyond the NDEF Length field (NLEN), which indicates
the size of the NDEF message stored in the NDEF file.
8.3
Reading a locked NDEF file
The RF or I²C host executes this procedure to read an NDEF file that has been previously
locked.
1. Select
the NDEF
T
a
g Application
2. Select
the NDEF file
3. Verify
the Read password by using the Verify command
4. Read
the data in the NDEF file
DS9985 Rev 12
63/88
78
Functional procedures
M24SR02-Y
8.4
Locking an NDEF file
The RF or I²C host executes this procedure to protect an NDEF file.
1. Select
the NDEF
T
a
g Application
2. Check
the right access provided by the CC file
3. Select
the NDEF file
4. Transmit
the NDEF file Write password by using the Verify command
5. Lock
the NDEF file by sending the Enable verification command.
8.5
8.6
Unlocking an NDEF file
The RF or I²C host executes this procedure to unlock an NDEF file that has been previously
locked.
1. Select
the NDEF
T
a
g Application
2. Select
the NDEF file
3. Verify
the NDEF file Write password or the I²C password by using the Verify command
4. Unlock
the NDEF file by sending the Disable verification command.
Reaching the read-only state for an NDEF file
The RF or I²C host executes this procedure to reach the read-only state for an NDEF file.
1. Select
the NDEF
T
a
g Application
2. Select
the NDEF file
3. Transmit
the NDEF file Write password or the I²C password by using the Verify
command
4. Send
an EnablePermanentState command as the Write access right of the previous
Select NDEF file.
8.7
Changing an NDEF password procedure
The RF or I²C host could use this procedure to change one NDEF password. it can be a
Read or Write password.
1. Select
the NDEF
T
a
g Application
2. Select
the NDEF file
3. Transmit
the NDEF file Write password or the I²C password by using the Verify
command
4. Change
the password by sending a ChangeReferenceData command.
64/88
DS9985 Rev 12
M24SR02-Y
Functional procedures
8.8
Changing a File type Procedure
The RF or I²C host executes this procedure to change the File Type of a file for which all
access rights were previously granted.
1. Select
the NDEF
T
a
g Application
2. Select
the File to be modified
3. Set
the File Length to 0x00 using the UpdateBinary command
4. Send
an UpdateFileType command with the New file Type as data.
8.9
Updating an NDEF file
When there’s enough space in the file to update it with new content, the following steps must
be followed to update the NDEF message:
1. Select
the NDEF
T
a
g Application
2. Select
the NDEF file
3. Unlock
the NDEF file if necessary
4. Write
the NDEF length to 0x0000 with the Update Binary command.
5. Write
the NDEF message in the NDEF message field using one or more Update Binary
commands.
6. Write
the NDEF length of the NDEF message using the Update Update command.
It is recommended the NDEF length is read back and checked against the desired value to
ensure the Update sequence has been correctly performed.
DS9985 Rev 12
65/88
78
UID: unique identifier
M24SR02-Y
9
UID: unique identifier
The M24SR02-Y is uniquely identified by a 7-byte unique identifier (UID). The UID is a
read-only code and comprises:
•
•
•
the IC manufacturer code on 1 byte (0x02 for STMicroelectronics)
the product code on 1 byte
a device number on 5 bytes.
Table 72. UID format
0x02 0x82
–
5 bytes
IC manufacturer code
M24SR02-Y product code
Device number
66/88
DS9985 Rev 12
M24SR02-Y
Maximum ratings
10
Maximum ratings
the device. These are stress ratings only and operation of the device at these or any other
conditions above those indicated in the operating sections of this specification is not implied.
Exposure to absolute maximum rating conditions for extended periods may affect the device
reliability.
Table 73. Absolute maximum ratings
Symbol
Parameter
Min.
Max.
Unit
T
A
Ambient operating temperature
-40
15
85
25
°C
°C
T
ST
G
, h
STG
,
Sawn wafer on
UV tape
Storage conditions
9
(1)
months
t
STG
Kept in its original packing form
UFDFPN8, SO8,
TSSOP8
T
STG
Storage temperature
–65
15
150
°C
Storage temperature
Storage time
Sawn bumped
wafer (kept in its
antistatic bag)
25
9
°C
T
STG
months
Lead temperature
during soldering
UFDFPN8, SO8,
TSSOP8
T
LEAD
V
IO
See note
(2)
°C
I
2
C input or output range and GPO
-0.50
–
6.5
V
(3)
I
CC
RF supply current AC0 – AC1
100
mA
RF input voltage
amplitude between AC0
and AC1, GND pad left
floating
(3)
V
MAX_1
VAC0-VAC1
–
10
V
AC voltage between
AC0 and GND, or AC1
and GND
VAC0-GND or
VAC1-GND
(3)
V
MAX_2
-0.5
4.5
V
V
V
Electrostatic discharge
voltage (human body
model)
(4)
V
ESD
AC0-AC1
–
–
1000
3500
Electrostatic discharge
voltage (human body
V
ESD
Other pads
1. Counted
from ST shipment date.
2. Compliant
with JEDEC Std J-STD-020D (for small body, Sn-Pb or Pb assembly), the ST ECOPACK
7191395 specification, and the European directive on Restrictions on Hazardous Substances (ROHS
directive 2011/65/EU, July 2011).
3. Based
on characterization, not tested in production. Maximum adsorbed power = 100 mW @ 7.5 A/m
4. AEC-Q100-002
(compliant with JEDEC Std JESD22-A114A, C1 = 100 p
F
,
R
1 = 1500
ꢀ
, R2 = 500
ꢀ
)
DS9985 Rev 12
67/88
78
I2C DC and AC parameters
M24SR02-Y
2
11
I C
DC and AC parameters
This section summarizes the operating and measurement conditions, and the DC and AC
2
characteristics of the device in I
C mode. The parameters in the DC and AC characteristic
tables that follow are derived from tests performed under the measurement conditions
summarized in the relevant tables. Designers must check that the operating conditions in
their circuit match the measurement conditions when relying on the quoted parameters.
2
Table 74. I C operating conditions
Symbol
Parameter
Min.
Max.
Unit
V
CC
T
A
Supply voltage
Ambient operating temperature
2.7
5.5
85
V
– 40
°C
Table 75. AC test measurement conditions
Symbol
Parameter
Min.
Max.
Unit
C
L
Load capacitance
100
pF
ns
V
t
r,
t
f
Input rise and fall times
Input levels
–
50
V
hi-lo
V
ref(t)
0.2 V
CC
to 0.8 V
CC
0.3 V
CC
to 0.7 V
CC
Input and output timing reference levels
V
Figure 15. AC test measurement I/O waveform
,QSXWꢄOHYHOV
,QSXWꢄDQGꢄRXWSXW
WLPLQJꢄUHIHUHQFHꢄOHYHOV
ꢊꢇꢃꢄ9
FF
ꢊꢇꢈꢄ9
ꢊꢇꢀꢄ9
FF
FF
ꢀꢁꢂ 6
CC
06ꢆꢈꢉꢊꢂ9ꢂ
Table 76. Input parameters
Parameter
Symbol
Min.
Max.
Unit
C
IN
C
IN
t
NS
Input capacitance (SDA)
–
–
–
8
6
pF
pF
ns
Input capacitance (other pins)
Pulse width ignored (Input filter on SCL and SDA)
80
68/88
DS9985 Rev 12
M24SR02-Y
Symbol
I2C DC and AC parameters
2
Table 77. I C DC characteristics
Parameter
Test condition
Min.
Max.
Unit
Input leakage current
(SCL, SDA)
V
IN
= V
SS
or V
CC
device in Standby mode
I
LI
–
± 2
µA
SDA in Hi-Z, external voltage applied on
SDA: V
SS
or V
CC
I
LO
Output leakage current
–
± 2
µA
V
CC
= 3.3
V
,
w
ith RF ON
CC
= 3.3
V
,
w
ith RF OFF
CC
= 5.5 V, with RF ON
(1)
V
CC
= 5.5
V
,
w
ith RF OFF
CC
= 3.3
V
,
w
ith RF ON
CC
= 3.3
V
,
w
ith RF OFF
V
CC
= 5.5
V
,
w
ith RF ON
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
30
5
V
Standby power mode supply
current
I
CC0
I
CC1
I
CC2
I
CC3
µA
V
30
5
V
150
150
150
150
250
200
250
200
550
500
550
500
V
Supply current
µA
µA
µA
(I
2
C Session open)
V
CC
= 5.5
V
,
w
ith RF OFF
V
CC
= 3.3 V (f
C
= 1 MHz), with RF ON
(3)
Supply current
(2)
(Read binary)
V
CC
= 3.3 V (f
C
= 1 MHz), with RF OFF
(3)
CC
= 5.5 V (f
C
= 1 MHz), with RF ON
(3)
V
CC
= 5.5 V (f
C
= 1 MHz), with RF OFF
(3)
CC
= 3.3 V (f
C
= 1 MHz), with RF ON
(3)
CC
= 3.3 V (f
C
= 1 MHz),with RF OFF
(3)
V
V
Supply current
(2)
(Update binary)
V
V
CC
= 5.5 V (f
C
= 1 MHz), with RF ON
(3)
V
CC
= 5.5 V (f
C
= 1 MHz), with RF OFF
(3)
V
CC
= 2.7 V
V
IL
V
IH
V
IL
V
IH
Input low voltage (SDA, SCL)
Input high voltage (SDA, SCL)
Input low voltage (RF disable)
Input high voltage (RF disable)
-0.45
0.7 V
CC
–
0.3 V
CC
6.5
V
V
V
V
V
CC
= 5.5 V
V
CC
= 2.7 V
V
CC
= 5.5 V
V
CC
= 2.7 V
V
CC
= 5.5 V
0.45
–
V
CC
= 2.7 V
1.4
V
CC
= 5.5 V
Output low voltage (SDA)
Output low voltage (GPO)
I
OL
= 3 mA, V
CC
= 5.5 V
OL
= 1 mA, V
CC
= 2.7 to 5.5 V
–
–
0.4
0.4
V
V
V
OL
I
1. When
an RF session is Opened, I
cc
corresponds to the standby power mode.
2. Characterized
only.
DS9985 Rev 12
69/88
78
I2C DC and AC parameters
M24SR02-Y
2
Table 78. I
C AC characteristics (400 kHz)
(preliminary data based on design simulations)
Symbol
Alt.
Parameter
Min.
Max.
Unit
f
C
f
SCL
t
HIGH
t
LOW
–
Clock frequency
0.05
0.6
400
kHz
µs
µs
µs
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ms
ms
ns
ms
(1)
t
CHCL
Clock pulse width high
Clock pulse width low
Clock reset
20000
20000
(2)
t
CLCH
1.3
t
CL_reset
t
XH1XH2
t
XL1XL2
t
DL1DL2
t
DXCX
40000
–
(3)
(3)
t
R
Input signal rise time
Input signal fall time
SDA (out) fall time
(3)
(3)
t
F
t
F
20
100
0
300
t
SU:DAT
Data in set up time
t
HD:DAT
Data in hold time
–
–
t
CLDX
(4)
t
CLQX
t
DH
t
AA
Data out hold time
100
–
–
(5)
t
CLQV
Clock low to next data valid (access time)
900
–
(6)
t
CHDX
t
SU:STA
Start condition set up time
t
HD:STA
Start condition hold time
t
SU:STO
Stop condition set up time
600
600
600
1300
–
t
DLCL
t
CHDH
t
DHDL
–
–
t
BUF
Time between Stop condition and next Start condition
–
I²C write time in one page
5
t
W
t
WR
I²C write time up to 246 bytes
–
90
80
40
(7)
t
NS
–
–
Pulse width ignored (input filter on SCL and SDA)
Delay for I²C token release
–
t
START_OUT
20
1. t
CHCL
timeout.
2. t
CLCH
timeout.
3. There
is no min. or max. value for the input signal rise and fall times. It is however recommended by the I²C specification that the input
signal rise and fall times be more than 20 ns and less than 300 ns when f
C
< 400 kHz.
4.
T
o
a
void spurious Start and Stop conditions, a minimum delay is placed between SCL=1 and the falling or rising edge of
SDA.
5. t
CLQV
is the time (from the falling edge of SCL) required by the SDA bus line to reach 0.8V
CC
in a compatible way with the
I
2
C specification (which specifies t
SU:DAT
(min) = 100 ns), assuming that the R
bus
× C
bus
time constant is less than 500 ns
6. For
a restart condition, or following a write cycle.
7. Characterized
only, not tested in production.
70/88
DS9985 Rev 12
M24SR02-Y
I2C DC and AC parameters
2
Table 79. I C AC characteristics (1 MHz)
(preliminary data based on design simulations)
Symbol
Alt.
Parameter
Min.
Max.
Unit
f
C
f
SCL
Clock frequency
0.05
260
1000
–
kHz
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
(1)
t
CHCL
t
HIGH
Clock pulse width high
t
LOW
Clock pulse width low
(2)
t
CLCH
500
–
(3)
(3)
t
XH1XH2
t
XL1XL2
t
DL1DL2
t
DXCX
t
R
t
F
t
F
Input signal rise time
Input signal fall time
SDA (out) fall time
(3)
(3)
20
50
120
t
SU:DAT
Data in set up time
t
HD:DAT
Data in hold time
–
t
CLDX
0
–
t
CLQX
t
DH
t
AA
Data out hold time
100
–
–
(4)(5)
t
CLQV
Clock low to next data valid (access time)
450
(6)
t
CHDX
t
SU:STA
Start condition set up time
t
HD:STA
Start condition hold time
t
SU:STO
Stop condition set up time
250
250
250
–
–
–
t
DLCL
t
CHDH
Time between Stop condition and next Start
condition
t
DHDL
t
BUF
t
WR
–
500
–
ns
I²C write time in one page
I²C write time up to 246 bytes
–
–
5
ms
ms
t
W
90
Pulse width ignored (input filter on SCL and
SDA)
(7)
t
NS
–
80
ns
1. t
CHCL
timeout.
2. t
CLCH
timeout.
3. There
is no min. or max. value for the input signal rise and fall times. It is however recommended by the I²C
specification that the input signal rise and fall times be less than 120 ns when f
C
< 1 MHz.
4.
T
o
a
void spurious Start and Stop conditions, a minimum delay is placed between SCL = 1 and the falling or
rising edge of SDA.
5. t
CLQV
is the time (from the falling edge of SCL) required by the SDA bus line to reach 0.8V
CC
in a
compatible way with the I
2
C specification (which specifies t
SU:DAT
(min) = 100 ns), assuming that the R
bus
6. For
a reStart condition, or following a write cycle.
7. Characterized
only, not tested in production.
DS9985 Rev 12
71/88
78
I2C DC and AC parameters
M24SR02-Y
2
Figure 16. I C AC waveforms
W
W
&+&/
;/ꢂ;/ꢁ
W
W
W
&/&+
;+ꢂ;+ꢁ
6&/
W
‘/&/
;/ꢂ;/ꢁ
6’$ꢄ,Q
W
W
W
‘;&+
6’$
&KDQJH
W
W
W
‘+’/
&+’/
6WDUW
FRQGLWLRQ
&/’;
;+ꢂ;+ꢁ
&+’+
6WDUW
6’$
,QSXW
6WRS
FRQGLWLRQ
FRQGLWLRQ
6&/
6’$ꢄ,Q
W
:
W
W
&+’+
&+’/
6WRS
FRQGLWLRQ
:ULWHꢄFFOH
6WDUW
FRQGLWLRQ
W
&+&/
6&/
W
W
W
4/ꢂ4/ꢁ
&/49
&/4;
‘DWDꢄYDOLG
‘DWDꢄYDOLG
6’$ꢄ2XW
06ꢆꢈꢉꢀꢁ9ꢂ
72/88
DS9985 Rev 12
M24SR02-Y
I2C DC and AC parameters
11.1
I
2
C timing measurement condition
Figure 17
represents the maximum R
value versus bus parasitic capacitance (C
) for
bus
bus
C
Figure 17. Maximum Rbus value with f
= 400 kHz
C
ꢃꢀꢀ
4HE 2
X #
TIME CONSTANT
BUS
BUS
MUST BE BELOW THE ꢄꢀꢀ NS
TIME CONSTANT LINE REPRESENTED
ON THE LEFTꢁ
6
##
ꢃꢀ
2
BUS
(ERE 2
BUS
§ #
ꢋ ꢃꢂꢀ NS
BUS
ꢄ K
½
3#,
3$!
)£# BUS
MASTER
-ꢂꢄXXX
ꢃ
ꢌꢀ P&
#
BUS
ꢃꢀ
ꢃꢀꢀ
“US LINE CAPACITOR ꢈP&ꢉ
ꢃꢀꢀꢀ
AIꢃꢄꢅꢆꢇB
Figure 18
represents the Maximum Rbus value versus bus parasitic capacitance (Cbus) for
an I
C bus at maximum frequency f
= 1 MHz.
C
Figure 18. Maximum Rbus value with f
= 1 MHz
C
6
ꢃ
ꢀ
ꢀ
##
2
BUS
4HE 2
§ #
TIME CONSTANT
BUS
BUS
MUST BE BELOW THE ꢃꢍꢀ NS
TIME CONSTANT LINE REPRESENTED
ON THE LEFTꢁ
3#,
3$!
)£# BUS
MASTER
ꢃꢀ
ꢄ
-ꢂꢄXXX
(EREꢎ
#
§
BUS
ꢋ ꢃꢂꢀ NS
#
2
BUS
BUS
ꢃ
ꢃꢀ
ꢌꢀ
“US LINE CAPACITOR ꢈP&ꢉ
ꢃꢀꢀ
-3ꢃꢆꢅꢄꢍ6ꢃ
DS9985 Rev 12
73/88
78
I2C DC and AC parameters
M24SR02-Y
2
Figure 19. I
C bus protocol
6&/
6’$
6’$
,QSXW
6’$
&KDQJH
6WDUW
6WRS
FRQGLWLRQ
FRQGLWLRQ
6&/
6’$
ꢂ
ꢁ
ꢀ
ꢈ
ꢃ
ꢍ
$&.
06%
6WDUWꢄ
FRQGLWLRQ
ꢂ
ꢁ
ꢀ
ꢈ
ꢃ
ꢍ
6&/
6’$
06%
$&.
6WRS
FRQGLWLRQ
-3ꢄꢅꢍꢃꢌ6ꢃ
Table 80. Device select code
Device type identifier
(1)
Chip Enable address
RW
b7
b6
b5
b4
b3
b2
b1
b0
1
0
1
0
1
1
0
RW
1. The
most significant bit, b7, is sent first.
74/88
DS9985 Rev 12
M24SR02-Y
GPO parameters
12
GPO parameters
This section lists the timing of the GPO according to its configuration.
(1)
Table 81. GPO timings measurement
GPO field
I/F
Condition
Command
Symbol
CmdSTPtoGPlow
Typ. Unit
Kill session
Get session
15
(2)
GPO low when
session active
I
2
C
µs
ns
0xX1
0x1X
I
2
C token release
sequence
I
2
C
RF
GPO return HZ
AnswerlbLBtoGPHZ 105
Session open
GPO low when
session active
NDEF select
Deselect
CmdEOFtoGPlow
170
µs
RF
I
2
C
GPO return HZ
CmdEOFtoGPHZ
CmdSTPtoGPlow
370
45
µs
ms
µs
GPO low when
programming
Update Binary
Update Binary
Writing time duration
(No time extension)
0xX2
0x2X
I
2
C
RF
RF
5
75
5
WIP
CmdEOFtoGPlow
GPO low when
programming
Writing time duration
(No time extension)
ms
µs
GPO low when a
command is
computed
ReadBinary
or
UpdateBinary
55
or
5
I
2
C
CmdSTPtoGPlow
ms
ns
Answer ready
0xX3
0x3X
GPO return HZ on
new command
After NewCmdlbFB
or AnswerlbFB
I
2
C
RF
RF
All commands
105
75
5
GPO low when
modifying NDEF
UpdateBinary
(Msg Length #0)
CmdEOFtoGPlow
µs
Message in
progress
GPO low when
modifying NDEF
Writing time duration
(No time extension)
UpdateBinary
SendInterrupt
All commands
SendInterrupt
ms
GPO low after
receiving an
Interrupt command
I
2
C
I
2
C
CmdSTPtoGPlow
50
µs
ns
µs
0xX4
0x4X
After NewCmdlbFB
or AnswerlbFB
Interrupt
GPO return HZ
105
RF
RF
GPO low after
receiving an
Interrupt command
CmdEOFtoGPlow
Pulse duration
75
540
DS9985 Rev 12
75/88
78
GPO parameters
GPO field
M24SR02-Y
(1)
Table 81. GPO timings measurement
(continued)
Symbol
I/F
Condition
Command
Typ. Unit
GPO low when
reset
I
2
C
Reset GPO
CmdSTPtoGPlow
CmdSTPtoGPHZ
CmdEOFtoGPlow
CmdEOFtoGPHZ
40
0xX5
0x5X
GPO return HZ
when set
I
2
C
RF
RF
Set GPO
Reset GPO
Set GPO
40
60
State control
GPO low when
reset
GPO return HZ
when set
60
µs
6
Anticollision
command or start
of RF disturb
(command using
another RF
GPO low after
receiving an RF
command
RF
RF
CmdSOFtoGPlow
CmdEOFtoGPHZ
protocol)
RF busy
0x6X
Deselect or end of
RF disturb
(command using
another RF
GPO return HZ
after deselection or
RF command in
another protocol
460
protocol)
1. Characterized
only.
2. Add
100 µs for boot after POR.
76/88
DS9985 Rev 12
M24SR02-Y
Write cycle definition
13
Write cycle definition
(1)
Table 82. Write cycle definition
Test Conditions
Symbol
Parameter
Min
Max
Units
T
A
≤
25 °C, V
CC(min)
< V
CC
< V
CC(max)
T
A
≤
85 °C, V
CC(min)
< V
CC
< V
CC(max)
–
–
1,000,000
600,000
Write cycle
Ncycle
Write cycle
endurance
(2)
1. A
write cycle is calculated per byte, and corresponds to a write to this byte.
2. Write
cycle endurance is defined by characterization and qualification.
DS9985 Rev 12
77/88
78
RF electrical parameters
M24SR02-Y
14
RF electrical parameters
This section summarizes the operating and measurement conditions, and the DC and AC
characteristics of the device in RF mode.
The parameters in the following tables are derived from tests performed under the
measurement conditions summarized in the relevant tables. Designers have to check that
the operating conditions in their circuit match the measurement conditions when relying on
the quoted parameters.
Table 83. Default operating conditions
Symbol
Parameter
Min.
Max.
Unit
T
A
Ambient operating temperature
–40
85
°C
(1)
Table 84. RF characteristics
Symbol
Parameter
Condition
Min
Typ
Max
Unit
f
C
External RF signal frequency
13.553
1500
13.560 13.567
MHz
H_ISO
Operating field according to ISO
T
A
= 0 °C to 50 °C
–
–
7500 mA/m
7500 mA/m
Operating field in extended
temperature range
H_Extended
T
A
= -40 °C to 85 °C
500
MI
CARRIER
100% carrier modulation index
MI=(A-B)/(A+B)
90
28 / f
C
7 / f
C
1.5 x t
4
0
–
–
–
–
–
100
40.5 / f
C
t
1
%
t
1
t
2
t
3
t
4
Pause A length
–
–
–
–
Pause A low time
Pause A rise time
Pause A rise time section
µs
16 / f
C
6 / f
C
Minimum time from carrier
generation to first data
t
MIN CD
W
t
From H-field min
–
–
–
–
5
–
ms
RF write time (including internal
verify) for one page
6
C
TUN
Internal tuning capacitor in SO8
(2)
f
C
= 13.56 MHz
Chip reset
22.5
–
25
–
27.5
5
pF
t
RF_OFF
RF OFF time
ms
1. All
timing characterizations are performed on a reference antenna with the following characteristics:
External size: 75 mm x 48 mm
Number of turns: 6
Width of conductor: 0.6 mm
Space between two conductors: 0.6 mm
Value of the tuning capacitor in SO8: 25 pF (M24SR02-Y)
Value of the coil: 5 µH
Tuning frequency: 14.2 MHz.
2. Characterized
only, at room temperature only, measured at VAC0-VAC1 = 2 V peak to peak at 13.56 MHz.
78/88
DS9985 Rev 12
M24SR02-Y
Package information
15
Package information
In order to meet environmental requirements, ST offers these devices in different grades of
ECOPACK packages, depending on their level of environmental compliance. ECOPACK
ECOPACK is an ST trademark.
15.1
SO8N package information
Figure 20. SO8N – 8-lead plastic small outline, 150 mils body width, package outline
H X
ꢂ
ꢃ
!ꢄ
!
C
CCC
B
E
ꢀꢁꢂꢃꢄPP
*$8*(ꢄ3/$1(
$
K
ꢁ
%ꢀ
%
,
ꢀ
!ꢀ
,ꢀ
62ꢋ$B9ꢁ
1. Drawing
is not to scale.
Table 85. SO8N – 8-lead plastic small outline, 150 mils body width,
package data
millimeters
Typ
inches
(1)
Symbol
Min
Max
Min
Typ
Max
A
A1
A2
b
–
–
1.750
0.250
–
–
0.0689
0.0098
–
0.100
1.250
0.280
0.170
4.800
5.800
3.800
–
–
0.0039
0.0492
0.0110
0.0067
0.1890
0.2283
0.1496
–
–
–
–
–
0.480
0.230
5.000
6.200
4.000
–
–
0.0189
0.0091
0.1969
0.2441
0.1575
–
c
–
4.900
6.000
3.900
1.270
–
–
D
E
0.1929
0.2362
E1
e
0.1535
0.0500
h
0.250
0°
0.500
8°
0.0098
0°
–
–
–
0.0197
8°
k
–
L
0.400
–
1.270
0.0157
0.0500
DS9985 Rev 12
79/88
84
Package information
M24SR02-Y
Table 85. SO8N – 8-lead plastic small outline, 150 mils body width,
package data (continued)
millimeters
inches
(1)
Symbol
Min
Typ
Max
Min
Typ
Max
L1
–
–
1.040
–
–
–
–
0.0409
–
–
ccc
0.100
0.0039
1. Values
in inches are converted from mm and rounded to four decimal digits.
Figure 21. SO8N – 8-lead plastic small outline, 150 mils body width,
package recommended footprint
ꢊꢇꢌꢄꢎ[ꢃꢏ
ꢂꢇꢁꢈ
2ꢈB62ꢃ1B)3B9ꢂ
80/88
DS9985 Rev 12
M24SR02-Y
Package information
15.2
TSSOP8 package information
Figure 22. TSSOP8 – 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch,
package outline
ꢀ
ϴ
ϱ
Đ
ꢄϭ
ꢄ
ϭ
ϰ
ɲ
>
ꢃϭ
ꢃϮ
ꢃ
>ϭ
ꢂW
ď
Ğ
76623ꢃ$0B9ꢁ
1. Drawing
is not to scale.
/
Table 86. TSSOP8 – 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch,
package mechanical data
millimeters
Min
inches
(1)
Symbol
Typ
Max
Typ
Min
Max
A
A1
A2
b
–
–
1.200
0.150
1.050
0.300
0.200
0.100
3.100
–
–
–
0.0472
0.0059
0.0413
0.0118
0.0079
0.0039
0.1220
–
0.050
0.800
0.190
0.090
–
–
0.0020
0.0315
0.0075
0.0035
–
–
0.0394
–
1.000
–
c
–
–
CP
D
–
–
2.900
–
3.000
0.650
6.400
4.400
0.600
1.000
0.1142
–
0.1181
0.0256
0.2520
0.1732
0.02636
0.0394
–
e
E
6.200
4.300
0.450
–
6.600
4.500
0.750
–
0.2441
0.1693
0.0177
–
0.2598
0.1772
0.0295
–
E1
L
L1
α
0°
8°
0°
8°
1. Values
in inches are converted from mm and rounded to four decimal digits.
DS9985 Rev 12
81/88
84
Package information
M24SR02-Y
15.3
UFDFPN8 package information
Figure 23. UFDFPN8 – 8-lead, 2 x 3 mm, 0.5 mm pitch ultra thin profile fine pitch
dual flat package outline
$
‘
%
1
$
$ꢂ
FFF
ꢂ
3LQꢄꢐꢂꢄ
,’ꢄPDUNLQJ
&
(
HHH
&
6HDWLQJꢄSODQH
$ꢀ
6LGHꢄYLHZ
DDD
&
ꢁ[
ꢂ
ꢁ
ꢁ[
DDD
&
7
R
SꢄYLHZ
‘ꢁ
H
‘DWXPꢄ$
E
ꢂ
ꢁ
/ꢂ
/ꢀ
3LQꢄꢐꢂꢄ
/
/ꢀ
(ꢁ
.
,’ꢄPDUNLQJ
Hꢅꢁ
/ꢂ
7
H
UPLQDOꢄWLS
H
‘HWDLOꢄ³$´
/
(YHQꢄWHUPLQDO
1’ꢋꢂꢄ
[
H
%RWWRPꢄYLHZ
6HHꢄ’HWDLOꢄ³$´
=:EB0(B9ꢂ
1. Max
package warpage is 0.05 mm.
2. Exposed
copper is not systematic and can appear partially or totally according to the cross section.
3. Drawing
is not to scale.
4. The
central pad (the area E2 by D2 in the above illustration) must be either connected to V
SS
or left floating
(not connected) in the end application.
82/88
DS9985 Rev 12
M24SR02-Y
Package information
Table 87. UFDFPN8 – 8- lead, 2 x 3 mm, 0.5 mm pitch ultra thin profile fine pitch
dual flat package mechanical data
millimeters
Typ
inches
(1)
Symbol
Min
Max
Min
Typ
Max
A
0.450
0.550
0.600
0.050
0.300
2.100
1.600
3.100
1.600
–
0.0177
0.0217
0.0236
0.0020
0.0118
0.0827
0.0630
0.1220
0.0630
–
A1
0.000
0.020
0.0000
0.0008
b
(2)
0.200
0.250
0.0079
0.0098
D
1.900
2.000
0.0748
0.0787
D2 (rev MC)
1.200
–
0.0472
–
E
2.900
3.000
0.1142
0.1181
E2 (rev MC)
1.200
–
0.0472
–
e
K (rev MC)
L
–
0.500
–
0.0197
0.300
–
–
–
–
–
–
–
–
–
–
0.0118
–
–
–
–
–
–
–
–
–
–
0.300
0.500
0.150
–
0.0118
0.0197
0.0059
–
L1
–
–
L3
0.300
0.0118
aaa
–
–
–
–
–
0.150
0.100
0.100
0.050
0.080
–
–
–
–
–
0.0059
0.0039
0.0039
0.0020
0.0031
bbb
ccc
ddd
eee
(3)
1. Values
in inches are converted from mm and rounded to four decimal digits.
2. Dimension
b applies to plated terminal and is measured between 0.15 and 0.30 mm from the terminal tip.
3. Applied
for exposed die paddle and terminals. Exclude embedded part of exposed die paddle from
measuring.
DS9985 Rev 12
83/88
84
Ordering information
M24SR02-Y
16
Ordering information
Example:
M24 SR
02- Y
MN
6
T
/2
Device type
M24 = I
2
C interface device
Device feature
SR = Short range
Memory size
02 = memory size in Kbits
Voltage range
Y = 2.7 to 5.5 V
Package
MN = SO8N
DW = TSSOP8
MC = UFDFPN8
SG12I = 120 µm ± 15 µm bumped and sawn inkless wafer on 8-inch frame
U = unsawn wafer 725 µm ± 20 µm
Device grade
6 = industrial: device tested with standard test flow over –40 to 85 °C
(no parameter for SG12I)
Option
T =
T
a
pe and reel packing
(no parameter for SG12I)
Capacitance
/2 = 25 pF
Note:
Parts marked as “ES”, “E” or accompanied by an Engineering Sample notification letter, are
not yet qualified and therefore not approved for use in production. ST is not responsible for
any consequences resulting from such use. In no event will ST be liable for the customer
using any of these engineering samples in production. ST Quality has to be contacted prior
to any decision to use these Engineering samples to run qualification activity.
84/88
DS9985 Rev 12
M24SR02-Y
Revision history
17
Revision history
Table 88. Document revision history
Changes
Date
Revision
29-Oct-2013
1
Initial release.
09-Nov-2013
2
Changed the datasheet status from “Preliminary data” to “Production
data”.
VCC
.
20-Dec-2013
3
file
.
28-Feb-2014
4
ultra thin profile fine pitch dual flat package outline
title: UFDPFN8
changed into UFDFPN8.
DS9985 Rev 12
85/88
87
Revision history
M24SR02-Y
Table 88. Document revision history (continued)
Revision Changes
Date
Added WFDFPN8 package for automotive grade under qualification
Added
Figure 24: WFDFPN8 (MLP8) 8-lead, 2 x 3 mm, 0.5 mm pitch
very thin fine pitch dual flat package outline
04-Jun-2014
5
Added
T
a
ble 88: WFDFPN8 8-lead thin fine pitch dual flat package no
lead mechanical data
Added MF = WFDFPN8 inside
Table 88: Ordering information scheme
for packaged devices
Added
Updated:
04-May-2016
6
Updated:
08-Aug-2016
7
Updated:
04-Oct-2016
23-Nov-2016
8
9
Updated:
86/88
DS9985 Rev 12
M24SR02-Y
Revision history
Table 88. Document revision history (continued)
Revision Changes
Date
Added:
07-Feb-2017
10
Updated:
–
T
a
ble 88: Ordering information scheme for packaged devices
Updated:
02-Oct-2017
11
–
T
a
ble 88: Ordering information scheme for packaged devices
04-Apr-2019
12
Minor text edits across the whole document.
DS9985 Rev 12
87/88
87
M24SR02-Y
IMPORTANT NOTICE – PLEASE READ CAREFULLY
STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, enhancements, modifications, and
improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on
ST products before placing orders. ST products are sold pursuant to ST’s terms and conditions of sale in place at the time of order
acknowledgement.
Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or
the design of Purchasers’ products.
No license, express or implied, to any intellectual property right is granted by ST herein.
Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.
ST and the ST logo are trademarks of S
T
.
F
or additional information about ST trademarks, please refer to
www.st.com/trademarks
.
All other
product or service names are the property of their respective owners.
Information in this document supersedes and replaces information previously supplied in any prior versions of this document.
© 2019 STMicroelectronics – All rights reserved
88/88
DS9985 Rev 12
