AN4054 Application note Comparison of RF addressing modes of low-density and high-density ISO/IEC 15693 devices Introduction This application note highlights the key differences of RF addressing modes between the products of the ISO/IEC 15693 STMicroelectronics family, which is composed of the dual interface EEPROM products (M24LRx) and the long range contactless products (LRix). The memory size is a key point and has an impact on some specific parameters of the RF (Radio frequency) commands. Dual interface memory M24LRx overview M24LRx devices are a dual-interface EEPROM. They feature an I2C interface. They are also a contactless memory powered by the received carrier electromagnetic wave. Thus, its internal memory can be addressed by either an I2C bus or the RF interface. The M24LRx products are compliant to the ISO/IEC 15693 recommendation for radiofrequency power and signal interface. Long range contactless tag LRxK overview LRxK devices are contactless memory powered by the received carrier electromagnetic wave with an EEPROM. They are compliant with the ISO/IEC 15693 specification. Table 1 lists the products concerned by this application note. . Table 1. Applicable products Type Applicable products Dual Interface EEPROM M24LR04E-R, M24LR64-R, M24LR64E-R, M24LR16E-R RFID & RF Memory ICs LRi1K, LRi2K, LRiS2K, LRiS64K November 2012 Doc ID 022825 Rev 3 1/13 www.st.com Contents AN4054 Contents 1 Comparison between low-density and high-density devices . . . . . . . . 4 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 IC reference of ISO/IEC 15693 products . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 How to identify the ISO/IEC 15693 products . . . . . . . . . . . . . . . . . . . . . . . 4 1.3.1 Using the Inventory command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3.2 Using the GetSystemInfo command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.4 Memory mapping of ISO/IEC 15693 products . . . . . . . . . . . . . . . . . . . . . . 6 1.5 Request_flags management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.5.1 Request_flags description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.5.2 Protocol Extension bit of Request_flags management . . . . . . . . . . . . . . 8 Appendix A Acronym and notational conventions . . . . . . . . . . . . . . . . . . . . . . . 10 A.1 List of acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 A.2 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 A.2.1 Binary number representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 A.2.2 Hexadecimal number representation . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 A.2.3 Decimal number representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2/13 Doc ID 022825 Rev 3 AN4054 List of tables List of tables Table 1. Table 2. Table 3. Table 4. Table 5. Table 6. Table 7. Table 8. Table 9. Table 10. Table 11. Table 12. Table 13. Table 14. Table 15. Applicable products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Low-density and high-density devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 IC references of the ISO/IEC 15693 family products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 UID of the STMicroelectronics ISO/IEC 15693 product . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Product code vs the ISO/IEC 15693 product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Memory mapping of LRix and M24LRx devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Addressing mode of LRix and M24LRx devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Write single block request format for low-density products. . . . . . . . . . . . . . . . . . . . . . . . . . 7 Write single block request format for high-density products . . . . . . . . . . . . . . . . . . . . . . . . . 7 RF command for low-density products using 1 byte and high-density products using 2 bytes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 RF command frame for low-density products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 RF command with block number parameter frame for high-density products . . . . . . . . . . . 8 Request_flags functions according to the product types . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 List of acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Doc ID 022825 Rev 3 3/13 Comparison between low-density and high-density devices 1 AN4054 Comparison between low-density and high-density devices This chapter highlights the differences of RF addressing modes between the ISO/IEC 15693 family products. 1.1 Overview The STMicroelectronics ISO/IEC 15693 family can be split as shown in Table 2. The M24LRx products can be accessed either by the I2C or the RF interface, and the LRix products can be addressed only by the RF interface. The M24LR64-R, M24LR64E-R, M24LR16E-R and LRiS64k devices have an extended memory and some RF commands shall be updated. Details are given in Chapter 1.4: Memory mapping of ISO/IEC 15693 products. Table 2. Low-density and high-density devices Access type Low-density High-density M24LR64-R RF and I2C access M24LR04E-R M24LR64E-R M24LR16E-R LRi1K RF access LRi2K LRiS64K LRiS2K 1.2 IC reference of ISO/IEC 15693 products The IC reference (IC ref) is a byte that identifies an STMicroelectronics product. Each product of the ISO/IEC 15693 family has its own and can be retrieved by issuing the GetSystemInfo RF command. Table 3 lists the different IC references of the ISO/IEC 15693 family products. Table 3. IC references of the ISO/IEC 15693 family products LRi1K IC ref 1.3 LRi2K LRiS2K LRiS64K M24LR04E-R M24LR16E-R M24LR64E-R M24LR64-R 0b010000xx 0b001000xx 0b001010xx 0x44 0x5A 0x4E 0x5E How to identify the ISO/IEC 15693 products There are two ways to identify the STMicroelectronics ISO/IEC 15693 products: 4/13 ● Analyze the product code field of the UID. ● Analyze the IC reference value of the GetSystemInfo response. Doc ID 022825 Rev 3 0x2C AN4054 1.3.1 Comparison between low-density and high-density devices Using the Inventory command The user can identify the STMicroelectronics ISO/IEC 15693 product by issuing an inventory command and analyzing the product code field of the UID. The UID of the STMicroelectronics ISO/IEC 15693 product is defined as shown in Table 4. Table 4. UID of the STMicroelectronics ISO/IEC 15693 product UID Byte 7 Byte 6 Byte 5 Byte 4 to 0 Value 0xE0 0x02 (1) Product code field IC manufacture code (2) 1. Manufacture code 0x02 for STMicroelectronics. 2. the product code field is defined in Table 5. The product code field (only the first 6 bits are relevant) is defined in the STMicroelectronics ISO/IEC 15693 as shown in Table 5. Table 5. Product code vs the ISO/IEC 15693 product Product LRI1k LRI2k LRis2K LRiS64k M24LR04E-R M24LR16E-R Product code field 0b0100 00xx 0b0010 00xx 0b0010 10xx 0b0100 01xx 0b0101 11xx 0b0100 11xx 1.3.2 M24LR64E M24LR64 -R -R 0b0101 11xx 0b0010 11xx Using the GetSystemInfo command Figure 1 is an example using the GetSystemInfo command to identify the STMicroelectronics ISO/IEC 15693 product: 1. Issue a GetSystemInfo with the Protocol Extension flag set to 1, and identify the STMicroelectronics product by analyzing the IC reference field, as defined in Table 3. 2. Issue a GetSystemInfo with the Protocol Extension flag set to 0. Doc ID 022825 Rev 3 5/13 Comparison between low-density and high-density devices Figure 1. AN4054 Flow diagram start Send an Inventory command No Is the IC manufacture code 0x02? Yes. This is an STMicroelectronics device Send a GetSystemInfo command with the Protocol Extension flag to 1 Has the tag replied to the GetSystemInfo Response? Yes. This is a high-density device (1) No or error code Send a GetSystemInfo command with the Protocol Extension flag to 0 No Has the tag replied to the GetSystemInfo Response? Yes. This is a low-density device (2) end MS30745V2 1. The RF host shall use the extended format for the addressing mode (see Table 7). 2. The RF host shall use the standard format for the addressing mode (see Table 7). 6/13 Doc ID 022825 Rev 3 AN4054 1.4 Comparison between low-density and high-density devices Memory mapping of ISO/IEC 15693 products Table 6 lists the key parameters of the memory mapping of LRix and M24LRx devices. Table 6. Memory mapping of LRix and M24LRx devices Device LRi1K LRi2K LRiS2K LRiS64K Memory size 1 Kbit 2 Kbits 2 Kbits 64 Kbits 4 Kbits 16 Kbits 64 Kbits Block size 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 0x1F 0x3F 0x3F 0x7FF 0x3F 0x1FF 0x7FF Number of blocks M24LR04E-R M24LR16E-R M24LR64x-R The ISO/IEC 15693 specification defines the read or write command with a block number coded on 1 byte. The high-density products of the ISO/IEC 15693 family require a block number coding on 2 bytes. It is the extended addressing mode. Table 7 lists the ISO/IEC 15693 products and their addressing mode. Table 7. Addressing mode of LRix and M24LRx devices Device LRi1K LRi2K LRiS2K LRiS64K M24LR04E-R Addressing mode standard standard standard extended standard M24LR16E-R M24LR64x-R extended extended As an example, the next two tables define the write single block command for low- and highdensity devices, and show the difference between the two density families. Table 8 describes the format of the write single block RF command for low-density products. The block number parameter is coded on 8 bits or 1 byte. Table 8. SOF Write single block request format for low-density products Request_ flags Write single block UID (1) Block number Data CRC16 8 bits 0x21 64 bits 8 bits 32 bits 16 bits EOF 1. Gray color means that the field is optional. Table 9 is the write single block RF command for high-density products. The block number parameter is coded on 16 bits or 2 bytes. Table 9. SOF Write single block request format for high-density products Request_ flags Write single block UID (1) Block number Data CRC16 8 bits 0x21 64 bits 16 bits 32 bits 16 bits EOF 1. Gray color means that the field is optional. Doc ID 022825 Rev 3 7/13 Comparison between low-density and high-density devices AN4054 Table 10 lists all RF commands for: ● low-density products which require using 1 byte to define the block number parameter, ● high-density products which require using 2 bytes to define the block number parameter. Table 10. RF command for low-density products using 1 byte and high-density products using 2 bytes Number of bytes to code the block number of the following RF command Low-density products High-density products Read single block 1 byte 2 bytes Write single block 1 byte 2 bytes Read multiple blocks 1 byte 2 bytes Get multiple security blocks status 1 byte 2 bytes Fast read single block 1 byte 2 bytes Fast read multiple blocks 1 byte 2 bytes 1.5 Request_flags management 1.5.1 Request_flags description Request_flags is the first byte of all RF commands and contains some information on the formats of the RF commands. The forth bit of this Request_flags is the Protocol Extension bit and it is used to define the number of bytes of the block number parameter. For more information about the Request_flags, please refer to ISO/IEC 15693 STMicroelectronics product datasheet. Table 11 shows an RF command frame for low-density products. The Protocol Extension flag is set to 0 for all RF commands. The block number is coded on 1 byte. Table 11. RF command frame for low-density products Block name Request_flags 0 Command code Data Block number Data 1 byte … 1 byte … Table 12 shows an RF read/write frame for high-density products. The Protocol Extension flag is set to 1 for read and write commands. In this case, the block number is coded on 2 bytes. Table 12. RF command with block number parameter frame for high-density products Block name Request flags 1 8/13 Command code Data Block number Data 1 byte … 2 bytes … Doc ID 022825 Rev 3 AN4054 1.5.2 Comparison between low-density and high-density devices Protocol Extension bit of Request_flags management Table 13 describes the Protocol Extension bit of the Request_flags byte according to the product type. Table 13. Request_flags functions according to the product types High-density product Function Low-density product LRiS64K, M24LR64x-R M24LR16E-R Read single block 0 1 1 Write single block 0 1 1 Read multiple blocks 0 1 1 Get system Info 0 1 - Get multiple blocks security status 0 1 1 Lock sector (1) 0 1 1 Fast read single block 0 0 0 Fast read multiple blocks 0 0 0 Other commands 0 0 0 1. This command is not available for LRi1k, LRi2k and LRiS2k products. Note: ‘0’ means that the flag is reset. ‘1’ means that the flag is set. ‘-’ means that it shall be managed by the application. Doc ID 022825 Rev 3 9/13 Acronym and notational conventions Appendix A A.1 AN4054 Acronym and notational conventions List of acronyms Table 14. List of acronyms Acronym A.2 Definition EEPROM Electrically-Erasable Programmable Read-Only Memory EOF End of frame I2C Inter-integrated circuit IC Integrated circuit IC ref Integrated circuit reference ISO International Organization for Standardization IEC International Electrotechnical Commission LRi Long range interface M24LR64-R Dual interface EEPROM (I2C and RF) with 64 Kbits memory size M24LR16-E Dual interface EEPROM (I2C and RF) with 16 Kbits memory size and energy harvesting feature RF Radio frequency RFID Radio frequency identification SOF Start of frame UID Unique identifier Notational conventions The following conventions and notations apply in this document unless otherwise stated. A.2.1 Binary number representation Binary numbers are represented by strings of digits 0 and 1, with the most significant bit (MSB) on the left, the least significant bit (LSB) on the right, and a "0b" prefix added at the beginning. Example: 0b11110101 A.2.2 Hexadecimal number representation Hexadecimal numbers are represented by numbers 0 to 9, characters A - F, and a "0x" prefix added at the beginning. The most significant byte (MSB) is shown on the left and the least significant byte (LSB) on the right. Example: 0xF5 10/13 Doc ID 022825 Rev 3 AN4054 A.2.3 Acronym and notational conventions Decimal number representation Decimal numbers are represented as is, without any trailing character. Example: 245 Doc ID 022825 Rev 3 11/13 Revision history AN4054 Revision history Table 15. 12/13 Document revision history Date Revision Changes 02-Mar-2012 1 Initial release. 22-Oct-2012 2 Added Section 1.3: How to identify the ISO/IEC 15693 products. 23-Nov-2012 3 Updated Figure 1: Flow diagram and added 2 notes below. Doc ID 022825 Rev 3 AN4054 Please Read Carefully: Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any time, without notice. All ST products are sold pursuant to ST’s terms and conditions of sale. Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no liability whatsoever relating to the choice, selection or use of the ST products and services described herein. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such third party products or services or any intellectual property contained therein. UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS EXPRESSLY APPROVED IN WRITING BY TWO AUTHORIZED ST REPRESENTATIVES, ST PRODUCTS ARE NOT RECOMMENDED, AUTHORIZED OR WARRANTED FOR USE IN MILITARY, 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 whatsoever, any liability of ST. ST and the ST logo are trademarks or registered trademarks of ST in various countries. Information in this document supersedes and replaces all information previously supplied. The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners. © 2012 STMicroelectronics - All rights reserved STMicroelectronics group of companies Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan Malaysia - Malta - Morocco - Philippines - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America www.st.com Doc ID 022825 Rev 3 13/13