This is information on a product in full production.
June 2015 DocID027794 Rev 2 1/64
1
ST25TA02K-P
NFC Forum Type 4 Tag IC with 2-Kbit EEPROM and
General Purpose Digital Output
Datasheet - production data
Features
Contactless interface
•NFC Forum Type 4 Tag
•ISO/IEC 14443 Type A
•106 Kbps data rate
•Internal tuning capacitance: 50 pF
Memory
•256-byte (2-kbit) EEPROM
•Support of NDEF data structure
•Data retention: 200 years
•Endurance: 1 million erase-write cycles
•Read up to 255 bytes in a single command
•Write up to 54 bytes in a single command
•Chaining capability
•7 bytes unique identifier (UID)
•128 bits passwords protection
•20 bits event counter with anti-tearing
•RF field detect
Package
•UFDFPN8 ECOPACK®2
•UFDFPN5 ECOPACK®2
Digital pad
•GPO: Configurable General Purpose Output
(enabling no DC consumption CMOS Output
buffer).
Description
The ST25TA02K-P device is a dynamic
NFC/RFID tag IC with a General Purpose Digital
Output.
It embeds an EEPROM memory. It can be
operated from a 13.56 MHz RFID reader or an
NFC phone.
The ST25TA02K-P is an NFC Forum Type 4 Tag;
it communicates using the ISO/IEC 14443 Type A
protocol.
UFDFPN8
Wafer
UFDFPN5
www.st.com
Contents ST25TA02K-P
2/64 DocID027794 Rev 2
Contents
1 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1 Functional modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.1 Tag mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2 Signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.1 Antenna coil (AC0, AC1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.2 Ground (VSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.3 GPO Supply voltage (VDCG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.3.1 Operating supply voltage VDCG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.2 Power-up conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 General Purpose Output (GPO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4.1 Session Open configuration (GPO field = 0x10 or 0x90) . . . . . . . . . . . . 13
2.4.2 WIP Writing in Progress configuration (GPO field = 0x20 or 0xA0) . . . . 14
2.4.3 MIP NDEF Message writing in Progress configuration
(GPO field = 0x30 or 0xB0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.4 INT Interrupt configuration (GPO field = 0x40 or 0xC0) . . . . . . . . . . . . . 16
2.4.5 State Control configuration (GPO field = 0x50 or 0xD0) . . . . . . . . . . . . 17
2.4.6 RF busy configuration (GPO field = 0x60 or 0xE0) . . . . . . . . . . . . . . . . 18
2.4.7 Field detect configuration (GPO field = 0x70 or 0xF0) . . . . . . . . . . . . . . 19
3 ST25TA02K-P memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1 Memory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.1 File identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.2 CC file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.3 NDEF file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.4 System file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.2 Read and write access rights to the NDEF File . . . . . . . . . . . . . . . . . . . . 23
3.2.1 State of the Read and Write access rights . . . . . . . . . . . . . . . . . . . . . . . 23
3.2.2 Changing the read access right to NDEF files . . . . . . . . . . . . . . . . . . . . 24
3.2.3 Changing the write access right to NDEF files . . . . . . . . . . . . . . . . . . . 25
3.3 Access right life time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.4 NDEF file passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.5 Read/Write counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
DocID027794 Rev 2 3/64
ST25TA02K-P Contents
4
4 Communication mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1 Master and slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5 RF command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.1 Structure of the command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2 I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2.1 C-APDU: payload format of a command . . . . . . . . . . . . . . . . . . . . . . . . 31
5.2.2 R-APDU: payload format of a response . . . . . . . . . . . . . . . . . . . . . . . . 31
5.3 R-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.4 S-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.5 CRC of the RF frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.6 NFC Forum Type 4 Tag protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.6.1 Commands set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.6.2 Status and error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.6.3 NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . 36
5.6.4 Capability Container Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.6.5 NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.6.6 System File Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.6.7 ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.6.8 UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.7 ISO/IEC 7816-4 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.7.1 Verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.7.2 Change Reference Data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.7.3 Enable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . . 43
5.7.4 Disable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . 44
5.8 ST Proprietary command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.8.1 ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.8.2 EnablePermanentState command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.9 Specific RF command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.9.1 Anticollision command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.9.2 RATS command and ATS response . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.9.3 PPS command & response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6 RF device operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1 Anticollision and Device Activation command set for the RF interface . . 51
6.2 Open an RF session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Contents ST25TA02K-P
4/64 DocID027794 Rev 2
6.3 Close an RF session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.4 Applicative command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7 Functional procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.1 Selection of an NDEF message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.2 Reading of an NDEF message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.3 Reading a locked NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.4 Locking an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.5 Unlocking an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.6 Reaching the read-only state for an NDEF file . . . . . . . . . . . . . . . . . . . . . 53
7.7 Changing a File type Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8 UID: Unique identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
9 Maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
10 GPO characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
11 GPO parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
12 RF electrical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
13 Package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
13.1 UFDFN8 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
13.2 UFDFPN5 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
14 Part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
15 Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
DocID027794 Rev 2 5/64
ST25TA02K-P List of tables
6
List of tables
Table 1. Signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 2. Functional mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 3. File identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 4. CC file layout for 1 NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 5. NDEF file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 6. Field list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 7. Details about the GPO field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 8. Details about the Counter config field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 9. Read access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 10. Write access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 11. RF command sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 12. I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 13. PCB field of the I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 14. C-APDU format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 15. R-APDU format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 16. R-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 17. R-Block detailed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 18. S-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 19. S-Block detailed format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 20. Command set overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 21. Status code of the ST25TA02K-P. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 22. Error code of the ST25TA02K-P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 23. C-APDU of the NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 24. R-APDU of the NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 25. C-APDU of the Capability Container Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 26. R-APDU of the Capability Container Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 27. C-APDU of the NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 28. R-APDU of the NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 29. C-APDU of the System File Select command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 30. R-APDU of the System File Select command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 31. C-APDU of the ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 32. R-APDU of the ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 33. C-APDU of the UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 34. R-APDU of the UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 35. Verify command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 36. R-APDU of the Verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 37. Change reference data command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 38. R-APDU of the Change Reference Data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 39. Enable Verification Requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Table 40. R-APDU of the Enable Verification Requirement command. . . . . . . . . . . . . . . . . . . . . . . . 44
Table 41. Disable Verification Requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Table 42. R-APDU of the Disable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . . . 45
Table 43. C-APDU of the ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 44. R-APDU of the ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 45. EnablePermanentState command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 46. R-APDU table of the EnablePermanentState command . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 47. Commands issues by the RF host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 48. Example of anticollision sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
List of tables ST25TA02K-P
6/64 DocID027794 Rev 2
Table 49. RATS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 50. Conversion from FDSI to FSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 51. ATS response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 52. PPS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 53. Ascending and descending data rate coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 54. PPS response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 55. UID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 56. Absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 57. GPO Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 58. DC characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 59. GPO AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 60. GPO timings measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 61. Default operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 62. RF characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 63. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat
package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 64. UFDFPN5 - 5-lead, 1.7 × 1.4 mm, 0.55 mm thickness
package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Table 65. Ordering information scheme for packaged devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 66. Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
DocID027794 Rev 2 7/64
ST25TA02K-P List of figures
7
List of figures
Figure 1. ST25TA02K-P block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 2. Applicative schematic example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 3. 8-pin package connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 4. 5-pin package connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 5. GPO configured as Session Open (GPO field = 0x10 or 0x90) . . . . . . . . . . . . . . . . . . . . . 13
Figure 6. GPO configured as WIP (GPO field = 0x20 or 0xA0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 7. GPO configured as MIP (GPO field = 0x30 or 0xB0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 8. GPO configured as INT (GPO field = 0x40 or 0xC0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 9. GPO configured as State Control (GPO field = 0x50 or 0xD0). . . . . . . . . . . . . . . . . . . . . . 17
Figure 10. GPO configured as RF busy (GPO field = 0x60 or 0xE0). . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 11. Field detect (GPO field = 0x70 or 0xF0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 12. Changing the read access right to an NDEF file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 13. Changing the write access right to an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 14. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch
dual flat package outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 15. UFDFPN5 - 5-lead, 1.7 × 1.4 mm, 0.55 mm thickness package outline. . . . . . . . . . . . . . . 61
Functional description ST25TA02K-P
8/64 DocID027794 Rev 2
1 Functional description
The ST25TA02K-P device is a dynamic NFC/RFID tag that can be accessed from the RF
interface. The RF interface is based on the ISO/IEC 14443 Type A standard. The
ST25TA02K-P is compatible with the NFC Forum Type 4 Tag specifications and supports all
corresponding commands.
Figure 1 displays the block diagram of the ST25TA02K-P device.
Figure 1. ST25TA02K-P block diagram
069
5)LQWHUIDFH
EDVHGRQ
,62,(&
7\SH$
VWDQGDUG
*32
I9'&*
$&
$&
*32
966
3RZHU
PDQDJHPHQW
XQLW
h/ΘƐLJƐƚĞŵ
ĂƌĞĂ
hƐĞƌŵĞŵŽƌLJ
$QDORJ)URQWHQG
EDVHGRQ
,62,(&
7\SH$VWDQGDUG
,QWHUQDOWXQLQJ
FDSDFLWDQFH
'LJLWDOXQLW
9'&*
1)&)RUXP
7\SH7DJ
SURWRFRO
DocID027794 Rev 2 9/64
ST25TA02K-P Functional description
Figure 2. Applicative schematic example
1. Decoupling capacitor
Figure 3. 8-pin package connections
1. See Package mechanical data section for package dimensions, and how to identify pin 1.
Figure 4. 5-pin package connections
1. See Package mechanical data section for package dimensions, and how to identify pin 1.
069
677$.3 0LFURFRQWUROOHU
Q)
9'&*
966
9''
*32 ,2
$&
$&
5)
DQWHQQD
Table 1. Signal names
Signal name Function Direction
AC0, AC1 Antenna coils -
VDCG Supply voltage for GPO Power
VSS Ground -
GPO Interrupt output CMOS output
069
1&
9
*32
$&
$&
1&
966
1&
'&*
-36
!# !#
'0/
633 633
4OPVIEW
MARKINGSIDE
"OTTOMVIEW
PADSSIDE
!"#$
89:7
6$#'
Functional description ST25TA02K-P
10/64 DocID027794 Rev 2
1.1 Functional modes
The ST25TA02K-P has just one functional mode available (see Table 2).
1.1.1 Tag mode
The ST25TA02K-P is supplied by the RF field and can communicate with an RF host (RFID
reader or an NFC phone). The User memory can be accessed by the RF commands.
Table 2. Functional mode
Mode Supply source Comments
Tag mode RF field only The RF interface is connected, GPO driver
request an external supply to operate.
DocID027794 Rev 2 11/64
ST25TA02K-P Signal descriptions
2 Signal descriptions
2.1 Antenna coil (AC0, AC1)
These inputs are used to connect the device to an external coil exclusively. It is advised not
to connect any other DC or AC path to AC0 or AC1.
When correctly tuned, the coil is used to access the device using NFC Forum Type 4
commands.
2.2 Ground (VSS)
VSS, when connected, is the reference for the VDCG supply voltage for all pads, even AC0
and AC1.
2.3 GPO Supply voltage (VDCG)
This pin can be connected to an external DC supply voltage. It only supplies the GPO driver
block.
2.3.1 Operating supply voltage VDCG
Prior to checking ST25TA02K-P GPO, a valid and stable VDCG voltage within the specified
[VDCG(min), VDCG(max)] range must be applied.
To maintain a stable DC supply voltage, it is recommended to decouple the VDCG line with
suitable capacitors (usually of the order of 10 nF and 100 pF) close to the VDCG/VSS
package pins.
This voltage must remain stable and valid until the end of the GPO usage by the
ST25TA02K-P.
2.3.2 Power-up conditions
The VDCG rise time must not vary faster than 1 V/µs.
Signal descriptions ST25TA02K-P
12/64 DocID027794 Rev 2
2.4 General Purpose Output (GPO)
The GPO pad is a CMOS pad, with default polarity set to 0.
This pad is a configurable output signal, driven to the alternate polarity when configured
event occurs. Its behavior is consistent with the RF session activated and with the mode
chosen by the user.
The user can select one of these configurations(a):
•SessionOpen: an RF session is ongoing.
•MIP (NDEF Message updating In Progress): the RF host is writing an NDEF length
different from 0x0000. This mode can be used to detect when the RF host changes the
NDEF message as defined by the NFC Forum.
•WIP (Writing In Progress): the ST25TA02K-P is executing a writing operation.
•INT (interrupt): the RF host can force the ST25TA02K-P to send an alternate pulse on
the GPO pin.
•State mode: the RF host can control the state of the GPO pad during the RF session.
•RF busy: an RF host is communicating with the ST25TA02K-P.
•Field detection: the RF field is sufficient to establish an RF communication with the
ST25TA02K-P.
GPO configuration byte can be locked, by setting its Most Significant Bit to 1 (1xxx 0000 b).
Once locked, this byte cannot be changed anymore.
a. See Table 60: GPO timings measurement for more details.
DocID027794 Rev 2 13/64
ST25TA02K-P Signal descriptions
2.4.1 Session Open configuration (GPO field = 0x10 or 0x90)
When the GPO is configured as "Session Open", it goes to the high state when an RF
session is ongoing (see Figure 5).
An RF session is taken when ST25TA02K-P receives a valid Select Application. The
session is released when:
•ST25TA02K-P receives a valid Deselect command
•RF field becomes OFF
GPO is driven high after a delay (1.) when the session is open.
GPO is released after a delay (2.) when the session is released.
Figure 5. GPO configured as Session Open (GPO field = 0x10 or 0x90)
1. CmdEOFtoGPhigh (RF command End of frame to GPORF Session pad high)
2. CmdEOFtoGPlow (RF command End of frame to GPORF Session pad low)
069
5)6HVVLRQ 5)6HVVLRQ
5)FKDQQHO
*32DV6HVVLRQ2SHQ
$QWLFROOLVLRQ
1'()VHOHFW
'HVHOHFW
$QWLFROOLVLRQ
1'()VHOHFW
'HVHOHFW
Signal descriptions ST25TA02K-P
14/64 DocID027794 Rev 2
2.4.2 WIP Writing in Progress configuration (GPO field = 0x20 or 0xA0)
When the GPO is configured as "WIP", it goes to the high state during an RF writing
operation (see Figure 6).
During an RF session, when ST25TA02K-P updates a file, GPO is driven high after a delay
(1.) following the beginning of the correspondent UpdateBinary command execution.
GPO will remain high during the writing time (2.), before being released.
Figure 6. GPO configured as WIP (GPO field = 0x20 or 0xA0)
1. CmdEOFtoGPhigh (RF Command End of frame to GPO high)
2. Writing time duration
069
8SGDWH
FRPPDQG
$Q\RWKHU
FRPPDQG
5)FKDQQHO
*32DV:,3
(QGRIZULWLQJ
RSHUDWLRQ
DocID027794 Rev 2 15/64
ST25TA02K-P Signal descriptions
2.4.3 MIP NDEF Message writing in Progress configuration
(GPO field = 0x30 or 0xB0)
When the GPO is configured as MIP, its state goes to the high state when the RF host writes
the NDEF length to another value than 0x0000 (see Figure 7).
During an RF session, when ST25TA02K-P changes an NDEF file and updates the NDEF
length with a value different from 0x0000, GPO is driven high after a delay (1.) following the
beginning of the correspondent UpdateBinary command execution.
GPO will remain high during the writing time (2.), before being released.
Figure 7. GPO configured as MIP (GPO field = 0x30 or 0xB0)
1. CmdEOFtoGPhigh (RF command End of frame to GPO high)
2. Writing time duration
069
$Q\RWKHU
FRPPDQG
8SGDWHWKH1'()
OHQJWK
[
5)FKDQQHO
*32DV0,3
677$[.3
UHVSRQVH
Signal descriptions ST25TA02K-P
16/64 DocID027794 Rev 2
2.4.4 INT Interrupt configuration (GPO field = 0x40 or 0xC0)
The RF host can send a positive pulse on the GPO pad. The GPO pad goes to high state at
the end of the command and goes to the low state at the end of the ST25TA02K-P response
(see Figure 8).
During an RF session, when ST25TA02K-P receives a valid Interrupt command,
ST25TA02K-P GPO pin is driven high after (1.). Then GPO pin is released at the end of the
response (2.).
Figure 8. GPO configured as INT (GPO field = 0x40 or 0xC0)
1. CmdEOFtoGPhigh (RF command End of frame to GPO high)
2. RespEOFtoGPlow
069
6HQG
,QWHUUXSW
*32DV,17
$Q\RWKHU
RSHUDWLRQ
5)FKDQQHO
677$[.3
UHVSRQVH
DocID027794 Rev 2 17/64
ST25TA02K-P Signal descriptions
2.4.5 State Control configuration (GPO field = 0x50 or 0xD0)
When the GPO is configured as State Control, the RF host can control the state of the GPO
by sending a dedicated command (see Figure 9).
During an RF session, the ST25TA02K-P can control the GPO pin. After receiving a valid
reset GPO command, GPO pin is driven high after a delay (1.). GPO will be released after a
valid Set command or after a Power off.
Figure 9. GPO configured as State Control (GPO field = 0x50 or 0xD0)
1. CmdEOFtoGPhigh (RF Reset GPO command End of frame to GPO high)
2. CmdEOFtoGPlow (RF Set GPO command End of frame to GPO low)
069
5HVHW*32
FRPPDQG
$Q\RWKHU
FRPPDQG
6HW*32
FRPPDQG
5)FKDQQHO
*32DV
6WDWH&RQWURO
Signal descriptions ST25TA02K-P
18/64 DocID027794 Rev 2
2.4.6 RF busy configuration (GPO field = 0x60 or 0xE0)
When the GPO is configured as RF busy, the GPO goes to the high state, both when the
ST25TA02K-P is processing an RF command or when an RF session is ongoing (see ).
When an RF field is present, GPO is driven high after a delay (1.) when ST25TA02K-P
detects the first command. If the RF session is ongoing and ST25TA02K-P receives a not-
supported command, GPO remains high. It will be released only at the end of the RF
session, after (2.).
Figure 10. GPO configured as RF busy (GPO field = 0x60 or 0xE0)
1. CmdSOFtoGPhigh (RF command Start of frame to GPO high)
2. CmdEOFtoGPlow (RF command End of frame to GPO low)
069
5)FRPPDQGQRW
VXSSRUWHG
6HQV5HT
6HQV5HV 5)FRPPDQG
5)FKDQQHO
*32DV5)EXV\
6/3B5(4RU
6'(6RU
EDGFRPPDQGRU
5))LHOG2))
DocID027794 Rev 2 19/64
ST25TA02K-P Signal descriptions
2.4.7 Field detect configuration (GPO field = 0x70 or 0xF0)
When the GPO is configured as Field detect, the GPO goes to the high state when
ST25TA02K-P detects an RF Field (see Figure 11).
When an RF field is present, GPO is driven high after a delay when ST25TA02K-P detects
this field. Whatever the activity during the RF field detection (communication with the reader
or not), GPO will stay high. It will be released when ST25TA02K-P leaves the RF field.
Figure 11. Field detect (GPO field = 0x70 or 0xF0)
06Y9
+PLQ
*32
W)'(721
5)ILHOG
9'&*
W)'(72))
966
ST25TA02K-P memory management ST25TA02K-P
20/64 DocID027794 Rev 2
3 ST25TA02K-P memory management
3.1 Memory structure
The ST25TA02K-P supports the NDEF Tag Application as defined in the NFC Forum Type 4
Tag. The ST25TA02K-P is composed of three files:
•One Capability Container file
•One NDEF file
•One System file: this file is an ST-proprietary file
The System file contains some information on the configuration of the ST25TA02K-P
device. The CC file gives some information about the ST25TA02K-P itself and the NDEF
file. The NDEF file contains the User data.
3.1.1 File identifier
The file identifier is the value used in the Select command to select a file.
3.1.2 CC file layout
The CC file gives some information about the ST25TA02K-P and the NDEF file. This file is a
read-only file for the RF host and cannot be modified by issuing a write command.
The T field, Read Access and Write Access fields can be changed by the RF host by issuing
a specific process (refer to Section 7: Functional procedures).
Table 3. File identifier
File identifier Meaning
0xE101 System file
0xE103 CC file
0x0001 NDEF file
Table 4. CC file layout for 1 NDEF file
File offset Meaning Value Comments
0x0000 Length CC file 0x000F 15 bytes
0x0002 Mapping version(1) 0x20 or 0x10 V 2.0 or V 1.0
0x0003 Maximum number of bytes that can be read 0x00FF 255 bytes
0x0005 Maximum number of bytes that can be written 0x0036 54 bytes
DocID027794 Rev 2 21/64
ST25TA02K-P ST25TA02K-P memory management
3.1.3 NDEF file layout
The NDEF file contains the NDEF message which contains the User data. The RF host can
read and write data inside the file. The first two bytes named NDEF Message Length define
the size of the NDEF message. The NDEF Message Length shall be managed by the
application and the ST25TA02K-P device does not check if its value is relevant vs the data
written by the RF host. The ST25TA02K-P device uses the NDEF Message Length, e. g. the
standard read can be processed only inside the NDEF message; otherwise, the
ST25TA02K-P device returns an error code. For more details about the read command,
refer to Section 5.6.7: ReadBinary command.
0x0007
NDEF file control TLV
0x04 (2) T field
0x0008 0x06 L field
0x0009 0x0001 FileID
0x000B 0x0100 Maximum NDEF
file size in Byte
0x000D 0x00 (2) Read access
0x000E 0x00 (2) Write access
1. According to the reader command format ST25TA02K-P will automatically align to the corresponding NFC
Forum version.
2. Delivery state.
Table 4. CC file layout for 1 NDEF file (continued)
File offset Meaning Value Comments
Table 5. NDEF file layout
File offset Byte 0 Byte 1 Byte 2 Byte 3
0x0000 NDEF message length User data User data
0x0004 User data User data User data User data
... ... ... ... ...
... ... ... ... ...
... ... ... ... ...
0x00FC ... ... ... User data
ST25TA02K-P memory management ST25TA02K-P
22/64 DocID027794 Rev 2
3.1.4 System file layout
The system file specifies the configuration of the ST25TA02K-P. Table 6 lists the different
fields.
Table 6. Field list
File offset Field name Number of
bytes Read access Write access Delivery state
0x0000 Length system file 2 yes - 0x0012
0x0002 GPO Config 1 yes yes(1)
1. Configuration bytes can be locked by setting the Most significant bit to 1. Once locked, these bytes cannot
be changed anymore.
0x70(2)
2. Field detect as default GPO configuration.
0x0003 Event Counter
Config 1 yes yes(1) 0x00
0x0004 20 bits counter (MS
nibble 0x0) 3 yes none 0x000000
0x0007 Product version 1 yes none 0x13(3)
3. ST reserved.
0x0008 UID 7 yes none 0x02A2 xx xx
xx xx xx (4)
4. x values are defined by ST to ensure UID unicity.
0x000F Memory Size - 1 2 yes none 0x00FF
0x0011 Product Code 1 yes none 0xA2
Table 7. Details about the GPO field
File offset b7 b6-b4 b3-b0
0x0002
GPO config lock bit:
0b0: unlocked
0b1: locked
GPO configuration:
0b000: Not used
0b001: Session opened
0b010: WIP
0b011: MIP
0b100: Interrupt
0b101: State Control
0b110: RF Busy
0b111: Field Detect
0b0000 ST Reserved
DocID027794 Rev 2 23/64
ST25TA02K-P ST25TA02K-P memory management
Warning: When GPO config lock bit is set to "1", the whole byte cannot
be changed anymore.
3.2 Read and write access rights to the NDEF File
The NDEF file can be locked for read or write accesses. It is also protected by a 128-bit
password that the host shall present before accessing the NDEF file. There are two 128-bit
passwords, one for the read access and the other one for the write access.
An NDEF file can be permanently locked for read or write accesses. Thus, the host cannot
access the NDEF file.
The read password shall be sent to the ST25TA02K-P device before reading a read-locked
NDEF file.
The write password shall be present on the ST25TA02K-P device before writing a write-
locked NDEF file. The write password shall be sent to change the read or write access. The
read or write access right is defined for the NDEF file.
3.2.1 State of the Read and Write access rights
Two bytes in the CC file are used to define the Read and Write access rights to the NDEF
file. For more details, refer to Section 3.1.2: CC file layout.
Table 8. Details about the Counter config field
File offset b7 b6-b2 b1 b0
0x0003
Counter config lock bit:
0b0: unlocked
0b1: locked
0b00000: ST reserved
Counter enable:
0b0: disable
0b1: enable
Counter increment:
0b0: on Read
0b1: on Write
Table 9. Read access right
Value Meaning
0x00 Read access without any security
0x80 Locked (1)
1. The read password shall be sent before reading in the NDEF file.
0xFE Read not authorized
ST25TA02K-P memory management ST25TA02K-P
24/64 DocID027794 Rev 2
The state 0xFF and 0xFE cannot be changed by using the Read or Write passwords.
3.2.2 Changing the read access right to NDEF files
The state diagram on Figure 12 shows how to change the access right to read an NDEF file.
Figure 12. Changing the read access right to an NDEF file
1. See the procedure to lock the read access (Section 7.4: Locking an NDEF file).
2. See the procedure to unlock the read access (Section 7.5: Unlocking an NDEF file).
3. See the procedure to permanently lock the read access (Section 7.6: Reaching the read-only state for an
NDEF file).
4. Proprietary state, not defined by NFC Forum Type 4 Tag.
Table 10. Write access right
Value Meaning
0x00 Write access without any security
0x80 Locked (1)
1. The write password shall be sent before writing in the NDEF file.
0xFF Write not authorized
069
3HUPDQHQWO\ORFNWKH1'()ILOH
[
[ [)(
/RFNWKH1'()ILOH
8QORFNWKH1'()ILOH
DocID027794 Rev 2 25/64
ST25TA02K-P ST25TA02K-P memory management
3.2.3 Changing the write access right to NDEF files
The state diagram on Figure 13 shows how to change the write access right to an NDEF file.
Figure 13. Changing the write access right to an NDEF file
1. See the procedure to lock the write access.
2. See the procedure to unlock the write access.
3. See the procedure to permanently lock the write access (Section 7.6: Reaching the read-only state for an
NDEF file).
4. Proprietary state, not defined by NFC Forum Type 4 Tag.
3.3 Access right life time
The access right life time is validated while the NDEF file is selected or until the end of the
RF session. Once the read or write access right is granted, the host can send one or more
ReadBinary or UpdateBinary commands.
At the end of a session or when the host selects another file, the read and write access
rights are initialized.
3.4 NDEF file passwords
The NDEF file passwords protect the read or write access from an RF interface from/to an
NDEF file.
Two NDEF file passwords are available for each NDEF file:
•Read password
•Write password
The length of a password is 128 bits (16 bytes).
Note: The delivery state for all passwords = 0x00000000000000000000000000000000.
069
[
[ [))
/RFNWKH1'()ILOH
8QORFNWKH1'()ILOH
3HUPDQHQWO\ORFNWKH1'()ILOH
ST25TA02K-P memory management ST25TA02K-P
26/64 DocID027794 Rev 2
3.5 Read/Write counter
A 20 bits counter can track the read or write events on the NDEF file.
It benefits from an anti-tearing mechanism, that ensures the consistency of the counter,
even if there has been an electrical problem during its increment.
The value of the Read/Write counter can be checked by any application, by reading suitable
bytes in System file (see Section 3.1.4).
If enabled, the Read/Write counter will be incremented on first event (exclusively Read or
Write) which is performed on the NDEF File, inside an RF session (an RF session is entered
when ST25TA02K-P receives a valid "Select Application" command).
The counter is reset when it is disabled.
Apart from these procedures, there is no way to act on the value of this counter.
The Read/Write counter can be configured through a specific byte in System file (see
Section 3.1.4).
This configuration byte allows to:
•Enable or disable this counter
•Define if the counter must be incremented on a read or write sequence
•Definitively lock this configuration byte
Warning: Once this configuration byte is locked, it cannot be changed
anymore: the counter will behave accordingly.
If enabled, the Read/Write counter will have an impact on the execution time of the event
which is countered: the counter increment needs some write cycles of specific EEPROM
cells automatically managed by ST25TA02K-P, which increase the total time before the
response is sent to the reader.
As a consequence, an S(WTX) request can be issued on the command that will increment
the counter (see Section 5.4: S-Block format).
DocID027794 Rev 2 27/64
ST25TA02K-P Communication mechanism
58
4 Communication mechanism
This section describes the principle of communication between an RF host and the
ST25TA02K-P device.
4.1 Master and slave
The ST25TA02K-P acts as a slave device on the RF channel and therefore waits for a
command from the RF host before sending its response.
The RF host shall generate the RF field and the RF commands.
RF command sets ST25TA02K-P
28/64 DocID027794 Rev 2
5 RF command sets
This section describes the ST25TA02K-P command sets that can be issued by the RF host.
There are three command families:
•the NFC Forum Type 4 Tag command set
•the ISO/IEC 7816-4 command set
•the proprietary command set
The NFC Forum Type 4 Tag command set and the ISO/IEC 7816-4 command set use the I-
Block format. For more details about the I-Block format, refer to Section 5.2: I-Block format.
Two other command formats exist:
•the commands using the R-Block format
•the commands using the S-Block format
For more details about these formats, refer to the corresponding sections: Section 5.3: R-
Block format and Section 5.4: S-Block format.
This section gives a brief description of the RF host commands. The format of these
command sets is the I-Block format.
Table 11 lists the RF command sets.
Table 11. RF command sets
Family
command set Command name Class byte Instruction code Brief description
NFC Forum
Type 4 Tag
NDEF Tag Application Select 0x00 0xA4 NDEF Tag Application
Select
CC select 0x00 0xA4 Select the CC file
NDEF select 0x00 0xA4 Select the NDEF file
System select 0x00 0xA4 Select the system file
ReadBinary 0x00 0xB0 Read data from file
UpdateBinary 0x00 0xD6 Write or erase data to a
NDEF file
ISO/IEC 7816-4
Verify 0x00 0x20
Checks the right access of
a NDEF file or sends a
password
ChangeReferenceData 0x00 0x24 Change a Read or write
password
EnableVerificationRequirement 0x00 0x28 Activate the password
security
DisableVerificationRequirement 0x00 0x26 Disable the password
security
ST Proprietary EnablePermanentState 0xA2 0x28 Enables the Read Only or
Write Only security state
ST Proprietary ExtendedReadBinary 0xA2 0xB0 Read data from file
DocID027794 Rev 2 29/64
ST25TA02K-P RF command sets
58
5.1 Structure of the command sets
The exchange of data between the RF host and the ST25TA02K-P uses three kinds of data
formats, called blocks:
•I-Block (Information block): to exchange the command and the response
•R-Block (Receive ready block): to exchange positive or negative acknowledgement
•S-Block (Supervisory block): to use either the Deselect command or the Frame Waiting
eXtension (WTX) command or response
This section describes the structure of I-Block, R-block and S-Block. This format is used for
the application command set.
5.2 I-Block format
The I-Block is used to exchange data between the RF host and the ST25TA02K-P. It is
composed of three fields. Table 12 details the I-Block format.
Table 12. I-Block format
Name
SoD Payload EoD
PCB DID - CRC
Length 1 byte 1 byte 1 to 251 bytes 2 bytes
PCB field
DID field (optional)
RF host to ST25TA02K-P: C-APDU
ST25TA02K-P to RF host: R-APDU
2 CRC bytes
RF command sets ST25TA02K-P
30/64 DocID027794 Rev 2
Note: Block numbering rules:
When the RF host sends a command to the ST25TA02K-P the format of the payload is the
C-APDU.
When the ST25TA02K-P sends a command to the RF host, the format of the payload is the
R-APDU.
Table 13. PCB field of the I-Block format
b7-b6b5b4b3b2b1b0
0b00 0 0 X 0 1 X
I-Block
RFU
Must be set to 0
DID field is present, if bit is set
Must be set to 0
Must be set to 1
Block number(1)
1. Follow ISO 14443_4 Block numbering rules (see note)
Reader rules:
Rule A: The Reader block number shall be initialized to 0.
Rule B: When an I-block or an R(ACK) block with a block number equal to
the current block number is received, the Reader shall toggle the
current block number before optionally sending a block to the
ST25TA02K-P.
ST25TA02K-P rules:
Rule C. The ST25TA02K-P block number shall be initialized to 1 at
activation.
Rule D. When an I-block is received, the ST25TA02K-P shall toggle its block
number before sending a block.
Note: The ST25TA02K-P may check if the received block number is not in
compliance with Reader rules to decide neither to toggle its internal block
number nor to send a response block.
Rule E. When an R(ACK) block with a block number not equal to the current
ST25TA02K-P block number is received, the ST25TA02K-P shall
toggle its block number before sending a block.
Note: There is no block number toggling when an R(NAK) block is received.
DocID027794 Rev 2 31/64
ST25TA02K-P RF command sets
58
5.2.1 C-APDU: payload format of a command
The C-APDU format is used by the RF host to send a command to the ST25TA02K-P.
Table 14 describes its format.
5.2.2 R-APDU: payload format of a response
the ST25TA02K-P uses the I-Block format to reply to a command which used the I-Block
format. This format is described in Table 15.
Table 14. C-APDU format
Name
Payload field
CLA INS P1 P2 LCData Le
Length 1 byte 1 byte 1 byte 1 byte 1 byte Lc byte 1 byte
Class byte
- 0x00: standard command
- 0xA2: ST command(1)
1. See Table 11
Instruction byte
Param Byte 1
Param Byte 2
Number of bytes of the Data field
Data bytes
Number of bytes to be read in the ST25TA02K-P memory
Table 15. R-APDU format
Name
Payload field
Data (optional) SW1 SW2
Length Le byte 1 byte 1 byte
Data
Status byte 1
Status byte 2
RF command sets ST25TA02K-P
32/64 DocID027794 Rev 2
5.3 R-Block format
The R-Block is used to convey positive or negative acknowledgment between the RF host
and the ST25TA02K-P.
There are two kinds of R-Blocks:
•R(ACK): the acknowledgment block sent by the RF host or by the ST25TA02K-P
•R(NAK): the non-acknowledgment block sent by the RF host
Table 16. R-Block format
NFC frame
SoD - EoD
PCB DID Payload CRC
Length 1 byte 1 byte 0 byte 2 bytes
R(ACK) without the DID field: 0xA2 or 0xA3
R(ACK) with the DID field: 0xAA or 0xAB
R(NAK) without the DID field: 0xB2 or 0xB3
R(NAK) with the DID field: 0xBA or 0xBB
DID field (optional)
-
2 CRC bytes
Table 17. R-Block detailed format
b7-b6b5b4b3b2b1b0
0b10 1 X X 0 0 X
R-Block
Must be set to 1.
0: NAK
1: ACK
0: DID field is not present
1: DID field is present
Must be set to 0
Must be set to 0
Block number
DocID027794 Rev 2 33/64
ST25TA02K-P RF command sets
58
5.4 S-Block format
The S-Block is used to exchange control information between a reader and a contactless
tag.
There are two requests using the S-Block format:
•S(DES): the deselect command
•S(WTX): the Waiting Frame eXtension command or response.
A Waiting Time eXtension request occurs in RF when the operating time needed by
ST25TA02K-P is greater than 19.2 ms.
The WTX field indicates the increase time factor to be used in this command execution
(FDTtemp = WTX * 19.2 ms). WTX depends on FWI.
Table 18. S-Block format
NFC frame
SoD - EoD
PCB DID Payload CRC
Length 1 byte 1 byte 1 byte 2 bytes
0xC2: for S(DES) when the DID field is not present
0xCA: for S(DES) when the DID field is present
0xF2: for S(WTX) when the DID field is not present
0xFA: for S(WTX) when the DID field is present
DID field (optional)
WTX field (optional)(1)
1. This field is present when b5-b4 bits are set to 0b11 (S-Block is a WTX). see Table 19: S-Block detailed
format.
2 CRC bytes
Table 19. S-Block detailed format
b7-b6 b5-b4 b3 b2 b1 b0
0b11 X X 0 1 0
S-Block
0b00: Deselect
0b11: WTX
0: DID field is not present
1: DID field is present
Must be set to 0
Must be set to 1
Must be set to 0
RF command sets ST25TA02K-P
34/64 DocID027794 Rev 2
Note: After receiving the deselect command, the session is released and ST25TA02K-P enters
the Standby power mode.
In response to a RATS command, ST25TA02K-P returns FWI parameter (default frame
waiting time used); when ST25TA02K-P needs more time for a command execution, it
requests a frame waiting time extension by responding 0xF2 0xWTX (Request waiting time =
FWI * WTX). If the reader accepts ST25TA02K-P request, it acknowledges by sending the
command 0xF2 0xWTX. The frame waiting time becomes FWI * WTX for the current
command only.
5.5 CRC of the RF frame
The two CRC bytes check the data transmission between the RF host and the ST25TA02K-
P. For the RF frame, the CRC is computed on all the data bits in the frame, excluding parity
bits, SOF and EOF, and the CRC itself.
The CRC is as defined in ISO/IEC 13239. The initial register content shall be 0x6363 and
the register content shall not be inverted after calculation.
5.6 NFC Forum Type 4 Tag protocol
5.6.1 Commands set
ST25TA02K-P command set is built to easily support the NFC Forum Type 4 Tag protocol.
5.6.2 Status and error codes
This section lists the status and the error code of the ST25TA02K-P.
Table 20. Command set overview
Command name Brief description
NDEF Tag Application Select Select the NDEF Tag Application
Capability Container Select Select the capability container (CC) file using the Select command
NDEF Select Select the NDEF file using the Select command.
System File Select Select the system file using the Select command.
ReadBinary Read data from a file
UpdateBinary Write new data to a file
Table 21. Status code of the ST25TA02K-P
SW1 SW2 Comment
Value 0x90 0x00 Command completed successfully
DocID027794 Rev 2 35/64
ST25TA02K-P RF command sets
58
Table 22. Error code of the ST25TA02K-P
SW1 SW2
Comment
Length 1 byte 1 byte
Value 0x62 0x82 End of file or record reached before
reading Le bytes
Value 0x63 0x00 Password is required
Value 0x63 0xCX
Password is incorrect, X further
retries allowed (X can take value
0,1, 2)
Value 0x65 0x81 Unsuccessful updating
Value 0x67 0x00 Wrong frame length
Value 0x69 0x81 Cmd is incompatible with the file
structure
Value 0x69 0x82 Security status not satisfied
Value 0x69 0x84 Reference data not usable
Value 0x6A 0x80 Incorrect parameters Le or Lc
Value 0x6A 0x82 File or application not found
Value 0x6A 0x84 File overflow (Lc error)
Value 0x6A 0x86 Incorrect P1 or P2 values
Value 0x6D 0x00 INS field not supported
Value 0x6E 0x00 Class not supported
RF command sets ST25TA02K-P
36/64 DocID027794 Rev 2
5.6.3 NDEF Tag Application Select command
the RF host shall send this command to activate the NDEF Tag Application.
To activate the NDEF Tag Application, the RF host sends the Select command (see
Table 23) in addition to the sequence defined in the NFC Forum digital protocol.
Table 23 defines the C-APDU of the Select command to select the NDEF Tag Application
(called NDEF Tag Application Select).
Table 24 defines the R-APDU of the NDEF Tag Application Select command.
Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.6.4 Capability Container Select command
The RF host uses the Capability Container Select procedure to select the capability
container (CC) file.
The CC file is selected when this command returns "command completed" in the R-APDU.
Table 25 defines the C-APDU of the Select command to select the CC file (called Capability
Container Select).
Table 23. C-APDU of the NDEF Tag Application Select command
Name CLA INS P1 P2 Lc Data Le
- 0x00 0xA4 0x04 0x00 0x07 0xD27600
00850101 0x00
Class byte
Select instruction code
P1 field
P2 field
Number of bytes of data
Application ID
Le field
Table 24. R-APDU of the NDEF Tag Application Select command
Data SW1 SW2 Comment
Length - 1 byte 1 byte -
Value - 0x90 0x00 Command completed
Value - 0x6A 0x82 NDEF Tag Application not found
Value - 0x6D 0x00 Class not supported
DocID027794 Rev 2 37/64
ST25TA02K-P RF command sets
58
Table 26 defines the R-APDU of the CC Select command.
Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.6.5 NDEF Select command
The RF host uses the NDEF Select command to select the NDEF file.
The NDEF file is selected when this command returns "command completed" in the R-
APDU. Table 27 defines the C-APDU of the Select command to select the NDEF file (called
NDEF Select).
Table 25. C-APDU of the Capability Container Select command
Name CLA INS P1 P2 Lc Data Le
- 0x00 0xA4 0x00 0x0C 0x02 0xE103 -
Class byte
Select instruction code
P1 field
P2 field
Number of bytes of data
CC file ID
(empty field)
Table 26. R-APDU of the Capability Container Select command
Data SW1 SW2 Comment
Length - 1 byte 1 byte -
Value - 0x90 0x00 Command completed
Value - 0x6A 0x82 File or application not found
Value - 0x6D 0x00 Class not supported
Table 27. C-APDU of the NDEF Select command
Name CLA INS P1 P2 Lc Data Le
- 0x00 0xA4 0x00 0x0C 0x02 0x0001 -
Class byte
Select instruction code
P1 field
P2 field
Number of bytes of data
0x0001: NDEF file
(empty field)
RF command sets ST25TA02K-P
38/64 DocID027794 Rev 2
Table 28 defines the R-APDU of the NDEF Select command.
Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.6.6 System File Select command
The RF host uses this command to select the system file.
The System file is selected when this command returns "command completed" in the R-
APDU.
Table 29 defines the C-APDU of the command to select the System file (called System
Select).
Table 30 defines the R-APDU of the System File Select command.
Note: Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
Table 28. R-APDU of the NDEF Select command
Data SW1 SW2 Comment
Length - 1 byte 1 byte -
Value - 0x90 0x00 Command completed
Value - 0x6A 0x82 File or application not found
Table 29. C-APDU of the System File Select command
Name CLA INS P1 P2 Lc Data Le
- 0x00 0xA4 0x00 0x0C 0x02 0xE101 -
Class byte
Select instruction code
P1 field
P2 field
Number of bytes of data
System file ID
(empty field)
Table 30. R-APDU of the System File Select command
Data SW1 SW2 Comment
Length - 1 byte 1 byte -
Value - 0x90 0x00 Command completed
Value - 0x6A 0x82 System file not found, no data is
returned
DocID027794 Rev 2 39/64
ST25TA02K-P RF command sets
58
5.6.7 ReadBinary command
On receiving the ReadBinary command, the ST25TA02K-P reads the requested memory
field and sends back its value in the R-APDU response.
Before sending a ReadBinary command, a file shall be selected by using a Select
command.
The Response of the ReadBinary command is successful when the data to be read is within
the selected file (a); in other words, when the sum of P1-P2 and Le fields is equal to or lower
than the selected file length.
Table 31 defines the ReadBinary command.
Table 32 defines the R-APDU of the ReadBinary command.
Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
a. For more details about CC file, refer to Section 3.1.2: CC file layout.
For more details about NDEF file, refer to Section 3.1.3: NDEF file layout.
For more details about System file, refer to Section 3.1.4: System file layout.
Table 31. C-APDU of the ReadBinary command
Name CLA INS P1 & P2 Lc Data Le
- 0x00 0xB0 2 bytes - - 1 byte
Class byte
Read instruction code
Offset in the file selected
(empty field)
(empty field)
Number of bytes to read between
0x01 ≤ Le ≤ max(Selected File length, 0xFFh)
Table 32. R-APDU of the ReadBinary command
Data SW1 SW2 Comment
Length - 1 byte 1 byte -
Value Content read 0x90 0x00 Command completed
Value - 0x67 0x00 Wrong length
Value - 0x69 0x82 Security status not satisfied
Value - 0x6A 0x82 File or application not found
Value - 0x6E 0x00 -
RF command sets ST25TA02K-P
40/64 DocID027794 Rev 2
5.6.8 UpdateBinary command
On receiving the UpdateBinary command, the ST25TA02K-P writes the data field into the
selected file and sends back a status in the R-APDU response. If needed, ST25TA02K-P
will request a timing extension (see Section 5.4).
Before sending an UpdateBinary command, a file shall be selected by issuing a Select
command.
Table 33 defines the UpdateBinary command.
Note: Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
Table 34 defines the R-APDU of the UpdateBinary command.
Note: For further return codes and definitions, refer to Status and error codes.
Table 33. C-APDU of the UpdateBinary command
Name CLA INS P1 & P2 Lc Data Le
- 0x00 0xD6 2 bytes 1 byte Lc bytes -
Class byte
Write instruction code
Offset in the file selected
Number of bytes of data (0x01 ≤ Lc ≤ 0xF6)
Data to write in the ST25TA02K-P memory
(empty field)
Table 34. R-APDU of the UpdateBinary command
Data SW1 SW2 Comment
Length - 1 byte 1 byte -
Value - 0x90 0x00 Command completed
Value - 0x65 0x81 Unsuccessful updating
Value - 0x67 0x00 -
Value - 0x69 0x82 Security status not satisfied
Value - 0x6A 0x82 File or application not found
Value - 0x6E 0x00 -
DocID027794 Rev 2 41/64
ST25TA02K-P RF command sets
58
5.7 ISO/IEC 7816-4 commands
The ISO/IEC 7816-4 command set offers some extended features such as the protection of
the NDEF file. This command set is used to manage the right access of the NDEF file.
5.7.1 Verify command
The Verify command has two functions:
1. Check if a password is required to access to the NDEF file (the LC field = 0x00).
2. Check that the password embedded in the Verify command allows the access to the
memory (the Lc field = 0x10 and the password is present).
When the Lc field if equal to 0x00, the verify command returns a success code (0x90 00)
provided that the access to the NDEF file does not require a password. When the access to
the NDEF file is protected, the response to the Verify command returns an error code
(0x63 00).
When the Lc field equals 0x10, on receiving the Verify command, the ST25TA02K-P
compares the requested password with the data contained in the request and reports
whether the operation has been successful in the response.
Before sending this command, an NDEF file shall be selected by issuing the NDEF Select
command. Thus, this command checks the right access condition of the last NDEF file
selected.
After a successful command, an access is granted for the whole NDEF file.
Table 35 defines the Verify command.
Table 35. Verify command format
Name CLA INS P1 & P2 Lc Data Le
- 0x00 0x20 2 bytes 1 byte Lc bytes -
Class byte
Instruction code
Password identification
0x0001: Read NDEF password transmit
0x0002: Write NDEF password transmit
Other: RFU(1)
1. Return ERROR code when used.
0x00: the password is not present
0x10: the password is present in the data field
Password
(empty field)
RF command sets ST25TA02K-P
42/64 DocID027794 Rev 2
Table 36 defines the R-APDU of the Verify command.
Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.7.2 Change Reference Data command
The Change Reference Data command replaces the read or write password related to the
NDEF files previously selected. It can be performed only if the security status satisfies the
security attributes for this command.
Before sending this command, the verify command with the correct NDEF write password
shall be issued. Thus, this command changes the reference data of the NDEF file.
Table 37 defines the Change Reference Data command.
Table 37. Change reference data command format
Table 36. R-APDU of the Verify command
Data SW1 SW2 Comment
Length - 1 byte 1 byte -
Value - 0x90 0x00 Command completed, the password is correct
Value - 0x69 0x84
The conditions of use are not satisfied (e.g. no
NDEF file was selected or Write access equal to
FFh (write lock) or read access equal to FEh (read
lock)
Value - 0x69 0x81 Cmd incompatible with file structure
Value - 0x69 0x82 Security status not satisfied
Value - 0x6A 0x80 Incorrect parameter in cmd data field
Value - 0x63 0x00 A password is required
Value - 0x63 0xCX (1)
1. At each session, the RF host can check a password 3 times.
The password transmitted is incorrect and X
encodes the number of further allowed retries.
Name CLA INS P1 & P2 Lc Data Le
- 0x00 0x24 2 bytes 0x10 Lc bytes -
Class byte
Instruction code
Password identification
0x0001: Read password transmit
0x0002: Write password transmit
Other: RFU(1)
1. Return ERROR code when used.
0x10: the password is present in the data field
NDEF new file Password
(empty field)
DocID027794 Rev 2 43/64
ST25TA02K-P RF command sets
58
Table 38 defines the R-APDU of the Change Reference Data command.
Note: Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.7.3 Enable Verification Requirement command
The Enable Verification Requirement command activates the protection by password of the
NDEF file. When this command is successful, the read or write access to the NDEF file is
protected by a 128-bit password. It can be performed only if the security status satisfies the
security attributes for this command.
This command can update the right access of the NDEF file by writing into the EEPROM. In
this case, the response timing will be around 5 ms.
Before sending this command, the verify command with the correct NDEF write password
shall be issued. Thus, this command changes the access right of the NDEF file.
Table 39 defines the Enable Verification requirement command.
Table 38. R-APDU of the Change Reference Data command
Data SW1 SW2 Comment
Length 0 1 byte 1 byte -
Value - 0x90 0x00 Command completed, the access right has
been changed
Value - 0x69 0x81 Cmd is incompatible with the
file structure
Value - 0x65 0x81 Unsuccessful updating
Value - 0x69 0x82 Security status not satisfied
Value - 0x6A 0x80 Incorrect param. in file structure
Value - 0x6A 0x82 File or application not found
Value - 0x6A 0x86 Incorrect P1 or P2 values
Table 39. Enable Verification Requirement command format
Name CLA INS P1 & P2 Lc Data Le
- 0x00 0x28 2 bytes - - -
Class byte
Instruction code
New security attributes
0x0001: Enable the read protection of the NDEF file
0x0002: Enable the write protection of the NDEF file
Other: RFU
(empty field)
(empty field)
(empty field)
RF command sets ST25TA02K-P
44/64 DocID027794 Rev 2
The last five bits identify the password sent in the Verify command.
Table 40 defines the R-APDU of the Enable Verification Requirement command.
Note: Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.7.4 Disable Verification Requirement command
The Disable Requirement command deactivates the protection by password of the NDEF
file. When this command is successful, the read or write access to the NDEF file is granted
without security requirements. It can be performed only if the security status satisfies the
security attributes for this command.
Before sending this command, the verify command with the correct NDEF write password
shall be issued. Thus, this command changes the access right of the NDEF file.
This command can update the right access of the NDEF file by writing into the EEPROM. In
this case, the response timing will be around 6 ms.
Table 41 defines the Disable Verification Requirement command.
Table 40. R-APDU of the Enable Verification Requirement command
Data SW1 SW2 Comment
Length 0 1 byte 1 byte -
Value - 0x90 0x00 Command completed, the password is correct
Value - 0x69 0x81 Cmd is incompatible with the file structure
Value - 0x69 0x82 Security status not satisfied
Value - 0x6A 0x80 Incorrect param. in cmd data field
Value - 0x6A 0x82 File or application not found
Value - 0x6A 0x86 Incorrect P1 or P2 values
Table 41. Disable Verification Requirement command format
Name CLA INS P1 & P2 Lc Data Le
- 0x00 0x26 2 bytes - - -
Class byte
Instruction code
New security attributes
0x0001: Disable the read protection of the NDEF file
0x0002: Disable the write protection of the NDEF file
Other: RFU
(empty filed)
(empty filed)
(empty filed)
DocID027794 Rev 2 45/64
ST25TA02K-P RF command sets
58
Table 42 defines the R-APDU of the Disable Verification Requirement command.
Note: Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.8 ST Proprietary command set
The RF host can be issued with the command set described in this chapter.
5.8.1 ExtendedReadBinary command
On receiving the ExtendedReadBinary command, the ST25TA02K-P reads the requested
memory field and sends back its value in the R-APDU response.
Before sending an ExtendedReadBinary command, a file shall be selected by issuing an
NDEF select command.
The response of the ExtendedReadBinary command will be successful even if the data to
be read is beyond the NDEF message. The command returns an error code if the data to be
read goes beyond the end of the file.
Table 42. R-APDU of the Disable Verification Requirement command
Data SW1 SW2 Comment
Length 0 1 byte 1 byte -
Value - 0x90 0x00 Command completed, the password is correct
Value - 0x69 0x81 Cmd is incompatible with the file structure
Value - 0x69 0x82 Security status not satisfied
Value - 0x6A 0x80 CC file or System file selected
Value - 0x6A 0x82 File or application not found
Value - 0x6A 0x86 Incorrect P1 or P2 values
Value - 0x65 0x81 Update failed
Table 43. C-APDU of the ExtendedReadBinary command
Name CLA INS P1 & P2 Lc Data Le
- 0xA2 0xB0 2 bytes - - 1 byte
ST Class byte
Read instruction code
Offset in the file selected
(empty field)
(empty field)
Number of bytes to read between 0x01 ≤ Le ≤ 0xFF
RF command sets ST25TA02K-P
46/64 DocID027794 Rev 2
Table 44 defines the R-APDU of the read binary command.
Note: Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.8.2 EnablePermanentState command
The command configures the NDEF file to the ReadOnly or to the WriteOnly State.
This command can update the right access to the NDEF file by writing into the EEPROM. In
this case, the response timing will be around 6 ms.
Table 45 defines the EnablePermanentState requirement command.
Table 46 defines the R-APDU of the EnablePermanentState command.
Table 44. R-APDU of the ExtendedReadBinary command
Data SW1 SW2 comment
Length Le bytes 1 byte 1 byte -
Value Content read 0x90 0x00 Command completed
Value - 0x67 0x00 Wrong length
Value - 0x69 0x82 Security status not satisfied
Value - 0x6A 0x82 File or application not found
Value - 0x6A 0x86 Incorrect P1 or P2 values
Table 45. EnablePermanentState command format
Name CLA INS P1 & P2 Lc Data Le
- 0xA2 0x28 2 bytes - - -
Class byte
Instruction code
New security attributes
0x0001: Lock the NDEF file in read mode
0x0002: Lock the NDEF file in write mode
Other: RFU
(empty field)
(empty field)
(empty field)
Table 46. R-APDU table of the EnablePermanentState command
Data SW1 SW2 Comment
Length - 1 byte 1 byte -
Value - 0x90 0x00 Command completed
Value - 0x65 0x81 Update failed
Value - 0x69 0x82 Security status not satisfied
DocID027794 Rev 2 47/64
ST25TA02K-P RF command sets
58
Note: For further return codes and definitions, refer to Section 5.6.2: Status and error codes.
5.9 Specific RF command set
This section describes the command set that can be issued only by the RF host.
5.9.1 Anticollision command set
Table 47 lists the commands that can be issued only by the RF host. The format of these
commands is described in the NFC Forum Digital Protocol specification.
Note: In response to a SDD_REQ Command with a SEL_PAR value equal to 20h, ST25TA02K-P
in the Operating Field transmit the requested cascade level of their NFCID1 (NFCID1 CLn,
with n=1 or 2). The NFCID1 of ST25TA02K-P consists of 7 bytes. The length of the
Response containing a complete NFCID1 cascade level (i.e., NFCID1 CL1, or NFCID1 CL2)
is always 5 bytes. The coding of the Response depends on the value of the SEL_CMD byte
and the size of the NFCID1.
Refer to example below for more details .
Value - 0x6A 0x82 File or application not found
Value - 0x6A 0x86 Incorrect P1 or P2 values
Table 46. R-APDU table of the EnablePermanentState command (continued)
Data SW1 SW2 Comment
Table 47. Commands issues by the RF host
Family command set Command name Instruction code
NFC-A technology
ALL_REQ 0x52 (1)
1. Code on 7 bits.
SENS_REQ 0x26 (1)
SDD_REQ 0x93 or 0x95
SEL_REQ 0x93 or 0x95
SLP_REQ 0x50
Table 48. Example of anticollision sequence
Command Code Comment Response Code Comment
SENS_REQ
or
ALL-REQ
26
- ATQA 42 00 UID double size bit
frame anticollision
52
SDD_REQ 1 93 20
NVB 20
Number Valid bit
(2 bytes Code & NVB)
-CT uid1 uid2
uid3 BCC
CT Cascade Tag
“0x88”
(UID 7bytes)
BCC Block Check
Character (XOR
previous Bytes)
RF command sets ST25TA02K-P
48/64 DocID027794 Rev 2
5.9.2 RATS command and ATS response
RATS command and ATS response are used for NFC Forum Type 4A Tag Platform Device
Activation (as defined in NFC Forum Digital Protocol specification).
Table 49 details the RATS command. This command shall be sent after the anticollision
process.
The FSDI field codes the FSD that defines the maximum size that an RF host is able to
receive. Table 50 gives the conversion from FDSI to FSD.
The DID field defines the value of the addressed ST25TA02K-P.
SEL_REQ 1
93 70 CT
uid1 uid2
uid3 BBC
NVB 70
(cmd NVB Uid lower bytes)
CT Cascade Tag “0x88”
SAK & CRC 04 DAD7 UID Not complete
SDD_REQ 2 95 20
NVB 20
Number Valid bit
(2 bytes Code & NVB)
-
uid4 uid5
uid6 uid7
BCC
(UID 7bytes)
BCC Block Check
Character
(XOR previous Bytes)
SEL_REQ 1
95 70
uid4 uid5
uid6 uid7
BBC
NVB 70
(cmd NVB Uid Upper
bytes)
SAK & CRC 20 FC70 UID complete
Table 48. Example of anticollision sequence (continued)
Command Code Comment Response Code Comment
Table 49. RATS command
Name INS Param CRC
Byte field 0xE0 1 byte 2 bytes
Bit field - b7-b4 b3-b0 -
Instruction code
FSDI
DID (0 ≤ DID ≤ 14)
2 CRC bytes
Table 50. Conversion from FDSI to FSD
FSDI 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9h-
0xE 0xF
FSD 16 24 32 40 48 64 96 128 256 RFU 256
DocID027794 Rev 2 49/64
ST25TA02K-P RF command sets
58
The FSCI codes the FSC which stands for the maximum frame size that the ST25TA02K-P
is able to receive. The ST25TA02K-P is able to receive up to 64 bytes of command. If the
RF host sends a command with more than 64 bytes, the ST25TA02K-P will not be able to
treat the command and will not reply.
The FWI which stands for the Frame Waiting time Integer codes the FWT. This time
corresponds to the maximum duration while an RF host shall send before sending the next
command.
The SFGI which stands for the Start-up Frame Guard Time is the minimum time that the
reader shall wait after receiving the response of the ST25TA02K-P.
5.9.3 PPS command & response(b)
PPS (Protocol and Parameter Selection) command and response are defined in ISO/IEC
14443-4, in the Protocol Activation of PICC Type A.
The PPS command allows to change the data rates of the ascending (RF host to
ST25TA02K-P) and descending (ST25TA02K-P to RF host) data rates. Usage of this
command is optional, ST25TA02K-P only supports 106 Kb/s in both direction.
Table 51. ATS response
Name TL T0 TA(1) TB(1) TC(1) CRC
Byte field 0x05 0x75 0x80 0x60 0x02 2 bytes
Bit field - - - b8-b5 b4-b1 - -
Length of the ATS
response
FSCI = 5 => FSC = 64 bytes
The maximum ascending data rate is 106 kbps
The maximum descending data rate is 106 kbps
FWI field (FWI = 6 => FWT = 19.2 ms)
SFGI field (SFGI = 0 => SFGT =302 µs)
The DID is supported
2 CRC bytes
b. Not useful in case of ST25TA02K-P which only support a Data Rate of 106 Kb/s in both direction.
RF command sets ST25TA02K-P
50/64 DocID027794 Rev 2
The ascending and descending data rates shall be coded as described in Table 53.
When the ST25TA02K-P is able to change both data rates, it returns the following response.
The data rate of this response is 106 kbps; then, the ST25TA02K-P changes the ascending
and descending data rates.
Table 54 gives the details of the PPS response.
Table 52. PPS command
Name INS (PPSS) PPS0 PPS1 CRC
Byte field 0xDX 0x11 1 byte 2 bytes
Bit field b7-b4 b3-b0 - 0b0000 b3-b2 b1-b0 -
INS
Instruction code
DID
- PPS1 is present
PPS1
RFU
Descending data rate (106 kb/s) = 0b00
Ascending data rate (106 kb/s) = 0b00
- 2 CRC bytes
Table 53. Ascending and descending data rate coding
Value 0b00 0b01 0b10 0b11
Data rate 106 kbps RFU RFU RFU
Table 54. PPS response
Name RESPONSE (PPSS) CRC
Byte field 0xDX 2 bytes
Bit field b8-b5 b4-b1 -
Response code
DID field
2 CRC bytes
DocID027794 Rev 2 51/64
ST25TA02K-P RF device operation
58
6 RF device operation
6.1 Anticollision and Device Activation command set for the RF
interface
The ST25TA02K-P device supports the command set defined in the NFC-A Technology and
the Type 4A Tag Platform chapters of the NFC Digital Protocol V1.0 specification.
6.2 Open an RF session
Once the RF host has terminated the anticollision procedure and retrieve the ATS response,
it shall send the SelectApplication command. The ST25TA02K-P will open an RF session.
At this point, the RF host can send the applicative command set.
6.3 Close an RF session
The RF host can close the RF session by issuing one of these methods:
•send an S(DES) command
•turn off the RF field
6.4 Applicative command set
The applicative command set is composed of the following command sets:
•the NFC Forum Type 4 Tag command set
•the ISO/IEC 7816-4 command set
•the proprietary command set
Functional procedures ST25TA02K-P
52/64 DocID027794 Rev 2
7 Functional procedures
This section describes some procedure to access the memory or manage its protection.
7.1 Selection of an NDEF message
The RF host shall use this procedure to detect the NDEF message inside an ST25TA02K-P.
The NDEF detection procedure is as follows:
1. Open an RF session
2. Send the SelectNDEFTagApplication command
3. Select the CC file
4. Read the CC file
5. Select the NDEF file.
7.2 Reading of an NDEF message
The RF host executes the NDEF read procedure to read the NDEF file.
1. Detect successfully the NDEF file using the NDEF detection procedure
2. Check that the read access without any security is granted for the NDEF file from the
information provided by the CC file
3. Select the NDEF file
4. Read the NDEF file.
7.3 Reading a locked NDEF file
The RF host executes this procedure to read an NDEF file which has been locked
previously.
1. Select the NDEF Tag Application
2. Select the NDEF file
3. Present the Read password by using the Verify command
4. Read the data in the NDEF file.
7.4 Locking an NDEF file
The RF host executes this procedure to protect an NDEF file.
1. Select the NDEF Tag Application
2. Check the right access provided by the CC file
3. Select the NDEF file
4. Present the NDEF file Write password by using the Verify command
5. Lock the NDEF file by sending the Enable verification command.
DocID027794 Rev 2 53/64
ST25TA02K-P Functional procedures
58
7.5 Unlocking an NDEF file
The RF host executes this procedure to read an NDEF file which has been locked
previously.
1. Select the NDEF Tag Application
2. Select the NDEF file
3. Present the NDEF file Write password by using the Verify command
4. Unlock the NDEF file by sending the Disable verification command.
7.6 Reaching the read-only state for an NDEF file
The RF host executes this procedure to read an NDEF file which has been locked
previously.
1. Select the NDEF Tag Application
2. Select the NDEF file
3. Transmit the NDEF file Write password by using the Verify command
4. Send an EnablePermanentState command.
7.7 Changing a File type Procedure
The RF host executes this procedure to change the File Type of a file for which all access
rights were previously granted.
1. Select the NDEF Tag Application
2. Select the File to be modified
3. Set the File Length to 0x00 using the UpdateBinary command
4. Send an UpdateFileType command with the New file Type as data.
UID: Unique identifier ST25TA02K-P
54/64 DocID027794 Rev 2
8 UID: Unique identifier
The ST25TA02K-P is uniquely identified by a 7 bytes unique identifier (UID). The UID is a
read-only code and comprises:
•The IC manufacturer code on 1 byte (0x02 for STMicroelectronics).
•The Product code on 1 byte.
•A device number on 5 bytes.
Table 55 describes the UID format.
Table 55. UID format
- 0x02 0xA2 5 bytes
IC manufacturer code
ST25TA02K-P product code
Device number
DocID027794 Rev 2 55/64
ST25TA02K-P Maximum rating
58
9 Maximum rating
Stressing the device above the rating listed in Table 56 may cause permanent damage to
the device. These are stress ratings only and operation of the device at these or any other
conditions above those indicated in the operating sections of this specification is not implied.
Exposure to absolute maximum rating conditions for extended periods may affect the device
reliability.
Table 56. Absolute maximum ratings
Symbol Parameter Min. Max. Unit
TAAmbient operating temperature -40 85 °C
TSTG
,
hSTG
,
tSTG
Storage conditions Sawn wafer
on UV tape
15 25 °C
-6
(1)
1. Counted from ST shipment date.
months
Kept in its original packing form
TSTG Storage temperature UFDFPN5 –65 150 °C
TSTG
Storage temperature Sawn bumped
Wafer
(kept in its
antistatic bag)
15 25 °C
Storage time - 6 months
TLEAD
Lead temperature
during soldering UFDFPN5 see note (2)
2. Compliant with JEDEC Std J-STD-020D (for small body, Sn-Pb or Pb assembly), the ST ECOPACK®
7191395 specification, and the European directive on Restrictions on Hazardous Substances (ROHS
directive 2011/65/EU, July 2011).
°C
VDCG GPO Power Supply -0.5 5.5 V
ICC (3)
3. Based on characterization, not tested in production. Maximum absorbed power = 100 mW @ 7.5 A/m
RF supply current AC0 - AC1 - 64 mA
VMAX_1 (3)
RF input voltage
amplitude between
AC0 and AC1, VSS pad
left floating
VAC0-VAC1
(Peak to Peak) -10V
VMAX_2
AC voltage between
AC0 and VSS, or AC1
and VSS
VAC0-VSS or
VAC1-VSS
-0.5 4.5 V
VESD
Electrostatic discharge
voltage (human body
model) (4)
4. AEC-Q100-002 (compliant with JEDEC Std JESD22-A114A, C1 = 100 pF, R1 = 1500 Ω, R2 = 500 Ω)
AC0-AC1 - 1500 V
VESD
Electrostatic discharge
voltage (human body
model) (4)
Other pads - 3500 V
GPO characteristics ST25TA02K-P
56/64 DocID027794 Rev 2
10 GPO characteristics
This section summarizes the operating and measurement conditions of the GPO feature.
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. GPO is
CMOS compliant.
Note: The GPO (general purpose output) can sink or source at least 0.7 mA @1.65V , 2mA
@2.7V, 4mA @ 5.5V.
Table 57. GPO Operating Conditions
Symbol Parameter Min. Max. Unit
VDCG GPO Power Supply 1.65 5.5 V
Table 58. DC characteristics
Symbol Parameter Test condition Min. Max. Unit
VOL Output Low voltage (GPO) IOL = 0.7 mA, VDCG = 1.65V - 0.2VDCG V
VOH Output High voltage (GPO) IOH = -0.7 mA, VDCG = 1.65V 0.8VDCG -V
VOL Output Low voltage (GPO) IOL = 2 mA, VDCG = 2.7V - 0.2VDCG V
VOH Output High voltage (GPO) IOH = -2 mA, VDCG 2.7V 0.8VDCG -V
VOL Output Low voltage (GPO) IOL = 4 mA, VDCG 5.5V - 0.2VDCG V
VOH Output High voltage (GPO) IOH = -4 mA, VDCG = 5.5V 0.8VDCG -V
Table 59. GPO AC Characteristics
Symbol Parameter Test condition Min. Max. Unit
tf(IO)out Output fall time(1)
1. Vref(t) output timing reference levels 0.3 VDCG to 0.7 VDCG V.
CL = 50 pF, VDCG = 1.65 V to 5.5 V -90
(2)(3)
2. Characterization only on bench.
3. When GPO is set in RF Field detection mode return to quiet position could request long time depending of
ST25TA02K-P activity (~20ms).
ns
tr(IO)out Output rise time(1) CL = 50 pF, VDCG = 1.65 V to 5.5 V -90
(2) ns
DocID027794 Rev 2 57/64
ST25TA02K-P GPO parameters
58
11 GPO parameters
This section lists the timing of the GPO according to its configuration.
Table 60. GPO timings measurement (1)
GPO field I/F Condition Command Symbol Typ. Unit
Session Open 0x10 or
0x90
RF GPO high when
session active NDEF select CmdEOFtoGPhigh 170 µs
RF GPO return low Deselect CmdEOFtoGPlow 370 µs
WIP 0x20 or
0xA0
RF
GPO high when
programming Update Binary
CmdEOFtoGPhigh 75 µs
RF Writing time duration
(No time extension)
(2) ms
Message In
Progress
0x30 or
0xB0
RF GPO high when
modifying NDEF
UpdateBinary (Msg
Length #0) CmdEOFtoGPhigh 75 µs
RF GPO high when
modifying NDEF UpdateBinary Writing time duration
(No time extension)
(2) ms
Interrupt 0x40 or
0xC0
RF GPO high after
receiving an
Interrupt command
SendInterrupt
CmdEOFtoGPhigh 75 µs
RF Pulse duration 540 µs
State Control 0x50 or
0xD0
RF GPO high when
reset Reset GPO CmdEOFtoGPhigh 60 µs
RF GPO return low
when set Set GPO CmdEOFtoGPlow 60 µs
RF Busy 0x60 or
0xE0
RF
GPO high after
receiving an RF
command
Anticollision
command or start of
RF disturb
(command using
another RF protocol)
CmdSOFtoGPhigh 6 µs
RF
GPO return low
after deselection or
RF command in
another protocol
Deselect or end of
RF disturb
(command using
another RF protocol)
CmdEOFtoGPlow 460 µs
Field detect 0x70 or
0xF0 RF GPO high when RF
field is present -
tFDETON 140 µs
tFDETOFF 20 µs
1. Characterized only.
2. Writing time is function of the message length and is automatically manage by ST25TA02K-P. NDEF message is mapped
on memory blocks of 16 bytes. Each basic block has a typical update time duration of 6 ms including the internal verify.
RF electrical parameters ST25TA02K-P
58/64 DocID027794 Rev 2
12 RF electrical parameters
This section summarizes the operating and measurement conditions, and the DC and AC
characteristics of the device in RF mode.
The parameters in the DC and AC characteristics tables that follow are derived from tests
performed under the Measurement Conditions summarized in the relevant tables.
Designers should check that the operating conditions in their circuit match the measurement
conditions when relying on the quoted parameters.
Table 61. Default operating conditions
Symbol Parameter Min. Max. Unit
TAAmbient operating temperature –40 85 °C
Table 62. RF characteristics(1)
Symbol Parameter Condition Min Typ Max Unit
fCExternal RF signal frequency - 13.553 13.56 13.567 MHz
H_ISO Operating field according to ISO TA = 0°C to 50°C 1500 - 7500 mA/m
H_Extended Operating field in extended
temperature range TA = -40°C to 85°C 200 - 7500 mA/m
Hmin Field detect, Set-up field(1) TA = -40°C to 85°C - 115 - mA/m
MICARRIER 100% carrier modulation index MI=(A-B)/(A+B) 90 - 100 %
t1Pause A length - 28 / fC- 40.5 / fCµs
t2Pause A low time - 7 / fC-t
1µs
t3Pause A rise time - 1.5xt4 - 16 / fCµs
t4Pause A rise time section - 0 - 6 / fCµs
tMIN CD
Minimum time from carrier
generation to first data From H-field min - - 5 ms
Wt
RF write time (including internal
Verify) for one page - - 4.468(2) -ms
CTUN / 5 (3) Internal tuning capacitor(4) fC = 13.56 MHz 45 50 55 pF
tRF_OFF RF OFF time Chip reset - - 0.1 ms
1. All timing characterizations were performed on a reference antenna with the following characteristics:
External size: 75 mm x 48 mm
Number of turns: 4
Width of conductor: 0.5 mm
Space between two conductors: 0.5 mm
Value of the tuning capacitor: 50 pF (ST25TA02K-P)
Value of the coil: 2.5 µH
Tuning frequency: 14.2 MHz.
2. Time between command EOF and Response SOF when Updating NDEF message Length
3. See Capacitor value
4. Characterized only, at room temperature only, measured at VAC0-VAC1 = 2 V peak to peak at 13.56 MHz.
DocID027794 Rev 2 59/64
ST25TA02K-P Package information
62
13 Package information
In order to meet environmental requirements, ST offers these devices in different grades of
ECOPACK® packages, depending on their level of environmental compliance. ECOPACK®
specifications, grade definitions and product status are available at: www.st.com.
ECOPACK® is an ST trademark.
13.1 UFDFN8 package information
Figure 14. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch
dual flat package outline
1. Max. package warpage is 0.05 mm.
2. Exposed copper is not systematic and can appear partially or totally according to the cross section.
3. Drawing is not to scale.
=:DB0(B9
7RSYLHZ
3LQ
,'PDUNLQJ
6LGHYLHZ
6HDWLQJSODQH
HHH
FFF
&
&
&
&
%
$
1
'
(
DDD
DDD
$
$
$
[
[
'DWXP$
7HUPLQDOWLS
'HWDLO³$´
(YHQWHUPLQDO
/
//
H
H
3LQ
,'PDUNLQJ
%RWWRPYLHZ 6HH'HWDLO³$´
H
H
1'[
'
/
/
(
.
/
E
Package information ST25TA02K-P
60/64 DocID027794 Rev 2
Table 63. UFDFN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat
package mechanical data
Symbol
millimeters inches(1)
1. Values in inches are converted from mm and rounded to 4 decimal digits.
Min Typ Max Min Typ Max
A 0.450 0.550 0.600 0.0177 0.0217 0.0236
A1 0.000 0.020 0.050 0.0000 0.0008 0.0020
b(2)
2. Dimension b applies to plated terminal and is measured between 0.15 and 0.30 mm from the terminal tip.
0.200 0.250 0.300 0.0079 0.0098 0.0118
D 1.900 2.000 2.100 0.0748 0.0787 0.0827
D2 1.500 1.600 1.700 0.0591 0.0630 0.0669
E 2.900 3.000 3.100 0.1142 0.1181 0.1220
E2 0.100 0.200 0.300 0.0039 0.0079 0.0118
e - 0.500 - 0.0197
K 0.800 - - 0.0315 - -
L 0.400 0.450 0.500 0.0157 0.0177 0.0197
L1 - - 0.150 - - 0.0059
L3 0.300 - - 0.0118 - -
aaa - - 0.150 - - 0.0059
bbb - - 0.100 - - 0.0039
ccc - - 0.100 - - 0.0039
ddd - - 0.050 - - 0.0020
eee(3)
3. Applied for exposed die paddle and terminals. Exclude embedding part of exposed die paddle from
measuring.
- - 0.080 - - 0.0031
DocID027794 Rev 2 61/64
ST25TA02K-P Package information
62
13.2 UFDFPN5 package information
Figure 15. UFDFPN5 - 5-lead, 1.7 × 1.4 mm, 0.55 mm thickness package outline
1. Max. package warpage is 0.05 mm.
2. Exposed copper is not systematic and can appear partially or totally according to the cross section.
3. Drawing is not to scale.
Table 64. UFDFPN5 - 5-lead, 1.7 × 1.4 mm, 0.55 mm thickness
package mechanical data
Symbol
millimeters inches(1)
1. Values in inches are converted from mm and rounded to 4 decimal digits.
Min Typ Max Min Typ Max
A 0.500 0.550 0.600 0.0197 0.0217 0.0236
A1 0.000 - 0.050 0.0000 - 0.0020
b(2)
2. Dimension b applies to plated terminal and is measured between 0.15 and 0.30mm from the terminal tip.
0.175 0.200 0.225 0.0069 0.0079 0.0089
D 1.600 1.700 1.800 0.0630 0.0669 0.0709
D1 1.400 1.500 1.600 0.0551 0.0591 0.0630
E 1.300 1.400 1.500 0.0512 0.0551 0.0591
E1 0.175 0.200 0.225 0.0069 0.0079 0.0089
e - 0.400 - - 0.0157 -
L 0.500 0.550 0.600 0.0197 0.0217 0.0236
L1 - 0.100 - - 0.0039 -
k - 0.400 - - 0.0157 -
7RSYLHZ
PDUNLQJVLGH
'
(
6LGHYLHZ
$
$
$8.B0(B9
%RWWRPYLHZ
SDGVVLGH
'
(
E
N/
H
3LQ
3LQ
Part numbering ST25TA02K-P
62/64 DocID027794 Rev 2
14 Part numbering
Note: Parts marked as “ES”, “E” or accompanied by an Engineering Sample notification letter, are
not yet qualified and therefore not yet ready to be used in production and any consequences
deriving from such usage will not be at ST charge. In no event, ST will be liable for any
customer usage of these engineering samples in production. ST Quality has to be contacted
prior to any decision to use these Engineering samples to run qualification activity.
Table 65. Ordering information scheme for packaged devices
ST25 T A 02K - P C 6 H/C 5
Device type
ST25 = RF memory
Product Type
T = Tags +RFID
Protocol
A = ISO14443-A
Memory density
02K (binary)
Interface
P = P-CMOS GPO
Features
C = Counter as option
Operating temperature
6 = -40oC to +85oC
Package / Packing
H = DFN5
C = DFN8
Capacitor value
5 = 50 pF
DocID027794 Rev 2 63/64
ST25TA02K-P Revision history
15 Revision history
Table 66. Document revision history
Date Revision Changes
24-Apr-2015 1 Initial release.
01-Jun-2015 2
Updated package info on Cover page.
Updated Figure 7: GPO configured as MIP (GPO field = 0x30 or 0xB0)
and Figure 8: GPO configured as INT (GPO field = 0x40 or 0xC0).
Updated Section 13.2: UFDFPN5 package information.
Updated Table 65: Ordering information scheme for packaged devices.
ST25TA02K-P
64/64 DocID027794 Rev 2
IMPORTANT NOTICE – PLEASE READ CAREFULLY
STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, enhancements, modifications, and
improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on
ST products before placing orders. ST products are sold pursuant to ST’s terms and conditions of sale in place at the time of order
acknowledgement.
Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or
the design of Purchasers’ products.
No license, express or implied, to any intellectual property right is granted by ST herein.
Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.
ST and the ST logo are trademarks of ST. All other product or service names are the property of their respective owners.
Information in this document supersedes and replaces information previously supplied in any prior versions of this document.
© 2015 STMicroelectronics – All rights reserved
