M24LR64E-RDW6T/2 - STMicroelectronics

This is information on a product in full production.

July 2017 DocID022712 Rev 12 1/144

M24LR64E-R

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

energy harvesting, I²C bus and ISO 15693 RF interface

Datasheet - production data

Features

•Belonging to ST25 family, which includes all

NFC/RF ID tag and reader products from ST

I2C interface

•Two-wires I2C serial interface supports

400 kHz protocol

•Single supply voltage:

– 1.8 V to 5.5 V

•Byte and Page Write (up to 4 bytes)

•Random and Sequential read modes

•Self-timed programming cycle

•Automatic address incrementing

•Enhanced ESD/latch-up protection

•I²C timeout

Contactless interface

•

ISO 15693 and ISO 18000-3 mode 1 compatible

•13.56 MHz ± 7 kHz carrier frequency

•

To tag: 10% or 100% ASK modulation using 1/4 (26

Kbit/s) or 1/256 (1.6 Kbit/s) pulse position coding

•From tag: load modulation using Manchester

coding with 423 kHz and 484 kHz subcarriers

in low (6.6 kbit/s) or high (26 kbit/s) data rate

mode. Supports the 53 kbit/s data rate with

Fast commands

•Internal tuning capacitance: 27.5 pF

•64-bit unique identifier (UID)

•Read Block & Write (32-bit blocks)

Digital output pin

•User configurable pin: RF write in progress or

RF busy mode

Energy harvesting

•Analog pin for energy harvesting

•Four sink current configurable ranges

Temperature range

•From –40 to 85 °C

Memory

•64-Kbit EEPROM organized into:

– 8192 bytes in I2C mode

– 2048 blocks of 32 bits in RF mode

•Write time

–I

2C: 5 ms (max.)

– RF: 5.75 ms including the internal Verify

time

•Write cycling endurance:

– 1 million write cycles at 25 °C

– 150 k write cycles at 85 °C

•More than 40-year data retention

•Multiple password protection in RF mode

•Single password protection in I2C mode

Package

•SO8 (ECOPACK2®)

•TSSOP8 (ECOPACK2®)

•UFDFPN8 (ECOPACK2®)

SO8 (MN) UFDFPN8 (MC) TSSOP8 (DW)

Wafer (SB12I)

2 x 3 mm

Wafer (RUW20)

www.st.com

Contents M24LR64E-R
2/144 DocID022712 Rev 12
Contents
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Signal descriptions  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1 Serial clock (SCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
2 Serial data (SDA)  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
3 RF Write in progress / RF Busy (RF WIP/BUSY) . . . . . . . . . . . . . . . . . . .  15
4 Energy harvesting analog output (Vout) . . . . . . . . . . . . . . . . . . . . . . . . . .  15
5 Antenna coil (AC0, AC1)   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
5.1 Device reset in RF mode  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6 VSS ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
7 Supply voltage (VCC)  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
7.1 Operating supply voltage VCC  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.2 Power-up conditions   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.3 Device reset in I²C mode  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.4 Power-down conditions  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
User memory organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
System memory area   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1 M24LR64E-R block security in RF mode  . . . . . . . . . . . . . . . . . . . . . . . . .  24
1.1 Example of the M24LR64E-R security protection in RF mode   . . . . . . . 26
2 M24LR64E-R block security in I²C mode (I2C_Write_Lock bit area)  . . . .  27
3 Configuration byte and Control register  . . . . . . . . . . . . . . . . . . . . . . . . . .  27
3.1 RF WIP/BUSY pin configuration   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2 Energy harvesting configuration   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 FIELD_ON indicator bit  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.4 Configuration byte access in I²C and RF modes  . . . . . . . . . . . . . . . . . . 30
3.5 Control register access in I²C or RF mode   . . . . . . . . . . . . . . . . . . . . . . 30
4 ISO 15693 system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  30
5I
2C device operation  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1 Start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  32
2 Stop condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  32

DocID022712 Rev 12 3/144
M24LR64E-R Contents
3 Acknowledge bit (Ack)  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  32
4 Data input  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  32
5 I²C timeout  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  32
5.1 I²C timeout on Start condition   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.2 I²C timeout on clock period   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6 Memory addressing  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  33
7 Write operations  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  34
8 Byte write  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  35
9 Page write   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  35
10 Minimizing system delays by polling on Ack   . . . . . . . . . . . . . . . . . . . . . .  36
11 Read operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  38
12 Random Address Read  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  38
13 Current Address Read  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  38
14 Sequential Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  38
15 Acknowledge in Read mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  38
16 M24LR64E-R I2C password security  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  39
16.1 I2C present password command description  . . . . . . . . . . . . . . . . . . . . . 39
16.2 I2C write password command description  . . . . . . . . . . . . . . . . . . . . . . . 40
M24LR64E-R memory initial state  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
RF device operation   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
1 RF communication and energy harvesting . . . . . . . . . . . . . . . . . . . . . . . .  42
2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  43
3 Initial dialog for vicinity cards  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  44
3.1 Power transfer  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.2 Frequency  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3 Operating field  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Communication signal from VCD to M24LR64E-R . . . . . . . . . . . . . . . . 45
Data rate and data coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1 Data coding mode: 1 out of 256  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  47
2 Data coding mode: 1 out of 4  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  48
3 VCD to M24LR64E-R frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  49

Contents M24LR64E-R
4/144 DocID022712 Rev 12
4 Start of frame (SOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  50
Communication signal from M24LR64E-R to VCD . . . . . . . . . . . . . . . . 51
1 Load modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  51
2 Subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  51
3 Data rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  51
Bit representation and coding  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1 Bit coding using one subcarrier  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  52
1.1 High data rate   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1.2 Low data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2 Bit coding using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  54
2.1 High data rate   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.2 Low data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
M24LR64E-R to VCD frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
1 SOF when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  55
1.1 High data rate   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
1.2 Low data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2 SOF when using two subcarriers  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  56
2.1 High data rate   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.2 Low data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3 EOF when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  57
3.1 High data rate   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.2 Low data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4 EOF when using two subcarriers  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  58
4.1 High data rate   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.2 Low data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Unique identifier (UID)   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Application family identifier (AFI)  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Data storage format identifier (DSFID)   . . . . . . . . . . . . . . . . . . . . . . . . . 61
1 CRC  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  61
M24LR64E-R protocol description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

DocID022712 Rev 12 5/144
M24LR64E-R Contents
M24LR64E-R states  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
1 Power-off state  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  64
2 Ready state   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  64
3 Quiet state  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  64
4 Selected state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  64
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
1 Addressed mode   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  66
2 Non-addressed mode (general request)   . . . . . . . . . . . . . . . . . . . . . . . . .  66
3 Select mode  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  66
Request format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
1 Request flags  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  67
Response format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
1 Response flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  69
2 Response error code  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  70
Anticollision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
1 Request parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  71
Request processing by the M24LR64E-R  . . . . . . . . . . . . . . . . . . . . . . . 73
Explanation of the possible cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Inventory Initiated command  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Timing definition  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
1 t1: M24LR64E-R response delay  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  77
2 t2: VCD new request delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  77
3 t3: VCD new request delay when no response is received
from the M24LR64E-R  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  77
Command codes  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
1 Inventory   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  79
2 Stay Quiet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  81

Contents M24LR64E-R
6/144 DocID022712 Rev 12
3 Read Single Block  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  82
4 Write Single Block   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  83
5 Read Multiple Block  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  87
6 Select  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  88
7 Reset to Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  89
8 Write AFI   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  90
9 Lock AFI  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  92
10 Write DSFID  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  94
11 Lock DSFID   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  95
12 Get System Info  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  96
13 Get Multiple Block Security Status  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  98
14 Write-sector Password  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  100
15 Lock-sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  101
16 Present-sector Password  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  103
17 Fast Read Single Block  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  104
18 Fast Inventory Initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  106
19 Fast Initiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  107
20 Fast Read Multiple Block  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  108
21 Inventory Initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  109
22 Initiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
23 ReadCfg  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
24 WriteEHCfg   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
25 WriteDOCfg  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
26 SetRstEHEn  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
27 CheckEHEn  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  119
I2C DC and AC parameters  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Write cycle definition   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
RF electrical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

DocID022712 Rev 12 7/144

M24LR64E-R Contents

31.1 SO8N package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

31.2 UFDFN8 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

31.3 TSSOP8 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

32 Part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Appendix A Anticollision algorithm (informative) . . . . . . . . . . . . . . . . . . . . . . . 138

A.1 Algorithm for pulsed slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Appendix B CRC (informative) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

B.1 CRC error detection method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

B.2 CRC calculation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Appendix C Application family identifier (AFI) (informative) . . . . . . . . . . . . . . 141

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

List of tables M24LR64E-R
8/144 DocID022712 Rev 12
List of tables
Table 1. Signal names  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 2. Device select code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 3. Address most significant byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 4. Address least significant byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 5. Sector details  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 6. Sector security status byte area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 7. Sector security status byte organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 8. Read/Write protection bit setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 9. Password control bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 10. Password system area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 11. M24LR64E-R sector security protection after power-up . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 12. M24LR64E-R sector security protection after a valid presentation of password 1 . . . . . . . 26
Table 13. I2C_Write_Lock bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 14. Configuration byte. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 15. Control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 16. EH_enable bit value after power-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 17. System parameter sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 18. Operating modes  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 19. 10% modulation parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 20. Response data rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 21. UID format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Table 22. CRC transmission rules  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Table 23. VCD request frame format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 24. M24LR64E-R Response frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 25. M24LR64E-R response depending on Request_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 26. General request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 27. Definition of request flags 1 to 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 28. Request flags 5 to 8 when Bit 3 = 0  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 29. Request flags 5 to 8 when Bit 3 = 1  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 30. General response format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 31. Definitions of response flags 1 to 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 32. Response error code definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Table 33. Inventory request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 34. Example of the addition of 0-bits to an 11-bit mask value  . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 35. Timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Table 36. Command codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 37. Inventory request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 38. Inventory response format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 39. Stay Quiet request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 40. Read Single Block request format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Table 41. Read Single Block response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . 82
Table 42. Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Table 43. Read Single Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . 82
Table 44. Write Single Block request format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Table 45. Write Single Block response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . 83
Table 46. Write Single Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . 84
Table 47. Read Multiple Block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 48. Read Multiple Block response format when Error_flag is NOT set. . . . . . . . . . . . . . . . . . . 87

DocID022712 Rev 12 9/144
M24LR64E-R List of tables
Table 49. Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 50. Read Multiple Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . 87
Table 51. Select request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 52. Select Block response format when Error_flag is NOT set. . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 53. Select response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 54. Reset to Ready request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 55. Reset to Ready response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . 90
Table 56. Reset to ready response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Table 57. Write AFI request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 58. Write AFI response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 59. Write AFI response format when Error_flag is set  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 60. Lock AFI request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 61. Lock AFI response format when Error_flag is NOT set  . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 62. Lock AFI response format when Error_flag is set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Table 63. Write DSFID request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 64. Write DSFID response format when Error_flag is NOT set  . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 65. Write DSFID response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 66. Lock DSFID request format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Table 67. Lock DSFID response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . . 95
Table 68. Lock DSFID response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Table 69. Get System Info request format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 70. Get System Info response format when Protocol_extension_flag = 0 and
Error_flag is NOT set  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 71. Get System Info response format when Protocol_extension_flag = 1 and
Error_flag is NOT set  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 72. Get System Info response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 73. Get Multiple Block Security Status request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Table 74. Get Multiple Block Security Status response format when Error_flag is NOT set  . . . . . . . 99
Table 75. Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Table 76. Get Multiple Block Security Status response format when Error_flag is set. . . . . . . . . . . . 99
Table 77. Write-sector Password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Table 78. Write-sector Password response format when Error_flag is NOT set  . . . . . . . . . . . . . . . 100
Table 79. Write-sector Password response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . 100
Table 80. Lock-sector request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Table 81. Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Table 82. Lock-sector response format when Error_flag is NOT set  . . . . . . . . . . . . . . . . . . . . . . . . 102
Table 83. Lock-sector response format when Error_flag is set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Table 84. Present-sector Password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Table 85. Present-sector Password response format when Error_flag is NOT set  . . . . . . . . . . . . . 103
Table 86. Present-sector Password response format when Error_flag is set. . . . . . . . . . . . . . . . . . 103
Table 87. Fast Read Single Block request format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Table 88. Fast Read Single Block response format when Error_flag is NOT set . . . . . . . . . . . . . . . 105
Table 89. Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Table 90. Fast Read Single Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . 105
Table 91. Fast Inventory Initiated request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Table 92. Fast Inventory Initiated response format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Table 93. Fast Initiate request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 94. Fast Initiate response format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 95. Fast Read Multiple Block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 96. Fast Read Multiple Block response format when Error_flag is NOT set. . . . . . . . . . . . . . 108
Table 97. Sector security status if Option_flag is set  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Table 98. Fast Read Multiple Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . 109

List of tables M24LR64E-R
10/144 DocID022712 Rev 12
Table 99. Inventory Initiated request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Table 100. Inventory Initiated response format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Table 101. Initiate request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Table 102. Initiate response format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Table 103. ReadCfg request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Table 104. ReadCfg response format when Error_flag is NOT set  . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Table 105. ReadCfg response format when Error_flag is set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Table 106. WriteEHCfg request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Table 107. WriteEHCfg response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . 113
Table 108. WriteEHCfg response format when Error_flag is set  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Table 109. WriteDOCfg request format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Table 110. WriteDOCfg response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . 115
Table 111. WriteDOCfg response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Table 112. SetRstEHEn request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Table 113. SetRstEHEn response format when Error_flag is NOT set  . . . . . . . . . . . . . . . . . . . . . . . 116
Table 114. SetRstEHEn response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Table 115. CheckEHEn request format  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Table 116. CheckEHEn response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . 117
Table 117. CheckEHEn response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Table 118. Absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Table 119. I2C operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 120. AC test measurement conditions  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 121. Input parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 122. I2C DC characteristics  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Table 123. I2C AC characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 124. Write cycle endurance  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Table 125. RF characteristics   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Table 126. Operating conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Table 127. Energy harvesting   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Table 128. SO8N – 8-lead plastic small outline, 150 mils body width,
package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Table 129. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch
dual flat package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Table 130. TSSOP8 – 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch, 
package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Table 131. Ordering information scheme for packaged devices  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Table 132. Ordering and marking information  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Table 133. CRC definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Table 134. AFI coding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Table 135. Document revision history  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

DocID022712 Rev 12 11/144
M24LR64E-R List of figures
List of figures
Figure 1. Logic diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 2. 8-pin package connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 3. I2C Fast mode (fC = 400 kHz): maximum Rbus value versus bus parasitic
capacitance (Cbus)  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 4. I2C bus protocol  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 5. Circuit diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 6. Memory sector organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 7. I²C timeout on Start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 8. Write mode sequences with I2C_Write_Lock bit = 1 (data write inhibited). . . . . . . . . . . . . 34
Figure 9. Write mode sequences with I2C_Write_Lock bit = 0 (data write enabled) . . . . . . . . . . . . . 35
Figure 10. Write cycle polling flowchart using Ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 11. Read mode sequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 12. I2C present password command  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 13. I2C write password command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 14. 100% modulation waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 15. 10% modulation waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 16. 1 out of 256 coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 17. Detail of a time period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 18. 1 out of 4 coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 19. 1 out of 4 coding example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 20. SOF to select 1 out of 256 data coding mode  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 21. SOF to select 1 out of 4 data coding mode  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 22. EOF for either data coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 23. Logic 0, high data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 24. Logic 0, high data rate, fast commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 25. Logic 1, high data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 26. Logic 1, high data rate, fast commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 27. Logic 0, low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 28. Logic 0, low data rate, fast commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 29. Logic 1, low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 30. Logic 1, low data rate, fast commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 31. Logic 0, high data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 32. Logic 1, high data rate  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 33. Logic 0, low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 34. Logic 1, low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 35. Start of frame, high data rate, one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 36. Start of frame, high data rate, one subcarrier, fast commands. . . . . . . . . . . . . . . . . . . . . . 55
Figure 37. Start of frame, low data rate, one subcarrier  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 38. Start of frame, low data rate, one subcarrier, fast commands  . . . . . . . . . . . . . . . . . . . . . . 56
Figure 39. Start of frame, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 40. Start of frame, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 41. End of frame, high data rate, one subcarrier  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 42. End of frame, high data rate, one subcarrier, fast commands  . . . . . . . . . . . . . . . . . . . . . . 57
Figure 43. End of frame, low data rate, one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 44. End of frame, low data rate, one subcarrier, Fast commands  . . . . . . . . . . . . . . . . . . . . . . 57
Figure 45. End of frame, high data rate, two subcarriers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 46. End of frame, low data rate, two subcarriers  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 47. M24LR64E-R decision tree for AFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

List of figures M24LR64E-R
12/144 DocID022712 Rev 12
Figure 48. M24LR64E-R protocol timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 49. M24LR64E-R state transition diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 50. Principle of comparison between the mask, the slot number and the UID . . . . . . . . . . . . . 72
Figure 51. Description of a possible anticollision sequence  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 52. M24LR64E RF-Busy management following Inventory command . . . . . . . . . . . . . . . . . . . 80
Figure 53. Stay Quiet frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . . . . 81
Figure 54. Read Single Block frame exchange between VCD and M24LR64E-R. . . . . . . . . . . . . . . . 83
Figure 55. Write Single Block frame exchange between VCD and M24LR64E-R. . . . . . . . . . . . . . . . 84
Figure 56. M24LR64E RF-Busy management following Write command . . . . . . . . . . . . . . . . . . . . . . 85
Figure 57. M24LR64E RF-Wip management following Write command . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 58. Read Multiple Block frame exchange between VCD and M24LR64E-R  . . . . . . . . . . . . . . 88
Figure 59. Select frame exchange between VCD and M24LR64E-R  . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 60. Reset to Ready frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . 90
Figure 61. Write AFI frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 62. Lock AFI frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 63. Write DSFID frame exchange between VCD and M24LR64E-R  . . . . . . . . . . . . . . . . . . . . 95
Figure 64. Lock DSFID frame exchange between VCD and M24LR64E-R. . . . . . . . . . . . . . . . . . . . . 96
Figure 65. Get System Info frame exchange between VCD and M24LR64E-R  . . . . . . . . . . . . . . . . . 98
Figure 66. Get Multiple Block Security Status frame exchange between VCD and M24LR64E-R . . . 99
Figure 67. Write-sector Password frame exchange between VCD and M24LR64E-R . . . . . . . . . . . 101
Figure 68. Lock-sector frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . . 102
Figure 69. Present-sector Password frame exchange between VCD and M24LR64E-R . . . . . . . . . 104
Figure 70. Fast Read Single Block frame exchange between VCD and M24LR64E-R. . . . . . . . . . . 105
Figure 71. Fast Initiate frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . . 107
Figure 72. Fast Read Multiple Block frame exchange between VCD and M24LR64E-R  . . . . . . . . . 109
Figure 73. Initiate frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . . . . . . 111
Figure 74. ReadCfg frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . . . . 112
Figure 75. WriteEHCfg frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . . 114
Figure 76. WriteDOCfg frame exchange between VCD and M24LR64E-R. . . . . . . . . . . . . . . . . . . . 115
Figure 77. SetRstEHEn frame exchange between VCD and M24LR64E-R . . . . . . . . . . . . . . . . . . . 116
Figure 78. CheckEHEn frame exchange between VCD and M24LR64E-R. . . . . . . . . . . . . . . . . . . . 118
Figure 79. AC test measurement I/O waveform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 80. I2C AC waveforms  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Figure 81. ASK modulated signal  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Figure 82. Energy harvesting: Vout min vs. Isink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 83. Energy harvesting: working domain range 11  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 84. Energy harvesting: working domain range 10  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 85. Energy harvesting: working domain range 01  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 86. Energy harvesting: working domain range 00  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 87. SO8N – 8-lead plastic small outline, 150 mils body width, package outline . . . . . . . . . . . 131
Figure 88. SO8N – 8-lead plastic small outline, 150 mils body width, 
package recommended footprint  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 89. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch
dual flat package outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 90. TSSOP8 – 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch,
package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

DocID022712 Rev 12 13/144

M24LR64E-R Description

1 Description

The M24LR64E-R device is a Dynamic NFC/RFID tag IC with a dual-interface, electrically

erasable programmable memory (EEPROM). It features an I2C interface and can be

operated from a VCC power supply. It is also a contactless memory powered by the received

carrier electromagnetic wave. The M24LR64E-R is organized as 8192 × 8 bits in the I2C

mode and as 2048 × 32 bits in the ISO 15693 and ISO 18000-3 mode 1 RF mode.

The M24LR64E-R also features an energy harvesting analog output, as well as a

user-configurable digital output pin toggling during either RF write in progress or RF busy

mode.

Figure 1. Logic diagram

The I2C uses a two-wire serial interface, comprising a bidirectional data line and a clock line.

The devices carry a built-in 4-bit device type identifier code (1010) in accordance with the

I2C bus definition.

The device behaves as a slave in the I2C protocol, with all memory operations synchronized

by the serial clock. Read and Write operations are initiated by a Start condition, generated

by the bus master. The Start condition is followed by a device select code and Read/Write

bit (RW) (as described in Table 2), terminated by an acknowledge bit.

When writing data to the memory, the device inserts an acknowledge bit during the 9th bit

time, following the bus master’s 8-bit transmission. When data is read by the bus master,

the bus master acknowledges the receipt of the data byte in the same way. Data transfers

are terminated by a Stop condition after an Ack for Write, and after a NoAck for Read.

In the ISO15693/ISO18000-3 mode 1 RF mode, the M24LR64E-R is accessed via the

13.56 MHz carrier electromagnetic wave on which incoming data is demodulated from the

received signal amplitude modulation (ASK: Amplitude Shift Keying). When connected to an

antenna, the operating power is derived from the RF energy and no external power supply is

required. The received ASK wave is 10% or 100% modulated with a data rate of 1.6 Kbit/s

0/5(5

6&/

6'$

$&

$&

06Y9

RXW

5):,3%86<

Description M24LR64E-R

14/144 DocID022712 Rev 12

using the 1 out of 256 pulse coding mode, or a data rate of 26 Kbit/s using the 1 out of 4

pulse coding mode.

Outgoing data is generated by the M24LR64E-R load variation using Manchester coding

with one or two subcarrier frequencies at 423 kHz and 484 kHz. Data is transferred from the

M24LR64E-R at 6.6 Kbit/s in low data rate mode and at 26 Kbit/s in high data rate mode.

The M24LR64E-R supports the 53 Kbit/s fast mode in high data rate mode using one

subcarrier frequency at 423 kHz.

The M24LR64E-R follows the ISO 15693 and ISO 18000-3 mode 1 recommendation for

radio-frequency power and signal interface.

The M24LR64E-R provides an Energy harvesting mode on the analog output pin Vout.

When the Energy harvesting mode is activated, the M24LR64E-R can output the excess

energy coming from the RF field on the Vout analog pin. In case the RF field strength is

insufficient or when the Energy harvesting mode is disabled, the analog output pin Vout goes

into high-Z state and the Energy harvesting mode is automatically stopped.

The M24LR64E-R features a user configurable digital out pin RF WIP/BUSY that can be

used to drive a microcontroller interrupt input pin (available only when the M24LR64E-R is

correctly powered on the VCC pin).

When configured in the RF write in progress mode (RF WIP mode), the RF WIP/BUSY pin is

driven low for the entire duration of the RF internal write operation. When configured in the

RF busy mode (RF BUSY mode), the RF WIP/BUSY pin is driven low for the entire duration

of the RF command progress.

The RF WIP/BUSY pin is an open drain output and must be connected to a pull-up resistor.

Figure 2. 8-pin package connections

1. See Section 31 for package dimensions, and how to identify pin 1.

Table 1. Signal names

Signal name Function Direction

Vout Energy harvesting Output Analog output

SDA Serial Data I/O

SCL Serial Clock Input

AC0, AC1 Antenna coils I/O

VCC Supply voltage -

RF WIP/BUSY Digital signal Digital output

VSS Ground -

069

6'$

966

6&/

5):,3%86<$&

9RXW 9&&

















$&

DocID022712 Rev 12 15/144

M24LR64E-R Signal descriptions

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 VCC. (Figure 3 indicates how the value of the pull-up resistor can be calculated). 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 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 VCC. (Figure 3 indicates how

the value of the pull-up resistor can be calculated).

2.3 RF Write in progress / RF Busy (RF WIP/BUSY)

This configurable output signal is used either to indicate that the M24LR64E-R is executing

an internal write cycle from the RF channel or that an RF command is in progress. RF WIP

and signals are available only when the M24LR64E-R is powered by the Vcc pin. It is an

open drain output and a pull-up resistor must be connected from RF WIP/BUSY to VCC.

2.4 Energy harvesting analog output (Vout)

This analog output pin is used to deliver the analog voltage Vout available when the Energy

harvesting mode is enabled and the RF field strength is sufficient. When the Energy

harvesting mode is disabled or the RF field strength is not sufficient, the energy harvesting

analog voltage output Vout is in High-Z state.

2.5 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 power and access the device using the ISO 15693

and ISO 18000-3 mode 1 protocols.

2.5.1 Device reset in RF mode

To ensure a proper reset of the RF circuitry, the RF field must be turned off (100%

modulation) for a minimum tRF_OFF period of time.

Signal descriptions M24LR64E-R

16/144 DocID022712 Rev 12

2.6 VSS ground

VSS is the reference for the VCC supply voltage and Vout analog output voltage.

2.7 Supply voltage (VCC)

This pin can be connected to an external DC supply voltage.

Note: An internal voltage regulator allows the external voltage applied on VCC to supply the

M24LR64E-R, while preventing the internal power supply (rectified RF waveforms) to output

a DC voltage on the VCC pin.

2.7.1 Operating supply voltage VCC

Prior to selecting the memory and issuing instructions to it, a valid and stable VCC voltage

within the specified [VCC(min), VCC(max)] range must be applied (see Table 119). To

maintain a stable DC supply voltage, it is recommended to decouple the VCC line with a

suitable capacitor (usually around 10 nF) close to the VCC/VSS package pins.

This voltage must remain stable and valid until the end of the transmission of the instruction

and, for a Write instruction, until the completion of the internal I²C write cycle (tW).

2.7.2 Power-up conditions

When the power supply is turned on, VCC rises from VSS to VCC. The VCC rise time must not

vary faster than 1V/µs.

2.7.3 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 VCC), the device does not respond to any

I²C instruction until VCC has reached the power-on reset threshold voltage (this threshold is

lower than the minimum VCC operating voltage defined in Table 119). When VCC passes

over the POR threshold, the device is reset and enters the Standby power mode. However,

the device must not be accessed until VCC has reached a valid and stable VCC voltage

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

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

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

sent to it.

2.7.4 Power-down conditions

During power-down (continuous decay of VCC), the device must be in Standby power mode

(mode reached after decoding a Stop condition, assuming that there is no internal write

cycle in progress).

DocID022712 Rev 12 17/144

M24LR64E-R Signal descriptions

Figure 3. I2C Fast mode (fC = 400 kHz): maximum Rbus value versus bus parasitic

capacitance (Cbus)

Figure 4. I2C bus protocol

AIB







  

"USLINECAPACITORP&

"USLINEPULLUPRESISTOR

K 



)£#BUS

MASTER -XXX

2BUS

6##

#BUS

3#,

3$!

2BUS§#BUSNS

(ERE2BUS§#BUSNS

K½

P&

4HE2X#TIMECONSTANT

MUSTBEBELOWTHENS

TIMECONSTANTLINEREPRESENTED

ONTHELEFT

BUS BUS

Signal descriptions M24LR64E-R

18/144 DocID022712 Rev 12

Table 2. Device select code

Device type identifier(1)

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

Chip Enable address RW

b7 b6 b5 b4 b3 b2 b1 b0

Device select code1010E2

(2)

2. E2 is not connected to any external pin. It is however used to address the M24LR64E-R as

described in Section 3 and Section 4.

11RW

Table 3. Address most significant byte

b15 b14 b13 b12 b11 b10 b9 b8

Table 4. Address least significant byte

b7 b6 b5 b4 b3 b2 b1 b0

DocID022712 Rev 12 19/144

M24LR64E-R User memory organization

3 User memory organization

The M24LR64E-R is divided into 64 sectors of 32 blocks of 32 bits, as shown in Table 5.

Figure 6 shows the memory sector organization. Each sector can be individually read-

and/or write-protected using a specific password command. Read and write operations are

possible if the addressed data is not in a protected sector.

The M24LR64E-R also has a 64-bit block that is used to store the 64-bit unique identifier

(UID). The UID is compliant with the ISO 15963 description, and its value is used during the

anticollision sequence (Inventory). This block is not accessible by the user in RF device

operation and its value is written by ST on the production line.

The M24LR64E-R includes an AFI register that stores the application family identifier, and a

DSFID register that stores the data storage family identifier used in the anticollision

algorithm.

The M24LR64E-R has four 32-bit blocks that store an I2C password plus three RF password

codes.

Figure 5. Circuit diagram

069

5)9&&

$&

$&

3RZHUPDQDJHPHQW

9RXW

5):,3%86<

/RJLF

((3520

/DWFK

,&

&RQWDFW9&&

6&/

6'$

9&&

966

5RZGHFRGHU

User memory organization M24LR64E-R

20/144 DocID022712 Rev 12

Figure 6. Memory sector organization

Sector details

The M24LR64E-R user memory is divided into 64 sectors. Each sector contains 1024 bits.

The protection scheme is described in Section 4: System memory area.

In RF mode, a sector provides 32 blocks of 32 bits. Each read and write access is done by

block. Read and write block accesses are controlled by a Sector Security Status byte that

defines the access rights to the 32 blocks contained in the sector. If the sector is not

protected, a Write command updates the complete 32 bits of the selected block.

In I2C mode, a sector provides 128 bytes that can be individually accessed in Read and

Write modes. When protected by the corresponding I2C_Write_Lock bit, the entire sector is

write-protected. To access the user memory, the device select code used for any I2C

command must have the E2 Chip Enable address at 0.

D^ϯϬϳϲϯsϭ

ϭ<ďŝƚWZKDƐĞĐƚŽƌ

^ĞĐƚŽƌ ƌĞĂ ^ĞĐƚŽƌƐĞĐƵƌŝƚǇ

ƐƚĂƚƵƐ

ϭ<ďŝƚWZKDƐĞĐƚŽƌ

/ϸƉĂƐƐǁŽƌĚ

Z&ƉĂƐƐǁŽƌĚϭ

Z&ƉĂƐƐǁŽƌĚϮ

Z&ƉĂƐƐǁŽƌĚϯ

ϴͲďŝƚ^&/

ϴͲďŝƚ&/

ϴͲďŝƚĐŽŶĨŝŐƵƌĂƚŝŽŶ

ϭϲͲďŝƚ/ϸtƌŝƚĞ>ŽĐŬͺďŝƚ

ϲϰͲďŝƚh/

ϲϬ

ϲϭ

ϲϮ

ϲϯ

ϱďŝƚƐ

^ǇƐƚĞŵ

ϴϬͲďŝƚ^^^ ^ǇƐƚĞŵ



DocID022712 Rev 12 21/144

M24LR64E-R User memory organization

Table 5. Sector details

Sector

number

RF block

address

I2C byte

address Bits [31:24] Bits [23:16] Bits [15:8] Bits [7:0]

0 0 user user user user

1 4 user user user user

2 8 user user user user

3 12 user user user user

4 16 user user user user

5 20 user user user user

6 24 user user user user

7 28 user user user user

8 32 user user user user

9 36 user user user user

10 40 user user user user

11 44 user user user user

12 48 user user user user

13 52 user user user user

14 56 user user user user

15 60 user user user user

16 64 user user user user

17 68 user user user user

18 72 user user user user

19 76 user user user user

20 80 user user user user

21 84 user user user user

22 88 user user user user

23 92 user user user user

24 96 user user user user

25 100 user user user user

26 104 user user user user

27 108 user user user user

28 112 user user user user

29 116 user user user user

30 120 user user user user

31 124 user user user user

User memory organization M24LR64E-R

22/144 DocID022712 Rev 12

32 128 user user user user

33 132 user user user user

34 136 user user user user

35 140 user user user user

36 144 user user user user

37 148 user user user user

38 152 user user user user

39 156 user user user user

...

Table 5. Sector details (continued)

Sector

number

RF block

address

I2C byte

address Bits [31:24] Bits [23:16] Bits [15:8] Bits [7:0]

DocID022712 Rev 12 23/144

M24LR64E-R User memory organization

2016 8064 user user user user

2017 8068 user user user user

2018 8072 user user user user

2019 8076 user user user user

2020 8080 user user user user

2021 8084 user user user user

2022 8088 user user user user

2023 8092 user user user user

2024 8096 user user user user

2025 8100 user user user user

2026 8104 user user user user

2027 8108 user user user user

2028 8112 user user user user

2029 8116 user user user user

2030 8120 user user user user

2031 8124 user user user user

2032 8128 user user user user

2033 8132 user user user user

2034 8136 user user user user

2035 8140 user user user user

2036 8144 user user user user

2037 8148 user user user user

2038 8152 user user user user

2039 8156 user user user user

2040 8160 user user user user

2041 8164 user user user user

2042 8168 user user user user

2043 8172 user user user user

2044 8176 user user user user

2045 8180 user user user user

2046 8184 user user user user

2047 8188 user user user user

Table 5. Sector details (continued)

Sector

number

RF block

address

I2C byte

address Bits [31:24] Bits [23:16] Bits [15:8] Bits [7:0]

System memory area M24LR64E-R

24/144 DocID022712 Rev 12

4 System memory area

4.1 M24LR64E-R block security in RF mode

The M24LR64E-R provides a special protection mechanism based on passwords. In RF

mode, each memory sector of the M24LR64E-R can be individually protected by one out of

three available passwords, and each sector can also have Read/Write access conditions

set.

Each memory sector of the M24LR64E-R is assigned with a Sector security status byte

including a Sector Lock bit, two Password Control bits and two Read/Write protection bits,

as shown in Table 7.

Table 6 describes the organization of the Sector security status byte, which can be read

using the Read Single Block and Read Multiple Block commands with the Option_flag set

to 1.

On delivery, the default value of the SSS bytes is set to 00h.

Table 6. Sector security status byte area

I2C byte address Bits [31:24] Bits [23:16] Bits [15:8] Bits [7:0]

E2 = 1 0 SSS 3 SSS 2 SSS 1 SSS 0

E2 = 1 4 SSS 7 SSS 6 SSS 5 SSS 4

E2 = 1 8 SSS 11 SSS 10 SSS 9 SSS 8

E2 = 1 12 SSS 15 SSS 14 SSS 13 SSS 12

E2 = 1 16 SSS 19 SSS 18 SSS 17 SSS 16

E2 = 1 20 SSS 23 SSS 22 SSS 21 SSS 20

E2 = 1 24 SSS 27 SSS 26 SSS 25 SSS 24

E2 = 1 28 SSS 31 SSS 30 SSS 29 SSS 28

E2 = 1 32 SSS 35 SSS 34 SSS 33 SSS 32

E2 = 1 36 SSS 39 SSS 38 SSS 37 SSS 36

E2 = 1 40 SSS 43 SSS 42 SSS 41 SSS 40

E2 = 1 44 SSS 47 SSS 46 SSS 45 SSS 44

E2 = 1 48 SSS 51 SSS 50 SSS 49 SSS 48

E2 = 1 52 SSS 55 SSS 54 SSS 53 SSS 52

E2 = 1 56 SSS 59 SSS 58 SSS 57 SSS 56

E2 = 1 60 SSS 63 SSS 62 SSS 61 SSS 60

Table 7. Sector security status byte organization

b7b6b5b4b3b2b1b0

0 0 0 Password control bits Read / Write

protection bits

Sector

Lock

DocID022712 Rev 12 25/144

M24LR64E-R System memory area

When the Sector Lock bit is set to 1, for instance by issuing a Lock-sector command, the

two Read/Write protection bits (b1, b2) are used to set the Read/Write access of the sector

as described in Table 8.

The next two bits of the Sector security status byte (b3, b4) are the password control bits.

The value of these two bits is used to link a password to the sector, as defined in Table 9.

The M24LR64E-R password protection is organized around a dedicated set of commands,

plus a system area of three password blocks where the password values are stored. This

system area is described in Table 10.

The dedicated commands for protection in RF mode are:

•Write-sector password:

The Write-sector password command is used to write a 32-bit block into the password

system area. This command must be used to update password values. After the write

cycle, the new password value is automatically activated. It is possible to modify a

password value after issuing a valid Present-sector password command. On delivery,

the three default password values are set to 0000 0000h and are activated.

•Lock-sector:

The Lock-sector command is used to set the sector security status byte of the selected

sector. Bits b4 to b1 of the sector security status byte are affected by the Lock-sector

Table 8. Read/Write protection bit setting

Sector

Lock b2, b1

Sector access

when password presented

Sector access

when password not presented

0 xx Read Write Read Write

1 00 Read Write Read No Write

1 01 Read Write Read Write

1 10 Read Write No Read No Write

1 11 Read No Write No Read No Write

Table 9. Password control bits

b4, b3Password

00 The sector is not protected by a password.

01 The sector is protected by password 1.

10 The sector is protected by password 2.

11 The sector is protected by password 3.

Table 10. Password system area

Add Password

1 Password 1

2 Password 2

3 Password 3

System memory area M24LR64E-R

26/144 DocID022712 Rev 12

command. The sector lock bit, b0, is set to 1 automatically. After issuing a Lock-sector

command, the protection settings of the selected sector are activated. The protection of

a locked block cannot be changed in RF mode. A Lock-sector command sent to a

locked sector returns an error code.

•Present-sector password:

The Present-sector password command is used to present one of the three passwords

to the M24LR64E-R in order to modify the access rights of all the memory sectors

linked to that password (Table 8) including the password itself. If the presented

password is correct, the access rights remain activated until the tag is powered off or

until a new Present-sector password command is issued. If the presented password

value is not correct, all the access rights of all the memory sectors are deactivated.

•Sector security status byte area access conditions in I2C mode:

In I2C mode, read access to the sector security status byte area is always allowed.

Write access depends on the correct presentation of the I2C password (see

Section 5.16.1: I2C present password command description).

To access the Sector security status byte area, the device select code used for any I2C

command must have the E2 Chip Enable address at 1.

An I2C write access to a sector security status byte re-initializes the RF access

condition to the given memory sector.

4.1.1 Example of the M24LR64E-R security protection in RF mode

Table 11 and Table 12 show the sector security protections before and after a valid Present-

sector password command. Table 11 shows the sector access rights of an M24LR64E-R

after power-up. After a valid Present-sector password command with password 1, the

memory sector access is changed as shown in Table 12.

Table 11. M24LR64E-R sector security protection after power-up

Sector

address Sector features

Sector security status byte

b7b6b5b4b3b2b1b0

0 Protection: standard Read No Write xxx 00001

1 Protection: password 1 Read No Write xxx 01001

2 Protection: password 1 Read Write xxx 01011

3 Protection: password 1 No Read No Write xxx 01101

4 Protection: password 1 No Read No Write xxx 01111

Table 12. M24LR64E-R sector security protection after a valid presentation of

password 1

Sector

address Sector features

Sector security status byte

b7b6b5b4b3b2b1b0

0 Protection: standard Read No Write xxx 00001

1 Protection: password 1 Read Write xxx 01001

2 Protection: password 1 Read Write xxx 01011

DocID022712 Rev 12 27/144

M24LR64E-R System memory area

4.2 M24LR64E-R block security in I²C mode (I2C_Write_Lock bit

area)

In the I2C mode only, it is possible to protect individual sectors against Write operations.

This feature is controlled by the I2C_Write_Lock bits stored in the 8 bytes of the

I2C_Write_Lock bit area. I2C_Write_Lock bit area starts from location 8192 (see Table 13).

To access the I2C_Write_Lock bit area, the device select code used for any I2C command

must have the E2 Chip Enable address at 1.

Using these 16 bits, it is possible to write-protect all the 64 sectors of the M24LR64E-R

memory. Each bit controls the I2C write access to a specific sector as shown in Table 13. It

is always possible to unprotect a sector in the I2C mode. When an I2C_Write_Lock bit is

reset to 0, the corresponding sector is unprotected. When the bit is set to 1, the

corresponding sector is write-protected.

In I2C mode, read access to the I2C_Write_Lock bit area is always allowed. Write access

depends on the correct presentation of the I2C password.

On delivery, the default value of the eight bytes of the I2C_Write_Lock bit area is reset to

00h.

4.3 Configuration byte and Control register

The M24LR64E-R offers an 8-bit non-volatile Configuration byte located at I²C location 2320

of the system area used to store the RF WIP/BUSY pin and the energy harvesting

configuration (see Table 14).

The M24LR64E-R also offers an 8-bit volatile Control register located at I²C location 2336 of

the system area used to store the energy harvesting enable bit as well as a FIELD_ON bit

indicator (see Table 15).

4.3.1 RF WIP/BUSY pin configuration

The M24LR64E-R features a configurable open drain output RF WIP/BUSY pin used to

provide RF activity information to an external device.

3 Protection: password 1 Read Write xxx 01101

4 Protection: password 1 Read No Write xxx 01111

Table 12. M24LR64E-R sector security protection after a valid presentation of

password 1 (continued)

Sector

address Sector features

Sector security status byte

b7b6b5b4b3b2b1b0

Table 13. I2C_Write_Lock bit

I2C byte address Bits [31:24] Bits [23:16] Bits [15:8] Bits [7:0]

E2 = 1 2048 sectors 31-24 sectors 23-16 sectors 15-8 sectors 7-0

E2 = 1 2052 sectors 63-56 sectors 55-48 sectors 47-40 sectors 39-32

System memory area M24LR64E-R

28/144 DocID022712 Rev 12

The RF WIP/BUSY pin functionality depends on the value of bit 3 of the Configuration byte.

•RF busy mode

When bit 3 of the Configuration byte is set to 0, the RF WIP/BUSY pin is configured in RF

busy mode.

The purpose of this mode is to indicate to the I²C bus master whether the M24LR64E-R is

busy in RF mode or not.

In this mode, the RF WIP/BUSY pin is tied to 0 from the RF command Start Of Frame (SOF)

until the end of the command execution.

If a bad RF command is received, the RF WIP/BUSY pin is tied to 0 from the RF command

SOF until the reception of the RF command CRC. Otherwise, the RF WIP/BUSY pin is in

high-Z state.

When tied to 0, the RF WIP/BUSY signal returns to High-Z state if the RF field is cut-off.

During the execution of I²C commands, the RF WIP/BUSY pin remains in high-Z state.

•RF Write in progress

When bit 3 of the Configuration byte is set to 1, the RF WIP/BUSY pin is configured in RF

Write in progress mode.

The purpose of this mode is to indicate to the I²C bus master that some data has been

changed in RF mode.

In this mode, the RF WIP/BUSY pin is tied to 0 for the duration of an internal write operation

(i.e. between the end of a valid RF write command and the beginning of the RF answer).

During the execution of I²C write operations, the RF WIP/BUSY pin remains in high-Z state.

4.3.2 Energy harvesting configuration

The M24LR64E-R features an Energy harvesting mode on the Vout analog output.

The general purpose of the Energy harvesting mode is to deliver a part of the non-

necessary RF power received by the M24LR64E-R on the AC0-AC1 RF input in order to

supply an external device. The current consumption on the analog voltage output Vout is

limited to ensure that the M24LR64E-R is correctly supplied during the powering of the

external device.

When the Energy harvesting mode is enabled and the power delivered on the AC0-AC1 RF

input exceeds the minimum required PAC0-AC1_min, the M24LR64E-R is able to deliver a

limited and unregulated voltage on the Vout pin, assuming the current consumption on the

Vout does not exceed the Isink_max maximum value.

If one of the conditions above is not met, the analog voltage output pin Vout is set in High-Z

state.

For robust applications using the Energy harvesting mode, four current fan-out levels can be

chosen.

DocID022712 Rev 12 29/144

M24LR64E-R System memory area

•Vout sink current configuration

The sink current level is chosen by programming EH_cfg1 and EH_cfg0 into the

Configuration byte (see Table 14).

The minimum power level required on AC0-AC1 RF input PAC0-AC1_min, the delivered

voltage Vout, as well as the maximum current consumption Isink_max on the Vout pin

corresponding to the <EH_cfg1,EH_cfg0> bit values are described in Table 127.

•Energy harvesting enable control

Delivery of Energy harvesting analog output voltage on the Vout pin depends on the value of

the EH_enable bit of the volatile Control register (see Table 15).

– When set to 1, the EH_enable bit enables the Energy harvesting mode, meaning

that the Vout analog output signal is delivered when the PAC0-AC1_min and Isink_max

conditions corresponding to the chosen sink current configuration bit are met (see

Table 127).

– When set to 0, the EH_enable bit disables the Energy harvesting mode and the

analog output Vout remains in High-Z state.

– The T_Prog flag indicates a correct duration of the I²C write time (tw). This bit is

reset to 0 after POR and at the beginning of each writing cycle; it is set to 1 only

after a correct completion of the writing cycle.

•Energy harvesting default mode control

At power-up, in I²C or RF mode, the EH_enable bit is updated according to the value of the

EH_mode bit stored in the non-volatile Configuration byte (see Table 16). In other words,

the EH_mode bit is used to configure whether the Energy harvesting mode is enabled or not

by default.

Table 14. Configuration byte

I2C byte address Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 BIT 1 BIT 0

E2=1 2320 X(1)

1. Bit 7 to bit 4 are don’t care bits.

X(1) X(1) X(1) RF WIP/BUSY EH_mode EH_cfg1 EH_cfg0

Table 15. Control register

I2C byte address Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 BIT 1 BIT 0

E2=1 2336 T-Prog(1)

1. Bit 7 to bit 1 are read-only bits.

0(1) 0(1) 0(1) 0(1) 0(1) FIELD_ON(1) EH_enable

Table 16. EH_enable bit value after power-up

EH_mode value EH_enable after power-up Energy harvesting

after power-up

0 1 enabled

1 0 disabled

System memory area M24LR64E-R

30/144 DocID022712 Rev 12

4.3.3 FIELD_ON indicator bit

The FIELD_ON indicator bit located as bit 1 of the Control register is a read-only bit used to

indicate when the RF power level delivered to the M24LR64E-R is sufficient to execute RF

commands.

•When FIELD_ON = 0, the M24LR64E-R is not able to execute any RF commands.

•When FIELD_ON =1, the M24LR64E-R is able to execute any RF commands.

Note: During read access to the Control register in RF mode, the FIELD_ON bit is always read

at 1.

4.3.4 Configuration byte access in I²C and RF modes

In I²C mode, read and write accesses to the non-volatile Configuration byte are always

allowed. To access the Configuration byte, the device select code used for any I²C

command must have the E2 Chip enable address at 1.

The dedicated commands to access the Configuration byte in RF mode are:

•Read configuration byte command (ReadCfg):

– The ReadCfg command is used to read the eight bits of the Configuration byte.

•Write energy harvesting configuration command (WriteEHCfg):

– The WriteEHCfg command is used to write the EH_mode, EH_cfg1 and EH_cfg0

bits into the Configuration byte.

•Write RF WIP/BUSY pin configuration command (WriteDOCfg):

– The WriteDOCfg command is used to write the RF WIP/BUSY bit into the

Configuration byte.

After any write access to the Configuration byte, the new configuration is automatically

applied.

4.3.5 Control register access in I²C or RF mode

In I²C mode, read and write accesses to the volatile Control register are always allowed. To

access the Control register, the device select code used for any I²C command must have

the E2 Chip enable address at 1.

The dedicated commands to access the Control register in RF mode are:

•Check energy harvesting enable bit command (CheckEHEn):

– The CheckEHEn command is used to read the eight bits of the Control register.

When it is run, the FIELD_ON bit is always read at 1.

•Set/reset energy harvesting enable bit command (SetRstEHEn):

– The SetRstEHEn command is used to set or reset the value of the EH_enable bit

into the Control register.

4.4 ISO 15693 system parameters

The M24LR64E-R provides the system area required by the ISO 15693 RF protocol, as

shown in Table 17.

The first 32-bit block starting from I2C address 2304 stores the I2C password. This

password is used to activate/deactivate the write protection of the protected sector in I2C

DocID022712 Rev 12 31/144

M24LR64E-R System memory area

mode. At power-on, all user memory sectors protected by the I2C_Write_Lock bits can be

read but cannot be modified. To remove the write protection, it is necessary to use the I2C

present password described in Figure 12. When the password is correctly presented — that

is, when all the presented bits correspond to the stored ones — it is also possible to modify

the I2C password using the I2C write password command described in Figure 13.

The next three 32-bit blocks store the three RF passwords. These passwords are neither

read- nor write- accessible in the I2C mode.

The next byte stores the Configuration byte, at I²C location 2320. This Control register is

used to store the three energy harvesting configuration bits and the RF WIP/BUSY

configuration bit.

The next two bytes are used to store the AFI, at I2C location 2322, and the DSFID, at I2C

location 2323. These two values are used during the RF inventory sequence. They are

read-only in the I2C mode.

The next eight bytes, starting from location 2324, store the 64-bit UID programmed by ST on

the production line. Bytes at I2C locations 2332 to 2335 store the IC Ref and the Mem_Size

data used by the RF Get_System_Info command. The UID, Mem_Size and IC ref values are

read-only data.

Table 17. System parameter sector

I2C byte address Bits [31:24] Bits [23:16] Bits [15:8] Bits [7:0]

E2 = 1 2304 I2C password(1)

1. Delivery state: I2C password = 0000 0000h, RF password = 0000 0000h, Configuration byte =

F4h

E2 = 1 2308 RF password 1(1)

E2 = 1 2312 RF password 2(1)

E2 = 1 2316 RF password 3(1)

E2 = 1 2320 DSFID (FFh) AFI (00h) ST reserved (Exh)(2)

2. The product revision is the Most significant nibble of the byte located at address 0x911 (2321 d)

in the system area (Device select code E2 =1). From DS rev4, the product revision value is

0xE. The Least significant nibble is ST reserved.

Configuration byte (F4h)

E2 = 1 2324 UID UID UID UID

E2 = 1 2328 UID (E0h) UID (02h) UID UID

E2 = 1 2332 Mem_Size (03 07FFh) IC Ref (5Eh)

E2 = 1 2336 - - - Prog. completion and

Energy harvesting status(3)

3. Address system 2336 (920h, E2=1) is the control register.

Bit 7 is T_Prog (refer to Table 15: Control register). When accessed in RF, this bit is not

significant and set to 0.

Bits 2-6 are RFU and set to 0.

Bit 1 is FIELD_ON (refer to Table 15: Control register).

Bit 0 is EH_enable (refer to Table 15: Control register).

I2C device operation M24LR64E-R

32/144 DocID022712 Rev 12

5 I2C device operation

The device supports the I2C protocol. This is summarized in Figure 4. Any device that sends

data to the bus is defined as a transmitter, and any device that reads data is defined as a

receiver. The device that controls the data transfer is known as the bus master, and the

other as the slave device. A data transfer can only be initiated by the bus master, which also

provides the serial clock for synchronization. The M24LR64E-R device is a slave in all

communications.

5.1 Start condition

Start 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 a write cycle) the SDA and the SCL for a Start

condition, and does not respond unless one is given.

5.2 Stop condition

Stop is identified by a rising edge of serial data (SDA) while the serial clock (SCL) is stable

and driven high. A Stop condition terminates communication between the device and the

bus master. A Read command that is followed by NoAck can be followed by a Stop condition

to force the device into the Standby mode. A Stop condition at the end of a Write command

triggers the internal write cycle.

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

5.4 Data input

During data input, the device samples serial data (SDA) on the rising edge of the serial clock

(SCL). For 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.

5.5 I²C timeout

During the execution of an I²C operation, RF communications are not possible.

To prevent RF communication freezing due to inadvertent unterminated instructions sent to

the I²C bus, the M24LR64E-R features a timeout mechanism that automatically resets the

I²C logic block.

DocID022712 Rev 12 33/144

M24LR64E-R I2C device operation

5.5.1 I²C timeout on Start condition

I²C communication with the M24LR64E-R 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 tSTART_OUT time

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

until the next valid Start condition.

Figure 7. I²C timeout on Start condition

5.5.2 I²C timeout on clock period

During data transfer on the I²C bus, if the serial clock pulse width high (tCHCL) or serial clock

pulse width low (tCLCH) exceeds the maximum value specified in Table 123, the I²C logic

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

condition.

5.6 Memory addressing

To start a communication between the bus master and the slave device, the bus master

must initiate a Start condition. Following this, the bus master sends the device select code,

shown in Table 2 (on Serial Data (SDA), the most significant bit first).

The device select code consists of a 4-bit device type identifier and a 3-bit Chip Enable

“Address” (E2,1,1). To address the memory array, the 4-bit device type identifier is 1010b.

Refer to Table 2.

The eighth bit is the Read/Write bit (RW). It is set to 1 for Read and to 0 for Write operations.

If a match occurs on the device select code, the corresponding device gives an

acknowledgment on serial data (SDA) during the ninth bit time. If the device does not match

the device select code, it deselects itself from the bus, and goes into Standby mode.

069

6&/

6'$

W67$57B287

6WDUW

FRQGLWLRQ

I2C device operation M24LR64E-R

34/144 DocID022712 Rev 12

Figure 8. Write mode sequences with I2C_Write_Lock bit = 1 (data write inhibited)

5.7 Write operations

Following a Start condition, the bus master sends a device select code with the Read/Write

bit (RW) reset to 0. The device acknowledges this, as shown in Figure 8, and waits for two

address bytes. The device responds to each address byte with an acknowledge bit, and

then waits for the data byte.

Writing to the memory may be inhibited if the I2C_Write_Lock bit = 1. A Write instruction

issued with the I2C_Write_Lock bit = 1 and with no I2C_Password presented does not

modify the memory contents, and the accompanying data bytes are not acknowledged, as

shown in Figure 8.

Each data byte in the memory has a 16-bit (two-byte wide) address. The most significant

byte (Table 3) is sent first, followed by the least significant byte (Table 4). Bits b15 to b0 form

the address of the byte in memory.

Table 18. Operating modes

Mode RW bit Bytes Initial sequence

Current address read 1 1 Start, device select, RW = 1

Random address read

Start, device select, RW = 0, address

1 reStart, device select, RW = 1

Sequential read 1 ≥ 1 Similar to current or random address read

Byte write 0 1 Start, device select, RW = 0

Page write 0 ≤ 4 bytes Start, device select, RW = 0

3TOP

3TART

"YTE7RITE $EVSELECT "YTEADDRESS "YTEADDRESS $ATAIN

3TART

0AGE7RITE $EVSELECT "YTEADDRESS "YTEADDRESS $ATAIN $ATAIN

!)

