LRI2K-A1S/1GE STMicroelectronics, LRI2K-A1S/1GE Datasheet
LRI2K-A1S/1GE
Specifications of LRI2K-A1S/1GE
Available stocks
Related parts for LRI2K-A1S/1GE
LRI2K-A1S/1GE Summary of contents
Page 1
... Electrical article surveillance capable (software controlled) ■ Kill function ■ Read & Write (Block of 32 bits) ■ programming time ■ Packages ® – ECOPACK (RoHS compliant) September 2008 UFDFPN8 (MB) 2 × 3 mm² (MLP) Wafer Rev 8 LRI2K 1/86 www.st.com 1 ...
Page 2
... Bit representation and coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.1 Bit coding using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.1.1 5.1.2 5.2 Bit coding using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.2.1 5.2.2 6 LRI2K to VCD frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1 SOF when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1.1 6.1.2 2/86 Power transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Operating field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 High data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 High data rate ...
Page 3
... EOF when using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 6.4.1 6.4.2 7 Unique identifier (UID Application family identifier (AFI Data storage format identifier (DSFID 9.1 CRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 10 LRI2K protocol description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 11 LRI2K states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 11.1 Power-off state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 11.2 Ready state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 11.3 Quiet state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 11.4 Selected state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 12 Modes ...
Page 4
... Request parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 16 Request processing by the LRI2K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 17 Explanation of the possible cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 18 Inventory Initiated command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 19 Timing definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 19.1 t1: LRI2K response delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 19.2 t2: VCD new request delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 19 VCD new request delay in the absence of a response from the LRI2K Commands codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 20.1 Inventory ...
Page 5
... LRI2K 20.21 Fast Read Multiple Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 20.22 Inventory Initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 20.23 Initiate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 21 Maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . and AC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 23 Package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 24 Part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Appendix A Anticollision algorithm (Informative A.1 Algorithm for pulsed slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Appendix B CRC (Informative B.1 CRC error detection method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 B.2 CRC calculation example ...
Page 6
... Table 5. UID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table 6. CRC transmission rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Table 7. VCD request frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Table 8. LRI2K response frame format Table 9. LRI2K response depending on request flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Table 10. General request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Table 11. Definitions of request flags Table 12. Request flags when bit Table 13. Request flags when bit Table 14 ...
Page 7
... LRI2K Table 49. Lock AFI response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Table 50. Write DSFID request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Table 51. Write DSFID response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . 59 Table 52. Write DSFID response format when Error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Table 53. Lock DSFID request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Table 54. Lock DSFID response format when Error_flag is NOT set . . . . . . . . . . . . . . . . . . . . . . . . . 60 Table 55 ...
Page 8
... Lock Block frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Figure 45. Read Multiple Block frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . 54 Figure 46. Select frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Figure 47. Reset to Ready frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . . . . . 56 Figure 48. Write AFI frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 ...
Page 9
... Fast Initiate frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Figure 59. Fast Read Multiple Block frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . 73 Figure 60. Initiate frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Figure 61. LRI2K synchronous timing, transmit and receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Figure 62. UFDFPN8 - 8-lead ultra thin fine pitch dual flat package no lead (MLP) outline . . . . . . . . 79 ...
Page 10
... Outgoing data are generated by the LRI2K load variation using Manchester coding with one or two subcarrier frequencies at 423 kHz and 484 kHz. Data are transferred from the LRI2K at 6.6 Kbit/s in low data rate mode and 26 Kbit/s fast data rate mode. The LRI2K supports 53 Kbit/s in high data rate mode with one subcarrier frequency at 423 kHz. ...
Page 11
... During a write operation, the 32 bits of the block are replaced by the new 32-bit value. The LRI2K also has a 64-bit block that is used to store the 64-bit unique identifier (UID). The UID is compliant to the ISO 15963 description, and its value is used during the anticollision sequence (Inventory) ...
Page 12
... The LRI2K supports the following commands: ● Inventory, used to perform the anticollision sequence. ● Stay Quiet, used to put the LRI2K in quiet mode, where it does not respond to any inventory command. ● Select, used to select the LRI2K. After this command, the LRI2K processes all Read/Write commands with Select_flag set. ● ...
Page 13
... Power transfer Power is transferred to the LRI2K by radio frequency at 13.56 MHz via coupling antennas in the LRI2K and the VCD. The RF operating field of the VCD is transformed on the LRI2K antenna voltage which is rectified, filtered and internally regulated. The amplitude modulation (ASK) on this received signal is demodulated by the ASK demodulator. ...
Page 14
... The modulation index is defined as [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 The LRI2K is operational for any degree of modulation index between 10% and 30%. Figure 3. 100% modulation waveform Table 3. 10% modulation parameters Symbol ...
Page 15
... The data coding implemented in the LRI2K uses pulse position modulation. Both data coding modes that are described in the ISO 15693 are supported by the LRI2K. The selection is made by the VCD and indicated to the LRI2K within the start of frame (SOF). 3.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 256 successive time periods of 18.88 µ ...
Page 16
... Data rate and data coding Figure 6. Detail of one time period Pulse Modulated Carrier . . 16/ 9.44 µs 18.88 µ Time Period one of 256 AI06657 LRI2K ...
Page 17
... LRI2K 3.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 successive time periods of 18.88 µs (256/f 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 ...
Page 18
... Frames are delimited by a start of frame (SOF) and an end of frame (EOF). They are implemented using code violation. Unused options are reserved for future use. The LRI2K is ready to receive a new command frame from the VCD 311.5 µs (t sending a response frame to the VCD. ...
Page 19
... Data rates The LRI2K 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. ...
Page 20
... For the Fast commands, a logic 1 starts with an unmodulated time of 9.44 µs followed by 4 pulses at 423.75 kHz (f Figure 15. Logic 1, high data rate x2 20/86 /32) followed by an unmodulated time of C Figure 12. 37.76µs Figure 13. 18.88µs Figure 14. 37.76µs /32) as shown in Figure 15. C 18.88µs LRI2K ai12076 /32) followed ai12066 ai12077 ai12067 ...
Page 21
... LRI2K 5.1.2 Low data rate A logic 0 starts with 32 pulses at 423.75 kHz (f 75.52 µs as shown in Figure 16. Logic 0, low data rate For the fast commands, a logic 0 starts with 16 pulses of 423,75 kHz (f unmodulated time of 37,76 µs as shown in Figure 17. Logic 0, low data rate x2 A logic 1 starts with an unmodulated time of 75,52 µs followed by 32 pulses of 423,75 kHz ...
Page 22
... For the Fast commands, the x2 mode is not available. 37.46µs /32) followed by 36 pulses at 484.28 kHz C Figure 22. For the Fast commands, the x2 mode is not available. 149.84µs /28) followed by 32 pulses at 423.75kHz C Figure 23. For the fast commands, the x2 mode is not available. 149.84µs LRI2K ai12074 ai12073 ai12072 ai12075 ...
Page 23
... Figure 25. Start of frame, high data rate, one subcarrier x2 Figure 24. 113.28µs /32), and a logic 1 that consists of an unmodulated time of C Figure 56.64µs LRI2K to VCD frames 37.76µs ai12078 25. 18.88µs ai12079 23/86 ...
Page 24
... LRI2K to VCD frames 6.1.2 Low data rate SOF comprises an unmodulated time of 226.56 µs, followed by 96 pulses at 423.75 kHz (f /32), and a logic 1 that consists of an unmodulated time of 75.52 µs followed by 32 pulses C at 423.75 kHz as shown in Figure 26. Start of frame, low data rate, one subcarrier For the Fast commands, the SOF comprises an unmodulated time of 113.28 µ ...
Page 25
... Figure 33. End of frame, low data rate, one subcarrier x2 C Figure 30. Figure 31. 56.64µs 18.88µs Figure 32. Figure 33. 75.52µs 226.56µs LRI2K to VCD frames /32) and by an unmodulated time of 113.28µs /32) and an C ai12085 /32) and an unmodulated time of C 453.12µs /32) and an C ai12087 ai12084 ai12086 ...
Page 26
... LRI2K to VCD frames 6.4 EOF when using two subcarriers 6.4.1 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 (f /28) as shown in C For the Fast commands, the x2 mode is not available. ...
Page 27
... IC manufacturer code of ST 02h bits (ISO/IEC 7816-6/AM1) ● a unique serial number on 48 bits. Table 5. UID format MSB 63 E0h With the UID each LRI2K can be addressed uniquely and individually during the anticollision loop and for one-to-one exchanges between a VCD and an LRI2K 02h Unique identifier (UID) ...
Page 28
... Application family identifier (AFI) The AFI (application family identifier) represents the type of application targeted by the VCD and is used to identify, among all the LRI2Ks present, only the LRI2Ks that meet the required application criteria. Figure 36. LRI2K decision tree for AFI The AFI is programmed by the LRI2K issuer (or purchaser) in the AFI register. Once programmed and Locked, it can no longer be modified ...
Page 29
... EOF. The CRC is calculated on all the bytes between the SOF and the CRC field. Upon reception of a request from the VCD, the LRI2K verifies that the CRC value is valid invalid, the LRI2K discards the frame and does not answer to the VCD. ...
Page 30
... LRI2K protocol description The transmission protocol (or simply protocol) defines the mechanism used to exchange instructions and data between the VCD and the LRI2K, in both directions based on the concept of "VCD talks first". This means that an LRI2K 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: ● ...
Page 31
... LRI2K Figure 37. LRI2K protocol timing Request VCD frame (Table LRI2K Timing 7) Response frame (Table LRI2K protocol description Request frame (Table 7) Response frame (Table 31/86 ...
Page 32
... The LRI2K is in the Power-off state when it does not receive enough energy from the VCD. 11.2 Ready state The LRI2K is in the Ready state when it receives enough energy from the VCD. When in the Ready state, the LRI2K answers any request where the Select_flag is not set. 11.3 ...
Page 33
... UID) Error (03h) Figure 38. LRI2K state transition diagram Any other command where the Address_Flag is set AND where Inventory_Flag is not set 1. The intention of the state transition method is that only one LRI2K should be in the selected state at a time. Address_flag 1 Addressed Non addressed X ...
Page 34
... Modes 12 Modes The term “mode” refers to the mechanism used in a request to specify the set of LRI2Ks that will answer the request. 12.1 Addressed mode When the Address_flag is set to 1 (Addressed mode), the request contains the Unique ID (UID) of the addressed LRI2K. Any LRI2K that receives a request with the Address_flag set to 1 compares the received Unique ID to its own ...
Page 35
... F 13.1 Request flags In a request, the "flags" field specifies the actions to be performed by the LRI2K 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). ...
Page 36
... AFI flag Bit 6 Nb_slots flag Bit 7 Option flag Bit 8 RFU 36/86 Level Request is executed by any LRI2K according to the setting of 0 Address_flag (1) 1 Request is executed only by the LRI2K in Selected state Request is not addressed. UID field is not present. The request is 0 executed by all LRI2Ks. ...
Page 37
... General response format S O Response flags F 14.1 Response flags In a response, the flags indicate how actions have been performed by the LRI2K and whether corresponding fields are present or not. The response flags consist of eight bits. Table 15. Definitions of response flags Bit No. Flag Bit 1 ...
Page 38
... Response format 14.2 Response error code If the Error_flag is set by the LRI2K in the response, the Error code field is present and provides information about the error that occurred. Error codes not specified in Table 16. Response error code definition Error code 03h 0F 10h 11h 12h ...
Page 39
... The purpose of the anticollision sequence is to inventory the LRI2Ks present in the VCD field using their unique ID (UID). The VCD is the master of communications with one or several LRI2Ks. It initiates LRI2K communication by issuing the Inventory request. The LRI2K sends its response in the determined slot or does not respond. ...
Page 40
... VCD sends an EOF. The following rules and restrictions apply: ● LRI2K answer is detected, the VCD may switch to the next slot by sending an EOF, ● if one or more LRI2K answers are detected, the VCD waits until the complete frame has been received before sending an EOF for switching to the next slot. ...
Page 41
... LRI2K 16 Request processing by the LRI2K Upon reception of a valid request, the LRI2K performs the following algorithm: ● NbS is the total number of slots (1 or 16) ● 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 ● ...
Page 42
... The VCD sends an Inventory request frame terminated by an EOF. The number of slots is 16. ● LRI2K 1 transmits its response in Slot the only one to do so, therefore no collision occurs and its UID is received and registered by the VCD; ● The VCD sends an EOF in order to switch to the next slot. ...
Page 43
... LRI2K Figure 40. Description of a possible anticollision sequence Explanation of the possible cases 43/86 ...
Page 44
... Inventory Initiated command 18 Inventory Initiated command The LRI2K provides a special feature to improve the inventory time response of moving tags using the Initiate_flag value. This flag, controlled by the Initiate command, allows tags to answer to Inventory Initiated commands. For applications in which multiple tags are moving in front of a reader possible to miss tags using the standard inventory command ...
Page 45
... 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 LRI2K also the time after which the VCD may send a new request to the LRI2K as described in 2 Table 37: LRI2K protocol Values of t ...
Page 46
... Commands codes 20 Commands codes The LRI2K supports the commands described in this section. Their codes are given in Table 20. Table 20. Command codes Command code standard 01h 02h 20h 21h 22h 23h 25h 26h 27h 28h 29h 2Ah 2Bh 2Ch 46/86 Command code Function ...
Page 47
... Inventory response format Response Response SOF flags 8 bits During an Inventory process, if the VCD does not receive an RF LRI2K response, it waits a time t before sending an EOF to switch to the next slot request EOF sent by the VCD. ● If the VCD sends a 100% modulated EOF, the minimum value of t ...
Page 48
... Commands codes 20.2 Stay Quiet On receiving the Stay Quiet command, the LRI2K enters the Quiet state 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 LRI2K does not process any request if the Inventory_flag is set, ● ...
Page 49
... LRI2K 20.3 Read Single Block On receiving the Read Single Block command, the LRI2K reads the requested block and sends back its 32 bits value in the response. The Option_flag is supported. Table 24. Read Single Block request format Request Request_flags SOF 8 bits Request parameters: ● ...
Page 50
... Commands codes Figure 42. READ Single Block frame exchange between VCD and LRI2K VCD SOF LRI2K 50/86 Read Single EOF Block request <-t -> SOF 1 Read Single EOF Block response LRI2K ...
Page 51
... LRI2K 20.4 Write Single Block On receiving the Write Single Block Command, the LRI2K writes the data contained in the request to the requested block and reports whether the write operation was successful in the response. The Option_flag is supported. During the write cycle t Otherwise, the LRI2K may not program correctly the data into the memory. The t equal × ...
Page 52
... Commands codes 20.5 Lock Block On receiving the Lock Block command, the LRI2K permanently locks the selected block. The Option_flag is supported. During the write cycle t Otherwise, the LRI2K may not lock correctly the memory block. The × 302µs. Table 31. Lock Single Block request format ...
Page 53
... Read Multiple Block When receiving the Read Multiple Block command, the LRI2K reads the selected blocks and sends back their value in multiples of 32 bits in the response. The blocks are numbered from '00 to '3F' in the request and the value is minus one (–1) in the field. For example, if the “ ...
Page 54
... Commands codes Figure 45. Read Multiple Block frame exchange between VCD and LRI2K VCD SOF LRI2K 54/86 Read Multiple EOF Block request <-t -> SOF 1 Read Multiple Block EOF response LRI2K ...
Page 55
... UID does not match its own, the selected LRI2K returns to the Ready state and does not send a response. The LRI2K answers an error code only if the UID is equal to its own UID. If not, no response is generated. Table 38. Select request format ...
Page 56
... Commands codes 20.8 Reset to Ready On receiving a Reset to Ready command, the LRI2K returns to the Ready state. In the Addressed mode, the LRI2K answers an error code only if the UID is equal to its own UID. If not, no response is generated. Table 41. Reset to Ready request format Request Request_ SOF ...
Page 57
... LRI2K 20.9 Write AFI On receiving the Write AFI request, the LRI2K writes the AFI byte value into its memory. The Option_flag is supported. During the write cycle t Otherwise, the LRI2K may not write correctly the AFI value into the memory. The t equal × ...
Page 58
... Lock AFI On receiving the Lock AFI request, the LRI2K locks the AFI value permanently. The Option_flag is supported. During the write cycle t Otherwise, the LRI2K may not Lock correctly the AFI value in memory. The × 302 µs. 1nom Table 47. Lock AFI request format ...
Page 59
... LRI2K 20.11 Write DSFID On receiving the Write DSFID request, the LRI2K writes the DSFID byte value into its memory. The Option_flag is supported. During the write cycle t Otherwise, the LRI2K may not write correctly the DSFID value in memory. The t equal × 302µs. ...
Page 60
... Lock DSFID On receiving the Lock DSFID request, the LRI2K locks the DSFID value permanently. The Option_flag is supported. During the write cycle t Otherwise, the LRI2K may not lock correctly the DSFID value in memory. The t equal × 302µs. 1nom Table 53. ...
Page 61
... LRI2K 20.13 Get System Info When receiving the Get System Info command, the LRI2K 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. Table 56. ...
Page 62
... Get Multiple Block Security Status When receiving the Get Multiple Block Security Status command, the LRI2K sends back the block security status. The blocks are numbered from '00 to '3F' 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 ...
Page 63
... LRI2K Figure 53. Get Multiple Block Security Status frame exchange between VCD and LRI2K VCD SOF LRI2K Get Multiple Block EOF Security Status <-t -> SOF 1 Commands codes Get Multiple Block Security EOF Status 63/86 ...
Page 64
... Non Addressed or the Selected mode, the LRI2K returns an error response. During the comparison cycle equal to t 10%). Otherwise, the LRI2K may not match the kill code correctly. The × 302µs. After a successful Kill command, the LRI2K is deactivated and does not 1nom interpret any other command. Table 63. ...
Page 65
... Write Kill On receiving the Write Kill command, the LRI2K writes the kill code with the data contained in the request and reports whether the operation was successful in the response. The Option_flag is supported. After a successful write, the kill code must be locked by a Lock Kill command to activate the protection ...
Page 66
... Commands codes 20.17 Lock Kill On receiving the Lock Kill command, the LRI2K locks the Kill code permanently. The Option_flag is supported. RFU bit 8 of the request flag must be set to ‘1’. During the write cycle t Otherwise, the LRI2K may not lock the memory block correctly. The × ...
Page 67
... LRI2K Figure 56. Lock Kill frame exchange between VCD and LRI2K VCD SOF LRI2K LRI2K Lock Kill EOF request <-t -> SOF 1 <------------ t ------------>< Commands codes Lock Kill Lock sequence when EOF response error Lock Kill -> SOF 1 response EOF 67/86 ...
Page 68
... Commands codes 20.18 Fast Read Single Block On receiving the Fast Read Single Block command, the LRI2K 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. Table 72. Fast Read Single Block request format ...
Page 69
... LRI2K Figure 57. Fast Read Single Block frame exchange between VCD and LRI2K VCD SOF LRI2K Fast Read Single EOF Block request <-t -> SOF 1 Commands codes Fast Read Single EOF Block response 69/86 ...
Page 70
... Fast Inventory Initiated Before receiving the Fast Inventory Initiated command, the LRI2K must have received an Initiate or a Fast Initiate command in order to set the Initiate_ flag. If not, the LRI2K does not answer to the Fast Inventory Initiated command. On receiving the Fast Inventory Initiated request, the LRI2K runs the anticollision sequence. ...
Page 71
... On receiving the Fast Initiate command, the LRI2K sets the internal Initiate_flag and sends back a response. 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 error occurs, the LRI2K does not generate any answer. The Initiate_flag is reset after a power off of the LRI2K. The data rate of the response is multiplied by 2 ...
Page 72
... For example, a value 06h in the “number of blocks” field causes the LRI2K to read 7 blocks. The maximum number of blocks is fixed at 64. During Sequential Block Read, when the block address reaches 64, it rolls over to 0 ...
Page 73
... LRI2K Figure 59. Fast Read Multiple Block frame exchange between VCD and LRI2K VCD SOF LRI2K Fast Read Multiple EOF Block request <-t -> SOF 1 Commands codes Fast Read Multiple Block EOF response 73/86 ...
Page 74
... Inventory Initiated Before receiving the Inventory Initiated command, the LRI2K must have received an Initiate or a Fast Initiate command in order to set the Initiate_ flag. If not, the LRI2K does not answer to the Inventory Initiated command. On receiving the Inventory Initiated request, the LRI2K runs the anticollision sequence. The Inventory_flag must be set to 1 ...
Page 75
... On receiving the Initiate command, the LRI2K sets the internal Initiate_flag and sends back a response. 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 error occurs, the LRI2K does not generate any answer. The Initiate_flag is reset after a power off of the LRI2K. ...
Page 76
... Mil. Std. 883 - Method 3015. 2. Human body model. 3. Machine model. 76/86 Parameter UFDFPN8 Wafer (kept in its antistatic bag) Wafer (kept in its antistatic bag) UFDFPN8 (HBM (1) UFDFPN8 (MM Min. Max. –65 150 months –20 20 –7 7 (2) ) –1000 1000 (3) ) –100 100 LRI2K Unit ° ...
Page 77
... A 2. All timing measurements were performed on a reference antenna with the following characteristics: External size Number of turns: 6 Width of conductor Space between 2 conductors: 0.4 mm Value of the tuning capacitor: 28.5 pF (LRI2K-W4) Value of the coil: 4.3 µH Tuning frequency: 13.8 MHz. (1) (2) Parameter Condition ...
Page 78
... Ambient operating temperature A Figure 61. LRI2K synchronous timing, transmit and receive t MAX Figure 61 shows an ASK modulated signal, from the VCD to the LRI2K. The test condition for the AC/DC parameters are: ● Close coupling condition with tester antenna (1mm) ● LRI2K performance measured at the tag antenna ...
Page 79
... LRI2K 23 Package mechanical data In order to meet environmental requirements, ST offers these devices in ECOPACK packages. These packages have a Lead-free second-level interconnect. The category of second-level interconnect is marked on the package and on the inner box label, in compliance with JEDEC Standard JESD97. The maximum ratings related to soldering conditions are also marked on the inner box label. ...
Page 80
... MBTG = UFDFPN8 (MLP8), tape & reel packing, ECOPACK RoHS compliant, Sb Tuning capacitance 28 Customer code given generic product xx = customer code after personalization For further information on any aspect of this device, please contact your nearest ST sales office. 80/86 LRI2K O -free and TBBA-free ® , lead-free, LRI2K ...
Page 81
... LRI2K is inventoried then store (LRI2K_UID) else ; remember a collision was detected push(mask,address) endif next sub_address if stack_not_empty ...
Page 82
... CRC (Informative) 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 LRI2K and from LRI2K to VCD. Table 94. CRC definition CRC type ...
Page 83
... LRI2K } else // check CRC { number_of_databytes = NUMBER_OF_BYTES + 2; } current_crc_value = PRESET_VALUE; for ( < number_of_databytes; i++) { current_crc_value = current_crc_value ^ ((unsigned int)array_of_databytes[i]); for ( < 8; j++) { if (current_crc_value & 0001h) { POLYNOMIAL; } else { } } } 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) ...
Page 84
... Application family identifier (AFI) (informative) The AFI (application family identifier) represents the type of application targeted by the VCD and is used to extract from all the LRI2K present only the LRI2K meeting the required application criteria programmed by the LRI2K issuer (the purchaser of the LRI2K). Once locked, it cannot be modified ...
Page 85
... UFDFPN8 package mechanical data updated and dimensions in 7 inches rounded to four decimal digits instead of three in UFDFPN8 - 8-lead ultra thin fine pitch dual flat package no lead (MLP) mechanical data. LRI2K products are no longer offered in A1 inlays and A6 and A7 antennas added for UFDPFN8 package in STG ratings ...
Page 86
... Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan - Malaysia - Malta - Morocco - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America 86/86 Please Read Carefully: © 2008 STMicroelectronics - All rights reserved STMicroelectronics group of companies www.st.com LRI2K ...