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
43 of 127
5.4 Proprietary command to enable proprietary extensions
I
t is visible on the previous flow chart that NXP has introduced a proprietary command sent
by the DH to enable the proprietary extensions to [NCI], which are available in the PN7150.
So, when the PN7150 receives this command NCI_PROPRIETARY_ACT_CMD, it knows
that the DH is aware of the proprietary extensions and may therefore send proprietary
notifications (see the list in Table 12). If the PN7150 does not receive this proprietary
command, it knows that the DH do not understand proprietary extensions and will therefore
not send any proprietary notifications.
Here is the description of this command:
T
able 22. NCI_PROPRIETARY_ACT_CMD
G
ID
O
ID
N
umbers of
p
arameter(s)
D
escription
1111b 0x
02 0 DH informs the PN7150 that it knows the proprietary
extensions.
T
able 23. NCI_PROPRIETARY_ACT_RSP
G
ID
O
ID
Numbers of
p
arameter(s)
D
escription
1111b 0x
02 2 PN7150 indicates that it understood the command.
T
able 24. NCI_PROPRIETARY_ACT_RSP parameters
P
ayload Field(s)
L
ength
V
alue/Description
STATUS 1 Octet One of the following Status codes, as defined in [NCI_Table1]
0x00 STATUS_OK
0x03 STATUS_FAILED
O
thers Forbidden
FW_Build_Number 4 Octets NXP internal firmware build number
5
.5 Configuration template
I
n order to help the user of the PN7150 to issue the right configuration sequence for a
given mode of operation, the present document will detail a typical configuration sequence,
based on the following template:
T
able 25. Template for a typical configuration sequence
C
ommand
M
ain Parameters
V
alues
RF
_DISCOVER_MAP_CMD
RF Protocol …
Mode …
R
F Interface …
CO
RE_SET_CONFIG_CMD Depends on technology & mode …
RF
_DISCOVER_CMD RF Technology & Mode …