0AGE7RITE

CONTgD

3TOP

$ATAIN.

!#+ !#+ !#+ ./!#+

27

!#+ !#+ !#+ ./!#+

27

./!#+ ./!#+

DocID022712 Rev 12 35/144

M24LR64E-R I2C device operation

When the bus master generates a Stop condition immediately after the Ack bit (in the tenth-

bit time slot), either at the end of a byte write or a page write, the internal write cycle is

triggered. A Stop condition at any other time slot does not trigger the internal write cycle.

After the Stop condition, the delay tW, and the successful completion of a Write operation,

the device’s internal address counter is incremented automatically, to point to the next byte

address after the last one that was modified.

During the internal write cycle, the serial data (SDA) signal is disabled internally, and the

device does not respond to any requests.

5.8 Byte write

After the device select code and the address bytes, the bus master sends one data byte. If

the addressed location is write-protected by the I2C_Write_Lock bit (= 1), the device replies

with NoAck, and the location is not modified. If the addressed location is not write-protected,

the device replies with Ack. The bus master terminates the transfer by generating a Stop

condition, as shown in Figure 9.

5.9 Page write

The Page write mode allows up to four bytes to be written in a single write cycle, provided

that they are all located in the same “row” in the memory: that is, the most significant

memory address bits (b12-b2) are the same. If more bytes are sent than fit up to the end of

the row, a condition known as “roll-over” occurs. This should be avoided, as data starts to

become overwritten in an implementation-dependent way.

The bus master sends from one to four bytes of data, each of which is acknowledged by the

device if the I2C_Write_Lock bit = 0 or the I2C_Password was correctly presented. If the

I2C_Write_Lock_bit = 1 and the I2C_password are not presented, the contents of the

addressed memory location are not modified, and each data byte is followed by a NoAck.

After each byte is transferred, the internal byte address counter (inside the page) is

incremented. The transfer is terminated by the bus master generating a Stop condition.

Figure 9. Write mode sequences with I2C_Write_Lock bit = 0 (data write enabled)

3TOP

3TART

"YTE7RITE $EV3ELECT "YTEADDRESS "YTEADDRESS $ATAIN

3TART

0AGE7RITE $EV3ELECT "YTEADDRESS "YTEADDRESS $ATAIN $ATAIN

!)

3TOP

$ATAIN.

!#+

27

!#+ !#+ !#+

!#+ !#+ !#+ !#+

27

!#+!#+

I2C device operation M24LR64E-R

36/144 DocID022712 Rev 12

Figure 10. Write cycle polling flowchart using Ack

5.10 Minimizing system delays by polling on Ack

During the internal write cycle, the device disconnects itself from the bus, and writes a copy

of the data from its internal latches to the memory cells. The maximum I²C write time (tw) is

shown in Table 123, but the typical time is shorter. To make use of this, a polling sequence

can be used by the bus master.

The sequence, as shown in Figure 10, is:

1. Initial condition: a write cycle is in progress.

2. Step 1: the bus master issues a Start condition followed by a device select code (the

first byte of the new instruction).

3. Step 2: if the device is busy with the internal write cycle, no Ack is returned and the bus

master goes back to Step 1. If the device has terminated the internal write cycle, it

responds with an Ack, indicating that the device is ready to receive the second part of

the instruction (the first byte of this instruction having been sent during Step 1).

069

:ULWHF\FOHLQSURJUHVV

6WDUWFRQGLWLRQ

$FNUHWXUQHG

1H[WRSHUDWLRQLV

DGGUHVVLQJWKHPHPRU\

6WDUWFRQGLWLRQ

6HQGDGGUHVV

DQG5HFHLYH$FN

'DWDIRUWKH

:ULWHRSHUDWLRQ

5H6WDUW

6WRS

<HV

&RQWLQXHWKH

:ULWHRSHUDWLRQ

&RQWLQXHWKH

5DQGRP5HDGRSHUDWLRQ

)LUVWE\WHRILQVWUXFWLRQ

ZLWK5: DOUHDG\

GHFRGHGE\WKHGHYLFH

'HYLFHVHOHFWZLWK5: 

'HYLFHVHOHFW

ZLWK5: 

DocID022712 Rev 12 37/144

M24LR64E-R I2C device operation

Figure 11. Read mode sequences

1. The seven most significant bits of the device select code of a random read (in the first and fourth bytes)

must be identical.

6WDUW

'HYVHO %\WHDGGU %\WHDGGU

6WDUW

'HYVHO 'DWDRXW

$,G

'DWDRXW1

6WRS

6WDUW

&XUUHQW

$GGUHVV

5HDG

'HYVHO 'DWDRXW

5DQGRP

$GGUHVV

5HDG

6WRS

6WDUW

'HYVHO 'DWDRXW

6HTXHQWLDO

&XUUHQW

5HDG

6WRS

'DWDRXW1

6WDUW

'HYVHO %\WHDGGU %\WHDGGU

6HTXHQWLRQ

5DQGRP

5HDG

6WDUW

'HYVHO 'DWDRXW

6WRS

$&.

5:

12$&.

$&.

5:

$&. $&. $&.

5:

$&. $&. $&. 12$&.

5:

12$&.

$&. $&. $&.

5:

$&. $&.

5:

$&. 12$&.

I2C device operation M24LR64E-R

38/144 DocID022712 Rev 12

5.11 Read operations

Read operations are performed independently of the state of the I2C_Write_Lock bit.

After the successful completion of a read operation, the device’s internal address counter is

incremented by one, to point to the next byte address.

5.12 Random Address Read

A dummy write is first performed to load the address into this address counter (as shown in

Figure 11) but without sending a Stop condition. Then, the bus master sends another Start

condition, and repeats the device select code, with the Read/Write bit (RW) set to 1. The

device acknowledges this, and outputs the contents of the addressed byte. The bus master

must not acknowledge the byte, and terminates the transfer with a Stop condition.

5.13 Current Address Read

For the Current Address Read operation, following a Start condition, the bus master only

sends a device select code with the Read/Write bit (RW) set to 1. The device acknowledges

this, and outputs the byte addressed by the internal address counter. The counter is then

incremented. The bus master terminates the transfer with a Stop condition, as shown in

Figure 11, without acknowledging the byte.

5.14 Sequential Read

This operation can be used after a Current Address Read or a Random Address Read. The

bus master does acknowledge the data byte output, and sends additional clock pulses so

that the device continues to output the next byte in sequence. To terminate the stream of

bytes, the bus master must not acknowledge the last byte, and must generate a Stop

condition, as shown in Figure 11.

The output data comes from consecutive addresses, with the internal address counter

automatically incremented after each byte output. After the last memory address, the

address counter “rolls over”, and the device continues to output data from memory

address 00h.

5.15 Acknowledge in Read mode

For all Read commands, the device waits, after each byte read, for an acknowledgment

during the ninth bit time. If the bus master does not drive Serial Data (SDA) low during this

time, the device terminates the data transfer and switches to its Standby mode.

DocID022712 Rev 12 39/144

M24LR64E-R I2C device operation

5.16 M24LR64E-R I2C password security

The M24LR64E-R controls I2C sector write access using the 32-bit-long I2C password and

the 64-bit I2C_Write_Lock bit area. The I2C password value is managed using two I2C

commands: I2C present password and I2C write password.

5.16.1 I2C present password command description

The I2C present password command is used in I2C mode to present the password to the

M24LR64E-R in order to modify the write access rights of all the memory sectors protected

by the I2C_Write_Lock bits, including the password itself. If the presented password is

correct, the access rights remain activated until the M24LR64E-R is powered off or until a

new I2C present password command is issued.

Following a Start condition, the bus master sends a device select code with the Read/Write

bit (RW) reset to 0 and the Chip Enable bit E2 at 1. The device acknowledges this, as shown

in Figure 12, and waits for two I2C password address bytes, 09h and 00h. The device

responds to each address byte with an acknowledge bit, and then waits for the four

password data bytes, the validation code, 09h, and a resend of the four password data

bytes. The most significant byte of the password is sent first, followed by the least significant

bytes.

It is necessary to send the 32-bit password twice to prevent any data corruption during the

sequence. If the two 32-bit passwords sent are not exactly the same, the M24LR64E-R

does not start the internal comparison.

When the bus master generates a Stop condition immediately after the Ack bit (during the

tenth bit time slot), an internal delay equivalent to the write cycle time is triggered. A Stop

condition at any other time does not trigger the internal delay. During that delay, the

M24LR64E-R compares the 32 received data bits with the 32 bits of the stored I2C

password. If the values match, the write access rights to all protected sectors are modified

after the internal delay. If the values do not match, the protected sectors remain protected.

During the internal delay, the serial data (SDA) signal is disabled internally, and the device

does not respond to any requests.

Figure 12. I2C present password command

AIC

3TART

$EVICESELECT

CODE 0ASSWORD

ADDRESSH 0ASSWORD

ADDRESSH 0ASSWORD

;=

!CK

27

!CK !CK !CK

$EVICESELECTCODE

0ASSWORD

;= 0ASSWORD

;= 0ASSWORD

;=

!CK !CK !CK

!CKGENERATEDDURING

THBITTIMESLOT

3TOP

6ALIDATION

CODEH

!CK

0ASSWORD

;=

!CK

0ASSWORD

;= 0ASSWORD

;= 0ASSWORD

;=

!CK !CK !CK

I2C device operation M24LR64E-R

40/144 DocID022712 Rev 12

5.16.2 I2C write password command description

The I2C write password command is used to write a 32-bit block into the M24LR64E-R I2C

password system area. This command is used in I2C mode to update the I2C password

value. It cannot be used to update any of the RF passwords. After the write cycle, the new

I2C password value is automatically activated. The I2C password value can only be modified

after issuing a valid I2C present password command.

On delivery, the I2C default password value is set to 0000 0000h and is activated.

Following a Start condition, the bus master sends a device select code with the Read/Write

bit (RW) reset to 0 and the Chip Enable bit E2 at 1. The device acknowledges this, as shown

in Figure 13, and waits for the two I2C password address bytes, 09h and 00h. The device

responds to each address byte with an acknowledge bit, and then waits for the four

password data bytes, the validation code, 07h, and a resend of the four password data

bytes. The most significant byte of the password is sent first, followed by the least significant

bytes.

It is necessary to send twice the 32-bit password to prevent any data corruption during the

write sequence. If the two 32-bit passwords sent are not exactly the same, the M24LR64E-

R does not modify the I2C password value.

When the bus master generates a Stop condition immediately after the Ack bit (during the

tenth bit time slot), the internal write cycle is triggered. A Stop condition at any other time

does not trigger the internal write cycle.

During the internal write cycle, the serial data (SDA) signal is disabled internally, and the

device does not respond to any requests.

Figure 13. I2C write password command

AIB

3TART

$EVICESELECT

CODE 0ASSWORD

ADDRESSH 0ASSWORD

ADDRESSH .EWPASSWORD

;=

!CK

27

!CK !CK !CK

$EVICESELECTCODE

.EWPASSWORD

;= .EWPASSWORD

;= .EWPASSWORD

;=

!CK !CK !CK

!CKGENERATEDDURING

THBITTIMESLOT

3TOP

6ALIDATION

CODEH

!CK

.EWPASSWORD

;=

!CK

.EWPASSWORD

;= .EWPASSWORD

;= .EWPASSWORD

;=

!CK !CK !CK

DocID022712 Rev 12 41/144

M24LR64E-R M24LR64E-R memory initial state

6 M24LR64E-R memory initial state

The device is delivered with all bits in the user memory array set to 1 (each byte contains

FFh).

The DSFID is programmed to FFh and the AFI is programmed to 00h.

Configuration byte set to F4h:

•Bit 7 to bit 4: all set to 1

•Bit 3: set to 0 (RF BUSY mode on RF WIP/BUSY pin)

•Bit 2: set to 1 (Energy harvesting not activated by default)

•Bit 1 and bit 0: set to 0

RF device operation M24LR64E-R

42/144 DocID022712 Rev 12

7 RF device operation

The M24LR64E-R is divided into 64 sectors of 32 blocks of 32 bits, as shown in Table 5.

Each sector can be individually read- and/or write-protected using a specific lock or

password command.

Read and Write operations are possible if the addressed block is not protected. During a

Write, the 32 bits of the block are replaced by the new 32-bit value.

The M24LR64E-R also has a 64-bit block that is used to store the 64-bit unique identifier

(UID). The UID is compliant with the ISO 15963 description, and its value is used during the

anticollision sequence (Inventory). This block is not accessible by the user in RF device

operation and its value is written by ST on the production line.

The M24LR64E-R also includes an AFI register in which the application family identifier is

stored, and a DSFID register in which the data storage family identifier used in the

anticollision algorithm is stored.

The M24LR64E-R has three 32-bit blocks in which the password codes are stored and an 8-

bit Configuration byte in which the Energy harvesting mode and RF WIP/BUSY pin

configuration is stored.

7.1 RF communication and energy harvesting

As the current consumption can affect the AC signal delivered by the antenna, RF

communications with M24LR64E-R are not guaranteed during voltage delivery on the

energy harvesting analog output Vout.

RF communication can disturb and possibly stop Energy Harvesting mode.

DocID022712 Rev 12 43/144

M24LR64E-R RF device operation

7.2 Commands

The M24LR64E-R supports the following commands:

•Inventory, used to perform the anticollision sequence.

•Stay quiet, used to put the M24LR64E-R in quiet mode, where it does not respond to

any inventory command.

•Select, used to select the M24LR64E-R. After this command, the M24LR64E-R

processes all Read/Write commands with Select_flag set.

•Reset to ready, used to put the M24LR64E-R in the ready state.

•Read block, used to output the 32 bits of the selected block and its locking status.

•Write block, used to write the 32-bit value in the selected block, provided that it is not

locked.

•Read multiple blocks, used to read the selected blocks and send back their value.

•Write AFI, used to write the 8-bit value in the AFI register.

•Lock AFI, used to lock the AFI register.

•Write DSFID, used to write the 8-bit value in the DSFID register.

•Lock DSFID, used to lock the DSFID register.

•Get system info, used to provide the system information value.

•Get multiple block security status, used to send the security status of the selected

block.

•Initiate, used to trigger the tag response to the Inventory initiated sequence.

•Inventory initiated, used to perform the anticollision sequence triggered by the Initiate

command.

•Write-sector password, used to write the 32 bits of the selected password.

•Lock-sector, used to write the sector security status bits of the selected sector.

•Present-sector password, enables the user to present a password to unprotect the

user blocks linked to this password.

•Fast initiate, used to trigger the tag response to the Inventory initiated sequence.

•Fast inventory initiated, used to perform the anticollision sequence triggered by the

Initiate command.

•Fast read single block, used to output the 32 bits of the selected block and its locking

status.

•Fast read multiple blocks, used to read the selected blocks and send back their

value.

•ReadCfg, used to read the 8-bit Configuration byte and send back its value.

•WriteEHCfg, used to write the energy harvesting configuration bits into the

Configuration byte.

•WriteDOCfg, used to write the RF WIP/BUSY pin configuration bit into the

Configuration byte.

•SetRstEHEn, used to set or reset the EH_enable bit into the volatile Control register.

•CheckEHEn, used to send back the value of the volatile Control register.

RF device operation M24LR64E-R

44/144 DocID022712 Rev 12

7.3 Initial dialog for vicinity cards

The dialog between the vicinity coupling device or VCD (commonly the “RF reader”) and the

vicinity integrated circuit card or VICC (M24LR64E-R) takes place as follows:

•activation of the M24LR64E-R by the RF operating field of the VCD

•transmission of a command by the VCD

•transmission of a response by the M24LR64E-R.

These operations use the RF power transfer and communication signal interface described

below (see Power transfer, Frequency and Operating field). This technique is called RTF

(Reader talks first).

7.3.1 Power transfer

Power is transferred to the M24LR64E-R by radio frequency at 13.56 MHz via coupling

antennas in the M24LR64E-R and the VCD. The RF operating field of the VCD is

transformed on the M24LR64E-R antenna to an AC voltage which is rectified, filtered and

internally regulated.

During communications, the amplitude modulation (ASK) on this received signal is

demodulated by the ASK demodulator.

7.3.2 Frequency

The ISO 15693 standard defines the carrier frequency (fC) of the operating field as

13.56 MHz ±7 kHz.

7.3.3 Operating field

The M24LR64E-R operates continuously between the minimum and maximum values of the

electromagnetic field H defined in Table 125. The VCD has to generate a field within these

limits.

DocID022712 Rev 12 45/144

M24LR64E-R Communication signal from VCD to M24LR64E-R

8 Communication signal from VCD to M24LR64E-R

Communications between the VCD and the M24LR64E-R take place using the modulation

principle of ASK (Amplitude shift keying). Two modulation indexes are used, 10% and

100%. The M24LR64E-R decodes both. The VCD determines which index is used.

The modulation index is defined as [a – b]/[a + b], where a is the peak signal amplitude, and

b the minimum signal amplitude of the carrier frequency.

Depending on the choice made by the VCD, a “pause” is created as described in Figure 14

and Figure 15.

The M24LR64E-R is operational for the 100% modulation index or for any degree of

modulation index between 10% and 30% (see Table 125).

Figure 14. 100% modulation waveform

Table 19. 10% modulation parameters

Symbol Parameter definition Value

hr 0.1 x (a – b) max

hf 0.1 x (a – b) max

069

7KHFORFNUHFRYHU\VKDOOEHRSHUDWLRQDODIWHUWPD[

V

WV

WV W

V

WV

V V

0LQ 0D[

W









&DUULHU

DPSOLWXGH

ƚϮ

W

W

W

Communication signal from VCD to M24LR64E-R M24LR64E-R

46/144 DocID022712 Rev 12

Figure 15. 10% modulation waveform

069

7KH9,&&VKDOOEHRSHUDWLRQDOIRUDQ\YDOXHRIPRGXODWLRQLQGH[EHWZHHQDQG

W

&DUULHUDPSOLWXGH

WW

VWV

WV W

WV

0RGXODWLRQLQGH[  

0LQ 0D[

DE\

KIKU DEPD[

DocID022712 Rev 12 47/144

M24LR64E-R Data rate and data coding

9 Data rate and data coding

The data coding implemented in the M24LR64E-R uses pulse position modulation. Both

data coding modes that are described in the ISO15693 are supported by the M24LR64E-R.

The selection is made by the VCD and indicated to the M24LR64E-R within the start of

frame (SOF).

9.1 Data coding mode: 1 out of 256

The value of a single byte is represented by the position of one pause. The position of the

pause on one of 256 successive time periods of 18.88 µs (256/fC) determines the value of

the byte. In this case, the transmission of one byte takes 4.833 ms and the resulting data

rate is 1.65 Kbits/s (fC/8192).

Figure 16 illustrates this pulse position modulation technique. In this figure, data E1h (225

decimal) is sent by the VCD to the M24LR64E-R.

The pause occurs during the second half of the position of the time period that determines

the value, as shown in Figure 17.

A pause during the first period transmits the data value 00h. A pause during the last period

transmits the data value FFh (255 decimal).

Figure 16. 1 out of 256 coding mode

!)







MS

S

S

0ULSE

-ODULATED

#ARRIER

Data rate and data coding M24LR64E-R

48/144 DocID022712 Rev 12

Figure 17. Detail of a time period

9.2 Data coding mode: 1 out of 4

The value of two bits is represented by the position of one pause. The position of the pause

on one of four successive time periods of 18.88 µs (256/fC) determines the value of the two

bits. Four successive pairs of bits form a byte, where the least significant pair of bits is

transmitted first.

In this case, the transmission of one byte takes 302.08 µs and the resulting data rate is

26.48 Kbits/s (fC/512). Figure 18 illustrates the 1 out of 4 pulse position technique and

coding. Figure 19 shows the transmission of E1h (225d - 1110 0001b) by the VCD.

!)





S

S

0ULSE

-ODULATED

#ARRIER











4IME0ERIOD

ONEOF

DocID022712 Rev 12 49/144

M24LR64E-R Data rate and data coding

Figure 18. 1 out of 4 coding mode

Figure 19. 1 out of 4 coding example

9.3 VCD to M24LR64E-R frames

Frames are delimited by a start of frame (SOF) and an end of frame (EOF). They are

implemented using code violation. Unused options are reserved for future use.

The M24LR64E-R is ready to receive a new command frame from the VCD 311.5 µs after

sending a response frame to the VCD.

!)

S S

S

S S

S

S S

S

S S

S

0ULSEPOSITIONFOR

0ULSEPOSITIONFOR

0ULSEPOSITIONFOR,3"

0ULSEPOSITIONFOR,3"



  



  

Data rate and data coding M24LR64E-R

50/144 DocID022712 Rev 12

The M24LR64E-R takes a power-up time of 0.1 ms after being activated by the powering

field. After this delay, the M24LR64E-R is ready to receive a command frame from the VCD.

9.4 Start of frame (SOF)

The SOF defines the data coding mode the VCD is to use for the following command frame.

The SOF sequence described in Figure 20 selects the 1 out of 256 data coding mode. The

SOF sequence described in Figure 21 selects the 1 out of 4 data coding mode. The EOF

sequence for either coding mode is described in Figure 22.

Figure 20. SOF to select 1 out of 256 data coding mode

Figure 21. SOF to select 1 out of 4 data coding mode

Figure 22. EOF for either data coding mode





 







 













DocID022712 Rev 12 51/144

M24LR64E-R Communication signal from M24LR64E-R to VCD

10 Communication signal from M24LR64E-R to VCD

The M24LR64E-R has several modes defined for some parameters, so that it can operate in

various noise environments and meet various application requirements.

10.1 Load modulation

The M24LR64E-R is capable of communicating to the VCD via an inductive coupling area

whereby the carrier is loaded to generate a subcarrier with frequency fS. The subcarrier is

generated by switching a load in the M24LR64E-R.

The load-modulated amplitude received on the VCD antenna must be of at least 10 mV

when measured, as described in the test methods defined in International Standard

ISO10373-7.

10.2 Subcarrier

The M24LR64E-R supports the one-subcarrier and two-subcarriers response formats.

These formats are selected by the VCD using the first bit in the protocol header. When one

subcarrier is used, the frequency fS1 of the subcarrier load modulation is 423.75 kHz (fC/32).

When two subcarriers are used, the frequency fS1 is 423.75 kHz (fC/32), and frequency fS2

is 484.28 kHz (fC/28). When using the two-subcarriers mode, the M24LR64E-R generates a

continuous phase relationship between fS1 and fS2.

10.3 Data rates

The M24LR64E-R can respond using the low or the high data rate format. The selection of

the data rate is made by the VCD using the second bit in the protocol header. For fast

commands, the selected data rate is multiplied by two. Table 20 shows the different data

rates produced by the M24LR64E-R using the different response format combinations.

Table 20. Response data rates

Data rate One subcarrier Two subcarriers

Low

Standard commands 6.62 Kbit/s (fc/2048) 6.67 Kbit/s (fc/2032)

Fast commands 13.24 Kbit/s (fc/1024) Not applicable

High

Standard commands 26.48 Kbit/s (fc/512) 26.69 Kbit/s (fc/508)

Fast commands 52.97 Kbit/s (fc/256) Not applicable

Bit representation and coding M24LR64E-R

52/144 DocID022712 Rev 12

11 Bit representation and coding

Data bits are encoded using Manchester coding, according to the following schemes. For

the low data rate, same subcarrier frequency or frequencies is/are used. In this case, the

number of pulses is multiplied by 4 and all times increase by this factor. For the Fast

commands using one subcarrier, all pulse numbers and times are divided by 2.

11.1 Bit coding using one subcarrier

11.1.1 High data rate

A logic 0 starts with eight pulses at 423.75 kHz (fC/32) followed by an unmodulated time of

18.88 µs, as shown in Figure 23.

Figure 23. Logic 0, high data rate

For the fast commands, a logic 0 starts with four pulses at 423.75 kHz (fC/32) followed by an

unmodulated time of 9.44 µs, as shown in Figure 24.

Figure 24. Logic 0, high data rate, fast commands

A logic 1 starts with an unmodulated time of 18.88 µs followed by eight pulses at 423.75 kHz

(fC/32), as shown in Figure 25.

Figure 25. Logic 1, high data rate

For the Fast commands, a logic 1 starts with an unmodulated time of 9.44 µs followed by

four pulses of 423.75 kHz (fC/32), as shown in Figure 26.

Figure 26. Logic 1, high data rate, fast commands

S

AI

S

AI

S

AI

S

AI

DocID022712 Rev 12 53/144

M24LR64E-R Bit representation and coding

11.1.2 Low data rate

A logic 0 starts with 32 pulses at 423.75 kHz (fC/32) followed by an unmodulated time of

75.52 µs, as shown in Figure 27.

Figure 27. Logic 0, low data rate

For the Fast commands, a logic 0 starts with 16 pulses at 423.75 kHz (fC/32) followed by an

unmodulated time of 37.76 µs, as shown in Figure 28.

Figure 28. Logic 0, low data rate, fast commands

A logic 1 starts with an unmodulated time of 75.52 µs followed by 32 pulses at 423.75 kHz

(fC/32), as shown in Figure 29.

Figure 29. Logic 1, low data rate

For the Fast commands, a logic 1 starts with an unmodulated time of 37.76 µs followed by

16 pulses at 423.75 kHz (fC/32), as shown in Figure 30.

Figure 30. Logic 1, low data rate, fast commands

S

AI

S

AI

S

AI

S

AI

Bit representation and coding M24LR64E-R

54/144 DocID022712 Rev 12

11.2 Bit coding using two subcarriers

11.2.1 High data rate

A logic 0 starts with eight pulses at 423.75 kHz (fC/32) followed by nine pulses at

484.28 kHz (fC/28), as shown in Figure 31. Bit coding using two subcarriers is not supported

for the Fast commands.

Figure 31. Logic 0, high data rate

A logic 1 starts with nine pulses at 484.28 kHz (fC/28) followed by eight pulses at

423.75 kHz (fC/32), as shown in Figure 32. Bit coding using two subcarriers is not supported

for the Fast commands.

Figure 32. Logic 1, high data rate

11.2.2 Low data rate

A logic 0 starts with 32 pulses at 423.75 kHz (fC/32) followed by 36 pulses at 484.28 kHz

(fC/28), as shown in Figure 33. Bit coding using two subcarriers is not supported for the Fast

commands.

Figure 33. Logic 0, low data rate

A logic 1 starts with 36 pulses at 484.28 kHz (fC/28) followed by 32 pulses at 423.75 kHz

(fC/32) as shown in Figure 34. Bit coding using two subcarriers is not supported for the Fast

commands.

Figure 34. Logic 1, low data rate

ϯϳϰϲђƐ

ĂŝϭϮϬϳϰ

ϯϳϰϲђƐ ĂŝϭϮϬϳϯ









DocID022712 Rev 12 55/144

M24LR64E-R M24LR64E-R to VCD frames

12 M24LR64E-R to VCD frames

Frames are delimited by an SOF and an EOF. They are implemented using code violation.

Unused options are reserved for future use. For the low data rate, the same subcarrier

frequency or frequencies is/are used. In this case, the number of pulses is multiplied by 4.

For the Fast commands using one subcarrier, all pulse numbers and times are divided by 2.

12.1 SOF when using one subcarrier

12.1.1 High data rate

The SOF includes an unmodulated time of 56.64 µs, followed by 24 pulses at 423.75 kHz

(fC/32), and a logic 1 that consists of an unmodulated time of 18.88 µs followed by eight

pulses at 423.75 kHz, as shown in Figure 35.

Figure 35. Start of frame, high data rate, one subcarrier

For the Fast commands, the SOF comprises an unmodulated time of 28.32 µs, followed by

12 pulses at 423.75 kHz (fC/32), and a logic 1 that consists of an unmodulated time of

9.44 µs followed by four pulses at 423.75 kHz, as shown in Figure 36.

Figure 36. Start of frame, high data rate, one subcarrier, fast commands

12.1.2 Low data rate

The SOF comprises an unmodulated time of 226.56 µs, followed by 96 pulses at 423.75

kHz (fC/32), and a logic 1 that consists of an unmodulated time of 75.52 µs followed by 32

pulses at 423.75 kHz, as shown in Figure 37.

Figure 37. Start of frame, low data rate, one subcarrier







ϱϲϲϰђƐ

ĂŝϭϮϬϳϵ

ϭϴϴϴђƐ

ϰϱϯϭϮђƐ

ĂŝϭϮϬϴϬď

ϭϱϭϬϰђƐ

M24LR64E-R to VCD frames M24LR64E-R

56/144 DocID022712 Rev 12

For the Fast commands, the SOF comprises an unmodulated time of 113.28 µs, followed by

48 pulses at 423.75 kHz (fC/32), and a logic 1 that includes an unmodulated time of

37.76 µs followed by 16 pulses at 423.75 kHz, as shown in Figure 38.

Figure 38. Start of frame, low data rate, one subcarrier, fast commands

12.2 SOF when using two subcarriers

12.2.1 High data rate

The SOF comprises 27 pulses at 484.28 kHz (fC/28), followed by 24 pulses at 423.75 kHz

(fC/32), and a logic 1 that includes nine pulses at 484.28 kHz followed by eight pulses at

423.75 kHz, as shown in Figure 39.

Bit coding using two subcarriers is not supported for the Fast commands.

Figure 39. Start of frame, high data rate, two subcarriers

12.2.2 Low data rate

The SOF comprises 108 pulses at 484.28 kHz (fC/28), followed by 96 pulses at 423.75 kHz

(fC/32), and a logic 1 that includes 36 pulses at 484.28 kHz followed by 32 pulses at

423.75 kHz, as shown in Figure 40.

Bit coding using two subcarriers is not supported for the Fast commands.

Figure 40. Start of frame, low data rate, two subcarriers







ϭϭϮϯϵђƐ

ĂŝϭϮϬϴϮ

ϯϳϰϲђƐ

ϰϰϵϱϲђƐ

ĂŝϭϮϬϴϯ

ϭϰϵϴϰђƐ

DocID022712 Rev 12 57/144

M24LR64E-R M24LR64E-R to VCD frames

12.3 EOF when using one subcarrier

12.3.1 High data rate

The EOF comprises a logic 0 that includes eight pulses at 423.75 kHz and an unmodulated

time of 18.88 µs, followed by 24 pulses at 423.75 kHz (fC/32), and by an unmodulated time

of 56.64 µs, as shown in Figure 41.

Figure 41. End of frame, high data rate, one subcarrier

For the Fast commands, the EOF comprises a logic 0 that includes four pulses at

423.75 kHz and an unmodulated time of 9.44 µs, followed by 12 pulses at 423.75 kHz

(fC/32) and an unmodulated time of 37.76 µs, as shown in Figure 42.

Figure 42. End of frame, high data rate, one subcarrier, fast commands

12.3.2 Low data rate

The EOF comprises a logic 0 that includes 32 pulses at 423.75 kHz and an unmodulated

time of 75.52 µs, followed by 96 pulses at 423.75 kHz (fC/32) and an unmodulated time of

226.56 µs, as shown in Figure 43.

Figure 43. End of frame, low data rate, one subcarrier

For the Fast commands, the EOF comprises a logic 0 that includes 16 pulses at 423.75 kHz

and an unmodulated time of 37.76 µs, followed by 48 pulses at 423.75 kHz (fC/32) and an

unmodulated time of 113.28 µs, as shown in Figure 44.

Figure 44. End of frame, low data rate, one subcarrier, Fast commands

























M24LR64E-R to VCD frames M24LR64E-R

58/144 DocID022712 Rev 12

12.4 EOF when using two subcarriers

12.4.1 High data rate

The EOF comprises a logic 0 that includes eight pulses at 423.75 kHz and nine pulses at

484.28 kHz, followed by 24 pulses at 423.75 kHz (fC/32) and 27 pulses at 484.28 kHz

(fC/28), as shown in Figure 45.

Bit coding using two subcarriers is not supported for the Fast commands.

Figure 45. End of frame, high data rate, two subcarriers

12.4.2 Low data rate

The EOF comprises a logic 0 that includes 32 pulses at 423.75 kHz and 36 pulses at

484.28 kHz, followed by 96 pulses at 423.75 kHz (fC/32) and 108 pulses at 484.28 kHz

(fC/28), as shown in Figure 46.

Bit coding using two subcarriers is not supported for the Fast commands.

Figure 46. End of frame, low data rate, two subcarriers

V

069

V

ϰϰϵϱϲђƐ

ĂŝϭϮϬϴϵ

ϭϰϵϴϰђƐ

DocID022712 Rev 12 59/144

M24LR64E-R Unique identifier (UID)

13 Unique identifier (UID)

The M24LR64E-R is uniquely identified by a 64-bit unique identifier (UID). This UID

complies with ISO/IEC 15963 and ISO/IEC 7816-6. The UID is a read-only code and

comprises:

•eight MSBs with a value of E0h,

•the IC manufacturer code “ST 02h” on 8 bits (ISO/IEC 7816-6/AM1),

•a unique serial number on 48 bits.

With the UID, each M24LR64E-R can be addressed uniquely and individually during the

anticollision loop and for one-to-one exchanges between a VCD and an M24LR64E-R.

Table 21. UID format

MSB LSB

63 56 55 48 47 0

0xE0 0x02 Unique serial number

Application family identifier (AFI) M24LR64E-R

60/144 DocID022712 Rev 12

14 Application family identifier (AFI)

The AFI (application family identifier) represents the type of application targeted by the VCD

and is used to identify, among all the M24LR64E-Rs present, only those that meet the

required application criteria.

Figure 47. M24LR64E-R decision tree for AFI

The AFI is programmed by the M24LR64E-R issuer (or purchaser) in the AFI register. Once

programmed and locked, it can no longer be modified.

The most significant nibble of the AFI is used to code one specific or all application families.

The least significant nibble of the AFI is used to code one specific or all application

subfamilies. Subfamily codes different from 0 are proprietary.

See also ISO 15693-3 documentation.

!)

)NVENTORYREQUEST

RECEIVED

.OANSWER

9E S

!&)VALUE



9E S

.O !&)FLAG

SET

9E S

!NSWERGIVENBYTHE-2&

TOTHE)NVENTORYREQUEST

!&)VALUE

)NTERNAL

VALUE

DocID022712 Rev 12 61/144

M24LR64E-R Data storage format identifier (DSFID)

15 Data storage format identifier (DSFID)

The data storage format identifier indicates how the data is structured in the M24LR64E-R

memory. The logical organization of data can be known instantly using the DSFID. It can be

programmed and locked using the Write DSFID and Lock DSFID commands.

15.1 CRC

The CRC used in the M24LR64E-R is calculated as per the definition in ISO/IEC 13239. The

initial register contents are all 1s: “FFFF”.

The two-byte CRC is appended to each request and response, within each frame, before

the EOF. The CRC is calculated on all the bytes after the SOF up to the CRC field.

Upon reception of a request from the VCD, the M24LR64E-R verifies that the CRC value is

valid. If it is invalid, the M24LR64E-R discards the frame and does not answer the VCD.

Upon reception of a response from the M24LR64E-R, it is recommended that the VCD

verifies whether the CRC value is valid. If it is invalid, actions to be performed are left to the

VCD designer judgment.

The CRC is transmitted least significant byte first. Each byte is transmitted least significant

bit first.

Table 22. CRC transmission rules

LSByte LSByte

LSBitMSBitLSBitMSBit

CRC 16 (8 bits) CRC 16 (8 bits)

M24LR64E-R protocol description M24LR64E-R

62/144 DocID022712 Rev 12

16 M24LR64E-R protocol description

The transmission protocol (or simply “the protocol”) defines the mechanism used to

exchange instructions and data between the VCD and the M24LR64E-R in both directions.

It is based on the concept of “VCD talks first”.

This means that an M24LR64E-R does not start transmitting unless it has received and

properly decoded an instruction sent by the VCD. The protocol is based on an exchange of:

•a request from the VCD to the M24LR64E-R,

•a response from the M24LR64E-R to the VCD.

Each request and each response are contained in a frame. The frame delimiters (SOF,

EOF) are described in Section 12.

Each request consists of:

•a request SOF (see Figure 20 and Figure 21),

•flags,

•a command code,

•parameters depending on the command,

•application data,

•a 2-byte CRC,

•a request EOF (see Figure 22).

Each response consists of:

•an answer SOF (see Figure 35 to Figure 40),

•flags,

•parameters depending on the command,

•application data,

•a 2-byte CRC,

•an answer EOF (see Figure 41 to Figure 46).

The protocol is bit-oriented. The number of bits transmitted in a frame is a multiple of eight

(8), that is an integer number of bytes.

A single-byte field is transmitted least significant bit (LSBit) first. A multiple-byte field is

transmitted least significant byte (LSByte) first and each byte is transmitted least significant

bit (LSBit) first.

The setting of the flags indicates the presence of the optional fields. When the flag is set (to

one), the field is present. When the flag is reset (to zero), the field is absent.

Table 23. VCD request frame format

Request

SOF Request_flags Command code Parameters Data 2-byte CRC Request

EOF

Table 24. M24LR64E-R Response frame format

Response

SOF Response_flags Parameters Data 2-byte CRC Response

EOF

DocID022712 Rev 12 63/144

M24LR64E-R M24LR64E-R protocol description

Figure 48. M24LR64E-R protocol timing

VCD

Request

frame

(Table 23)

Request

frame

(Table 23)

M24LR64E-R

Response

frame

(Table 24)

Response

frame

(Table 24)

Timing <-t1-> <-t2-> <-t1-> <-t2->

M24LR64E-R states M24LR64E-R

64/144 DocID022712 Rev 12

17 M24LR64E-R states

An M24LR64E-R can be in one of four states:

•Power-off

•Ready

•Quiet

•Selected

Transitions between these states are specified in Figure 49 and Table 25.

17.1 Power-off state

The M24LR64E-R is in the Power-off state when it does not receive enough energy from the

VCD.

17.2 Ready state

The M24LR64E-R is in the Ready state when it receives enough energy from the VCD.

When in the Ready state, the M24LR64E-R answers any request where the Select_flag is

not set.

17.3 Quiet state

When in the Quiet state, the M24LR64E-R answers any request except for Inventory

requests with the Address_flag set.

17.4 Selected state

In the Selected state, the M24LR64E-R answers any request in all modes (see Section 18):

•Request in Select mode with the Select_flag set

•Request in Addressed mode if the UID matches

•Request in Non-Addressed mode as it is the mode for general requests

DocID022712 Rev 12 65/144

M24LR64E-R M24LR64E-R states

Figure 49. M24LR64E-R state transition diagram

1. The M24LR64E-R returns to the Power Off state if the tag is out of the RF field for at least tRF_OFF. Refer to

application note AN4125 for more information.

2. The intention of the state transition method is that only one M24LR64E-R should be in the Selected state at

a time.

Table 25. M24LR64E-R response depending on Request_flags

Flags

Address_flag Select_flag

Addressed

Non addressed

Selected

Non selected

M24LR64E-R in Ready or

Selected state (Devices in Quiet

state do not answer)

-X-X

M24LR64E-R in Selected state - X X -

M24LR64E-R in Ready, Quiet or

Selected state (the device which

matches the UID)

X- -X

Error (03h) X - X -

$,E

3RZHURII

,QILHOG

2XW



ILHOG

5HDG\

4XLHW 6HOHFWHG

$Q\RWKHU&RPPDQG

ZKHUH6HOHFWB)ODJ

LVQRWVHW

 





6WD\TXLHW8,'

6HOHFW8,'

$Q\RWKHUFRPPDQG

$Q\RWKHUFRPPDQGZKHUHWKH

$GGUHVVB)ODJLVVHW$1'

ZKHUH,QYHQWRU\B)ODJLVQRWVHW

6WD\TXLHW8,'

6HOHFW8,'

5HVHWWRUHDG\ZKHUH

6HOHFWB)ODJLVVHWRU

6HOHFWGLIIHUHQW8,'

5HVHWWRUHDG\

2XWRI5)ILHOG

DIWHUW5)B2))



2XW RI 5) ILHOG

DIWHUW5)B2))



DIWHUW5)B2))

Modes M24LR64E-R

66/144 DocID022712 Rev 12

18 Modes

The term “mode” refers to the mechanism used in a request to specify the set of

M24LR64E-Rs that answers the request.

18.1 Addressed mode

When the Address_flag is set to 1 (Addressed mode), the request contains the Unique ID

(UID) of the addressed M24LR64E-R.

Any M24LR64E-R that receives a request with the Address_flag set to 1 compares the

received Unique ID to its own. If it matches, then the M24LR64E-R executes the request (if

possible) and returns a response to the VCD as specified in the command description.

If the UID does not match, then it remains silent.

18.2 Non-addressed mode (general request)

When the Address_flag is cleared to 0 (Non-Addressed mode), the request does not contain

a Unique ID. Any M24LR64E-R receiving a request with the Address_flag cleared to 0

executes it and returns a response to the VCD as specified in the command description.

18.3 Select mode

When the Select_flag is set to 1 (Select mode), the request does not contain an M24LR64E-

R Unique ID. The M24LR64E-R in the Selected state that receives a request with the

Select_flag set to 1 executes it and returns a response to the VCD as specified in the

command description.

Only M24LR64E-Rs in the Selected state answer a request where the Select_flag is set to

The system design ensures in theory that only one M24LR64E-R can be in the Select state

at any given time.

DocID022712 Rev 12 67/144

M24LR64E-R Request format

19 Request format

The request consists of:

•an SOF,

•flags,

•a command code,

•parameters and data,

•a CRC,

•an EOF.

19.1 Request flags

In a request, the “flags” field specifies the actions to be performed by the M24LR64E-R and

whether corresponding fields are present or not.

The flags field consists of eight bits. Bit 3 (Inventory_flag) of the request flag defines the

contents of the four MSBs (bits 5 to 8). When bit 3 is reset (0), bits 5 to 8 define the

M24LR64E-R selection criteria. When bit 3 is set (1), bits 5 to 8 define the M24LR64E-R

Inventory parameters.

Table 26. General request format

Request_flags Command code Parameters Data CRC

Table 27. Definition of request flags 1 to 4

Bit No. Flag Level Description

Bit 1 Subcarrier_flag(1)

1. Subcarrier_flag refers to the M24LR64E-R-to-VCD communication.

0A single subcarrier frequency is used by the

M24LR64E-R

1 Two subcarriers are used by the M24LR64E-R

Bit 2 Data_rate_flag(2)

2. Data_rate_flag refers to the M24LR64E-R-to-VCD communication.

0 Low data rate is used

1 High data rate is used

Bit 3 Inventory_flag

0 The meaning of flags 5 to 8 is described in Table 28

1 The meaning of flags 5 to 8 is described in Table 29

Bit 4 Protocol_extension_flag(3)

3. Protocol_extension_flag must be set to 1 for Read Single Block, Read Multiple Block, Fast

Read Multiple Block, Write Single Block, and Get Multiple Block Security Status commands.

Get System Info command supports two options: a standard response format when

Protocol_extension_flag is set to 0, and a rich response when protocol extension is set to 1.

0 No Protocol format extension

1 Protocol format extension

Request format M24LR64E-R

68/144 DocID022712 Rev 12

Table 28. Request flags 5 to 8 when Bit 3 = 0

Bit No. Flag Level Description

Bit 5 Select flag(1)

1. If the Select_flag is set to 1, the Address_flag is set to 0 and the UID field is not present in the

request.

0The request is executed by any M24LR64E-R according to the

setting of Address_flag

1The request is executed only by the M24LR64E-R in Selected

state

Bit 6 Address flag(1)

0The request is not addressed. UID field is not present. The request

is executed by all M24LR64E-Rs.

The request is addressed. UID field is present. The request is

executed only by the M24LR64E-R whose UID matches the UID

specified in the request.

Bit 7 Option flag

0 Option not activated.

1 Option activated.

Bit 8 RFU 0 -

Table 29. Request flags 5 to 8 when Bit 3 = 1

Bit No. Flag Level Description

Bit 5 AFI flag

0 AFI field is not present

1 AFI field is present

Bit 6 Nb_slots flag

0 16 slots

11 slot

Bit 7 Option flag 0 -

Bit 8 RFU 0 -

DocID022712 Rev 12 69/144

M24LR64E-R Response format

20 Response format

The response consists of:

•an SOF,

•flags,

•parameters and data,

•a CRC,

•an EOF.

20.1 Response flags

In a response, the flags indicate how actions have been performed by the M24LR64E-R and

whether corresponding fields are present or not. The response flags consist of eight bits.

Table 30. General response format

Response_flags Parameters Data CRC

Table 31. Definitions of response flags 1 to 8

Bit No. Flag Level Description

Bit 1 Error_flag

0 No error

1 Error detected. Error code is in the “Error” field.

Bit 2 RFU 0 -

Bit 3 RFU 0 -

Bit 4 Extension flag 0 No extension

Bit 5 RFU 0 -

Bit 6 RFU 0 -

Bit 7 RFU 0 -

Bit 8 RFU 0 -

Response format M24LR64E-R

70/144 DocID022712 Rev 12

20.2 Response error code

If the Error_flag is set by the M24LR64E-R in the response, the Error code field is present

and provides information about the error that occurred.

Error codes not specified in Table 32 are reserved for future use.

Table 32. Response error code definition

Error code Meaning

03h The option is not supported.

0Fh Error with no information given.

10h The specified block is not available.

11h The specified block is already locked and thus cannot be locked again.

12h The specified block is locked and its contents cannot be changed.

13h The specified block was not successfully programmed.

14h The specified block was not successfully locked.

15h The specified block is read-protected.

DocID022712 Rev 12 71/144

M24LR64E-R Anticollision

21 Anticollision

The purpose of the anticollision sequence is to inventory the M24LR64E-Rs present in the

VCD field using their unique ID (UID).

The VCD is the master of communications with one or several M24LR64E-Rs. It initiates an

M24LR64E-R communication by issuing the Inventory request.

The M24LR64E-R sends its response in the determined slot or does not respond.

21.1 Request parameters

When issuing the Inventory Command:

•The VCD sets the Nb_slots_flag as desired.

•The VCD adds the mask length and the mask value after the command field:

– The mask length is the number of significant bits of the mask value.

– The mask value is contained in an integer number of bytes. The mask length

indicates the number of significant bits. LSB is transmitted first.

•If the mask length is not a multiple of 8 (bits), as many 0-bits as required are added to

the mask value MSB, so that the mask value is contained in an integer number of

bytes.

•The next field starts at the next byte boundary.

In the example provided in Table 3 4 and Figure 50, the mask length is 11 bits. Five 0-bits

are added to the mask value MSB. The 11-bit mask and the current slot number are

compared to the UID.

Table 33. Inventory request format

MSB LSB

SOF Request_flags Command Optional AFI Mask length Mask value CRC EOF

- 8 bits 8 bits 8 bits 8 bits 0 to 8 bytes 16 bits -

Table 34. Example of the addition of 0-bits to an 11-bit mask value

MSB (b15)LSB (b

0000 0 100 1100 1111

0-bits added 11-bit mask value

Anticollision M24LR64E-R

72/144 DocID022712 Rev 12

Figure 50. Principle of comparison between the mask, the slot number and the UID

The AFI field is present if the AFI_flag is set.

The pulse is generated according to the definition of the EOF in ISO/IEC 15693-2.

The first slot starts immediately after the request EOF is received. To switch to the next slot,

the VCD sends an EOF.

The following rules and restrictions apply:

•If no M24LR64E-R answer is detected, the VCD may switch to the next slot by sending

an EOF.

•If one or more M24LR64E-R answers are detected, the VCD waits until the complete

frame has been received before sending an EOF for switching to the next slot.

!)

-ASKVALUERECEIVEDINTHE)NVENTORYCOMMAND     BBITS

4HE-ASKVALUELESSTHEPADDINGSISLOADED

INTOTHE4AGCOMPARATOR    BBITS

4HE3LOTCOUNTERISCALCULATED

XXXX.B?SLOTS?FLAGSSLOTS3LOT#OUNTERISBITS

4HE3LOTCOUNTERISCONCATENEDTOTHE-ASKVALUE

XXXX    B

.B?SLOTS?FLAGS BITS

4HECONCATENATEDRESULTISCOMPAREDWITH

THELEASTSIGNIFICANTBITSOFTHE4A G5)$

XXXX XXXX  XXXX XXXX X XXX XXXX XXXX XXXX BITS

,3"-3"

BB

#OMPARE"ITSIGNORED

5)$

BITS

DocID022712 Rev 12 73/144

M24LR64E-R Request processing by the M24LR64E-R

22 Request processing by the M24LR64E-R

Upon reception of a valid request, the M24LR64E-R performs the following algorithm:

•NbS is the total number of slots (1 or 16)

•SN is the current slot number (0 to 15)

•LSB (value, n) function returns the n Less Significant Bits of value

•MSB (value, n) function returns the n Most Significant Bits of value

•“&” is the concatenation operator

•Slot_Frame is either an SOF or an EOF

SN = 0

if (Nb_slots_flag)

then NbS = 1

SN_length = 0

endif

else NbS = 16

SN_length = 4

endif

label1:

if LSB(UID, SN_length + Mask_length) =

LSB(SN,SN_length)&LSB(Mask,Mask_length)

then answer to inventory request

endif

wait (Slot_Frame)

if Slot_Frame = SOF

then Stop Anticollision

decode/process request

exit

endif

if Slot_Frame = EOF

if SN < NbS-1

then SN = SN + 1

goto label1

exit

endif

Explanation of the possible cases M24LR64E-R

74/144 DocID022712 Rev 12

23 Explanation of the possible cases

Figure 51 summarizes the main possible cases that can occur during an anticollision

sequence when the number of slots is 16.

The sequence of steps is as follows:

•The VCD sends an Inventory request, in a frame terminated by an EOF. The number of

slots is 16.

•M24LR64E-R_1 transmits its response in Slot 0. It is the only one to do so, therefore no

collision occurs and its UID is received and registered by the VCD.

•The VCD sends an EOF in order to switch to the next slot.

•In Slot 1, two M24LR64E-Rs (M24LR64E-R_2 and M24LR64E-R_3) transmit a

response, thus generating a collision. The VCD records the event and registers that a

collision was detected in Slot 1.

•The VCD sends an EOF in order to switch to the next slot.

•In Slot 2, no M24LR64E-R transmits a response. Therefore the VCD does not detect

any M24LR64E-R SOF and switches to the next slot by sending an EOF.

•In Slot 3, another collision occurs due to responses from M24LR64E-R_4 and

M24LR64E-R_5.

•The VCD sends a request (for instance a Read Block) to M24LR64E-R_1 whose UID

has already been correctly received.

•All M24LR64E-Rs detect an SOF and exit the anticollision sequence. They process this

request and since the request is addressed to M24LR64E-R_1, only M24LR64E-R_1

transmits a response.

•All M24LR64E-Rs are ready to receive another request. If it is an Inventory command,

the slot numbering sequence restarts from 0.

Note: The decision to interrupt the anticollision sequence is made by the VCD. EOFs could have

been sent until Slot 16, and the request to M24LR64E-R_1 sent then.

M24LR64E-R Explanation of the possible cases

DocID022712 Rev 12 75/143

Figure 51. Description of a possible anticollision sequence

069

9&'

0/5(5V

7LPLQJ

&RPPHQW

1R

FROOLVLRQ &ROOLVLRQ 1R

UHVSRQVH &ROOLVLRQ

7LPH

6ORW 6ORW 6ORW 6ORW















(

)

(

)

(

)

(

)

5HTXHVWWR

-,2%2?

)

5HVSRQVH



5HVSRQVH



5HVSRQVH



5HVSRQVH



5HVSRQVH



5HVSRQVHIURP

-,2%2?

(

)

,QYHQWRU\

5HTXHVW

)

Inventory Initiated command M24LR64E-R

76/144 DocID022712 Rev 12

24 Inventory Initiated command

The M24LR64E-R provides a special feature to improve the inventory time response of

moving tags using the Initiate_flag value. This flag, controlled by the Initiate command,

allows tags to answer Inventory Initiated commands.

For applications in which multiple tags are moving in front of a reader, it is possible to miss

tags using the standard inventory command. The reason is that the inventory sequence has

to be performed on a global tree search. For example, a tag with a particular UID value may

have to wait the run of a long tree search before being inventoried. If the delay is too long,

the tag may be out of the field before it has been detected.

Using the Initiate command, the inventory sequence is optimized. When multiple tags are

moving in front of a reader, the ones which are within the reader field are initiated by the

Initiate command. In this case, a small batch of tags answers to the Inventory Initiated

command, which optimizes the time necessary to identify all the tags. When finished, the

reader has to issue a new Initiate command in order to initiate a new small batch of tags

which are new inside the reader field.

It is also possible to reduce the inventory sequence time using the Fast Initiate and Fast

Inventory Initiated commands. These commands allow the M24LR64E-Rs to increase their

response data rate by a factor of 2, up to 53 Kbit/s.

DocID022712 Rev 12 77/144

M24LR64E-R Timing definition

25 Timing definition

25.1 t1: M24LR64E-R response delay

Upon detection of the rising edge of the EOF received from the VCD, the M24LR64E-R

waits for a t1nom time before transmitting its response to a VCD request or switching to the

next slot during an inventory process. Values of t1 are given in Table 35. The EOF is defined

in Figure 22.

25.2 t2: VCD new request delay

t2 is the time after which the VCD may send an EOF to switch to the next slot when one or

more M24LR64E-R responses have been received during an Inventory command. It starts

from the reception of the EOF from the M24LR64E-Rs.

The EOF sent by the VCD may be either 10% or 100% modulated regardless of the

modulation index used for transmitting the VCD request to the M24LR64E-R.

t2 is also the time after which the VCD may send a new request to the M24LR64E-R, as

described in Figure 48.

Values of t2 are given in Table 35.

25.3 t3: VCD new request delay when no response is received

from the M24LR64E-R

t3 is the time after which the VCD may send an EOF to switch to the next slot when no

M24LR64E-R response has been received.

The EOF sent by the VCD may be either 10% or 100% modulated regardless of the

modulation index used for transmitting the VCD request to the M24LR64E-R.

From the time the VCD has generated the rising edge of an EOF:

•If this EOF is 100% modulated, the VCD waits for a time at least equal to t3min before

sending a new EOF.

•If this EOF is 10% modulated, the VCD waits for a time at least equal to the sum of

t3min + the M24LR64E-R nominal response time (which depends on the M24LR64E-R

data rate and subcarrier modulation mode) before sending a new EOF.

Table 35. Timing values(1)

1. The tolerance of specific timings is ± 32/fC.

Minimum (min) values Nominal (nom) values Maximum (max) values

t1318.6 µs 320.9 µs 323.3 µs

t2309.2 µs No tnom No tmax

t3t1max(2) + tSOF(3)

2. t1max does not apply for write-alike requests. Timing conditions for write-alike requests are

defined in the command description.

3. tSOF is the time taken by the M24LR64E-R to transmit an SOF to the VCD. tSOF depends on

the current data rate: High data rate or Low data rate.

No tnom No tmax

Command codes M24LR64E-R

78/144 DocID022712 Rev 12

26 Command codes

The M24LR64E-R supports the commands described in this section. Their codes are given

in Table 36.

- Table 36. Command codes

Command code

standard Function Command code

custom Function

01h Inventory 2Ch Get Multiple Block Security Status

02h Stay Quiet B1h Write-sector Password

20h Read Single Block B2h Lock-sector

21h Write Single Block B3h Present-sector Password

23h Read Multiple Block C0h Fast Read Single Block

25h Select C1h Fast Inventory Initiated

26h Reset to Ready C2h Fast Initiate

27h Write AFI C3h Fast Read Multiple Block

28h Lock AFI D1h Inventory Initiated

29h Write DSFID D2h Initiate

2Ah Lock DSFID A0h ReadCfg

2Bh Get System Info A1h WriteEHCfg

- - A2h SetRstEHEn

- - A3h CheckEHEn

-- A4hWriteDOCfg

DocID022712 Rev 12 79/144

M24LR64E-R Command codes

26.1 Inventory

When receiving the Inventory request, the M24LR64E-R runs the anticollision sequence.

The Inventory_flag is set to 1. The meaning of flags 5 to 8 is shown in Table 29.

The request contains:

•the flags,

•the Inventory command code (see Table 36),

•the AFI if the AFI flag is set,

•the mask length,

•the mask value,

•the CRC.

The M24LR64E-R does not generate any answer in case of error.

The response contains:

•the flags,

•the Unique ID.

During an Inventory process, if the VCD does not receive an RF M24LR64E-R response, it

waits for a time t3 before sending an EOF to switch to the next slot. t3 starts from the rising

edge of the request EOF sent by the VCD.

•If the VCD sends a 100% modulated EOF, the minimum value of t3 is:

t3min = 4384/fC (323.3µs) + tSOF

•If the VCD sends a 10% modulated EOF, the minimum value of t3 is:

t3min = 4384/fC (323.3µs) + tNRT

where:

•tSOF is the time required by the M24LR64E-R to transmit an SOF to the VCD,

•tNRT is the nominal response time of the M24LR64E-R.

tNRT and tSOF are dependent on the M24LR64E-R-to-VCD data rate and subcarrier

modulation mode.

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF

starting the inventory command to the end of the M24LR64E-R response. If the

M24LR64E-R does not receive the corresponding slot marker, the RF WIP/BUSY pin

remains at 0 until the next RF power-off.

Table 37. Inventory request format

Request

SOF Request_flags Inventory Optional

AFI

Mask

length

Mask

value CRC16 Request

EOF

- 8 bits 01h 8 bits 8 bits 0 - 64 bits 16 bits -

Table 38. Inventory response format

Response

SOF Response_flags DSFID UID CRC16 Response

EOF

- 8 bits 8 bits 64 bits 16 bits -

Command codes M24LR64E-R

80/144 DocID022712 Rev 12

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

Figure 52. M24LR64E RF-Busy management following Inventory command

069

)

,QYHQWRU\

FRPPDQG

(

)

(

)

6ORW

)

,UHSO\

0/5[

(

)

(

)

(

)

6ORWQ

0/5[UHSOLHVLQVORWQ5)B%XV\LVUHOHDVHGDIWHU0/5[UHVSRQVH

5)B%XV\

)

,QYHQWRU\

FRPPDQG

(

)

(

)

6ORW

(

)

6ORWQ

6ORWQQHYHURFFXUV5)B%XV\LVRQO\UHOHDVHGE\3RZHURII

3RZHURII

5)B%XV\

)

,QYHQWRU\

FRPPDQG

(

)

(

)

6ORW

9&'VHQGVD9DOLGFRPPDQGEHIRUHVORWQ5)B%XV\LVUHOHDVHGDIWHU0/5[

UHVSRQVH

5)B%XV\

)

,QYHQWRU\

FRPPDQG

(

)

(

)

6ORW

9&'VHQGVD%DGFRPPDQGEHIRUHVORWQ5)B%XV\LVUHOHDVHGDIWHU9&'

FRPPDQG

5)B%XV\

)

,1HZ

FRPPDQG

(

)

,UHSO\

0/5[

(

)

,1HZ

FRPPDQG

(

)

DocID022712 Rev 12 81/144

M24LR64E-R Command codes

26.2 Stay Quiet

Command code = 0x02

On receiving the Stay Quiet command, the M24LR64E-R enters the Quiet state if no error

occurs, and does NOT send back a response. There is NO response to the Stay Quiet

command even if an error occurs.

When in the Quiet state:

•the M24LR64E-R does not process any request if the Inventory_flag is set,

•the M24LR64E-R processes any Addressed request.

The M24LR64E-R exits the Quiet state when:

•it is reset (power off),

•receiving a Select request. It then goes to the Selected state,

•receiving a Reset to Ready request. It then goes to the Ready state.

The Stay Quiet command must always be executed in Addressed mode (Select_flag is reset

to 0 and Address_flag is set to 1).

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 during the Stay

Quiet command.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

Table 39. Stay Quiet request format

Request

SOF Request flags Stay Quiet UID CRC16 Request

EOF

- 8 bits 02h 64 bits 16 bits -

Figure 53. Stay Quiet frame exchange between VCD and M24LR64E-R

VCD SOF Stay Quiet

request EOF

M24LR64E-R

Command codes M24LR64E-R

82/144 DocID022712 Rev 12

26.3 Read Single Block

On receiving the Read Single Block command, the M24LR64E-R reads the requested block

and sends back its 32-bit value in the response. The Protocol_extension_flag should be set

to 1 for the M24LR64E-R to operate correctly. If the Protocol_extension_flag is at 0, the

M24LR64E-R answers with an error code. The Option_flag is supported.

Request parameters:

•Request flags

•UID (optional)

•Block number

Response parameters:

•Sector security status if Option_flag is set (see Ta ble 42)

•Four bytes of block data

Response parameter:

•Error code as Error_flag is set

– 10h: the specified block is not available

– 15h: the specified block is read-protected

Table 40. Read Single Block request format

Request

SOF Request_flags Read Single

Block UID(1)

1. Gray color means that the field is optional.

Block number CRC16 Request

EOF

-8 bits 20h

64 bits 16 bits 16 bits -

Table 41. Read Single Block response format when Error_flag is NOT set

Response

SOF Response_flags Sector security

status(1)

1. Gray color means that the field is optional.

Data CRC16 Response

EOF

-8 bits8 bits 32 bits 16 bits -

Table 42. Sector security status

b7b6b5b4b3b2b1b0

Reserved for future use.

All at 0.

Password control

bits

Read / Write

protection bits

0: Current sector not locked

1: Current sector locked

Table 43. Read Single Block response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

DocID022712 Rev 12 83/144

M24LR64E-R Command codes

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Read Single Block command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.4 Write Single Block

On receiving the Write Single Block command, the M24LR64E-R writes the data contained

in the request to the requested block and reports whether the write operation was

successful in the response. The Protocol_extension_flag should be set to 1 for the

M24LR64E-R to operate correctly. If the Protocol_extension_flag is at 0, the M24LR64E-R

answers with an error code. The Option_flag is supported.

During the RF write cycle Wt, there should be no modulation (neither 100% nor 10%),

otherwise the M24LR64E-R may not program correctly the data into the memory. The Wt

time is equal to t1nom + 18 × 302 µs.

Request parameters:

•Request flags

•UID (optional)

•Block number

•Data

Response parameter:

•No parameter. The response is sent back after the writing cycle.

Figure 54. Read Single Block frame exchange between VCD and M24LR64E-R

VCD SOF Read Single Block

request EOF

M24LR64E-R <-t1-> SOF Read Single Block

response EOF

Table 44. Write Single Block request format

Request

SOF Request_flags Write Single

Block UID(1)

1. Gray color means that the field is optional.

Block

number Data CRC16 Request

EOF

- 8 bits 21h 64 bits 16 bits 32 bits 16 bits -

Table 45. Write Single Block response format when Error_flag is NOT set

Response SOF Response_flags CRC16 Response EOF

- 8 bits 16 bits -

Command codes M24LR64E-R

84/144 DocID022712 Rev 12

Response parameter:

•Error code as Error_flag is set:

– 0Fh: error with no information given

– 10h: the specified block is not available

– 12h: the specified block is locked and its contents cannot be changed

– 13h: the specified block was not successfully programmed

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Write Single Block command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

duration of the internal write cycle (from the end of a valid write single block command to the

beginning of the M24LR64E-R response).

Table 46. Write Single Block response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 55. Write Single Block frame exchange between VCD and M24LR64E-R

VCD SOF Write Single

Block request EOF

M24LR64E-R <-t1-> SOF Write Single

Block response EOF Write sequence when

error

M24LR64E-R <------------------- Wt ---------------> SOF Write Single

Block response EOF

DocID022712 Rev 12 85/144

M24LR64E-R Command codes

Figure 56. M24LR64E RF-Busy management following Write command

069

)

:ULWH

FRPPDQG

(

)

,UHSO\

0/5[

(

)

0/5[UHSOLHV5)B%XV\LVUHOHDVHGDIWHU0/5[UHVSRQVH

5)B%XV\

)

:ULWH

FRPPDQG

(

)

(

)

0/5[UHSOLHVZKHQRSWLRQIODJLVVHW5)B%XV\LVUHOHDVHGDIWHU0/5[

UHVSRQVH

5)B%XV\

W 6

)

,UHSO\

