Sloa 192 A

Application Report
SLOA192A – April 2014 – Revised December 2016
NFC Active and Passive Peer-to-Peer Communication

Using the TRF7970A
Erick Macias, Josh Wyatt
ABSTRACT
Peer-to-peer (P2P) is one of the three modes supported by the TRF7970A. The Near Field
Communication (NFC) market is emerging into multiple fields including Medical, Consumer, Retail,
Industrial, Automotive, and Smart Grid. Peer-to-peer (P2P) is very common in these fields, because it
allows for a wireless virtual channel to be created between two devices. This application report describes
two NFC technologies, the NFC-F and NFC-A protocols, which are used to initiate the communication for
peer-to-peer active or passive modes. Furthermore, this application report explains how to implement an
application using active or passive P2P communication, supporting baud rates of 106 kbps, 212 kbps and
424 kbps on the TRF7970A transceiver.
Project collateral and source code discussed in this application report can be downloaded from
http://www.ti.com/lit/zip/sloa192.
SLOA192A – April 2014 – Revised December 2016 NFC Active and Passive Peer-to-Peer Communication Using the TRF7970A 1
Submit Documentation Feedback
Copyright © 2014–2016, Texas Instruments Incorporated
www.ti.com
Contents
1 Introduction ................................................................................................................... 3
2 Initial RF Collision............................................................................................................ 4
3 TRF7970A Register Settings ............................................................................................... 6
4 Peer-to-Peer at 106 kbps ................................................................................................... 8
5 Peer-to-Peer at 212 kbps and 424 kbps ................................................................................ 13
6 Hardware Description ...................................................................................................... 17
7 Passive and Active Peer-to-Peer Firmware Example ................................................................. 20
8 Quick Start Guide .......................................................................................................... 27
9 Operational Overview ...................................................................................................... 28
10 Peer-to-Peer Interoperability Results .................................................................................... 28
11 Conclusion .................................................................................................................. 31
12 References .................................................................................................................. 32
List of Figures
1 Peer-to-Peer Layers Including the PHY (TRF7970A) ................................................................... 3
2 RSSI Level Measurement Orientations ................................................................................... 4
3 Long Side RSSI Level Measurement ..................................................................................... 5
4 Short Side RSSI Level Measurement ..................................................................................... 5
5 Top-Side RSSI Level Measurement....................................................................................... 6
6 Frame Format for 106 kbps ................................................................................................ 8
7 Peer-to-Peer 106 kbps Flow Diagram .................................................................................... 8
8 Peer-to-Peer 106 kbps Initiator Anticollision for Active Communication ............................................ 10
9 Peer-to-Peer 106 kbps Initiator Anticollision for Passive Communication .......................................... 12
10 Frame Format for 212 kbps and 424 kbps .............................................................................. 13
11 Peer-to-Peer 212 kbps or 424 kbps Initiator Anticollision for Active Communication ............................. 13
12 Peer-to-Peer 212 kbps Active Initiator Anticollision.................................................................... 15
13 MSP430F5529 LaunchPad Development Kit and DLP-7970ABP BoosterPack Plug-in Module ................ 17
14 MSP432P401R LaunchPad Development Kit and DLP-7970ABP BoosterPack Plug-in Module ............... 18
15 MSP430F5529 USB Experimenter Board and TRF7970ATB ........................................................ 19
16 Peer-to-Peer NFC Stack Architecture .................................................................................. 20
17 TI NFC Tool GUI ........................................................................................................... 27
18 Peer-to-Peer Demo System Block Diagram ............................................................................ 28
List of Tables
1 NFC Enabled Devices Used to Test Peer-to-Peer ..................................................................... 4
2 TRF7970A Default Register Values After Receiving SOFT_INIT and IDLE Direct Commands................... 7
3 DLP-7970ABP BoosterPack Plug-in Module + MSP-EXP430F5529LP Hardware Connections ................ 21
4 TRF7970ATB + MSP-EXP430F5529 Experimenter Board Hardware Connections............................... 21
5 DLP-7970ABP + MSP-EXP432P401R LaunchPad Development Kit Hardware Connections ................... 22
6 Legend for the Result of the NFC Enabled Devices Tests ........................................................... 28
7 TRF7970A and Smart Phone Interoperability Results (Target Mode) .............................................. 29
8 TRF7970A and Smart Phone Interoperability Results (Initiator Mode) ............................................. 30
9 Data Throughput at 424 kbps for a 3.6kBytes NDEF.................................................................. 31
Trademarks
BoosterPack, LaunchPad are trademarks of Texas Instruments.
FeliCa is a trademark of Sony Corporation.
All other trademarks are the property of their respective owners.
2 NFC Active and Passive Peer-to-Peer Communication Using the TRF7970A SLOA192A – April 2014 – Revised December 2016
www.ti.com Introduction
1 Introduction
The TRF7970A supports three modes: Reader/Writer, Card Emulation, and Peer-to-Peer. This document
focuses on how to use the TRF7970A in peer-to-peer (P2P) active or passive. P2P requires two NFC-
enabled devices to communicate using technologies NFC-A or NFC-F at baud rates of 106 kbps (NFC-A),
212 kbps (NFC-F), or 424 kbps (NFC-F). The transceiver that is initially polling and initiates the
communication is the initiator. The transceiver that is initially listening is the target.
The initiator always generates the RF field for both active and passive communication modes. However,
the target generates its own RF field only for active mode (while the initiator's RF field is disabled), and
load modulates the initiator's RF field in passive mode. Once the technology selection for either mode has
been completed, the higher layers are the same (as shown in Figure 1). The NDEF Push Protocol (NPP)
was commonly used on Gingerbread Android NFC devices as the protocol to push NDEF messages from
one NFC device to another; however, the Simple NDEF Exchange Protocol (SNEP) has become the
standard on Ice Cream Sandwich Android NFC devices and onward.
NFC Data Exchange Format

(NDEF)
Simple NDEF NDEF Push

Exchange Protocol Protocol
(SNEP) (NPP)
Logical Link Control Protocol

(LLCP)
Data Exchange Protocol

(DEP)
NFC-A NFC-F
(106kbps) (212 and 424kbps)
NFC/RFID Transceiver TRF7970A
Figure 1. Peer-to-Peer Layers Including the PHY (TRF7970A)
A 16-bit and a 32-bit microcontroller are used to interface with the TRF7970A to demonstrate a reference
example of the Peer-to-Peer mode. The firmware supports flexible functions that let the user enable or
disable different Peer-to-Peer modes and technologies. The firmware supports both initiator and target for
active and passive communication at baud rates of 106 kbps, 212 kbps, and 424 kbps. Additionally, the
firmware can send and receive NDEF messages from NFC-enabled smart phones with SNEP.
Initial RF Collision www.ti.com
Table 1 lists the NFC-enabled devices used to validate the firmware.
Table 1. NFC Enabled Devices Used to Test Peer-to-Peer

Smartphone Model (Release Date) Operating System Kernel Version
Samsung Galaxy Nexus (Nov 2011) Android 4.3 3.0.72 Jun 7 2013
Samsung Galaxy S3 (T-Mobile) (May 2012) Android 4.0.4 3.031 Oct 31 2013
Asus Nexus 7 (July 2012) Android 4.4.2 3.1.10 Nov 20 2013
Samsung Galaxy Note 2 (Sept 2012) Android 4.3 3.0.31 Nov 19 2013
AU Arrows Fujitsu FJL21 (Oct 2012) Android 4.0.4 3.0.21 Oct 16 2012
Nokia Lumia 820 (Oct 2012) Windows 8 8.0.10211.204
HP Elite Tablet (Nov 2012) Windows 8 Windows 8 Pro
Samsung Nexus 10 (Nov 2012) Android 4.4.2 3.4.39 Nov 20 2013
Google Nexus 4 (Nov 2012) Android 4.3 3.4.0 Nov 20 2013
Samsung Galaxy S4 (April 2013) Android 4.3 3.4.0 Nov 16 2013
Hisense Sero 7 Pro (June 2013) Android 4.2.1 3.1.10
Asus Nexus 7 (July 2013) Android 4.4 3.4.0 Dec 11 2013
Google Nexus 5 (Oct 2013) Android 4.4 3.4.0 Nov 20 2013
2 Initial RF Collision
Various implementations of peer-to-peer exist today; these implementations may poll through commands
at different time intervals (500 ms, 300 ms, and so forth). To ensure that two NFC devices do not send
commands at the same time, an initial RF collision detection is required. The transceiver must check the
external Received Signal Strength Indicator (RSSI) value, which measures the strength of the
demodulated subcarrier signal, before enabling its own RF field. If the RSSI value is greater than 0x00,
the transceiver does not enable its RF field.
The relation between the 3-bit code and the external RF field strength (A/m) sensed by the antenna must
be determined by calculation or by experiments for each antenna design. The antenna Q-factor, coupling
factor between the two antennas, and connection to the RF input influence the result. Figure 3 through
Figure 5 provide the correlation of the free space distance between two unmodified TRF7970ATB modules
and the 3-bit external RSSI value in three directions. For more details on each orientation, see Figure 2.
One TRF7970A has its RF field at full power (+23 dBm), and the second TRF7970A is used to take RSSI
measurements across different distances.
Figure 2. RSSI Level Measurement Orientations
www.ti.com Initial RF Collision
Distance vs RSSI Levels ( Long Side)

9
Distance between antennas (cm) 8
7
6
5
4
3
2
1
0
0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07
RSSI Levels and Oscillator Status Register value (0x0F)
Figure 3. Long Side RSSI Level Measurement
Distance vs RSSI Levels ( Short Side)

9
Distance between antennas (cm)
8
7
6
5
4
3
2
1
0
0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07
Figure 4. Short Side RSSI Level Measurement
TRF7970A Register Settings www.ti.com
Distance vs RSSI Values ( Top Side)

9
Distance between atnennas (cm) 8

7
6
5
4
3
2
1
0
0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07
Figure 5. Top-Side RSSI Level Measurement
The initial RF collision can be accomplished by performing the following steps:

1. Write a 0x02/0x03 (3 VDC and 5 VDC operation) to the Chip Status Control register (0x00) disabling
the transmitter and enabling the receiver.
2. Send a Test External RF Direct command (0x19).
3. Delay 50 µs to allow transceiver to measure the field strength, and latch the value into the RSSI
register.
4. Read the RSSI Levels and Oscillator Status register (0x0F).
5. If the Active channel RSSI value (bits 2-0) is greater than 0, remain in target mode for a predetermined
n ms.
6. If the Active channel RSSI value (bits 2-0) is equal to 0, go into initiator or target mode for active or
passive communication.
3 TRF7970A Register Settings

After powering up the TRF7970A, the MCU must send SOFT_INIT (0x03) and IDLE (0x00) direct
commands to enable the passive target mode at 106 kbps. Table 2 shows the default value of registers
0x00 through 0x16 and 0x18 through 0x1C after the commands are issued. The table also shows the
registers that must be modified for both target and initiator modes.
The ISO Control (0x01) register is modified whenever the Peer-to-Peer technology or bit rate changes.
The Chip Status Control (0x00) register is modified after initialization and whenever the RF field is enabled
or disabled. The Modulator and SYS_CLK Control (0x09), RX Special Settings (0x0A), and Regulator and
I/O Control (0x0B) registers need to be modified only once, right after initialization. The NFC Low Field
Detection Level (0x16) register needs to be modified only for Target mode operation. The NFC Target
Detection Level (0x18) register must be modified after initialization for Target mode operation, and also for
Initiator mode operation based on the TRF7970A Silicon Errata.
www.ti.com TRF7970A Register Settings
Table 2. TRF7970A Default Register Values After Receiving SOFT_INIT and IDLE Direct Commands
Requires Modification
Address Register Value Notes
Initiator Target
0x00 Chip status control 0x01 5-V operation Yes Yes
0x01 ISO control 0x21 Passive target Yes Yes
Automatic Single Device Detection
0x02 ISO14443B TX options 0x00 No No
(SDD) disabled
0x03 ISO14443A high bit-rate options 0x00 See TRF7970A data sheet No No
0x04 TX timer setting, H-byte 0xC1 See TRF7970A data sheet No No
0x05 TX timer setting, L-byte 0xC1 See TRF7970A data sheet No No
0x06 TX pulse-length control 0x00 See TRF7970A data sheet No No
0x07 RX no response wait 0x0E See TRF7970A data sheet No No
0x08 RX wait time 0x07 See TRF7970A data sheet No No
27-MHz crystal enabled, SYS_CLK
0x09 Modulator and SYS_CLK control 0x91 Yes Yes
enabled, OOK (100%)
0x0A RX special setting 0x10 Band-pass 100 kHz to 1.5 MHz Yes Yes
0x0B Regulator and I/O control 0x87 Automatic VDD RF Yes Yes
0x0C IRQ status 0x00 See TRF7970A data sheet No No
Collision position and interrupt
0x0D 0x3E See TRF7970A data sheet No No
mask
0x0E Collision position 0x00 See TRF7970A data sheet No No
0x0F RSSI levels and oscillator status 0x40 See TRF7970A data sheet No No
0x10 Special function 0x00 See TRF7970A data sheet No No
0x11 Special function 0x00 See TRF7970A data sheet No No
0x12 RAM 0x00 See TRF7970A data sheet No No
0x13 RAM 0x00 See TRF7970A data sheet No No
0x14 Adjustable FIFO IRQ levels 0x00 See TRF7970A data sheet Optional Optional
0x15 Reserved 0x00 N/A No No
0x16 NFC low field detection level 0x00 See TRF7970A data sheet No Yes
0x18 NFC target detection level 0x00 See TRF7970A data sheet Yes Yes
0x19 NFC target protocol 0x00 See TRF7970A data sheet No No
0x1A Test 0x00 See TRF7970A data sheet No No
0x1B Test 0x00 See TRF7970A data sheet No No
0x1C FIFO status 0x00 See TRF7970A data sheet No No
Peer-to-Peer at 106 kbps www.ti.com
4 Peer-to-Peer at 106 kbps

The TRF7970A supports initiator and target P2P mode at 106 kbps (fc/128). When the transceiver is in
default mode [ISO mode (for more information, see the Direct Mode section of [1])] only the decoded data
is available to the MCU through the FIFO. The frame format for Data Exchange Protocol (DEP) packets at
106 kbps (shown in Figure 6) are based on the NFC-A technology specified in the NFCForum-TS-
DigitalProtocol-1.0. The format does not include the Start Byte for the passive anticollision of 106 kbps.
This section covers the register settings and anticollision sequence for both the active and passive peer-
to-peer modes at 106 kbps.
Start Byte Length

('F0') (8 bit) CMD1 CMD2 Byte 1 ... Byte n CRC
Legend
Handled by MCU during DEP
Handled by MCU
Handled by TRF7970A
Figure 6. Frame Format for 106 kbps
Legend
Start
Passive Target Active Communication
Passive Communication
Initial RF Collision No
Avoidance
RF field Yes Stay in Target mode Yes Packet

detected? for n mSec received? No
No No
Switch to Initiator Switch to Initiator No

Is packet Is packet
mode for Active mode for Passive
ATR_REQ? REQ_A?
Communication Communication
Yes Yes
Initiator SDD for Initiator SDD for Active Passive

active passive Target Target Anticollision
communication. communication. SDD. SDD.
Data Exchange
Protocol Data Exchange
De-Activation
Terminate
Communication
End
Figure 7. Peer-to-Peer 106 kbps Flow Diagram
www.ti.com Peer-to-Peer at 106 kbps
4.1 Active Communication

The TRF7970A ISO Control register (0x01) sets the modulation of the transceiver's RF field when is in
initiator mode or active NFC target. The NFC initiator and active target for baud rate of 106 kbps can be
achieved by initializing the transceiver as a NFC-A RFID reader (0x08). Each time the transceiver finishes
sending a command while being an initiator and active Target it must:
1. Turn off the field by modifying the ISO Control register → 0x21 (passive target).
2. Write to the RX Special Setting register (0x0A) → 0x30 (band-pass 450 kHz to 1.5 MHz and band-pass
100 kHz to 1.5 MHz).
3. Write to the Adjustable FIFO IRQ Levels register (0x14) → 0x0F (IRQ triggered when there are 96
bytes in FIFO during RX or 32 bytes during TX).
4.1.1 Initiator
Once the Initial RF Collision avoidance is completed and no RF field has been detected (see Figure 7),
the following registers must be modified each time before a DEP_REQ is sent to the active target (see
Figure 8). For more information, see Section 2.
1. Delay time specified in the technology specification (56 µs to 188 µs).
2. ISO Control register (0x01) → 0x08 (ISO1443A at 106 kbps, receive with CRC).
3. Delay 1 ms.
4. Send packet:
(a) Reset FIFO (0x0F) direct command.
(b) Transmission with (0x11) or without (0x10) CRC direct command.
(c) TX Length Byte 1 (0x1D) and TX Length Byte 2 (0x1E) registers.
(d) Write the command to the FIFO.
4.1.2 Target
After receiving commands from the initiator, the transceiver must follow the next steps each time before
responding to the initiator:
2. Perform Response RF Collision avoidance, and ensure no RF field is detected.
3. ISO Control register (0x01) → 0x08 (ISO14443A at 106 kbps, receive with CRC).
4. Delay 1 ms
5. Send packet:
(b) Transmission with (0x11) or without (0x10) CRC direct command.
(c) TX Length Byte 1 and 2 (0x1D and 0x1E) registers.
(d) Write the response to the FIFO.
Send ATR_REQ
at 106 kbps and turn
off RF Field
ATR_RES No Exit Anti-Collision

received? Layer
212 kbps or
424 kbps
supported?
Yes
No
Send PSL_REQ to
switch to higher bit
rate turn off RF Field
PSL_RES
received?
Yes
No No
Correct DID?
Yes
Write to ISO Control

Register ® 0x1A/
ox1B (212 kbps/
424 kbps)
Data Exchange
Protocol Layer
Figure 8. Peer-to-Peer 106 kbps Initiator Anticollision for Active Communication
4.2 Passive Communication

The TRF7970A ISO Control register (0x01) sets the modulation of the transceiver RF field when is in
initiator mode and the bit rate at which to load modulate when it is in target mode. Unlike active
communication, the target load modulates the initiator RF field instead of modulating its own field.
Furthermore, the anticollision procedure is different for passive communication at 106 kbps.
www.ti.com Peer-to-Peer at 106 kbps
4.2.1 Initiator
When the initial RF collision is completed and no RF field has been detected (as shown in Figure 7), the
following registers must be modified before and after the anticollision is completed as shown in Figure 9.
For more information, see Section 2.
1. ISO Control register (0x01) → 0x88 (ISO14443A 106 kbps, receive without CRC during anticollision,
before Select command)
or
ISO Control register (0x01) → 0x08 (ISO14443A 106 kbps, receive with CRC after anticollision is
completed).
2. Send packet:
(b) Transmission without (0x10, anticollision before Select command) or with (0x11, after anticollision is
completed) CRC direct command.
Unlike the active communication, no further RF collisions are required. The ISO control register needs to
be modified for the anticollision state to receive without CRC for the required commands. For more
information, see the ISO14443-3 specification. Once the anticollision is completed the ISO Control register
needs to be modified to receive with CRC. Step 2 must be used to send commands to the passive target.
4.2.2 Target
Initially the TRF7970A must be receiving without CRC. After receiving commands from the initiator, the
following registers must be modified before and after the anticollision is completed:
1. ISO Control register (0x01) → 0xA4 (ISO14443A 106 kbps, receive without CRC during anticollision,
before Select command)
or
ISO Control register (0x01) → 0x24 (ISO14443A 106 kbps, receive with CRC, after anticollision is
completed).
2. 2. Send packet:
(b) Transmission without (0x10, anticollision before Select command) or with (0x11, after anticollision is
completed) CRC direct command.
(c) c. TX Length Byte 1 and 2 (0x1D and 0x1E) registers.
The ISO control register needs to be modified for the anticollision state to receive without CRC for the
required commands. For more information, see the ISO14443-3 specification. Once the anticollision is
completed the ISO Control register needs to be modified to receive with CRC. Step 2 must be used to
send commands to the initiator.
Send SENS_REQ
at 106 kbps
SENS_RES No Exit Anti-Collision

received? Layer
n=1
Send SDD_REQ
(Cascade n)
SDD_RES No
Send SDD_REQ
(Cascade n)
NFCID1 not
complete
Increase Cascade SEL_RES
NFCID1 complete, and
not DEP compliant
(i.e. Type 2 or 4A Tag)
Send ATR_REG
Data Exchange
Layer
Figure 9. Peer-to-Peer 106 kbps Initiator Anticollision for Passive Communication
www.ti.com Peer-to-Peer at 212 kbps and 424 kbps
5 Peer-to-Peer at 212 kbps and 424 kbps

The TRF7970A supports initiator and target for NFC-F FeliCa™ at 212 kbps (fc/64) and 424 kbps (fc/32).
When the transceiver is in default mode [ISO mode (for more information, see the Direct Mode section of
[1])] the decoded data is available to the MCU through the FIFO. The frame format for 212 kbps and
424 kbps is shown in Figure 10. This section covers the register settings and anticollision sequence for
both the active and passive NFC-F peer-to-peer modes.
Preamble
Sync Length ...
(Minimum CMD1 CMD2 Byte 1 Byte n CRC
(16 bits 'B24D') (8 bit)
48 bits all 0's)
Legend
Handled by TRF7970A
Handled by MCU
Figure 10. Frame Format for 212 kbps and 424 kbps
Legend
Start
Passive Target Active Communication
Passive Communication
Initial RF Collision No
Avoidance
RF field Yes Stay in Target mode Yes Packet

detected? for n mSec received? No
No No Yes
Switch to Initiator Switch to Initiator No Is packet

Is packet
mode for Active mode for Passive SENSF_REQ?
ATR_REQ?
Communication Communication
Yes Yes
Initiator SDD for Initiator SDD for Active Passive

active passive Target Target Anticollision
communication. communication. SDD. SDD.
Data Exchange
Protocol Data Exchange
De-Activation
Terminate
Communication
End
Figure 11. Peer-to-Peer 212 kbps or 424 kbps Initiator Anticollision for Active Communication
Peer-to-Peer at 212 kbps and 424 kbps www.ti.com
5.1 Active Communication

The TRF7970A ISO Control register (0x01) sets the modulation of the transceiver RF field when is in
initiator mode and the bit rate to load modulate when it is in target mode. The NFC active and passive
initiator (bit 5 = 1 and bit 2 = 1) for baud rates of 212 kbps and 424 kbps, can be achieved by initializing
the transceiver as a NFC-F reader (Bit 5 = 1 and bits 4-0 = 0x12 (212 kbps) or 0x13 (424 kbps)). Each
time the transceiver finishes sending a command while being an initiator or target, the transceiver must:
1. Turn off the field by modifying the ISO Control register → 0x21 (passive target).
2. Write to RX Special Setting register (0x0A) → 0x80 (band-pass filter set for 110 kHz to 570 kHz)
3. Write to Adjustable FIFO IRQ Levels register (0x14) → 0x0F (IRQ triggered when there are 96 bytes in
FIFO during RX or 32 bytes during TX)
5.1.1 Initiator
Once the Initial RF Collision is completed and no RF field has been detected (as shown in Figure 11), the
following registers must be modified to initialize the anticollision (as shown in Figure 12). For more
information, see Section 2.
2. ISO Control register (0x01) → 0x32 (NFC-F at 212 kbps, receive with CRC).
3. Delay 1 ms
4. Send packet:
(b) Transmission with CRC direct command (0x11).
5.1.2 Target
After receiving commands from the initiator, the transceiver must follow the next steps each time before
responding to the initiator:
2. Perform Response RF Collision avoidance, and ensure no RF field is detected.
3. ISO Control register (0x01) → 0x32 (NFC-F at 212 kbps).
4. Delay 1 ms
5. Send packet:
NOTE: For more details on the NFC-F protocol, see [2], [3], [6], [7] and [8].
www.ti.com Peer-to-Peer at 212 kbps and 424 kbps
Send ATR_REQ
at 212 kbps and
turn off RF field
ATR_RES No Exit Anti-Collision

received? Layer
424 kbps
supported?
Yes
No
Send PSL_REQ and

turn off RF Field
PSL_RES
received?
Yes
No No
Correct DID?
Yes
Write to ISO Control

Register ® 0x33
(NFC-F at 424 kbps)
Data Exchange
Protocol Layer
Figure 12. Peer-to-Peer 212 kbps Active Initiator Anticollision
5.2 Passive Communication

The TRF7970A ISO Control register (0x01) sets the modulation of the transceiver RF field when it is in
initiator mode and the bit rate at which to load modulate the initiator's field when it is in target mode.
Unlike active communication, the target load modulates the initiator RF field instead of modulating its own
field. Furthermore, the anticollision procedure is different for passive communication and active
communication.
Peer-to-Peer at 212 kbps and 424 kbps www.ti.com
5.2.1 Initiator
Once the Initial RF Collision is completed and no RF field has been detected (as shown in Figure 11), the
following registers must be modified before the anticollision. For more information, see Section 2).
2. Send packet:
Step 2 must be used to send commands to the passive target.
5.2.2 Target
After receiving commands from the initiator, the transceiver must be modified when the anticollision
process is started:
2. Send packet:
Step 2 must be used to send commands to the passive target.
www.ti.com Hardware Description
6 Hardware Description
6.1 LaunchPad™ Development Kit and BoosterPack™ Plug-in Module Setup
6.1.1 BoosterPack Plug-in Module: DLP-7970ABP

The third party provider DLP Design NFC/RFID BoosterPack™ plug-in module (DLP-7970ABP) is an add-
on board designed to fit all of TI's MCU LaunchPad™ development kits. This BoosterPack plug-in module
allows the software application developer to get familiar with the functionalities of TRF7970A multi-protocol
fully integrated 13.56-MHz NFC/HF RFID IC on their TI embedded microcontroller platform of choice
without having to worry about designing the RF section (see Figure 13 and Figure 14).
The TRF7970A device is an integrated analog front end and data-framing device for a 13.56-MHz NFC/HF
RFID system. Built-in programming options make the device suitable for a wide range of applications for
proximity and vicinity identification systems. The device can perform in one of three modes: Reader/Writer,
Peer-to-Peer, or Card Emulation mode. Built-in user-configurable programming registers allows fine tuning
of various reader parameters as needed.
Link for purchase: https://store.ti.com/dlp-7970abp.aspx
6.1.2 LaunchPad Development Kit: MSP-EXP430F5529LP

The MSP-EXP430F5529LP LaunchPad development kit is an easy-to-use evaluation module for the
MSP430F5529 USB microcontroller. It contains everything needed to start developing, including on-board
emulation for programming and debugging, as well as on-board buttons and LEDs for quickly adding a
simple user interface. Rapid prototyping is a snap, thanks to 40-pin access headers and a wide range of
BoosterPack plug-in modules. This enables technologies such as wireless, display drivers, temperature
sensing, and much more (see Figure 13).
Link for purchase: https://store.ti.com/msp-exp430f5529lp.aspx
Figure 13. MSP430F5529 LaunchPad Development Kit and DLP-7970ABP BoosterPack Plug-in Module
Hardware Description www.ti.com
6.1.3 LaunchPad Development Kit: MSP-EXP432P401R

The MSP432P401R LaunchPad development kit enables you to develop high-performance applications
that benefit from low-power operation. It features the MSP432P401R – which includes a 48-MHz ARM
Cortex M4F, 95-µA/MHz active power, and 850-nA RTC operation, a 14-bit 1-MSPS differential SAR ADC,
and an AES256 accelerator.
This LaunchPad development kit includes an on-board emulator with EnergyTrace+ Technology, which
means you can program and debug your projects without the need for additional tools, while also
measuring total system energy consumption (see Figure 14).
Link for purchase: https://store.ti.com/msp-exp432p401r.aspx
Figure 14. MSP432P401R LaunchPad Development Kit and DLP-7970ABP BoosterPack Plug-in Module
6.2 Experimenter Board Setup
6.2.1 MSP-EXP430F5529
The MSP430F5529 Experimenter Board (MSP-EXP430F5529) is a development platform for the
MSP430F5529 device, from the latest generation of MSP430 devices with integrated USB. The board is
compatible with many TI low-power RF wireless evaluation modules such as the TRF7970ATB module.
The Experimenter Board helps designers quickly learn and develop using the new F55xx MCUs, which
provide the industry's lowest active power consumption, integrated USB, and more memory and leading
integration for other applications such as energy harvesting, wireless sensing and automatic metering
infrastructure (AMI) (see Figure 15).
Link for purchase: https://store.ti.com/MSP-EXP430F5529-MSP430F5529-USB-Experimenters-Board-
P2413.aspx
www.ti.com Hardware Description
6.3 TRF7970ATB Module

The TRF7970ATB Evaluation Module allows the software application developer to get familiar with the
functionalities of TRF7970A Multi-Protocol Fully Integrated 13.56-MHz NFC/ HF RFID IC while allowing
the freedom to develop with the Texas Instruments MCU of their choosing. The MSP-EXP430F5529
Experimenter Board is one such development platform. Alternatively, any other TI embedded
microcontroller platform with the EM socket headers populated can be used.
The TRF7970ATB is hardwired for SPI communications, supports slave select and TRF7970A Direct
Mode 2 (default), Direct Mode 1, and Direct Mode 0 operations. The user also has access to and full
control over the TRF7970A EN2 and EN lines, allowing for design and development of ultra-low-power
high-frequency (HF) RFID/NFC systems. The module has an onboard boost converter (TPS61222DCKT)
that boosts 3.3 VDC to 5 VDC out to TRF7970A IC for +23 dBm (full transmitter power out) operations
(see Figure 15).
Link for purchase: https://store.ti.com/TRF7970ATB-TRF7970ATB-P4618.aspx
Figure 15. MSP430F5529 USB Experimenter Board and TRF7970ATB
6.4 Available Bundles for Purchase

The TI Store also has bundles available for purchase for each evaluation kit setup.
MSP-EXP430F5529LP + DLP-7970ABP: https://store.ti.com/nfclink-bndl.aspx
MSP-EXP432P401R + DLP-7970ABP: https://store.ti.com/nfclink-bndl-msp432.aspx
MSP-EXP430F5529 + TRF7970ATB: https://store.ti.com/NFCLink-Evalution-Kit-P4617.aspx
Passive and Active Peer-to-Peer Firmware Example www.ti.com
7 Passive and Active Peer-to-Peer Firmware Example

This section explains which APIs are used by the NFC/RFID layer (see Figure 16) to initialize and handle
the peer-to-peer communication. Furthermore, it covers how to implement a sample peer-to-peer
application, which can send and receive an NDEF message to and from an NFC-enabled device.
The firmware example that contains the Peer-to-Peer APIs discussed in this document can be
downloaded from http://www.ti.com/lit/zip/sloa192.
As downloaded, the firmware example includes the full TI NFC stack which supports Peer-to-Peer, Card
Emulation, and Reader/Writer modes. For applications that do not require all NFC operating modes, there
are configuration options available to reduce the NFC stack memory footprint (only compiling required
operating modes). These configurations can be made by modifying the #define statements within the
nfc_config.h file, located at [Install Path]\nfclink\Source\headers.
Figure 16. Peer-to-Peer NFC Stack Architecture
7.1 Peer-to-Peer APIs

For details on all available APIs used in the provided example firmware for NFC peer-to-peer mode, see
the NFCLink Standalone Software Library API Guide included in the install package. The guide is located
in [Install Path]\doc.
The NFCLink Standalone Software Library API Guide describes the flow of the software stack, all APIs
that are available for NFC peer-to-peer functionality, and each function to help users with developing
custom NFC peer-to-peer applications.
www.ti.com Passive and Active Peer-to-Peer Firmware Example
7.2 Implementing a Peer-to-Peer Sample Application

This section explains how to implement a peer-to-peer sample application that uses buttons S1 and S2 on
the MSP430F5529 LaunchPad development kit to send different NDEF messages to an NFC-enabled
device. Table 3 and Table 4 lists the connections between the MSP430F5529 and the TRF7970A for the
different MSP430F5529 evaluation platforms. Table 5 shows the connections between the MSP432P401R
and the TRF7970A for the MSP432P401R LaunchPad development kit.
Table 3. DLP-7970ABP BoosterPack Plug-in Module +

MSP-EXP430F5529LP Hardware Connections
MSP430F5529 LaunchPad
DLP-7970ABP Pins
Development Kit Pins
TRF7970A EN1 P4.1
TRF7970A IRQ P2.2 (1)
MOSI P3.0
MISO P3.1
CLK P3.2
Slave Select P4.2
I/O_2 P6.6 (2)
I/O_3 P2.0 (2)
I/O_5 P1.6 (2)
(1)
IRQ defaults to P2.2 for DLP-7970ABP v4.5 and newer (see the DLP-
7970ABP Hardware Update Overview).
(2)
Pin is only needed for using Special Direct Mode
Table 4. TRF7970ATB + MSP-EXP430F5529

Experimenter Board Hardware Connections
TRF7970ATB Pins MSP430F5529 EXP Board Pins
TRF7970A EN1 P2.3
TRF7970A IRQ P2.0 (1)
MOSI P3.0
MISO P3.1
CLK P3.2
Slave Select P2.6
MOD P2.1
ASK/OOK P4.7
(1)
Requires a jumper to be placed between P2.0 and P4.0 on the
Experimenter Board.
Table 5. DLP-7970ABP + MSP-EXP432P401R

LaunchPad Development Kit Hardware Connections
MSP432P401R LaunchPad
TRF7970ATB Pins
Development Kit Pins
TRF7970A EN1 P6.2
TRF7970A IRQ P3.0 (1)
MOSI P1.6
MISO P1.7
CLK P1.5
Slave Select P6.5
I/O_2 P4.3 (2)
I/O_3 P2.5 (2)
I/O_5 P4.1 (2)
(1)
IRQ defaults to P3.0 for DLP-7970ABP v4.5 and newer (see the DLP-
7970ABP Hardware Update Overview ).
(2)
Pin is needed only for using Special Direct Mode.
7.2.1 Low-Level Initialization

For the low-level initialization, the MCU is initialized in MCU_init() by setting the MSP430F5529 main clock
frequency to 25 MHz. The TRF7970A hardware connections and the MSP430F5529 SPI module (SPI
clock running at 4 MHz - minimum recommended is 2MHz) is initialized in TRF79x0_init(). The local
variables are needed for transmit and receive and the peer-to-peer stack initialization. The Buttons_init
function set the GPIO direction to inputs and the Buttons_interruptEnable() enable the interrupt for buttons
S1 and S2.
#include "msp430.h"
#include "nfc_controller.h"
#include "ndef_image.h"
#include "lp_buttons.h"
uint16_t g_ui16ListenTime;
t_sNfcP2PMode g_sP2PSupportedModes;
t_sNfcP2PCommBitrate g_sP2PSupportedTargetBitrates;
t_sNfcP2PCommBitrate g_sP2PSupportedInitiatorBitrates;
t_sNfcDEP_P2PSetup g_sP2PSetupOptions;
uint8_t g_ui8NfcDepInitiatorDID;
void main(void)
{
tNfcState eTempNFCState;
tNfcState eCurrentNFCState;
uint32_t ui32PacketRemaining;
uint8_t ui8TXBytes;
uint16_t ui16TxIndex;
uint32_t ui32PacketLength;
uint8_t * pui8NdefPointer;
uint8_t ui8FragmentSize;
// Peer to peer RX Status

tNfcP2PRxStatus sP2PRxStatus;
t_sNfcP2PMode sP2PMode;
t_sNfcP2PCommBitrate sP2PBitrate;
// Bytes Received from Peer to Peer

uint16_t ui16BytesReceived = 0x00;
// Initialize MCU
MCU_init();
//Enable interrupts globally
__enable_interrupt();
// Initialize TRF7970
TRF79x0_init();
// Initialize S1 and S2 buttons

Buttons_init(BUTTON_ALL);
Buttons_interruptEnable(BUTTON_ALL);
// Initialize TRF7970A Idle Mode

TRF79x0_idleMode();
// Initialize the NFC Controller

NFC_init();
// This function will configure all the settings for each protocol
NFC_configuration();
// Initialize IDs for NFC-A, NFC-B and NFC-F

NFC_initIDs();
7.2.2 Peer-to-Peer NFC Stack Setup

The peer-to-peer NFC stack is initialized by setting the bInitiatorEnabled or bTargetEnabled bits inside the
sP2PSupportedModes variable. If both bInitiatorEnabled and bTargetEnabled are set, the stack operates
in a switching mechanism similar to how NFC enabled handsets operate when NFC is enabled. For this
demo, all passive target and initiator bitrates are enabled.
// Enable Peer 2 Peer Supported Modes
g_sP2PSupportedModes.bits.bTargetEnabled = 1;
g_sP2PSupportedModes.bits.bInitiatorEnabled = 1;
// Set P2P Supported Bit Rates - Target mode

g_sP2PSupportedTargetBitrates.bits.bPassive106kbps = 1;
g_sP2PSupportedTargetBitrates.bits.bActive106kbps = 0;
// Set P2P Supported Bit Rates - Initiator mode

g_sP2PSupportedInitiatorBitrates.bits.bPassive106kbps = 1;
g_sP2PSupportedInitiatorBitrates.bits.bActive106kbps = 0;
// Configure Peer 2 Peer functions for the correct modes and communication bitrates
NFC_P2P_configure(g_sP2PSupportedModes,g_sP2PSupportedTargetBitrates,g_sP2PSupportedInitiatorBitra
tes);
7.2.3 Sending NDEF Packets

The NFC_run switches between target and initiator until an NFC-enabled device is presented to the
TRF7970A RF field. Once the peer-to-peer communication is established and eTempNFCState is
NFC_DATA_EXCHANGE_PROTOCOL, the firmware checks whether button S1 or button S2 has been
pressed. When button S1 is pressed, a text RTD is queued to the SNEP TX buffer. When button S2 is
pressed, a MIME RTD is queued to the SNEP TX buffer. When the size of the NDEF packet is smaller
than the SNEP queue, the NFC_P2P_sendNdefPacket() is only executed once because the number of
remaining bytes return by the function would be 0. When the size of the NDEF packet is larger than the
SNEP queue, the NFC_P2P_sendNdefPacket() continues to queue fragments of the complete packet until
the number of remaining bytes is 0.
eTempNFCState = NFC_run();
if(eTempNFCState == NFC_DATA_EXCHANGE_PROTOCOL)
{
else if(NFC_P2P_getModeStatus(&sP2PMode,&sP2PBitrate))
{
// Check for button input
if ((buttonsPressed & BUTTON_S1) && (buttonDebounce == 2))
{
ui16TxIndex = 0x00;
buttonDebounce = 0x00;
// Total Length of the packet.
ui32PacketLength = 46;
ui32PacketRemaining = ui32PacketLength;
// Send Text String
pui8NdefPointer = (uint8_t *) (pui8NfcPoweredByTexasInstruments+2);
if(ui32PacketRemaining < LLCP_MIU)
{
ui8FragmentSize = (uint8_t) ui32PacketRemaining;
}
else
{
ui8FragmentSize = LLCP_MIU;
}
ui8TXBytes =
NFC_P2P_sendNdefPacket(pui8NdefPointer,true,ui8FragmentSize,ui32PacketLength);
if(ui8TXBytes)
{
ui32PacketRemaining = ui32PacketRemaining - (uint16_t) (ui8TXBytes);
ui16TxIndex = ui16TxIndex + (uint16_t) ui8TXBytes;
// Toggle TX LED
NFC_TX_LED_POUT ^= NFC_TX_LED_BIT;
}
}
else if((buttonsPressed & BUTTON_S2) && (buttonDebounce == 2))
{
ui16TxIndex = 0x00;
// Total Length of the packet.
ui32PacketLength = 3597;
ui32PacketRemaining = ui32PacketLength;
// Send TI Logo
pui8NdefPointer = (uint8_t *) (pui8TiLogo + 2);
{
}
else
{
}
ui8TXBytes =
NFC_P2P_sendNdefPacket(pui8NdefPointer,true,ui8FragmentSize,ui32PacketLength);
if(ui8TXBytes)
{
// Toggle TX LED
}
}
else if(ui32PacketRemaining > 0)
{
{
}
else
{
}
ui8TXBytes = NFC_P2P_sendNdefPacket((uint8_t *)
(pui8NdefPointer+ui16TxIndex),false,ui8FragmentSize,(uint32_t) ui32PacketLength);
if(ui8TXBytes)
{
// Toggle TX LED
}
}
else if(buttonDebounce == 0x00)
{
// Enable the button debounce.
}
else if (ui32PacketRemaining == 0)
{
// Clear TX LED
NFC_TX_LED_POUT &= ~NFC_TX_LED_BIT;
}
}
}
7.2.4 Receiving NDEF Packets

The NFC_run function switches between target and initiator until an NFC-enabled device is presented to
the TRF7970A RF field. Once the peer-to-peer communication is established and eTempNFCState is
NFC_DATA_EXCHANGE_PROTOCOL, the firmware checks the RX status with
NFC_P2P_getReceiveState() . When a packet is received, the sP2PRxStatus.sDataReceivedStatus will
be RECEIVED_FIRST_FRAGMENT, or RECEIVED_N_FRAGMENT, or
RECEIVED_FRAGMENT_COMPLETED. When the first fragment is received from another NFC device if
the packet is incomplete, the sP2PRxStatus.sDataReceivedStatus will be
RECEIVED_FIRST_FRAGMENT. When the first fragment is received from another NFC device if the
packet is complete, the sP2PRxStatus.sDataReceivedStatus will be
RECEIVED_FRAGMENT_COMPLETED. When the packet is broken into multiple fragments due to the
total size being larger than the SNEP queue the sP2PRxStatus.sDataReceivedStatus will be
RECEIVED_N_FRAGMENT until the last fragment is received. When the last fragment is received, the
sP2PRxStatus.sDataReceivedStatus will be RECEIVED_FRAGMENT_COMPLETED.
eTempNFCState = NFC_run();
if(eTempNFCState == NFC_DATA_EXCHANGE_PROTOCOL)
{
else if(NFC_P2P_getModeStatus(&sP2PMode,&sP2PBitrate))
{
//
// Read the receive status structure -
check if there is a received packet from the Target
//
sP2PRxStatus = NFC_P2P_getReceiveState();
if(sP2PRxStatus.sDataReceivedStatus != RECEIVED_NO_FRAGMENT)
{
ui16BytesReceived = sP2PRxStatus.ui16DataReceivedLength + ui16BytesReceived;
// Check if the last packet was received completely

if((uint16_t) sP2PRxStatus.ui32PacketSize == ui16BytesReceived)
{
// Reset Bytes received
ui16BytesReceived = 0;
}
}
}
}
www.ti.com Quick Start Guide
8 Quick Start Guide

The NFCLink Standalone Getting Started Guide provides complete details of how to get started with the
provided example firmware and the MSP-EXP430F5529LP and DLP-7970ABP.
This guide describes how to load the example firmware to TI evaluation boards and explains the features
of the TI NFC Tool GUI (see Figure 17), which is installed with the firmware package.
The TI NFC Tool allows for quick configuration of the different NFC modes and provides an inferface to
send and receive data with NFC-enabled devices.
Figure 17. TI NFC Tool GUI
Operational Overview www.ti.com
9 Operational Overview
The peer-to-peer demo on the MSP430F5529 has two modes. The first mode is a stand-alone mode
where both initiator and target are enabled for passive supporting 106 kbps, 212 kbps and 424 kbps. The
firmware sends polling commands for NFC-A Passive at 106 kbps and NFC-F passive at 212 kbps each
time the initiator mode is enabled. If all the polling commands timeout, the peer-to-peer stack switches the
mode to target mode. In target mode, the firmware waits for a technology to be activated for 500 ms. If no
technology is activated during target mode, the firmware switches the mode to initiator mode. When a
connection is established with an NFC-enabled device, press the button S1 to send a Text RTD or press
the button S2 to send a MIME RTD (TI Logo).
The second mode requires a host (PC) to run the TI NFC Tool and connect to the MSP430F5529 through
the USB CDC. Figure 18 shows the system block diagram. When the GUI is connected to the
MSP430F5529, pressing the buttons S1 or S2 will not send an NDEF as it previously did in stand-alone
mode. The GUI allows you to select which modes to enable and disable. Once a connection is established
with an NFC-enabled device, the GUI switches to the peer-to-peer tab, which allows you to send a
modifiable Text or URI RTD.
Figure 18. Peer-to-Peer Demo System Block Diagram
10 Peer-to-Peer Interoperability Results

This section covers the results of the interoperability between the existing TRF7970A Peer-to-Peer stack
and the list of NFC-enabled devices mentioned earlier in the application report (see Table 1). Use the
legend shown in Table 6 for the Target results in Table 7 and for the Initiator results in Table 8.
Based on the results of the interoperability tests, TI recommends using Passive Peer-to-Peer modes as
they have proven to be more consistent, reliable, and robust than Active Peer-to-Peer modes.
Table 6. Legend for the Result of the NFC Enabled Devices Tests
Legend
Success
The P2P communication only works if the TRF7970A is polling for both NFC-A and NFC-F. The field
1
cannot be disabled between passive commands.
2 The P2P communication only works when the initiator sends a PSL_REQ from 106 to 212 or 424 kbps.
3 Requires both Initiator Active Polling commands for 106 kbps and 212 kbps to work properly.
4 Difficult to establish an active P2P link.
1 The device does not support NFC DEP
NRP No Reply to Polling command - The target does not reply to the polling command.
NRT No Reply to Target response - The initiator does not reply to the polling response command.
Not Applicable
www.ti.com Peer-to-Peer Interoperability Results
Table 7 includes the interoperability results for test cases where the TRF7970A is a passive and active
target. The results show that legacy NFC-enabled devices did not support sending a PSL REQ, instead
they would poll for 106 kbps, 212 kbps, and 424 kbps separately. The newer devices go through the
anticollision loop and immediately send a PSL_REQ up to 424 kbps for both active and passive
communication at 106 kbps or 212 kbps up to 424 kbps. The smartphone devices are listed with model
and release date to illustrate that the interoperability across all target modes is better for newer NFC-
enabled devices. The TRF7970A peer-to-peer stack is replying to incoming commands SENS_REQ
(polling at 106 kbps), and ATR_REQ (active polling at 106 kbps, or 212 kbps, or 424 kbps); however, no
further commands are received from the initiator.
Table 7. TRF7970A and Smart Phone Interoperability Results (Target Mode)

Test With Firmware 1.00.35 TRF7970A Modes and Bitrates (kbps)
Target (Passive Target (Active TRF7970A
Smartphone Model (Release Date) Communication) Communication) Received
106 212 424 106 212 424 PSL REQ
Samsung Galaxy Nexus (Nov 2011) No
Blackberry Curve 9360 (August 2011) NRT Yes
Samsung Galaxy S3 (T-Mobile) (May 2012) No
Asus Nexus 7 (July 2012) No
Samsung Galaxy Note 2 (Sept 2012) No
AU Arrows Fujitsu FJL21 (Oct 2012) No
Samsung S3 Mini (October 2012) NRT NRT No
Nokia Lumia 820 (Oct 2012) No
HP Elite Tablet (Nov 2012) NRT No
Samsung Nexus 10 (Nov 2012) Yes
Google Nexus 4 (Nov 2012) Yes
Samsung Galaxy S4 T-Mobile (April 2013) No
Samsung Galaxy S4 (April 2013) Yes
Hisense Sero 7 Pro (June 2013) Yes
Asus Nexus 7 (July 2013) NRT Yes
Samsung Galaxy Note 3 ( Sept. 2013) NRT No
Google Nexus 5 (Oct 2013) Yes
Peer-to-Peer Interoperability Results www.ti.com
Table 8 includes the interoperability results for test cases where the TRF7970A is a passive and active
initiator. The smartphone devices are listed with model and release date included to illustrate that the
interoperability across all initiator modes is better for newer NFC-enabled devices. The TRF7970A peer-
to-peer stack does not get a response from the devices that are failing for the SENS_REQ (polling at 106
kbps), and ATR_REQ (active polling at 106 kbps or 212 kbps). The peer-to-peer stack does not support
incrementing from 106 kbps → 212 kbps or 424 kbps for both active and passive communication.
Table 8. TRF7970A and Smart Phone Interoperability Results (Initiator Mode)

Test With Firmware 1.00.35 TRF7970A Modes and Bitrates (kbps)
Initiator (Passive Communication) Initiator (Active Communication)
Smartphone Model (Release Date)
106 212 424 106 212 424
Samsung Galaxy Nexus (Nov 2011) 1
Blackberry Curve 9360 (August 2011) NRP NRP NRP
Samsung Galaxy S3 (T-Mobile) (May 2012) NRP 1 1 NRP NRP NRP
Asus Nexus 7 (July 2012) NRP 1 1 2 2
Samsung Galaxy Note 2 (Sept 2012) NRP 1 1 NRP NRP NRP
AU Arrows Fujitsu FJL21 (Oct 2012) 2 2 NRP NRP NRP
Samsung S3 Mini (October 2012) NRP NRP
Nokia Lumia 820 (Oct 2012) NRP 1 1 2 2
HP Elite Tablet (Nov 2012) NRP
Samsung Nexus 10 (Nov 2012) 2 2
Google Nexus 4 (Nov 2012) NRP 3 3
Samsung Galaxy S4 T-Mobile (April 2013) NRP NRP
Samsung Galaxy S4 ATT (April 2013) NRP NRP 3 3
Hisense Sero 7 Pro (June 2013) NRP 4 4 4
Asus Nexus 7 (July 2013)
Samsung Galaxy Note 3 ( Sept. 2013) 2 2 NRP NRP NRP
Google Nexus 5 (Oct 2013)
www.ti.com Conclusion
Table 9 shows the results for the time it took to send a 3.6kB file from the TRF7970A to the NFC-enabled
devices listed. The NFC-enabled devices were the initiators (passive communication) at 424 kbps. The
start edge was measured from the Transmit Complete Interrupt of the LLCP CONNECT PDU (sent from
the TRF7970A to the NFC-enabled device). The end edge was measured at the RX Complete interrupt of
the SNEP SUCCESS response. The results show that the throughput is highly related to the performance
of the processor in the NFC-enabled device. The highest throughput was measured with the Nexus 10,
which has the fastest processor.
Table 9. Data Throughput at 424 kbps for a 3.6kBytes NDEF

Test With Firmware 1.00.23
Send 3.6kB File Throughput at 424 kbps
Smartphone Model (Release Date)
(seconds) (kBps)
Samsung Galaxy Nexus (Nov 2011) 0.7569 4.76
Samsung Galaxy S3 (T-Mobile) (May 2012) 1.8567 1.94
Asus Nexus 7 (July 2012) 1.339 2.69
Samsung Galaxy Note 2 (Sept 2012) 0.8087 4.45
AU Arrows Fujitsu FJL21 (Oct 2012) 0.3547 10.15
Nokia Lumia 820 (Oct 2012) 0.5099 7.06
HP Elite Tablet (Nov 2012) 0.5541 6.5
Samsung Nexus 10 (Nov 2012) 0.163 22.09
Google Nexus 4 (Nov 2012) 0.2557 14.08
Samsung Galaxy S4 (April 2013) 0.887 4.06
Hisense Sero 7 Pro (June 2013) 0.2981 12.08
Asus Nexus 7 (July 2013) 0.2964 12.15
Google Nexus 5 (Oct 2013) 0.5295 6.8
11 Conclusion
Peer-to-peer is one of three modes supported by the TRF7970A transceiver. The existing P2P NFC stack
supports active and passive communication for both initiator and target at 106 kbps, 212 kbps, and 424
kbps. The transceiver that is initially polling and initiates the communication is the initiator. The transceiver
that is initially listening is the target. The initiator always generates the RF field for both active and passive
communication modes. However, the target generates its own RF field for active communication and load
modulates the initiator's RF field for passive communication. To avoid two devices enabling their RF field
at the same time, one must perform an initial RF collision (see Section 2) before enabling its own RF field.
The P2P demo has two modes: a stand-alone mode and a TI NFC Tool GUI mode. The stand-alone mode
is the only way to test sending a large NDEF packet (3.6kB), however, using the TI NFC Tool GUI allows
you to modify the default peer-to-peer modes enabled at power up. Furthermore, the GUI can be used to
test for throughput rates when NDEF packets (larger than 1000 bytes) are sent from an NFC-enabled
device to the TRF7970A transceiver.
Based on the tests executed with NFC-enabled devices in Table 1, the newer NFC-enabled devices
interoperability with the TRF7970A is better. For legacy devices, the active communication may not be
supported at all for either target or initiator at all bit rates. For newer devices, active communication has
mixed results in terms of support, reliability and robust connections. Therefore, it is recommended to use
passive communication over active communication.
As downloaded, the firmware example includes the full TI NFC stack which supports Peer-to-Peer, Card
Emulation, and Reader/Writer modes. For applications that do not require all NFC operating modes, there
are configuration options available to reduce the NFC stack memory footprint (only compiling required
operating modes). These configurations can be made by modifying the #define statements within the
nfc_config.h file, located at [Install Path]\nfclink\Source\headers.
For more information about NFC Card Emulation operation, see NFC Card Emulation Using the
TRF7970A.
For more information about NFC Reader/Writer, see NFC/HF RFID Reader/Writer Using the TRF7970A.
References www.ti.com
12 References
1. TRF7970A Multiprotocol Fully Integrated 13.56-MHz RFID and Near Field Communication (NFC)
Transceiver IC
2. ISO/IEC18092/ECMA-340 (NFCIP – 1) (http://www.ecma-international.org)
3. ISO/IEC21481/ECMA-352 (NFCIP – 2) (http://www.ecma-international.org)
4. ISO/IEC14443-3:2009(E) (http://www.ansi.org)
5. ISO/IEC14443-4:2008(E) (http://www.ansi.org)
6. NFCForum-TS-DigitalProtocol-1.0 (Digital Protocol) (http://www.nfc-forum.org)
7. NFCForum-TS_LLCP_1.1 (Logical Link Control Protocol) (http://www.nfc-forum.org)
8. NFCForum-TS-SNEP_1.0 (Simple NDEF Exchange Protocol) (http://www.nfc-forum.org)
9. NFC Research Lab Hagenberg (http://www.nfc-research.at)
www.ti.com Revision History
Revision History
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
Changes from April 30, 2014 to December 9, 2016 ......................................................................................................... Page
• Added the paragraph that starts "A 16-bit and a 32-bit microcontroller are used to interface..." in Section 1, Introduction 3
• Added Section 3, TRF7970A Register Settings, and moved existing content to it ............................................... 6
• Added the paragraph that starts "The ISO Control (0x01) register is modified..." ................................................ 6
• Changed the Requires Modification, Initiator column from No to Yes for address 0x18 in Table 2, TRF7970A Default
Register Values After Receiving SOFT_INIT and IDLE Direct Commands ....................................................... 7
• Updated all of Section 6, Hardware Description ..................................................................................... 17
• Added two paragraphs starting at "The firmware example that contains the Peer-to-Peer APIs..." in Section 7, Passive and
Active Peer-to-Peer Firmware Example .............................................................................................. 20
• Removed API descriptions and added reference to API guide in Section 7.1, Peer-to-Peer APIs ........................... 20
• Replaced former Table 4, TRF7970A + MSP430F5529 Experimenters Board Hardware Connection, with Table 3 through
Table 5 .................................................................................................................................... 21
• Removed row for TRF7970A EN2 from Table 3, DLP-7970ABP BoosterPack Plug-in Module + MSP-EXP430F5529LP
Hardware Connections .................................................................................................................. 21
• Changed P3.0 to P2.2 in note (1) on Table 3, DLP-7970ABP BoosterPack Plug-in Module + MSP-EXP430F5529LP
• Removed row for TRF7970A EN2 from Table 4, TRF7970ATB + MSP-EXP430F5529 Experimenter Board Hardware
Connections .............................................................................................................................. 21
• Removed row for TRF7970A EN2 from Table 5, DLP-7970ABP + MSP-EXP432P401R LaunchPad Development Kit
• Changed function names and the code example in Section 7.2.1, Low-Level Initialization ................................... 22
• Changed the code example in Section 7.2.2, Peer-to-Peer NFC Stack Setup .................................................. 23
• Changed function names and the code example in Section 7.2.3, Sending NDEF Packets .................................. 24
• Changed function names and the code example in Section 7.2.4, Receiving NDEF Packets ................................ 26
• Added Section 8, Quick Start Guide .................................................................................................. 27
• Removed former Section 8, Operational Detail ...................................................................................... 28
• Added the paragraph that starts "Based on the results of the interoperability tests..." in Section 10, Peer-to-Peer
Interoperability Results .................................................................................................................. 28
• Removed former Section 10, Out of the Box Experience .......................................................................... 31
• Updated Section 11, Conclusion....................................................................................................... 31
SLOA192A – April 2014 – Revised December 2016 Revision History 33

IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and other
changes to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per JESD48, latest
issue. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and
complete. All semiconductor products (also referred to herein as “components”) are sold subject to TI’s terms and conditions of sale
supplied at the time of order acknowledgment.
TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty in TI’s terms
and conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent TI deems necessary
to support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarily
performed.
TI assumes no liability for applications assistance or the design of Buyers’ products. Buyers are responsible for their products and
applications using TI components. To minimize the risks associated with Buyers’ products and applications, Buyers should provide
adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, or
other intellectual property right relating to any combination, machine, or process in which TI components or services are used. Information
published by TI regarding third-party products or services does not constitute a license to use such products or services or a warranty or
endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the
third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alteration
and is accompanied by all associated warranties, conditions, limitations, and notices. TI is not responsible or liable for such altered
documentation. Information of third parties may be subject to additional restrictions.
Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or service
voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice.
TI is not responsible or liable for any such statements.
Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements
concerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or support
that may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which
anticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might cause
harm and take appropriate remedial actions. Buyer will fully indemnify TI and its representatives against any damages arising out of the use
of any TI components in safety-critical applications.
In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TI’s goal is to
help enable customers to design and create their own end-product solutions that meet applicable functional safety standards and
requirements. Nonetheless, such components are subject to these terms.
No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of the parties
have executed a special agreement specifically governing such use.
Only those TI components which TI has specifically designated as military grade or “enhanced plastic” are designed and intended for use in
military/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI components
which have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for compliance with all legal and
regulatory requirements in connection with such use.
TI has specifically designated certain components as meeting ISO/TS16949 requirements, mainly for automotive use. In any case of use of
non-designated products, TI will not be responsible for any failure to meet ISO/TS16949.
Products Applications
Audio www.ti.com/audio Automotive and Transportation www.ti.com/automotive
Amplifiers amplifier.ti.com Communications and Telecom www.ti.com/communications
Data Converters dataconverter.ti.com Computers and Peripherals www.ti.com/computers
DLP® Products www.dlp.com Consumer Electronics www.ti.com/consumer-apps
DSP dsp.ti.com Energy and Lighting www.ti.com/energy
Clocks and Timers www.ti.com/clocks Industrial www.ti.com/industrial
Interface interface.ti.com Medical www.ti.com/medical
Logic logic.ti.com Security www.ti.com/security
Power Mgmt power.ti.com Space, Avionics and Defense www.ti.com/space-avionics-defense
Microcontrollers microcontroller.ti.com Video and Imaging www.ti.com/video
RFID www.ti-rfid.com
OMAP Applications Processors www.ti.com/omap TI E2E Community e2e.ti.com
Wireless Connectivity www.ti.com/wirelessconnectivity
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2016, Texas Instruments Incorporated

Sloa 192 A

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Sloa 192 A

Hochgeladen von

Copyright:

Verfügbare Formate

Application Report

SLOA192A – April 2014 – Revised December 2016

NFC Active and Passive Peer-to-Peer Communication

Erick Macias, Josh Wyatt

NFC Data Exchange Format

Simple NDEF NDEF Push

Logical Link Control Protocol

Data Exchange Protocol

NFC/RFID Transceiver TRF7970A

Figure 1. Peer-to-Peer Layers Including the PHY (TRF7970A)

Table 1 lists the NFC-enabled devices used to validate the firmware.

Table 1. NFC Enabled Devices Used to Test Peer-to-Peer

Figure 2. RSSI Level Measurement Orientations

Distance vs RSSI Levels ( Long Side)

Distance vs RSSI Levels ( Short Side)

Distance vs RSSI Values ( Top Side)

Distance between atnennas (cm) 8

The initial RF collision can be accomplished by performing the following steps:

3 TRF7970A Register Settings

4 Peer-to-Peer at 106 kbps

Start Byte Length

Figure 6. Frame Format for 106 kbps

RF field Yes Stay in Target mode Yes Packet

Switch to Initiator Switch to Initiator No

Initiator SDD for Initiator SDD for Active Passive

Figure 7. Peer-to-Peer 106 kbps Flow Diagram

4.1 Active Communication

ATR_RES No Exit Anti-Collision

Write to ISO Control

Figure 8. Peer-to-Peer 106 kbps Initiator Anticollision for Active Communication

4.2 Passive Communication

SENS_RES No Exit Anti-Collision

Figure 9. Peer-to-Peer 106 kbps Initiator Anticollision for Passive Communication

5 Peer-to-Peer at 212 kbps and 424 kbps

RF field Yes Stay in Target mode Yes Packet

Switch to Initiator Switch to Initiator No Is packet

Initiator SDD for Initiator SDD for Active Passive

5.1 Active Communication

ATR_RES No Exit Anti-Collision

Send PSL_REQ and

Write to ISO Control

Figure 12. Peer-to-Peer 212 kbps Active Initiator Anticollision

5.2 Passive Communication

6.1 LaunchPad™ Development Kit and BoosterPack™ Plug-in Module Setup

6.1.1 BoosterPack Plug-in Module: DLP-7970ABP

6.1.2 LaunchPad Development Kit: MSP-EXP430F5529LP

6.1.3 LaunchPad Development Kit: MSP-EXP432P401R

6.2 Experimenter Board Setup

6.3 TRF7970ATB Module

Figure 15. MSP430F5529 USB Experimenter Board and TRF7970ATB

6.4 Available Bundles for Purchase

7 Passive and Active Peer-to-Peer Firmware Example

Figure 16. Peer-to-Peer NFC Stack Architecture

7.1 Peer-to-Peer APIs

7.2 Implementing a Peer-to-Peer Sample Application

Table 3. DLP-7970ABP BoosterPack Plug-in Module +

Table 4. TRF7970ATB + MSP-EXP430F5529

Table 5. DLP-7970ABP + MSP-EXP432P401R

7.2.1 Low-Level Initialization

// Peer to peer RX Status

// Bytes Received from Peer to Peer

//Enable interrupts globally

// Initialize S1 and S2 buttons