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.3.3 Capability Container

The Capability Container is stored inside of a file that has a file identifier of 0xE103. The format for the Capability Container is specified in the NFC Forum Type 4 Tag Operation Specification 3.0. See Figure 21 for an example of a properly formatted CC.

fig21_Example_Type4_Capability.gifFigure 21. Example of Type 4 Capability Container Contents
  • CC Length – This 2 byte value is determined by the number of different files contained within the tag. The formula to calculate the CC Length is: [7 + (number of files × 8)].
  • Mapping Version – This value tells the reader the mapping specification used by the tag.
  • MLe – These 2 bytes indicate the maximum number of bytes that can be read from the tag by a single Read Binary command.
  • MLc – These 2 bytes indicate the maximum number of bytes that can be written to the tag by a single Write Binary command.
  • File Control TLV – The TLV blocks provide the reader with information about the tag data.
  • Tag Field (T) – This field contains the file type information of the TLV block. The following values may be used:
    • 0x04 – NDEF File
    • 0x05 – Proprietary File
    • 0x06 – Extended NDEF file
  • Length Field (L) – This field contains the length of the value field of the TLV block
  • Value Field (V) – This field contains the file ID, the maximum file size, and the read/write access conditions of the file.
    • File ID – Each file within the tag should have its own unique file ID number.
    • Max File Size – This value is not the size of the data itself, but the size of the maximum possible data that can be stored within the file.
    • Read Access (R) – Determines the read access properties of the file. A value of 0x00 means that the file has full read access. All other values are for limited read access.
    • Write Access (W) – Determines the write access properties of the file. The value 0x00 allows for full write privileges. The value 0xFF disables all write privileges and makes the file read-only. All other values are for limited write access.

There must be a File Control TLV for each different file contained within the tag. Therefore, if there are three different files, there must be three TLVs that correspond to the settings of each file.