View LRIS64K_8286878.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

october 2011 doc id 15336 rev 11 1/100 1 LRIS64K 64 kbit eeprom tag ic at 13 .56 mhz with 64-bit uid and password based on iso/iec 15693 and iso/iec 18000-3 mode 1 features based on iso/iec 15693 and iso/iec 18000-3 mode 1 standards 13.56 mhz 7 khz carrier frequency to tag: 10% or 100% ask modulation using 1/4 (26 kbit/s) or 1/256 (1.6 kbit/s) pulse position coding from tag: load modulation using manchester coding with 423 khz and 484 khz subcarriers in low (6.6 kbit/s) or hi gh (26 kbit/s) data rate mode. supports the 53 kbit/s data rate with fast commands internal tuning capacitor (27.5 pf) more than 1 million write cycles more than 40-year data retention 64 kbit eeprom organize d into 2048 blocks of 32 bits 64-bit unique identifier (uid) multipassword protection read block & write (32-bit blocks) write time: 5.75 ms including the internal verify wafer (sbn18) www.st.com
contents LRIS64K 2/100 doc id 15336 rev 11 contents 1 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2 user memory organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3 system memory area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.1 LRIS64K rf block security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.2 example of the LRIS64K security protection . . . . . . . . . . . . . . . . . . . . . . 17 4 initial delivery state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.1 initial dialogue for vicinity cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.1.1 power transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.1.2 frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.1.3 operating field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6 communication signal from vcd to LRIS64K . . . . . . . . . . . . . . . . . . . 21 7 data rate and data coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.1 data coding mode: 1 out of 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.2 data coding mode: 1 out of 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.3 vcd to LRIS64K frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.4 start of frame (sof) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 8 communications signal from lr is64k to vcd . . . . . . . . . . . . . . . . . . 27 8.1 load modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 8.2 subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 8.3 data rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 9 bit representation and coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 9.1 bit coding using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 9.1.1 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 9.1.2 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 9.2 bit coding using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
LRIS64K contents doc id 15336 rev 11 3/100 9.3 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 9.4 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 10 LRIS64K to vcd frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 10.1 sof when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 10.2 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 10.3 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 10.4 sof when using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 10.5 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 10.6 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 10.7 eof when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 10.8 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 10.9 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 10.10 eof when using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 10.11 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 10.12 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 11 unique identifier (uid) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 12 application family identifier (a fi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 13 data storage format identifier (dsfid) . . . . . . . . . . . . . . . . . . . . . . . . . 37 13.1 crc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 14 LRIS64K protocol descrip tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 15 LRIS64K states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 15.1 power-off state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 15.2 ready state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 15.3 quiet state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 15.4 selected state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 16 modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 16.1 addressed mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 16.2 non-addressed mode (general request) . . . . . . . . . . . . . . . . . . . . . . . . . 42
contents LRIS64K 4/100 doc id 15336 rev 11 16.3 select mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 17 request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 17.1 request flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 18 response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 18.1 response flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 18.2 response error code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 19 anticollision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 19.1 request parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 20 request processing by the lris 64k . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 21 explanation of the possible cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 22 inventory initiated command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 23 timing definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 23.1 t1: LRIS64K response delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 23.2 t2: vcd new request delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 23.3 t 3 : vcd new request delay in the absence of a response from the LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 24 commands codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 24.1 inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 24.2 stay quiet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 24.3 read single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 24.4 write single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 24.5 read multiple block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 24.6 select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 24.7 reset to ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 24.8 write afi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 24.9 lock afi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 24.10 write dsfid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 24.11 lock dsfid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
LRIS64K contents doc id 15336 rev 11 5/100 24.12 get system info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 24.13 get multiple block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 24.14 write-sector password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 24.15 lock-sector password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 24.16 present-sector password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 24.17 fast read single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 24.18 fast inventory initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 24.19 fast initiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 24.20 fast read multiple block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 24.21 inventory initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 24.22 initiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 25 maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 26 rf dc and ac parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 27 part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 appendix a anticollision algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 a.1 algorithm for pulsed slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 appendix b crc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 b.1 crc error detection method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 b.2 crc calculation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 appendix c application family identif ier (afi). . . . . . . . . . . . . . . . . . . . . . . . . . . 98 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
list of tables LRIS64K 6/100 doc id 15336 rev 11 list of tables table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 table 2. sector details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 table 3. sector security status byte area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 table 4. sector security status byte organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 5 table 5. read / write protection bit setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 6. password control bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 7. password system area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 8. sector security protection after power-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 9. sector security protection after a valid presentation of password 1 . . . . . . . . . . . . . . . . . . 17 table 10. 10% modulation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 11. response data rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 12. uid format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 table 13. crc transmission rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 14. vcd request frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 15. LRIS64K response frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 8 table 16. LRIS64K response depending on request_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 17. general request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 table 18. definition of request flags 1 to 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 table 19. request flags 5 to 8 when bit 3 = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 20. request flags 5 to 8 when bit 3 = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 table 21. general response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 table 22. definitions of response flags 1 to 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 table 23. response error code definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 table 24. inventory request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 25. example of the addition of 0-bits to an 11-bit mask value . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 26. timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 27. command codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 table 28. inventory request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 table 29. inventory response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 table 30. stay quiet request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 table 31. read single block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 table 32. read single block response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . 57 table 33. sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 table 34. read single block response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . 57 table 35. write single block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 table 36. write single block response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . 59 table 37. write single block response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . 59 table 38. read multiple block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 table 39. read multiple block response format when error_flag is not set. . . . . . . . . . . . . . . . . . . 61 table 40. sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 table 41. read multiple block response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . 62 table 42. select request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 table 43. select block response format when error_flag is not set. . . . . . . . . . . . . . . . . . . . . . . . . 63 table 44. select response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 table 45. reset to ready request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 table 46. reset to ready response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . 64 table 47. reset to ready response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 table 48. write afi request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
LRIS64K list of tables doc id 15336 rev 11 7/100 table 49. write afi response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 table 50. write afi response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 table 51. lock afi request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 table 52. lock afi response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 table 53. lock afi response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 table 54. write dsfid request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 55. write dsfid response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . 69 table 56. write dsfid response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 57. lock dsfid request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 58. lock dsfid response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 59. lock dsfid response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 60. get system info request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 61. get system info response format when error_flag is not set. . . . . . . . . . . . . . . . . . . . . . 73 table 62. get system info response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 63. get multiple block security status request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 64. get multiple block security status response format when error_flag is not set . . . . . . . 75 table 65. sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 66. get multiple block security status response format when error_flag is set . . . . . . . . . . . . 76 table 67. write-sector password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 table 68. write-sector password response format when error_flag is not set . . . . . . . . . . . . . . . . 77 table 69. write-sector password response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . 77 table 70. lock-sector password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 table 71. sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 table 72. lock-sector password response format when error_flag is not set . . . . . . . . . . . . . . . . . 79 table 73. lock-sector password response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . 79 table 74. present-sector password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 table 75. present-sector password response format when error_flag is not set . . . . . . . . . . . . . . 81 table 76. present-sector password response format when error_flag is set . . . . . . . . . . . . . . . . . . . 81 table 77. fast read single block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 table 78. fast read single block response format when error_flag is not set . . . . . . . . . . . . . . . . 83 table 79. sector security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 table 80. fast read single block response format when error_flag is set . . . . . . . . . . . . . . . . . . . . 83 table 81. fast inventory initiated request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 table 82. fast inventory initiated response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5 table 83. fast initiate request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 table 84. fast initiate response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 table 85. fast read multiple block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 table 86. fast read multiple block response format when error_flag is not set. . . . . . . . . . . . . . . 87 table 87. sector security status if option_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 table 88. fast read multiple block response format when error_flag is set . . . . . . . . . . . . . . . . . . . 88 table 89. inventory initiated request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 table 90. inventory initiated response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 table 91. initiate request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 table 92. initiate initiated response format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 table 93. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 table 94. rf ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 table 95. rf dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 table 96. operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 table 97. ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 table 98. crc definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 table 99. afi coding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 table 100. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
list of figures LRIS64K 8/100 doc id 15336 rev 11 list of figures figure 1. pad connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 2. memory sector organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 3. 100% modulation waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 figure 4. 10% modulation waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 figure 5. 1 out of 256 coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 figure 6. detail of a time period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 figure 7. 1 out of 4 coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 8. 1 out of 4 coding example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 9. sof to select 1 out of 256 data coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 10. sof to select 1 out of 4 data coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 11. eof for either data coding mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 12. logic 0, high data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 13. logic 0, high data rate, one subcarriers x2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 14. logic 1, high data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 15. logic 1, high data rate, one subcarriers x2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 16. logic 0, low data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 17. logic 0, low data rate, one subcarriers x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 18. logic 1, low data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 19. logic 1, low data rate, one subcarriers x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 figure 20. logic 0, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 21. logic 1, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 22. logic 0, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 23. logic 1, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 figure 24. start of frame, high data rate, one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 figure 25. start of frame, high data rate, one subcarrier x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 figure 26. start of frame, low data rate, one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 figure 27. start of frame, low data rate, one subcarrier x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 figure 28. start of frame, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2 figure 29. start of frame, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2 figure 30. end of frame, high data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 31. end of frame, high data rate, one subcarriers x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 32. end of frame, low data rate, one subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 33. end of frame, low data rate, one subcarriers x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 figure 34. end of frame, high data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 figure 35. end of frame, low data rate, two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 figure 36. LRIS64K decision tree for afi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 figure 37. LRIS64K protocol timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 figure 38. LRIS64K state transition diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 figure 39. principle of comparison between the mask, the slot number and the uid . . . . . . . . . . . . . 48 figure 40. description of a po ssible anticollision sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 figure 41. stay quiet frame exchange between vcd and LRIS64K. . . . . . . . . . . . . . . . . . . . . . . . . . 56 figure 42. read single block frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . 58 figure 43. write single block frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . 60 figure 44. read multiple block frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . 62 figure 45. select frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 figure 46. reset to ready frame exchange between vcd and LRIS64K. . . . . . . . . . . . . . . . . . . . . . 64 figure 47. write afi frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . 66 figure 48. lock afi frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
LRIS64K list of figures doc id 15336 rev 11 9/100 figure 49. write dsfid frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . 70 figure 50. lock dsfid frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . 72 figure 51. get system info frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . . . 74 figure 52. get multiple block security status frame exchange between vcd and LRIS64K . . . . . . . 76 figure 53. write-sector password frame exchange betwee n vcd and LRIS64K . . . . . . . . . . . . . . . . 78 figure 54. lock-sector password frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . 80 figure 55. present-sector password frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . 82 figure 56. fast read single block frame exchange betw een vcd and LRIS64K . . . . . . . . . . . . . . . 84 figure 57. fast initiate frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . 86 figure 58. fast read multiple block frame exchange be tween vcd and LRIS64K . . . . . . . . . . . . . . 88 figure 59. initiate frame exchange between vcd and LRIS64K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 figure 60. LRIS64K synchronous timing, transmit and receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
description LRIS64K 10/100 doc id 15336 rev 11 1 description the LRIS64K is a contactless memory powered by the received carrier electromagnetic wave, which follows the iso/iec 15693 and iso/iec 18000-3 mode 1 recommendation for radio-frequency power and signal interface. it is a 64 kbit electrically erasable programmable memory (eeprom). the memory is organized as 64 sectors divi ded into 32 blocks of 32 bits. the LRIS64K is accessed via the 13.56 mhz carrier electromagnetic wave, on which incoming data are demodulate d from the received signal amplitude modulation (ask: amplitude shift keying). the received ask wave is 10% or 100% modu lated with a data rate of 1.6 kbit/s using the 1/256 pulse coding mode, or a data rate of 26 kbit/s using the 1/4 pulse coding mode. outgoing data are generated by the LRIS64K load variation using manchester coding with one or two subcarrier frequencies at 423 khz and 484 khz. data are transferred from the LRIS64K at 6.6 kbit/s in low data rate mode and 26 kbit/s in high data rate mode. the LRIS64K supports the 53 kbit/s data rate in high data rate mode with a single subcarrier frequency of 423 khz. the LRIS64K also features a unique 32-bit multi-password protection scheme. figure 1. pad connection table 1. signal names signal name function direction ac0 antenna coil i/o ac1 antenna coil i/o ai15689 ac1 ac0 power supply regulator manchester load modulator ask demodulator 64 kbit eeprom memory
LRIS64K user memory organization doc id 15336 rev 11 11/100 2 user memory organization the LRIS64K is divided into 64 sectors of 32 blocks of 32 bits as shown in ta b l e 2 . figure 2 shows the memory sector organization. each sector can be individually read- and/or write- protected using a specific password command. read and write operations are possible if the addressed data are not in a protected sector. the LRIS64K also has a 64-bit block that is used to store the 64-bit unique identifier (uid). the uid is compliant with the is o/iec 15963 description, and its value is used during the anticollision sequence (inventory). this block is not accessible by the user and its value is written by st on the production line. the LRIS64K includes an afi register that stores the application family identifier, and a dsfid register that st ores the data storage family iden tifier used in the anticollision algorithm. the LRIS64K has three additional 32-bit blocks that store the rf password codes. figure 2. memory sector organization sector details the LRIS64K user memory is divided into 64 se ctors. each sector contains 1024 bits. the protection scheme is described in section 3: system memory area . a sector provides 32 blocks of 32 bits. each read and write access are done by block. read and write block accesses are controlled by a sector security status byte that defines the access rights to all the 32 blocks contained in the sector. if the sector is not protected, a write command updates the complete 32 bits of the selected block. +bit%%02/-sector bits +bit%%02/-sector bits +bit%%02/-sector bits +bit%%02/-sector bits +bit%%02/-sector bits +bit%%02/-sector bits +bit%%02/-sector bits +bit%%02/-sector bits 2&0assword 3ystem 2&0assword 3ystem 2&0assword 3ystem bit$3&)$ 3ystem bit!&) 3ystem bit5)$ 3ystem 3ector !rea 3ectorsecurity status ai
user memory organization LRIS64K 12/100 doc id 15336 rev 11 table 2. sector details sector number rf block address bits [31:24] bits [23:16] bits [15:8] bits [7:0] 0 0 user user user user 1 user user user user 2 user user user user 3 user user user user 4 user user user user 5 user user user user 6 user user user user 7 user user user user 8 user user user user 9 user user user user 10 user user user user 11 user user user user 12 user user user user 13 user user user user 14 user user user user 15 user user user user 16 user user user user 17 user user user user 18 user user user user 19 user user user user 20 user user user user 21 user user user user 22 user user user user 23 user user user user 24 user user user user 25 user user user user 26 user user user user 27 user user user user 28 user user user user 29 user user user user 30 user user user user 31 user user user user
LRIS64K user memory organization doc id 15336 rev 11 13/100 1 32 user user user user 33 user user user user 34 user user user user 35 user user user user 36 user user user user 37 user user user user 38 user user user user 39 user user user user ... ... ... ... ... ... ... ... ... ... ... 63 2016 user user user user 2017 user user user user 2018 user user user user 2019 user user user user 2020 user user user user 2021 user user user user 2022 user user user user 2023 user user user user 2024 user user user user 2025 user user user user 2026 user user user user 2027 user user user user 2028 user user user user 2029 user user user user 2030 user user user user 2031 user user user user 2032 user user user user 2033 user user user user 2034 user user user user 2035 user user user user 2036 user user user user 2037 user user user user 2038 user user user user 2039 user user user user table 2. sector details (continued) sector number rf block address bits [31:24] bits [23:16] bits [15:8] bits [7:0]
user memory organization LRIS64K 14/100 doc id 15336 rev 11 63 continued 2040 user user user user 2041 user user user user 2042 user user user user 2043 user user user user 2044 user user user user 2045 user user user user 2046 user user user user 2047 user user user user table 2. sector details (continued) sector number rf block address bits [31:24] bits [23:16] bits [15:8] bits [7:0]
LRIS64K system memory area doc id 15336 rev 11 15/100 3 system memory area 3.1 LRIS64K rf block security the LRIS64K provides a special protection mechanism based on passwords. each memory sector of the LRIS64K can be individually protected by one out of three available passwords, and each sector can also have read/write access conditions set. each memory sector of the LRIS64K is assigned with a sector security status byte including a sector lock bit, two password control bits and two read/write protection bits as shown in ta bl e 4 . ta b l e 3 describes the organization of the sector security status byte which can be read using the read single block and read multiple block commands with the option_flag set to ?1?. on delivery, the default value of the sss bytes is reset to 00h. table 3. sector security status byte area rf address bits [31:24] bits [23:16] bits [15:8] bits [7:0] 0 sss 3 sss 2 sss 1 sss 0 128 sss 7 sss 6 sss 5 sss 4 256 sss 11 sss 10 sss 9 sss 8 384 sss 15 sss 14 sss 13 sss 12 512 sss 19 sss 18 sss 17 sss 16 640 sss 23 sss 22 sss 21 sss 20 768 sss 27 sss 26 sss 25 sss 24 896 sss 31 sss 30 sss 29 sss 28 1024 sss 35 sss 34 sss 33 sss 32 1152 sss 39 sss 38 sss 37 sss 36 1280 sss 43 sss 42 sss 41 sss 40 1408 sss 47 sss 46 sss 45 sss 44 1536 sss 51 sss 50 sss 49 sss 48 1664 sss 55 sss 54 sss 53 sss 52 1792 sss 59 sss 58 sss 57 sss 56 1920 sss 63 sss 62 sss 61 sss 60 table 4. sector security status byte organization b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 0 0 0 password control bits read / write protection bits sector lock
system memory area LRIS64K 16/100 doc id 15336 rev 11 when the sector lock bit is set to ?1?, for instance by issuing a lock-sector password command, the 2 read/write protection bits (b 1 , b 2 ) are used to set the read/write access of the sector as described in ta b l e 5 . the next 2 bits of the sector security status byte (b 3 , b 4 ) are the password control bits. the value these two bits is used to link a password to the sector as defined in ta b l e 6 . the LRIS64K password protection is organized around a dedicated set of commands plus a system area of three password blocks where the password values are stored. this system area is described in ta b l e 7 . the dedicated password commands are: write-sector password the write-sector password command is used to write a 32-bit block into the password system area. this command must be used to update password values. after the write cycle, the new password value is automatica lly activated. it is possible to modify a password value after issuing a valid present-sector password command. on delivery, the three default password values are set to 0000 0000h and are activated. lock-sector password the lock-sector password command is used to set the sector security status byte of the selected sector. bits b 4 to b 1 of the sector security status byte are affected by the table 5. read / write protection bit setting sector lock b 2 , b 1 sector access when password presented sector access when password not presented 0 xx read write read write 1 00 read write read no write 1 01 read write read write 1 10 read write no read no write 1 11 read no write no read no write table 6. password control bits b 4 , b 3 password 00 the sector is not protected by a password 01 the sector is protected by the password 1 10 the sector is protected by the password 2 11 the sector is protected by the password 3 table 7. password system area add 0 7 8 15 16 23 24 31 1 password 1 2 password 2 3 password 3
LRIS64K system memory area doc id 15336 rev 11 17/100 lock-sector password command. the sector lock bit, b 0 , is set to ?1? automatically. after issuing a lock-sector password command, the protection settings of the selected sector are activated. the protection of a locked block cannot be changed. a lock- sector password command sent to a locked sector returns an error code. present-sector password the present-sector password command is used to present one of the three passwords to the LRIS64K in order to modify the access rights of all the memory sectors linked to that password ( ta bl e 5 ) including the password itself. if the presented password is correct, the access rights remain activated until the tag is powered off or until a new present-sector password command is issued. if the presented password value is not correct, all the access rights of all the memory sectors are deactivated. 3.2 example of the lris 64k security protection ta bl e 8 and ta bl e 9 show the sector security protections before and after a valid present- sector password command. ta b l e 8 shows the sector access ri ghts of an LRIS64K after power-up. after a valid present-sector password command with password 1, the memory sector access is changed as shown in ta b l e 9 . table 8. sector security protection after power-up sector address sector security status byte b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 0 protection: standard read no write xxx 00001 1 protection: pswd 1 read no write xxx 01001 2 protection: pswd 1 read write xxx 01011 3 protection: pswd 1 no read no write xxx 01101 4 protection: pswd 1 no read no write xxx 01111 table 9. sector security protection after a valid presentation of password 1 sector address sector security status byte b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 0 protection: standard read no write xxx 0 0 0 0 1 1 protection: pswd 1 read write xxx 0 1 0 0 1 2 protection: pswd 1 read write xxx 0 1 0 1 1 3 protection: pswd 1 read write xxx 0 1 1 0 1 4 protection: pswd 1 read no write xxx 0 1 1 1 1
initial delivery state LRIS64K 18/100 doc id 15336 rev 11 4 initial delivery state the device is delivered with the following factory settings: all bits in the memory array are set to 1 (each byte contains ffh). the default value of the sss bytes is reset to 00h. the three default password values are set to 0000 0000h and are activated. system parameters are set to: (e0 02 xx xx xx xx xx xx )h for uid (03 07 ff)h for memory size 00h for afi 00h for dsfid
LRIS64K commands doc id 15336 rev 11 19/100 5 commands the LRIS64K supports the following commands: inventory , used to perform the anticollision sequence. stay quiet , used to put the LRIS64K in quiet mode, where it does not respond to any inventory command. select , used to select the LRIS64K. after this command, the LRIS64K processes all read/write commands with select_flag set. reset to ready , used to put the LRIS64K in the ready state. read block , used to output the 32 bits of the selected block and its locking status. write block , used to write the 32-bit value in the selected block, provided that it is not locked. read multiple blocks , used to read the selected blocks and send back their value. write afi , used to write the 8-bit value in the afi register. lock afi , used to lock the afi register. write dsfid , used to write the 8-bit value in the dsfid register. lock dsfid , used to lock the dsfid register. get system info , used to provide the system information value get multiple block security status , used to send the security status of the selected block. initiate , used to trigger the tag response to the inventory initiated sequence. inventory initiated , used to perform the anticollision sequence triggered by the initiate command. write-sector password , used to write the 32 bits of the selected password. lock-sector password , used to write the sector security status bits of the selected sector. present-sector password , enables the user to present a password to unprotect the user blocks linked to this password. fast initiate , used to trigger the tag response to the inventory initiated sequence. fast inventory initiated , used to perform the anticollis ion sequence triggered by the initiate command. fast read single block , used to output the 32 bits of the selected block and its locking status. fast read multiple blocks , used to read the selected blocks and send back their value.
commands LRIS64K 20/100 doc id 15336 rev 11 5.1 initial dialogue for vicinity cards the dialog between the vicinity coupling device (vcd) and the vicinity integrated circuit card or vicc (LRIS64K) takes place as follows: activation of the LRIS64K by the rf operating field of the vcd. transmission of a command by the vcd. transmission of a response by the LRIS64K. these operations use the rf power transfer an d communication signal interface described below (see power transfer , frequency and operating field ). this technique is called rtf (reader talk first). 5.1.1 power transfer power is transferred to the LRIS64K by radi o frequency at 13.56 mhz via coupling antennas in the LRIS64K and the vcd. the rf operating field of the vcd is transformed on the LRIS64K antenna to an ac voltage which is rectified, filtered and internally regulated. the amplitude modulation (ask) on this received signal is demodulated by the ask demodulator. 5.1.2 frequency the iso/iec 15693 standard defines the carrier frequency ( f c ) of the operating field as 13.56 mhz 7 khz. 5.1.3 operating field the LRIS64K operates continuously between h min and h max . the minimum operating field is h min and has a value of 150 ma/m rms. the maximum operating field is h max and has a value of 5 a/m rms. a vcd shall generate a field of at least h min and not exceeding h max in the operating volume.
LRIS64K communication signal from vcd to LRIS64K doc id 15336 rev 11 21/100 6 communication signal from vcd to LRIS64K communications between the vcd and the LRIS64K takes place using the modulation principle of ask (amplitude sh ift keying). two modulation indexes are used, 10% and 100%. the LRIS64K decodes both. the vcd determines which index is used. the modulation index is defined as [a ? b]/[a + b] where a is the peak signal amplitude and b, the minimum signal amplitude of the carrier frequency. depending on the choice made by the vcd, a ?pause? will be created as described in figure 3 and figure 4 . the LRIS64K is operational for any degree of modulation index from between 10% and 30%. figure 3. 100% modulation waveform table 10. 10% modulation parameters symbol parameter definition value hr 0.1 x (a ? b) max hf 0.1 x (a ? b) max 105 % a 95 % 5 % 60 % c a rrier amplit u de t t 2 t 1 t 3 t 4 min ( s ) t 1 6,0 t 2 2,1 t 3 0 m a x ( s ) 9,44 t 1 4,5 t 4 0 0, 8 b the clock recovery s h a ll b e oper a tion a l a fter t 4 m a x. a i1579 3
communication signal from vcd to LRIS64K LRIS64K 22/100 doc id 15336 rev 11 figure 4. 10% modulation waveform the vicc s h a ll b e oper a tion a l for a ny v a l u e of mod u l a tion index b etween 10 % a nd 3 0 % . min 6,0 s t2 3 ,0 s t 3 0 m a x 9,44 s t1 4,5 s mod u l a tion index t1 10 % 3 0 % hf, hr 0,1 ( a - b ) m a x y 0,05 ( a - b ) t1 t2 hf y hr t 3 t y a b c a rrier amplit u de min 6,0 s t2 3 ,0 s t 3 0 m a x 9,44 s t1 4,5 s mod u l a tion index t1 10 % 3 0 % min 6,0 s t2 3 ,0 s t 3 0 m a x 9,44 s t1 4,5 s mod u l a tion index t1 10 % 3 0 % hf, hr 0,1 ( a - b ) m a x y 0,05 ( a - b ) hf, hr 0,1 ( a - b ) m a x y 0,05 ( a - b ) t1 t2 hf y hr t 3 t y a b c a rrier amplit u de a i15794
LRIS64K data rate and data coding doc id 15336 rev 11 23/100 7 data rate and data coding the data coding implemented in the LRIS64K uses pulse position modulation. both data coding modes that are described in the iso/iec15693 are supported by the LRIS64K. the selection is made by the vcd and indicated to the LRIS64K within the start of frame (sof). 7.1 data coding mode: 1 out of 256 the value of one single byte is represented by the position of one pause. the position of the pause on 1 of 256 successive time periods of 18.88 s (256/ f c ), determines the value of the byte. in this case the transmission of one byte takes 4.833 ms and the resulting data rate is 1.65 kbits/s ( f c /8192). figure 5 illustrates this pulse positi on modulation technique. in this figure, data e1h (225 decimal) is sent by the vcd to the LRIS64K. the pause occurs during the second half of the position of the time period that determines the value, as shown in figure 6 . a pause during the first period transmits the data value 00h. a pause during the last period transmit the data value ffh (255 decimal). figure 5. 1 out of 256 coding mode ai06656 0 1 2 3 . . . . . . . . 2 . . . . . . . . . . . . . . . . . . . . . 2 2 2 2 . . . . . . . . . 2 . . . . . . . . . . . . . . . . . . . . . 5 5 5 5 . . . . . . . . . 5 . . . . . . . . . . . . . . . . . . . . . 2 3 4 5 4.833 ms 18.88 s 9.44 s pulse modulated carrier
data rate and data coding LRIS64K 24/100 doc id 15336 rev 11 figure 6. detail of a time period 7.2 data coding mode: 1 out of 4 the value of 2 bits is represented by the position of one pause. the position of the pause on 1 of 4 successive time periods of 18.88 s (256/ f c ), determines the value of the 2 bits. four successive pairs of bits form a byte, where the least significant pair of bits is transmitted first. in this case the transmission of one byte takes 302.08 s and the resulting data rate is 26.48 kbits/s ( f c /512). figure 7 illustrates the 1 out of 4 pulse position technique and coding. figure 8 shows the transmission of e1h (225d - 1110 0001b) by the vcd. ai06657 2 2 5 18.88 s 9.44 s pulse modulated carrier 2 2 6 2 2 4 . . . . . . . . . . . . . . time period one of 256
LRIS64K data rate and data coding doc id 15336 rev 11 25/100 figure 7. 1 out of 4 coding mode figure 8. 1 out of 4 coding example ai06658 9.44 s 9.44 s 75.52 s 28.32 s 9.44 s 75.52 s 47.20 s 9.44 s 75.52 s 66.08 s 9.44 s 75.52 s pulse position for "00" pulse position for "11" pulse position for "10" (0=lsb) pulse position for "01" (1=lsb) ai06659 75.52 s 75.52 s 75.52 s 75.52 s 00 10 01 11
data rate and data coding LRIS64K 26/100 doc id 15336 rev 11 7.3 vcd to LRIS64K frames frames are delimited by a start of frame (sof) and an end of frame (eof). they are implemented using code violation. unus ed options are reserved for future use. the LRIS64K is ready to receive a new command frame from the vcd 311.5 s (t 2 ) after sending a response frame to the vcd. the LRIS64K takes a power-up time of 0.1 ms after being activated by the powering field. after this delay, the LRIS64K is ready to receive a command frame from the vcd. 7.4 start of frame (sof) the sof defines the data coding mode the vcd is to use for the following command frame. the sof sequence described in figure 9 selects the 1 out of 256 data coding mode. the sof sequence described in figure 10 selects the 1 out of 4 data coding mode. the eof sequence for either coding mode is described in figure 11 . figure 9. sof to select 1 out of 256 data coding mode figure 10. sof to select 1 out of 4 data coding mode figure 11. eof for either data coding mode ai06661 37.76 s 9.44 s 9.44 s 37.76 s ai06660 37.76 s 9.44 s 9.44 s 37.76 s 9.44 s ai06662 9.44 s 37.76 s 9.44 s
LRIS64K communications signal from LRIS64K to vcd doc id 15336 rev 11 27/100 8 communications signal from LRIS64K to vcd the LRIS64K has several modes defined for some parameters, owing to which it can operate in different noise environments and meet different application requirements. 8.1 load modulation the LRIS64K is capable of communication to the vcd via an inductive coupling area whereby the carrier is loaded to generate a subcarrier with frequency f s . the subcarrier is generated by switching a load in the LRIS64K. the load-modulated amplitude received on the vcd antenna must be of at least 10mv when measured as described in the test methods defined in international standard iso/iec10373-7. 8.2 subcarrier the LRIS64K supports the one-subcarrier and two-subcarrier response formats. these formats are selected by the vcd using the first bit in the protocol header. when one subcarrier is used, the frequency f s1 of the subcarrier load modulation is 423.75 khz ( f c /32). when two subcarriers are used, the frequency f s1 is 423.75 khz ( f c /32), and frequency f s2 is 484.28 khz ( f c /28). when using the two-subcarrier mode, the LRIS64K generates a continuous phase relationship between f s1 and f s2 . 8.3 data rates the LRIS64K can respond using the low or the high data rate format. the selection of the data rate is made by the vcd using the second bit in the protocol header. it also supports the x2 mode available on all the fast commands. ta b l e 1 1 shows the different data rates produced by the LRIS64K using the different response format combinations. table 11. response data rates data rate one subcarrier two subcarriers low standard commands 6.62 kbit/s ( f c /2048) 6.67 kbit/s ( f c /2032) fast commands 13.24 kbit/s ( f c /1024) not applicable high standard commands 26.48 kbit/s ( f c /512) 26.69 kbit/s ( f c /508) fast commands 52.97 kbit/s ( f c /256) not applicable
bit representation and coding LRIS64K 28/100 doc id 15336 rev 11 9 bit representation and coding data bits are encoded using manchester coding, according to the following schemes. for the low data rate, same subcarrier frequency or frequencies is/are used, in this case the number of pulses is multiplied by 4 and all ti mes will increase by this factor. for the fast commands using one subcarrier, all pulse numbers and times are divided by 2. 9.1 bit coding using one subcarrier 9.1.1 high data rate a logic 0 starts with 8 pulses at 423.75 khz (f c /32) followed by an unmodulated time of 18.88 s as shown in figure 12 . figure 12. logic 0, high data rate, one subcarriers for the fast commands, a logic 0 starts with 4 pulses at 423.75 khz (f c /32) followed by an unmodulated time of 9.44 s as shown in figure 13 . figure 13. logic 0, high data rate, one subcarriers x2 a logic 1 starts with an unmodulated time of 18.88 s followed by 8 pulses at 423.75 khz (f c /32) as shown in figure 14 . figure 14. logic 1, high data rate, one subcarriers for the fast commands, a logic 1 starts with an unmodulated time of 9.44 s followed by 4 pulses of 423.75 khz (f c /32) as shown in figure 15 . figure 15. logic 1, high data rate, one subcarriers x2 37.76 s ai12076 18.88 s ai12066 37.76 s ai12077 18.88 s ai12067
LRIS64K bit representation and coding doc id 15336 rev 11 29/100 9.1.2 low data rate a logic 0 starts with 32 pulses at 423.75 khz (f c /32) followed by an unmodulated time of 75.52 s as shown in figure 16 . figure 16. logic 0, low data rate, one subcarriers for the fast commands, a logic 0 starts with 16 pulses at 423.75 khz (f c /32) followed by an unmodulated time of 37.76 s as shown in figure 17 . figure 17. logic 0, low data rate, one subcarriers x2 a logic 1 starts with an unmodulated time of 75.52 s followed by 32 pulses at 423.75 khz (f c /32) as shown in figure 18 . figure 18. logic 1, low data rate, one subcarriers for the fast commands, a logic 1 starts with an unmodulated time of 37.76 s followed by 16 pulses at 423.75 khz (f c /32) as shown in figure 18 . figure 19. logic 1, low data rate, one subcarriers x2 151.04 s ai12068 75.52 s ai12069 151.04 s ai12070 75.52 s ai12071
bit representation and coding LRIS64K 30/100 doc id 15336 rev 11 9.2 bit coding using two subcarriers 9.3 high data rate a logic 0 starts with 8 pulses at 423.75 khz (f c /32) followed by 9 pulses at 484.28 khz (f c /28) as shown in figure 20 . for the fast commands, the x2 mode is not available. figure 20. logic 0, high data rate, two subcarriers a logic 1 starts with 9 pulses at 484.28 khz (f c /28) followed by 8 pulses at 423.75 khz (f c /32) as shown in figure 21 . for the fast commands, the x2 mode is not available. figure 21. logic 1, high data rate, two subcarriers 9.4 low data rate a logic 0 starts with 32 pulses at 423.75 khz (f c /32) followed by 36 pulses at 484.28 khz (f c /28) as shown in figure 22 . for the fast commands, the x2 mode is not available. figure 22. logic 0, low data rate, two subcarriers a logic 1 starts with 36 pulses at 484.28 khz (f c /28) followed by 32 pulses at 423.75 khz (f c /32) as shown in figure 23 . for the fast commands, the x2 mode is not available. figure 23. logic 1, low data rate, two subcarriers 37.46 s ai12074 37.46 s ai12073 149.84 s ai12072 149.84 s ai12075
LRIS64K LRIS64K to vcd frames doc id 15336 rev 11 31/100 10 LRIS64K to vcd frames frames are delimited by an sof and an eof. they are implemented using code violation. unused options are reserved for future use. for the low data rate, the same subcarrier frequency or frequencies is/are used. in this case the number of pulses is multiplied by 4. for the fast commands using one subcarrier, all pulse numbers and times are divided by 2. 10.1 sof when using one subcarrier 10.2 high data rate the sof includes an unmodulated time of 56.64 s, followed by 24 pulses at 423.75 khz (f c /32), and a logic 1 that consists of an unmodulated time of 18.88 s followed by 8 pulses at 423.75 khz as shown in figure 24 . figure 24. start of frame, high data rate, one subcarrier for the fast commands, the sof comprises an unmodulated time of 28.32 s, followed by 12 pulses at 423.75 khz (f c /32), and a logic 1 that consists of an unmodulated time of 9.44 s followed by 4 pulses at 423.75 khz as shown in figure 25 . figure 25. start of frame, high data rate, one subcarrier x2 10.3 low data rate the sof comprises an unmodulated time of 226.56 s, followed by 96 pulses at 423.75 khz ( f c /32), and a logic 1 that consists of an unmodulated time of 75.52 s followed by 32 pulses at 423.75 khz as shown in figure 26 . figure 26. start of frame, low data rate, one subcarrier 113.28 s ai12078 37.76 s 56.64 s ai12079 18.88 s 453.12 s ai12080 151.04 s
LRIS64K to vcd frames LRIS64K 32/100 doc id 15336 rev 11 for the fast commands, the sof comprises an unmodulated time of 113.28 s, followed by 48 pulses at 423.75 khz ( f c /32), and a logic 1 that includes an unmodulated time of 37.76 s followed by 16 pulses at 423.75 khz as shown in figure 27 . figure 27. start of frame, low data rate, one subcarrier x2 10.4 sof when using two subcarriers 10.5 high data rate the sof comprises 27 pulses at 484.28 khz ( f c /28), followed by 24 pulses at 423.75 khz ( f c /32), and a logic 1 that includes 9 pulses at 484.28 khz followed by 8 pulses at 423.75 khz as shown in figure 28 . for the fast commands, the x2 mode is not available. figure 28. start of frame, high data rate, two subcarriers 10.6 low data rate the sof comprises 108 pulses at 484.28 khz ( f c /28), followed by 96 pulses at 423.75 khz ( f c /32), and a logic 1 that includes 36 pulses at 484.28 khz followed by 32 pulses at 423.75 khz as shown in figure 29 . for the fast commands, the x2 mode is not available. figure 29. start of frame, low data rate, two subcarriers 226.56 s ai12081 75.52 s 112.39 s ai12082 37.46 s 449.56 s ai12083 149.84 s
LRIS64K LRIS64K to vcd frames doc id 15336 rev 11 33/100 10.7 eof when using one subcarrier 10.8 high data rate the eof comprises a logic 0 that includes 8 pulses at 423.75 khz and an unmodulated time of 18.88 s, followed by 24 pulses at 423.75 khz ( f c /32), and by an unmodulated time of 56.64 s as shown in figure 30 . figure 30. end of frame, high data rate, one subcarriers for the fast commands, the eof comprises a logic 0 that includes 4 pulses at 423.75 khz and an unmodulated time of 9.44 s, followed by 12 pulses at 423.75 khz ( f c /32) and an unmodulated time of 37.76 s as shown in figure 31 . figure 31. end of frame, high data rate, one subcarriers x2 10.9 low data rate the eof comprises a logic 0 that includes 32 pulses at 423.75 khz and an unmodulated time of 75.52 s, followed by 96 pulses at 423.75 khz ( f c /32) and an unmodulated time of 226.56 s as shown in figure 32 . figure 32. end of frame, low data rate, one subcarriers for the fast commands, the eof comprises a logic 0 that includes 16 pulses at 423.75 khz and an unmodulated time of 37.76 s, followed by 48 pulses at 423.75 khz ( f c /32) and an unmodulated time of 113.28 s as shown in figure 33 . figure 33. end of frame, low data rate, one subcarriers x2 113.28 s ai12084 37.76 s 56.64 s ai12085 18.88 s 453.12 s ai12086 151.04 s 226.56 s ai12087 75.52 s
LRIS64K to vcd frames LRIS64K 34/100 doc id 15336 rev 11 10.10 eof when using two subcarriers 10.11 high data rate the eof comprises a logic 0 that includes 8 pulses at 423.75 khz and 9 pulses at 484.28 khz, followed by 24 pulses at 423.75 khz ( f c /32) and 27 pulses at 484.28 khz ( f c /28) as shown in figure 34 . for the fast commands, the x2 mode is not available. figure 34. end of frame, high data rate, two subcarriers 10.12 low data rate the eof comprises a logic 0 that includes 32 pulses at 423.75 khz and 36 pulses at 484.28 khz, followed by 96 pulses at 423.75 khz ( f c /32) and 108 pulses at 484.28 khz ( f c /28) as shown in figure 35 . for the fast commands, the x2 mode is not available. figure 35. end of frame, low data rate, two subcarriers 112.39 s ai12088 37.46 s 449.56 s ai12089 149.84 s
LRIS64K unique identifier (uid) doc id 15336 rev 11 35/100 11 unique identifier (uid) the LRIS64K is uniquely identified by a 64-bit unique identifier (uid). this uid complies with iso/iec 15963 and iso/iec 7816-6. the uid is a read-only code and comprises: 8 msbs with a value of e0h the ic manufacturer code of st 02h, on 8 bits (iso/iec 7816-6/am1) a unique serial number on 48 bits with the uid each LRIS64K can be addressed uniquely and individually during the anticollision loop and for one-to-one exchange s between a vcd and an LRIS64K. table 12. uid format msb lsb 63 56 55 48 47 0 0xe0 0x02 unique serial number
application family identifier (afi) LRIS64K 36/100 doc id 15336 rev 11 12 application family identifier (afi) the afi (application family identifier) represent s the type of application targeted by the vcd and is used to identify, among all the LRIS64Ks present, only the LRIS64Ks that meet the required application criteria. figure 36. LRIS64K decision tree for afi the afi is programmed by the LRIS64K issuer (or purchaser) in the afi register. once programmed and locked, it can no longer be modified. the most significant nibble of th e afi is used to code one spec ific or all application families. the least significant nibble of the afi is us ed to code one specific or all application subfamilies. subfamily codes diff erent from 0 are proprietary. (see iso/iec 15693-3 documentation) !) )nventoryrequest received .o .oanswer 9e s .o !&)value 9e s .o !&)flag set 9e s !nswergivenbythe,2)3+ tothe)nventoryrequest !&)value )nternal value
LRIS64K data storage format identifier (dsfid) doc id 15336 rev 11 37/100 13 data storage format identifier (dsfid) the data storage format identifier indicates how the data is structured in the LRIS64K memory. the logical organization of data can be known instantly using the dsfid. it can be programmed and locked using the write dsfid and lock dsfid commands. 13.1 crc the crc used in the LRIS64K is calculated as per the definition in iso/iec 13239. the initial register contents are all ones: ?ffff?. the two-byte crc are appended to each request and response, within each frame, before the eof. the crc is calculated on all the bytes after the sof up to the crc field. upon reception of a request from the vcd, the LRIS64K verifies that the crc value is valid. if it is invalid, the LRIS64K discards the frame and does not answer to the vcd. upon reception of a response from the LRIS64K, it is recommended that the vcd verifies whether the crc value is valid. if it is invalid, actions to be performed are left to the discretion of the vcd designer. the crc is transmitted least significant byte firs t. each byte is transm itted least significant bit first. table 13. crc transmission rules lsbyte lsbit msbit msbyte lsbit msbit crc 16 (8 bits) crc 16 (8 bits)
LRIS64K protocol description LRIS64K 38/100 doc id 15336 rev 11 14 LRIS64K protocol description the transmission protocol (or simply protoc ol) defines the mechanism used to exchange instructions and data between the vcd and the LRIS64K, in both directions. it is based on the concept of ?vcd talks first?. this means that an LRIS64K will not start transmitting unless it has received and properly decoded an instruction sent by the vcd. the protocol is based on an exchange of: a request from the vcd to the LRIS64K a response from the LRIS64K to the vcd each request and each response are contained in a frame. the frame delimiters (sof, eof) are described in section 10: LRIS64K to vcd frames . each request consists of: a request sof (see figure 9 and figure 10 ) flags a command code parameters, depending on the command application data a 2-byte crc a request eof (see figure 11 ) each response consists of: an answer sof (see figure 24 to figure 29 ) flags parameters, depending on the command application data a 2-byte crc an answer eof (see figure 30 to figure 35 ) the protocol is bit-oriented. the number of bits transmitted in a frame is a multiple of eight (8), that is an integer number of bytes. a single-byte field is transmitted least signific ant bit (lsbit) first. a multiple-byte field is transmitted least significant byte (lsbyte) first, each byte is transmitted least significant bit (lsbit) first. the setting of the flags indicates the presence of the optional fields. when the flag is set (to one), the field is present. when the flag is reset (to zero), the field is absent. table 14. vcd request frame format request sof request_flags command code parameters data 2-byte crc request eof table 15. LRIS64K response frame format response sof response_flags parameters data 2-byte crc response eof
LRIS64K LRIS64K protocol description doc id 15336 rev 11 39/100 figure 37. LRIS64K protocol timing vcd request frame ( ta b l e 1 4 ) request frame ( ta b l e 1 4 ) LRIS64K response frame ( ta b l e 1 5 ) response frame ( ta b l e 1 5 ) timing <-t 1 -> <-t 2 -> <-t 1 -> <-t 2 ->
LRIS64K states LRIS64K 40/100 doc id 15336 rev 11 15 LRIS64K states an LRIS64K can be in one of 4 states: power-off ready quiet selected transitions between these states are specified in figure 38: LRIS64K state transition diagram and table 16: LRIS64K response depending on request_flags . 15.1 power-off state the LRIS64K is in the power-off state when it does not receive enough energy from the vcd. 15.2 ready state the LRIS64K is in the ready state when it receives enough energy from the vcd. when in the ready state, the LRIS64K answers any request where the select_flag is not set. 15.3 quiet state when in the quiet state, the LRIS64K answers any request except for inventory requests with the address_flag set. 15.4 selected state in the selected state, the LRIS64K answers any request in all modes (see section 16: modes ): request in select mode with the select_flag set request in addressed mode if the uid matches request in non-addressed mode as it is the mode for general requests
LRIS64K LRIS64K states doc id 15336 rev 11 41/100 figure 38. LRIS64K state transition diagram 1. the intention of the state transition method is th at only one LRIS64K should be in the selected state at a time. table 16. LRIS64K response depending on request_flags flags address_flag select_flag 1 addressed 0 non addressed 1 selected 0 non selected LRIS64K in ready or selected state (devices in quiet state do not answer) xx LRIS64K in selected state x x LRIS64K in ready, quiet or selected state (the device which matches the uid) xx error (03h) x x ai06681 power off in field out of field ready quiet selected any other command where select_flag is not set out of field out of field stay quiet(uid) select (uid) any other command any other command where the address_flag is set and where inventory_flag is not set stay quiet(uid) select (uid) reset to ready where select_flag is set or select(different uid) reset to ready
modes LRIS64K 42/100 doc id 15336 rev 11 16 modes the term ?mode? refers to the mechanism used in a request to specify the set of LRIS64Ks that will answer the request. 16.1 addressed mode when the address_flag is set to 1 (addressed mode), the request contains the unique id (uid) of the addressed LRIS64K. any LRIS64K that receives a request with the address_flag set to 1 compares the received unique id to its own. if it matches, then the LRIS64K executes the request (if possible) and returns a response to the vcd as specified in the command description. if the uid does not match, then it remains silent. 16.2 non-addressed mode (general request) when the address_flag is cleared to 0 (non-a ddressed mode), the request does not contain a unique id. any LRIS64K receiving a request with the address_flag cleared to 0 executes it and returns a response to the vcd as specified in the command description. 16.3 select mode when the select_flag is set to 1 (select mode ), the request does not contain an LRIS64K unique id. the LRIS64K in the selected state that receives a request with the select_flag set to 1 executes it and returns a response to the vcd as specified in the command description. only LRIS64Ks in the selected state answer a request where the select_flag set to 1. the system design ensures in theory that only one LRIS64K can be in the select state at a time.
LRIS64K request format doc id 15336 rev 11 43/100 17 request format the request consists of: an sof flags a command code parameters and data a crc an eof 17.1 request flags in a request, the ?flags? field specifies the actions to be performed by the LRIS64K and whether corresponding fields are present or not. the flags field consists of eight bits. the bit 3 (inventory_flag) of the request flag defines the contents of the 4 msbs (bits 5 to 8). when bit 3 is reset (0), bits 5 to 8 define the LRIS64K selection criteria. when bit 3 is set (1), bits 5 to 8 define the LRIS64K inventory parameters. table 17. general request format s o f request_flags command code parameters data crc e o f table 18. definition of request flags 1 to 4 bit no flag level description bit 1 subcarrier_flag (1) 1. subcarrier_flag refers to the LRIS64K-to-vcd communication. 0 a single subcarrier frequency is used by the LRIS64K 1 two subcarrier are used by the LRIS64K bit 2 data_rate_flag (2) 2. data_rate_flag refers to the LRIS64K-to-vcd communication 0 low data rate is used 1 high data rate is used bit 3 inventory_flag 0 the meaning of flags 5 to 8 is described in ta bl e 1 9 1 the meaning of flags 5 to 8 is described in ta bl e 2 0 bit 4 protocol_extension_flag 0 no protocol format extension 1 protocol format extension
request format LRIS64K 44/100 doc id 15336 rev 11 . table 19. request flags 5 to 8 when bit 3 = 0 bit no flag level description bit 5 select flag (1) 1. if the select_flag is set to 1, the address_flag is set to 0 and the uid field is not present in the request. 0 request is executed by any LRIS64K according to the setting of address_flag 1 request is executed only by the LRIS64K in selected state bit 6 address flag (1) 0 request is not addressed. uid field is not present. the request is executed by all LRIS64Ks. 1 request is addressed. uid field is present. the request is executed only by the LRIS64K whose uid matches the uid specified in the request. bit 7 option flag 0 option not activated. 1 option activated. bit 8 rfu 0 table 20. request flags 5 to 8 when bit 3 = 1 bit no flag level description bit 5 afi flag 0 afi field is not present 1 afi field is present bit 6 nb_slots flag 0 16 slots 11 slot bit 7 option flag 0 bit 8 rfu 0
LRIS64K response format doc id 15336 rev 11 45/100 18 response format the response consists of: an sof flags parameters and data a crc an eof 18.1 response flags in a response, the flags indicate how actions have been performed by the LRIS64K and whether corresponding fields are present or not. the response flags consist of eight bits. table 21. general response format s o f response_flags parameters data crc e o f table 22. definitions of response flags 1 to 8 bit no flag level description bit 1 error_flag 0 no error 1 error detected. e rror code is in the "error" field. bit 2 rfu 0 bit 3 rfu 0 bit 4 extension flag 0 no extension bit 5 rfu 0 bit 6 rfu 0 bit 7 rfu 0 bit 8 rfu 0
response format LRIS64K 46/100 doc id 15336 rev 11 18.2 response error code if the error_flag is set by the LRIS64K in the response, the error code field is present and provides information about the error that occurred. error codes not specified in ta bl e 2 3 are reserved for future use. table 23. response error code definition error code meaning 02h the command is not recognized, for example a format error occurred 03h the option is not supported 0fh error with no information given 10h the specified block is not available 11h the specified block is already locked and thus cannot be locked again 12h the specified block is locked an d its contents cannot be changed. 13h the specified block was not successfully programmed 14h the specified block was not successfully locked 15h the specified block is read-protected
LRIS64K anticollision doc id 15336 rev 11 47/100 19 anticollision the purpose of the anticollision sequence is to inventor y the LRIS64Ks present in the vcd field using their unique id (uid). the vcd is the master of communications with one or several LRIS64Ks. it initiates LRIS64K communication by issuing the inventory request. the LRIS64K sends its response in the determined slot or does not respond. 19.1 request parameters when issuing the inventory command, the vcd: sets the nb_slots_flag as desired adds the mask length and the mask value after the command field the mask length is the number of significant bits of the mask value. the mask value is contained in an integer number of bytes. the mask length indicates the number of significant bits. lsb is transmitted first if the mask length is not a mu ltiple of 8 (bits), as many 0-bits as required will be added to the mask value msb so that the mask value is contained in an integer number of bytes the next field starts at the next byte boundary. in the example of the ta bl e 2 5 and figure 39 , the mask length is 11 bits. five 0-bits are added to the mask value msb. the 11-bit mask and the current slot number are compared to the uid. table 24. inventory request format msb sof request _flags command optional afi (1) 1. gray means that t he field is optional. mask length mask value crc lsb eof 8 bits 8 bits 8 bits 8 bits 0 to 8 bytes 16 bits table 25. example of the addition of 0-bits to an 11-bit mask value (b 15 ) msb lsb (b 0 ) 0000 0 100 1100 1111 0-bits added 11-bit mask value
anticollision LRIS64K 48/100 doc id 15336 rev 11 figure 39. principle of comparison between the mask, the slot number and the uid the afi field is present if the afi_flag is set. the pulse is generated according to the definition of the eof in iso/iec 15693-2. the first slot starts immediately after the reception of the request eof. to switch to the next slot, the vcd sends an eof. the following rules and restrictions apply: if no LRIS64K answer is detected, the vcd may switch to the next slot by sending an eof, if one or more LRIS64K answers are detected, the vcd waits until the complete frame has been received before sending an eof for switching to the next slot. ai06682 mask value received in the inventory command 0000 0100 1100 1111 b 16 bits the mask value less the padding 0s is loaded into the tag comparator 100 1100 1111 b 11 bits the slot counter is calculated xxxx nb_slots_flags = 0 (16 slots), slot counter is 4 bits the slot counter is concatened to the mask value xxxx 100 1100 1111 b nb_slots_flags = 0 15 bits the concatenated result is compared with the least significant bits of the tag uid. xxxx xxxx ..... xxxx xxxx x xxx xxxx xxxx xxxx 64 bits lsb msb b lsb msb lsb msb lsb msb b0 b63 compare bits ignored uid 4 bits
LRIS64K request processing by the LRIS64K doc id 15336 rev 11 49/100 20 request processing by the LRIS64K upon reception of a valid request, the LRIS64K performs the following algorithm: nbs is the total number of slots (1 or 16) sn is the current slot number (0 to 15) lsb (value, n) function returns the n less significant bits of value msb (value, n) function returns the n most significant bits of value ?&? is the concatenation operator slot_frame is either an sof or an eof sn = 0 if (nb_slots_flag) then nbs = 1 sn_length = 0 endif else nbs = 16 sn_length = 4 endif label1: if lsb(uid, sn_length + mask_length) = lsb(sn,sn_length)&lsb(mask,mask_length) then answer to inventory request endif wait (slot_frame) if slot_frame = sof then stop anticollision decode/process request exit endif if slot_frame = eof if sn < nbs-1 then sn = sn + 1 goto label1 exit endif endif
explanation of the possible cases LRIS64K 50/100 doc id 15336 rev 11 21 explanation of the possible cases figure 40 summarizes the main poss ible cases that can occu r during an anticollision sequence when the slot number is 16. the different steps are: the vcd sends an inventory request, in a frame terminated by an eof. the number of slots is 16. LRIS64K_1 transmits its response in slot 0. it is the only one to do so, therefore no collision occurs and its uid is rece ived and registered by the vcd; the vcd sends an eof in order to switch to the next slot. in slot 1, two LRIS64Ks, LRIS64K_2 and LRIS64K_3 transmit a response, thus generating a collision. the vc d records the event and reme mbers that a collision was detected in slot 1. the vcd sends an eof in order to switch to the next slot. in slot 2, no LRIS64K transmits a response. therefore the vcd does not detect any LRIS64K sof and decides to switch to the next slot by sending an eof. in slot 3, there is anot her collision caused by resp onses from LRIS64K_4 and LRIS64K_5 the vcd then decides to send a request (for instance a read block) to LRIS64K_1 whose uid has already been correctly received. all LRIS64Ks detect an sof and exit the anticollision se quence. they process this request and since the request is address ed to LRIS64K_1, only LRIS64K_1 transmits a response. all LRIS64Ks are ready to receive another request. if it is an inventory command, the slot numbering sequence restarts from 0. note: the decision to interrupt the anticollision sequenc e is made by the vcd. it could have continued to send eofs until slot 16 and only then sent the request to LRIS64K_1.
LRIS64K explanation of the possible cases doc id 15336 rev 11 51/100 figure 40. description of a possible anticollision sequence !) 3lot 3lot 3lot 3lot 6#$ 3/& )nventory 2equest %/& %/& %/& %/& 3/& 2equestto ,2)3+? %/& 2esponse 2esponse ,2)3+s 2esponse from ,2)3+? 2esponse 2esponse 2esponse 4iming t t t t t t t t #omment .o collision #ollision .o 2esponse #ollision 4ime
inventory initiated command LRIS64K 52/100 doc id 15336 rev 11 22 inventory initiated command the LRIS64K provides a special feature to improve the inventory time response of moving tags using the initiate_flag valu e. this flag, controlled by the initiate command, allows tags to answer to inventory initiated commands. for applications in which multiple tags are moving in front of a reader, it is possible to miss tags using the standard inventory command. the reason is that the inventory sequence has to be performed on a global tree search. for example, a tag with a particular uid value may have to wait the run of a long tree search before being inventoried. if the delay is too long, the tag may be out of the field before it has been detected. using the initiate command, the inventory sequence is optimized. when multiple tags are moving in front of a re ader, the ones which are within th e reader field will be initiated by the initiate command. in th is case, a small batch of tags will answer to the inventory initiated command which will optimize the time necessary to identify all the ta gs. when finished, the reader has to issue a new initia te command in order to initia te a new small batch of tags which are new inside the reader field. it is also possible to reduce the inventory sequence time using the fast initiate and fast inventory initiated commands. these commands allow the LRIS64Ks to increase their response data rate by a factor of 2, up to 53 kbit/s.
LRIS64K timing definition doc id 15336 rev 11 53/100 23 timing definition 23.1 t 1 : LRIS64K response delay upon detection of the rising edge of the eof received from the vcd, the LRIS64K waits for a time t 1nom before transmitting its response to a vcd request or before switching to the next slot during an inventory process. values of t 1 are given in ta b l e 2 6 . the eof is defined in figure 11 on page 26 . 23.2 t 2 : vcd new request delay t 2 is the time after which the vcd may send an eof to switch to the next slot when one or more LRIS64K responses have been received during an inventory command. it starts from the reception of the eof from the LRIS64Ks. the eof sent by the vcd may be either 10% or 100% modulated regardless of the modulation index used for transmitting the vcd request to the LRIS64K. t 2 is also the time after which the vcd may send a new request to the LRIS64K as described in table 37: LRIS64K protocol timing . values of t 2 are given in ta b l e 2 6 . 23.3 t 3 : vcd new request delay in th e absence of a response from the LRIS64K t 3 is the time after which the vcd may send an eof to switch to the next slot when no LRIS64K response has been received. the eof sent by the vcd may be either 10% or 100% modulated regardless of the modulation index used for transmitting the vcd request to the LRIS64K. from the time the vcd has generated the rising edge of an eof: if this eof is 100% modulated, the vcd waits a time at least equal to t 3min before sending a new eof. if this eof is 10% modulated, the vcd waits a time at least equal to the sum of t 3min + the LRIS64K nominal response time (which depends on the LRIS64K data rate and subcarrier modulation mode) before sending a new eof. table 26. timing values (1) 1. the tolerance of specific timings is 32/f c . minimum (min) values nominal (n om) values maximum (max) values t 1 318.6 s 320.9 s 323.3 s t 2 309.2 sno t nom no t max t 3 t 1max (2) + t sof (3) 2. t 1max does not apply for write alike requests. timing condi tions for write alike requests are defined in the command description. 3. t sof is the time taken by the LRIS64K to transmit an sof to the vcd. t sof depends on the current data rate: high data rate or low data rate. no t nom no t max
commands codes LRIS64K 54/100 doc id 15336 rev 11 24 commands codes the LRIS64K supports the commands described in this section. their codes are given in ta bl e 2 7 . table 27. command codes command code standard function command code custom function 01h inventory 2ch get multiple block security status 02h stay quiet b1h write-sector password 20h read single block b2h lock-sector password 21h write single block b3h present-sector password 23h read multiple block c0h fast read single block 25h select c1h fast inventory initiated 26h reset to ready c2h fast initiate 27h write afi c3h fast read multiple block 28h lock afi d1h inventory initiated 29h write dsfid d2h initiate 2ah lock dsfid 2bh get system info
LRIS64K commands codes doc id 15336 rev 11 55/100 24.1 inventory when receiving the inventory request, the LRIS64K runs th e anticollision sequence. the inventory_flag is set to 1. the meaning of flags 5 to 8 is shown in table 20: request flags 5 to 8 when bit 3 = 1 . the request contains: the flags, the inventory command code (see table 27: command codes ) the afi if the afi flag is set the mask length the mask value the crc the LRIS64K does not generate any answer in case of error. the response contains: the flags the unique id during an inventory process, if the vcd does not receive an rf LRIS64K response, it waits a time t 3 before sending an eof to switch to the next slot. t 3 starts from the rising edge of the request eof sent by the vcd. if the vcd sends a 100% modulated eof, the minimum value of t 3 is: t 3 min = 4384/f c (323.3 s) + t sof if the vcd sends a 10% modulated eof, the minimum value of t 3 is: t 3 min = 4384/f c (323.3 s) + t nrt where: t sof is the time required by the LRIS64K to transmit an sof to the vcd t nrt is the nominal response time of the LRIS64K t nrt and t sof are dependent on the LRIS64K-to-vcd data rate and subcarrier modulation mode. table 28. inventory request format request sof request_flags inventory optional afi (1) 1. gray means that t he field is optional. mask length mask value crc16 request eof 8 bits 01h 8 bits 8 bits 0 - 64 bits 16 bits table 29. inventory response format response sof response_ flags dsfid uid crc16 response eof 8 bits 8 bits 64 bits 16 bits
commands codes LRIS64K 56/100 doc id 15336 rev 11 24.2 stay quiet command code = 0x02 on receiving the stay quiet command, the LRIS64K enters the quiet state if no error occurs, and does not send back a response. there is no response to the stay quiet command even if an error occurs. when in the quiet state: the LRIS64K does not process any request if the inventory_flag is set, the LRIS64K processes any addressed request the LRIS64K exits the quiet state when: it is reset (power off), receiving a select request. it then goes to the selected state, receiving a reset to ready request. it then goes to the ready state. the stay quiet command must always be executed in addressed mode (select_flag is reset to 0 and address_flag is set to 1). table 30. stay quiet request format request sof request flags stay quiet uid crc16 request eof 8 bits 02h 64 bits 16 bits figure 41. stay quiet frame exchange between vcd and LRIS64K vcd sof stay quiet request eof LRIS64K timing
LRIS64K commands codes doc id 15336 rev 11 57/100 24.3 read single block on receiving the read single block command, the LRIS64K reads the requested block and sends back its 32-bit value in the response. the protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. if the protocol_extention_flag is at 0, the LRIS64K answers with an error code. the option_flag is supported. request parameters: option_flag uid (optional) block number response parameters: sector security status if option_flag is set (see table 33: sector security status ) 4 bytes of block data table 31. read single block request format request sof request_ flags read single block uid (1) 1. gray means that t he field is optional. block number crc16 request eof 8 bits 20h 64 bits 16 bits 16 bits table 32. read single block response format when error_flag is not set response sof response_ flags sector security status (1) 1. gray means that t he field is optional. data crc16 response eof 8 bits 8 bits 32 bits 16 bits table 33. sector security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use. all at 0 password control bits read / write protection bits 0: current sector not locked 1: current sector locked table 34. read single block response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 58/100 doc id 15336 rev 11 response parameter: error code as error_flag is set ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 15h: the specified block is read-protected figure 42. read single block frame exchange between vcd and LRIS64K vcd sof read single block request eof LRIS64K <-t 1 -> sof read single block response eof
LRIS64K commands codes doc id 15336 rev 11 59/100 24.4 write single block on receiving the write single block command, the LRIS64K writes the data contained in the request to the requested block and reports whether the write operation was successful in the response. the protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. if the protocol_extention_flag is at 0, the LRIS64K answers with an error code. the option_flag is supported. during write cycle w t , there should be no modulation (neither 100% nor 10%). otherwise, the LRIS64K may not program correctly the data into the memory. the w t time is equal to t 1nom + 18 302 s. request parameters: uid (optional) block number data response parameter: no parameter. the response is send back after the writing cycle. response parameter: error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 12h: the specified block is locked and its contents cannot be changed. ? 13h: the specified block was not successfully programmed table 35. write single block request format request sof request_ flags write single block uid (1) 1. gray means that t he field is optional. block number data crc16 request eof 8 bits 21h 64 bits 16 bits 32 bits 16 bits table 36. write single block response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 37. write single block response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 60/100 doc id 15336 rev 11 figure 43. write single block frame exchange between vcd and LRIS64K vcd sof write single block request eof LRIS64K <-t 1 -> sof write single block response eof write sequence when error LRIS64K <----------------- w t -----------------> sof write single block response eof
LRIS64K commands codes doc id 15336 rev 11 61/100 24.5 read multiple block when receiving the read multiple block command, the LRIS64K reads the selected blocks and sends back their value in multiples of 32 bits in the response. the blocks are numbered from '00h to '7ffh' in the request and the value is minus one (?1) in the field. for example, if the ?number of blocks? field contains the value 06h, 7 blocks are read. the maximum number of blocks is fixed at 32 assuming that they are all located in the same sector. if the number of blocks overlaps sectors, the LRIS64K returns an error code. the protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. if the protocol_extention_flag is at 0, the LRIS64K answers with an error code. the option_flag is supported. request parameters: option_flag uid (optional) first block number number of blocks response parameters: sector security status if option_flag is set (see table 40: sector security status ) n blocks of data table 38. read multiple block request format request sof request_ flags read multiple block uid (1) 1. gray means that t he field is optional. first block number number of blocks crc16 request eof 8 bits 23h 64 bits 16 bits 8 bits 16 bits table 39. read multiple block response format when error_flag is not set response sof response_ flags sector security status (1) 1. gray means that t he field is optional. data crc16 response eof 8 bits 8 bits (2) 2. repeated as needed. 32 bits (2) 16 bits table 40. sector security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use. all at 0 password control bits read / write protection bits 0: current sector not locked 1: current sector locked
commands codes LRIS64K 62/100 doc id 15336 rev 11 response parameter: error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 15h: the specified block is read-protected table 41. read multiple block response format when error_flag is set response sof response_flags error code crc16 response eof 8 bits 8 bits 16 bits figure 44. read multiple block frame exchange between vcd and LRIS64K vcd sof read multiple block request eof LRIS64K <-t 1 -> sof read multiple block response eof
LRIS64K commands codes doc id 15336 rev 11 63/100 24.6 select when receiving the select command: if the uid is equal to its own uid, the LRIS64K enters or stays in the selected state and sends a response. if the uid does not match its own, the selected LRIS64K returns to the ready state and does not send a response. the LRIS64K answers an error code only if the uid is equal to its own uid. if not, no response is generated. if an error occurs, the LRIS64K remains in its current state. request parameter: uid response parameter: no parameter. response parameter: error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given table 42. select request format request sof request_ flags select uid crc16 request eof 8 bits 25h 64 bits 16 bits table 43. select block response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 44. select response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits figure 45. select frame exchange between vcd and LRIS64K vcd sof select request eof LRIS64K <-t 1 -> sof select response eof
commands codes LRIS64K 64/100 doc id 15336 rev 11 24.7 reset to ready on receiving a reset to ready command, the LRIS64K returns to the ready state if no error occurs. in the addressed mode, the LRIS64K answers an error code only if the uid is equal to its own uid. if not, no response is generated. request parameter: uid (optional) response parameter: no parameter response parameter: error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given table 45. reset to ready request format request sof request_ flags reset to ready uid (1) 1. gray means that t he field is optional. crc16 request eof 8 bits 26h 64 bits 16 bits table 46. reset to ready response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 47. reset to ready response format when error_flag is set response sof response_flags error code crc16 response eof 8 bits 8 bits 16 bits figure 46. reset to ready frame exchange between vcd and LRIS64K vcd sof reset to ready request eof LRIS64K <-t 1 -> sof reset to ready response eof
LRIS64K commands codes doc id 15336 rev 11 65/100 24.8 write afi on receiving the write afi request, the LRIS64K programs the 8-bit afi value to its memory. the option_flag is supported. during write cycle w t , there should be no modulation (neither 100% nor 10%). otherwise, the LRIS64K may not write correctly the afi value into the memory. the w t time is equal to t 1nom + 18 302 s. request parameter: uid (optional) afi response parameter: no parameter. response parameter: error code as error_flag is set ? 03h: the option is not supported ? 0fh: error with no information given ? 12h: the specified block is locked and its contents cannot be changed. ? 13h: the specified block was not successfully programmed table 48. write afi request format request sof request _flags write afi uid (1) 1. gray means that t he field is optional. afi crc16 request eof 8 bits 27h 64 bits 8 bits 16 bits table 49. write afi response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 50. write afi response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 66/100 doc id 15336 rev 11 figure 47. write afi frame exchange between vcd and LRIS64K vcd sof write afi request eof LRIS64K <-t 1 -> sof write afi response eof write sequence when error LRIS64K <---------------- w t ----------------> sof write afi response eof
LRIS64K commands codes doc id 15336 rev 11 67/100 24.9 lock afi on receiving the lock afi request, the LRIS64K locks the afi value permanently. the option_flag is supported. during write cycle w t , there should be no modulation (neither 100% nor 10%). otherwise, the LRIS64K may not lock correctly the afi value in memory. the w t time is equal to t 1nom + 18 302 s. request parameter: uid (optional) response parameter: no parameter response parameter: error code as error_flag is set ? 03h: the option is not supported ? 0fh: error with no information given ? 11h: the specified block is already locked and thus cannot be locked again ? 14h: the specified block was not successfully locked table 51. lock afi request format request sof request_ flags lock afi uid (1) 1. gray means that t he field is optional. crc16 request eof 8 bits 28h 64 bits 16 bits table 52. lock afi response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 53. lock afi response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 68/100 doc id 15336 rev 11 figure 48. lock afi frame exchange between vcd and LRIS64K vcd sof lock afi request eof LRIS64K <-t 1 -> sof lock afi response eof lock sequence when error LRIS64K <--------------- w t ---------------> sof lock afi response eof
LRIS64K commands codes doc id 15336 rev 11 69/100 24.10 write dsfid on receiving the write dsfid request, the LRIS64K programs the 8-bit dsfid value to its memory. the option_flag is supported. during write cycle w t , there should be no modulation (neither 100% nor 10%). otherwise, the LRIS64K may not write correctly the dsfid value in memory. the w t time is equal to t 1nom + 18 302 s. request parameter: uid (optional) dsfid response parameter: no parameter response parameter: error code as error_flag is set ? 03h: the option is not supported ? 0fh: error with no information given ? 12h: the specified block is locked and its contents cannot be changed. ? 13h: the specified block was not successfully programmed table 54. write dsfid request format request sof request_ flags write dsfid uid (1) 1. gray means that t he field is optional. dsfid crc16 request eof 8 bits 29h 64 bits 8 bits 16 bits table 55. write dsfid response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 56. write dsfid response format when error_flag is set response sof response_flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 70/100 doc id 15336 rev 11 figure 49. write dsfid frame exchange between vcd and LRIS64K vcd sof write dsfid request eof LRIS64K <-t 1 -> sof write dsfid response eof write sequence when error LRIS64K <--------------- w t ---------------> sof write dsfid response eof
LRIS64K commands codes doc id 15336 rev 11 71/100 24.11 lock dsfid on receiving the lock dsfid request, the LRIS64K locks the dsfid value permanently. the option_flag is supported. during write cycle w t , there should be no modulation (neither 100% nor 10%). otherwise, the LRIS64K may not lock correctly the dsfid value in memory. the w t time is equal to t 1nom + 18 302 s. request parameter: uid (optional) response parameter: no parameter. response parameter: error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given ? 11h: the specified block is already locked and thus cannot be locked again ? 14h: the specified block was not successfully locked table 57. lock dsfid request format request sof request_ flags lock dsfid uid (1) 1. gray means that t he field is optional. crc16 request eof 8 bits 2ah 64 bits 16 bits table 58. lock dsfid response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 59. lock dsfid response format when error_flag is set response sof response_flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 72/100 doc id 15336 rev 11 figure 50. lock dsfid frame exchange between vcd and LRIS64K vcd sof lock dsfid request eof LRIS64K <-t 1 -> sof lock dsfid response eof lock sequence when error LRIS64K <--------------- w t ---------------> sof lock dsfid response eof
LRIS64K commands codes doc id 15336 rev 11 73/100 24.12 get system info when receiving the get system info command, the LRIS64K sends back its information data in the response.the option_flag is supported and must be reset to 0. the get system info can be issued in both addressed and non addressed modes. the protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. if the protocol_extention_flag is at 0, the LRIS64K answers with an error code. request parameter: uid (optional) response parameters: information flags set to 0fh. dsfid, afi, memory size and ic reference fields are present uid code on 64 bits dsfid value afi value memory size. the LRIS64K provides 2048 blocks (07ffh) of 4 byte (03h) ic reference. only the 6 msb are significant. response parameter: error code as error_flag is set: ? 03h: option not supported ? 0fh: other error table 60. get system info request format request sof request _flags get system info uid (1) 1. gray means that t he field is optional. crc16 request eof 8 bits 2bh 64 bits 16 bits table 61. get system info response format when error_flag is not set response sof response _flags information flags uid dsfid afi memory size ic reference crc16 response eof 00h 0fh 64 bits 8 bits 8 bits 0307ffh 44h 16 bits table 62. get system info response format when error_flag is set response sof response_flags error code crc16 response eof 01h 8 bits 16 bits
commands codes LRIS64K 74/100 doc id 15336 rev 11 figure 51. get system info frame exchange between vcd and LRIS64K vcd sof get system info request eof LRIS64K <-t 1 -> sof get system info response eof
LRIS64K commands codes doc id 15336 rev 11 75/100 24.13 get multiple bl ock security status when receiving the get multiple block security status command, the LRIS64K sends back the sector security status. the blocks are numbered from '00h to '07ffh' in the request and the value is minus one (?1) in the field. for example, a value of '06' in the ?number of blocks? field requests to return the security status of 7 blocks. the protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. if the protocol_extention_flag is at 0, the LRIS64K answers with an error code. during the LRIS64K response, if the internal block address counter reaches 07ffh, it rolls over to 0000h and the sector security status bytes for that location are sent back to the reader. request parameter: uid (optional) first block number number of blocks response parameters: sector security status (see table 65: sector security status ) table 63. get multiple block security status request format request sof request _flags get multiple block security status uid (1) 1. gray means that t he field is optional. first block number number of blocks crc16 request eof 8 bits 2ch 64 bits 16 bits 16 bits 16 bits table 64. get multiple block security status response format when error_flag is not set response sof response_ flags sector security status crc16 response eof 8 bits 8 bits (1) 1. repeated as needed. 16 bits table 65. sector security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use. all at 0 password control bits read / write protection bits 0: current sector not locked 1: current sector locked
commands codes LRIS64K 76/100 doc id 15336 rev 11 response parameter: error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available table 66. get multiple block security status response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits figure 52. get multiple block security status frame exchange between vcd and LRIS64K vcd sof get multiple block security status eof LRIS64K <-t 1 -> sof get multiple block security status eof
LRIS64K commands codes doc id 15336 rev 11 77/100 24.14 write-sector password on receiving the write-sector password command, the LRIS64K uses the data contained in the request to write the password and reports whether the operation was successful in the response. the option_flag is supported. during write cycle time w t , there must be no modulation at all (neither 100% nor 10%). otherwise, the LRIS64K may not correctly program the data into the memory. the w t time is equal to t 1nom + 18 302 s. after a successful write, the new value of the selected password is automatically activated. it is not required to present the new password value until LRIS64K power-down. request parameter: uid (optional) password number (01h = pswd1, 02h = pswd2, 03h = pswd3, other = error) data response parameter: 32-bit password value. the response is sent back after the write cycle. response parameter: error code as error_flag is set: ? 02h: the command is not recognized, for example: a format error occurred ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 12h: the specified block is locked and its contents cannot be changed. ? 13h: the specified block was not successfully programmed table 67. write-sector pa ssword request format request sof request _flags write- sector password ic mfg code uid (1) 1. gray means that t he field is optional. password number data crc16 request eof 8 bits b1h 02h 64 bits 8 bits 32 bits 16 bits table 68. write-sector password response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 69. write-sector password response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 78/100 doc id 15336 rev 11 figure 53. write-sector password frame exchange between vcd and LRIS64K vcd sof write- sector password request eof LRIS64K <-t 1 -> sof write-sector password response eof write sequence when error LRIS64K <--------------- w t ---------------> sof write- sector password response eof
LRIS64K commands codes doc id 15336 rev 11 79/100 24.15 lock-sector password on receiving the lock-sector password command, the LRIS64K sets the access rights and permanently locks the selected sector. the option_flag is supported. a sector is selected by giving the address of one of its blocks in the lock-sector password request (sector number field). for example, addresses 0 to 31 are used to select sector 0 and addresses 32 to 63 are used to select sector 1. care must be taken when issuing the lock-sector password command as all the blocks belonging to the same sector are automatically locked by a single command. the protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. if the protocol_extention_flag is at 0, the LRIS64K answers with an error code. during write cycle w t , there should be no modulation (neither 100% nor 10%) otherwise, the LRIS64K may not correctly lock the memory block. the w t time is equal to t 1nom + 18 302 s. request parameters: (optional) uid sector number sector security status (refer to ta bl e 7 1 ) response parameter: no parameter. table 70. lock-sector password request format request sof request _flags lock- sector password ic mfg code uid (1) 1. gray means that t he field is optional. sector number sector security status crc16 request eof 8 bits b2h 02h 64 bits 16 bits 8 bits 16 bits table 71. sector security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 0 0 0 password control bits read / write protection bits 1 table 72. lock-sector password response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 73. lock-sector password response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 80/100 doc id 15336 rev 11 response parameter: error code as error_flag is set: ? 02h: the command is not recognized, for example: a format error occurred ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 11h: the specified block is already locked and thus cannot be locked again ? 14h: the specified block was not successfully locked figure 54. lock-sector password frame exchange between vcd and LRIS64K vcd sof lock-sector password request eof LRIS64K <-t 1 -> sof lock-sector password response eof lock sequence when error LRIS64K <--------------- w t ---------------> sof lock-sector password response eof
LRIS64K commands codes doc id 15336 rev 11 81/100 24.16 present-sector password on receiving the present-sector password command, the LRIS64K compares the requested password with the data contained in the request and reports whether the operation has been successful in the response. the option_flag is supported. during the w t comparison cycle time, there should be no modulation (neither 100% nor 10%) otherwise, the LRIS64K password value may not be correctly compared. the w t time is equal to t 1nom + 18 302 s. after a successful command, the access to all the memory blocks linked to the password is changed as described in section 3.1: LRIS64K rf block security . request parameter: uid (optional) password number (0x01 = pswd1, 0x02 = pswd2, 0x03 = pswd3, other = error) data response parameter: no parameter. the response is send back after the writing cycle response parameter: error code as error_flag is set: ? 02h: the command is not recognized, for example: a format error occurred ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available table 74. present-sector password request format request sof request _flags present- sector password ic mfg code uid (1) 1. gray means that t he field is optional. password number data crc16 request eof 8 bits b3h 02h 64 bits 8 bits 32 bits 16 bits table 75. present-sector password response format when error_flag is not set response sof response_flags crc16 response eof 8 bits 16 bits table 76. present-sector password response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 82/100 doc id 15336 rev 11 figure 55. present-sector password frame exchange between vcd and LRIS64K vcd sof present- sector password request eof LRIS64K <-t 1 -> sof present- sector password response eof sequence when error LRIS64K <-------------- w t --------------> sof present- sector password response eof
LRIS64K commands codes doc id 15336 rev 11 83/100 24.17 fast read single block on receiving the fast read single block command, the LRIS64K reads the requested block and sends back its 32-bit value in the response. the option_flag is supported. the data rate of the response is multiplied by 2. the protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. if the protocol_extention_flag is at 0, the LRIS64K answers with an error code. request parameters: option_flag uid (optional) block number response parameters: sector security status if option_flag is set (see ta b l e 7 9 ) 4 bytes of block data table 77. fast read single block request format request sof request_ flags fast read single block ic mfg code uid (1) 1. gray means that t he field is optional. block number crc16 request eof 8 bits c0h 02h 64 bits 16 bits 16 bits table 78. fast read single block response format when error_flag is not set response sof response _flags sector security status (1) 1. gray means that t he field is optional. data crc16 response eof 8 bits 8 bits 32 bits 16 bits table 79. sector security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future used. all at 0 password control bits read / write protection bits 0: current sector not locked 1: current sector locked table 80. fast read single block response format when error_flag is set response sof response_ flags error code crc16 response eof 8 bits 8 bits 16 bits
commands codes LRIS64K 84/100 doc id 15336 rev 11 response parameter: error code as error_flag is set: ? 02h: the command is not recognized, for example: a format error occurred ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 15h: the specified block is read protected figure 56. fast read single block frame exchange between vcd and LRIS64K vcd sof fast read single block request eof LRIS64K <-t 1 -> sof fast read single block response eof
LRIS64K commands codes doc id 15336 rev 11 85/100 24.18 fast inventory initiated before receiving the fast inventory initiated command, the LRIS64K must have received an initiate or a fast initiate command in order to set the initiate_ flag. if not, the LRIS64K does not answer to the fast inventory initiated command. on receiving the fast inventory initiated request, the LRIS64K runs the anticollision sequence. the inventory_flag must be set to 1. the meaning of flags 5 to 8 is shown in table 20: request flags 5 to 8 when bit 3 = 1 . the data rate of the re sponse is multiplied by 2. the request contains: the flags, the inventory command code the afi if the afi flag is set the mask length the mask value the crc the LRIS64K does not generate any answer in case of error. the response contains: the flags the unique id during an inventory process, if the vcd does not receive an rf LRIS64K response, it waits a time t 3 before sending an eof to switch to the next slot. t 3 starts from the rising edge of the request eof sent by the vcd. if the vcd sends a 100% modulated eof, the minimum value of t 3 is: t 3 min = 4384/f c (323.3 s) + t sof if the vcd sends a 10% modulated eof, the minimum value of t 3 is: t 3 min = 4384/f c (323.3 s) + t nrt where: t sof is the time required by the LRIS64K to transmit an sof to the vcd t nrt is the nominal response time of the LRIS64K table 81. fast inventory initiated request format request sof request _flags fast inventory initiated ic mfg code optional afi (1) 1. gray means that t he field is optional. mask length mask value crc16 request eof 8 bits c1h 02h 8 bits 8 bits 0 - 64 bits 16 bits table 82. fast inventory initiated response format response sof response _flags dsfid uid crc16 response eof 8 bits 8 bits 64 bits 16 bits
commands codes LRIS64K 86/100 doc id 15336 rev 11 t nrt and t sof are dependent on the LRIS64K-to-vcd data rate and subcarrier modulation mode. 24.19 fast initiate on receiving the fast initiate command, the LRIS64K will set the internal initiate_flag and send back a response only if it is in the ready state. the command has to be issued in the non addressed mode only (select_flag is reset to 0 and address_flag is reset to 0). if an error occurs, the LRIS64K does not generate any answer. the initiate_flag is reset after a power off of the LRIS64K. the data rate of the response is multiplied by 2. the request contains: no data the response contains: the flags the unique id table 83. fast initiate request format request sof request_flags fast initiate ic mfg code crc16 request eof 8 bits c2h 02h 16 bits table 84. fast initiate response format response sof response _flags dsfid uid crc16 response eof 8 bits 8 bits 64 bits 16 bits figure 57. fast initiate frame exchange between vcd and LRIS64K vcd sof fast initiate request eof LRIS64K <-t 1 -> sof fast initiate response eof
LRIS64K commands codes doc id 15336 rev 11 87/100 24.20 fast read multiple block on receiving the fast read multiple block command, the LRIS64K reads the selected blocks and sends back their value in multiples of 32 bits in the response. the blocks are numbered from '00h to '7ffh' in the request and the value is minus one (?1) in the field. for example, if the ?number of blocks? field contains the value 06h, 7 blocks are read. the maximum number of blocks is fixed to 32 assuming that they are all located in the same sector. if the number of blocks overlaps sectors, the LRIS64K returns an error code. the protocol_extention_flag should be set to 1 for the LRIS64K to operate correctly. if the protocol_extention_flag is at 0, the LRIS64K answers with an error code. the option_flag is supported. the data rate of the response is multiplied by 2. request parameters: option_flag uid (optional) first block number number of blocks response parameters: sector security status if option_flag is set (see table 87: sector security status if option_flag is set ) n block of data table 85. fast read multiple block request format request sof request_ flags fast read multiple block ic mfg code uid (1) 1. gray means that t he field is optional. first block number number of blocks crc16 request eof 8 bits c3h 02h 64 bits 16 bits 8 bits 16 bits table 86. fast read multiple block response format when error_flag is not set response sof response_ flags sector security status (1) 1. gray means that t he field is optional. data crc16 response eof 8 bits 8 bits (2) 2. repeated as needed. 32 bits (2) 16 bits table 87. sector security status if option_flag is set b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use. all at 0 password control bits read / write protection bits 0: current sector not locked 1: current sector locked
commands codes LRIS64K 88/100 doc id 15336 rev 11 response parameter: error code as error_flag is set: ? 0fh: other error ? 10h: block address not available table 88. fast read multiple block response format when error_flag is set response sof response_flags err or code crc16 response eof 8 bits 8 bits 16 bits figure 58. fast read multiple block frame exchange between vcd and LRIS64K vcd sof fast read multiple block request eof LRIS64K <-t 1 -> sof fast read multiple block response eof
LRIS64K commands codes doc id 15336 rev 11 89/100 24.21 inventory initiated before receiving the inventory initiated command, the LRIS64K must have received an initiate or a fast initiate command in order to set the initiate_ flag. if not, the LRIS64K does not answer to the inventory initiated command. on receiving the inventory initiated request, the LRIS64K runs the anticollision sequence. the inventory_flag must be set to 1. the meaning of flags 5 to 8 is given in ta bl e 2 0 : request flags 5 to 8 when bit 3 = 1 . the request contains: the flags, the inventory command code the afi if the afi flag is set the mask length the mask value the crc the LRIS64K does not generate any answer in case of error. the response contains: the flags the unique id during an inventory process, if the vcd does not receive an rf LRIS64K response, it waits a time t 3 before sending an eof to switch to the next slot. t 3 starts from the rising edge of the request eof sent by the vcd. if the vcd sends a 100% modulated eof, the minimum value of t 3 is: t 3 min = 4384/f c (323.3 s) + t sof if the vcd sends a 10% modulated eof, the minimum value of t 3 is: t 3 min = 4384/f c (323.3 s) + t nrt where: t sof is the time required by the LRIS64K to transmit an sof to the vcd t nrt is the nominal response time of the LRIS64K t nrt and t sof are dependent on the LRIS64K-to-vcd data rate and subcarrier modulation mode. table 89. inventory initiated request format request sof request _flags inventory initiated ic mfg code optional afi mask length mask value crc16 request eof 8 bits d1h 02h 8 bits 8 bits 0 - 64 bits 16 bits table 90. inventory initiated response format response sof response _flags dsfid uid crc16 response eof 8 bits 8 bits 64 bits 16 bits
commands codes LRIS64K 90/100 doc id 15336 rev 11 24.22 initiate on receiving the initiate command, the lris64 k will set the internal initiate_flag and send back a response only if it is in the ready state. the command has to be issued in the non addressed mode only (select_flag is reset to 0 and address_flag is reset to 0). if an error occurs, the LRIS64K does not generate any answer. the initiate_flag is reset after a power off of the LRIS64K. the request contains: no data the response contains: the flags the unique id table 91. initiate request format request sof request_flags initiate ic mfg code crc16 request eof 8 bits d2h 02h 16 bits table 92. initiate initiated response format response sof response _flags dsfid uid crc16 response eof 8 bits 8 bits 64 bits 16 bits figure 59. initiate frame exchange between vcd and LRIS64K vcd sof initiate request eof LRIS64K <-t 1 -> sof initiate response eof
LRIS64K maximum rating doc id 15336 rev 11 91/100 25 maximum rating stressing the device above the rating listed in the absolute maximum ratings table may cause permanent damage to the device. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not imp lied. exposure to absolute ma ximum rating conditions for extended periods may affect device reliability. refer also to the stmicroelectronics sure program and other relevant quality documents. table 93. absolute maximum ratings symbol parameter min. max. unit t stg storage conditions sawn bumped wafer (kept in its antistatic bag) 15 25 c t stg storage time 6 months i cc supply current on ac0 / ac1 ?20 20 ma v max input voltage on ac0 / ac1 ?7 7 v v esd electrostatic discharge voltage ac0 - ac1 (hbm) (1) 1. aec-q100-002 (compliant with jedec std jesd22-a114a, c1 = 100 pf, r1 = 1500 ? , r2 = 500 ? ) . ?800 800 v ac0 - ac1 (mm) ?100 100 v
rf dc and ac parameters LRIS64K 92/100 doc id 15336 rev 11 26 rf dc and ac parameters this section summarizes the operating and measurement conditions, and the dc and ac characteristics of the device in rf mode. the parameters in the dc and ac characteristic tables that follow are derived from tests performed under the measurement conditions summarized in the relevant tables. designers should check that the operating conditions in their circuit match the measurement conditions when relying on the quoted parameters. table 94. rf ac characteristics (1) (2) symbol parameter condition min typ max unit f cc external rf signal frequency 13.553 13.56 13.567 mhz h_iso operating field according to iso t a = 0 c to 50 c 150 5000 ma/m h_extended operating field in extended temperature range t a = ?40 c to 85 c 150 3500 ma/m mi carrier 10% carrier modulation index (3) (4) mi=(a-b)/(a+b) 150 ma/m > h_iso > 1000 ma/m 15 30 % h_iso > 1000 ma/m 10 30 t rfr ,t rff 10% rise and fall time 0.5 3.0 s t rfsbl 10% minimum pulse width for bit 7.1 9.44 s mi carrier 100% carrier modulation index mi=(a-b)/(a+b) 95 100 % t rfr ,t rff 100% rise and fall time 0.5 3.5 s t rfsbl 100% minimum pulse width for bit 7.1 9.44 s t jit bit pulse jitter -2 +2 s t min cd minimum time from carrier generation to first data from h-field min 0.1 1 ms f sh subcarrier frequency high f cc /32 423.75 khz f sl subcarrier frequency low f cc /28 484.28 khz t 1 time for LRIS64K response 4224/f s 318.6 320.9 323.3 s t 2 time between commands 4224/f s 309 311.5 314 s w t rf write time (including internal verify) 5.75 ms 1. t a = ?40 to 85 c. 2. all timing measurements were performed between 0 c and 50 c on a reference antenna with the following characteristics: external size: 75 mm x 48 mm number of turns: 5 width of conductor: 0.5 mm space between 2 conductors: 0.3 mm value of the tuning capacitor in so8: 27.5 pf (LRIS64K) value of the coil: 5 h tuning frequency: 13.56 mhz. 3. characterized only, not 100% tested 4. 15% (or more) carrier modulation index o ffers a better signal/noise ratio and ther efore a wider operating range with a better noise immunity
LRIS64K rf dc and ac parameters doc id 15336 rev 11 93/100 figure 60 shows an ask modulated signal, from the vcd to the LRIS64K. the test condition for the ac/dc parameters are: close coupling condition with tester antenna (1mm) LRIS64K performance measured at the tag antenna figure 60. LRIS64K synchronous timing, transmit and receive table 95. rf dc characteristics (1) 1. t a = ?40 to 85 c. symbol parameter test conditions min. typ. max. unit v cc limited voltage 2.0 v v back backscattered level as defined by iso test iso/iec 10373-7 10 mv i cc supply current read v cc = 2.0 v 50 a write v cc = 2.0 v 150 a c tun internal tuning capacitor (2) 2. characterised only, at room temperature only, measured at v ac0-ac1 = 0.5 v peak. f = 13.56 mhz 24.8 27.5 30.2 pf table 96. operating conditions symbol parameter min. max. unit t a ambient operating temperature ?40 85 c ai06680 ab t rff t rfr t rfsbl t max t min cd f cc
part numbering LRIS64K 94/100 doc id 15336 rev 11 27 part numbering for a list of available options (speed, package, etc.) or for further information on any aspect of this device, please contact your nearest st sales office. table 97. ordering information scheme example: LRIS64K - sbn18/ 2 device type LRIS64K (long-range tag with 64 kbit eeprom) package sbn18 = 180 m 15 m bumped and sawn wafer on 8-inch frame tuning capacitance 2= 27.5 pf
LRIS64K anticollision algorithm doc id 15336 rev 11 95/100 appendix a anticollision algorithm the following pseudocode describes how anti collision could be implemented on the vcd, using recursivity. a.1 algorithm for pulsed slots function push (mask, address); pushes on private stack function pop (mask, address); pops from private stack function pulse_next_pause; generates a power pulse function store(LRIS64K_uid); stores LRIS64K_uid function poll_loop (sub_address_size as integer) pop (mask, address) mask = address & mask; generates new mask ; send the request mode = anticollision send_request (request_cmd, mode, mask length, mask value) for sub_address = 0 to (2^sub_address_size - 1) pulse_next_pause if no_collision_is_detected ; LRIS64K is inventoried then store (LRIS64K_uid) else ; remember a collision was detected push(mask,address) endif next sub_address if stack_not_empty ; if some collisions have been detected and then ; not yet processed, the function calls itself poll_loop (sub_address_size); recursively to process the last stored collision endif end poll_loop main_cycle: mask = null address = null push (mask, address) poll_loop(sub_address_size) end_main_cycle
crc LRIS64K 96/100 doc id 15336 rev 11 appendix b crc b.1 crc error detection method the cyclic redundancy check (crc) is calculated on all data contained in a message, from the start of the flags through to the end of data. the crc is used from vcd to LRIS64K and from LRIS64K to vcd. to add extra protection against shifting errors, a further transformation on the calculated crc is made. the one?s complement of the calculated crc is the value attached to the message for transmission. to check received messages the 2 crc bytes are often also included in the re-calculation, for ease of use. in this case, the expected value for the generated crc is the residue f0b8h. b.2 crc calculation example this example in c language illustrates one met hod of calculating the crc on a given set of bytes comprising a message. c-example to calculate or check the crc16 according to iso/iec 13239 #define polynomial0x8408// x^16 + x^12 + x^5 + 1 #define preset_value0xffff #define check_value0xf0b8 #define number_of_bytes4// example: 4 data bytes #define calc_crc1 #define check_crc0 void main() { unsigned int current_crc_value; unsigned char array_of_databytes[number_of_bytes + 2] = {1, 2, 3, 4, 0x91, 0x39}; int number_of_databytes = number_of_bytes; int calculate_or_check_crc; int i, j; calculate_or_check_crc = calc_crc; // calculate_or_check_crc = check_crc;// this could be an other example if (calculate_or_check_crc == calc_crc) { table 98. crc definition crc definition crc type length polynomial direction preset residue iso/iec 13239 16 bits x 16 + x 12 + x 5 + 1 = 8408h backward ffffh f0b8h
LRIS64K crc doc id 15336 rev 11 97/100 number_of_databytes = number_of_bytes; } else // check crc { number_of_databytes = number_of_bytes + 2; } current_crc_value = preset_value; for (i = 0; i < number_of_databytes; i++) { current_crc_value = current_crc_value ^ ((unsigned int)array_of_databytes[i]); for (j = 0; j < 8; j++) { if (current_crc_value & 0x0001) { current_crc_value = (current_crc_value >> 1) ^ polynomial; } else { current_crc_value = (current_crc_value >> 1); } } } if (calculate_or_check_crc == calc_crc) { current_crc_value = ~current_crc_value; printf ("generated crc is 0x%04x\n", current_crc_value); // current_crc_value is now ready to be appended to the data stream // (first lsbyte, then msbyte) } else // check crc { if (current_crc_value == check_value) { printf ("checked crc is ok (0x%04x)\n", current_crc_value); } else { printf ("checked crc is not ok (0x%04x)\n", current_crc_value); } } }
application family identifier (afi) LRIS64K 98/100 doc id 15336 rev 11 appendix c application family identifier (af i) the afi (application family identifier) represents the type of application targeted by the vcd and is used to extract from all the LRIS64K present only the LRIS64K meeting the required application criteria. it is programmed by the LRIS64K issuer (the purchaser of the LRIS64K). once locked, it cannot be modified. the most significant nibble of the afi is used to code one specific or all application families, as defined in ta b l e 9 9 . the least significant nibble of the afi is us ed to code one specific or all application subfamilies. subfamily codes diff erent from 0 are proprietary. table 99. afi coding (1) 1. x = '1' to 'f', y = '1' to 'f' afi most significant nibble afi least significant nibble meaning viccs respond from examples / note ?0? ?0? all families and subfamilies no applicative preselection ?x? '0 'all subfamilies of family x wide applicative preselection 'x '?y? only the yth subfamily of family x ?0? ?y? proprietary subfamily y only ?1 '?0?, ?y? transport mass transit, bus, airline, etc. '2 '?0?, ?y? financial iep, banking, retail, etc. '3 '?0?, ?y? identificati on access control, etc. '4 '?0?, ?y? telecommunication public telephony, gsm, etc. ?5? ?0?, ?y? medical '6 '?0?, ?y? multimedia internet services, etc. '7 '?0?, ?y? gaming 8 '?0?, ?y? data storage portable files, etc. '9 '?0?, ?y? item management 'a '?0?, ?y? express parcels 'b '?0?, ?y? postal services 'c '?0?, ?y? airline bags 'd '?0?, ?y? rfu 'e '?0?, ?y? rfu ?f? ?0?, ?y? rfu
LRIS64K revision history doc id 15336 rev 11 99/100 revision history table 100. document revision history date revision changes 26-jan-2009 1 initial release. 05-feb-2009 2 tssop8 package removed. wafer silhouette added on page 1 . 13-feb-2009 3 device programming time corrected. 02-apr-2009 4 revision history corrected (revision 3 added). figure 2: ufdfpn8 connections corrected. 16-jul-2009 5 document status promot ed from target specification to preliminary data. v esd modified in table 93: absolute maximum ratings . 17-sep-2009 6 v esd modified in table 93: absolute maximum ratings . 25-aug-2010 7 updated features on page 1 . removed all references to packages. removed figure 2: ufdfpn8 connections. updated section 4: initial delivery state on page 18 . updated figure 3 , figure 4 , ta b l e 9 4 , and ta bl e 9 5 . updated storage time (t stg ) in table 93: absolute maximum ratings on page 91 . 05-oct-2010 8 document classification changed to public. updated dsfid value in section 4: initial delivery state 08-nov-2010 9 updated document status from prelimi nary status to public. 19-sep-2011 10 modified section 1: description updated disclaimer on last page. 27-oct-2011 11 updated footnote (2) of table 94: rf ac characteristics .
LRIS64K 100/100 doc id 15336 rev 11 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 he rein 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 as sumes 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. i f 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 whatsoev er 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 parti cular purpose (and their equivalents under the laws of any jurisdiction), or infringement of any patent, copyright or other intellectual property right. unless expressly approved in writing by two authorized st representatives, st products are not recommended, authorized or warranted for use in milita ry, air craft, space, life saving, or life sustaining applications, nor in products or systems where failure or malfunction may result in personal injury, death, or severe property or environmental damage. st products which are not specified as "automotive grade" may only be used in automotive applications at user?s own risk. resale of st products with provisions different from the statements and/or technical features set forth in this document shall immediately void any warranty granted by st for the st product or service described herein and shall not create or extend in any manner whatsoev er, any liability of st. st and the st logo are trademarks or registered trademarks of st in various countries. information in this document supersedes and replaces all information previously supplied. the st logo is a registered trademark of stmicroelectronics. all other names are the property of their respective owners. ? 2011 stmicroelectronics - all rights reserved stmicroelectronics group of companies australia - belgium - brazil - canada - china - czech republic - finland - france - germany - hong kong - india - israel - ital y - japan - malaysia - malta - morocco - philippines - singapore - spain - sweden - switzerland - united kingdom - united states of america www.st.com

▲Up To Search▲

Price & Availability of LRIS64K

	To Download LRIS64K Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .