 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| 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 (v ss ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 2.3 gpo supply voltage (v dcg ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 2.3.1 operating supply voltage v dcg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.3.2 power-up conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.4 general purpose output (gpo) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.4.1 session open configuratio n (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 configuratio n (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 manageme nt . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 applic ation select command . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 24. r-apdu of the ndef tag applic ation select command . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 25. c-apdu of the capability container sele ct command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 26. r-apdu of the capability container sele ct command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 27. c-apdu of the ndef select comman d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 28. r-apdu of the ndef select comman d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 29. c-apdu of the system file sele ct command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 30. r-apdu of the system file sele ct 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 comma nd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 34. r-apdu of the updatebinary comma nd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 co mmand. . . . . . . . . . . . . . . . . . . . . . . . 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 comman d . . . . . . . . . . . . . . . . . . . . . . . . . . 46 table 47. commands issues by the rf host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7 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 pitc h 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 = 0x 10 or 0x90) . . . . . . . . . . . . . . . . . . . . . 13 figure 6. gpo configured as wip (gpo fi eld = 0x20 or 0xa0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 figure 7. gpo configured as mip (gpo field = 0x30 or 0xb0 ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 8. gpo configured as int (gpo fi eld = 0x40 or 0xc0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 9. gpo configured as state control (gpo field = 0x 50 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 thic kness 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 0 6 9 5 ) l q w h u i d f h e d v h g r q , 6 2 , ( & 7 \ s h $ v w d q g d u g * 3 2 i 9 ' & * $ & $ & * 3 2 9 6 6 3 r z h u p d q d j h p h q w x q l w h / ? ???? u ? h? ? u u}?? $ q d o r j ) u r q w h q g e d v h g r q , 6 2 , ( & 7 \ s h $ v w d q g d u g , q w h u q d o w x q l q j f d s d f l w d q f h ' l j l w d o x q l w 9 ' & * 1 ) & ) r u x p 7 \ s h 7 d j s u r w r f r o 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 packa ge dimensions, and how to identify pin 1. figure 4. 5-pin package connections 1. see package mechanical data section for packa ge dimensions, and how to identify pin 1. 0 6 9 6 7 7 $ . 3 0 l f u r f r q w u r o o h u q ) 9 ' & * 9 6 6 9 ' ' * 3 2 , 2 $ & $ & 5 ) d q w h q q d table 1. signal names signal name function direction ac0, ac1 antenna coils - v dcg supply voltage for gpo power v ss ground - gpo interrupt output cmos output 0 6 9 1 & 9 * 3 2 $ & $ & 1 & 9 6 6 1 & ' & * - 3 6 ! # ! # ' 0 / 6 3 3 6 3 3 4 o p v i e w m a r k i n g s i d e " o t t o m v i e w p a d s s i d e ! " # $ 8 9 : 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 (v ss ) v ss , when connected, is the reference for the v dcg supply voltage for all pads, even ac0 and ac1. 2.3 gpo supply voltage (v dcg ) this pin can be connected to an external dc su pply voltage. it only supplies the gpo driver block. 2.3.1 operating supply voltage v dcg prior to checking st25ta02k-p gpo, a valid and stable v dcg voltage within the specified [v dcg (min), v dcg (max)] range must be applied. to maintain a stable dc supply voltage , it is recommended to decouple the v dcg line with suitable capacitors (usually of the order of 10 nf and 100 pf) close to the v dcg /v ss 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 v dcg 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, dr iven 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 st25ta 02k-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 settin g 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 configurat ion (gpo field = 0x10 or 0x90) when the gpo is configured as "session op en", 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 sele ct 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) 0 6 9 5 ) 6 h v v l r q 5 ) 6 h v v l r q 5 ) f k d q q h o * 3 2 d v 6 h v v l r q 2 s h q $ q w l f r o o l v l r q 1 ' ( ) v h o h f w ' h v h o h f w $ q w l f r o o l v l r q 1 ' ( ) v h o h f w ' h v h o h f w signal descriptions st25ta02k-p 14/64 docid027794 rev 2 2.4.2 wip writing in pr ogress configuration (gpo field = 0x20 or 0xa0) when the gpo is configured as "wip", it g oes 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 corres pondent 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 0 6 9 8 s g d w h f r p p d q g $ q \ r w k h u f r p p d q g 5 ) f k d q q h o * 3 2 d v : , 3 ( q g r i z u l w l q j r s h u d w l r q docid027794 rev 2 15/64 st25ta02k-p signal descriptions 2.4.3 mip ndef messa ge 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 mi p (gpo field = 0x30 or 0xb0) 1. cmdeoftogphigh (rf command end of frame to gpo high) 2. writing time duration 0 6 9 $ q \ r w k h u f r p p d q g 8 s g d w h w k h 1 ' ( ) o h q j w k ? [ 5 ) f k d q q h o * 3 2 d v 0 , 3 6 7 7 $ [ . 3 u h v s r q v h signal descriptions st25ta02k-p 16/64 docid027794 rev 2 2.4.4 int interrupt configurati on (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 st ate at the end of the st25ta02k-p response (see figure 8 ). during an rf session, when st25ta02 k-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 in t (gpo field = 0x40 or 0xc0) 1. cmdeoftogphigh (rf command end of frame to gpo high) 2. respeoftogplow 0 6 9 6 h q g , q w h u u x s w * 3 2 d v , 1 7 $ q \ r w k h u r s h u d w l r q 5 ) f k d q q h o 6 7 7 $ [ . 3 u h v s r q v h docid027794 rev 2 17/64 st25ta02k-p signal descriptions 2.4.5 state control configurati on (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 c ontrol (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) 0 6 9 5 h v h w * 3 2 f r p p d q g $ q \ r w k h u f r p p d q g 6 h w * 3 2 f r p p d q g 5 ) f k d q q h o * 3 2 d v 6 w d w h & r q w u r o 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) 0 6 9 5 ) f r p p d q g q r w v x s s r u w h g 6 h q v 5 h t 6 h q v 5 h v 5 ) f r p p d q g 5 ) f k d q q h o * 3 2 d v 5 ) e x v \ 6 / 3 b 5 ( 4 r u 6 ' ( 6 r u e d g f r p p d q g r u 5 ) ) l h o g 2 ) ) docid027794 rev 2 19/64 st25ta02k-p signal descriptions 2.4.7 field detect configurat ion (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 activi ty during the rf field detection (communication with the reader or not), gpo will stay high. it will be releas ed when st25ta02k-p leaves the rf field. figure 11. field detect (gpo field = 0x70 or 0xf0) 0 6 y 9 + p l q * 3 2 w ) ' ( 7 2 1 5 ) i l h o g 9 ' & * w ) ' ( 7 2 ) ) 9 6 6 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 st 25ta02k-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 identi fier 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 t hat can be read 0x00ff 255 bytes 0x0005 maximum number of bytes t hat 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 whic h 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 co nfiguration 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 si gnificant bit to 1. once locked, these bytes cannot be changed anymore. 0x70 (2) 2. field detect as defaul t 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 writ e 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 pa ssword 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 f ile 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 0 6 9 3 h u p d q h q w o \ o r f n w k h 1 ' ( ) i l o h [ [ [ ) ( / r f n w k h 1 ' ( ) i l o h 8 q o r f n w k h 1 ' ( ) i l o h 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 nd ef 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 av ailable 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. 0 6 9 [ [ [ ) ) / r f n w k h 1 ' ( ) i l o h 8 q o r f n w k h 1 ' ( ) i l o h 3 h u p d q h q w o \ o r f n w k h 1 ' ( ) i l o h 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 che cked by any application, by reading suitable bytes in system file (see section 3.1.4 ). if enabled, the read/write coun ter will be incremented on first event (exclusively read or write) which is performed on the ndef file, insi de 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 increm ented 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 coun ter will have an impact on the execution time of the event which is countered: the counte r increment needs some writ e 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 comma nd 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 th ree 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 st25 ta02k-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 numb er 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 l c data 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 a ll 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 f ile 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 applic ation 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 define d 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 code s and definitions, refer to section 5.6.2: status and error codes . 5.6.4 capability cont ainer select command the rf host uses the capability container se lect procedure to se lect the capability container (cc) file. the cc file is selected when this command re turns "command completed" in the r-apdu. table 25 defines the c-apdu of the se lect 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 code s 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 co mmand returns "command completed" in the r- apdu. table 27 defines the c-apdu of the select comma nd 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 code s 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 co mmand returns "command completed" in the r- apdu. table 29 defines the c-apdu of the command to se lect the system file (called system select). table 30 defines the r-apdu of the sy stem 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 su ccessful 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 code s 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 st 25ta02k-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 f ile 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 code s 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 ext ended features such as the protection of the ndef file. this command set is used to ma nage 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 righ t 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 code s 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 perform ed 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 incompatib le with file structure value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 incorrect para meter 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 re sponse 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 chan ges the access right of the ndef file. table 39 defines the enable verification requirement command. table 38. r-apdu of the chan ge 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 verificati on 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 prot ection 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 pa ssword 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 succe ssful, 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 chan ges 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 re sponse 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 verificati on 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 prot ection 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 comma nd, 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 comm and 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 re sponse 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 code s 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 fo rum 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., nf cid1 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 comma nd 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 comma nd and ats response rats command and ats response are used for nfc forum type 4a tag platform device activation (as defined in nfc foru m digital protocol specification). table 49 details the rats command. this command shall be se nt 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 st25t a02k-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 fram e guard time is the minimum time that the reader shall wait after receiving the response of the st25ta02k-p. 5.9.3 pps comm and & response (b) pps (protocol and parameter se lection) command a nd response are defined in iso/iec 14443-4, in the protocol activation of picc type a. the pps command allows to change the da ta rates of the a scending (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 acti vation 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 th e nfc digital protocol v1.0 specification. 6.2 open an rf session once the rf host has terminated the ant icollision procedure and re trieve the at s response, it shall send the selectapplication comma nd. 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 det ect the ndef message inside an st25ta02k-p. the ndef detection procedure is as follows: 1. open an rf session 2. send the selectnd eftagapplication 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 re ad procedure to read the ndef file. 1. detect successfully t he ndef file using the ndef detection procedure 2. check that the read access without any security is gr anted 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 pa ssword 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 pa ssword by using the verify command 4. unlock the ndef file by sending the disable verification command. 7.6 reaching the read-onl y 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 ab ove 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 specif ication 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 t a ambient operating temperature -40 85 c t stg , h stg , t stg 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 t stg storage temperature ufdfpn5 ?65 150 c t stg storage temperature sawn bumped wafer (kept in its antistatic bag) 15 25 c storage time - 6 months t lead 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 v dcg gpo power supply -0.5 5.5 v i cc (3) 3. based on characterization, not tested in prod uction. maximum absorbed power = 100 mw @ 7.5 a/m rf supply current ac0 - ac1 - 64 ma v max_1 (3) rf input voltage amplitude between ac0 and ac1, v ss pad left floating vac0-vac1 (peak to peak) -10v v max_2 ac voltage between ac0 and v ss , or ac1 and v ss vac0-v ss or vac1-v ss -0.5 4.5 v v esd electrostatic discharge voltage (human body model) (4) 4. aec-q100-002 (compliant with jedec st d jesd22-a114a, c1 = 100 pf, r1 = 1500 , r2 = 500 ) ac0-ac1 - 1500 v v esd 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 me asurement 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 v dcg gpo power supply 1.65 5.5 v table 58. dc characteristics symbol parameter test condition min. max. unit v ol output low voltage (gpo) i ol = 0.7 ma, v dcg = 1.65v - 0.2v dcg v v oh output high voltage (gpo) i oh = -0.7 ma, v dcg = 1.65v 0.8v dcg -v v ol output low voltage (gpo) i ol = 2 ma, v dcg = 2.7v - 0.2v dcg v v oh output high voltage (gpo) i oh = -2 ma, v dcg 2.7v 0.8v dcg -v v ol output low voltage (gpo) i ol = 4 ma, v dcg 5.5v - 0.2v dcg v v oh output high voltage (gpo) i oh = -4 ma, v dcg = 5.5v 0.8v dcg -v table 59. gpo ac characteristics symbol parameter test condition min. max. unit t f (io) out output fall time (1) 1. v ref(t) output timing reference levels 0.3 v dcg to 0.7 v dcg v. c l = 50 pf, v dcg = 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 t r (io) out output rise time (1) c l = 50 pf, v dcg = 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 - t fdeton 140 s t fdetoff 20 s 1. characterized only. 2. writing time is function of the message length and is aut omatically manage by st25ta02k-p. ndef message is mapped on memory blocks of 16 bytes. each basic block has a typi cal 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 characterist ics tables that follow are derived from tests performed under the measurement conditi ons summarized in the relevant tables. designers should check that the operating cond itions in their circuit match the measurement conditions when relying on the quoted parameters. table 61. default operating conditions symbol parameter min. max. unit t a ambient operating temperature ?40 85 c table 62. rf characteristics (1) symbol parameter condi tion min typ max unit f c external rf signal frequency - 13.553 13.56 13.567 mhz h_iso operating field according to iso t a = 0c to 50c 1500 - 7500 ma/m h_extended operating field in extended temperature range t a = -40c to 85c 200 - 7500 ma/m h min field detect, set-up field (1) t a = -40c to 85c - 115 - ma/m mi carrier 100% carrier modulation index mi=(a-b)/(a+b) 90 - 100 % t 1 pause a length - 28 / f c - 40.5 / f c s t 2 pause a low time - 7 / f c -t 1 s t 3 pause a rise time - 1.5xt4 - 16 / f c s t 4 pause a rise time section - 0 - 6 / f c s t min cd minimum time from carrier generation to first data from h-field min - - 5 ms w t rf write time (including internal verify) for one page - - 4.468 (2) -ms c tun / 5 (3) internal tuning capacitor (4) f c = 13.56 mhz 45 50 55 pf t rf_off rf off time chip reset - - 0.1 ms 1. all timing characterizations were performed on a re ference antenna with the fo llowing char acteristics: 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, m easured 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 a nd 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 parti ally or totally according to the cross section. 3. drawing is not to scale. = : d b 0 ( b 9 7 r s y l h z 3 l q , ' p d u n l q j 6 l g h y l h z 6 h d w l q j s o d q h h h h f f f & & & & % $ 1 ' ( d d d d d d $ $ $ [ [ ' d w x p $ 7 h u p l q d o w l s ' h w d l o 3 $ ( y h q w h u p l q d o / / / h h 3 l q , ' p d u n l q j % r w w r p y l h z 6 h h ' h w d l o 3 $ h h 1 ' [ ' / / ( . / e package information st25ta02k-p 60/64 docid027794 rev 2 table 63. ufdfn8 - 8-lead, 2 3 mm, 0.5 mm pi tch 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 meas ured 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 parti ally 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 meas ured 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 - 7 r s y l h z p d u n l q j v l g h ' ( 6 l g h y l h z $ $ $ 8 . b 0 ( b 9 % r w w r p y l h z s d g v v l g h ' ( e n / h 3 l q 3 l q 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 char ge. in no event, st wi ll 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 = -40 o c to +85 o c 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 mi p (gpo field = 0x30 or 0xb0) and figure 8: gpo configured as in t (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 in formation 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 o rder 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 |
Price & Availability of ST25TA02K-PC6H5
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |