SLOA227B October   2015  – March 2019 TRF7964A , TRF7964A , TRF7970A , TRF7970A

 

  1.   NFC/HF RFID reader/writer using the TRF7970A
    1.     Trademarks
    2. 1  Terms, Definitions, and Symbols
    3. 2  Introduction
    4. 3  Initial RF Collision
    5. 4  TRF7970A Register Settings
    6. 5  Reader/Writer Mode
      1. 5.1 Technology Activation Using the TRF7970A
        1. 5.1.1 ISO14443-3 Type A (Type 2 and Type 4A Tags)
          1. 5.1.1.1 Additional Tag Activation Commands for Type 4A Tags
        2. 5.1.2 ISO14443B-3 (Type 4B Tags)
          1. 5.1.2.1 Selection for Type 4B Tags
        3. 5.1.3 ISO18092 (Type 3 Tags)
        4. 5.1.4 ISO15693 (Type 5 Tags)
      2. 5.2 Tag Memory Format With NDEF Examples
        1. 5.2.1 Type 2 Tags
          1. 5.2.1.1 Layout
          2. 5.2.1.2 NDEF Format
            1. 5.2.1.2.1 Static Memory Structure
            2. 5.2.1.2.2 Dynamic Memory Structure
          3. 5.2.1.3 Capability Container
        2. 5.2.2 Type 3 Tags
          1. 5.2.2.1 Layout
          2. 5.2.2.2 NDEF Format
          3. 5.2.2.3 Attribute Information Block
        3. 5.2.3 Type 4 Tags
          1. 5.2.3.1 Layout
          2. 5.2.3.2 NDEF Format
          3. 5.2.3.3 Capability Container
        4. 5.2.4 Type 5 Tags
          1. 5.2.4.1 Layout
          2. 5.2.4.2 NDEF Format
          3. 5.2.4.3 Capability Container
    7. 6  Hardware Description
      1. 6.1 LaunchPad™ Development Kit and BoosterPack™ Plug-in Module Setup
        1. 6.1.1 BoosterPack Plug-in Module: DLP-7970ABP
        2. 6.1.2 LaunchPad Development Kit: MSP-EXP430F5529LP
        3. 6.1.3 LaunchPad Development Kit: MSP-EXP432P401R
      2. 6.2 Bundle Available for Purchase
    8. 7  Reader/Writer Firmware Example
      1. 7.1 Reader/Writer APIs
      2. 7.2 Implementing a Reader/Writer Sample Application
        1. 7.2.1 Low-Level Initialization
          1.        Example 1. MCU and TRF7970A Initialization Code Snippet
        2. 7.2.2 Reader/Writer NFC Stack Configuration
          1.        Example 2. Reader/Writer Stack Configuration Code Snippet
        3. 7.2.3 Activation
        4. 7.2.4 Reading and Writing Tags
    9. 8  Quick Start Guide
    10. 9  Operational Overview
    11. 10 Reader/Writer Interoperability Results
    12. 11 Conclusion
    13. 12 References
  2.   Revision History

5.2.2.3 Attribute Information Block

The format for the Attribute Information Block (see Figure 18) is specified in the NFC Forum Type 3 Tag Operation Specification. Version 1.2 was used to write this application report.

fig18_Type3_Attrib_Info_Block.gifFigure 18. Type 3 Tag Attribute Information Block Format
  • Mapping Version (Byte 0): For NDEF format it is required that this is set to a valid version number.
  • Max Blocks to Read (Byte 1): This value indicates how many blocks of data can be read from the tag at one time.
  • Max Blocks to Write (Byte 2): This value indicates how many blocks of data can be written to the tag at one time.
  • Blocks for NDEF Storage (Bytes 3 and 4): These bytes indicate the number of blocks available for NDEF content. Since each block is 16 bytes, this value should be multiplied by 16 to know how big the tag is in bytes.
  • Unused (Bytes 5-8): These bytes are not used, and typically are set to 0x00.
  • Write Flag (Byte 9): This flag is toggled when data is being written to the tag to indicate that the tag is currently in a write cycle.
  • NDEF Access Read/Write Flag (Byte 10): This flag is used to indicate the Read/Write privileges of the tag. A value of 0x00 means that the tag is Read Only, and a value of 0x01 means that the tag is Read/Write available.
  • Current NDEF Message Length (Bytes 11-13): These bytes indicate the size of the NDEF message that is stored in bytes. Since this value is stored in bytes, it must be divided by 16 to determine how many blocks must be read to receive the full NDEF message.
  • Checksum (Bytes 14-15): This is used to verify the validity of the data in the Attribute block, and it is calculated by adding together the values of Bytes 0 through 13. (modified when written to)