STMicroelectronics SRTAG2K-D Datasheet
PDF
Dokumen
Iklan
Iklan
SRTAG2K-D NFC Forum Type 4 Tag IC with 2-Kbit EEPROM and RF Session digital output Datasheet - preliminary data Package • UFDFPN8 ECOPACK®2 Digital pad UFDFPN8 (MC) • RF Session output Wafer (SB12I) Description Features The SRTAG2K-D device is a dynamic NFC/RFID tag IC. It embeds an EEPROM memory. It can be operated from a 13.56 MHz RFID reader or an NFC phone. Contactless interface • NFC Forum Type 4 Tag The RF protocol is compatible with ISO/IEC 14443 Type A and NFC Forum Type 4 Tag. • ISO/IEC 14443 Type A • 106 Kbps data rate • Internal tuning capacitance: 25 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 246 bytes in a single command • Write up to 246 bytes in a single command • 7 bytes unique identifier (UID) • 128 bits passwords protection February 2014 DocID025446 Rev 3 This is preliminary information on a new product now in development or undergoing evaluation. Details are subject to change without notice. 1/51 www.st.com 1 Contents SRTAG2K-D Contents 1 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.1 Functional modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.1.1 2 Signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1 Antenna coil (AC0, AC1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2 Ground (VSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.3 RF Session output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.3.1 3 3.2 2/51 Memory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 3.1.1 File identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1.2 CC file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1.3 NDEF file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.1.4 System file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Read and write access rights to the memory . . . . . . . . . . . . . . . . . . . . . . 13 3.2.1 State of the Read and Write access rights . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.2 Changing the read access right to NDEF files . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Changing the write access right to NDEF files . . . . . . . . . . . . . . . . . . . 15 3.3 Access right life time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.4 NDEF file passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Communication mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.1 5 Session Open configuration (RF Session field = 0x11) . . . . . . . . . . . . . 10 SRTAG2K-D memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1 4 Tag mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Master and slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 RF command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.1 Structure of the command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.2 I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.2.1 C-APDU: payload format of a command . . . . . . . . . . . . . . . . . . . . . . . . 20 5.2.2 R-APDU: payload format of a response . . . . . . . . . . . . . . . . . . . . . . . . 21 5.3 R-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.4 S-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 DocID025446 Rev 3 SRTAG2K-D 5.5 CRC of the RF frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.6 NFC Forum Type 4 Tag protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.7 5.8 5.9 6 7 Contents 5.6.1 Commands set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.6.2 Status and error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.6.3 NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . 25 5.6.4 Capability Container Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.6.5 NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.6.6 System File Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 5.6.7 ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 5.6.8 UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 ISO/IEC 7816-4 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.7.1 Verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.7.2 Change Reference Data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5.7.3 Enable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . . 32 5.7.4 Disable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . 33 ST Proprietary command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5.8.1 ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5.8.2 EnablePermanentState command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Specific RF command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.9.1 Anticollision command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.9.2 RATS command and ATS response . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.9.3 PPS command & response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 RF device operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.1 Anticollision and Device Activation command set for the RF interface . . 39 6.2 Open an RFsession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.3 Close an RFsession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.4 Applicative command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Functional procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.1 Selection of an NDEF message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.2 Reading of an NDEF message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.3 Reading a locked NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.4 Locking an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.5 Unlocking an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 7.6 Reaching the read-only state for an NDEF file . . . . . . . . . . . . . . . . . . . . . 41 DocID025446 Rev 3 3/51 Contents SRTAG2K-D 7.7 Changing an NDEF password procedure . . . . . . . . . . . . . . . . . . . . . . . . . 41 7.8 Changing a File type Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 8 UID: Unique identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 9 Maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 10 RF Session pad parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 11 RF electrical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 12 Package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 12.1 Mechanical data for the UFDFPN8 package . . . . . . . . . . . . . . . . . . . . . . 47 13 Part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 14 Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 4/51 DocID025446 Rev 3 SRTAG2K-D List of tables 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. Signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Functional mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 File identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 CC file layout for 1 NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 NDEF file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Field list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Read access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Write access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 RF command sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 PCB field of the I-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 C-APDU format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 R-APDU format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 R-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 R-Block detailed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 S-Block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 S-Block detailed format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Command set overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Status code of the SRTAG2K-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Error code of the SRTAG2K-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 C-APDU of the NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 25 R-APDU of the NDEF Tag Application Select command . . . . . . . . . . . . . . . . . . . . . . . . . . 25 C-APDU of the Capability Container Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 R-APDU of the Capability Container Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 C-APDU of the NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 R-APDU of the NDEF Select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 C-APDU of the System File Select command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 R-APDU of the System File Select command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 C-APDU of the ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 R-APDU of the ReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 C-APDU of the UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 R-APDU of the UpdateBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Verify command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 R-APDU of the Verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Change reference data command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 R-APDU of the Change Reference Data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Enable Verification Requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 R-APDU of the Enable Verification Requirement command. . . . . . . . . . . . . . . . . . . . . . . . 33 Disable Verification Requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 R-APDU of the Disable Verification Requirement command . . . . . . . . . . . . . . . . . . . . . . . 34 C-APDU of the ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 R-APDU of the ExtendedReadBinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 EnablePermanentState command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 R-APDU table of the EnablePermanentState command . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Commands issues by the RF host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 RATS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Conversion from FDSI to FSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 ATS response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 DocID025446 Rev 3 5/51 List of tables Table 49. Table 50. Table 51. Table 52. Table 53. Table 54. Table 55. Table 56. Table 57. Table 58. Table 59. Table 60. 6/51 SRTAG2K-D PPS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Ascending and descending data rate coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 PPS response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 UID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 DC characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 RF Session pad timings measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Default operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 RF characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 UFDFPN8 - 8-lead ultra thin fine pitch dual flat package, no lead, package data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Ordering information scheme for packaged devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 DocID025446 Rev 3 SRTAG2K-D List of figures List of figures Figure 1. Figure 2. Figure 3. Figure 4. Figure 5. Figure 6. SRTAG2K-D block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8-pin package connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Session Open (RF Session field = 0x11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Changing the read access right to an NDEF file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Changing the write access right to an NDEF file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 UFDFPN8 - 8-lead ultra thin fine pitch dual flat package, no lead, 2x3 mm, package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 DocID025446 Rev 3 7/51 Functional description 1 SRTAG2K-D Functional description The SRTAG2K-D 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 SRTAG2K-D is compatible with the NFC Forum Type 4 Tag specifications and supports all corresponding commands. Figure 1 displays the block diagram of the SRTAG2K-D device. Figure 1. SRTAG2K-D block diagram 5)LQWHUIDFH EDVHGRQ ,62,(& 7\SH$ VWDQGDUG $& $& $QDORJ)URQWHQG EDVHGRQ ,62,(& 7\SH$VWDQGDUG 3RZHU PDQDJHPHQW XQLW h/ΘƐLJƐƚĞŵ ĂƌĞĂ ,QWHUQDOWXQLQJ FDSDFLWDQFH 1)&)RUXP 7\SH7DJ SURWRFRO 5) 6HVVLRQ hƐĞƌŵĞŵŽƌLJ 'LJLWDOXQLW 5)6HVVLRQ SXOOXSVXSSO\ 9±9 966 069 8/51 DocID025446 Rev 3 SRTAG2K-D Functional description Table 1. Signal names Signal name Function AC0, AC1 Antenna coils VSS Ground RF Session Direction - Interrupt output (1) Open drain output 1. An external pull-up > 4.7 kΩ is required. Figure 2. 8-pin package connections 1& 1& $& 5)6HVVLRQ $& 1& 966 1& 069 1. See Package mechanical data section for package dimensions, and how to identify pin 1. 1.1 Functional modes The SRTAG2K-D has just one functional mode available (see Table 2). Table 2. Functional mode Mode Tag mode 1.1.1 Supply source RF field only Comments The RF interface is connected Tag mode The SRTAG2K-D is supplied by the RF field and can communicate with an RF host (RFID reader or an NFC phone). The User memory can only be accessed by the RF commands. DocID025446 Rev 3 9/51 Signal descriptions SRTAG2K-D 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 VCC supply voltage for all pads, even AC0 and AC1. 2.3 RF Session output The RF Session Output pin is an open drain output and must be connected to an external pull-up resistor > 4.7 KOhm ( 20 KOhm is recommended to save power consumption) 2.3.1 Session Open configuration (RF Session field = 0x11) "Session Open" pad goes to the Low state when an RF session is ongoing (see Figure 3). An RF session is taken when SRTAG2K-D receives a valid Select Application. The session is released after SRTAG2K-D has received a valid Deselect command, when the RF field became OFF. RF Session pad is driven low after a delay (1) when the session is open. RF Session pad is released after a delay (2) when the session is released. ĞƐĞůĞĐƚ ^ĞƐƐŝŽŶ ŶƚŝĐŽůůŝƐŝŽŶΘ E&ƐĞůĞĐƚ Figure 3. Session Open (RF Session field = 0x11) Z&^ĞƐƐŝŽŶ ^ĞƐƐŝŽŶKƉĞŶƉĂĚ ;ϭͿ Z&^ĞƐƐŝŽŶ ;ϮͿ D^ϯϯϯϭϵsϭ 1. CmdEOFtoGPlow (RF command End of frame to RF Session pad low) 2. CmdEOFtoGPHZ (RF command End of frame to RF Session pad HZ) 10/51 DocID025446 Rev 3 SRTAG2K-D SRTAG2K-D memory management 3 SRTAG2K-D memory management 3.1 Memory structure The SRTAG2K-D supports the NDEF Tag Application as defined in the NFC Forum Type 4 Tag. The SRTAG2K-D is composed of three files: • One Capability Container file • One NDEF file • One System file: this is an ST-proprietary file The System file contains some information on the configuration of the SRTAG2K-D device. The CC file gives some information about the SRTAG2K-D itself and the NDEF file. The NDEF file contains the User data. 3.1.1 File identifier The file identifier is the value used in the Select command to select a file. Table 3. File identifier File identifier 3.1.2 Meaning 0xE101 System file 0xE103 CC file 0x0001 NDEF file CC file layout The CC file gives some information about the SRTAG2K-D 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). DocID025446 Rev 3 11/51 SRTAG2K-D memory management SRTAG2K-D Table 4. CC file layout for 1 NDEF file File offset 0x0000 Meaning Number of bytes of CC file (1) Value Comments 0x000F 15 bytes 0x20 or 0x10 V 2.0 or V 1.0 0x0002 Mapping version 0x0003 Maximum number of bytes that can be read 0x00F6 246 bytes 0x0005 Maximum number of bytes that can be written 0x00F6 246 bytes (2) T field 0x0007 0x04 0x0008 0x06 L field 0x0009 0x0001 FileID 0x0100 Maximum NDEF file size 0x000D 0x00 (2) Read access 0x000E (2) Write access 0x000B NDEF file control TLV 0x00 1. According to the reader. 2. Delivery state. 3.1.3 NDEF file layout The NDEF file contains the NDEF message which contains the User data. The RF host 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 SRTAG2K-D device does not check if its value is relevant vs the data written by the RF host. The SRTAG2K-D device uses the NDEF Message Length, e. g. the standard read can be processed only inside the NDEF message; otherwise, the SRTAG2KD device returns an error code. For more details about the read command, refer to Section 5.6.7: ReadBinary command. 12/51 DocID025446 Rev 3 SRTAG2K-D SRTAG2K-D memory management Table 5. NDEF file layout File offset Byte 0 0x0000 NDEF message length 0x0004 3.1.4 Byte 1 Byte 2 Byte 3 User data User data User data User data User data User data ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 0x00FF ... ... ... User data System file layout The system file specifies the configuration of the SRTAG2K-D. Table 6 lists the different fields. Table 6. Field list Field name Number of bytes Read access Write access Delivery state (1) 0x0000 Length system file 2 RF - 0x0012 0x0002 ST reserved 1 RF none 0x01 0x0003 ST reserved 1 RF none 0x00 0x0004 RF Session field 1 RF none 0x11 0x0005 ST reserved 1 RF none 0x00 0x0006 ST reserved 1 RF none 0x01 0x0007 NDEF File number (RFU) 1 RF none 0x00 0x0008 UID 7 RF none 0x02D2 xx xx xx xx xx (2) 0x000F Memory Size 2 RF none 0x00FF 0x0011 Product Code 1 RF none 0xD2 File offset 1. The delivery state for all passwords = 0x00000000000000000000000000000000. 2. 3.2 x values are defined by ST to insure UID unicity. Read and write access rights to the memory An NDEF file can be locked for read or write accesses. It is also protected by a 128-bit password that the host shall present before accessing the NDEF file. There are two 128-bit passwords, one for the read access and the other one for the write access. An NDEF file can be permanently locked for read or write accesses. Thus, the host cannot access the NDEF file. DocID025446 Rev 3 13/51 SRTAG2K-D memory management SRTAG2K-D The read password shall be sent to the SRTAG2K-D device before reading a read-locked NDEF file. The write password shall be present on the SRTAG2K-D device before writing a writelocked 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 7. Read access right Value Meaning 0x00 Read access without any security 0x80 Locked (1) 0xFE Read not authorized 1. The read password shall be sent before reading in the NDEF file. Table 8. Write access right Value Meaning 0x00 Write access without any security 0x80 Locked (1) 0xFF Write not authorized 1. The write password shall be sent before writing in the NDEF file. The state 0xFF and 0xFE cannot be changed by using the Read or Write passwords. 3.2.2 Changing the read access right to NDEF files The state diagram on Figure 4 shows how to change the access right to read an NDEF file. 14/51 DocID025446 Rev 3 SRTAG2K-D SRTAG2K-D memory management Figure 4. Changing the read access right to an NDEF file [ /RFNWKH1'()ILOH 8QORFNWKH1'()ILOH [ 3HUPDQHQWO\ORFNWKH1'()ILOH [)) 069 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. 3.2.3 Changing the write access right to NDEF files The state diagram on Figure 5 shows how to change the write access right to an NDEF file. Figure 5. Changing the write access right to an NDEF file [ /RFNWKH1'()ILOH 8QORFNWKH1'()ILOH [ [)( 069 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. DocID025446 Rev 3 15/51 SRTAG2K-D memory management 3.3 SRTAG2K-D 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). 16/51 DocID025446 Rev 3 SRTAG2K-D 4 Communication mechanism Communication mechanism This chapter describes the principle of communication between an RF host and the SRTAG2K-D device. 4.1 Master and slave The SRTAG2K-D 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. DocID025446 Rev 3 17/51 RF command sets 5 SRTAG2K-D RF command sets This section describes the SRTAG2K-D 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 IBlock 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: RBlock 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 9 lists the RF command sets. Table 9. RF command sets Family command set Class byte Instruction code 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 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 NFC Forum Type 4 Tag ISO/IEC 7816-4 18/51 Command name DocID025446 Rev 3 Brief description SRTAG2K-D 5.1 RF command sets Structure of the command sets The exchange of data between the RF host and the SRTAG2K-D uses three kinds of data formats, called blocks: • I-Block: to exchange the command and the response • R-Block: to exchange positive or negative acknowledgement • S-Block: to use either the Deselect command or the Frame Waiting eXtension (WTX) command or response This section describes the structure of the I-Block, R-block and S-Block. This format is used for the application command set. 5.2 I-Block format The I-Block is used to exchange data between the RF host and the SRTAG2K-D. It is composed of three fields. Table 10 details the I-Block format. Table 10. I-Block format SoD Payload EoD Name Length PCB DID 0 CRC 1 byte 1 byte 1 to 251 bytes 2 bytes PCB field DID field (optional) RF host to SRTAG2K-D: C-APDU SRTAG2K-D to RF host: R-APDU 2 CRC bytes DocID025446 Rev 3 19/51 RF command sets SRTAG2K-D Table 11. PCB field of the I-Block format b7-b6 b5 b4 b3 b2 b1 b0 0b00 0 0 X 0 1 X I-Block RFU Must be set to 0 DID field, if bit is set Must be set to 0 Must be set to 1 Block number When the RF host sends a command to the SRTAG2K-D the format of the payload is the CAPDU. When the SRTAG2K-D sends a command to the RF host, the format of the payload is the RAPDU. 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 SRTAG2K-D. Table 12 describes its format. Table 12. C-APDU format Payload field Name Length CLA INS P1 P2 LC Data Le 1 byte 1 byte 1 byte 1 byte 1 byte Lc byte 1 byte Class byte 0x00: standard command 0xA2: ST command Instruction byte Param Byte 1 Param Byte 2 Number of bytes of the Data field Data bytes Number of bytes to be read in the SRTAG2K-D memory 20/51 DocID025446 Rev 3 SRTAG2K-D 5.2.2 RF command sets R-APDU: payload format of a response the SRTAG2K-D uses the I-Block format to reply to a command which used the I-Block format. This format is described in Table 13. Table 13. R-APDU format Payload field Name Length Data (optional) SW1 SW2 Le byte 1 byte 1 byte Data Status byte 1 Status byte 2 5.3 R-Block format The R-Block is used to convey positive or negative acknowledgment between the RF host and the SRTAG2K-D. Table 14. R-Block format PCB CRC R(ACK) without the DID field: 0xA2 or 0xA3 R(ACK) with the DID field: 0xAA or 0xAB R(NAK) without the DID field: 0xB2 0xB3 R(NAK) with the DID field: 0xBA 0xBB 2 CRC bytes There are two kinds of R-Blocks: • R(ACK): the acknowledgement block sent by the RF host or by the SRTAG2K-D • R(NAK): the non-acknowledgement block sent by the RF host or by the SRTAG2K-D DocID025446 Rev 3 21/51 RF command sets SRTAG2K-D Table 15. R-Block detailed format b7-b6 b5 b4 b3 b2 b1 b0 0b10 1 X X 0 0 X R-Block RFU 0: NAK 1: ACK 0: DID field is not present 1: DID field is present Must be set to 0 RFU Block number 5.4 S-Block format The S-Block is used to exchange control information between a reader and a contactless tag. Table 16. S-Block format SoD EoD NFC frame Length PCB DID Payload CRC 1 byte 1 byte 1 to 255 bytes 2 bytes 0xC2: for S(DES) when the DID field is not present 0xCA: for S(DES) when the DID field is present 0xF2: for S(WTX) when the DID field is not present 0xFA: for S(WTX) when the DID field is present DID field (optional) WTX field (1) 2 CRC bytes 1. This field is present when b5-b4 bits are set to 0b11 (S-Block is a WTX). see Table 17: S-Block detailed format. 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 or I2C, when the operating time needed by M24SRxx is greater than 9.6 ms. The WTX field indicates the increase time factor to be used in this command execution (FDTtemp = WTX * 9.6 ms). 22/51 DocID025446 Rev 3 SRTAG2K-D RF command sets Table 17. 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 RFU RFU Note: After receiving the deselect command, the session is released and SRTAG2K-D enters the Standby power mode. In response to a RATS command, SRTAG2K-D returns FWI parameter (default frame waiting time used); when SRTAG2K-D 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 SRTAG2K-D 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 SRTAG2K-D. 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 SRTAG2K-D command set is built to easily support the NFC Forum Type 4 Tag protocol. Table 18. 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 System File Select Select the system file DocID025446 Rev 3 23/51 RF command sets SRTAG2K-D Table 18. Command set overview (continued) Command name 5.6.2 Brief description ReadBinary Read data from a file UpdateBinary Write new data to a file Status and error codes This section lists the status and the error code of the SRTAG2K-D. Table 19. Status code of the SRTAG2K-D Value ---- SW2 Comment 0x90 0x00 Command completed successfully Table 20. Error code of the SRTAG2K-D SW1 SW2 1 byte 1 byte Value 0x62 0x80 File overflow (Le error) 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 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 Length 24/51 SW1 DocID025446 Rev 3 Comment SRTAG2K-D 5.6.3 RF command sets 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 21) in addition to the sequence defined in the NFC Forum digital protocol. Table 21 defines the C-APDU of the Select command to select the NDEF Tag Application (called NDEF Tag Application Select). Table 21. C-APDU of the NDEF Tag Application Select command Name Value 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 22 defines the R-APDU of the NDEF Tag Application Select command. Table 22. R-APDU of the NDEF Tag Application Select command 5.6.4 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 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 23 defines the C-APDU of the Select command to select the CC file (called Capability Container Select). DocID025446 Rev 3 25/51 RF command sets SRTAG2K-D Table 23. C-APDU of the Capability Container Select command Name Value 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 - Table 24 defines the R-APDU of the CC Select command. Table 24. R-APDU of the Capability Container Select command 5.6.5 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 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 RAPDU. Table 25 defines the C-APDU of the Select command to select the NDEF file (called NDEF Select). Table 25. C-APDU of the NDEF Select command Name Value CLA INS P1 P2 Lc Data Le 0x00 0xA4 0x00 0x0C 0x02 0x000X - Class byte Select instruction code P1 field P2 field Number of bytes of data 0x0001: first NDEF file - 26/51 DocID025446 Rev 3 SRTAG2K-D RF command sets Table 26 defines the R-APDU of the NDEF Select command. Table 26. R-APDU of the NDEF Select command Data 5.6.6 SW1 SW2 Comment Length - 1 byte 1 byte - Value - 0x90 0x00 Command completed Value - 0x6A 0x82 File or application not found 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 RAPDU. Table 27 defines the C-APDU of the command to select the System file (called System Select). Table 27. C-APDU of the System File Select command Name CLA INS P1 P2 Lc Data Le 0x00 0xA4 0x00 0x0C 0x02 0xE101 - Class byte Select instruction code P1 field P2 field Number of bytes of data System file ID - Table 28 defines the R-APDU of the System File Select command. Table 28. R-APDU of the System File Select command 5.6.7 Data SW1 SW2 Comment Length - 1 byte 1 byte - Value - 0x90 0x00 Command completed Value - 0x6A 0x82 Capability container not found, no data is returned ReadBinary command On receiving the ReadBinary command, the SRTAG2K-D reads the requested memory field and sends back its value in the R-APDU response. DocID025446 Rev 3 27/51 RF command sets SRTAG2K-D 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 29 defines the ReadBinary command. Table 29. C-APDU of the ReadBinary command Name CLA INS P1 & P2 Lc Data Le 0x00 0xB0 2 bytes - - 1 byte Class byte Read instruction code Offset in the file selected Number of bytes to read between 0x01 ≤Le ≤max(Selected File length, 0xF6) Table 30 defines the R-APDU of the ReadBinary command. Table 30. R-APDU of the ReadBinary command 5.6.8 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 Class not supported UpdateBinary command On receiving the UpdateBinary command, the SRTAG2K-D writes the data field into the selected file and sends back a status in the R-APDU response. If needed, M24SR 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 31 defines the UpdateBinary command. 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. 28/51 DocID025446 Rev 3 SRTAG2K-D RF command sets Table 31. 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 SRTAG2K-D memory - Table 32 defines the R-APDU of the UpdateBinary command. Table 32. R-APDU of the UpdateBinary command Note: Data SW1 SW2 Comment Length - 1 byte 1 byte - Value - 0x90 0x00 Command completed Value - 0x65 0x81 Unsuccessful updating Value - 0x67 0x00 Wrong length Value - 0x69 0x82 Security status not satisfied Value - 0x6A 0x82 File or application not found Value - 0x6E 0x00 Class not supported For further return codes and definitions, refer to Status and error codes. DocID025446 Rev 3 29/51 RF command sets 5.7 SRTAG2K-D 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 SRTAG2K-D 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 33 defines the Verify command. Table 33. 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 0x00: the password is not present 0x10: the password is present in the data field Password - 30/51 DocID025446 Rev 3 SRTAG2K-D RF command sets Table 34 defines the R-APDU of the Verify command. Table 34. 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 0x85 The conditions of use are not satisfied (e.g. no NDEF file was selected) 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) Value - 0x6E 0x00 The password transmitted is incorrect and X encodes the number of further allowed retries. Class not supported 1. At each session, the RF host can check a password 3 times. 5.7.2 Change Reference Data command The Change Reference Data command replaces the read or write password related to the NDEF files previously selected. It can be performed only if the security status satisfies the security attributes for this command. Before sending this command, the verify command with the correct NDEF write password shall be issued. Thus, this command changes the reference data of the NDEF file. Table 35 defines the Change Reference Data command. Table 35. Change reference data command format Name CLA INS P1 & P2 Lc Data Le 0x00 0x24 2 bytes 1 byte Lc bytes - Class byte Instruction code Password identification 0x0001: Read password transmit 0x0002: Write password transmit Other: RFU 0x10: the password is present in the data field NDEF file Password - Table 36 defines the R-APDU of the Change Reference Data command. DocID025446 Rev 3 31/51 RF command sets SRTAG2K-D Table 36. R-APDU of the Change Reference Data command 5.7.3 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 CC file or System file selected Value - 0x6A 0x82 File or application not found Value - 0x6A 0x86 Incorrect P1 or P2 values Value - 0x6E 0x00 Class not supported 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 37 defines the Enable Verification requirement command. Table 37. Enable Verification Requirement command format Name CLA INS P1 & P2 Lc Data Le 0x00 0x28 2 bytes - - - Class byte Instruction code New security attributes 0x0001: Enable the read protection of the NDEF file 0x0002: Enable the write protection of the NDEF file Other: RFU - The last five bits identify the password sent in the Verify command. Table 38 defines the R-APDU of the Enable Verification Requirement command. 32/51 DocID025446 Rev 3 SRTAG2K-D RF command sets Table 38. R-APDU of the Enable Verification Requirement command 5.7.4 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 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 39 defines the Disable Verification Requirement command. Table 39. Disable Verification Requirement command format Name CLA INS P1 & P2 Lc Data Le 0x00 0x26 2 bytes - - - Class byte Instruction code New security attributes 0x0001: Disable the read protection of the NDEF file 0x0002: Disable the write protection of the NDEF file Other: RFU - Table 40 defines the R-APDU of the Disable Verification Requirement command. DocID025446 Rev 3 33/51 RF command sets SRTAG2K-D Table 40. R-APDU of the Disable Verification Requirement command 5.8 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 - 0x6E 0x00 Class not supported Value - 0x65 0x81 Update failed 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 SRTAG2K-D 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 41. C-APDU of the ExtendedReadBinary command Name Length CLA INS P1 & P2 Lc Data Le 0xA2 0xB0 2 bytes - - 1 byte ST Class byte Read instruction code Offset in the file selected Number of bytes to read between 0x01 ≤Le ≤0xF6 Table 42 defines the R-APDU of the read binary command. 34/51 DocID025446 Rev 3 SRTAG2K-D RF command sets Table 42. R-APDU of the ExtendedReadBinary command Data 5.8.2 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 Value - 0x6E 0x00 Class not supported 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 43 defines the EnablePermanentState requirement command. Table 43. EnablePermanentState command format Name Length CLA INS P1 & P2 Lc Data Le 0xA2 0x28 2 bytes - - - Class byte Instruction code New security attributes 0x0001: Enable the read protection of the NDEF file 0x0002: Enable the write protection of the NDEF file Other: RFU - Table 44 defines the R-APDU of the EnablePermanentState command. Table 44. R-APDU table of the EnablePermanentState command Data SW1 SW2 Length - 1 byte 1 byte - Value - 0x90 0x00 Command completed Value - 0x65 0x81 Update failed Value - 0x67 0x00 Wrong length DocID025446 Rev 3 comment 35/51 RF command sets SRTAG2K-D Table 44. R-APDU table of the EnablePermanentState command (continued) 5.9 Data SW1 SW2 comment 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 - 0x6E 0x00 Class not supported 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 45 lists the commands that can be issued only by the RF host. The format of these commands is described in the NFC Forum Digital Protocol specification. Table 45. Commands issues by the RF host Family command set NFC-A technology Command name Instruction code ALL_REQ 0x52 (1) SENS_REQ 0x26 (1) SDD_REQ 0x93 or 0x95 or 0x97 SEL_REQ 0x93 or 0x95 or 0x97 SLP_REQ 0x50 1. Code on 7 bits. 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 46 details the RATS command. This command shall be sent after the anticollision process. Table 46. RATS command Name INS Param CRC Byte field 0xE0 1 byte 2 bytes Bit field b7-b4 Instruction code FSDI DID (0 ≤DID ≤14) 2 CRC bytes 36/51 DocID025446 Rev 3 b3-b0 SRTAG2K-D RF command sets The FSDI field codes the FSD that defines the maximum size that an RF host is able to receive. Table 47 gives the conversion from FDSI to FSD. Table 47. Conversion from FDSI to FSD FSDI FSD 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9h0xE 0xF 16 24 32 40 48 64 96 128 256 RFU 256 The DID field defines the value of the addressed SRTAG2K-D. Table 48. ATS response Name TL T0 TA(1) TB(1) TC(1) CRC Byte field 0x05 0x78 1 byte 1 byte 0x02 2 bytes Bit field b8-b5 b4-b1 Length of the ATS response FSCI = 256 bytes The maximum ascending data rate is 106 kbps The maximum descending data rate is 106 kbps FWI field (9.6 ms when TB = 0x50) SFGI field (302 µs when TB = 0x50) The DID is supported 2 CRC bytes The FSCI codes the FSC which stands for the maximum frame size that the SRTAG2K-D is able to receive. The SRTAG2K-D is able to receive up to 256 bytes of command. If the RF host sends a command with more than 256 bytes, the SRTAG2K-D 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 SRTAG2K-D. 5.9.3 PPS command & response PPS (Protocol and Parameter Selection) command and response are defined in ISO/IEC 14443-4, in the Protocol Activation of PICC Type A. The PPS command allows to change the data rates of the ascending (RF host to SRTAG2KD) and descending (SRTAG2K-D to RF host) data rates. DocID025446 Rev 3 37/51 RF command sets SRTAG2K-D Table 49. PPS command - Name INS PPS0 PPS1 CRC Byte field 0xDX 0x11 1 byte 2 bytes Bit field INS b7-b4 b3-b0 0b0000 b3-b2 b1-b0 Instruction code DID PPS1 is present RFU PPS1 Descending data rate Ascending data rate 2 CRC bytes The ascending and descending data rates shall be coded as described in Table 50. Table 50. Ascending and descending data rate coding Value Data rate 0b00 0b01 0b10 0b11 106 kbps RFU RFU RFU When the SRTAG2K-D is able to change both data rates, it returns the following response. The data rate of this response is 106 kbps; then, the SRTAG2K-D changes the ascending and descending data rates. Table 51 gives the details sof the PPS response. Table 51. PPS response Name INS - PPS0 Byte field 0xDX - 0x11 Bit field b8-b5 b4-b1 Response code DID field 2 CRC bytes 38/51 DocID025446 Rev 3 SRTAG2K-D RF device operation 6 RF device operation 6.1 Anticollision and Device Activation command set for the RF interface The SRTAG2K-D device supports the command set defined in the NFC-A Technology and the Type 4A Tag Platform chapters of the NFC Digital Protocol V1.0 specification. 6.2 Open an RFsession Once the RF host has terminated the anticollision procedure and retrieve the ATS response, it shall send the SelectApplication command. The SRTAG2K-D will open an RF session. At this point, the RF host can send the applicative command set. 6.3 Close an RFsession The RF host can close the RF session by issuing one of these methods: 6.4 • send an S(DES) command • turn off the RF field Applicative command set The applicative command set is composed of the following command sets: • the NFC Forum Type 4 Tag command set • the ISO/IEC 7816-4 command set • the proprietary command set DocID025446 Rev 3 39/51 Functional procedures 7 SRTAG2K-D 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 SRTAG2K-D. The NDEF detection procedure is as follows: 7.2 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. Reading of an NDEF message The RF host executes the NDEF read procedure to read the NDEF file. 7.3 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. Reading a locked NDEF file The RF host executes this procedure to read an NDEF file which has been locked previously. 7.4 1. Select the NDEF Tag Application 2. Select the NDEF file 3. Verify the Read password by using the Verify command 4. Read the data in the NDEF file. Locking an NDEF file The RF host executes this procedure to protect an NDEF file. 40/51 1. Select the NDEF Tag Application 2. Check the right access provided by the CC file 3. Select the NDEF file 4. Transmit the NDEF file Write password by using the Verify command 5. Lock the NDEF file by sending the Enable verification command. DocID025446 Rev 3 SRTAG2K-D 7.5 Functional procedures Unlocking an NDEF file The RF host executes this procedure to read an NDEF file which has been locked previously. 7.6 1. Select the NDEF Tag Application 2. Select the NDEF file 3. Verify the NDEF file Write password by using the Verify command 4. Unlock the NDEF file by sending the Disable verification command. Reaching the read-only state for an NDEF file The RF host executes this procedure to read an NDEF file which has been locked previously. 7.7 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 as the Write access right of the previous Select NDEF file. Changing an NDEF password procedure The RF host could use this procedure to change one NDEF password. it can be a Read or Write password. 7.8 1. Select the NDEF Tag Application 2. Select the NDEF file 3. Transmit the NDEF file Write password by using the Verify command 4. Change the password by sending a ChangeReferenceData command. 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. DocID025446 Rev 3 41/51 UID: Unique identifier 8 SRTAG2K-D UID: Unique identifier The SRTAG2K-D 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 52 describes the UID format. Table 52. UID format 0x02 IC manufacturer code SRTAG2K-D product code Device number 42/51 DocID025446 Rev 3 0xD2 5 bytes SRTAG2K-D 9 Maximum rating Maximum rating Stressing the device above the rating listed in Table 53 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 53. Absolute maximum ratings Symbol TA Parameter Ambient operating temperature TSTG, hSTG, Storage conditions tSTG TSTG TSTG RFSession ICC (3) VMAX_1 (3) VMAX_2 (3) VESD VESD Max. Unit -40 85 °C 15 25 °C Sawn wafer on UV tape 6 (1) months kept in its original packing form Storage temperature UFDFPN8 –65 150 °C Storage temperature Sawn Bumped Wafer (kept in its antistatic bag) 15 25 °C 6 months Storage time TLEAD Min. Lead temperature during soldering see note (2) UFDFPN8 °C RF Session pad output range -0.50 6.5 V RF supply current AC0 - AC1 - 100 mA RF input voltage amplitude between AC0 and AC1, GND pad left floating - 10 V -0.5 4.5 V Electrostatic discharge voltage (human body AC0-AC1 model) (4) - 1000 V Electrostatic discharge voltage (human body RF Session model) (4) - 3500 V VAC0-VAC1 AC voltage between VAC0-GND or AC0 and GND, or AC1 VAC1-GND and GND 1. Counted from ST shipment date. 2. Compliant with JEDEC Std J-STD-020D (for small body, Sn-Pb or Pb assembly), the ST ECOPACK® 7191395 specification, and the European directive on Restrictions on Hazardous Substances (ROHS directive 2011/65/EU, July 2011). 3. Based on characterization, not tested in production. Maximum absorbed power = 100 mW @ 7.5 A/m 4. AEC-Q100-002 (compliant with JEDEC Std JESD22-A114A, C1 = 100 pF, R1 = 1500 Ω, R2 = 500 Ω) DocID025446 Rev 3 43/51 Maximum rating SRTAG2K-D Table 54. DC characteristics Symbol VOL 44/51 Parameter Output low voltage (RF session pad) Test condition Min. Max. Unit IOL = 1 mA, VCC = 2.7 to 5.5 V - 0.4 V DocID025446 Rev 3 SRTAG2K-D 10 RF Session pad parameters RF Session pad parameters This section lists the timing of the RF Session pad according to its configuration. Table 55. RF Session pad timings measurement (1) RF Session pad Session Open I/F Condition Command Symbol Typ. Unit RF RF Session pad low when session active NDEF select CmdEOFtoGPlow 170 µs RF RF Session pad return HZ Deselect CmdEOFtoGPHZ 370 µs 0x11 1. Characterized only. DocID025446 Rev 3 45/51 RF electrical parameters 11 SRTAG2K-D 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 56. Default operating conditions Symbol TA Parameter Ambient operating temperature Min. Max. Unit –40 85 °C Table 57. RF characteristics (1) Symbol fC H_ISO H_Extended MICARRIER Parameter Condition Min Typ Max Unit 13.553 13.56 13.567 MHz TA = 0 °C to 50 °C 1500 - 7500 mA/m TA = -40 °C to 85 °C 500 - 7500 mA/m MI=(A-B)/(A+B) 90 - 100 % External RF signal frequency Operating field according to ISO Operating field in extended temperature range 100% carrier modulation index t1 Pause A length - 28/fC - 40.5/fC µs t2 Pause A low time - 7/fC - t1 µs t3 Pause A rise time - 1.5xt4 - 16/fC µs t4 Pause A rise time section - 0 - 6/fC µs tMIN CD Minimum time from carrier generation to first data From H-field min - - 5 ms - - 6 - ms fC = 13.56 MHz 22.5 25 27.5 pF Chip reset - - 5 ms Wt CTUN tRF_OFF RF write time (including internal Verify) for one page Internal tuning capacitor in SO8 (2) RF OFF time 1. All timing characterizations were performed on a reference antenna with the following characteristics: External size: 75 mm x 48 mm Number of turns: 6 Width of conductor: 0.6 mm Space between two conductors: 0.6 mm Value of the tuning capacitor in SO8: 25 pF (SRTAG2K-D) Value of the coil: 5 µH Tuning frequency: 14.2 MHz. 2. Characterized only, at room temperature only, measured at VAC0-VAC1 = 2 V peak to peak at 13.56 MHz. 46/51 DocID025446 Rev 3 SRTAG2K-D 12 Package mechanical data Package mechanical data 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. 12.1 Mechanical data for the UFDFPN8 package Figure 6. UFDFPN8 - 8-lead ultra thin fine pitch dual flat package, no lead, 2x3 mm, package outline D Ğ >ϭ >ϯ WŝŶϭ ď Ϯ < > Ϯ ĞĞĞ ϭ tͺDĞsϮ 1. Drawing is not to scale. 2. The central pad (area E2 by D2 in the above illustration) is internally pulled to VSS. It must not be connected to any other voltage or signal line on the PCB, for example during the soldering process. DocID025446 Rev 3 47/51 Package mechanical data SRTAG2K-D Table 58. UFDFPN8 - 8-lead ultra thin fine pitch dual flat package, no lead, package data inches (1) millimeters Symbol Typ Min Max Typ Min Max A 0.550 0.450 0.600 0.0217 0.0177 0.0236 A1 0.020 0.000 0.050 0.0008 0.0000 0.0020 b 0.250 0.200 0.300 0.0098 0.0079 0.0118 D 2.000 1.900 2.100 0.0787 0.0748 0.0827 D2 (rev MC) - 1.200 1.600 - 0.0472 0.0630 E 3.000 2.900 3.100 0.1181 0.1142 0.1220 E2 (rev MC) - 1.200 1.600 - 0.0472 0.0630 e 0.500 - - 0.0197 - - K (rev MC) - 0.300 - - 0.0118 - L - 0.300 0.500 - 0.0118 0.0197 L1 - - 0.150 - - 0.0059 L3 - 0.300 - - 0.0118 - - 0.080 - - 0.0031 - eee (2) 1. Values in inches are converted from mm and rounded to 4 decimal digits. 2. Applied for exposed die paddle and terminals. Exclude embedded part of exposed die paddle from measuring. 48/51 DocID025446 Rev 3 SRTAG2K-D 13 Part numbering Part numbering Table 59. Ordering information scheme for packaged devices Example: SRTAG 2K -D MC 6 T /2 Device type SRTAG = Short range tag Memory size 2K = memory size in Kbits Device feature D = digital output Package MC = UFDFPN8 SB12I = 120 µm ± 15 µm bumped and sawn inkless wafer on 8-inch frame Device grade 6 = industrial: device tested with standard test flow over –40 to 85 °C (No parameter for SB12I) Option T = Tape and reel packing (No parameter for SB12I) Capacitance /2 = 25 pF DocID025446 Rev 3 49/51 Revision history 14 SRTAG2K-D Revision history Table 60. Document revision history Date Revision 31-Oct-2013 1 Initial release. 07-Nov-2013 2 Placed Table 4: CC file layout for 1 NDEF file in Section 3.1.2: CC file layout. 3 Edited the third paragraph of Section 5.8.1: ExtendedReadBinary command. Added Section 7.8: Changing a File type Procedure. Removed VESD (machine model) row from Table 53: Absolute maximum ratings. Fixed a typo in Figure 6: UFDFPN8 - 8-lead ultra thin fine pitch dual flat package, no lead, 2x3 mm, package outline title: UFDPFN8 changed into UFDFPN8. Added Table 54: DC characteristics. 24-Feb-2014 50/51 Changes DocID025446 Rev 3 SRTAG2K-D 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. ST PRODUCTS ARE NOT DESIGNED OR AUTHORIZED FOR USE IN: (A) SAFETY CRITICAL APPLICATIONS SUCH AS LIFE SUPPORTING, ACTIVE IMPLANTED DEVICES OR SYSTEMS WITH PRODUCT FUNCTIONAL SAFETY REQUIREMENTS; (B) AERONAUTIC APPLICATIONS; (C) AUTOMOTIVE APPLICATIONS OR ENVIRONMENTS, AND/OR (D) AEROSPACE APPLICATIONS OR ENVIRONMENTS. WHERE ST PRODUCTS ARE NOT DESIGNED FOR SUCH USE, THE PURCHASER SHALL USE PRODUCTS AT PURCHASER’S SOLE RISK, EVEN IF ST HAS BEEN INFORMED IN WRITING OF SUCH USAGE, UNLESS A PRODUCT IS EXPRESSLY DESIGNATED BY ST AS BEING INTENDED FOR “AUTOMOTIVE, AUTOMOTIVE SAFETY OR MEDICAL” INDUSTRY DOMAINS ACCORDING TO ST PRODUCT DESIGN SPECIFICATIONS. PRODUCTS FORMALLY ESCC, QML OR JAN QUALIFIED ARE DEEMED SUITABLE FOR USE IN AEROSPACE BY THE CORRESPONDING GOVERNMENTAL AGENCY. 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. © 2014 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 DocID025446 Rev 3 51/51 ">
/
Unduh
Hanya pengingat ramah. Anda dapat melihat dokumen di sini. Tetapi yang paling penting, AI kami telah membacanya. Ia dapat menjelaskan hal-hal kompleks dengan istilah sederhana, menjawab pertanyaan Anda dalam bahasa apa pun, dan membantu Anda menavigasi dengan cepat bahkan dokumen terpanjang atau paling rumit.
Tautan publik diperbarui
Tautan publik ke obrolan Anda telah diperbarui. You may view and manage your chat links after registration here.
Tautan publik dokumen
Iklan