0/5[

(

)

9&'VHQGVDIRUELGGHQ:ULWHVHFWRUORFNSDVVZRUGSURWHFWHG5)B%XV\LV

UHOHDVHGDIWHU0/5[FRPPDQG

)

:ULWH

FRPPDQG

(

)

,UHSO\

0/5[

(

)

W

5)B%XV\

Command codes M24LR64E-R

86/144 DocID022712 Rev 12

When configuring in the RF Write in progress mode, the RF WIP/BUSY pin is tied to 0

during the Write & verify sequence, as shown in Figure 57.

Figure 57. M24LR64E RF-Wip management following Write command

069

)

:ULWH

FRPPDQG

(

)

,UHSO\

0/5[

(

)

0/5[UHSOLHV5)B:LSLVUHOHDVHGDIWHU0/5[UHVSRQVH

5)B:LS

)

:ULWH

FRPPDQG

(

)

(

)

0/5[UHSOLHVZKHQRSWLRQIODJLVVHW5)B:LSLVUHOHDVHGDIWHU0/5[

UHVSRQVH

5)B:LS

W 6

)

,UHSO\

0/5[

(

)

9&'VHQGVDIRUELGGHQ:ULWHVHFWRUORFNSDVVZRUGSURWHFWHG5)B:LSLV

UHOHDVHGDIWHU0/5[FRPPDQG

)

:ULWH

FRPPDQG

(

)

,UHSO\

0/5[

(

)

W

5)B:LS

DocID022712 Rev 12 87/144

M24LR64E-R Command codes

26.5 Read Multiple Block

When receiving the Read Multiple Block command, the M24LR64E-R reads the selected

blocks and sends back their value in multiples of 32 bits in the response. The blocks are

numbered from 00h to 1FFh in the request and the value is minus one (–1) in the field. For

example, if the “Number of blocks” field contains the value 06h, seven blocks are read. The

maximum number of blocks is fixed at 32 assuming that they are all located in the same

sector. If the number of blocks overlaps sectors, the M24LR64E-R returns an error code.

The Protocol_extension_flag should be set to 1 for the M24LR64E-R to operate correctly. If

the Protocol_extension_flag is at 0, the M24LR64E-R answers with an error code. The

Option_flag is supported.

Request parameters:

•Request flags

•UID (optional)

•First block number

•Number of blocks

Response parameters:

•Sector security status if Option_flag is set (see Ta ble 49)

•N blocks of data

Table 47. Read Multiple Block request format

Request

SOF

Request_

flags

Read Multiple

Block UID(1)

1. Gray color means that the field is optional.

First block

number

Number

of blocks CRC16 Request

EOF

-8 bits 23h 64 bits 16 bits 8 bits 16 bits -

Table 48. Read Multiple Block response format when Error_flag is NOT set

Response

SOF

Response_

flags

Sector security

status(1)

1. Gray color means that the field is optional.

Data CRC16 Response

EOF

-8 bits

8 bits(2)

2. Repeated as needed.

32 bits(2) 16 bits -

Table 49. Sector security status

b7b6b5b4b3b2b1b0

Reserved for future use.

All at 0.

Password control

bits

Read / Write

protection bits

0: Current sector not locked

1: Current sector locked

Table 50. Read Multiple Block response format when Error_flag is set

Response SOF Response_flags Error code CRC16 Response EOF

- 8 bits 8 bits 16 bits -

Command codes M24LR64E-R

88/144 DocID022712 Rev 12

Response parameter:

•Error code as Error_flag is set:

– 0Fh: error with no information given

– 10h: the specified block is not available

– 15h: the specified block is read-protected

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Read Multiple Block command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.6 Select

When receiving the Select command:

•If the UID is equal to its own UID, the M24LR64E-R enters or stays in the Selected

state and sends a response.

•If the UID does not match its own UID, the selected M24LR64E-R returns to the Ready

state and does not send a response.

The M24LR64E-R answers an error code only if the UID is equal to its own UID. If not, no

response is generated. If an error occurs, the M24LR64E-R remains in its current state.

Request parameter:

•UID

Figure 58. Read Multiple Block frame exchange between VCD and M24LR64E-R

VCD SOF Read Multiple

Block request EOF

M24LR64E-R <-t1-> SOF Read Multiple

Block response EOF

Table 51. Select request format

Request

SOF Request_flags Select UID CRC16 Request

EOF

- 8 bits 25h 64 bits 16 bits -

Table 52. Select Block response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

DocID022712 Rev 12 89/144

M24LR64E-R Command codes

Response parameter:

•No parameter

Response parameter:

•Error code as Error_flag is set:

– 03h: the option is not supported

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Select command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.7 Reset to Ready

On receiving a Reset to Ready command, the M24LR64E-R returns to the Ready state if no

error occurs. In the Addressed mode, the M24LR64E-R answers an error code only if the

UID is equal to its own UID. If not, no response is generated.

Request parameter:

•UID (optional)

Table 53. Select response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 59. Select frame exchange between VCD and M24LR64E-R

VCD SOF Select

request EOF

M24LR64E-R <-t1-> SOF Select

response EOF

Table 54. Reset to Ready request format

Request

SOF Request_flags Reset to Ready UID(1)

1. Gray color means that the field is optional.

CRC16 Request

EOF

- 8 bits 26h 64 bits 16 bits -

Command codes M24LR64E-R

90/144 DocID022712 Rev 12

Response parameter:

•No parameter

Response parameter:

•Error code as Error_flag is set:

– 03h: the option is not supported

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Reset to ready command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.8 Write AFI

On receiving the Write AFI request, the M24LR64E-R programs the 8-bit AFI value to its

memory. The Option_flag is supported.

During the RF write cycle Wt, there should be no modulation (neither 100% nor 10%),

otherwise the M24LR64E-R may not write correctly the AFI value into the memory. The Wt

time is equal to t1nom + 18 × 302 µs.

Table 55. Reset to Ready response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

Table 56. Reset to ready response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 60. Reset to Ready frame exchange between VCD and M24LR64E-R

VCD SOF

Reset to

Ready

request

EOF

M24LR64E-R <-t1-> SOF

Reset to

Ready

response

EOF

DocID022712 Rev 12 91/144

M24LR64E-R Command codes

Request parameter:

•Request flags

•UID (optional)

•AFI

Response parameter:

•No parameter

Response parameter:

•Error code as Error_flag is set

– 12h: the specified block is locked and its contents cannot be changed

– 13h: the specified block was not successfully programmed

Table 57. Write AFI request format

Request

SOF Request_flags Write AFI UID(1)

1. Gray color means that the field is optional.

AFI CRC16 Request

EOF

- 8 bits 27h 64 bits 8 bits 16 bits -

Table 58. Write AFI response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

Table 59. Write AFI response format when Error_flag is set

Response

SOF

Response_

flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 61. Write AFI frame exchange between VCD and M24LR64E-R

VCD SOF Write AFI

request EOF

M24LR64E-R <-t1-> SOF Write AFI

response EOF Write sequence

when error

M24LR64E-R <------------------ Wt --------------> SOF Write AFI

response EOF

Command codes M24LR64E-R

92/144 DocID022712 Rev 12

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Write AFI command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

duration of the internal write cycle (from the end of a valid Write AFI command to the

beginning of the M24LR64E-R response).

26.9 Lock AFI

On receiving the Lock AFI request, the M24LR64E-R locks the AFI value permanently. The

Option_flag is supported.

During the RF write cycle Wt, there should be no modulation (neither 100% nor 10%),

otherwise the M24LR64E-R may not lock correctly the AFI value in memory. The Wt time is

equal to t1nom + 18 × 302 µs.

Request parameter:

•Request Flags

•UID (optional)

Response parameter:

•No parameter

Response parameter:

•Error code as Error_flag is set

– 11h: the specified block is already locked and thus cannot be locked again

– 14h: the specified block was not successfully locked

Table 60. Lock AFI request format

Request

SOF Request_flagsLock AFI UID(1)

1. Gray color means that the field is optional.

CRC16 Request

EOF

- 8 bits 28h 64 bits 16 bits -

Table 61. Lock AFI response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

Table 62. Lock AFI response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

DocID022712 Rev 12 93/144

M24LR64E-R Command codes

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Lock AFI command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

entire duration of the internal write cycle (from the end of valid Lock AFI command to the

beginning of the M24LR64E-R response).

Figure 62. Lock AFI frame exchange between VCD and M24LR64E-R

VCD SOF Lock AFI

request EOF

M24LR64E-R <-t1-> SOF Lock AFI

response EOF Lock sequence

when error

M24LR64E-R <----------------- Wt -----------> SOF Lock AFI

response EOF

Command codes M24LR64E-R

94/144 DocID022712 Rev 12

26.10 Write DSFID

On receiving the Write DSFID request, the M24LR64E-R programs the 8-bit DSFID value to

its memory. The Option_flag is supported.

During the RF write cycle Wt, there should be no modulation (neither 100% nor 10%),

otherwise the M24LR64E-R may not write correctly the DSFID value in memory. The Wt

time is equal to t1nom + 18 × 302 µs.

Request parameter:

•Request flags

•UID (optional)

•DSFID

Response parameter:

•No parameter

Response parameter:

•Error code as Error_flag is set

– 12h: the specified block is locked and its contents cannot be changed

– 13h: the specified block was not successfully programmed

Table 63. Write DSFID request format

Request

SOF Request_flags Write DSFID UID(1)

1. Gray color means that the field is optional.

DSFID CRC16 Request

EOF

- 8 bits 29h 64 bits 8 bits 16 bits -

Table 64. Write DSFID response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

Table 65. Write DSFID response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

DocID022712 Rev 12 95/144

M24LR64E-R Command codes

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Write DSFID command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

duration of the internal write cycle (from the end of a valid Write DSFID command to the

beginning of the M24LR64E-R response).

26.11 Lock DSFID

On receiving the Lock DSFID request, the M24LR64E-R locks the DSFID value

permanently. The Option_flag is supported.

During the RF write cycle Wt, there should be no modulation (neither 100% nor 10%),

otherwise the M24LR64E-R may not lock correctly the DSFID value in memory. The Wt time

is equal to t1nom + 18 × 302 µs.

Request parameter:

•Request flags

•UID (optional)

Figure 63. Write DSFID frame exchange between VCD and M24LR64E-R

VCD SOF Write DSFID

request

M24LR64E-R <-t1-> SO

Write DSFID

response

Write sequence

when error

M24LR64E-R <---------------- Wt ----------> SO

Write DSFID

response EOF

Table 66. Lock DSFID request format

Request

SOF Request_flags Lock DSFID UID(1)

1. Gray color means that the field is optional.

CRC16 Request

EOF

-8 bits 2Ah 64 bits 16 bits -

Table 67. Lock DSFID response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

Command codes M24LR64E-R

96/144 DocID022712 Rev 12

Response parameter:

•No parameter.

Response parameter:

•Error code as Error_flag is set:

– 11h: the specified block is already locked and thus cannot be locked again

– 14h: the specified block was not successfully locked

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Lock DSFID command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

duration of the internal write cycle (from the end of a valid Lock DSFID command to the

beginning of the M24LR64E-R response).

26.12 Get System Info

When receiving the Get System Info command, the M24LR64E-R sends back its

information data in the response. The Option_flag is not supported. The Get System Info

can be issued in both Addressed and Non Addressed modes.

The Protocol_extension_flag can be set to 0 or 1. Table 70 and Table 72 show M24LR64E-

R response to the Get System Info command depending on the value of the

Protocol_extension_flag.

Table 68. Lock DSFID response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 64. Lock DSFID frame exchange between VCD and M24LR64E-R

VCD SOF

Lock

DSFID

request

EOF

M24LR64E-R <-t1-> SOF Lock DSFID

response EOF Lock sequence

when error

M24LR64E-R <---------------- Wt -------------> SOF

Lock

DSFID

response

EOF

DocID022712 Rev 12 97/144

M24LR64E-R Command codes

Request parameter:

•Request flags

•UID (optional)

Response parameters:

•Information flags set to 0Ch. DSFID, AFI and IC reference fields are present.

•UID code on 64 bits

•DSFID value

•AFI value

•M24LR64E-R IC reference: the 8 bits are significant.

Response parameters:

•Information flags set to 0Fh. DSFID, AFI, Memory Size and IC reference fields are

present.

•UID code on 64 bits

•DSFID value

•AFI value

•Memory size. The M24LR64E-R provides 2048 blocks (07FFh) of 4 bytes (03h)

•IC reference: the 8 bits are significant.

Table 69. Get System Info request format

Request

SOF Request_flags Get System Info UID(1)

1. Gray color means that the field is optional.

CRC16 Request

EOF

- 8 bits 2Bh 64 bits 16 bits -

Table 70. Get System Info response format when Protocol_extension_flag = 0 and

Error_flag is NOT set

Response

SOF

Response_

flags

Information

flags UID DSFID AFI IC ref. CRC16 Response

EOF

- 00h 0Bh 64 bits 8 bits 8 bits 5Eh 16 bits -

Table 71. Get System Info response format when Protocol_extension_flag = 1 and

Error_flag is NOT set

Response

SOF

Response

_flags

Information

flags UID DSFID AFI Memory

size

ref CRC16 Response

EOF

- 00h 0Fh 64 bits 8 bits 8 bits 03 07FFh 5Eh 16 bits -

Table 72. Get System Info response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 01h 8 bits 16 bits -

Command codes M24LR64E-R

98/144 DocID022712 Rev 12

Response parameter:

•Error code as Error_flag is set:

– 03h: Option not supported

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Get System Info command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.13 Get Multiple Block Security Status

When receiving the Get Multiple Block Security Status command, the M24LR64E-R sends

back the sector security status. The blocks are numbered from 00h to 01FFh in the request

and the value is minus one (–1) in the field. For example, a value of '06' in the “Number of

blocks” field requests to return the security status of seven blocks.

The Protocol_extension_flag should be set to 1 for the M24LR64E-R to operate correctly. If

the Protocol_extension_flag is at 0, the M24LR64E-R answers with an error code.

During the M24LR64E-R response, if the internal block address counter reaches 01FFh, it

rolls over to 0000h and the Sector Security Status bytes for that location are sent back to the

reader.

Request parameter:

•Request flags

•UID (optional)

•First block number

•Number of blocks

Figure 65. Get System Info frame exchange between VCD and M24LR64E-R

VCD SOF Get System Info

request EOF

M24LR64E-R <-t1-> SOF Get System Info

response EOF

Table 73. Get Multiple Block Security Status request format

Request

SOF

Request

_flags

Get Multiple Block

Security Status UID(1)

1. Gray color means that the field is optional.

First block

number

Number

of blocks CRC16 Request

EOF

-8 bits 2Ch 64 bits 16 bits 16 bits 16 bits -

DocID022712 Rev 12 99/144

M24LR64E-R Command codes

Response parameters:

•Sector security status (see Table 75)

Response parameter:

•Error code as Error_flag is set:

– 03h: the option is not supported

– 10h: the specified block is not available

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Get Multiple Block Security Status command to the end of the M24LR64E-R

response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

Table 74. Get Multiple Block Security Status response format when Error_flag is NOT

set

Response

SOF Response_flags Sector security status CRC16 Response

EOF

- 8 bits 8 bits(1)

1. Repeated as needed.

16 bits -

Table 75. Sector security status

b7b6b5b4b3b2b1b0

Reserved for future use

All at 0

Password control

bits

Read / Write

protection bits

0: Current sector not locked

1: Current sector locked

Table 76. Get Multiple Block Security Status response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 66. Get Multiple Block Security Status frame exchange between VCD and

M24LR64E-R

VCD SOF Get Multiple Block

Security Status EOF

M24LR64E-R <-t1-> SOF Get Multiple Block

Security Status EOF

Command codes M24LR64E-R

100/144 DocID022712 Rev 12

26.14 Write-sector Password

On receiving the Write-sector Password command, the M24LR64E-R uses the data

contained in the request to write the password and reports whether the operation was

successful in the response. The Option_flag is supported.

During the RF write cycle time, Wt, there must be no modulation at all (neither 100% nor

10%), otherwise the M24LR64E-R may not correctly program the data into the memory.

The Wt time is equal to t1nom + 18 × 302 µs. After a successful write, the new value of the

selected password is automatically activated. It is not required to present the new password

value until M24LR64E-R power-down.

Request parameter:

•Request flags

•UID (optional)

•Password number (01h = Pswd1, 02h = Pswd2, 03h = Pswd3, other = Error)

•Data

Response parameter:

•no parameter.

Response parameter:

•Error code as Error_flag is set:

– 10h: the password number is incorrect

– 12h: the session was not opened before the password update

– 13h: the specified block was not successfully programmed

– 0Fh: the presented password is incorrect

Table 77. Write-sector Password request format

Request

SOF

Request

_flags

Write-sector

password

IC Mfg

code UID(1)

1. Gray color means that the field is optional.

Password

number Data CRC16 Request

EOF

-8 bits B1h02h

64 bits 8 bits 32 bits 16 bits -

Table 78. Write-sector Password response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

Table 79. Write-sector Password response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

DocID022712 Rev 12 101/144

M24LR64E-R Command codes

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Write-sector Password command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

duration of the internal write cycle (from the end of a valid Write sector password command

to the beginning of the M24LR64E-R response).

26.15 Lock-sector

On receiving the Lock-sector command, the M24LR64E-R sets the access rights and

permanently locks the selected sector. The Option_flag is supported.

A sector is selected by giving the address of one of its blocks in the Lock-sector request

(Sector number field). For example, addresses 0 to 31 are used to select sector 0 and

addresses 32 to 63 are used to select sector 1. Care must be taken when issuing the Lock-

sector command as all the blocks belonging to the same sector are automatically locked by

a single command.

The Protocol_extension_flag should be set to 1 for the M24LR64E-R to operate correctly. If

the Protocol_extension_flag is at 0, the M24LR64E-R answers with an error code.

During the RF write cycle Wt, there should be no modulation (neither 100% nor 10%),

otherwise the M24LR64E-R may not correctly lock the memory block. The Wt time is equal

to t1nom + 18 × 302 µs.

Figure 67. Write-sector Password frame exchange between VCD and M24LR64E-R

VCD SOF

Write-

sector

Password

request

EOF

M24LR64E-R <-t1-> SOF

Write-sector

Password

response

EOF Write sequence

when error

M24LR64E-R <---------------- Wt -------------> SOF

Write-

sector

Password

response

EOF

Table 80. Lock-sector request format

Request

SOF

Request

_flags

Lock-

sector

IC Mfg

code UID(1)

1. Gray color means that the field is optional.

Sector

number

Sector security

status CRC16 Request

EOF

- 8 bits B2h 02h 64 bits 16 bits 8 bits 16 bits -

Command codes M24LR64E-R

102/144 DocID022712 Rev 12

Request parameters:

•Request flags

•(optional) UID

•Sector number

•Sector security status (refer to Table 81)

Response parameter:

•No parameter

Response parameter:

•Error code as Error_flag is set:

– 10h: the specified block is not available

– 11h: the specified block is already locked and thus cannot be locked again

– 14h: the specified block was not successfully locked

Table 81. Sector security status

b7b6b5b4b3b2b1b0

0 0 0 Password control bits Read / Write protection bits 1

Table 82. Lock-sector response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

Table 83. Lock-sector response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 68. Lock-sector frame exchange between VCD and M24LR64E-R

VCD SOF Lock-sector

request EOF

M24LR64E-R <-t1-> SOF Lock-sector

response EOF Lock sequence

when error

M24LR64E-R <--------------- Wt -----------> SOF Lock-sector

response EOF

DocID022712 Rev 12 103/144

M24LR64E-R Command codes

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Lock-sector command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

duration of the internal write cycle (from the end of a valid Lock sector command to the

beginning of the M24LR64E-R response).

26.16 Present-sector Password

On receiving the Present-sector Password command, the M24LR64E-R compares the

requested password with the data contained in the request and reports whether the

operation has been successful in the response. The Option_flag is supported.

During the comparison cycle equal to Wt, there should be no modulation (neither 100% nor

10%), otherwise the M24LR64E-R Password value may not be correctly compared. The Wt

time is equal to t1nom + 18 × 302 µs.

After a successful command, the access to all the memory blocks linked to the password is

changed as described in Section 4.1: M24LR64E-R block security in RF mode.

Request parameter:

•Request flags

•UID (optional)

•Password Number (0x01 = Pswd1, 0x02 = Pswd2, 0x03 = Pswd3, other = Error)

•Password

Response parameter:

•No parameter. The response is sent back after the write cycle.

Table 84. Present-sector Password request format

Request

SOF

Request

_flags

Present-

sector

Password

IC Mfg

code UID(1)

1. Gray color means that the field is optional.

Password

number Password CRC16 Request

EOF

-8 bitsB3h02h64 bits 8 bits 32 bits 16 bits -

Table 85. Present-sector Password response format when Error_flag is NOT set

Response

SOF Response_flags CRC16 Response

EOF

- 8 bits 16 bits -

Table 86. Present-sector Password response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Command codes M24LR64E-R

104/144 DocID022712 Rev 12

Response parameter:

•Error code as Error_flag is set:

– 10h: the password number is incorrect

– 0Fh: the present password is incorrect

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Present Sector Password command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY remains in high-Z

state.

26.17 Fast Read Single Block

On receiving the Fast Read Single Block command, the M24LR64E-R reads the requested

block and sends back its 32-bit value in the response. The Option_flag is supported. The

data rate of the response is multiplied by 2.

The Protocol_extension_flag should be set to 1 for the M24LR64E-R to operate correctly. If

the Protocol_extension_flag is at 0, the M24LR64E-R answers with an error code.

The subcarrier_flag should be set to 0, otherwise the M24LR64E-R answers with an error

code.

Figure 69.

Present-sector Password frame exchange between VCD and M24LR64E-R

VCD SOF

Present-

sector

password

response

OR error

0F (bad

password)

EOF

M24LR64E-R <-t1-> SOF

Present-

sector

password

response

EOF Sequence

when error

M24LR64E-R <---------------- Wt ------------> SOF

Present-

sector

password

response

EOF

Table 87. Fast Read Single Block request format

Request

SOF Request_flags Fast Read

Single Block

IC Mfg

code UID(1)

1. Gray color means that the field is optional.

Block

number CRC16 Request

EOF

-8 bits C0h02h

64 bits 16 bits 16 bits -

DocID022712 Rev 12 105/144

M24LR64E-R Command codes

Request parameters:

•Request flags

•UID (optional)

•Block number

Response parameters:

•Sector security status if Option_flag is set (see Ta ble 89)

•Four bytes of block data

Response parameter:

•Error code as Error_flag is set:

– 10h: the specified block is not available

– 15h: the specified block is read-protected

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Fast Read Single block command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

Table 88. Fast Read Single Block response format when Error_flag is NOT set

Response

SOF Response_flags Sector security

status(1)

1. Gray color means that the field is optional.

Data CRC16 Response

EOF

-8 bits 8 bits 32 bits 16 bits -

Table 89. Sector security status

b7b6b5b4b3b2b1b0

Reserved for future use

All at 0

Password control

bits

Read / Write

protection bits

0: Current sector not locked

1: Current sector locked

Table 90. Fast Read Single Block response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 70. Fast Read Single Block frame exchange between VCD and M24LR64E-R

VCD SOF Fast Read Single

Block request EOF

M24LR64E-R <-t1-> SOF Fast Read Single

Block response EOF

Command codes M24LR64E-R

106/144 DocID022712 Rev 12

26.18 Fast Inventory Initiated

Before receiving the Fast Inventory Initiated command, the M24LR64E-R must have

received an Initiate or a Fast Initiate command in order to set the Initiate_ flag. If not, the

M24LR64E-R does not answer the Fast Inventory Initiated command.

The subcarrier_flag should be set to 0, otherwise the M24LR64E-R answers with an error

code.

On receiving the Fast Inventory Initiated request, the M24LR64E-R runs the anticollision

sequence. The Inventory_flag must be set to 1. The meaning of flags 5 to 8 is shown in

Table 29. The data rate of the response is multiplied by 2.

The request contains:

•the flags,

•the Inventory command code,

•the AFI if the AFI flag is set,

•the mask length,

•the mask value,

•the CRC.

The M24LR64E-R does not generate any answer in case of error.

The Response contains:

•the flags,

•the Unique ID.

During an Inventory process, if the VCD does not receive an RF M24LR64E-R response, it

waits for a time t3 before sending an EOF to switch to the next slot. t3 starts from the rising

edge of the request EOF sent by the VCD.

•If the VCD sends a 100% modulated EOF, the minimum value of t3 is:

t3min = 4384/fC (323.3µs) + tSOF

•If the VCD sends a 10% modulated EOF, the minimum value of t3 is:

t3min = 4384/fC (323.3µs) + tNRT

where:

•tSOF is the time required by the M24LR64E-R to transmit an SOF to the VCD

•tNRT is the nominal response time of the M24LR64E-R

Table 91. Fast Inventory Initiated request format

Request

SOF

Request

_flags

Fast Inventory

Initiated

IC Mfg

code

Optional

AFI

Mask

length

Mask

value CRC16 Request

EOF

- 8 bits C1h 02h 8 bits 8 bits 0 - 64

bits 16 bits -

Table 92. Fast Inventory Initiated response format

Response

SOF Response_flags DSFID UID CRC16 Response

EOF

- 8 bits 8 bits 64 bits 16 bits -

DocID022712 Rev 12 107/144

M24LR64E-R Command codes

tNRT and tSOF are dependent on the M24LR64E-R-to-VCD data rate and subcarrier

modulation mode.

When configured in the RF busy mode, the RF WIP/BUSY pin is driven to 0 from the SOF

starting the inventory command to the end of the M24LR64E-R response. If the M24LR64E-

R does not receive the corresponding slot marker, the RF WIP/BUSY pin remains at 0 until

the next RF power-off.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.19 Fast Initiate

On receiving the Fast Initiate command, the M24LR64E-R sets the internal Initiate_flag and

sends back a response only if it is in the Ready state. The command has to be issued in the

Non Addressed mode only (Select_flag is reset to 0 and Address_flag is reset to 0). If an

error occurs, the M24LR64E-R does not generate any answer. The Initiate_flag is reset after

a power-off of the M24LR64E-R. The data rate of the response is multiplied by 2.

The subcarrier_flag should be set to 0, otherwise the M24LR64E-R answers with an error

code.

The request contains:

•No data

The response contains:

•the flags,

•the Unique ID.

Table 93. Fast Initiate request format

Request

SOF Request_flags Fast Initiate IC Mfg Code CRC16 Request

EOF

- 8 bits C2h 02h 16 bits -

Table 94. Fast Initiate response format

Response

SOF Response_flags DSFID UID CRC16 Response

EOF

- 8 bits 8 bits 64 bits 16 bits -

Figure 71. Fast Initiate frame exchange between VCD and M24LR64E-R

VCD SOF Fast Initiate

request EOF

M24LR64E-R <-t1-> SOF Fast Initiate

response EOF

Command codes M24LR64E-R

108/144 DocID022712 Rev 12

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Fast Initiate command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z state.

26.20 Fast Read Multiple Block

On receiving the Fast Read Multiple Block command, the M24LR64E-R reads the selected

blocks and sends back their value in multiples of 32 bits in the response. The blocks are

numbered from 00h to 1FFh in the request and the value is minus one (–1) in the field. For

example, if the “Number of blocks” field contains the value 06h, seven blocks are read. The

maximum number of blocks is fixed to 32 assuming that they are all located in the same

sector. If the number of blocks overlaps sectors, the M24LR64E-R returns an error code.

The Protocol_extension_flag should be set to 1 for the M24LR64E-R to operate correctly. If

the Protocol_extension_flag is at 0, the M24LR64E-R answers with an error code.

The Option_flag is supported. The data rate of the response is multiplied by 2.

The subcarrier_flag should be set to 0, otherwise the M24LR64E-R answers with an error

code.

Request parameters:

•Request flag

•UID (Optional)

•First block number

•Number of blocks

Response parameters:

•Sector security status if Option_flag is set (see Ta ble 97)

•N block of data

Table 95. Fast Read Multiple Block request format

Request

SOF

Request_

flags

Fast Read

Multiple

Block

IC Mfg

code UID(1)

1. Gray color means that the field is optional.

First

block

number

Number

blocks

CRC16 Request

EOF

-8 bits C3h02h

64 bits 16 bits 8 bits 16 bits -

Table 96. Fast Read Multiple Block response format when Error_flag is NOT set

Response

SOF Response_flags Sector security

status(1)

1. Gray color means that the field is optional.

Data CRC16 Response

EOF

-8 bits8 bits(2)

2. Repeated as needed.

32 bits(2) 16 bits -

DocID022712 Rev 12 109/144

M24LR64E-R Command codes

Response parameter:

•Error code as Error_flag is set:

– 03h: the option is not supported

– 10h: block address not available

– 15h: block read-protected

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Fast Read Multiple Block command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.21 Inventory Initiated

Before receiving the Inventory Initiated command, the M24LR64E-R must have received an

Initiate or a Fast Initiate command in order to set the Initiate_ flag. If not, the M24LR64E-R

does not answer the Inventory Initiated command.

On receiving the Inventory Initiated request, the M24LR64E-R runs the anticollision

sequence. The Inventory_flag must be set to 1. The meaning of flags 5 to 8 is given in

Table 29 on page 68.

Table 97. Sector security status if Option_flag is set

b7b6b5b4b3b2b1b0

Reserved for future use

All at 0

Password

control bits

Read / Write

protection bits

0: Current sector not locked

1: Current sector locked

Table 98. Fast Read Multiple Block response format when Error_flag is set

Response SOF Response_flags Error code CRC16 Response EOF

- 8 bits 8 bits 16 bits -

Figure 72. Fast Read Multiple Block frame exchange between VCD and M24LR64E-R

VCD SOF

Fast Read

Multiple Block

request

EOF

M24LR64E-R <-t1-> SOF

Fast Read

Multiple Block

response

EOF

Command codes M24LR64E-R

110/144 DocID022712 Rev 12

The request contains:

•the flags,

•the Inventory Command code,

•the AFI if the AFI flag is set,

•the mask length,

•the mask value,

•the CRC.

The M24LR64E-R does not generate any answer in case of error.

The response contains:

•the flags,

•the Unique ID.

During an Inventory process, if the VCD does not receive an RF M24LR64E-R response, it

waits for a time t3 before sending an EOF to switch to the next slot. t3 starts from the rising

edge of the request EOF sent by the VCD.

•If the VCD sends a 100% modulated EOF, the minimum value of t3 is:

t3min = 4384/fC (323.3µs) + tSOF

•If the VCD sends a 10% modulated EOF, the minimum value of t3 is:

t3min = 4384/fC (323.3µs) + tNRT

where:

•tSOF is the time required by the M24LR64E-R to transmit an SOF to the VCD

•tNRT is the nominal response time of the M24LR64E-R

tNRT and tSOF are dependent on the M24LR64E-R-to-VCD data rate and subcarrier

modulation mode.

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF

starting the inventory command to the end of the M24LR64E-R response. If the M24LR64E-

R does not receive the corresponding slot marker, the RF WIP/BUSY pin remains at 0 until

the next RF power-off.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

Table 99. Inventory Initiated request format

Request

SOF

Request

_flags

Inventory

Initiated

IC Mfg

code

Optional

AFI

Mask

length Mask value CRC16 Request

EOF

- 8 bits D1h 02h 8 bits 8 bits 0 - 64 bits 16 bits -

Table 100. Inventory Initiated response format

Response

SOF Response_flags DSFID UID CRC16 Response

EOF

- 8 bits 8 bits 64 bits 16 bits -

DocID022712 Rev 12 111/144

M24LR64E-R Command codes

26.22 Initiate

On receiving the Initiate command, the M24LR64E-R sets the internal Initiate_flag and

sends back a response only if it is in the ready state. The command has to be issued in the

Non Addressed mode only (Select_flag is reset to 0 and Address_flag is reset to 0). If an

error occurs, the M24LR64E-R does not generate any answer. The Initiate_flag is reset after

a power-off of the M24LR64E-R.

The request contains:

•No data

The response contains:

•the flags,

•the Unique ID.

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the Initiate command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.23 ReadCfg

On receiving the ReadCfg command, the M24LR64E-R reads the Configuration byte and

sends back its 8-bit value in the response.

Table 101. Initiate request format

Request

SOF Request_flags Initiate IC Mfg code CRC16 Request

EOF

- 8 bits D2h 02h 16 bits -

Table 102. Initiate response format

Response

SOF Response_flags DSFID UID CRC16 Response

EOF

- 8 bits 8 bits 64 bits 16 bits -

Figure 73. Initiate frame exchange between VCD and M24LR64E-R

VCD SOF Initiate

request EOF

M24LR64E-R <-t1-> SOF Initiate

response EOF

Command codes M24LR64E-R

112/144 DocID022712 Rev 12

The Protocol_extension_flag should be set to 0 for the M24LR64E-R to operate correctly. If

the Protocol_extension_flag is at 1, the M24LR64E-R answers with an error code. The

Option_flag is not supported. The Inventory_flag must be set to 0.

Request parameters:

•UID (optional)

Response parameters:

•One byte of data: Configuration byte

Response parameter:

•Error code as Error_flag is set

– 03h: the option is not supported

– 0Fh: error with no information given

Figure 74. ReadCfg frame exchange between VCD and M24LR64E-R

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the ReadCfg command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

Table 103. ReadCfg request format

Request

SOF Request_flags ReadCfg IC Mfg code UID(1)

1. Gray color means that the field is optional.

CRC16 Request

EOF

- 8 bits A0h 02h 64 bits 16 bits -

Table 104. ReadCfg response format when Error_flag is NOT set

Response

SOF Response_flags Data CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Table 105. ReadCfg response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

VCD SOF ReadCfg request EOF

M24LR64E-R <-t1-> SOF ReadCfg response EOF

DocID022712 Rev 12 113/144

M24LR64E-R Command codes

26.24 WriteEHCfg

On receiving the WriteEHCfg command, the M24LR64E-R writes the data contained in the

request to the Configuration byte and reports whether the write operation was successful in

the response. The Protocol_extension_flag should be set to 0 for the M24LR64E-R to

operate correctly. If the Protocol_extension_flag is at 1, the M24LR64E-R answers with an

error code.

The Option_flag is supported, the Inventory_flag is not supported.

During the RF write cycle Wt, there should be no modulation (neither 100% nor 10%),

otherwise the M24LR64E-R may not program correctly the data into the Configuration byte.

The Wt time is equal to t1nom + 18 × 302 µs.

Request parameters:

•Request flags

•UID (optional)

•Data: during WriteEHCfg command, bit 3 of the data is ignored (see Table 14).

Response parameter:

•No parameter. The response is sent back after the writing cycle.

Response parameter:

•Error code as Error_flag is set:

– 13h: the specified block was not successfully programmed

Table 106. WriteEHCfg request format

Request

SOF Request_flags WriteEHCfg IC Mfg code UID(1)

1. Gray color means that the field is optional.

Data CRC16 Request

EOF

-8 bits A1h02h

64 bits 8 bits 16 bits -

Table 107. WriteEHCfg response format when Error_flag is NOT set

Response SOF Response_flags CRC16 Response EOF

- 8 bits 16 bits -

Table 108. WriteEHCfg response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Command codes M24LR64E-R

114/144 DocID022712 Rev 12

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the WriteEHCfg command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

entire duration of the internal write cycle (from the end of a valid WriteEHCfg command to

the beginning of the M24LR64E-R response).

26.25 WriteDOCfg

On receiving the WriteDOCfg command, the M24LR64E-R writes the data contained in the

request to the Configuration byte and reports whether the write operation was successful in

the response. The Protocol_extension_flag should be set to 0 for the M24LR64E-R to operate

correctly. If the Protocol_extension_flag is at 1, the M24LR64E-R answers with an error code.

The Option_flag is supported, the Inventory_flag is not supported.

During the RF write cycle Wt, there should be no modulation (neither 100% nor 10%),

otherwise the M24LR64E-R may not program correctly the data into the Configuration byte.

The Wt time is equal to t1nom + 18 × 302 µs.

Request parameters:

•Request flag

•UID (optional)

•Data: during a WriteDOCfg command, bits 2 to 0 of the data are ignored (see Table 14 ).

Figure 75. WriteEHCfg frame exchange between VCD and M24LR64E-R

VCD SOF WriteEHCfg

request EOF

M24LR64E-R <-t1-> SOF WriteEHCfg

response EOF WriteEHCfg sequence

when error

M24LR64E-R <------------------- Wt ---------------> SOF WriteEHCfg

response EOF

Table 109. WriteDOCfg request format

Request

SOF Request_ flags WriteDOCfg IC Mfg code UID(1)

1. Gray color means that the field is optional.

Data CRC16 Request

EOF

- 8 bits A4h 02h 64 bits 8 bits 16 bits -

DocID022712 Rev 12 115/144

M24LR64E-R Command codes

Response parameter:

•No parameter. The response is sent back after the writing cycle.

Response parameter:

•Error code as Error_flag is set:

– 13h: the specified block was not successfully programmed

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the WriteEHCfg command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin is tied to 0 for the

entire duration of the internal write cycle (from the end of a valid WriteDOCfg command to

the beginning of the M24LR64E-R response).

26.26 SetRstEHEn

On receiving the SetRstEHEn command, the M24LR64E-R sets or resets the EH_enable bit

in the volatile Control register. The Protocol_extension_flag should be set to 0 for the

M24LR64E-R to operate correctly. If the Protocol_extension_flag is at 1, the M24LR64E-R

answers with an error code. The Option_flag and the Inventory_flag are not supported.

Table 110. WriteDOCfg response format when Error_flag is NOT set

Response SOF Response_flags CRC16 Response EOF

- 8 bits 16 bits -

Table 111. WriteDOCfg response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 76. WriteDOCfg frame exchange between VCD and M24LR64E-R

VCD SOF WriteDOCfg

request EOF

M24LR64E-R <-t1-> SOF WriteDOCfg

response EOF WriteDOCfg sequence

when error

M24LR64E-R <----------------- Wt --------------> SOF WriteDOCfg

response EOF

Command codes M24LR64E-R

116/144 DocID022712 Rev 12

Request parameters:

•Request flags

•UID (optional)

•Data: during a SetRstEHEn command, bits 7 to 1 are ignored. Bit 0 is the EH_enable

bit.

Response parameter:

•No parameter. The response is sent back after t1.

Response parameter:

•Error code as Error_flag is set:

– 03h: the option is not supported

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the SetRstEHEn command to the end of the M24LR64E-R response.

Table 112. SetRstEHEn request format

Request

SOF Request_flags SetRstEHEn IC Mfg code UID(1)

1. Gray color means that the field is optional.

Data CRC16 Request

EOF

-8 bits A2h 02h

64 bits 8 bits 16 bits -

Table 113. SetRstEHEn response format when Error_flag is NOT set

Response SOF Response_flags CRC16 Response EOF

- 8 bits 16 bits -

Table 114. SetRstEHEn response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Figure 77. SetRstEHEn frame exchange between VCD and M24LR64E-R

VCD SOF SetRstEHEn

request EOF

M24LR64E-R <-t1-> SOF SetRstEHEn

response EOF WriteEHCfg sequence

when no error

M24LR64E-R <-t1-> SOF SetRstEHEn

response EOF WriteEHCfg sequence

when error

DocID022712 Rev 12 117/144

M24LR64E-R Command codes

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

26.27 CheckEHEn

On receiving the CheckEHEn command, the M24LR64E-R reads the Control register and

sends back its 8-bit value in the response.

The Protocol_extension_flag should be set to 0 for the M24LR64E-R to operate correctly. If

the Protocol_extension_flag is at 1, the M24LR64E-R answers with an error code. The

Option_flag is not supported. The Inventory_flag must be set to 0.

Request parameters:

•UID (optional)

Response parameters:

•One byte of data: volatile Control register (see Table 15)

Response parameter:

•Error code as Error_flag is set

– 03h: the option is not supported

Table 115. CheckEHEn request format

Request

SOF Request_flags CheckEHEn IC Mfg code UID(1)

1. Gray color means that the field is optional.

CRC16 Request

EOF

- 8 bits A3h 02h 64 bits 16 bits -

Table 116. CheckEHEn response format when Error_flag is NOT set

Response

SOF Response_flags Data CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Table 117. CheckEHEn response format when Error_flag is set

Response

SOF Response_flags Error code CRC16 Response

EOF

- 8 bits 8 bits 16 bits -

Command codes M24LR64E-R

118/144 DocID022712 Rev 12

When configured in the RF busy mode, the RF WIP/BUSY pin is tied to 0 from the SOF that

starts the CheckEHEn command to the end of the M24LR64E-R response.

When configured in the RF write in progress mode, the RF WIP/BUSY pin remains in high-Z

state.

Figure 78. CheckEHEn frame exchange between VCD and M24LR64E-R

VCD SOF CheckEHEn request EOF

M24LR64E-R <-t1-> SOF CheckEHEn

response EOF

DocID022712 Rev 12 119/144

M24LR64E-R Maximum ratings

27 Maximum ratings

Stressing the device above the rating listed in Table 118 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. Refer also to the STMicroelectronics SURE Program and other

relevant quality documents.

Table 118. Absolute maximum ratings

Symbol Parameter Min. Max. Unit

TAAmbient operating temperature -40 85 °C

TSTG

hSTG

, tSTG

Storage conditions Sawn wafer

on UV tape

15 25 °C

-9

(1)

1. Counted from ST shipment date.

months

Kept in its original

packing form

TSTG Storage temperature UFDFPN8 (MLP8),

SO8, TSSOP8 -65 150 °C

TLEAD Lead temperature during soldering UFDFPN8 (MLP8),

SO8, TSSOP8 See note (2)

2. Compliant with JEDEC Std J-STD-020C (for small body, Sn-Pb or Pb assembly), the ST

ECOPACK® 7191395 specification, and the European directive on Restrictions on Hazardous

Substances (RoHS) 2002/95/EU.

°C

VIO I2C input or output range -0.50 6.5 V

VCC I2C supply voltage -0.50 6.5 V

IOL_MAX

DC output current on pin SDA or RF WIP/BUSY (when

equal to 0) -5mA

ICC(3)

3. Based on characterization, not tested in production.

RF supply current AC0 - AC1 - 50 mA

VMAX_1(3)

RF input voltage amplitude peak to

peak between AC0 and AC1, GND

pad left floating

VAC0-VAC1 - 27 V

VMAX_2(3) AC voltage between AC0 and GND,

or AC1 and GND

VAC0-GND,

or VAC1-GND -1 11 V

VESD

Electrostatic discharge voltage

(human body model)(4)

4. AEC-Q100-002 (compliant with JEDEC Std JESD22-A114, C1 = 100 pF, R1 = 1500 Ω,

R2 = 500 Ω)

AC0, AC1 - 1000

Other pads - 3500

Electrostatic discharge voltage

on antenna (5)

5. Compliant with IEC 61000-4-3 method. (M24LRxxE packaged in S08N is mounted on ST’s

reference antenna ANT1- M24LRxxE)

AC0, AC1 - 4000

I2C DC and AC parameters M24LR64E-R

120/144 DocID022712 Rev 12

28 I2C DC and AC parameters

This section summarizes the operating and measurement conditions, and the DC and AC

characteristics of the device in I2C 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.

Figure 79. AC test measurement I/O waveform

Table 119. I2C operating conditions

Symbol Parameter Min. Max. Unit

VCC Supply voltage 1.8 5.5 V

TAAmbient operating temperature -40 85 °C

Table 120. AC test measurement conditions

Symbol Parameter Min. Max. Unit

CLLoad capacitance 100 pF

tr, tfInput rise and fall times - 50 ns

Vhi-lo Input levels 0.2 VCC to 0.8 VCC V

Vref(t) Input and output timing reference levels 0.3 VCC to 0.7 VCC V

Table 121. Input parameters

Symbol Parameter Min. Max. Unit

CIN Input capacitance (SDA) - 8 pF

CIN Input capacitance (other pins) - 6 pF

tNS(1)

1. Characterized only.

Pulse width ignored (Input filter on SCL and SDA) - 80 ns

!)"

6##

6##

6##

6##

)NPUTAND/UTPUT

4IMING2EFERENCE,EVELS

)NPUT,EVELS

DocID022712 Rev 12 121/144

M24LR64E-R I2C DC and AC parameters

Table 122. I2C DC characteristics

Symbol Parameter Test condition Min. Max. Unit

ILI

Input leakage current

(SCL, SDA)

VIN = VSS or VCC

device in Standby mode -± 2µA

ILO_Vout Vout output leakage current External voltage applied on

Vout: VSS or VCC

-± 5µA

ILO Output leakage current SDA in Hi-Z, external voltage

applied on SDA: VSS or VCC

-± 2µA

ICC Supply current (Read)(1)

1. SCL, SDA connected to Ground or VCC. SDA connected to VCC through a pull-up resistor.

VCC = 1.8 V, fc = 100 kHz

(rise/fall time < 50 ns) -50

µA

VCC = 1.8 V, fc = 400 kHz

(rise/fall time < 50 ns) - 100

VCC = 2.5 V, fc = 400 kHz

(rise/fall time < 50 ns) - 200

VCC = 5.5 V, fc = 400 kHz

(rise/fall time < 50 ns) - 400

ICC0 Supply current (Write)(1) VCC = 1.8 - 5.5 V - 220 µA

ICC1 Standby supply current

VIN = VSS or VCC

VCC = 1.8 V -30

µA

VIN = VSS or VCC

VCC = 2.5 V -30

VIN = VSS or VCC

VCC = 5.5 V - 100

VIL

Input low voltage

(SDA, SCL)

VCC = 1.8 V -0.45 0.25VCC

VVCC = 2.5 V -0.45 0.25VCC

VCC = 5.5 V -0.45 0.3VCC

VIH

Input high voltage

(SDA, SCL)

VCC = 1.8 V 0.75VCC VCC+1

VVCC = 2.5 V 0.75VCC VCC+1

VCC = 5.5 V 0.7VCC VCC+1

VOL Output low voltage IOL = 2.1 mA, VCC = 1.8 V or

IOL = 3 mA, VCC = 5.5 V -0.4V

I2C DC and AC parameters M24LR64E-R

122/144 DocID022712 Rev 12

Table 123. I2C AC characteristics

Test conditions specified in Table 119

Symbol Alt. Parameter Min. Max. Unit

fCfSCL Clock frequency 25 400 kHz

tCHCL tHIGH Clock pulse width high 0.6 20000(1)

1. tCHCL timeout.

µs

tCLCH tLOW Clock pulse width low 1.3 20000(2)

2. tCLCH timeout.

µs

tSTART_OUT - I²C timeout on Start condition 40 - ms

tXH1XH2(3)

3. Values recommended by the I²C-bus Fast-Mode specification.

tRInput signal rise time 20 300 ns

tXL1XL2(3) tFInput signal fall time 20 300 ns

tDL1DL2 tFSDA (out) fall time 20 100 ns

tDXCX tSU:DAT Data in set up time 100 - ns

tCLDX tHD:DAT Data in hold time 0 - ns

tCLQX(4)

4. To avoid spurious Start and Stop conditions, a minimum delay is placed between SCL=1 and

the falling or rising edge of SDA.

tDH Data out hold time 100 - ns

tCLQV(5)

5. tCLQV is the time (from the falling edge of SCL) required by the SDA bus line to reach 0.8VCC in

a compatible way with the I2C specification (which specifies tSU:DAT (min) = 100 ns), assuming

that the Rbus × Cbus time constant is less than 500 ns (as specified in Figure 3).

tAA Clock low to next data valid (access time) 100 900 ns

tCHDX(6)

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

tSU:STA Start condition set up time 600 - ns

tDLCL tHD:STA Start condition hold time 0.6 35000(7)

7. tDLCL timeout.

µs

tCHDH tSU:STO Stop condition set up time 600 - ns

tDHDL tBUF Time between Stop condition and next Start condition 1300 - ns

tW- I²C write time - 5 ms

DocID022712 Rev 12 123/144

