STMICROELECTRONICS LRIS64K

LRIS64K
64 Kbit EEPROM tag IC at 13.56 MHz with 64-bit UID and
password based on ISO/IEC 15693 and ISO/IEC 18000-3 Mode 1
Features
■
Based on ISO/IEC 15693 and
ISO/IEC 18000-3 mode 1 standards
■
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 capacitor (27.5 pF)
■
More than 1 million write cycles
■
More than 40-year data retention
■
64 Kbit EEPROM organized into 2048 blocks of
32 bits
■
64-bit unique identifier (UID)
■
Multipassword protection
■
Read Block & Write (32-bit blocks)
■
Write time: 5.75 ms including the internal verify
October 2011
Wafer (SBN18)
Doc ID 15336 Rev 11
1/100
www.st.com
1
Contents
LRIS64K
Contents
1
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2
User memory organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3
System memory area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1
LRIS64K RF block security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2
Example of the LRIS64K security protection . . . . . . . . . . . . . . . . . . . . . . 17
4
Initial delivery state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.1
Initial dialogue for vicinity cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.1
Power transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.2
Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.3
Operating field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6
Communication signal from VCD to LRIS64K . . . . . . . . . . . . . . . . . . . 21
7
Data rate and data coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8
9
7.1
Data coding mode: 1 out of 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.2
Data coding mode: 1 out of 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.3
VCD to LRIS64K frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.4
Start of frame (SOF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Communications signal from LRIS64K to VCD . . . . . . . . . . . . . . . . . . 27
8.1
Load modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
8.2
Subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
8.3
Data rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Bit representation and coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.1
9.2
2/100
Bit coding using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.1.1
High data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.1.2
Low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Bit coding using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Doc ID 15336 Rev 11
LRIS64K
10
Contents
9.3
High data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.4
Low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
LRIS64K to VCD frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.1
SOF when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.2
High data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.3
Low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10.4
SOF when using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.5
High data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.6
Low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.7
EOF when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.8
High data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.9
Low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.10 EOF when using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
10.11 High data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
10.12 Low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
11
Unique identifier (UID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
12
Application family identifier (AFI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
13
Data storage format identifier (DSFID) . . . . . . . . . . . . . . . . . . . . . . . . . 37
13.1
CRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
14
LRIS64K protocol description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
15
LRIS64K states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
16
15.1
Power-off state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
15.2
Ready state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
15.3
Quiet state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
15.4
Selected state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16.1
Addressed mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16.2
Non-addressed mode (general request) . . . . . . . . . . . . . . . . . . . . . . . . . 42
Doc ID 15336 Rev 11
3/100
Contents
LRIS64K
16.3
17
Request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
17.1
18
19
Select mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Request flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
18.1
Response flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
18.2
Response error code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Anticollision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
19.1
Request parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
20
Request processing by the LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
21
Explanation of the possible cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
22
Inventory Initiated command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
23
Timing definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
24
23.1
t1: LRIS64K response delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
23.2
t2: VCD new request delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
23.3
t3: VCD new request delay in the absence of a response from
the LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Commands codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
24.1
Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
24.2
Stay Quiet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
24.3
Read Single Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
24.4
Write Single Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
24.5
Read Multiple Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
24.6
Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
24.7
Reset to Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
24.8
Write AFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
24.9
Lock AFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
24.10 Write DSFID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
24.11 Lock DSFID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4/100
Doc ID 15336 Rev 11
LRIS64K
Contents
24.12 Get System Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
24.13 Get Multiple Block Security Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
24.14 Write-sector Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
24.15 Lock-sector Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
24.16 Present-sector Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
24.17 Fast Read Single Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
24.18 Fast Inventory Initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
24.19 Fast Initiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
24.20 Fast Read Multiple Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
24.21 Inventory Initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
24.22 Initiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
25
Maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
26
RF DC and AC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
27
Part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Appendix A Anticollision algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
A.1
Algorithm for pulsed slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Appendix B CRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
B.1
CRC error detection method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
B.2
CRC calculation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Appendix C Application family identifier (AFI). . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Doc ID 15336 Rev 11
5/100
List of tables
LRIS64K
List of tables
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
Table 9.
Table 10.
Table 11.
Table 12.
Table 13.
Table 14.
Table 15.
Table 16.
Table 17.
Table 18.
Table 19.
Table 20.
Table 21.
Table 22.
Table 23.
Table 24.
Table 25.
Table 26.
Table 27.
Table 28.
Table 29.
Table 30.
Table 31.
Table 32.
Table 33.
Table 34.
Table 35.
Table 36.
Table 37.
Table 38.
Table 39.
Table 40.
Table 41.
Table 42.
Table 43.
Table 44.
Table 45.
Table 46.
Table 47.
Table 48.
6/100
Signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Sector details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Sector security status byte area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Sector security status byte organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Read / Write protection bit setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Password Control bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Password system area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Sector security protection after power-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Sector security protection after a valid presentation of password 1 . . . . . . . . . . . . . . . . . . 17
10% modulation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Response data rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
UID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
CRC transmission rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
VCD request frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
LRIS64K Response frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
LRIS64K response depending on Request_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
General request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Definition of request flags 1 to 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Request flags 5 to 8 when Bit 3 = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Request flags 5 to 8 when Bit 3 = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
General response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Definitions of response flags 1 to 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Response error code definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Inventory request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Example of the addition of 0-bits to an 11-bit mask value . . . . . . . . . . . . . . . . . . . . . . . . . 47
Timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Command codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Inventory request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Inventory response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Stay Quiet request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Read Single Block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Read Single Block response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . 57
Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Read Single Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . 57
Write Single Block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Write Single Block response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . 59
Write Single Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . 59
Read Multiple Block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Read Multiple Block response format when Error_flag is NOT set. . . . . . . . . . . . . . . . . . . 61
Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Read Multiple Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . 62
Select request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Select Block response format when Error_flag is NOT set. . . . . . . . . . . . . . . . . . . . . . . . . 63
Select response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Reset to Ready request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Reset to Ready response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . 64
Reset to ready response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Write AFI request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Doc ID 15336 Rev 11
LRIS64K
Table 49.
Table 50.
Table 51.
Table 52.
Table 53.
Table 54.
Table 55.
Table 56.
Table 57.
Table 58.
Table 59.
Table 60.
Table 61.
Table 62.
Table 63.
Table 64.
Table 65.
Table 66.
Table 67.
Table 68.
Table 69.
Table 70.
Table 71.
Table 72.
Table 73.
Table 74.
Table 75.
Table 76.
Table 77.
Table 78.
Table 79.
Table 80.
Table 81.
Table 82.
Table 83.
Table 84.
Table 85.
Table 86.
Table 87.
Table 88.
Table 89.
Table 90.
Table 91.
Table 92.
Table 93.
Table 94.
Table 95.
Table 96.
Table 97.
Table 98.
Table 99.
Table 100.
List of tables
Write AFI response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Write AFI response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Lock AFI request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Lock AFI response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Lock AFI response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Write DSFID request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Write DSFID response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . 69
Write DSFID response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Lock DSFID request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Lock DSFID response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . . 71
Lock DSFID response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Get System Info request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Get System Info response format when Error_flag is NOT set. . . . . . . . . . . . . . . . . . . . . . 73
Get System Info response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Get Multiple Block Security Status request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Get Multiple Block Security Status response format when Error_flag is NOT set . . . . . . . 75
Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Get Multiple Block Security Status response format when Error_flag is set . . . . . . . . . . . . 76
Write-sector Password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Write-sector Password response format when Error_flag is NOT set . . . . . . . . . . . . . . . . 77
Write-sector Password response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . 77
Lock-sector Password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Lock-sector Password response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . 79
Lock-sector Password response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . 79
Present-sector Password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Present-sector Password response format when Error_flag is NOT set . . . . . . . . . . . . . . 81
Present-sector Password response format when Error_flag is set . . . . . . . . . . . . . . . . . . . 81
Fast Read Single Block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Fast Read Single Block response format when Error_flag is NOT set . . . . . . . . . . . . . . . . 83
Sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Fast Read Single Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . 83
Fast Inventory Initiated request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Fast Inventory Initiated response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Fast Initiate request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Fast Initiate response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Fast Read Multiple Block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Fast Read Multiple Block response format when Error_flag is NOT set. . . . . . . . . . . . . . . 87
Sector security status if Option_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Fast Read Multiple Block response format when Error_flag is set . . . . . . . . . . . . . . . . . . . 88
Inventory Initiated request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Inventory Initiated response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Initiate request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Initiate Initiated response format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
RF AC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
RF DC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
CRC definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
AFI coding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Doc ID 15336 Rev 11
7/100
List of figures
LRIS64K
List of figures
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
Figure 11.
Figure 12.
Figure 13.
Figure 14.
Figure 15.
Figure 16.
Figure 17.
Figure 18.
Figure 19.
Figure 20.
Figure 21.
Figure 22.
Figure 23.
Figure 24.
Figure 25.
Figure 26.
Figure 27.
Figure 28.
Figure 29.
Figure 30.
Figure 31.
Figure 32.
Figure 33.
Figure 34.
Figure 35.
Figure 36.
Figure 37.
Figure 38.
Figure 39.
Figure 40.
Figure 41.
Figure 42.
Figure 43.
Figure 44.
Figure 45.
Figure 46.
Figure 47.
Figure 48.
8/100
Pad connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Memory sector organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
100% modulation waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10% modulation waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1 out of 256 coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Detail of a time period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1 out of 4 coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1 out of 4 coding example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
SOF to select 1 out of 256 data coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
SOF to select 1 out of 4 data coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
EOF for either data coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Logic 0, high data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Logic 0, high data rate, one subcarriers x2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Logic 1, high data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Logic 1, high data rate, one subcarriers x2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Logic 0, low data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Logic 0, low data rate, one subcarriers x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Logic 1, low data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Logic 1, low data rate, one subcarriers x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Logic 0, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Logic 1, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Logic 0, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Logic 1, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Start of frame, high data rate, one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Start of frame, high data rate, one subcarrier x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Start of frame, low data rate, one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Start of frame, low data rate, one subcarrier x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Start of frame, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Start of frame, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
End of frame, high data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
End of frame, high data rate, one subcarriers x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
End of frame, low data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
End of frame, low data rate, one subcarriers x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
End of frame, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
End of frame, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
LRIS64K decision tree for AFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
LRIS64K protocol timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
LRIS64K state transition diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Principle of comparison between the mask, the slot number and the UID . . . . . . . . . . . . . 48
Description of a possible anticollision sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Stay Quiet frame exchange between VCD and LRIS64K. . . . . . . . . . . . . . . . . . . . . . . . . . 56
Read Single Block frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . 58
Write Single Block frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . 60
Read Multiple Block frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . 62
Select frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Reset to Ready frame exchange between VCD and LRIS64K. . . . . . . . . . . . . . . . . . . . . . 64
Write AFI frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Lock AFI frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Doc ID 15336 Rev 11
LRIS64K
Figure 49.
Figure 50.
Figure 51.
Figure 52.
Figure 53.
Figure 54.
Figure 55.
Figure 56.
Figure 57.
Figure 58.
Figure 59.
Figure 60.
List of figures
Write DSFID frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . 70
Lock DSFID frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . 72
Get System Info frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . . . 74
Get Multiple Block Security Status frame exchange between VCD and LRIS64K . . . . . . . 76
Write-sector Password frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . 78
Lock-sector Password frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . 80
Present-sector Password frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . 82
Fast Read Single Block frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . 84
Fast Initiate frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . 86
Fast Read Multiple Block frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . 88
Initiate frame exchange between VCD and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
LRIS64K synchronous timing, transmit and receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Doc ID 15336 Rev 11
9/100
Description
1
LRIS64K
Description
The LRIS64K is a contactless memory powered by the received carrier electromagnetic
wave, which follows the ISO/IEC 15693 and ISO/IEC 18000-3 mode 1 recommendation for
radio-frequency power and signal interface. It is a 64 Kbit electrically erasable
programmable memory (EEPROM). The memory is organized as 64 sectors divided into 32
blocks of 32 bits.
The LRIS64K is accessed via the 13.56 MHz carrier electromagnetic wave, on which
incoming data are demodulated from the received signal amplitude modulation (ASK:
amplitude shift keying). The received ASK wave is 10% or 100% modulated with a data rate
of 1.6 Kbit/s using the 1/256 pulse coding mode, or a data rate of 26 Kbit/s using the 1/4
pulse coding mode. Outgoing data are generated by the LRIS64K load variation using
Manchester coding with one or two subcarrier frequencies at 423 kHz and 484 kHz. Data
are transferred from the LRIS64K at 6.6 Kbit/s in low data rate mode and 26 Kbit/s in high
data rate mode. The LRIS64K supports the 53 Kbit/s data rate in high data rate mode with a
single subcarrier frequency of 423 kHz.
The LRIS64K also features a unique 32-bit multi-password protection scheme.
Figure 1.
Pad connection
Power
Supply
Regulator
64 Kbit
EEPROM
memory
AC1
ASK
Demodulator
Manchester
Load
Modulator
AC0
AI15689
Table 1.
Signal names
Signal name
10/100
Function
Direction
AC0
Antenna coil
I/O
AC1
Antenna coil
I/O
Doc ID 15336 Rev 11
LRIS64K
2
User memory organization
User memory organization
The LRIS64K is divided into 64 sectors of 32 blocks of 32 bits as shown in Table 2. Figure 2
shows the memory sector organization. Each sector can be individually read- and/or writeprotected using a specific password command. Read and write operations are possible if
the addressed data are not in a protected sector.
The LRIS64K also has a 64-bit block that is used to store the 64-bit unique identifier (UID).
The UID is compliant with the ISO/IEC 15963 description, and its value is used during the
anticollision sequence (Inventory). This block is not accessible by the user and its value is
written by ST on the production line.
The LRIS64K 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 LRIS64K has three additional 32-bit blocks that store the RF password codes.
Figure 2.
Memory sector organization
3ECTOR !REA
3ECTORSECURITY
STATUS
+BIT%%02/-SECTOR
BITS
+BIT%%02/-SECTOR
BITS
+BIT%%02/-SECTOR
BITS
+BIT%%02/-SECTOR
BITS
+BIT%%02/-SECTOR
BITS
+BIT%%02/-SECTOR
BITS
+BIT%%02/-SECTOR
BITS
+BIT%%02/-SECTOR
BITS
2&0ASSWORD
3YSTEM
2&0ASSWORD
3YSTEM
2&0ASSWORD
3YSTEM
BIT$3&)$
3YSTEM
BIT!&)
3YSTEM
BIT5)$
3YSTEM
AI
Sector details
The LRIS64K user memory is divided into 64 sectors. Each sector contains 1024 bits. The
protection scheme is described in Section 3: System memory area.
A sector provides 32 blocks of 32 bits. Each read and write access are done by block. Read
and write block accesses are controlled by a Sector Security Status byte that defines the
access rights to all 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.
Doc ID 15336 Rev 11
11/100
User memory organization
Table 2.
Sector
number
LRIS64K
Sector details
RF block
address
Bits [31:24]
Bits [23:16]
Bits [15:8]
Bits [7:0]
0
user
user
user
user
1
user
user
user
user
2
user
user
user
user
3
user
user
user
user
4
user
user
user
user
5
user
user
user
user
6
user
user
user
user
7
user
user
user
user
8
user
user
user
user
9
user
user
user
user
10
user
user
user
user
11
user
user
user
user
12
user
user
user
user
13
user
user
user
user
14
user
user
user
user
15
user
user
user
user
16
user
user
user
user
17
user
user
user
user
18
user
user
user
user
19
user
user
user
user
20
user
user
user
user
21
user
user
user
user
22
user
user
user
user
23
user
user
user
user
24
user
user
user
user
25
user
user
user
user
26
user
user
user
user
27
user
user
user
user
28
user
user
user
user
29
user
user
user
user
30
user
user
user
user
31
user
user
user
user
0
12/100
Doc ID 15336 Rev 11
LRIS64K
User memory organization
Table 2.
Sector
number
1
...
Sector details (continued)
RF block
address
Bits [31:24]
Bits [23:16]
Bits [15:8]
Bits [7:0]
32
user
user
user
user
33
user
user
user
user
34
user
user
user
user
35
user
user
user
user
36
user
user
user
user
37
user
user
user
user
38
user
user
user
user
39
user
user
user
user
...
...
...
...
...
...
...
...
...
...
2016
user
user
user
user
2017
user
user
user
user
2018
user
user
user
user
2019
user
user
user
user
2020
user
user
user
user
2021
user
user
user
user
2022
user
user
user
user
2023
user
user
user
user
2024
user
user
user
user
2025
user
user
user
user
2026
user
user
user
user
2027
user
user
user
user
2028
user
user
user
user
2029
user
user
user
user
2030
user
user
user
user
2031
user
user
user
user
2032
user
user
user
user
2033
user
user
user
user
2034
user
user
user
user
2035
user
user
user
user
2036
user
user
user
user
2037
user
user
user
user
2038
user
user
user
user
2039
user
user
user
user
63
Doc ID 15336 Rev 11
13/100
User memory organization
Table 2.
LRIS64K
Sector details (continued)
Sector
number
RF block
address
Bits [31:24]
Bits [23:16]
Bits [15:8]
Bits [7:0]
2040
user
user
user
user
2041
user
user
user
user
2042
user
user
user
user
2043
user
user
user
user
2044
user
user
user
user
2045
user
user
user
user
2046
user
user
user
user
2047
user
user
user
user
63 continued
14/100
Doc ID 15336 Rev 11
LRIS64K
System memory area
3
System memory area
3.1
LRIS64K RF block security
The LRIS64K provides a special protection mechanism based on passwords. Each memory
sector of the LRIS64K 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 LRIS64K 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 4. Table 3 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 reset to 00h.
Table 3.
Sector security status byte area
RF address
Bits [31:24]
Bits [23:16]
Bits [15:8]
Bits [7:0]
0
SSS 3
SSS 2
SSS 1
SSS 0
128
SSS 7
SSS 6
SSS 5
SSS 4
256
SSS 11
SSS 10
SSS 9
SSS 8
384
SSS 15
SSS 14
SSS 13
SSS 12
512
SSS 19
SSS 18
SSS 17
SSS 16
640
SSS 23
SSS 22
SSS 21
SSS 20
768
SSS 27
SSS 26
SSS 25
SSS 24
896
SSS 31
SSS 30
SSS 29
SSS 28
1024
SSS 35
SSS 34
SSS 33
SSS 32
1152
SSS 39
SSS 38
SSS 37
SSS 36
1280
SSS 43
SSS 42
SSS 41
SSS 40
1408
SSS 47
SSS 46
SSS 45
SSS 44
1536
SSS 51
SSS 50
SSS 49
SSS 48
1664
SSS 55
SSS 54
SSS 53
SSS 52
1792
SSS 59
SSS 58
SSS 57
SSS 56
1920
SSS 63
SSS 62
SSS 61
SSS 60
Table 4.
Sector security status byte organization
b7
b6
b5
0
0
0
b4
b3
Password Control bits
Doc ID 15336 Rev 11
b2
b1
Read / Write protection
bits
b0
Sector
Lock
15/100
System memory area
LRIS64K
When the Sector Lock bit is set to ‘1’, for instance by issuing a Lock-sector Password
command, the 2 Read/Write protection bits (b1, b2) are used to set the Read/Write access of
the sector as described in Table 5.
Table 5.
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
The next 2 bits of the Sector security status byte (b3, b4) are the Password Control bits. The
value these two bits is used to link a password to the sector as defined in Table 6.
Table 6.
Password Control bits
b4, b3
Password
00
The sector is not protected by a Password
01
The sector is protected by the Password 1
10
The sector is protected by the Password 2
11
The sector is protected by the Password 3
The LRIS64K 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 7.
Table 7.
Add
Password system area
0
7 8
15
16
1
Password 1
2
Password 2
3
Password 3
23
24
31
The dedicated password commands 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 Password
The Lock-sector Password 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
16/100
Doc ID 15336 Rev 11
LRIS64K
System memory area
Lock-sector Password command. The Sector Lock bit, b0, is set to ‘1’ automatically.
After issuing a Lock-sector Password command, the protection settings of the selected
sector are activated. The protection of a locked block cannot be changed. A Locksector Password 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 LRIS64K in order to modify the access rights of all the memory sectors linked to
that password (Table 5) 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.
3.2
Example of the LRIS64K security protection
Table 8 and Table 9 show the sector security protections before and after a valid Presentsector Password command. Table 8 shows the sector access rights of an LRIS64K after
power-up. After a valid Present-sector Password command with password 1, the memory
sector access is changed as shown in Table 9.
Table 8.
Sector security protection after power-up
Sector security status byte
Sector
address
b7b6b5
b4
b3
b2
b1
b0
0
Protection: Standard
Read
No Write
xxx
0
0
0
0
1
1
Protection: Pswd 1
Read
No Write
xxx
0
1
0
0
1
2
Protection: Pswd 1
Read
Write
xxx
0
1
0
1
1
3
Protection: Pswd 1
No Read
No Write
xxx
0
1
1
0
1
4
Protection: Pswd 1
No Read
No Write
xxx
0
1
1
1
1
Table 9.
Sector security protection after a valid presentation of password 1
Sector security status byte
Sector
address
b7b6b5
b4 b3 b2 b1 b0
0
Protection: Standard
Read
No Write
xxx
0
0
0
0
1
1
Protection: Pswd 1
Read
Write
xxx
0
1
0
0
1
2
Protection: Pswd 1
Read
Write
xxx
0
1
0
1
1
3
Protection: Pswd 1
Read
Write
xxx
0
1
1
0
1
4
Protection: Pswd 1
Read
No Write
xxx
0
1
1
1
1
Doc ID 15336 Rev 11
17/100
Initial delivery state
4
LRIS64K
Initial delivery state
The device is delivered with the following factory settings:
●
All bits in the memory array are set to 1 (each byte contains FFh).
●
The default value of the SSS bytes is reset to 00h.
●
The three default password values are set to 0000 0000h and are activated.
System parameters are set to:
18/100
●
(E0 02 xx xx xx xx xx xx )h for UID
●
(03 07 FF)h for Memory Size
●
00h for AFI
●
00h for DSFID
Doc ID 15336 Rev 11
LRIS64K
5
Commands
Commands
The LRIS64K supports the following commands:
●
Inventory, used to perform the anticollision sequence.
●
Stay Quiet, used to put the LRIS64K in quiet mode, where it does not respond to any
inventory command.
●
Select, used to select the LRIS64K. After this command, the LRIS64K processes all
Read/Write commands with Select_flag set.
●
Reset To Ready, used to put the LRIS64K 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 Password, 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.
Doc ID 15336 Rev 11
19/100
Commands
5.1
LRIS64K
Initial dialogue for vicinity cards
The dialog between the vicinity coupling device (VCD) and the vicinity integrated circuit
Card or VICC (LRIS64K) takes place as follows:
●
activation of the LRIS64K by the RF operating field of the VCD.
●
transmission of a command by the VCD.
●
transmission of a response by the LRIS64K.
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 Talk First).
5.1.1
Power transfer
Power is transferred to the LRIS64K by radio frequency at 13.56 MHz via coupling antennas
in the LRIS64K and the VCD. The RF operating field of the VCD is transformed on the
LRIS64K antenna to an AC Voltage which is rectified, filtered and internally regulated. The
amplitude modulation (ASK) on this received signal is demodulated by the ASK
demodulator.
5.1.2
Frequency
The ISO/IEC 15693 standard defines the carrier frequency (fC) of the operating field as
13.56 MHz ±7 kHz.
5.1.3
Operating field
The LRIS64K operates continuously between Hmin and Hmax.
●
The minimum operating field is Hmin and has a value of 150 mA/m rms.
●
The maximum operating field is Hmax and has a value of 5 A/m rms.
A VCD shall generate a field of at least Hmin and not exceeding Hmax in the operating
volume.
20/100
Doc ID 15336 Rev 11
LRIS64K
6
Communication signal from VCD to LRIS64K
Communication signal from VCD to LRIS64K
Communications between the VCD and the LRIS64K takes place using the modulation
principle of ASK (Amplitude Shift Keying). Two modulation indexes are used, 10% and
100%. The LRIS64K 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” will be created as described in
Figure 3 and Figure 4.
The LRIS64K is operational for any degree of modulation index from between 10% and
30%.
Figure 3.
100% modulation waveform
t1
t3
Carrier
Amplitude
t4
105%
a
95%
60%
t2
5%
t
b
t1
t2
t3
t4
Min (µs) Max (µs)
9,44
6,0
2,1
t1
0
4,5
0
0,8
The clock recovery shall be operational after t4 max.
ai15793
Table 10.
10% modulation parameters
Symbol
Parameter definition
Value
hr
0.1 x (a – b)
Max
hf
0.1 x (a – b)
Max
Doc ID 15336 Rev 11
21/100
Communication signal from VCD to LRIS64K
Figure 4.
LRIS64K
10% modulation waveform
Carrier
Amplitude
t1
t2
t3
y
hf
a
b
hr
y
t
t1
t2
t3
Min
6,0 µs
3,0 µs
0
Max
9,44 µs
t1
4,5 µs
Modulation
Index
10%
30%
y
hf, hr
0,05 (a-b)
0,1 (a-b) max
The VICC shall be operational for any value of modulation index between 10 % and 30 %.
ai15794
22/100
Doc ID 15336 Rev 11
LRIS64K
7
Data rate and data coding
Data rate and data coding
The data coding implemented in the LRIS64K uses pulse position modulation. Both data
coding modes that are described in the ISO/IEC15693 are supported by the LRIS64K. The
selection is made by the VCD and indicated to the LRIS64K within the start of frame (SOF).
7.1
Data coding mode: 1 out of 256
The value of one single byte is represented by the position of one pause. The position of the
pause on 1 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 5 illustrates this pulse position modulation technique. In this figure, data E1h (225
decimal) is sent by the VCD to the LRIS64K.
The pause occurs during the second half of the position of the time period that determines
the value, as shown in Figure 6.
A pause during the first period transmits the data value 00h. A pause during the last period
transmit the data value FFh (255 decimal).
Figure 5.
1 out of 256 coding mode
9.44 µs
Pulse
Modulated
Carrier
18.88 µs
0 1
2
3
. . . . . . . .
. . . . . . . . .
. . . . . . . . .
2
2
5
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
2
5
2
2
5
3
2
5
4
2
5
5
4.833 ms
AI06656
Doc ID 15336 Rev 11
23/100
Data rate and data coding
Figure 6.
LRIS64K
Detail of a time period
9.44 µs
18.88 µs
Pulse
Modulated
Carrier
.
.
.
.
.
.
.
.
2
2
4
2
2
5
.
.
.
.
.
2
2
6
Time Period
one of 256
7.2
.
AI06657
Data coding mode: 1 out of 4
The value of 2 bits is represented by the position of one pause. The position of the pause on
1 of 4 successive time periods of 18.88 µs (256/fC), determines the value of the 2 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 7 illustrates the 1 out of 4 pulse position technique and coding.
Figure 8 shows the transmission of E1h (225d - 1110 0001b) by the VCD.
24/100
Doc ID 15336 Rev 11
LRIS64K
Data rate and data coding
Figure 7.
1 out of 4 coding mode
Pulse position for "00"
9.44 µs
9.44 µs
75.52 µs
Pulse position for "01" (1=LSB)
28.32 µs
9.44 µs
75.52 µs
Pulse position for "10" (0=LSB)
47.20µs
Pulse position for "11"
9.44 µs
75.52 µs
66.08 µs
9.44 µs
75.52 µs
AI06658
Figure 8.
1 out of 4 coding example
10
00
01
11
75.52µs
75.52µs
75.52µs
75.52µs
AI06659
Doc ID 15336 Rev 11
25/100
Data rate and data coding
7.3
LRIS64K
VCD to LRIS64K 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 LRIS64K is ready to receive a new command frame from the VCD 311.5 µs (t2) after
sending a response frame to the VCD.
The LRIS64K takes a power-up time of 0.1 ms after being activated by the powering field.
After this delay, the LRIS64K is ready to receive a command frame from the VCD.
7.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 9 selects the 1 out of 256 data coding mode. The
SOF sequence described in Figure 10 selects the 1 out of 4 data coding mode. The EOF
sequence for either coding mode is described in Figure 11.
Figure 9.
SOF to select 1 out of 256 data coding mode
9.44µs
9.44µs
37.76µs
37.76µs
AI06661
Figure 10. SOF to select 1 out of 4 data coding mode
9.44µs
9.44µs
9.44µs
37.76µs
37.76µs
AI06660
Figure 11. EOF for either data coding mode
9.44µs
9.44µs
37.76µs
AI06662
26/100
Doc ID 15336 Rev 11
LRIS64K
8
Communications signal from LRIS64K to VCD
Communications signal from LRIS64K to VCD
The LRIS64K has several modes defined for some parameters, owing to which it can
operate in different noise environments and meet different application requirements.
8.1
Load modulation
The LRIS64K is capable of communication 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 LRIS64K.
The load-modulated amplitude received on the VCD antenna must be of at least 10mV
when measured as described in the test methods defined in International Standard
ISO/IEC10373-7.
8.2
Subcarrier
The LRIS64K supports the one-subcarrier and two-subcarrier 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-subcarrier mode, the LRIS64K generates a
continuous phase relationship between fS1 and fS2.
8.3
Data rates
The LRIS64K 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. It also supports
the x2 mode available on all the Fast commands. Table 11 shows the different data rates
produced by the LRIS64K using the different response format combinations.
Table 11.
Response data rates
Data rate
One subcarrier
Two subcarriers
Standard commands
6.62 Kbit/s (fc/2048)
6.67 Kbit/s (fc/2032)
Fast commands
13.24 Kbit/s (fc/1024)
not applicable
Standard commands
26.48 Kbit/s (fc/512)
26.69 Kbit/s (fc/508)
Fast commands
52.97 Kbit/s (fc/256)
not applicable
Low
High
Doc ID 15336 Rev 11
27/100
Bit representation and coding
9
LRIS64K
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 will increase by this factor. For the Fast
commands using one subcarrier, all pulse numbers and times are divided by 2.
9.1
Bit coding using one subcarrier
9.1.1
High data rate
A logic 0 starts with 8 pulses at 423.75 kHz (fC/32) followed by an unmodulated time of
18.88 µs as shown in Figure 12.
Figure 12. Logic 0, high data rate, one subcarriers
37.76µs
ai12076
For the fast commands, a logic 0 starts with 4 pulses at 423.75 kHz (fC/32) followed by an
unmodulated time of 9.44 µs as shown in Figure 13.
Figure 13. Logic 0, high data rate, one subcarriers x2
18.88µs
ai12066
A logic 1 starts with an unmodulated time of 18.88 µs followed by 8 pulses at 423.75 kHz
(fC/32) as shown in Figure 14.
Figure 14. Logic 1, high data rate, one subcarriers
37.76µs
ai12077
For the Fast commands, a logic 1 starts with an unmodulated time of 9.44 µs followed by 4
pulses of 423.75 kHz (fC/32) as shown in Figure 15.
Figure 15. Logic 1, high data rate, one subcarriers x2
18.88µs
ai12067
28/100
Doc ID 15336 Rev 11
LRIS64K
9.1.2
Bit representation and coding
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 16.
Figure 16. Logic 0, low data rate, one subcarriers
151.04µs
ai12068
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 17.
Figure 17. Logic 0, low data rate, one subcarriers x2
75.52µs
ai12069
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 18.
Figure 18. Logic 1, low data rate, one subcarriers
151.04µs
ai12070
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 18.
Figure 19. Logic 1, low data rate, one subcarriers x2
75.52µs
Doc ID 15336 Rev 11
ai12071
29/100
Bit representation and coding
LRIS64K
9.2
Bit coding using two subcarriers
9.3
High data rate
A logic 0 starts with 8 pulses at 423.75 kHz (fC/32) followed by 9 pulses at 484.28 kHz
(fC/28) as shown in Figure 20. For the Fast commands, the x2 mode is not available.
Figure 20. Logic 0, high data rate, two subcarriers
37.46µs
ai12074
A logic 1 starts with 9 pulses at 484.28 kHz (fC/28) followed by 8 pulses at 423.75 kHz
(fC/32) as shown in Figure 21. For the Fast commands, the x2 mode is not available.
Figure 21. Logic 1, high data rate, two subcarriers
37.46µs
9.4
ai12073
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 22. For the Fast commands, the x2 mode is not available.
Figure 22. Logic 0, low data rate, two subcarriers
149.84µs
ai12072
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 23. For the Fast commands, the x2 mode is not available.
Figure 23. Logic 1, low data rate, two subcarriers
149.84µs
30/100
Doc ID 15336 Rev 11
ai12075
LRIS64K
10
LRIS64K to VCD frames
LRIS64K 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.
10.1
SOF when using one subcarrier
10.2
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 8 pulses
at 423.75 kHz as shown in Figure 24.
Figure 24. Start of frame, high data rate, one subcarrier
37.76µs
113.28µs
ai12078
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 4 pulses at 423.75 kHz as shown in Figure 25.
Figure 25. Start of frame, high data rate, one subcarrier x2
56.64µs
18.88µs
ai12079
10.3
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 26.
Figure 26. Start of frame, low data rate, one subcarrier
453.12µs
151.04µs
ai12080
Doc ID 15336 Rev 11
31/100
LRIS64K to VCD frames
LRIS64K
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 27.
Figure 27. Start of frame, low data rate, one subcarrier x2
226.56µs
75.52µs
ai12081
10.4
SOF when using two subcarriers
10.5
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 9 pulses at 484.28 kHz followed by 8 pulses at
423.75 kHz as shown in Figure 28.
For the Fast commands, the x2 mode is not available.
Figure 28. Start of frame, high data rate, two subcarriers
112.39µs
10.6
37.46µs
ai12082
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 29.
For the Fast commands, the x2 mode is not available.
Figure 29. Start of frame, low data rate, two subcarriers
449.56µs
149.84µs
ai12083
32/100
Doc ID 15336 Rev 11
LRIS64K
LRIS64K to VCD frames
10.7
EOF when using one subcarrier
10.8
High data rate
The EOF comprises a logic 0 that includes 8 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 30.
Figure 30. End of frame, high data rate, one subcarriers
37.76µs
113.28µs
ai12084
For the Fast commands, the EOF comprises a logic 0 that includes 4 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 31.
Figure 31. End of frame, high data rate, one subcarriers x2
18.88µs
56.64µs
ai12085
10.9
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 32.
Figure 32. End of frame, low data rate, one subcarriers
453.12µs
151.04µs
ai12086
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 33.
Figure 33. End of frame, low data rate, one subcarriers x2
75.52µs
226.56µs
ai12087
Doc ID 15336 Rev 11
33/100
LRIS64K to VCD frames
LRIS64K
10.10
EOF when using two subcarriers
10.11
High data rate
The EOF comprises a logic 0 that includes 8 pulses at 423.75 kHz and 9 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 34.
For the Fast commands, the x2 mode is not available.
Figure 34. End of frame, high data rate, two subcarriers
37.46µs
10.12
112.39µs
ai12088
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 35.
For the Fast commands, the x2 mode is not available.
Figure 35. End of frame, low data rate, two subcarriers
149.84µs
449.56µs
ai12089
34/100
Doc ID 15336 Rev 11
LRIS64K
11
Unique identifier (UID)
Unique identifier (UID)
The LRIS64K 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:
●
8 MSBs with a value of E0h
●
The IC Manufacturer code of ST 02h, on 8 bits (ISO/IEC 7816-6/AM1)
●
a Unique Serial Number on 48 bits
Table 12.
UID format
MSB
63
LSB
56 55
0xE0
48
47
0x02
0
Unique serial number
With the UID each LRIS64K can be addressed uniquely and individually during the
anticollision loop and for one-to-one exchanges between a VCD and an LRIS64K.
Doc ID 15336 Rev 11
35/100
Application family identifier (AFI)
12
LRIS64K
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 LRIS64Ks present, only the LRIS64Ks that meet the
required application criteria.
Figure 36. LRIS64K decision tree for AFI
)NVENTORYREQUEST
RECEIVED
.O
!&)FLAG
SET
9ES
!&)VALUE
.O
9ES
!&)VALUE
)NTERNAL
VALUE
.O
9ES
!NSWERGIVENBYTHE,2)3+
TOTHE)NVENTORYREQUEST
.OANSWER
!)
The AFI is programmed by the LRIS64K 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 ISO/IEC 15693-3 documentation)
36/100
Doc ID 15336 Rev 11
LRIS64K
13
Data storage format identifier (DSFID)
Data storage format identifier (DSFID)
The data storage format identifier indicates how the data is structured in the LRIS64K
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.
13.1
CRC
The CRC used in the LRIS64K is calculated as per the definition in ISO/IEC 13239. The
initial register contents are all ones: “FFFF”.
The two-byte CRC are 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 LRIS64K verifies that the CRC value is valid.
If it is invalid, the LRIS64K discards the frame and does not answer to the VCD.
Upon reception of a Response from the LRIS64K, 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
discretion of the VCD designer.
The CRC is transmitted least significant byte first. Each byte is transmitted least significant
bit first.
Table 13.
CRC transmission rules
LSByte
MSByte
LSBit
MSBit
LSBit
CRC 16 (8 bits)
Doc ID 15336 Rev 11
MSBit
CRC 16 (8 bits)
37/100
LRIS64K protocol description
14
LRIS64K
LRIS64K protocol description
The transmission protocol (or simply protocol) defines the mechanism used to exchange
instructions and data between the VCD and the LRIS64K, in both directions. It is based on
the concept of “VCD talks first”.
This means that an LRIS64K will 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 LRIS64K
●
a response from the LRIS64K to the VCD
Each request and each response are contained in a frame. The frame delimiters (SOF,
EOF) are described in Section 10: LRIS64K to VCD frames.
Each request consists of:
●
a request SOF (see Figure 9 and Figure 10)
●
flags
●
a command code
●
parameters, depending on the command
●
application data
●
a 2-byte CRC
●
a request EOF (see Figure 11)
Each response consists of:
●
an answer SOF (see Figure 24 to Figure 29)
●
flags
●
parameters, depending on the command
●
application data
●
a 2-byte CRC
●
an answer EOF (see Figure 30 to Figure 35)
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, 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 14.
VCD request frame format
Request SOF Request_flags
Table 15.
Response
SOF
38/100
Command
code
Parameters
Data
2-byte CRC
Request
EOF
LRIS64K Response frame format
Response_flags
Parameters
Doc ID 15336 Rev 11
Data
2-byte CRC
Response
EOF
LRIS64K
LRIS64K protocol description
Figure 37. LRIS64K protocol timing
VCD
Request
frame
(Table 14)
Request
frame
(Table 14)
Timing
Response
frame
(Table 15)
Response
frame
(Table 15)
LRIS64K
<-t1->
<-t2->
Doc ID 15336 Rev 11
<-t1->
<-t2->
39/100
LRIS64K states
15
LRIS64K
LRIS64K states
An LRIS64K can be in one of 4 states:
●
Power-off
●
Ready
●
Quiet
●
Selected
Transitions between these states are specified in Figure 38: LRIS64K state transition
diagram and Table 16: LRIS64K response depending on Request_flags.
15.1
Power-off state
The LRIS64K is in the Power-off state when it does not receive enough energy from the
VCD.
15.2
Ready state
The LRIS64K is in the Ready state when it receives enough energy from the VCD. When in
the Ready state, the LRIS64K answers any request where the Select_flag is not set.
15.3
Quiet state
When in the Quiet state, the LRIS64K answers any request except for Inventory requests
with the Address_flag set.
15.4
Selected state
In the Selected state, the LRIS64K answers any request in all modes (see Section 16:
Modes):
40/100
●
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
Doc ID 15336 Rev 11
LRIS64K
LRIS64K states
Table 16.
LRIS64K response depending on Request_flags
Address_flag
Flags
1
Addressed
0
Non addressed
LRIS64K in Ready or Selected
state (Devices in Quiet state do not
answer)
X
LRIS64K in Selected state
X
LRIS64K in Ready, Quiet or
Selected state (the device which
matches the UID)
X
Error (03h)
X
Select_flag
1
Selected
0
Non selected
X
X
X
X
Figure 38. LRIS64K state transition diagram
Power Off
In field
Out of field
(U
iet
qu
ay
St
y
ad
re
o
tt
se
Re
e
er r
)
ID
wh o
y et D)
(U
ad s UI
ct
le
re is t
o ag en
Se
t t Fl er
se ct_ diff
Re ele ect(
S el
S
ID
)
Out of field
Out of field
Any other Command
where Select_Flag
is not set
Ready
Select (UID)
Quiet
Stay quiet(UID)
Any other command where the
Address_Flag is set AND
where Inventory_Flag is not set
Selected
Any other command
AI06681
1. The intention of the state transition method is that only one LRIS64K should be in the selected state at a
time.
Doc ID 15336 Rev 11
41/100
Modes
16
LRIS64K
Modes
The term “mode” refers to the mechanism used in a request to specify the set of LRIS64Ks
that will answer the request.
16.1
Addressed mode
When the Address_flag is set to 1 (Addressed mode), the request contains the Unique ID
(UID) of the addressed LRIS64K.
Any LRIS64K that receives a request with the Address_flag set to 1 compares the received
Unique ID to its own. If it matches, then the LRIS64K 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.
16.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 LRIS64K 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.
16.3
Select mode
When the Select_flag is set to 1 (Select mode), the request does not contain an LRIS64K
Unique ID. The LRIS64K 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 LRIS64Ks in the Selected state answer a request where the Select_flag set to 1.
The system design ensures in theory that only one LRIS64K can be in the Select state at a
time.
42/100
Doc ID 15336 Rev 11
LRIS64K
17
Request format
Request format
The request consists of:
●
an SOF
●
flags
●
a command code
●
parameters and data
●
a CRC
●
an EOF
Table 17.
S
O
F
17.1
General request format
Request_flags
Command code
Parameters
Data
CRC
E
O
F
Request flags
In a request, the “flags” field specifies the actions to be performed by the LRIS64K and
whether corresponding fields are present or not.
The flags field consists of eight bits. The bit 3 (Inventory_flag) of the request flag defines the
contents of the 4 MSBs (bits 5 to 8). When bit 3 is reset (0), bits 5 to 8 define the LRIS64K
selection criteria. When bit 3 is set (1), bits 5 to 8 define the LRIS64K Inventory parameters.
Table 18.
Bit No
Bit 1
Bit 2
Bit 3
Bit 4
Definition of request flags 1 to 4
Flag
Level
Subcarrier_flag(1)
Data_rate_flag(2)
Description
0
A single subcarrier frequency is used by the LRIS64K
1
Two subcarrier are used by the LRIS64K
0
Low data rate is used
1
High data rate is used
0
The meaning of flags 5 to 8 is described in Table 19
1
The meaning of flags 5 to 8 is described in Table 20
0
No Protocol format extension
1
Protocol format extension
Inventory_flag
Protocol_extension_flag
1. Subcarrier_flag refers to the LRIS64K-to-VCD communication.
2. Data_rate_flag refers to the LRIS64K-to-VCD communication
Doc ID 15336 Rev 11
43/100
Request format
.
Table 19.
Bit No
Bit 5
Bit 6
Bit 7
Bit 8
LRIS64K
Request flags 5 to 8 when Bit 3 = 0
Flag
Level
Select flag(1)
Description
0
Request is executed by any LRIS64K according to the setting of
Address_flag
1
Request is executed only by the LRIS64K in Selected state
0
Request is not addressed. UID field is not present. The request is
executed by all LRIS64Ks.
1
Request is addressed. UID field is present. The request is executed
only by the LRIS64K whose UID matches the UID specified in the
request.
0
Option not activated.
1
Option activated.
Address
flag(1)
Option flag
RFU
0
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.
Table 20.
Bit No
Bit 5
Bit 6
44/100
Request flags 5 to 8 when Bit 3 = 1
Flag
Level
Description
0
AFI field is not present
1
AFI field is present
0
16 slots
1
1 slot
AFI flag
Nb_slots flag
Bit 7
Option flag
0
Bit 8
RFU
0
Doc ID 15336 Rev 11
LRIS64K
18
Response format
Response format
The response consists of:
●
an SOF
●
flags
●
parameters and data
●
a CRC
●
an EOF
Table 21.
S
O
F
18.1
General response format
Response_flags
Parameters
Data
CRC
E
O
F
Response flags
In a response, the flags indicate how actions have been performed by the LRIS64K and
whether corresponding fields are present or not. The response flags consist of eight bits.
Table 22.
Definitions of response flags 1 to 8
Bit No
Bit 1
Flag
Level
Description
0
No error
1
Error detected. Error code is in the "Error" field.
Error_flag
Bit 2
RFU
0
Bit 3
RFU
0
Bit 4
Extension flag
0
Bit 5
RFU
0
Bit 6
RFU
0
Bit 7
RFU
0
Bit 8
RFU
0
No extension
Doc ID 15336 Rev 11
45/100
Response format
18.2
LRIS64K
Response error code
If the Error_flag is set by the LRIS64K in the response, the Error code field is present and
provides information about the error that occurred.
Error codes not specified in Table 23 are reserved for future use.
Table 23.
Response error code definition
Error code
46/100
Meaning
02h
The command is not recognized, for example a format error occurred
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
Doc ID 15336 Rev 11
LRIS64K
19
Anticollision
Anticollision
The purpose of the anticollision sequence is to inventory the LRIS64Ks present in the VCD
field using their unique ID (UID).
The VCD is the master of communications with one or several LRIS64Ks. It initiates
LRIS64K communication by issuing the Inventory request.
The LRIS64K sends its response in the determined slot or does not respond.
19.1
Request parameters
When issuing the Inventory Command, the VCD:
●
sets the Nb_slots_flag as desired
●
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 will be 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.
Table 24.
MSB
SOF
Inventory request format
Request
Command
_flags
8 bits
8 bits
Optional
AFI(1)
Mask
length
Mask value
CRC
8 bits
8 bits
0 to 8 bytes
16 bits
LSB
EOF
1. Gray means that the field is optional.
In the example of the Table 25 and Figure 39, 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 25.
Example of the addition of 0-bits to an 11-bit mask value
(b15) MSB
LSB (b0)
0000 0
100 1100 1111
0-bits added
11-bit mask value
Doc ID 15336 Rev 11
47/100
Anticollision
LRIS64K
Figure 39. Principle of comparison between the mask, the slot number and the UID
MSB
LSB
0000 0100 1100 1111 b 16 bits
Mask value received in the Inventory command
MSB
LSB
100 1100 1111 b 11 bits
The Mask value less the padding 0s is loaded
into the Tag comparator
MSB LSB
xxxx
The Slot counter is calculated
Nb_slots_flags = 0 (16 slots), Slot Counter is 4 bits
The Slot counter is concatened to the Mask value
Nb_slots_flags = 0
The concatenated result is compared with
the least significant bits of the Tag UID.
4 bits
MSB
LSB
xxxx 100 1100 1111 b 15 bits
UID
b63
b0
xxxx xxxx ..... xxxx xxxx x xxx xxxx xxxx xxxx b
Bits ignored
64 bits
Compare
AI06682
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 reception of the request EOF. To switch to the next
slot, the VCD sends an EOF.
The following rules and restrictions apply:
48/100
●
if no LRIS64K answer is detected, the VCD may switch to the next slot by sending an
EOF,
●
if one or more LRIS64K answers are detected, the VCD waits until the complete frame
has been received before sending an EOF for switching to the next slot.
Doc ID 15336 Rev 11
LRIS64K
20
Request processing by the LRIS64K
Request processing by the LRIS64K
Upon reception of a valid request, the LRIS64K 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
endif
Doc ID 15336 Rev 11
49/100
Explanation of the possible cases
21
LRIS64K
Explanation of the possible cases
Figure 40 summarizes the main possible cases that can occur during an anticollision
sequence when the slot number is 16.
The different steps are:
Note:
50/100
●
The VCD sends an Inventory request, in a frame terminated by an EOF. The number of
slots is 16.
●
LRIS64K_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 LRIS64Ks, LRIS64K_2 and LRIS64K_3 transmit a response, thus
generating a collision. The VCD records the event and remembers 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 LRIS64K transmits a response. Therefore the VCD does not detect any
LRIS64K SOF and decides to switch to the next slot by sending an EOF.
●
In slot 3, there is another collision caused by responses from LRIS64K_4 and
LRIS64K_5
●
The VCD then decides to send a request (for instance a Read Block) to LRIS64K_1
whose UID has already been correctly received.
●
All LRIS64Ks detect an SOF and exit the anticollision sequence. They process this
request and since the request is addressed to LRIS64K_1, only LRIS64K_1 transmits a
response.
●
All LRIS64Ks are ready to receive another request. If it is an Inventory command, the
slot numbering sequence restarts from 0.
The decision to interrupt the anticollision sequence is made by the VCD. It could have
continued to send EOFs until Slot 16 and only then sent the request to LRIS64K_1.
Doc ID 15336 Rev 11
Doc ID 15336 Rev 11
4IME
#OMMENT
4IMING
,2)3+S
6#$
3/&
)NVENTORY
%/&
2EQUEST
T
.O
COLLISION
2ESPONSE
3LOT
T
%/&
T
#OLLISION
2ESPONSE
2ESPONSE
3LOT
T
%/&
.O
2ESPONSE
T
3LOT
%/&
T
#OLLISION
2ESPONSE
2ESPONSE
3LOT
T
3/&
2EQUESTTO
%/&
,2)3+?
T
!)
2ESPONSE
FROM
,2)3+?
LRIS64K
Explanation of the possible cases
Figure 40. Description of a possible anticollision sequence
51/100
Inventory Initiated command
22
LRIS64K
Inventory Initiated command
The LRIS64K 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 to 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 will be initiated by the
Initiate command. In this case, a small batch of tags will answer to the Inventory Initiated
command which will optimize 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 LRIS64Ks to increase their
response data rate by a factor of 2, up to 53 Kbit/s.
52/100
Doc ID 15336 Rev 11
LRIS64K
Timing definition
23
Timing definition
23.1
t1: LRIS64K response delay
Upon detection of the rising edge of the EOF received from the VCD, the LRIS64K waits for
a time t1nom before transmitting its response to a VCD request or before switching to the
next slot during an inventory process. Values of t1 are given in Table 26. The EOF is defined
in Figure 11 on page 26.
23.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 LRIS64K responses have been received during an Inventory command. It starts from
the reception of the EOF from the LRIS64Ks.
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 LRIS64K.
t2 is also the time after which the VCD may send a new request to the LRIS64K as
described in Table 37: LRIS64K protocol timing.
Values of t2 are given in Table 26.
23.3
t3: VCD new request delay in the absence of a response from
the LRIS64K
t3 is the time after which the VCD may send an EOF to switch to the next slot when no
LRIS64K 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 LRIS64K.
From the time the VCD has generated the rising edge of an EOF:
●
If this EOF is 100% modulated, the VCD waits a time at least equal to t3min before
sending a new EOF.
●
If this EOF is 10% modulated, the VCD waits a time at least equal to the sum of t3min +
the LRIS64K nominal response time (which depends on the LRIS64K data rate and
subcarrier modulation mode) before sending a new EOF.
Table 26.
Timing values(1)
Minimum (min) values
Nominal (nom) values
Maximum (max) values
t1
318.6 µs
320.9 µs
323.3 µs
t2
309.2 µs
No tnom
No tmax
No tnom
No tmax
t3
t1max
(2)
+
tSOF(3)
1. The tolerance of specific timings is ± 32/fC.
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 LRIS64K to transmit an SOF to the VCD. tSOF depends on the current data
rate: High data rate or Low data rate.
Doc ID 15336 Rev 11
53/100
Commands codes
24
LRIS64K
Commands codes
The LRIS64K supports the commands described in this section. Their codes are given in
Table 27.
Table 27.
Command codes
Command code
standard
54/100
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 Password
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
2Bh
Get System Info
Doc ID 15336 Rev 11
LRIS64K
24.1
Commands codes
Inventory
When receiving the Inventory request, the LRIS64K runs the anticollision sequence. The
Inventory_flag is set to 1. The meaning of flags 5 to 8 is shown in Table 20: Request flags 5
to 8 when Bit 3 = 1.
The request contains:
●
the flags,
●
the Inventory command code (see Table 27: Command codes)
●
the AFI if the AFI flag is set
●
the mask length
●
the mask value
●
the CRC
The LRIS64K does not generate any answer in case of error.
Table 28.
Inventory request format
Request
Request_flags Inventory
SOF
Optional
AFI(1)
Mask
length
Mask
value
CRC16
8 bits
8 bits
8 bits
0 - 64 bits
16 bits
01h
Request
EOF
1. Gray means that the field is optional.
The response contains:
●
the flags
●
the Unique ID
Table 29.
Inventory response format
Response Response_
SOF
flags
8 bits
DSFID
UID
CRC16
8 bits
64 bits
16 bits
Response
EOF
During an Inventory process, if the VCD does not receive an RF LRIS64K response, it waits
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 LRIS64K to transmit an SOF to the VCD
●
tNRT is the nominal response time of the LRIS64K
tNRT and tSOF are dependent on the LRIS64K-to-VCD data rate and subcarrier modulation
mode.
Doc ID 15336 Rev 11
55/100
Commands codes
24.2
LRIS64K
Stay Quiet
Command code = 0x02
On receiving the Stay Quiet command, the LRIS64K 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 LRIS64K does not process any request if the Inventory_flag is set,
●
the LRIS64K processes any Addressed request
The LRIS64K 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.
Table 30.
Request
SOF
Stay Quiet request format
Request flags
Stay Quiet
UID
CRC16
8 bits
02h
64 bits
16 bits
Request
EOF
The Stay Quiet command must always be executed in Addressed mode (Select_flag is reset
to 0 and Address_flag is set to 1).
Figure 41. Stay Quiet frame exchange between VCD and LRIS64K
VCD
SOF
Stay Quiet
request
EOF
LRIS64K
Timing
56/100
Doc ID 15336 Rev 11
LRIS64K
24.3
Commands codes
Read Single Block
On receiving the Read Single Block command, the LRIS64K reads the requested block and
sends back its 32-bit value in the response. The Protocol_extention_flag should be set to 1
for the LRIS64K to operate correctly. If the Protocol_extention_flag is at 0, the LRIS64K
answers with an error code. The Option_flag is supported.
Table 31.
Read Single Block request format
Request Request_ Read Single
SOF
flags
Block
8 bits
20h
UID(1)
Block
number
CRC16
64 bits
16 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
Request parameters:
●
Option_flag
●
UID (optional)
●
Block number
Table 32.
Read Single Block response format when Error_flag is NOT set
Response Response_
SOF
flags
Sector
security
status(1)
Data
CRC16
8 bits
32 bits
16 bits
8 bits
Response
EOF
1. Gray means that the field is optional.
Response parameters:
●
Sector security status if Option_flag is set (see Table 33: Sector security status)
●
4 bytes of block data
Table 33.
b7
Sector security status
b6
b5
Reserved for future
use. All at 0
Table 34.
Response
SOF
b4
b3
password
control bits
b2
b1
Read / Write
protection bits
b0
0: Current sector not locked
1: Current sector locked
Read Single Block response format when Error_flag is set
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Doc ID 15336 Rev 11
Response
EOF
57/100
Commands codes
LRIS64K
Response parameter:
●
Error code as Error_flag is set
–
03h: the option is not supported
–
0Fh: error with no information given
–
10h: the specified block is not available
–
15h: the specified block is read-protected
Figure 42. Read Single Block frame exchange between VCD and LRIS64K
VCD
LRIS64K
58/100
SOF
Read Single Block
request
EOF
<-t1-> SOF
Doc ID 15336 Rev 11
Read Single Block
response
EOF
LRIS64K
24.4
Commands codes
Write Single Block
On receiving the Write Single Block command, the LRIS64K writes the data contained in the
request to the requested block and reports whether the write operation was successful in
the response. The Protocol_extention_flag should be set to 1 for the LRIS64K to operate
correctly. If the Protocol_extention_flag is at 0, the LRIS64K answers with an error code.
The Option_flag is supported.
During write cycle Wt, there should be no modulation (neither 100% nor 10%). Otherwise,
the LRIS64K may not program correctly the data into the memory. The Wt time is equal to
t1nom + 18 × 302 µs.
Table 35.
Write Single Block request format
Request Request_
SOF
flags
Write
Single
Block
UID(1)
Block
number
Data
CRC16
21h
64 bits
16 bits
32 bits
16 bits
8 bits
Request
EOF
1. Gray means that the field is optional.
Request parameters:
●
UID (optional)
●
Block number
●
Data
Table 36.
Write Single Block response format when Error_flag is NOT set
Response SOF
Response_flags
CRC16
8 bits
16 bits
Response EOF
Response parameter:
●
No parameter. The response is send back after the writing cycle.
Table 37.
Write Single Block response format when Error_flag is set
Response
SOF
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set:
–
03h: the option is not supported
–
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
Doc ID 15336 Rev 11
59/100
Commands codes
LRIS64K
Figure 43. Write Single Block frame exchange between VCD and LRIS64K
VCD
SOF
Write Single
Block request
EOF
LRIS64K
<-t1-> SOF
Write Single Block
response
EOF
LRIS64K
<----------------- Wt ----------------->
SOF
60/100
Doc ID 15336 Rev 11
Write sequence when
error
Write Single
Block response
EOF
LRIS64K
24.5
Commands codes
Read Multiple Block
When receiving the Read Multiple Block command, the LRIS64K reads the selected blocks
and sends back their value in multiples of 32 bits in the response. The blocks are numbered
from '00h to '7FFh' 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, 7 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 LRIS64K returns an error code.
The Protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. If the
Protocol_extention_flag is at 0, the LRIS64K answers with an error code.
The Option_flag is supported.
Table 38.
Read Multiple Block request format
Read
Request Request_
Multiple
SOF
flags
Block
UID(1)
First
block
number
Number
of blocks
CRC16
8 bits
64 bits
16 bits
8 bits
16 bits
23h
Request
EOF
1. Gray means that the field is optional.
Request parameters:
●
Option_flag
●
UID (optional)
●
First block number
●
Number of blocks
Table 39.
Read Multiple Block response format when Error_flag is NOT set
Response Response_
SOF
flags
8 bits
Sector
security
status(1)
Data
CRC16
8 bits(2)
32 bits(2)
16 bits
Response
EOF
1. Gray means that the field is optional.
2. Repeated as needed.
Response parameters:
●
Sector security status if Option_flag is set (see Table 40: Sector security status)
●
N blocks of data
Table 40.
b7
Sector security status
b6
b5
Reserved for future
use. All at 0
b4
b3
password
control bits
b2
b1
Read / Write
protection bits
Doc ID 15336 Rev 11
b0
0: Current sector not locked
1: Current sector locked
61/100
Commands codes
LRIS64K
Table 41.
Read Multiple Block response format when Error_flag is set
Response SOF
Response_flags
Error code
CRC16
8 bits
8 bits
16 bits
Response EOF
Response parameter:
●
Error code as Error_flag is set:
–
03h: the option is not supported
–
0Fh: error with no information given
–
10h: the specified block is not available
–
15h: the specified block is read-protected
Figure 44. Read Multiple Block frame exchange between VCD and LRIS64K
VCD
LRIS64K
62/100
SOF
Read Multiple
EOF
Block request
<-t1-> SOF
Doc ID 15336 Rev 11
Read Multiple
EOF
Block response
LRIS64K
24.6
Commands codes
Select
When receiving the Select command:
●
if the UID is equal to its own UID, the LRIS64K enters or stays in the Selected state and
sends a response.
●
if the UID does not match its own, the selected LRIS64K returns to the Ready state and
does not send a response.
The LRIS64K 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 LRIS64K remains in its current state.
Table 42.
Select request format
Request Request_
SOF
flags
Select
UID
CRC16
25h
64 bits
16 bits
8 bits
Request
EOF
Request parameter:
●
UID
Table 43.
Select Block response format when Error_flag is NOT set
Response
SOF
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
No parameter.
Table 44.
Select response format when Error_flag is set
Response
SOF
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set:
–
03h: the option is not supported
–
0Fh: error with no information given
Figure 45. Select frame exchange between VCD and LRIS64K
VCD
LRIS64K
SOF
Select
request
EOF
<-t1-> SOF
Doc ID 15336 Rev 11
Select
response
EOF
63/100
Commands codes
24.7
LRIS64K
Reset to Ready
On receiving a Reset to Ready command, the LRIS64K returns to the Ready state if no
error occurs. In the Addressed mode, the LRIS64K answers an error code only if the UID is
equal to its own UID. If not, no response is generated.
Table 45.
Reset to Ready request format
Request Request_ Reset to
SOF
flags
Ready
UID(1)
CRC16
8 bits
64 bits
16 bits
26h
Request
EOF
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
Table 46.
Reset to Ready response format when Error_flag is NOT set
Response
SOF
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
No parameter
Table 47.
Reset to ready response format when Error_flag is set
Response
Response_flags
SOF
8 bits
Error code
CRC16
8 bits
16 bits
Response parameter:
●
Error code as Error_flag is set:
–
03h: the option is not supported
–
0Fh: error with no information given
Figure 46. Reset to Ready frame exchange between VCD and LRIS64K
VCD
LRIS64K
64/100
SOF
Reset to
Ready
request
EOF
<-t1->
SOF
Doc ID 15336 Rev 11
Reset to
Ready
response
EOF
Response
EOF
LRIS64K
24.8
Commands codes
Write AFI
On receiving the Write AFI request, the LRIS64K programs the 8-bit AFI value to its
memory. The Option_flag is supported.
During write cycle Wt, there should be no modulation (neither 100% nor 10%). Otherwise,
the LRIS64K may not write correctly the AFI value into the memory. The Wt time is equal to
t1nom + 18 × 302 µs.
Table 48.
Write AFI request format
Request Request Write
SOF
_flags
AFI
8 bits
27h
UID(1)
AFI
CRC16
64 bits
8 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
●
AFI
Table 49.
Write AFI response format when Error_flag is NOT set
Response
SOF
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
No parameter.
Table 50.
Write AFI response format when Error_flag is set
Response
SOF
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set
–
03h: the option is not supported
–
0Fh: error with no information given
–
12h: the specified block is locked and its contents cannot be changed.
–
13h: the specified block was not successfully programmed
Doc ID 15336 Rev 11
65/100
Commands codes
LRIS64K
Figure 47. Write AFI frame exchange between VCD and LRIS64K
VCD
66/100
SOF
Write AFI
request
EOF
LRIS64K
<-t1-> SOF
EOF
Write sequence
when error
LRIS64K
<---------------- Wt ----------------> SOF
Write AFI
EOF
response
Doc ID 15336 Rev 11
Write AFI
response
LRIS64K
24.9
Commands codes
Lock AFI
On receiving the Lock AFI request, the LRIS64K locks the AFI value permanently. The
Option_flag is supported.
During write cycle Wt, there should be no modulation (neither 100% nor 10%). Otherwise,
the LRIS64K may not Lock correctly the AFI value in memory. The Wt time is equal to t1nom
+ 18 × 302 µs.
Table 51.
Lock AFI request format
Request Request_
SOF
flags
8 bits
Lock
AFI
UID(1)
CRC16
28h
64 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
Table 52.
Lock AFI response format when Error_flag is NOT set
Response
SOF
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
No parameter
Table 53.
Lock AFI response format when Error_flag is set
Response
SOF
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set
–
03h: the option is not supported
–
0Fh: error with no information given
–
11h: the specified block is already locked and thus cannot be locked again
–
14h: the specified block was not successfully locked
Doc ID 15336 Rev 11
67/100
Commands codes
LRIS64K
Figure 48. Lock AFI frame exchange between VCD and LRIS64K
VCD
68/100
SOF
Lock AFI
EOF
request
Lock AFI
response
LRIS64K
<-t1-> SOF
LRIS64K
<--------------- Wt ---------------> SOF
Doc ID 15336 Rev 11
EOF
Lock sequence when
error
Lock AFI
response
EOF
LRIS64K
24.10
Commands codes
Write DSFID
On receiving the Write DSFID request, the LRIS64K programs the 8-bit DSFID value to its
memory. The Option_flag is supported.
During write cycle Wt, there should be no modulation (neither 100% nor 10%). Otherwise,
the LRIS64K may not write correctly the DSFID value in memory. The Wt time is equal to
t1nom + 18 × 302 µs.
Table 54.
Write DSFID request format
Request Request_ Write
SOF
flags
DSFID
8 bits
29h
UID(1)
DSFID
CRC16
64 bits
8 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
●
DSFID
Table 55.
Write DSFID response format when Error_flag is NOT set
Response
SOF
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
No parameter
Table 56.
Write DSFID response format when Error_flag is set
Response
Response_flags
SOF
Error code
CRC16
8 bits
16 bits
8 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set
–
03h: the option is not supported
–
0Fh: error with no information given
–
12h: the specified block is locked and its contents cannot be changed.
–
13h: the specified block was not successfully programmed
Doc ID 15336 Rev 11
69/100
Commands codes
LRIS64K
Figure 49. Write DSFID frame exchange between VCD and LRIS64K
VCD
70/100
SOF
Write DSFID
EOF
request
Write DSFID
response
LRIS64K
<-t1-> SOF
LRIS64K
<--------------- Wt ---------------> SOF
Doc ID 15336 Rev 11
EOF
Write sequence when
error
Write DSFID
EOF
response
LRIS64K
24.11
Commands codes
Lock DSFID
On receiving the Lock DSFID request, the LRIS64K locks the DSFID value permanently.
The Option_flag is supported.
During write cycle Wt, there should be no modulation (neither 100% nor 10%). Otherwise,
the LRIS64K may not lock correctly the DSFID value in memory. The Wt time is equal to
t1nom + 18 × 302 µs.
Table 57.
Lock DSFID request format
Request Request_
SOF
flags
Lock
DSFID
UID(1)
CRC16
2Ah
64 bits
16 bits
8 bits
Request
EOF
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
Table 58.
Lock DSFID response format when Error_flag is NOT set
Response
SOF
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
No parameter.
Table 59.
Lock DSFID response format when Error_flag is set
Response
Response_flags
SOF
Error code
CRC16
8 bits
16 bits
8 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set:
–
03h: the option is not supported
–
0Fh: error with no information given
–
11h: the specified block is already locked and thus cannot be locked again
–
14h: the specified block was not successfully locked
Doc ID 15336 Rev 11
71/100
Commands codes
LRIS64K
Figure 50. Lock DSFID frame exchange between VCD and LRIS64K
VCD
72/100
SOF
Lock DSFID
EOF
request
Lock DSFID
response
LRIS64K
<-t1-> SOF
LRIS64K
<--------------- Wt ---------------> SOF
Doc ID 15336 Rev 11
EOF
Lock sequence
when error
Lock DSFID
EOF
response
LRIS64K
24.12
Commands codes
Get System Info
When receiving the Get System Info command, the LRIS64K sends back its information
data in the response.The Option_flag is supported and must be reset to 0. The Get System
Info can be issued in both Addressed and Non Addressed modes.
The Protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. If the
Protocol_extention_flag is at 0, the LRIS64K answers with an error code.
Table 60.
Get System Info request format
Request Request Get System
SOF
_flags
Info
8 bits
2Bh
UID(1)
CRC16
64 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
Table 61.
Get System Info response format when Error_flag is NOT set
Response Response Information
SOF
_flags
flags
00h
0Fh
UID
64 bits
DSFID AFI
Memory
IC
Response
CRC16
size reference
EOF
8 bits 8 bits 0307FFh
44h
16 bits
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 LRIS64K provides 2048 blocks (07FFh) of 4 byte (03h)
●
IC reference. Only the 6 MSB are significant.
Table 62.
Get System Info response format when Error_flag is set
Response
SOF
Response_flags
Error code
CRC16
01h
8 bits
16 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set:
–
03h: Option not supported
–
0Fh: other error
Doc ID 15336 Rev 11
73/100
Commands codes
LRIS64K
Figure 51. Get System Info frame exchange between VCD and LRIS64K
VCD
LRIS64K
74/100
SOF Get System Info request EOF
<-t1-> SOF Get System Info response EOF
Doc ID 15336 Rev 11
LRIS64K
24.13
Commands codes
Get Multiple Block Security Status
When receiving the Get Multiple Block Security Status command, the LRIS64K sends back
the sector security status. The blocks are numbered from '00h to '07FFh' 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 7 blocks.
The Protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. If the
Protocol_extention_flag is at 0, the LRIS64K answers with an error code.
During the LRIS64K response, if the internal block address counter reaches 07FFh, it rolls
over to 0000h and the Sector Security Status bytes for that location are sent back to the
reader.
Table 63.
Get Multiple Block Security Status request format
Get
Multiple
Request Request
Block
SOF
_flags
Security
Status
UID(1)
8 bits
64 bits
2Ch
First
Number
Request
block
CRC16
of blocks
EOF
number
16 bits
16 bits
16 bits
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
●
First block number
●
Number of blocks
Table 64.
Response
SOF
Get Multiple Block Security Status response format when Error_flag is
NOT set
Response_
flags
Sector security
status
CRC16
8 bits
8 bits(1)
16 bits
Response
EOF
1. Repeated as needed.
Response parameters:
●
Sector security status (see Table 65: Sector security status)
Table 65.
b7
Sector security status
b6
b5
Reserved for future use. All
at 0
b4
b3
password control
bits
b2
b1
Read / Write
protection bits
Doc ID 15336 Rev 11
b0
0: Current sector not locked
1: Current sector locked
75/100
Commands codes
LRIS64K
Table 66.
Get Multiple Block Security Status response format when Error_flag is
set
Response
SOF
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set:
–
03h: the option is not supported
–
0Fh: error with no information given
–
10h: the specified block is not available
Figure 52. Get Multiple Block Security Status frame exchange between VCD and
LRIS64K
VCD
LRIS64K
76/100
SOF
Get Multiple Block
Security Status
EOF
<-t1-> SOF
Doc ID 15336 Rev 11
Get Multiple Block
EOF
Security Status
LRIS64K
24.14
Commands codes
Write-sector Password
On receiving the Write-sector Password command, the LRIS64K 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 write cycle time Wt, there must be no modulation at all (neither 100% nor 10%).
Otherwise, the LRIS64K 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 LRIS64K power-down.
Table 67.
Write-sector Password request format
Request Request
SOF
_flags
WriteIC Mfg
sector
code
Password
8 bits
B1h
02h
UID(1)
Password
number
Data
CRC16
64 bits
8 bits
32 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
●
Password number (01h = Pswd1, 02h = Pswd2, 03h = Pswd3, other = Error)
●
Data
Table 68.
Write-sector Password response format when Error_flag is NOT set
Response
SOF
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
32-bit password value. The response is sent back after the write cycle.
Table 69.
Write-sector Password response format when Error_flag is set
Response
SOF
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set:
–
02h: the command is not recognized, for example: a format error occurred
–
03h: the option is not supported
–
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
Doc ID 15336 Rev 11
77/100
Commands codes
LRIS64K
Figure 53. Write-sector Password frame exchange between VCD and LRIS64K
VCD
LRIS64K
LRIS64K
78/100
SOF
Writesector
Password
request
EOF
<-t1-> SOF
Write-sector
Password
response
<--------------- Wt --------------->
Doc ID 15336 Rev 11
EOF
SOF
Write sequence
when error
Writesector
Password
response
EOF
LRIS64K
24.15
Commands codes
Lock-sector Password
On receiving the Lock-sector Password command, the LRIS64K 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 Password
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 Password command as all the blocks belonging to the same sector are
automatically locked by a single command.
The Protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. If the
Protocol_extention_flag is at 0, the LRIS64K answers with an error code.
During write cycle Wt, there should be no modulation (neither 100% nor 10%) otherwise, the
LRIS64K may not correctly lock the memory block.
The Wt time is equal to t1nom + 18 × 302 µs.
Table 70.
Lock-sector Password request format
Request Request
SOF
_flags
LockIC
sector
Mfg
Password code
8 bits
B2h
Sector
Sector
Request
security CRC16
number
EOF
status
UID(1)
64 bits
02h
16 bits
8 bits
16 bits
1. Gray means that the field is optional.
Request parameters:
●
(optional) UID
●
Sector number
●
Sector security status (refer to Table 71)
Table 71.
Sector security status
b7
b6
b5
0
0
0
Table 72.
Response
SOF
b4
b3
password control bits
b2
b1
b0
Read / Write protection
bits
1
Lock-sector Password response format when Error_flag is NOT set
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
No parameter.
Table 73.
Response
SOF
Lock-sector Password response format when Error_flag is set
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Doc ID 15336 Rev 11
Response
EOF
79/100
Commands codes
LRIS64K
Response parameter:
●
Error code as Error_flag is set:
–
02h: the command is not recognized, for example: a format error occurred
–
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
–
14h: the specified block was not successfully locked
Figure 54. Lock-sector Password frame exchange between VCD and LRIS64K
VCD
LRIS64K
LRIS64K
80/100
SOF
Lock-sector
Password
request
EOF
<-t1-> SOF
Lock-sector
Password
response
<--------------- Wt --------------->
Doc ID 15336 Rev 11
EOF
Lock sequence when
error
SOF
Lock-sector
Password
response
EOF
LRIS64K
24.16
Commands codes
Present-sector Password
On receiving the Present-sector Password command, the LRIS64K 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 Wt comparison cycle time, there should be no modulation (neither 100% nor
10%) otherwise, the LRIS64K 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 3.1: LRIS64K RF block security.
Table 74.
Present-sector Password request format
Request Request
SOF
_flags
PresentIC
sector
Mfg
Password code
8 bits
B3h
02h
UID(1)
Password
number
Data
CRC16
64 bits
8 bits
32 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
Request parameter:
●
UID (optional)
●
Password Number (0x01 = Pswd1, 0x02 = Pswd2, 0x03 = Pswd3, other = Error)
●
Data
Table 75.
Present-sector Password response format when Error_flag is NOT set
Response
SOF
Response_flags
CRC16
8 bits
16 bits
Response
EOF
Response parameter:
●
No parameter. The response is send back after the writing cycle
Table 76.
Present-sector Password response format when Error_flag is set
Response
SOF
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Response
EOF
Response parameter:
●
Error code as Error_flag is set:
–
02h: the command is not recognized, for example: a format error occurred
–
03h: the option is not supported
–
0Fh: error with no information given
–
10h: the specified block is not available
Doc ID 15336 Rev 11
81/100
Commands codes
LRIS64K
Figure 55. Present-sector Password frame exchange between VCD and LRIS64K
VCD
LRIS64K
LRIS64K
82/100
SOF
Presentsector
Password
request
EOF
<-t1-> SOF
Presentsector
Password
response
EOF
<-------------- Wt --------------> SOF
Doc ID 15336 Rev 11
sequence when error
Presentsector
Password
response
EOF
LRIS64K
24.17
Commands codes
Fast Read Single Block
On receiving the Fast Read Single Block command, the LRIS64K 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_extention_flag should be set to 1 for the LRIS64K to operate correctly. If the
Protocol_extention_flag is at 0, the LRIS64K answers with an error code.
Table 77.
Fast Read Single Block request format
Request Request_
SOF
flags
Fast Read
IC Mfg
Single
code
Block
8 bits
C0h
02h
UID(1)
Block
number
CRC16
64 bits
16 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
Request parameters:
●
Option_flag
●
UID (optional)
●
Block number
Table 78.
Fast Read Single Block response format when Error_flag is NOT set
Response Response
SOF
_flags
8 bits
Sector
security
status(1)
Data
CRC16
8 bits
32 bits
16 bits
Response
EOF
1. Gray means that the field is optional.
Response parameters:
●
Sector security status if Option_flag is set (see Table 79)
●
4 bytes of block data
Table 79.
b7
Sector security status
b6
b5
Reserved for future used. All
at 0
Table 80.
Response
SOF
b4
b3
password control
bits
b2
b1
Read / Write
protection bits
b0
0: Current sector not locked
1: Current sector locked
Fast Read Single Block response format when Error_flag is set
Response_
flags
Error code
CRC16
8 bits
8 bits
16 bits
Doc ID 15336 Rev 11
Response
EOF
83/100
Commands codes
LRIS64K
Response parameter:
●
Error code as Error_flag is set:
–
02h: the command is not recognized, for example: a format error occurred
–
03h: the option is not supported
–
0Fh: error with no information given
–
10h: the specified block is not available
–
15h: the specified block is read protected
Figure 56. Fast Read Single Block frame exchange between VCD and LRIS64K
VCD
SOF
Fast Read Single Block
EOF
request
LRIS64K
84/100
<-t1-> SOF
Doc ID 15336 Rev 11
Fast Read Single
Block response
EOF
LRIS64K
24.18
Commands codes
Fast Inventory Initiated
Before receiving the Fast Inventory Initiated command, the LRIS64K must have received an
Initiate or a Fast Initiate command in order to set the Initiate_ flag. If not, the LRIS64K does
not answer to the Fast Inventory Initiated command.
On receiving the Fast Inventory Initiated request, the LRIS64K runs the anticollision
sequence. The Inventory_flag must be set to 1. The meaning of flags 5 to 8 is shown in
Table 20: Request flags 5 to 8 when Bit 3 = 1. 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 LRIS64K does not generate any answer in case of error.
Table 81.
Fast Inventory Initiated request format
Fast
Request Request
IC Mfg Optional Mask
Inventory
SOF
_flags
AFI(1) length
code
Initiated
8 bits
C1h
02h
8 bits
8 bits
Mask value
CRC16
0 - 64 bits
16 bits
Request
EOF
1. Gray means that the field is optional.
The Response contains:
●
the flags
●
the Unique ID
Table 82.
Fast Inventory Initiated response format
Response Response
DSFID
SOF
_flags
8 bits
8 bits
UID
CRC16
64 bits
16 bits
Response
EOF
During an Inventory process, if the VCD does not receive an RF LRIS64K response, it waits
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 LRIS64K to transmit an SOF to the VCD
●
tNRT is the nominal response time of the LRIS64K
Doc ID 15336 Rev 11
85/100
Commands codes
LRIS64K
tNRT and tSOF are dependent on the LRIS64K-to-VCD data rate and subcarrier modulation
mode.
24.19
Fast Initiate
On receiving the Fast Initiate command, the LRIS64K will set the internal Initiate_flag and
send 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 LRIS64K does not generate any answer. The Initiate_flag is reset after a
power off of the LRIS64K. The data rate of the response is multiplied by 2.
The request contains:
●
No data
Table 83.
Request
SOF
Fast Initiate request format
Request_flags
Fast
Initiate
IC Mfg
Code
CRC16
8 bits
C2h
02h
16 bits
Request
EOF
The response contains:
●
the flags
●
the Unique ID
Table 84.
Fast Initiate response format
Response Response
DSFID
SOF
_flags
8 bits
8 bits
UID
CRC16
64 bits
16 bits
Response
EOF
Figure 57. Fast Initiate frame exchange between VCD and LRIS64K
VCD
LRIS64K
86/100
SOF
Fast Initiate request
EOF
<-t1-> SOF Fast Initiate response EOF
Doc ID 15336 Rev 11
LRIS64K
24.20
Commands codes
Fast Read Multiple Block
On receiving the Fast Read Multiple Block command, the LRIS64K reads the selected
blocks and sends back their value in multiples of 32 bits in the response. The blocks are
numbered from '00h to '7FFh' 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, 7 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 LRIS64K returns an error code.
The Protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. If the
Protocol_extention_flag is at 0, the LRIS64K answers with an error code.
The Option_flag is supported. The data rate of the response is multiplied by 2.
Table 85.
Fast Read Multiple Block request format
Request Request_
SOF
flags
Fast
Read
Multiple
Block
IC Mfg
code
UID(1)
C3h
02h
64 bits
8 bits
First
Number
Request
block
of
CRC16
EOF
number blocks
16 bits
8 bits
16 bits
1. Gray means that the field is optional.
Request parameters:
●
Option_flag
●
UID (Optional)
●
First block number
●
Number of blocks
Table 86.
Fast Read Multiple Block response format when Error_flag is NOT set
Response Response_
SOF
flags
8 bits
Sector
security
status(1)
Data
CRC16
8 bits(2)
32 bits(2)
16 bits
Response
EOF
1. Gray means that the field is optional.
2. Repeated as needed.
Response parameters:
●
Sector security status if Option_flag is set (see Table 87: Sector security status if
Option_flag is set)
●
N block of data
Table 87.
b7
Sector security status if Option_flag is set
b6
b5
Reserved for future use.
All at 0
b4
b3
password
control bits
b2
b1
Read / Write
protection bits
Doc ID 15336 Rev 11
b0
0: Current sector not locked
1: Current sector locked
87/100
Commands codes
LRIS64K
Table 88.
Fast Read Multiple Block response format when Error_flag is set
Response SOF
Response_flags
Error code
CRC16
8 bits
8 bits
16 bits
Response EOF
Response parameter:
●
Error code as Error_flag is set:
–
0Fh: other error
–
10h: block address not available
Figure 58. Fast Read Multiple Block frame exchange between VCD and LRIS64K
VCD
LRIS64K
88/100
SOF
Fast Read
Multiple Block
request
EOF
<-t1-> SOF
Doc ID 15336 Rev 11
Fast Read
Multiple Block
response
EOF
LRIS64K
24.21
Commands codes
Inventory Initiated
Before receiving the Inventory Initiated command, the LRIS64K must have received an
Initiate or a Fast Initiate command in order to set the Initiate_ flag. If not, the LRIS64K does
not answer to the Inventory Initiated command.
On receiving the Inventory Initiated request, the LRIS64K runs the anticollision sequence.
The Inventory_flag must be set to 1. The meaning of flags 5 to 8 is given in Table 20:
Request flags 5 to 8 when Bit 3 = 1.
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 LRIS64K does not generate any answer in case of error.
Table 89.
Inventory Initiated request format
IC
Optional Mask
Mfg
AFI
length
code
Request Request Inventory
SOF
_flags
Initiated
8 bits
D1h
02h
8 bits
8 bits
Mask value
CRC16
0 - 64 bits
16 bits
Request
EOF
The response contains:
●
the flags
●
the Unique ID
Table 90.
Inventory Initiated response format
Response Response
SOF
_flags
8 bits
DSFID
UID
CRC16
8 bits
64 bits
16 bits
Response
EOF
During an Inventory process, if the VCD does not receive an RF LRIS64K response, it waits
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 LRIS64K to transmit an SOF to the VCD
●
tNRT is the nominal response time of the LRIS64K
tNRT and tSOF are dependent on the LRIS64K-to-VCD data rate and subcarrier modulation
mode.
Doc ID 15336 Rev 11
89/100
Commands codes
24.22
LRIS64K
Initiate
On receiving the Initiate command, the LRIS64K will set the internal Initiate_flag and send
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 LRIS64K does not generate any answer. The Initiate_flag is reset after a power
off of the LRIS64K.
The request contains:
●
No data
Table 91.
Initiate request format
Request
Request_flags
SOF
Initiate
IC Mfg
code
CRC16
D2h
02h
16 bits
8 bits
Request
EOF
The response contains:
●
the flags
●
the Unique ID
Table 92.
Initiate Initiated response format
Response Response
SOF
_flags
8 bits
DSFID
UID
CRC16
8 bits
64 bits
16 bits
Figure 59. Initiate frame exchange between VCD and LRIS64K
VCD
LRIS64K
90/100
SOF
Initiate
request
EOF
<-t1-> SOF
Doc ID 15336 Rev 11
Initiate
response
EOF
Response
EOF
LRIS64K
25
Maximum rating
Maximum rating
Stressing the device above the rating listed in the absolute maximum ratings table 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 device reliability. Refer also to the STMicroelectronics SURE
Program and other relevant quality documents.
Table 93.
Absolute maximum ratings
Symbol
Parameter
Min.
Max.
Unit
15
25
°C
6
months
TSTG
Storage conditions
tSTG
Storage time
ICC
Supply current on AC0 / AC1
–20
20
mA
VMAX
Input voltage on AC0 / AC1
–7
7
V
AC0 - AC1 (HBM)(1)
–800
800
V
VESD
Electrostatic discharge voltage
AC0 - AC1 (MM)
–100
100
V
Sawn Bumped Wafer
(kept in its antistatic
bag)
1. AEC-Q100-002 (compliant with JEDEC Std JESD22-A114A, C1 = 100 pF, R1 = 1500 Ω, R2 = 500 Ω).
Doc ID 15336 Rev 11
91/100
RF DC and AC parameters
26
LRIS64K
RF DC and AC 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 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.
Table 94.
RF AC characteristics(1) (2)
Symbol
fCC
H_ISO
H_Extended
MICARRIER
tRFR, tRFF
tRFSBL
Parameter
Condition
External RF signal frequency
Operating field according to ISO
Operating field in extended
temperature range
Min
Typ
Max
Unit
13.553
13.56
13.567
MHz
TA = 0 °C to 50 °C
150
5000
mA/m
TA = –40 °C to 85 °C
150
3500
mA/m
150 mA/m > H_ISO >
1000 mA/m
15
H_ISO > 1000 mA/m
10
30
10% rise and fall time
0.5
3.0
µs
10% minimum pulse width for bit
7.1
9.44
µs
95
100
%
10% carrier modulation index(3) (4)
MI=(A-B)/(A+B)
%
MICARRIER
100% carrier modulation index
tRFR, tRFF
100% rise and fall time
0.5
3.5
µs
100% minimum pulse width for bit
7.1
9.44
µs
Bit pulse jitter
-2
+2
µs
1
ms
tRFSBL
tJIT
MI=(A-B)/(A+B)
30
tMIN CD
Minimum time from carrier
generation to first data
From H-field min
0.1
fSH
Subcarrier frequency high
fCC/32
423.75
kHz
fSL
Subcarrier frequency low
fCC/28
484.28
kHz
t1
Time for LRIS64K response
4224/fS
318.6
320.9
323.3
µs
t2
Time between commands
4224/fS
309
311.5
314
µs
Wt
RF write time (including internal
Verify)
5.75
ms
1. TA = –40 to 85 °C.
2. All timing measurements were performed between 0 °C and 50 °C 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 2 conductors: 0.3 mm
Value of the tuning capacitor in SO8: 27.5 pF (LRIS64K)
Value of the coil: 5 µH
Tuning frequency: 13.56 MHz.
3. Characterized only, not 100% tested
4. 15% (or more) carrier modulation index offers a better signal/noise ratio and therefore a wider operating range with a better
noise immunity
92/100
Doc ID 15336 Rev 11
LRIS64K
RF DC and AC parameters
RF DC characteristics(1)
Table 95.
Symbol
Parameter
VCC
Test conditions
Min.
Typ.
Limited voltage
Backscattered level as defined
by ISO test
VBACK
ICC
ISO/IEC 10373-7
Unit
2.0
V
10
mV
Read
VCC = 2.0 V
50
µA
Write
VCC = 2.0 V
150
µA
30.2
pF
Supply current
Internal tuning capacitor(2)
CTUN
Max.
f = 13.56 MHz
24.8
27.5
1. TA = –40 to 85 °C.
2. Characterised only, at room temperature only, measured at VAC0-AC1 = 0.5 V peak.
Table 96.
Operating conditions
Symbol
TA
Parameter
Min.
Max.
Unit
–40
85
°C
Ambient operating temperature
Figure 60 shows an ASK modulated signal, from the VCD to the LRIS64K. The test
condition for the AC/DC parameters are:
●
Close coupling condition with tester antenna (1mm)
●
LRIS64K performance measured at the tag antenna
Figure 60. LRIS64K synchronous timing, transmit and receive
A
B
tRFF
tRFR
fCC
tRFSBL
tMAX
tMIN CD
AI06680
Doc ID 15336 Rev 11
93/100
Part numbering
27
LRIS64K
Part numbering
Table 97.
Ordering information scheme
Example:
LRIS64K -
SBN18/ 2
Device type
LRIS64K (long-range tag with 64 Kbit EEPROM)
Package
SBN18 = 180 µm ± 15 µm bumped and sawn wafer on 8-inch frame
Tuning capacitance
2= 27.5 pF
For a list of available options (speed, package, etc.) or for further information on any aspect
of this device, please contact your nearest ST sales office.
94/100
Doc ID 15336 Rev 11
LRIS64K
Anticollision algorithm
Appendix A
Anticollision algorithm
The following pseudocode describes how anticollision could be implemented on the VCD,
using recursivity.
A.1
Algorithm for pulsed slots
function
function
function
function
push (mask, address); pushes on private stack
pop (mask, address); pops from private stack
pulse_next_pause; generates a power pulse
store(LRIS64K_UID); stores LRIS64K_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 ; LRIS64K is inventoried
then
store (LRIS64K_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
Doc ID 15336 Rev 11
95/100
CRC
LRIS64K
Appendix B
B.1
CRC
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 LRIS64K and
from LRIS64K to VCD.
Table 98.
CRC definition
CRC definition
CRC type
ISO/IEC 13239
Length
16 bits
Polynomial
16
X
+
X12
+
X5
+ 1 = 8408h
Direction
Preset
Residue
Backward
FFFFh
F0B8h
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 2 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
#define
#define
POLYNOMIAL0x8408//
PRESET_VALUE0xFFFF
CHECK_VALUE0xF0B8
x^16 + x^12 + x^5 + 1
#define
#define
#define
NUMBER_OF_BYTES4// Example: 4 data bytes
CALC_CRC1
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)
{
96/100
Doc ID 15336 Rev 11
LRIS64K
CRC
number_of_databytes = NUMBER_OF_BYTES;
}
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);
//
stream
//
}
else
{
if
{
current_crc_value is now ready to be appended to the data
(first LSByte, then MSByte)
// check CRC
(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);
}
}
}
Doc ID 15336 Rev 11
97/100
Application family identifier (AFI)
Appendix C
LRIS64K
Application family identifier (AFI)
The AFI (application family identifier) represents the type of application targeted by the VCD
and is used to extract from all the LRIS64K present only the LRIS64K meeting the required
application criteria.
It is programmed by the LRIS64K issuer (the purchaser of the LRIS64K). 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 99.
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 99.
AFI coding(1)
AFI
Most
significant
nibble
AFI
Least
significant
nibble
‘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, etc.
'2
'‘0’, ‘Y’
Financial
IEP, banking, retail, etc.
'3
'‘0’, ‘Y’
Identification
Access control, etc.
'4
'‘0’, ‘Y’
Telecommunication
Public telephony, GSM, etc.
‘5’
‘0’, ‘Y’
Medical
'6
'‘0’, ‘Y’
Multimedia
'7
'‘0’, ‘Y’
Gaming
8
'‘0’, ‘Y’
Data storage
'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
Meaning
VICCs respond from
1. X = '1' to 'F', Y = '1' to 'F'
98/100
Doc ID 15336 Rev 11
Examples / Note
Internet services, etc.
Portable files, etc.
LRIS64K
Revision history
Revision history
Table 100. Document revision history
Date
Revision
Changes
26-Jan-2009
1
Initial release.
05-Feb-2009
2
TSSOP8 package removed. Wafer silhouette added on page 1.
13-Feb-2009
3
Device programming time corrected.
02-Apr-2009
4
Revision history corrected (revision 3 added).
Figure 2: UFDFPN8 connections corrected.
16-Jul-2009
5
Document status promoted from Target specification to Preliminary
data.
VESD modified in Table 93: Absolute maximum ratings.
17-Sep-2009
6
VESD modified in Table 93: Absolute maximum ratings.
25-Aug-2010
7
Updated Features on page 1.
Removed all references to packages.
Removed Figure 2: UFDFPN8 connections.
Updated Section 4: Initial delivery state on page 18.
Updated Figure 3, Figure 4, Table 94, and Table 95.
Updated storage time (tSTG) in Table 93: Absolute maximum ratings
on page 91.
05-Oct-2010
8
Document classification changed to public.
Updated DSFID value in Section 4: Initial delivery state
08-Nov-2010
9
Updated document status from preliminary status to public.
19-Sep-2011
10
Modified Section 1: Description
Updated disclaimer on last page.
27-Oct-2011
11
Updated footnote (2) of Table 94: RF AC characteristics.
Doc ID 15336 Rev 11
99/100
LRIS64K
Please Read Carefully:
Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the
right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any
time, without notice.
All ST products are sold pursuant to ST’s terms and conditions of sale.
Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no
liability whatsoever relating to the choice, selection or use of the ST products and services described herein.
No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this
document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products
or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such
third party products or services or any intellectual property contained therein.
UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS
OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS EXPRESSLY APPROVED IN WRITING BY TWO AUTHORIZED ST REPRESENTATIVES, ST PRODUCTS ARE NOT
RECOMMENDED, AUTHORIZED OR WARRANTED FOR USE IN MILITARY, AIR CRAFT, SPACE, LIFE SAVING, OR LIFE SUSTAINING
APPLICATIONS, NOR IN PRODUCTS OR SYSTEMS WHERE FAILURE OR MALFUNCTION MAY RESULT IN PERSONAL INJURY,
DEATH, OR SEVERE PROPERTY OR ENVIRONMENTAL DAMAGE. ST PRODUCTS WHICH ARE NOT SPECIFIED AS "AUTOMOTIVE
GRADE" MAY ONLY BE USED IN AUTOMOTIVE APPLICATIONS AT USER’S OWN RISK.
Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void
any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any
liability of ST.
ST and the ST logo are trademarks or registered trademarks of ST in various countries.
Information in this document supersedes and replaces all information previously supplied.
The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.
© 2011 STMicroelectronics - All rights reserved
STMicroelectronics group of companies
Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan Malaysia - Malta - Morocco - Philippines - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America
www.st.com
100/100
Doc ID 15336 Rev 11