User's Manual
Table Of Contents
- 1. Introduction
- The PN7150 architecture overview
- 2. NCI Overview
- 3. DH interface
- 5. Initialization & Operation configuration
- 6. Reader/Writer Mode
- 6.1 T1T, T2T, MIFARE Ultralight, MIFARE Classic and MIFARE Plus tags
- 6.1.1 Access through the [NCI] Frame RF Interface
- 6.1.2 [PN7150-NCI] extension: TAG-CMD Interface
- 6.1.3 [PN7150-NCI] extension: Payload structure of the TAG-CMD RF Interface
- 6.1.4 [PN7150-NCI] extension: REQs & RSPs rules
- 6.1.5 [PN7150-NCI] extension: List of REQs & RSPs
- 6.1.6 [PN7150-NCI] extension: raw data exchange REQs & RSPs
- 6.1.7 [PN7150-NCI] extension: T2T & MFU REQs & RSPs
- 6.1.8 [PN7150-NCI] extension: MIFARE Classic REQs & RSPs
- 6.1.9 Access through the TAG-CMD RF Interface
- 6.2 T3T tag
- 6.3 T4T & ISO-DEP Tags/Cards
- 6.3.1 Access through the Frame RF Interface
- 6.3.2 Access through the ISO-DEP RF Interface
- 6.3.3 [PN7150-NCI] extension: Presence check Command/Response
- 6.3.4 [PN7150-NCI] extension: S-Block Command/Response
- 6.3.5 [PN7150-NCI] extension: WTX notification
- 6.3.6 [PN7150-NCI] extension: Higher bit rates in Poll NFC-A & NFC-B
- 6.4 [PN7150-NCI] extension: 15693 & I-Code tags
- 6.5 [PN7150-NCI] extension: KOVIO tags
- 6.1 T1T, T2T, MIFARE Ultralight, MIFARE Classic and MIFARE Plus tags
- 7. Card Emulation Mode
- 8. P2P Initiator & Target Mode
- 9. RF Discovery Management
- 9.1 RF Discovery functionalities
- 9.2 NFC FORUM Profile as defined in [NCI]
- 9.3 [PN7150-NCI] extension: additional technologies not yet supported by the NFC FORUM
- 9.4 [PN7150-NCI] extension: Low Power Card Detector (LPCD) Mode
- 9.5 [PN7150-NCI] extension: EMVCo Profile in Poll & Listen Modes
- 9.6 [PN7150-NCI] extension: Power optimization
- 10. Configurations
- 11. Test Mode
- 12. PN7150 Practical approach
U
M10936
P
N7150 User Manual
UM
10936 All information provided in this document is subject to legal disclaimers.
U
ser manual
CO
MPANY PUBLIC
Rev. 2.0 — 6 November 2020
348120
62 of 127
!
PN
7150 is parsing the bit Option Flag (bit b7 in the request Flags Byte, as
defined in ISO15693) to check if this bit is set by the DH or not. If set, this
indicates that the tag is from TI, and PN7150 is sending commands over RF
using a special mode, as defined for some commands in ISO15693.
D
ata from RF to the DH
The NCI Data Message corresponds to the Payload of the Response Format defined in
[ISO15693-3] Section 7.4, followed by a Status field of 1 octet.
After receiving an RF frame, the PN7150 checks and removes the EoD, the SOF & EOF
and sends the result in a Data Message to the DH.
In case of an error the Data Message may consist of only a part of the Payload of the
received RF frame but it will always include the trailing Status field. So the PN7150 may
send a Data Message consisting of only the Status field if the whole RF frame is corrupted.
If the RF frame was received correctly, the PN7150 sets the Status field of Data Message
to a value of STATUS_OK. If the PN7150 detected an error when receiving the RF frame,
it sets the Status field of the Data Message to a value of
STATUS_RF_FRAME_CORRUPTED.
The following figure illustrates the mapping of the RF frame received from the Remote NFC
Endpoint in technology NFC-15693 to the Data Message format to be sent to the DH. This
figure shows the case where NCI Segmentation and Reassembly feature is not used.
Data Packet Header Payload
RF Frame
Data Packet
1 octet254 octets at maximum
Status
Payload [EoD]
CRC_1
CRC-2
FLAGS PARAM DATA
SOF EOF
F
ig 34. Format for Frame RF Interface (NFC-15693) for Reception
6.
4.4 PN7150 behavior with multiple VICCs
PN
7150 supports collision resolution (using the Inventory command), so it can detect
multiple VICCs (2 maximum, as defined for CON_DEVICE_LIMIT in →4.2.5).
Here is the behavior when two VICCs are detected and then, one of them is removed from
the Field before the DH wants to select it:
• PN7150 is in state RFST_DISCOVERY; it detects 2 VICCs. It sends an
RF_DISCOVER_NTF to the DH for VICC1 and moves to
RFST_W4_ALL_DISCOVERIES.