M24LR64E-R I2C DC and AC parameters

Figure 80. I2C AC waveforms

3#,

3$!)N

3#,

3$!/UT

3#,

3$!)N

T#(#,

T$,#,

T#($8

3TART

CONDITION

T#,#(

T$8#8T#,$8

3$!

)NPUT

3$!

#HANGE

T#($( T$($,

3TOP

CONDITION

$ATAVALID

T#,16 T#,18

T#($(

3TOP

CONDITION

T#($8

3TART

CONDITION

7RITECYCLE

!)E

3TART

CONDITION

T#(#,

T8(8(

T8,8,

$ATAVALID

T$,$,

Write cycle definition M24LR64E-R

124/144 DocID022712 Rev 12

29 Write cycle definition

Table 124. Write cycle endurance(1)

1. A write cycle means the simultaneous writing of one byte, two bytes, three bytes or four bytes (one page).

Symbol Parameter Test conditions Min Max Unit

Ncycle(2)

2. Indicates the total number of write/erase cycles for one memory cell or the overall number of write/erase

cycles decoded by the whole memory.

Write cycle

endurance(3)

3. Write cycle endurance is defined by characterization and qualification.

TA≤ + 25 °C

VCC(min) < VCC < VCC(max)

- 1000000

Write cycle

TA≤ + 85 °C

VCC(min) < VCC < VCC(max)

- 150000

DocID022712 Rev 12 125/144

M24LR64E-R RF electrical parameters

30 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 125. RF characteristics(1) (2)

Symbol Parameter Condition Min Typ Max Unit

fCC External RF signal frequency - 13.553 13.56 13.567 MHz

H_ISO Operating field according to ISO TA = -40 °C to 85 °C 150 - 5000 mA/

MICARRIER

10% carrier modulation index(3)

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

150 mA/m > H_ISO > 1000

mA/m 15 - 30

H_ISO > 1000 mA/m 10 - 30

tRFR,t

RFF 10% rise and fall time - 0.5 - 3.0 µs

tRFSBL 10% minimum pulse width for bit - 7.1 - 9.44 µs

MICARRIER 100% carrier modulation index MI=(A-B)/(A+B)(4) 95 - 100 %

tRFR,t

RFF 100% rise and fall time - 0.5 - 3.5 µs

tRFSBL 100% minimum pulse width for bit - 7 - 9.44 µs

tMIN CD

Minimum time from carrier

generation to first data From H-field min - - 1 ms

fSH Subcarrier frequency high fCC/32 - 423.75 - kHz

fSL Subcarrier frequency low fCC/28 - 484.28 - kHz

t1Time for M24LR64E-R response 4224/fS318.6 320.9 323.3 µs

t2Time between commands 4224/fS309 311.5 314 µs

RF write time (including internal

Verify) - - 5.75 - ms

ICC_RF Operating current (Read)(5) VAC0-VAC1 (4 V peak to peak) - 20 - µA

CTUN Internal tuning capacitor in SO8(6) f = 13.56 MHz 24.8 27.5 30.2 pF

VBACK

Backscattered level as defined by

ISO test ISO10373-7 10 - - mV

VMAX_1(3)

RF input voltage amplitude

between AC0 and AC1, GND pad

left floating, VAC0-VAC1 peak to

peak(7)

---20V

VMAX_2(3) AC voltage between AC0 and

GND or between AC1 and GND --1-8.5V

RF electrical parameters M24LR64E-R

126/144 DocID022712 Rev 12

Figure 81 shows an ASK modulated signal from the VCD to the M24LR64E-R. The test

conditions for the AC/DC parameters are:

•Close coupling condition with tester antenna (1 mm)

•M24LR64E-R performance measured at the tag antenna

•M24LR64E-R synchronous timing, transmit and receive

VMIN_1(3)

RF input voltage amplitude

between AC0 and AC1, GND pad

left floating, VAC0-VAC1 peak to

peak(7)

Inventory and Read operations - 4 4.5 V

Write operations - 4.5 5 V

VMIN_2(3) AC voltage between AC0 and

GND or between AC1 and GND

Inventory and Read operations - 1.8 2 V

Write operations - 2 2.2 V

tRF_OFF RF OFF time Chip reset 2 - - ms

1. TA = –40 to 85 °C. Characterized only.

2. All timing characterizations were performed on a reference antenna with the following characteristics:

External size: 75 mm x 48 mm

Number of turns: 5

Width of conductor: 0.5 mm

Space between two conductors: 0.3 mm

Value of the tuning capacitor in SO8: 27.5 pF (M24LR64E-R)

Value of the coil: 5 µH

Tuning frequency: 13.56 MHz.

3. 15% (or more) carrier modulation index offers a better signal/noise ratio and therefore a wider operating

range with a better noise immunity.

4. Temperature range 0 °C to 90 °C.

5. Characterized on bench.

6. Characterized only, at room temperature only, measured at VAC0-VAC1 = 1 V peak to peak.

7. Characterized only, at room temperature only.

Table 125. RF characteristics(1) (2) (continued)

Symbol Parameter Condition Min Typ Max Unit

Table 126. Operating conditions

Symbol Parameter Min. Max. Unit

TAAmbient operating temperature -40 85 °C

DocID022712 Rev 12 127/144

M24LR64E-R RF electrical parameters

Figure 81. ASK modulated signal

Table 127 summarizes, respectively, the minimum AC0-AC1 input power level PAC0-AC1_min

required for the Energy harvesting mode, the corresponding maximum current consumption

Isink_max, and the variation of the analog voltage Vout for the various Energy harvesting

fan-out configurations defined by bits b0 and b1 of the Configuration byte.

Table 127. Energy harvesting(1) (2)

1. Characterized only.

2. Valid from -40 °C to +85 °C.

Range Hmin(3)

3. Hmin characterized according to ISO10373-7 test method.

Pmin(4)

4. Pmin calculated from DC measurements.

Note: It is recommended to choose the Energy Harvesting Range according to the

maximum current requested by the application to avoid any disabling of Energy

Harvesting mode (for example, choose Range 01 for a max consumption of

2mA).

Vout@I=0 Vout@Isink_max Isink_max@Pmin

00 3.5 A/m 100 mW 2.7 V min

4.5 V max 1.7 V 6 mA

01 2.4 A/m 60 mW 2.7 V min

4.5 V max 1.9 V 3 mA

10 1.6 A/m 30 mW 2.7 V min

4.5 V max 2.1 V 1 mA

11 1.0 A/m 16 mW 2.7 V min

4.5 V max 2.3 V 300 µA

-36

W5)) W5)5

W5)6%/

W0,1&'

I&&

RF electrical parameters M24LR64E-R

128/144 DocID022712 Rev 12

Figure 82. Energy harvesting: Vout min vs. Isink

Figure 83. Energy harvesting: working domain range 11

-36

7PVU

7

7

7

7

7

N" N" N" N" *TJOL

069

)DQRXW

$

P$

P$

P$

P$

$P $P )LHOG

+UPV

$P$P $P

:RUNLQJGRPDLQZKHQ

5DQJHLVVHOHFWHG

DocID022712 Rev 12 129/144

M24LR64E-R RF electrical parameters

Figure 84. Energy harvesting: working domain range 10

Figure 85. Energy harvesting: working domain range 01

069

)DQRXW

$

P$

P$

P$

P$

$P $P )LHOG

+UPV

$P$P $P

:RUNLQJGRPDLQZKHQ

5DQJHLVVHOHFWHG

069

)DQRXW

$

P$

P$

P$

P$

$P $P )LHOG

+UPV

$P$P $P

:RUNLQJGRPDLQZKHQ

5DQJHLVVHOHFWHG

RF electrical parameters M24LR64E-R

130/144 DocID022712 Rev 12

Figure 86. Energy harvesting: working domain range 00

069

)DQRXW

$

P$

P$

P$

P$

$P $P )LHOG

+UPV

$P$P $P

:RUNLQJGRPDLQZKHQ

5DQJHLVVHOHFWHG

DocID022712 Rev 12 131/144

M24LR64E-R Package information

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

31.1 SO8N package information

Figure 87. SO8N – 8-lead plastic small outline, 150 mils body width, package outline

1. Drawing is not to scale.

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

package mechanical data

Symbol

millimeters inches(1)

Min. Typ. Max. Min. Typ. Max.

A - - 1.750 - - 0.0689

A1 0.100 - 0.250 0.0039 - 0.0098

A2 1.250 - - 0.0492 - -

b 0.280 - 0.480 0.0110 - 0.0189

c 0.170 - 0.230 0.0067 - 0.0091

D 4.800 4.900 5.000 0.1890 0.1929 0.1969

E 5.800 6.000 6.200 0.2283 0.2362 0.2441

E1 3.800 3.900 4.000 0.1496 0.1535 0.1575

e - 1.270 - - 0.0500 -

h 0.250 - 0.500 0.0098 - 0.0197

k 0° - 8° 0° - 8°

L 0.400 - 1.270 0.0157 - 0.0500

62$B9

%



CCC



HX

!

PP

!

*$8*(3/$1(

,

Package information M24LR64E-R

132/144 DocID022712 Rev 12

Figure 88. SO8N – 8-lead plastic small outline, 150 mils body width,

package recommended footprint

1. Dimensions are expressed in millimeters.

L1 - 1.040 - - 0.0409 -

ccc - - 0.100 - - 0.0039

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

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

package mechanical data (continued)

Symbol

millimeters inches(1)

Min. Typ. Max. Min. Typ. Max.

2B621B)3B9



[





DocID022712 Rev 12 133/144

M24LR64E-R Package information

31.2 UFDFN8 package information

Figure 89. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch

dual flat package outline

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 (E2 by D2 in the above illustration) is internally pulled to VSS. It must not be connected to

any other voltage or signal line on the PCB, for example during the soldering process.

Table 129. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch

dual flat package mechanical data

Symbol

millimeters inches(1)

Min Typ Max Min Typ Max

A 0.450 0.550 0.600 0.0177 0.0217 0.0236

A1 0.000 0.020 0.050 0.0000 0.0008 0.0020

b(2) 0.200 0.250 0.300 0.0079 0.0098 0.0118

D 1.900 2.000 2.100 0.0748 0.0787 0.0827

D2 1.200 - 1.600 0.0472 - 0.0630

E 2.900 3.000 3.100 0.1142 0.1181 0.1220

=:EB0(B9

7RSYLHZ

3LQ

,'PDUNLQJ

6LGHYLHZ

6HDWLQJSODQH

HHH

FFF





(

DDD

$

$

[

'DWXP$

7HUPLQDOWLS

'HWDLO³$´

(YHQWHUPLQDO

/

//

H

3LQ

,'PDUNLQJ

%RWWRPYLHZ 6HH'HWDLO³$´



1'[

'

/

/

(

Package information M24LR64E-R

134/144 DocID022712 Rev 12

31.3 TSSOP8 package information

Figure 90.TSSOP8 – 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch,

package outline

1. Drawing is not to scale.

E2 1.200 - 1.600 0.0472 - 0.0630

e - 0.500 - 0.0197

K 0.300 - - 0.0118 - -

L 0.300 - 0.500 0.0118 - 0.0197

L1 - - 0.150 - - 0.0059

L3 0.300 - - 0.0118 - -

aaa - - 0.150 - - 0.0059

bbb - - 0.100 - - 0.0039

ccc - - 0.100 - - 0.0039

ddd - - 0.050 - - 0.0020

eee(3) - - 0.080 - - 0.0031

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

2. Dimension b applies to plated terminal and is measured between 0.15 and 0.30 mm from the

terminal tip.

3. Applied for exposed die paddle and terminals. Exclude embedding part of exposed die paddle

from measuring.

Table 129. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch

dual flat package mechanical data (continued)

Symbol

millimeters inches(1)

Min Typ Max Min Typ Max

76623$0B9

W





>ϭ

ϭ

Ϯ



ϴϱ

ϭ

DocID022712 Rev 12 135/144

M24LR64E-R Package information

Table 130. TSSOP8 – 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch,

package mechanical data

Symbol

millimeters inches(1)

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

Min. Typ. Max. Min. Typ. Max.

A - - 1.200 - - 0.0472

A1 0.050 - 0.150 0.0020 - 0.0059

A2 0.800 1.000 1.050 0.0315 0.0394 0.0413

b 0.190 - 0.300 0.0075 - 0.0118

c 0.090 - 0.200 0.0035 - 0.0079

CP - - 0.100 - - 0.0039

D 2.900 3.000 3.100 0.1142 0.1181 0.1220

e - 0.650 - - 0.0256 -

E 6.200 6.400 6.600 0.2441 0.2520 0.2598

E1 4.300 4.400 4.500 0.1693 0.1732 0.1772

L 0.450 0.600 0.750 0.0177 0.0236 0.0295

L1 - 1.000 - - 0.0394 -

α0° - 8° 0° - 8°

Part numbering M24LR64E-R

136/144 DocID022712 Rev 12

32 Part numbering

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.

Table 131. Ordering information scheme for packaged devices

Example: M24LR64E-R MN 6 T /2

Device type

M24LR = dynamic NFC/RFID tag IC

64 = memory size in Kbit

E = support for energy harvesting

Operating voltage(1)

1. For packaged devices only.

R = VCC = 1.8 to 5.5 V

Package

MN = SO8N (150 mils width)

MC = UFDFPN8 (MLP8)

DW = TSSOP8

SB12I = 120 µm ± 15 µmbumped and sawn

inkless wafer on 8-inch frame(2)

2. Delivery type: wafer tested. Bad chip identification by STIF wafer maps available on

STMicroelectronics inkless central transfer server.

RUW20 = 725 µm ± 25 µmunsawn inkless

8-inch wafer(2)

Device grade(1)

6 = industrial: device tested with standard

test flow over –40 to 85 °C

Option(1)

T = Tape and reel packing

Capacitance(1)

/2 = 27.5 pF

DocID022712 Rev 12 137/144

M24LR64E-R Part numbering

Table 132. Ordering and marking information

Reference Package Ordering code

First line marking

Initial revision

(0xF)

Actual revision

(0xE and below)

M24LR64E-R

TSSOP08 M24LR64E-RDW6T/2 464EU 4FEUB

MLP M24LR64E-RMC6T/2 464E 4FEB

SO8N M24LR64E-RMN6T/2 24L64ER 24LFERB

SB12I M24LR64E-SB12I/2 - -

RUW20 M24LR64E-RUW20/2 - -

Anticollision algorithm (informative) M24LR64E-R

138/144 DocID022712 Rev 12

Appendix A Anticollision algorithm (informative)

The following pseudocode describes how anticollision could be implemented on the VCD,

using recursivity.

A.1 Algorithm for pulsed slots

function push (mask, address); pushes on private stack

function pop (mask, address); pops from private stack

function pulse_next_pause; generates a power pulse

function store(M24LR64E-R_UID); stores M24LR64E-R_UID

function poll_loop (sub_address_size as integer)

pop (mask, address)

mask = address & mask; generates new mask

; send the request

mode = anticollision

send_Request (Request_cmd, mode, mask length, mask value)

for sub_address = 0 to (2^sub_address_size - 1)

pulse_next_pause

if no_collision_is_detected ; M24LR64E-R is inventoried

then

store (M24LR64E-R_UID)

else ; remember a collision was detected

push(mask,address)

endif

next sub_address

if stack_not_empty ; if some collisions have been detected and

then ; not yet processed, the function calls itself

poll_loop (sub_address_size); recursively to process the last

stored collision

endif

end poll_loop

main_cycle:

mask = null

address = null

push (mask, address)

poll_loop(sub_address_size)

end_main_cycle

DocID022712 Rev 12 139/144

M24LR64E-R CRC (informative)

Appendix B CRC (informative)

B.1 CRC error detection method

The cyclic redundancy check (CRC) is calculated on all data contained in a message, from

the start of the flags through to the end of Data. The CRC is used from VCD to M24LR64E-

R and from M24LR64E-R to VCD.

To add extra protection against shifting errors, a further transformation on the calculated

CRC is made. The one’s complement of the calculated CRC is the value attached to the

message for transmission.

To check received messages, the two CRC bytes are often also included in the re-

calculation, for ease of use. In this case, the expected value for the generated CRC is the

residue F0B8h.

B.2 CRC calculation example

This example in C language illustrates one method of calculating the CRC on a given set of

bytes comprising a message.

C-example to calculate or check the CRC16 according to ISO/IEC 13239

#define POLYNOMIAL0x8408// x^16 + x^12 + x^5 + 1

#define PRESET_VALUE0xFFFF

#define CHECK_VALUE0xF0B8

#define NUMBER_OF_BYTES4// Example: 4 data bytes

#define CALC_CRC1

#define CHECK_CRC0

void main()

{

unsigned int current_crc_value;

unsigned char array_of_databytes[NUMBER_OF_BYTES + 2] = {1, 2, 3, 4, 0x91,

0x39};

int number_of_databytes = NUMBER_OF_BYTES;

int calculate_or_check_crc;

int i, j;

calculate_or_check_crc = CALC_CRC;

// calculate_or_check_crc = CHECK_CRC;// This could be an other example

if (calculate_or_check_crc == CALC_CRC)

{

number_of_databytes = NUMBER_OF_BYTES;

Table 133. CRC definition

CRC type Length Polynomial Direction Preset Residue

ISO/IEC 13239 16 bits X16 + X12 + X5 + 1 = 8408h Backward FFFFh F0B8h

CRC (informative) M24LR64E-R

140/144 DocID022712 Rev 12

}

else // check CRC

{

number_of_databytes = NUMBER_OF_BYTES + 2;

}

current_crc_value = PRESET_VALUE;

for (i = 0; i < number_of_databytes; i++)

{

current_crc_value = current_crc_value ^ ((unsigned

int)array_of_databytes[i]);

for (j = 0; j < 8; j++)

{

if (current_crc_value & 0x0001)

{

current_crc_value = (current_crc_value >> 1) ^ POLYNOMIAL;

}

else

{

current_crc_value = (current_crc_value >> 1);

}

if (calculate_or_check_crc == CALC_CRC)

{

current_crc_value = ~current_crc_value;

printf ("Generated CRC is 0x%04X\n", current_crc_value);

// current_crc_value is now ready to be appended to the data stream

// (first LSByte, then MSByte)

}

else // check CRC

{

if (current_crc_value == CHECK_VALUE)

{

printf ("Checked CRC is ok (0x%04X)\n", current_crc_value);

}

else

{

printf ("Checked CRC is NOT ok (0x%04X)\n", current_crc_value);

}

DocID022712 Rev 12 141/144

M24LR64E-R Application family identifier (AFI) (informative)

Appendix C Application family identifier (AFI)

(informative)

The AFI (application family identifier) represents the type of application targeted by the VCD

and is used to extract from all the M24LR64E-Rs present only the one meeting the required

application criteria.

It is programmed by the M24LR64E-R issuer (the purchaser of the M24LR64E-R). Once

locked, it cannot be modified.

The most significant nibble of the AFI is used to code one specific or all application families,

as defined in Table 134.

The least significant nibble of the AFI is used to code one specific or all application

subfamilies. Subfamily codes different from 0 are proprietary.

Table 134. AFI coding(1)

1. X = '1' to 'F', Y = '1' to 'F'

AFI most

significant

nibble

AFI least

significant

nibble

Meaning VICCs respond from Examples / Note

‘0’ ‘0’ All families and subfamilies No applicative preselection

‘X’ '0 All subfamilies of family X Wide applicative preselection

'X '‘Y’ Only the Yth subfamily of family X -

‘0’ ‘Y’ Proprietary subfamily Y only -

‘1 '‘0’, ‘Y’ Transport Mass transit, bus, airline,...

'2 '‘0’, ‘Y’ Financial IEP, banking, retail,...

'3 '‘0’, ‘Y’ Identification Access control,...

'4 '‘0’, ‘Y’ Telecommunication Public telephony, GSM,...

‘5’ ‘0’, ‘Y’ Medical -

'6 '‘0’, ‘Y’ Multimedia Internet services....

'7 '‘0’, ‘Y’ Gaming -

8 '‘0’, ‘Y’ Data Storage Portable files,...

'9 '‘0’, ‘Y’ Item management -

'A '‘0’, ‘Y’ Express parcels -

'B '‘0’, ‘Y’ Postal services -

'C '‘0’, ‘Y’ Airline bags -

'D '‘0’, ‘Y’ RFU -

'E '‘0’, ‘Y’ RFU -

‘F’ ‘0’, ‘Y’ RFU -

Revision history M24LR64E-R
142/144 DocID022712 Rev 12
Revision history
          Table 135. Document revision history
Date Revision Changes
12-Apr-2012 1 Initial release.
08-Jun-2012 2
Updated Section 7.1: RF communication and energy harvesting on 
page 42 and Figure 49: M24LR64E-R state transition diagram on 
page 65.
Updated clock pulse width values in Table 123: I2C AC characteristics on 
page 122.
19-Jun-2012 3 Updated notes for Figure 49: M24LR64E-R state transition diagram.
21-Feb-2013 4
– Number of sectors updated in Section 3.
– Updated Section 4.2.
– Updated Figure 6: Memory sector organization. 
– M24LR64E changed into M24LR64x in Figure 52: M24LR64E RF-Busy 
management following Inventory command, Figure 56: M24LR64E RF-
Busy management following Write command and Figure 57: 
M24LR64E RF-Wip management following Write command.
– Updated Table 15: Control register, Table 17: System parameter 
sector, Table 118: Absolute maximum ratings, Table 12 2: I2C DC 
characteristics and Table 125: RF characteristics.
07-Mar-2013 5 Added Table 132: Ordering and marking information.
12-Jun-2013 6
Added “Dynamic NFC/RFID tag IC” to the title, Section 1: Description,
and the M24LR definition in Table 131: Ordering information scheme for 
packaged devices.
Updated VESD and Note 5 in Table 118: Absolute maximum ratings.
Removed MB package from Figure 88: UFDFPN8 (MLP8) – 8-lead ultra 
thin fine pitch dual flat package no lead 2 × 3mm, package outline.
21-Nov-2014 7
Updated Figure 1: Logic diagram, Figure 14: 100% modulation waveform 
and Figure 15: 10% modulation waveform.
Updated footnote 4 in Table 123: I2C AC characteristics.
Added note on Engineering samples marking in Section 32: Part 
numbering.
06-Nov-2015 8
Updated figure on Cover page with new wafer code SB12I.
Updated Figure 10: Write cycle polling flowchart using Ack, Figure 14: 
100% modulation waveform and Figure 15: 10% modulation waveform.
Updated Table 118: Absolute maximum ratings and its footnote 4.
Updated Section 31: Package information and its subsections.
Updated Table 131: Ordering information scheme for packaged devices 
and added footnotes 1 and 2.
27-Apr-2016 9 Updated Table 132: Ordering and marking information.
09-May-2016 10
Updated Features.
Updated Figure 51: Description of a possible anticollision sequence and 
Figure 53: Stay Quiet frame exchange between VCD and M24LR64E-R.
Updated Table 118: Absolute maximum ratings.
Added Section 29: Write cycle definition.

DocID022712 Rev 12 143/144

M24LR64E-R Revision history

13-Mar-2017 11

Updated image on cover page with introduction of RUW20 wafer option.

Updated Features.

Added footnote 4 to Figure 89: UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch

ultra thin profile fine pitch dual flat package outline.

Updated Table 131: Ordering information scheme for packaged devices

and Table 132: Ordering and marking information.

20-Jul-2017 12

Updated caption of Figure 90: TSSOP8 – 8-lead thin shrink small outline,

3 x 6.4 mm, 0.65 mm pitch, package outline and of Table 130: TSSOP8 –

8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch, package

mechanical data.

Table 135. Document revision history (continued)

Date Revision Changes

M24LR64E-R

144/144 DocID022712 Rev 12

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.

Mouser Electronics

Authorized Distributor

Click to View Pricing, Inventory, Delivery & Lifecycle Information:

STMicroelectronics:

M24LR64E-RDW6T/2 M24LR64E-RMN6T/2 M24LR64E-RMC6T/2