SLOA208B November   2014  – March 2019 TRF7970A , TRF7970A

 

  1.   NFC card emulation using the TRF7970A
    1.     Trademarks
    2.     Terms, Definitions, and Symbols
    3. 1  Introduction
    4. 2  Card Emulation
      1. 2.1 Anticollision
        1. 2.1.1 Card Emulation Type A
        2. 2.1.2 Card Emulation Type B
      2. 2.2 Data Exchange
    5. 3  Configuration and Commands for Type 4 Tag Platforms
      1. 3.1 Overview of Type 4 Tag Configuration
        1. 3.1.1 Tag
        2. 3.1.2 Applications
        3. 3.1.3 Files
      2. 3.2 Firmware Structure
        1.       Example 1. Type 4 Tag Structures Within Example Firmware
        2. 3.2.1 tType4AppDS
        3. 3.2.2 tType4App
        4. 3.2.3 tType4File
        5. 3.2.4 Example Setup
          1.        Example 2. Example Setup of a Type 4 Tag Structure
      3. 3.3 File Structure
        1. 3.3.1 Capability Container
          1.        Example 3. Format of the Capability Container for a Tag With Two Files
        2. 3.3.2 Text RTD
          1.        Example 4. Example of a Text RTD Within an NDEF File
        3. 3.3.3 URI RTD
          1.        Example 5. Example of a URI RTD Within a Proprietary File
        4. 3.3.4 Smart Poster
        5. 3.3.5 V-Card
        6. 3.3.6 MIME
      4. 3.4 Available Type 4 Tag Commands
        1. 3.4.1 Frame Format
        2. 3.4.2 Select
        3. 3.4.3 Read Binary
        4. 3.4.4 Update Binary
      5. 3.5 Modifying Stored Tag Information
    6. 4  Hardware Description
      1. 4.1 LaunchPad™ Development Kit and BoosterPack™ Plug-in Module Setup
        1. 4.1.1 BoosterPack Plug-in Module: DLP-7970ABP
        2. 4.1.2 LaunchPad Development Kit: MSP-EXP430F5529LP
        3. 4.1.3 LaunchPad Development Kit: MSP-EXP432P401R
      2. 4.2 Bundle Available for Purchase
    7. 5  Card Emulation Firmware Example
      1. 5.1 Card Emulation APIs
      2. 5.2 Implementing a Card Emulation Sample Application
        1. 5.2.1 Low-Level Initialization
          1.        Example 6. MCU and TRF7970A Initialization Code Snippet
        2. 5.2.2 Card Emulation NFC Stack Setup
          1.        Example 7. Card Emulation Initialization Code
        3. 5.2.3 Emulation of Different RTDs
    8. 6  Quick Start Guide
    9. 7  Operational Overview
    10. 8  Card Emulation Interoperability Results
    11. 9  Conclusion
    12. 10 References
  2.   Revision History

5.2.3 Emulation of Different RTDs

The NFC_run function sets the transceiver to listening mode, and it waits for a polling command. When a reader/writer is presented, it goes through the protocol activation and anticollision procedures to establish a connection. After the tag is selected, the state machine is in the NFC_DATA_EXCHANGE_PROTOCOL state, and the firmware emulates a tag based on the selected RTD type (default is Text RTD).

When no NFC device is present, the firmware checks if button S1 or button S2 has been pressed. When button S1 is pressed, the firmware cycles between the emulation of five RTD types: Text, URI, Smart Poster, V-Card, and MIME. The MIME RTD is an example of a Bluetooth handover application.. When button S2 is pressed, the emulated RTD becomes a stored MIME image. The MIME image is 3597 bytes, and it can be overwritten by NFC enabled reader/writers to hold any NDEF-compatible RTD that fits within the 3597-byte size constraint. The RTD that is emulated on button S2 is restored to the original MIME image when the board is reset or power is cycled. Figure 13 shows the process.

fig20_toggling_rtd_types.pngFigure 13. Toggling Between RTD Types
千亿体育app官网登录(中国)官方网站IOS/安卓通用版/手机APP | 米乐app下载官网（中国）|ios|Android/通用版APP最新版 | 米乐|米乐·M6（中国大陆）官方网站 | 千亿体育登陆地址 | 华体会体育（中国）HTH·官方网站 | 千赢qy国际_全站最新版千赢qy国际V6.2.14安卓/IOS下载 | 18新利网v1.2.5|中国官方网站 | bob电竞真人（中国官网）安卓/ios苹果/电脑版【1.97.95版下载】 | 千亿体育app官方下载(中国)官方网站IOS/安卓/手机APP下载安装 |