M24SR04-G_技术文档

M24SR04-Y

M24SR04-G

Dynamic NFC/RFID tag IC with 4-Kbit EEPROM,

NFC Forum Type 4 Tag and I²C interface

Datasheet - production data

• Read up to 246 bytes in a single command

• Write up to 246 bytes in a single command

• 7 bytes unique identifier (UID)

• 128 bits passwords protection

TSSOP8

(DW)

UFDFPN8

SO8

(MN)

(MC)

Package

• 8-lead small-outline package (SO8)

®

ECOPACK2

®

• TSSOP8 ECOPACK2

®

• UFDFPN8 ECOPACK2

WFDFPN8

(MF)

®(2)(3)

• WFDFDN8 ECOPACK2

Wafer

Digital pad

Features

• GPO: configurable General Purpose Output

I²C interface

• RF disable: activation/deactivation of RF

commands

2

• Two-wire I C serial interface supports

1 MHz protocol

Temperature range

• Single supply voltage:

• From - 40 °C up to 85 °C

– 2.7 V to 5.5 V for grade Y

(1)

– 2.4 V to 5.5 V for grade G

Description

Contactless interface

M24SR04 belongs to the ST25 family which

includes all STMicroelectronics NFC/RFID tag and

reader products.

• NFC Forum Type 4 Tag

• ISO/IEC 14443 Type A

• 106 Kbps data rate

The M24SR04 devices is a dynamic NFC/RFID

tag IC with a dual interface. It embeds an

• Internal tuning capacitance: 25 pF

2

EEPROM memory. It can be operated from an I C

interface or by a 13.56 MHz RFID reader or an

NFC phone.

Memory

• 512-byte (4-kbit) EEPROM

• Support of NDEF data structure

• Data retention: 200 years

2

The I C interface uses a two-wire serial interface,

consisting of a bidirectional data line and a clock

2

line. It behaves as a slave in the I C protocol.

• Write cycle endurance:

The RF protocol is compatible with ISO/IEC

14443 Type A and NFC Forum Type 4 Tag.

– 1 million Write cycles at 25 °C

– 600k Write cycles at 85 °C

2. Preliminary data for automotive grade (under

qualification).

1. Limited temperature range -25 to 85 °C

3. Package for automotive grade.

February 2017

DocID024754 Rev 15

1/90

This is information on a product in full production.

www.st.com

Contents

M24SR04-Y M24SR04-G

Contents

1

2

Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1

Functional modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.1.1

1.1.2

1.1.3

I2C mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Tag mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Dual interface mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1

2.2

2.3

2.4

2.5

Serial clock (SCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Serial data (SDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Antenna coil (AC0, AC1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Ground (VSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Supply voltage (V_CC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.5.1

2.5.2

2.5.3

2.5.4

Operating supply voltage V

CC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Power-up conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Device reset in I²C mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Power-down conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.6

2.7

RF disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

General purpose output (GPO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.7.1

2.7.2

2.7.3

2.7.4

Session Open configuration (GPO field = 0xX1 or 0x1X) . . . . . . . . . . . 14

WIP Writing in Progress configuration (GPO field = 0xX2 or 0x2X) . . . 15

2

I C answer ready configuration (GPO field = 0xX3) . . . . . . . . . . . . . . . 16

MIP NDEF Message writing in Progress configuration

(GPO field = 0x3X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.7.5

2.7.6

2.7.7

INT Interrupt configuration (GPO field = 0xX4 or 0x4X) . . . . . . . . . . . . 18

State Control configuration (GPO field = 0xX5 or 0x5X) . . . . . . . . . . . . 19

RF busy configuration (GPO field = 0x6X) . . . . . . . . . . . . . . . . . . . . . . . 20

3

M24SR04 memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.1

Memory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.1.1

3.1.2

3.1.3

3.1.4

File identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

CC file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

NDEF file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

System file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2

Read and write access rights to the memory . . . . . . . . . . . . . . . . . . . . . . 25

2/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Contents

3.2.1

3.2.2

3.2.3

State of the Read and Write access rights . . . . . . . . . . . . . . . . . . . . . . . 25

Changing the read access right to NDEF files . . . . . . . . . . . . . . . . . . . . 26

Changing the write access right to NDEF files . . . . . . . . . . . . . . . . . . . 27

3.3

3.4

3.5

Access right life time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

NDEF file passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

I2C password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.5.1

I²C password and I²C protect field of the System file . . . . . . . . . . . . . . . 28

4

5

Communication mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.1

4.2

Master and slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

M24SR04 session mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.2.1

4.2.2

RF token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2

I C token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

I²C and RF command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.1

5.2

Structure of the command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.2.1

5.2.2

C-APDU: payload format of a command . . . . . . . . . . . . . . . . . . . . . . . . 32

R-APDU: payload format of a response . . . . . . . . . . . . . . . . . . . . . . . . 33

5.3

5.4

5.5

5.6

R-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

S-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

CRC of the I2C and RF frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

NFC Forum Type 4 Tag protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.6.1

5.6.2

5.6.3

5.6.4

5.6.5

5.6.6

5.6.7

5.6.8

Commands set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Status and error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . 38

Capability Container Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 38

NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

System File Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5.7

ISO/IEC 7816-4 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.7.1

5.7.2

5.7.3

5.7.4

Verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Change Reference Data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Enable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . . 45

Disable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . 46

DocID024754 Rev 15

3/90

5

Contents

M24SR04-Y M24SR04-G

5.8

ST Proprietary command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.8.1

5.8.2

5.8.3

5.8.4

5.8.5

5.8.6

ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

EnablePermanentState command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

DisablePermanentState command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

UpdateFileType command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

SendInterrupt command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

StateControl command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.9

Specific RF command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.9.1

5.9.2

5.9.3

Anticollision command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

RATS command and ATS response . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

PPS command & response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.10 Specific I²C command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.10.1 GetI2Csession command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.10.2 KillRFsession command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

6

7

RF device operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

6.1

6.2

6.3

6.4

Anticollision and Device Activation command set for the RF interface . . 56

Open an RFsession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Close an RFsession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Applicative command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

I2C device operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7.1

7.2

7.3

7.4

7.5

7.6

7.7

7.8

7.9

I2C communication protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Stop condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

I²C token release sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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.9.1

Example of I²C frame commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

7.10 Open an I²C session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

7.11 Close the I²C session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Contents

8

Functional procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

8.1

8.2

8.3

8.4

8.5

8.6

8.7

8.8

8.9

Selection of an NDEF message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Reading of an NDEF message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Reading a locked NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Locking an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Unlocking an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Reaching the read-only state for an NDEF file . . . . . . . . . . . . . . . . . . . . . 64

Changing an NDEF password procedure . . . . . . . . . . . . . . . . . . . . . . . . . 64

Changing a File type Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Updating a NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

9

UID: Unique identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

10

11

I2C DC and AC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

11.1 I2C timing measurement condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

12

13

14

15

GPO parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Write cycle definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

RF electrical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

15.1 SO8N package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

15.2 TSSOP8 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

15.3 UFDFPN8 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

15.4 WFDFPN8 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

16

17

Part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

DocID024754 Rev 15

5/90

5

List of tables

M24SR04-Y M24SR04-G

List of tables

Table 1.

Table 2.

Table 3.

Table 4.

Table 5.

Table 6.

Table 7.

Table 8.

Signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Functional mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

File identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

CC file layout for 1 NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

NDEF file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Field list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Details about I2C watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Details about the GPO field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Details about the RF Session field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Details about the ST reserved field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Details about the RF enable field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Read access right. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Write access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

RF and I²C command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

PCB field of the I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

C-APDU format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

R-APDU format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

R-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

R-Block detailed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

S-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

S-Block detailed format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Command set overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Status code of the M24SR04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Error code of the M24SR04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

C-APDU of the NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 38

R-APDU of the NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 38

C-APDU of the Capability Container Select command. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

R-APDU of the Capability Container Select command. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

C-APDU of the NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

R-APDU of the NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

C-APDU of the System File Select command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

R-APDU of the System File Select command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

C-APDU of the ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

R-APDU of the ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

C-APDU of the UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

R-APDU of the UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Verify command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

R-APDU of the Verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Change reference data command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

R-APDU of the Change Reference Data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Enable Verification Requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

R-APDU of the Enable Verification Requirement command. . . . . . . . . . . . . . . . . . . . . . . . 46

Disable Verification Requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

R-APDU of the Disable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . . . 47

C-APDU of the ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

R-APDU of the ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

EnablePermanentState command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Table 9.

Table 10.

Table 11.

Table 12.

Table 13.

Table 14.

Table 15.

Table 16.

Table 17.

Table 18.

Table 19.

Table 20.

Table 21.

Table 22.

Table 23.

Table 24.

Table 25.

Table 26.

Table 27.

Table 28.

Table 29.

Table 30.

Table 31.

Table 32.

Table 33.

Table 34.

Table 35.

Table 36.

Table 37.

Table 38.

Table 39.

Table 40.

Table 41.

Table 42.

Table 43.

Table 44.

Table 45.

Table 46.

Table 47.

Table 48.

6/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

List of tables

Table 49.

Table 50.

Table 51.

Table 52.

Table 53.

Table 54.

Table 55.

Table 56.

Table 57.

Table 58.

Table 59.

Table 60.

Table 61.

Table 62.

Table 63.

Table 64.

Table 65.

Table 66.

Table 67.

Table 68.

Table 69.

Table 70.

Table 71.

Table 72.

Table 73.

Table 74.

Table 75.

Table 76.

Table 77.

Table 78.

Table 79.

Table 80.

Table 81.

Table 82.

Table 83.

Table 84.

Table 85.

R-APDU table of the EnablePermanentState command . . . . . . . . . . . . . . . . . . . . . . . . . . 48

DisablePermanentState command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

R-APDU of the DisablePermanentState command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

UpdateFileType command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

R-APDU of the UpdateFileType command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

SendInterrupt command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

R-APDU of the SendInterrupt command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

StateControl command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

R-APDU of the StateControl command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Commands issues by the RF host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

RATS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Conversion from FDSI to FSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

ATS response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

PPS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Ascending and descending data rate coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

PPS response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Specific I²C commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

GetI2Csession command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

KillRFsession command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

I2C device address format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

2

I C frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

I2C host to M24SR04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

M24SR04 to I2C host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

UID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

2

I C operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

AC test measurement conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Input parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

2

I C DC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

2

I C AC characteristics (400 kHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

2

I C AC characteristics (1 MHz). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Device select code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

GPO timings measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Write cycle definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Default operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

RF characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

SO8N - 8-lead plastic small outline, 150 mils body width,

package data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

TSSOP8 - 8-lead thin shrink small outline, 169 mils width, package data . . . . . . . . . . . . . 81

UFDFPN8 - 8- lead, 2 x 3 mm, 0.5 mm pitch ultra thin profile fine pitch

Table 86.

Table 87.

dual flat package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

WFDFPN8 8-lead thin fine pitch dual flat package no lead

Table 88.

mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Ordering information scheme for packaged devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Table 89.

Table 90.

DocID024754 Rev 15

7/90

7

List of figures

M24SR04-Y M24SR04-G

List of figures

Figure 1.

Figure 2.

Figure 3.

Figure 4.

Figure 5.

Figure 6.

Figure 7.

Figure 8.

Figure 9.

M24SR04 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

8-pin package connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

GPO configured as Session Open (GPO field = 0xX1 or 0x1X). . . . . . . . . . . . . . . . . . . . . 14

GPO configured as WIP (GPO field = 0xX2 or 0x2X). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2

GPO configured as I C answer ready (GPO field = 0xX3) . . . . . . . . . . . . . . . . . . . . . . . . . 16

GPO configured as MIP (GPO field = 0x3X). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

GPO configured as INT (GPO field = 0xX4 or 0x4X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

GPO configured as State Control (GPO field = 0xX5 or 0x5X). . . . . . . . . . . . . . . . . . . . . . 19

GPO configured as RF busy (GPO field = 0x6X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 10. Changing the read access right to an NDEF file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 11. Changing the write access right to an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

2

Figure 16. I C AC waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 17. Maximum Rbus value with fC = 400 kHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 18. Maximum Rbus value with fC = 1 MHz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Figure 19. I2C bus protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Figure 20. SO8N - 8-lead plastic small outline, 150 mils body width, package outline . . . . . . . . . . . . 79

Figure 21. SO8N - 8-lead plastic small outline, 150 mils bosy width,

package recommended footprint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Figure 22. TSSOP8 - 8-lead thin shrink small outline, 3 x 4 mm, 0.5 mm pitch

package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Figure 23. UFDFPN8 - 8-lead, 2 x 3 mm, 0.5 mm pitch ultra thin profile fine pitch

dual flat package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Figure 24. WFDFPN8 (MLP8) 8-lead, 2 x 3 mm, 0.5 mm pitch very thin fine pitch

dual flat package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

8/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Functional description

1

Functional description

2

The M24SR04 device is a dynamic NFC/RFID tag that can be accessed either from the I C

2

or the RF interface. The RF and I C host can read or write to the same memory, that is why

only one host can communicate at a time with the M24SR04. The management of the

interface selection is controlled by the M24SR04 device itself.

The RF interface is based on the ISO/IEC 14443 Type A standard. The M24SR04 is

compatible with the NFC Forum Type 4 Tag 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 M24SR04 device.

Figure 1. M24SR04 block diagram

6XSSO\ꢄYROWDJH

9_&&

ꢁ

IRUꢄ,^ꢄꢄ&ꢄLQWHUIDFH

h/ꢀꢁΘꢁƐǇƐƚĞŵꢁꢁꢁꢁ

ĂƌĞĂ

3RZHUꢄꢄꢄꢄ

PDQDJHPHQWꢄꢄꢄꢄ

XQLW

$QDORJꢄ)URQWꢋHQGꢄ

EDVHGꢄRQꢄ

5)ꢄLQWHUIDFHꢄꢄ

EDVHGꢄRQꢄ

,62ꢅ,(&ꢄꢂꢆꢆꢆꢀꢄ

7\SHꢄ$ꢄVWDQGDUG

$&ꢂ

$&ꢊ

,62ꢅ,(&ꢄꢂꢆꢆꢆꢀꢄ

7\SHꢄ$ꢄ

,QWHUQDOꢄWXQLQJ

FDSDFLWDQFHꢄꢄ

VWDQGDUG

1)&ꢄ)RUXPꢄ

7\SHꢄꢆꢄ7DJꢄ

SURWRFRO

5)ꢄ

GLVDEOH

hƐĞƌꢁŵĞŵŽƌǇ

*32

'LJLWDOꢄXQLW

6&/

6'$

,^ꢁ&ꢄLQWHUIDFH

ꢁꢇꢈꢄ9ꢄ±ꢄꢉꢇꢉꢄ9

1)&B,ꢁ&

LQWHUIDFH

*1'

06ꢀꢁꢀꢂꢃ9ꢀ

DocID024754 Rev 15

9/90

20

Functional description

M24SR04-Y M24SR04-G

Direction

Table 1. Signal names

Function

Signal name

SDA

Serial data

I/O

SCL

Serial clock

Input

AC0, AC1

V_CC

Antenna coils

-

Supply voltage

-

VSS

Ground

-

GPO

Interrupt output ⁽¹⁾

Disable the RF communication ⁽²⁾

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_ccis above its POR level.

Figure 2. 8-pin package connections

ꢂ

ꢁ

ꢀ

ꢆ

ꢃ

ꢈ

ꢌ

ꢉ

5)ꢄGLVDEOH

$&ꢊ

9_&&

*32

6&/

6'$

$&ꢂ

9₆₆

06ꢀꢊꢈꢆꢆ9ꢁ

1. See Package mechanical data section for package dimensions, and how to identify pin 1.

1.1

Functional modes

The M24SR04 has two functional modes available. The difference between the modes lies

in the power supply source (see Table 2).

Table 2. Functional mode

Mode

I²C mode

Supply source

Comments

V_cc

The I²C interface is available

Tag mode

RF field only

The ²C interface is disconnected

Both I²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

M24SR04 is powered by V . The I C interface is connected to the M24SR04. The I C host

can communicate with the M24SR04 device.

CC

Tag mode

The M24SR04 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/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Functional description

1.1.3

Dual interface mode

2

Both interfaces, RF and I C, are connected to the M24SR04 and both RF or I C host can

communicate with the M24SR04 device. The power supply and the access management

are carried out by the M24SR04 itself. For further details, please refer to the token

mechanism chapter.

DocID024754 Rev 15

11/90

20

Signal descriptions

M24SR04-Y M24SR04-G

2

Signal descriptions

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

(SCL) to V . (Figure 17 indicates how the value of the pull-up resistor can be calculated).

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

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

pull-up resistor must be connected from Serial data (SDA) to V . (Figure 17 indicates how

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, even 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

M24SR04.

CC

Operating supply voltage V

CC

Prior to selecting the M24SR04 and issuing instructions to it, a valid and stable V voltage

CC

within the specified [V (min), V (max)] range must be applied. To maintain a stable DC

CC

supply voltage, it is recommended to decouple the V line with suitable capacitors (usually

CC

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/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Signal descriptions

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 1V/µs.

CC

SS

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 M24SR04 does not respond to

CC

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

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

within the specified [V (min), V (max)] range.

CC

In a similar way, during power-down (continuous decrease in V ), as soon as V drops

CC

below the power-on reset threshold voltage, the M24SR04 stops responding to any

instruction sent to it.

2.5.4

Power-down conditions

During power-down (continuous decay of V ), the M24SR04 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 shall

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 shall 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.

DocID024754 Rev 15

13/90

20

Signal descriptions

M24SR04-Y M24SR04-G

(1)

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 M24SR04 is executing a writing operation.

2

INT (interrupt): the I C or RF host can force the M24SR04 to send a negative pulse on

the GPO pin.

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 M24SR04.

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

session is ongoing (see Figure 3).

An RF session is taken when M24SR04 receives a valid Select Application. The session is

released after M24SR04 has received a valid Deselect command, if M24SR04 has received

2

a Kill RF session command in I C or when the RF field became OFF.

2

An I C session is taken when M24SR04 receives a valid Get session command or a valid

2

Kill RF session command. The session is released after M24SR04 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)

1. See Table 81 for more details.

14/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Signal descriptions

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 M24SR04 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ƉĚĂƚĞꢁ

ĐŽŵŵĂŶĚ

ꢄŶĚꢁŽĨꢁǁƌŝƚŝŶŐꢁ

ŽƉĞƌĂƚŝŽŶ

ꢃŶǇꢁŽƚŚĞƌꢁ

ĐŽŵŵĂŶĚ

'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

DocID024754 Rev 15

15/90

20

Signal descriptions

2

M24SR04-Y M24SR04-G

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

M24SR04 has finished to treat the I C command and is ready to send the I C response.

2

During an I C session, after receiving a valid I C command, GPO pin is driven low after a

2

delay when M24SR04 is ready to deliver a response on the I C bus.

GPO is released when M24SR04 receives a new command.

2

Figure 5. GPO configured as I C answer ready (GPO field = 0xX3)

/ϸꢂꢁĐŚĂŶŶĞů

KƉĞŶꢁ

^ĞƐƐŝŽŶ

ꢃŶǇꢁ/ϸꢂꢁ

ĐŽŵŵĂŶĚ

DϮϰ^Zǆǆꢁ

ƌĞƐƉŽŶƐĞ

ꢃŶǇꢁ/ϸꢂꢁ

ĐŽŵŵĂŶĚ

DϮϰ^Zǆǆꢁ

ƌĞƐƉŽŶƐĞ

ꢃŶǇꢁ/ϸꢂꢁ

ĐŽŵŵĂŶĚ

DϮϰ^Zǆǆꢁ

ƌĞƐƉŽŶƐĞ

'WKꢁĂƐꢁ/ϸꢂꢁ

ĂŶƐǁĞƌꢁƌĞĂĚǇ

D^ϯϬϳϴϴsϰ

16/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Signal descriptions

2.7.4

MIP NDEF Message writing in Progress configuration

(GPO field = 0x3X)

When the GPO is configured as MIP, its state goes to the low state when the RF host writes

the NDEF length to another value than 0x0000.

During an RF session, when M24SR04 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Ϯϰ^Zǆǆꢁ

ƌĞƐƉŽŶƐĞ

ꢃŶǇꢁŽƚŚĞƌꢁ

ĐŽŵŵĂŶĚ

'WKꢁĂƐꢁD/W

;ϭͿ

;ϮͿ

D^ϯϬϳϴϱsϯ

1. CmdEOFtoGPlow (RF command End of frame to GPO low)

2. Writing time duration

DocID024754 Rev 15

17/90

20

Signal descriptions

M24SR04-Y M24SR04-G

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 M24SR04

response.

2

During an RF or I C session, when M24SR04 receives a valid Interrupt command,

M24SR04 GPO pin is driven low after (1) or (3) for a duration of (4) in RF, or after

responding in I2C (2). Then GPO pin is released.

Figure 7. GPO configured as INT (GPO field = 0xX4 or 0x4X)

Z&ꢁŽƌꢁ/ϸꢂꢁ

ĐŚĂŶŶĞů

;ϭͿꢁ

Žƌꢁ

;ϯͿ

;ϮͿꢁꢁ

DϮϰ^Zǆǆꢁ

ƌĞƐƉŽŶƐĞ

^ĞŶĚꢁ

/ŶƚĞƌƌƵƉƚ

ꢃŶǇꢁŽƚŚĞƌꢁ

ŽƉĞƌĂƚŝŽŶ

'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/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Signal descriptions

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 M24SR04 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)

DocID024754 Rev 15

19/90

20

Signal descriptions

M24SR04-Y M24SR04-G

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

M24SR04 is processing an RF command or when an RFsession is ongoing.

When an RF field is present, GPO is driven low after a delay (1) when M24SR04 detects the

first command. If the RF session is ongoing and M24SR04 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&ꢁďƵƐǇ

D^ϯϬϳϵϬsϯ

1. CmdSOFtoGPlow (RF command Start of frame to GPO low)

2. CmdEOFtoGPHZ (RF command End of frame to GPO HZ)

20/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

M24SR04 memory management

3

M24SR04 memory management

3.1

Memory structure

The M24SR04 supports the NDEF Tag Application as defined in the NFC Forum Type 4

Tag. The M24SR04 is composed of three files:

•

One Capability Container file

One NDEF file

One System file: this is an ST-proprietary file

The System file contains some information on the configuration of the M24SR04 device.

The CC file gives some information about the M24SR04 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 some information about the M24SR04 and the NDEF file. This file 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

issuing a specific process (refer to Section 8: Functional procedures).

DocID024754 Rev 15

21/90

28

M24SR04 memory management

File offset

M24SR04-Y M24SR04-G

Table 4. CC file layout for 1 NDEF file

Meaning

Value

Comments

15 bytes

0x0000

0x0002

0x0003

0x0005

0x0007

0x0008

0x0009

Number of bytes of CC file

Mapping version⁽¹⁾

Maximum number of bytes that can be read

0x000F

0x20 or 0x10

0x00F6

V 2.0 or V 1.0

246 bytes

T field

Maximum number of bytes that can be written 0x00F6

0x04 ⁽²⁾

0x06

L field

0x0001

FileID

NDEF file control TLV

0x0200

Maximum NDEF

file size

0x000B

0x000D

0x000E

0x00 ⁽²⁾

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 shall

be managed by the application and the M24SR04 device does not check if its value is

relevant vs the data written by the RF or I²C host. The M24SR04 device uses the NDEF

Message Length, e. g. the standard read can be processed only inside the NDEF message;

otherwise, the M24SR04 device returns an error code. For more details about the read

command, refer to Section 5.6.7: ReadBinary command.

22/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

M24SR04 memory management

Table 5. NDEF file layout

Byte 0 Byte 1

NDEF message length

File offset

Byte 2

Byte 3

0x0000

0x0004

...

User data

...

0x01FC

User data

3.1.4

System file layout

The system file specifies the configuration of the M24SR04. Table 6 lists the different fields.

Table 6. Field list

Numberof

File offset

Field name

Read access Write access

Delivery state ⁽¹⁾

bytes

0x0000

0x0002

0x0003

0x0004

0x0005

0x0006

Length system file

I²C protect

2

1

I²C or RF

-

0x0012

0x01

I²C ⁽²⁾

I²C watchdog

GPO

0x00

0x11

ST reserved

RF enable

0x00

0x xxxx xxx1⁽³⁾

NDEF File

number (RFU)

0x0007

0x0008

1

7

I²C or RF

none

0x00

0x0286 xx xx xx xx

xxor 0x028E xx xx xx

xx xx^{(4) (5)}

UID

0x000F

0x0011

Memory Size

Product Code

2

1

I²C or RF

none

0x01FF

0x86 or 0x8E⁽⁵⁾

1. The delivery state for all passwords = 0x00000000000000000000000000000000.

2. The access is granted when the field I²C protect is set to the state Unprotected or when the right I²C

password was correctly received (see Section 3.5: I2C password).

3. Refer Table 11.

4. x values are defined by ST to insure UID unicity.

5. Automotive grade

DocID024754 Rev 15

23/90

28

M24SR04 memory management

File offset

M24SR04-Y M24SR04-G

Table 7. Details about I2C watchdog

b7- b0

The “I²C Watchdog” ensures the I2C host will not keep the session open, while

there is no more activity on the I²C bus (between the stop bit of the previous

transaction and the start bit of the next one)

0x0003

– 0x00 (default value): the Watchdog is off

– Other values: If programmed to a non null value N, the Watchdog is enabled

and counts N*30 ms (30 ms is approximate) before releasing the I²C session.

Table 8. Details about the GPO field

File offset

b7

b6-b4

b3

b2-b0

0x0004

RFU

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

Table 9. Details about the RF Session field

File offset

0x0004

b7

b6-b4

b3-b0

RFU

When an RF session is open:

0b001: Session opened

RFU

24/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

M24SR04 memory management

Table 10 gives some details about the ST reserved field.

Table 10. Details about the ST reserved field

File offset b7-b0

0x0005

0x00

Table 11 gives some details about the RF enable field.

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: the RF field is on ⁽¹⁾

RFU

0: the RF disable pad is at low state ⁽¹⁾

1: the RF disable pad is at high state ⁽¹⁾

RFU

0: the M24SR04 does not decode the command received from the RF interface

1: the M24SR04 decodes the command received from the RF interface

1. this field is written by the M24SR04.

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 shall 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 shall be sent to the M24SR04 device before reading a read-locked

NDEF file.

The write password shall be present on the M24SR04 device before writing a write-locked

NDEF file. The write password shall 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

file. For more details, refer to Section 3.1.2: CC file layout.

DocID024754 Rev 15

25/90

28

M24SR04 memory management

Value

M24SR04-Y M24SR04-G

Table 12. Read access right

Meaning

0x00

0x80

0xFE

Read access without any security

Locked ⁽¹⁾

Read not authorized

1. The read password shall be sent before reading in the NDEF file.

Table 13. Write access right

Value

Meaning

0x00

0x80

0xFF

Write access without any security

Locked ⁽¹⁾

Write not authorized

1. The write password shall be sent before writing in the NDEF file.

The state 0xFF and 0xFE cannot be changed by using the Read or Write passwords.

3.2.2

Changing the read access right to NDEF files

The state diagram on Figure 10 shows how to change the access right to read an NDEF file.

Figure 10. Changing the read access right to an NDEF file

ϬǆϬϬ

>ŽĐŬꢁƚŚĞꢁEꢀꢄ&ꢁĨŝůĞꢁ^;ϭͿ

hŶůŽĐŬꢁƚŚĞꢁEꢀꢄ&ꢁĨŝůĞꢁ^;ϮͿ

WĞƌŵĂŶĞŶƚůǇꢁůŽĐŬꢁƚŚĞꢁEꢀꢄ&ꢁĨŝůĞꢁ^;ϯͿ

ϬǆϴϬꢁ^;ϰͿ

Ϭǆ&ꢄꢁ^;ϰͿ

WĞƌŵĂŶĞŶƚůǇꢁƵŶůŽĐŬꢁƚŚĞꢁEꢀꢄ&ꢁĨŝůĞ

D^ϯϬϳϳϮsϰ

1. See the procedure to lock the read access (Section 8.4: Locking an NDEF file).

2. See the procedure to unlock the read access (Section 8.5: Unlocking an NDEF file).

3. See the procedure to permanently lock the read access (Section 8.6: Reaching the read-only state for an

NDEF file).

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).

26/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

M24SR04 memory management

3.2.3

Changing the write access right to NDEF files

The state diagram on Figure 11 shows how to change the write access right to an NDEF file.

Figure 11. Changing the write access right to an NDEF file

ϬǆϬϬ

>ŽĐŬꢁƚŚĞꢁEꢀꢄ&ꢁĨŝůĞꢁ^;ϭͿ

hŶůŽĐŬꢁƚŚĞꢁEꢀꢄ&ꢁĨŝůĞꢁ^;ϮͿ

WĞƌŵĂŶĞŶƚůǇꢁůŽĐŬꢁƚŚĞꢁEꢀꢄ&ꢁĨŝůĞꢁ^;ϯͿ

ϬǆϴϬꢁ^;ϰͿ

Ϭǆ&&

WĞƌŵĂŶĞŶƚůǇꢁƵŶůŽĐŬꢁƚŚĞꢁEꢀꢄ&ꢁĨŝůĞ

D^ϯϬϳϳϯsϰ

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

NDEF file).

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 0xFF (permanently locked).

0x80 might not be fully decoded with 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).

DocID024754 Rev 15

27/90

28

M24SR04 memory management

M24SR04-Y M24SR04-G

3.5

I²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

For more details about the system file layout, refer to Section 3.1.4: System file layout.

28/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Communication mechanism

4

Communication mechanism

2

This chapter describes the principle of communication between an RF or an I C host and

the M24SR04 device.

4.1

Master and slave

2

The M24SR04 acts as a slave device on either the I C-bus or the RF channel and therefore

2

waits for a command from the I C master or the RF host before sending its response.

The RF host shall generate the RF field and the RF commands.

2

The I C host shall supply the M24SR04 through the V pin and shall generate the I C

CC

clock on the SCL pad.

4.2

M24SR04 session mechanism

2

The M24SR04 is a dynamic NFC/RFID tag which can be accessed either from the RF or I C

interface. The M24SR04 implements a token system. This token has two possible values,

2

RF or I C. When the token exists and is assigned to one interface (RF or I C), the M24SR04

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

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

I C token release sequence from the I C host, after which M24SR04 goes in Standby power

mode.

DocID024754 Rev 15

29/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

5

I²C and RF command sets

The command sets of the M24SR04 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 M24SR04 command sets that can be issued by the RF or the I²C host.

There are three command families:

•

the NFC Forum Type 4 Tag command set

the ISO/IEC 7816-4 command set

the proprietary command set

The NFC Forum Type 4 Tag command set and the ISO/IEC 7816-4 command set use the I-

Block format. For more details about the I-Block format, refer to Section 5.2: I-Block format.

Two other command formats exist:

•

the commands using the R-Block format

the commands using the S-Block format

For more details about these formats, refer to the corresponding sections: Section 5.3: R-

Block format and Section 5.4: S-Block format.

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 lists the RF and I²C command sets.

Table 14. RF and I²C command sets

Family

command set

Class Instruction

Command name

Brief description

byte

code

NDEF Tag Application

Select

NDEF Tag Application Select

0x00

0xA4

CC select

0x00

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 Tag

Write or erase data to a

NDEF file

UpdateBinary

Verify

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

30/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

Table 14. RF and I²C command sets (continued)

Class Instruction

Family

command set

Command name

Brief description

byte

code

Enables the Read Only or

Write Only security state

ST Proprietary EnablePermanentState

ST Proprietary ExtendedReadBinary

0xA2

0x28

0xB0

Read data from file

5.1

Structure of the command sets

The exchange of data between the RF or the I²C host and the M24SR04 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 M24SR04. It is

composed of three fields. Table 15 details the I-Block format.

Table 15. I-Block format

SoD

Payload

0

EoD

CRC

Name

PCB

DID

Length

1 byte

1 to 251 bytes

2 bytes

PCB field

DID field (optional)

RF or I²C host to M24SR04: C-APDU

M24SR04 to RF or I²C host: R-APDU

2 CRC bytes

DocID024754 Rev 15

31/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

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 M24SR04 the format of the payload is the

C-APDU.

When the M24SR04 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 M24SR04.

Table 17 describes its format.

Table 17. C-APDU format

Payload field

Name

CLA

INS

P1

P2

LC

Data

Le

Length

1 byte

Lc byte

1 byte

Class byte

0x00: standard command

0xA2: ST command

Instruction byte

Param Byte 1

Param Byte 2

Number of bytes of the Data field

Data bytes

Number of bytes to be read in the M24SR04 memory

32/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

5.2.2

R-APDU: payload format of a response

the M24SR04 uses the I-Block format to reply to a command which used the I-Block format.

This format is described in Table 18.

Table 18. R-APDU format

Payload field

Name

Data (optional)

Le byte

SW1

SW2

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 M24SR04.

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 M24SR04.

R(NAK): the non-acknowledgment block sent by the RF or I²C host or by the

M24SR04.

DocID024754 Rev 15

33/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

Table 20. R-Block detailed format

b7-b6

0b10

b5

1

b4

X

b3

X

b2

0

b1

0

b0

X

R-Block

RFU

0: NAK

1: ACK

0: DID field is not present

1: DID field is present

Must be set to 0

RFU

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

0 to 1 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 ⁽¹⁾

2 CRC bytes

1. This field is present when b5-b4 bits are set to 0b11 (S-Block is a WTX). see Table 22: S-Block detailed format.

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 0x0B.

34/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

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

Note:

After receiving the deselect command, the session is released and M24SR04 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, M24SR04 returns FWI parameter (default frame waiting

time used); when M24SR04 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 M24SR04 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²C and RF frame

The two CRC bytes check the data transmission between the RF host or I²C host and the

M24SR04. For the RF frame, the CRC is computed on all the data bits in the frame,

excluding parity bits, SOF and EOF, and 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 shall be 0x6363 and

the register content shall not be inverted after calculation.

DocID024754 Rev 15

35/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

5.6

NFC Forum Type 4 Tag protocol

5.6.1

Commands set

With the NFC Forum Type 4 Tag protocol, the commands are common to RF and I²C.

Table 23. Command set overview

Command name

NDEF Tag Application Select

Brief description

Select the NDEF Tag Application

Select the capability container (CC) file using the

Select command

Capability Container Select

NDEF Select

System File Select

ReadBinary

Select the NDEF file

Select the system file

Read data from a file

Write new data to a file

UpdateBinary

5.6.2

Status and error codes

This section lists the status and the error code of the M24SR04.

Table 24. Status code of the M24SR04

SW1

SW2

Comment

Command completed

successfully

Value

0x90

0x00

Table 25. Error code of the M24SR04

SW1

SW2

Comment

Length

1 byte

Value

0x62

0x80

File overflow (Le error)

End of file or record reached

before reading Le bytes

Value

0x62

0x63

0x82

0x00

Password is required

Password is incorrect, X further

retries allowed (X can take

value 0,1, 2)

Value

0x63

0xCX

Value

0x65

0x67

0x81

0x00

Unsuccessful updating

Wrong length

Cmd is incompatible with the

file structure

Value

0x69

0x81

Value

0x69

0x82

0x84

Security status not satisfied

Reference data not usable

36/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

Table 25. Error code of the M24SR04 (continued)

SW1

SW2

Comment

Length

1 byte

Value

0x6A

0x6D

0x6E

0x80

0x82

0x84

0x86

0x00

Incorrect parameters Le or Lc

File or application not found

File overflow (Lc error)

Incorrect P1 or P2 values

INS field not supported

Class not supported

DocID024754 Rev 15

37/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

5.6.3

NDEF Tag Application Select command

the RF or the I²C host shall send this command to activate the NDEF Tag Application.

To activate the NDEF Tag Application, the RF host sends the Select command (see

Table 26) in addition to the sequence defined in the NFC Forum digital protocol.

To activate the NDEF Tag Application, the I²C host sends the Select command (see

Table 26) in addition to the GetSession or the Kill RF session command.

Table 26 defines the C-APDU of the Select command to select the NDEF Tag Application

(called NDEF Tag 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 defines the R-APDU of the NDEF Tag Application Select command.

Table 27. R-APDU of the NDEF Tag Application Select command

Data

SW1

SW2

Comment

Length

Value

-

1 byte

0x90

0x6A

0x6D

1 byte

0x00

0x82

0x00

-

Command completed

NDEF Tag 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.

The CC file is selected when this command returns "command completed" in the R-APDU.

Table 28 defines the C-APDU of the Select command to select the CC file (called Capability

Container Select).

38/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Name

I²C and RF command sets

Table 28. C-APDU of the Capability Container Select command

CLA

INS

P1

P2

Lc

Data

Le

Value

0x00

0xA4

0x00

0x0C

0x02

0xE103

-

Class byte

Select instruction code

P1 field

P2 field

Number of bytes of data

CC file ID

-

Table 29 defines the R-APDU of the CC Select command.

Table 29. R-APDU of the Capability Container Select command

Data

SW1

SW2

Comment

Length

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 R-

APDU. Table 30 defines the C-APDU of the Select command to select the NDEF file (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.

Table 30. C-APDU of the NDEF Select command

Name

Value

Class byte

CLA

INS

P1

P2

Lc

Data

Le

0x00

0xA4

0x00

0x0C

0x02

0x000X

-

Select instruction code

P1 field

P2 field

Number of bytes of data

0x0001: first NDEF file

-

DocID024754 Rev 15

39/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

Table 31 defines the R-APDU of the NDEF Select command.

Table 31. R-APDU of the NDEF Select command

Data

SW1

1 byte

SW2

1 byte

Comment

Length

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.

Table 32 defines the C-APDU of the command to select the System file (called System

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

-

Table 33 defines the R-APDU of the System File Select command.

Table 33. R-APDU of the System File Select command

Data

SW1

SW2

Comment

Length

Value

-

1 byte

0x90

1 byte

0x00

-

Command completed

Capability container not found, no data

is returned

Value

-

0x6A

0x82

40/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

5.6.7

ReadBinary command

On receiving the ReadBinary command, the M24SR04 reads the requested memory field

and sends back its value in the R-APDU response.

Before sending a ReadBinary command, a file shall be selected by using a Select

command.

The Response of the ReadBinary command is successful when the data to be read is within

(1)

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 defines the ReadBinary command.

Table 34. C-APDU of the ReadBinary command

Name

CLA

INS

P1 & 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 defines the R-APDU of the ReadBinary command.

Table 35. R-APDU of the ReadBinary command

Data

SW1

SW2

Comment

Length

Value

-

1 byte

0x90

0x67

0x69

0x6A

0x6E

1 byte

-

Content read

Don’t care⁽¹⁾Command completed

-

0x00

0x82

0x00

Wrong length

Security status not satisfied

File or application not found

Class not supported

1. For more information, please contact your local ST support.

1. For more details about CC file, refer to Section 3.1.2: CC file layout.

For more details about NDEF file, refer to Section 3.1.3: NDEF file layout.

For more details about System file, refer to Section 3.1.4: System file layout.

DocID024754 Rev 15

41/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

5.6.8

UpdateBinary command

On receiving the UpdateBinary command, the M24SR04 writes the data field into the

selected file and sends back a status in the R-APDU response. If needed, M24SRxx will

request a timing extension (see Section 5.4).

Before sending an UpdateBinary command, a file shall be selected by issuing a Select

command.

Table 36 defines the UpdateBinary command.

Table 36. C-APDU of the UpdateBinary command

Name

CLA

INS

P1 & 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 M24SR04 memory

-

Table 37 defines the R-APDU of the UpdateBinary command.

Table 37. R-APDU of the UpdateBinary command

Data

SW1

SW2

Comment

Length

Value

-

1 byte

0x90

0x65

0x67

0x69

0x6A

0x6E

1 byte

0x00

0x81

0x00

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 definitions, refer to Status and error codes.

42/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

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 allows the access to the

memory (the Lc field = 0x10 and the password is present).

When the Lc field if 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 M24SR04 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 shall 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 defines the Verify command.

Table 38. Verify command format

Name

CLA

INS

P1 & 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 ⁽¹⁾

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.

DocID024754 Rev 15

43/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

Table 39 defines the R-APDU of the Verify command.

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

-

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

-

0x63

0x6E

0xCX ⁽¹⁾

0x00

Class not supported

1. At each session, the RF or I²C 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

shall be issued. Thus, this command changes the reference data of the NDEF file.

Table 40 defines the Change Reference Data command.

Table 40. Change reference data command format

Name

CLA

INS

P1 & 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 ⁽¹⁾

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/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

Table 41 defines the R-APDU of the Change Reference Data command.

Table 41. R-APDU of the Change Reference Data command

Data

SW1

SW2

Comment

Length

Value

0

1 byte

-

Command completed, the access right has

been changed

-

0x90

0x69

0x00

0x81

Cmd is incompatible with the

file structure

Value

-

0x65

0x69

0x6A

0x6E

0x81

0x82

0x80

0x82

0x86

0x00

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

shall be issued. Thus, this command changes the access right of the NDEF file.

Table 42 defines the Enable Verification requirement command.

Table 42. Enable Verification Requirement command format

Name

CLA

INS

P1 & 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.

DocID024754 Rev 15

45/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

Table 43 defines the R-APDU of the Enable Verification Requirement command.

Table 43. R-APDU of the Enable Verification Requirement command

Data

SW1

SW2

Comment

Length

Value

0

1 byte

-

Command completed, the password is

correct

-

0x90

0x00

Value

-

0x69

0x6A

0x81

0x82

0x80

0x82

0x86

Cmd 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

shall 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 defines the Disable Verification Requirement command.

Table 44. Disable Verification Requirement command format

Name

CLA

INS

P1 & 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

-

Table 45 defines the R-APDU of the Disable Verification Requirement command.

46/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

Table 45. R-APDU of the Disable Verification Requirement command

Data

SW1

SW2

Comment

Length

Value

0

-

1 byte

0x90

0x69

0x6A

0x6E

0x65

1 byte

0x00

0x81

0x82

0x80

0x82

0x86

0x00

0x81

-

Command completed, the password is correct

Cmd 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 chapter.

5.8.1

ExtendedReadBinary command

On receiving the ExtendedReadBinary command, the M24SR04 reads the requested

memory field and sends back its value in the R-APDU response.

Before sending an ExtendedReadBinary command, a file shall 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 & 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

Table 47 defines the R-APDU of the read binary command.

DocID024754 Rev 15

47/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

Table 47. R-APDU of the ExtendedReadBinary command

Data

SW1

SW2

comment

Length

Value

Le bytes

1 byte

0x90

0x67

0x69

0x6A

0x6E

1 byte

-

Content read

Don’t care⁽¹⁾

0x00

Command completed

Wrong length

-

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 defines the EnablePermanentState requirement command.

Table 48. EnablePermanentState command format

Name

Length

CLA

INS

P1 & 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 defines the R-APDU of the EnablePermanentState command.

Table 49. R-APDU table of the EnablePermanentState command

Data

SW1

SW2

comment

Length

Value

-

1 byte

0x90

0x65

0x67

1 byte

0x00

0x81

0x00

-

Command completed

Update failed

Wrong length

48/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

Table 49. R-APDU table of the EnablePermanentState command (continued)

Data

SW1

SW2

comment

Value

-

0x69

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 shall be selected by issuing the NDEF Select

command.

Table 50 defines the DisablePermanentState requirement command.

Table 50. DisablePermanentState command format

Name

Length

CLA

INS

P1 & 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 defines the R-APDU of the DisablePermanentState command.

Table 51. R-APDU of the DisablePermanentState command

Data

SW1

SW2

comment

Length

Value

-

1 byte

0x90

0x65

0x67

0x69

1 byte

0x00

0x81

0x00

0x82

-

Command completed

Update failed

Wrong length

Security status not satisfied

DocID024754 Rev 15

49/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

Table 51. R-APDU of the DisablePermanentState command (continued)

Data

SW1

SW2

comment

Value

-

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 defines the UpdateFileType command.

Table 52. UpdateFileType command format

Name

Value

Class byte

CLA

INS

P1

P2

Lc

Data

Le

0x04 or

0x05

0xA2

0xD6

0x00

0x01

-

Select instruction code

P1 field

P2 field

Number of bytes of data

File type

-

Table 53 describes the R-APDU of the UpdateFileType command.

Table 53. R-APDU of the UpdateFileType command

Data

SW1

SW2

Comment

Length

Value

-

1 byte

0x90

0x69

0x6A

1 byte

0x00

0x82

0x80

-

Command completed

Security status not satisfied

CC file or System file selected

50/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

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

-

0x6A

0x82

0x86

5.8.5

SendInterrupt command

On receiving the SendInterrupt command, the M24SR04 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 shall be selected by issuing the System

Select command.

Table 54 defines the SendInterrupt 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 describes the R-APDU of the SendInterrupt command.

Table 55. R-APDU of the SendInterrupt command

Data

SW1

SW2

Comment

Length

Value

-

1 byte

0x90

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 M24SR04 drives

the GPO pin low. On receiving the StateControl command with set value: data 0x01, the

M24SR04 releases the GPO pin which returns to HZ.

Before sending this command, the system file shall be selected by issuing the System

Select command.

Table 56 defines the State Control command.

DocID024754 Rev 15

51/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

Table 56. StateControl command format

CLA

INS

P1&P2

Lc

Data

Le

Length

1 byte

0xA2

1 byte

0xD6

2 bytes

0x001F

1 byte

0x01

-

Reset value

Set value

0x00

0x01

Table 57. R-APDU of the StateControl command

Data

SW1

SW2

Comment

Length

Value

-

1 byte

0x90

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

Table 58 lists the commands that can be issued only by the RF host. The format of these

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 ⁽¹⁾

ALL_REQ

SENS_REQ

SDD_REQ

SEL_REQ

SLP_REQ

0x26 ⁽¹⁾

NFC-A technology

1. Code on 7 bits.

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 Tag Platform Device

Activation (as defined in NFC Forum Digital Protocol specification).

Table 59 details the RATS command. This command shall be sent after the anticollision

process.

52/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

Table 59. RATS command

Param

Name

Byte field

Bit field

INS

CRC

0xE0

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

to receive. Table 60 gives the conversion from FDSI to FSD.

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 M24SR04.

Table 61. ATS response

Name

Byte field

Bit field

TL

T0

TA(1)

TB(1)

TC(1)

0x02

CRC

0x05

0x78

1 byte

2 bytes

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 M24SR04 is

able to receive. The M24SR04 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 M24SR04 will not be able to treat

the command and will not reply.

The FWI which stands for the Frame Waiting time Integer codes the FWT. This time

corresponds to the maximum duration while an RF or I²C host shall send before sending the

next command.

DocID024754 Rev 15

53/90

78

I²C and RF command sets

M24SR04-Y M24SR04-G

The SFGI which stands for the Start-up Frame Guard Time is the minimum time that the

reader shall wait after receiving the response of the M24SR04.

5.9.3

PPS command & 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 allows to change the data rates of the ascending (RF host to M24SR04)

and descending (M24SR04 to RF host) data rates.

Table 62. PPS command

Name

Byte field

Bit field

INS

PPS0

0x11

PPS1

1 byte

b3-b2

CRC

-

0xDX

2 bytes

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

The ascending and descending data rates shall be coded as described in Table 63.

Table 63. Ascending and descending data rate coding

Value

Data rate

0b00

0b01

0b10

0b11

106 kbps

RFU

When the M24SR04 is able to change both data rates, it returns the following response. The

data rate of this response is 106 kbps; then, the M24SR04 changes the ascending and

descending data rates.

Table 64 gives the details of the PPS response.

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/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I²C and RF command sets

5.10

Specific I²C command set

Table 65 lists the commands that can only be issued by the I²C host.

Table 65. Specific I²C commands

Instruction

Command name

Format

Class byte

Brief description

code

Open an I²C session when the

RF session is not ongoing

GetI2Csession

KillRFsession

-

0x26

Kill the RF session and open an

I²C session

0x52

5.10.1

GetI2Csession command

The GetI2Csession command opens an I²C session if an RF session is not ongoing.

Table 66 defines the GetI2Csession command.

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 defines the KillRFsession command.

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.

DocID024754 Rev 15

55/90

78

RF device operation

M24SR04-Y M24SR04-G

6

RF device operation

6.1

Anticollision and Device Activation command set for the RF

interface

The M24SR04 device supports the command set defined in the NFC-A Technology and the

Type 4A Tag Platform chapters of the NFC Digital Protocol V1.0 specification.

6.2

Open an RFsession

Once the RF host has terminated the anticollision procedure and retrieve the ATS response,

it shall send the SelectApplication command. The M24SR04 will open an RF session. At this

point, the RF host can send the applicative command set and the I²C cannot communicate

2

with the M24SR04 without closing first the RF session using the I C KillRFsession

command.

6.3

6.4

Close an RFsession

The RF host can close the RF session by issuing 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 Tag command set

the ISO/IEC 7816-4 command set

the proprietary command set

56/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I2C device operation

2

7

I C device operation

2

The M24SR04 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

M24SR04 device is a slave in all communications.

7.1

I²C communication protocol

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

M24SR04 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

M24SR04. 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 M24SR04 acknowledges on the reception of each byte.

Once the M24SR04 is ready to send the answer, the I²C host shall:

•

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 shall 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 M24SR04.

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 M24SR04 sends an ACK ( host read will a

'0').

DocID024754 Rev 15

57/90

78

I2C device operation

M24SR04-Y M24SR04-G

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 M24SR04-Y M24SR04-G 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 M24SR04 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

time (see Table 78), the I²C logic block is reset and further incoming data transfer is ignored

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.

(see Table 78), I C session token stays

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/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

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

value that is the maximum value specified in Table 78, the I C logic

CL_RESET

block is reset and any further incoming data transfer is ignored until the next valid Start

condition.

If the serial clock high pulse is under the maximum value of t_CHCLand the serial clock low

2

pulse is under the maximum value of t

in Table 78, the I C logic block is not reset.

CLCH

For proper operation, the serial clock high pulse should not be higher than t_CHCLand lesser

than t , and the serial clock low pulse should not be higher than t_CHCHand lesser

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

address coded on 3 bits, as shown in Table 68.

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

DocID024754 Rev 15

59/90

78

I2C device operation

M24SR04-Y M24SR04-G

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

Section 5.2.

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

Table 69 shows the format of an I C frame.

2

Table 69. I C frame format

I²C frame

SOD

Payload

EOD

0xAC or 0xAD

1 byte

1 to 251 bytes

2 bytes

Device select

0xAC: to send a request to the M24SR04

0xAD: to read a response of the M24SR04

PCB field

I²C command or I²C answer

2 CRC bytes

7.9.1

Example of I²C frame commands

NDEF Tag Application command

2

This example presents the I C frame of an NDEF Tag Application Select command. The I C

frame is detailed in Table 70.

2

Table 70. I C host to M24SR04

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

Before sending a new command, the I C host can send an I C frame to read the M24SR04

answer to the NDEF tag Application Select command.

60/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Field

I2C device operation

EOD

2

Table 71. M24SR04 to I C host

SOD

Payload

I²C host to

M24SR04

M24SR04 to I²C host

0x90 00

Value

0xAD

0x02 or 0x03

F1 09 or 2D 53

Device select

PCB field

I²C command

2 CRC bytes

2

Figure 14 shows the I C frame of the NDEF tag Application Select command.

Figure 14. NDEF tag Application Select command

6WDUWꢄRIꢄWKHꢄ

WUDQVPLVVLRQꢄ

RIꢄWKHꢄUHTXHVW

,ð&ꢄEXV

6

$&.

$&. $&. $&. $&. $&. $&. $&. $&. $&. $&. $&. $&. $&.

͘͘͘

Ϭǆꢃꢂ

ϬǆϬϮ ϬǆϬϬ Ϭǆꢃϰ ϬǆϬϰ ϬǆϬϬ ϬǆϬϳ ϬǆꢀϮ Ϭǆϳϲ ϬǆϬϬ ϬǆϬϬ Ϭǆϴϱ ϬǆϬϭ ϬǆϬϭ

(QGꢄRIꢄWKHꢄ

WUDQVPLVVLRQꢄ

RIꢄWKHꢄUHTXHVW

,ð&ꢄEXV

$&.

͘͘͘ ꢊ[ꢊꢊ ꢊ[ꢀꢉ ꢊ[&ꢊ

W

6WDUWꢄRIꢄWKHꢄ

WUDQVPLVVLRQꢄ

RIꢄWKHꢄDQVZHU

ꢄŶĚꢁŽĨꢁƚŚĞꢁ

ƚƌĂŶƐŵŝƐƐŝŽŶꢁ

ŽĨꢁƚŚĞꢁĂŶƐǁĞƌ

,ð&ꢄEXV

^

ꢃꢂ< ꢃꢂ< ꢃꢂ< ꢃꢂ< ꢃꢂ< EŽꢃꢂ<

͘͘͘

Ϭǆꢃꢀ ϬǆϬϮ ϬǆϵϬ ϬǆϬϬ Ϭǆ&ϭ ϬǆϬϵ

W

$&.

$FNQRZOHGJHꢄE\ꢄ0ꢁꢆ65[[ꢋ<

$&.

1R$&.

/HJHQG

$FNQRZOHGJHꢄE\ꢄWKHꢄ,ð&ꢄKRVW

1Rꢄ$FNQRZOHGJHꢄE\ꢄWKHꢄ,ð&ꢄKRVW

%\WHꢄVHQWꢄE\ꢄWKHꢄ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

06Yꢀꢌꢈꢊꢉ9ꢂ

DocID024754 Rev 15

61/90

78

I2C device operation

M24SR04-Y M24SR04-G

7.10

Open an I²C session

To open an I²C session, the I²C host shall 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 exist and opens an I²C

session.

When an I²C session is opened, the RF host cannot communicate with the M24SR04 and

cannot close the I²C session.

7.11

Close the I²C session

There are three ways to close an I²C session:

•

turn off the Vcc power supply

send the I2C token release sequence

wait for the I²C watchdog when it is enabled

wait for the I²C timeout on clock period

62/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

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 shall use this procedure to detect the NDEF message inside an

M24SR04.

The NDEF detection procedure is as follows:

1. Open an RF or an I²C session

2. Send the SelectNDEFTagApplication 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 should 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 which has been locked

previously.

1. Select the NDEF Tag Application

2. Select the NDEF file

3. Verify the Read password by using the Verify command

4. Read the data in the NDEF file.

DocID024754 Rev 15

63/90

78

Functional procedures

M24SR04-Y M24SR04-G

8.4

Locking an NDEF file

The RF or I²C host executes this procedure to protect an NDEF file.

1. Select the NDEF Tag 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 which has been locked

previously.

1. Select the NDEF Tag 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 Tag 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 Tag 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/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

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 Tag 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 a NDEF file

When there's enough space in the file to update it with new content, the following steps

should be followed to update the NDEF message:

1. Select the NDEF Tag 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.

DocID024754 Rev 15

65/90

78

UID: Unique identifier

M24SR04-Y M24SR04-G

9

UID: Unique identifier

The M24SR04 is uniquely identified by a 7 bytes 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 describes the UID format.

Table 72. UID format

0x02

0x86 or 0x8E⁽¹⁾

5 bytes

IC manufacturer code

M24SR04 product code

Device number

1. Automative grade

66/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Maximum ratings

10

Maximum ratings

Stressing the device above the ratings listed in Table 73 may cause permanent damage to

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

Ambient operating temperature

for grade 6

- 40

85

T_A

°C

Ambient operating temperature

for grade 5

- 25

85

UFDFPN8,

SO8, TSSOP8

Storage temperature

- 65

15

150

25

°C

Sawn Bumped

Wafer (kept in

its antistatic

bag)

T_STG

Storage time

-

9

months

°C

Lead temperature

during soldering

UFDFPN8,

SO8, TSSOP8

T_LEAD

V_IO

see note ⁽¹⁾

I²C input or output range and GPO

RF supply current AC0 - AC1

RF input voltage

- 0.50

-

6.5

V

(2)

I_CC

100

mA

amplitude between

AC0 and AC1, GND

(2)

V_{MAX_1}

VAC0-VAC1

-

10

V

pad left floating

AC voltage between

VAC0-GND or

(2)

V_{MAX_2}

AC0 and GND, or AC1

VAC1-GND

- 0.5

4.5

V

and GND

Electrostatic discharge

V_ESD

voltage (human body

AC0-AC1

-

1000

3500

model) ⁽³⁾

Electrostatic discharge

voltage (human body

model) ⁽³⁾

V_ESD

Other pads

1. 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).

2. Based on characterization, not tested in production. Maximum absorbed power = 100 mW @ 7.5 A/m

3. AEC-Q100-002 (compliant with JEDEC Std JESD22-A114A, C1 = 100 pF, R1 = 1500 Ω, R2 = 500 Ω)

DocID024754 Rev 15

67/90

78

I2C DC and AC parameters

M24SR04-Y M24SR04-G

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 should 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

Supply voltage range Y

Min.

Max.

Unit

2.7

2.4

–40

-25

5.5

85

V_CC

V

Supply voltage range G

Ambient operating temperature for grade 6

Ambient operating temperature for grade 5

T_A

°C

85

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_CCto 0.8 V_CC

0.3 V_CCto 0.7 V_CC

Input and output timing reference levels

V

Figure 15. AC test measurement I/O waveform

,QSXWꢄDQGꢄ2XWSXW

,QSXWꢄ/HYHOV

7LPLQJꢄ5HIHUHQFHꢄ/HYHOV

ꢊꢇꢃꢄೌꢄ9_&&

ꢊꢇꢈꢄೌꢄ9_&&

ꢊꢇꢀꢄೌꢄ9_&&

ꢊꢇꢁꢄೌꢄ9_&&

$,ꢊꢊꢃꢁꢉ&

Table 76. Input parameters

Symbol

Parameter

Input capacitance (SDA)

Min.

Max.

Unit

C_IN

t_NS

-

8

6

pF

ns

Input capacitance (other pins)

Pulse width ignored (Input filter on SCL and SDA)

80

68/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I2C DC and AC parameters

2

Table 77. I C DC characteristics

Symbol

Parameter

Test condition

Min.

Max.

Unit

Input leakage current

(SCL, SDA)

V_IN= V_SSor V_CC

device in Standby mode

I_LI

-

± 2

µA

SDA in Hi-Z, external voltage applied on SDA:

VSS or VCC

I_LO

Output leakage current

-

± 2

µA

V

_CC= 3.3 V, with RF ON

_CC= 3.3 V, with RF OFF

_CC= 5.5 V, with RF ON⁽¹⁾

V_CC= 5.5 V, with RF OFF

_CC= 3.3 V, with RF ON

_CC= 3.3 V, with RF OFF

V_CC= 5.5 V, with RF ON

-

30

5

V

Standby power mode

supply current

I_CC0

µA

V

30

5

V

150

250

200

250

200

550

500

550

500

V

Supply current

I_CC1

I_CC2

I_CC3

µA

(I²C Session open)

V_CC= 5.5 V, with RF OFF

V_CC= 3.3 V (f_C= 1 MHz), with RF ON ⁽³⁾

Supply current ⁽²⁾

(Read binary)

V

_CC= 3.3 V (f_C= 1 MHz), with RF OFF ⁽³⁾

V

_CC= 5.5 V (f_C= 1 MHz),with RF ON ⁽³⁾

V_CC= 5.5 V (f_C= 1 MHz),with RF OFF ⁽³⁾

V

_CC= 3.3 V (f_C= 1 MHz),with RF ON ⁽³⁾

_CC= 3.3 V (f_C= 1 MHz),with RF OFF ⁽³⁾

Supply current ⁽²⁾

(Update binary)

V

V_CC= 5.5 V (f_C= 1 MHz), with RF ON ⁽³⁾

V_CC= 5.5 V (f_C= 1 MHz), with RF OFF ⁽³⁾

V_CC= 2.7 V (grade Y)

V_CC= 2.4 V (grade G)

V_CC= 5.5 V

Input low voltage

(SDA, SCL)

0.3

V_CC

V_IL

V_IH

V_IL

V_IH

-0.45

V

V_CC= 2.7 V (grade Y)

Input high voltage

(SDA, SCL)

V_CC= 2.4 V (grade G)

0.7 V_CC

6.5

V_CC= 5.5 V

V_CC= 2.7 V (grade Y)

Input low voltage

(RF disable)

-

V_CC= 2.4 V (grade G)

0.45

V_CC= 5.5 V

V_CC= 2.7 V (grade Y)

V_CC= 2.4 V (grade G)

V_CC= 5.5 V

Input high voltage

(RF disable)

1.4

-

V

Output low voltage (SDA)

Output low voltage (GPO)

I_OL= 3 mA, V_CC= 5.5 V

-

0.4

I_OL= 1 mA,

V_CC= 2.7 V (grade Y) or 2.4 V (grade G)

to V_CC= 5.5 V

V_OL

1. When an RF session is Opened, I_cccorresponds to the standby power mode.

2. Characterized only.

3. Input levels as defined in Figure 15.

DocID024754 Rev 15

69/90

78

I2C DC and AC parameters

M24SR04-Y M24SR04-G

2

Table 78. I C AC characteristics (400 kHz)

Test conditions specified in Table 74

(preliminary data based on design simulations)

Symbol

Alt.

Parameter

Min.

Max.

Unit

f_C

f_SCL

Clock frequency

0.05

0.6

400

kHz

µs

ns

ms

ns

ms

(1)

t_CHCL

t_HIGHClock pulse width high

t_LOWClock pulse width low

20000

(2)

t_CLCH

1.3

t_{CL_reset}

t_XH1XH2

t_XL1XL2

t_DL1DL2

t_DXCX

-

Clock reset

40000

-

(3)

t_R

t_F

Input signal rise time

Input signal fall time

SDA (out) fall time

(3)

20

100

0

300

t_SU:DATData in set up time

t_HD:DATData 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:STAStart condition set up time

t_HD:STAStart condition hold time

t_SU:STOStop condition set up time

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

-

150

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_CHCLtimeout.

2. t_CLCHtimeout.

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. To avoid spurious Start and Stop conditions, a minimum delay is placed between SCL=1 and the falling or rising edge of

SDA.

5.

t_CLQVis the time (from the falling edge of SCL) required by the SDA bus line to reach 0.8V_CCin a compatible way with the

I²C specification (which specifies t_SU:DAT(min) = 100 ns), assuming that the R_bus× C_bustime constant is less than 500 ns

(as specified in Figure 17).

6. For a restart condition, or following a write cycle.

7. Characterized only, not tested in production.

70/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I2C DC and AC parameters

2

Table 79. I C AC characteristics (1 MHz)

Test conditions specified in Table 74

(preliminary data based on design simulations)

Symbol

Alt.

Parameter

Min.

Max.

Unit

f_C

f_SCLClock frequency

0.05

260

1000

-

kHz

ns

(1)

t_CHCL

t_HIGHClock pulse width high

t_LOWClock pulse width low

(2)

t_CLCH

500

-

(3)

t_XH1XH2

t_XL1XL2

t_DL1DL2

t_DXCX

t_R

t_F

Input signal rise time

Input signal fall time

SDA (out) fall time

(3)

20

50

120

t_SU:DATData in set up time

t_HD:DATData 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:STAStart condition set up time

t_HD:STAStart condition hold time

t_SU:STOStop condition set up time

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

t_W

150

Pulse width ignored (input filter on SCL and

SDA)

(7)

t_NS

-

80

ns

1. t_CHCLtimeout.

2. t_CLCHtimeout.

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. To avoid spurious Start and Stop conditions, a minimum delay is placed between SCL=1 and the falling or

rising edge of SDA.

5. t_CLQVis the time (from the falling edge of SCL) required by the SDA bus line to reach 0.8V_CCin a

compatible way with the I²C specification (which specifies t_SU:DAT(min) = 100 ns), assuming that the R_bus

× C_bustime constant is less than 500 ns (as specified in Figure 17).

6. For a reStart condition, or following a write cycle.

7. Characterized only, not tested in production.

DocID024754 Rev 15

71/90

78

I2C DC and AC parameters

M24SR04-Y M24SR04-G

2

Figure 16. I C AC waveforms

T8,ꢄ8,ꢅ

T#(#,

T#,#(

T8(ꢄ8(ꢅ

3#,

T$,#,

T8,ꢄ8,ꢅ

3$! )N

T#($8

3TART

CONDITION

T#,$8

T$8#8

3$!

#HANGE

T8(ꢄ8(ꢅ

T#($( T$($,

3TART

3$!

)NPUT

3TOP

CONDITION

3#,

3$! )N

T7

7RITE CYCLE

T#($(

T#($8

3TOP

CONDITION

3TART

CONDITION

T#(#,

3#,

T#,16

T#,18

$ATA VALID

T$,ꢄ$,ꢅ

$ATA VALID

3$! /UT

!)ꢀꢀꢁꢂꢃE

11.1

I²C timing measurement condition

Figure 17 represents the Maximum Rbus value versus bus parasitic capacitance (Cbus) for

2

an I C bus at maximum frequency f = 400 kHz.

C

Figure 17. Maximum Rbus value with f = 400 kHz

C

ꢄꢀꢀ

4HE 2

X # TIME CONSTANT

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

72/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

I2C DC and AC parameters

Figure 18 represents the Maximum Rbus value versus bus parasitic capacitance (Cbus) for

2

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

MUST BE BELOW THE ꢄꢃꢀ NS

TIME CONSTANT LINE REPRESENTED

ON THE LEFTꢍ

3#,

3$!

)£# BUS

MASTER

ꢄꢀ

ꢆ

-ꢅꢆXXX

(EREꢎ

#

§

BUS

ꢋ ꢄꢅꢀ NS

#

2

BUS

ꢄ

ꢄꢀ

ꢌꢀ

"US LINE CAPACITOR ꢈP&ꢉ

ꢄꢀꢀ

-3ꢄꢂꢁꢆꢃ6ꢄ

2

Figure 19. I C bus protocol

3#,

3$!

)NPUT

3$!

#HANGE

34!24

#ONDITION

34/0

#ONDITION

ꢄ

ꢅ

ꢌ

ꢁ

ꢏ

ꢂ

3#,

3$!

!#+

-3"

34!24

#ONDITION

ꢄ

ꢅ

ꢌ

ꢁ

ꢏ

ꢂ

3#,

3$!

-3"

!#+

34/0

#ONDITION

!)ꢀꢀꢁꢂꢅ"

DocID024754 Rev 15

73/90

78

I2C DC and AC parameters

M24SR04-Y M24SR04-G

Table 80. Device select code

Device type identifier ⁽¹⁾

Chip Enable address

b3 b2 b1

RW

b0

b7

b6

b5

b4

Device select code 1

0

1

0

1

0

RW

1. The most significant bit, b7, is sent first.

74/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

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

Kill session

Get session

Symbol

Typ. Unit

CmdSTPtoGPlow

*add 100 µs for boot

after POR

15*

µs

GPO low when

session active

I²C

0xX1

0x1X

I²C token release

sequence

I²C

RF

GPO return HZ

AnswerlbLBtoGPHZ 105

ns

µs

Session Open

GPO low when

session active

NDEF select

Deselect

CmdEOFtoGPlow

170

RF

I²C

GPO return HZ

CmdEOFtoGPHZ

CmdSTPtoGPlow

370

45

µs

GPO low when

programming

Update Binary

Writing time duration

(No time extension)

0xX2

0x2X

I²C

RF

5

75

5

ms

µs

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²C

CmdSTPtoGPlow

ms

ns

Answer Ready

0xX3

0x3X

GPO return HZ on

new command

After NewCmdlbFB

or AnswerlbFB

I²C

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²C

CmdSTPtoGPlow

50

µs

ns

0xX4

0x4X

After NewCmdlbFB

or AnswerlbFB

Interrupt

GPO return HZ

105

RF

GPO low after

receiving an

Interrupt command

CmdEOFtoGPlow

Pulse duration

75

µs

540

DocID024754 Rev 15

75/90

78

GPO parameters

GPO field

M24SR04-Y M24SR04-G

(1)

Table 81. GPO timings measurement (continued)

I/F

Condition

Command

Symbol

Typ. Unit

GPO low when

reset

I²C

Reset GPO

CmdSTPtoGPlow

40

60

µs

0xX5

0x5X

GPO return HZ

when set

I²C

RF

Set GPO

Reset GPO

Set GPO

CmdSTPtoGPHZ

CmdEOFtoGPlow

CmdEOFtoGPHZ

State Control

GPO low when

reset

GPO return HZ

when set

Anticollision

command or start

of RF disturb

(command using

another RF

GPO low after

receiving an RF

command

RF

CmdSOFtoGPlow

CmdEOFtoGPHZ

6

µs

protocol)

RF Busy

0x6X

Deselect or end of

RF disturb

(command using

another RF

GPO return HZ

afterdeselectionor

RF command in

another protocol

460

protocol)

1. Characterized only.

76/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Write cycle definition

13

Write cycle definition

(1)

Table 82. Write cycle definition

Test Conditions

Symbol

Ncycle

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

endurance⁽²⁾

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.

DocID024754 Rev 15

77/90

78

RF electrical parameters

M24SR04-Y M24SR04-G

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 DC and AC characteristics tables that follow are derived from tests

performed under the Measurement Conditions summarized in the relevant tables.

Designers should 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

Ambient operating temperature for grade 6

Ambient operating temperature for grade 5

–40

-25

85

T_A

°C

(1)

Table 84. RF characteristics

Symbol

Parameter

Condition

Min

Typ

Max

Unit

f_C

External RF signal frequency

13.553

1500

13.56 13.567 MHz

H_ISO

Operating field according to ISO

T_A= 0 °C to 50 °C

-

7500 mA/m

Operating field in extended

temperature range

H_Extended

T_A= -40 °C to 85 °C

500

MI_CARRIER100% carrier modulation index

MI=(A-B)/(A+B)

90

28/f_C

7/f_C

1.5xt4

0

-

100

40.5/f_C

t1

%

µs

t₁

t₂

t₃

t₄

Pause A length

-

Pause A low time

Pause A rise time

Pause A rise time section

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 ⁽²⁾

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 were 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 (M24SR04)

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/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

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

specifications, grade definitions and product status are available at: www.st.com.

®

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 ⁽¹⁾

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

DocID024754 Rev 15

79/90

86

Package information

M24SR04-Y M24SR04-G

Table 85. SO8N - 8-lead plastic small outline, 150 mils body width,

package data (continued)

millimeters

inches ⁽¹⁾

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 4 decimal digits.

Figure 21. SO8N - 8-lead plastic small outline, 150 mils bosy width,

package recommended footprint

ꢊꢇꢌꢄꢎ[ꢃꢏ

ꢂꢇꢁꢈ

2ꢈB62ꢃ1B)3B9ꢂ

80/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Package information

15.2

TSSOP8 package information

Figure 22. TSSOP8 - 8-lead thin shrink small outline, 3 x 4 mm, 0.5 mm pitch

package outline

ꢀ

ϴ

ϱ

Đ

ꢄϭ

ꢄ

ϭ

ϰ

ɲ

>

ꢃϭ

ꢃϮ

ꢃ

>ϭ

ꢂW

ď

Ğ

76623ꢃ$0B9ꢁ

1. Drawing is not to scale.

/

Table 86. TSSOP8 - 8-lead thin shrink small outline, 169 mils width, package data

millimeters

Min

inches ⁽¹⁾

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 4 decimal digits.

DocID024754 Rev 15

81/90

86

Package information

M24SR04-Y M24SR04-G

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 &

7RSꢄYLHZ

'ꢁ

H

'DWXPꢄ$

E

ꢂ

ꢁ

/ꢂ

/ꢀ

3LQꢄꢐꢂꢄ

/

/ꢀ

(ꢁ

.

,'ꢄPDUNLQJ

Hꢅꢁ

/ꢂ

7HUPLQDOꢄ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_SSor left floating

(not connected) in the end application.

82/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

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 ⁽¹⁾

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⁽²⁾

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.050

0.080

-

0.0059

0.0039

0.0020

0.0031

bbb

ccc

ddd

eee ⁽³⁾

1. Values in inches are converted from mm and rounded to 4 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.

DocID024754 Rev 15

83/90

86

Package information

M24SR04-Y M24SR04-G

15.4

WFDFPN8 package information

Figure 24. WFDFPN8 (MLP8) 8-lead, 2 x 3 mm, 0.5 mm pitch very thin fine pitch

dual flat package outline

'ꢁ

'ꢁꢅꢁ

'DWXPꢄ<

H

$

%

'

3LQꢄꢐꢂꢄ,'ꢄPDUNLQJ

3LQꢄꢐꢂ

(ꢁꢅꢁ

(ꢁ

(

6HHꢄ=

'HWDLO

.

ꢁ[

DDD #

ꢁ[

-

EEE

GGG

&

$ %

1;ꢄE

ꢎ1'ꢋꢂꢏꢄ[ꢄH

%RWWRPꢄYLHZ

DDD #

7RSꢄYLHZ

'DWXPꢄ<

ꢅꢅ FFF #

&

$

HHH #

6HDWLQJꢄSODQH

$ꢂ

/

/ꢀ

/ꢂ

7HUPLQDOꢄWLS

6LGHꢄYLHZ

Hꢅꢁ

H

'HWDLOꢄ³=´

$ꢊ<ꢀB0(B9ꢀ

1. Drawing is not to scale.

Table 88. WFDFPN8 8-lead thin fine pitch dual flat package no lead

mechanical data

millimeters

Typ

inches⁽¹⁾

Symbol

Min

Max

Min

Typ

Max

A

A1

b

0.700

0.025

0.200

1.900

2.900

-

0.750

0.045

0.250

2.000

3.000

0.500

-

0.800

0.065

0.300

2.100

3.100

-

0.0276

0.0010

0.0079

0.0748

0.1142

-

0.0295

0.0315

0.0026

0.0118

0.0827

0.1220

-

0.0018

0.0098

D

0.0787

E

0.1181

e

0.0197

L1

L3

D2

E2

-

0.150

-

0.0059

-

0.300

1.050

-

0.0118

0.0413

-

1.650

1.450

0.0650

0.0571

-

84/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Package information

Table 88. WFDFPN8 8-lead thin fine pitch dual flat package no lead

mechanical data (continued)

millimeters

Typ

inches⁽¹⁾

Symbol

Min

Max

Min

Typ

Max

K

L

0.400

0.300

-

0.0157

0.0118

-

0.500

0.0197

NX⁽²⁾

ND⁽³⁾

aaa

bbb

ccc

8

4

-

8

4

-

0.150

0.100

0.050

0.080

-

0.0059

0.0039

0.0020

0.0031

-

ddd

eee⁽⁴⁾

-

1. Values in inches are converted from mm and rounded to four decimal digits.

2. NX is the number of terminals.

3. ND is the number of terminals on “D” sides.

4. Applied for exposed die paddle and terminals. Excluding embedding part of exposed die paddle from

measuring.

DocID024754 Rev 15

85/90

86

Part numbering

M24SR04-Y M24SR04-G

16

Part numbering

Table 89. Ordering information scheme for packaged devices

M24 SR 04- Y MN

Example:

6

T

/2

Device type

M24 = I²C interface device

Device feature

SR = Short range

Memory size

04 = memory size in Kbits

Voltage range

Y = 2.7 to 5.5 V

G = 2.4 to 5.5 V, only available in grade 5 (-25 to 85 °C)

Package

MN = SO8N

DW = TSSOP8

MC = UFDFPN8

MF = WFDFPN8⁽¹⁾

SG12I = 120 µm ± 15 µm bumped and sawn inkless wafer on 8-inch frame⁽²⁾

Device grade

5 = industrial: device tested with standard test flow over -25 to 85 °C

6 = industrial: device tested with standard test flow over –40 to 85 °C

(No parameter for SG12I)

Option

T = Tape and reel packing

(No parameter for SG12I)

Capacitance

/2 = 25 pF

1. Package for automotive grade.

2. SG12I is only available for voltage range “G”.

Note:

Parts marked as “ES”, “E” or accompanied by an Engineering Sample notification letter, are

not yet qualified and therefore not yet ready to be used in production and any consequences

deriving from such usage will not be at ST charge. In no event, ST will be liable for any

customer usage 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.

86/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Revision history

17

Revision history

Table 90. Document revision history

Changes

Date

Revision

13-Jun-2013

1

Initial release.

Added UFDFPN8 drawing on page 1.

Edited Section 2.6: RF disable.

29-Aug-2013

2

Updated I_CC0parameter in Table 77: I2C DC characteristics and added a note.

Added Section 15.3: UFDFPN8 package information and UFDFPN8 package.

Updated the Capacitance value to 25 pF.

Removed all “Battery assisted” and “Wire power management” information (conditioned

for a future use).

Moved GetI2Csession command before Section 5.10.2: KillRFsession command.

Added 2 new sections: Section 7.4: I²C token release sequence and Section 7.5: I²C

timeout on clock period.

Removed “DID field” information from Section 7.9: I²C frame format and from Table 69

to Table 71 .

28-Oct-2013

3

Updated different values in Table 73: Absolute maximum ratings, Table 74: I2C

operating conditions, Table 77: I2C DC characteristics, Table 78: I2C AC characteristics

(400 kHz), Table 79: I2C AC characteristics (1 MHz), and Table 84: RF characteristics,

and removed all “(forecast data)” from the table titles.

Moved RF characteristics table before Table 84: RF characteristics, deleted footnote (1)

and updated footnote (2).

Fully edited.

Added a note to Section 7.1: I2C communication protocol below Figure 12: Command

and response exchange.

08-Nov-2013

4

Changed the datasheet status from “Preliminary data” to “Production data”.

Restored the whole content of Table 77: I2C DC characteristics.

Updated the capacitor values in Section 2.5.1: Operating supply voltage VCC.

Removed bullet (4) from Section 8.6: Reaching the read-only state for an NDEF file.

Updated V_ESDvalue in Table 73: Absolute maximum ratings, I_CCvalues in Table 77:

I2C DC characteristics, and H_Extended value in Table 84: RF characteristics.

18-Dec-2013

5

Added details to “S(WTX)” bullet in Section 5.4: S-Block format.

Added sentences to Section 5.6.8: UpdateBinary command and to Section 5.8.3:

DisablePermanentState command.

Changed ‘0x001E’ value into ‘0x001F’ in Table 56: StateControl command format.

Updated values in Table 61: ATS response.

Added Note (4) to Figure 10: Changing the read access right to an NDEF file and

Figure 11: Changing the write access right to an NDEF file.

DocID024754 Rev 15

87/90

89

Revision history

M24SR04-Y M24SR04-G

Table 90. Document revision history (continued)

Changes

Date

Revision

Updated Figure 5: GPO configured as I2C answer ready (GPO field = 0xX3) and

Figure 8: GPO configured as State Control (GPO field = 0xX5 or 0x5X).

Added I²C text to the Note below Table 22: S-Block detailed format.

Edited the third paragraph of Section 5.8.1: ExtendedReadBinary command.

Added Section 5.8.4: UpdateFileType command and Section 8.8: Changing a File

type Procedure.

Updated bullet 3 in Section 7.9: I²C frame format, and the Payload row of Table 70: I2C

host to M24SR04. Updated bullet 2 in Section 7.11: Close the I²C session.

26-Feb-2014

6

Edited V_IOrow and removed V_ESD(machine model) row from Table 73: Absolute

maximum ratings.

Updated I_CCrows and added a Note to Table 77: I2C DC characteristics.

Updated Figure 20: SO8N - 8-lead plastic small outline, 150 mils body width, package

outline.

Fixed a typo in Figure 23: UFDFPN8 - 8-lead, 2 x 3 mm, 0.5 mm pitch ultra thin profile

fine pitch dual flat package outline title: UFDPFN8 changed into UFDFPN8.

Added data for automotive grade in Table 6: Field list and Table 72: UID format

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

Added WFDFPN8 package for automotive grade under qualification

11-Jun-2014

7

Added Table 88: WFDFPN8 8-lead thin fine pitch dual flat package no lead mechanical

data

Added MF = WFDFPN8 inside Table 89: Ordering information scheme for packaged

devices

Inserted byte <04> between A4 and 00 inside Figure 14: NDEF tag Application

Select command

Added:

– New Root Part Number on cover page

– single supply voltage for I2C for grade G and note (1)

Updated:

20-Nov-2014

8

– Figure 14

– Figure 73,Figure 74, Figure 77, Figure 78, Figure 83, Figure 89

Added

– Figure 21: SO8N - 8-lead plastic small outline, 150 mils bosy width, package

recommended footprint

Updated

– Section 15: Package information

– Table 73: Absolute maximum ratings

– Table 74: I2C operating conditions

– Table 78: I2C AC characteristics (400 kHz)

– Table 89: Ordering information scheme for packaged devices

20-Aug-2015

9

88/90

DocID024754 Rev 15

M24SR04-Y M24SR04-G

Revision history

Table 90. Document revision history (continued)

Changes

Date

Revision

Updated:

– Features

– Section 2.7.6: State Control configuration (GPO field = 0xX5 or 0x5X)

Added:

04-Mar-2016

10

– Table 7: Details about I2C watchdog

– Table 82: Write cycle definition

Updated:

– Features

– Table 73: Absolute maximum ratings

– Table 82: Write cycle definition

Added:

27-Apr-2016

11

– Section 13: Write cycle definition

Updated:

– Section 3.2.2: Changing the read access right to NDEF files

– Section 3.2.3: Changing the write access right to NDEF files

– Section 5.6.5: NDEF Select command

– Section 5.8.4: UpdateFileType command

– Section 5.8.5: SendInterrupt command

– Section 8.2: Reading of an NDEF message

– Section 8.5: Unlocking an NDEF file

– Section 8.6: Reaching the read-only state for an NDEF file

– Section 16: Part numbering

14-Oct-2016

12

Added:

– Section 8.9: Updating a NDEF file

Updated:

– Table 35: R-APDU of the ReadBinary command

– Table 47: R-APDU of the ExtendedReadBinary command

– Table 89: Ordering information scheme for packaged devices

18-Nov-2016

07-Feb-2017

08-Feb-2017

13

14

15

Added:

– Note 4. on Figure 23.: UFDFPN8 - 8-lead, 2 x 3 mm, 0.5 mm pitch ultra thin profile

fine pitch dual flat package outline

Updated:

– Table 89: Ordering information scheme for packaged devices

Package SB12I replaced with SG12I.

Updated:

– Table 73: Absolute maximum ratings

– Table 89: Ordering information scheme for packaged devices

DocID024754 Rev 15

89/90

89

M24SR04-Y M24SR04-G

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 ST. 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.

90/90

DocID024754 Rev 15


型号：	M24SR04-G
厂家：	ST
描述：	Support of NDEF data structure
文件：	总90页 (文件大小：1547K)
中文：	中文翻译
下载：	下载PDF数据表文档文件

M24SR04-G [STMICROELECTRONICS]

相关型号：

SI9130DB

SI9135LG-T1

SI9135LG-T1-E3

SI9135_11

SI9136_11

SI9130CG-T1-E3

SI9130LG-T1-E3

SI9130_11

SI9137

SI9137DB

SI9137LG

SI9122E