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
51 of 127
T
able 38. MFC_Authenticate_REQ parameters
P
arameter
L
ength
(B
yte)
Va
lue
D
escription
1 Sector Address 1 Address of the sector to authenticate
2 Key Selector 1 N/A
B
it Mask
D
escription
b7 b6 b5 b4 b3 b2 b1 b0
X Ke
y A (‘0’) or Key B (‘1’)
X
0 =
> use pre-loaded key
1 => use Key in param Nbr 3
X X X X Pre-loaded key number (0 to 15)
0 0 RF
U
3 Embedded Key
(optional)
6 N/A This parameter is present in the MFC_Authenticate_CMD only if bit
b4 is set to logical '1' in Key Selector parameter. If present, this
parameter defines the value of the Key used for the Authentication.
T
able 39. MFC_Authenticate_RSP
RSP_ID RSP Name
P
resence
o
f Data
Description
0x40 MFC_Authenticate_RSP No DH gets the “authenticate” cmd status
T
able 40. TAG-CMD RF Status code, in the special case of MFC_Authenticate_CMD
Va
lue
D
escription
R
eason
0x00 STATUS_OK Authentication was successful
0x03 STATUS_FAILED Authentication failed (wrong key, time-out triggered during authentication etc…)
0xB0 RF_TRANSMISSION_ERROR Not used
0
xB1 RF_PROTOCOL_ERROR Not used
0
xB2 RF_TIMEOUT_ERROR Not used
Others Forbidden
O
nce a sector is authenticated, PN7150 will automatically encrypt any data sent by the DH
to be transferred over RF, thanks to the XCHG_DATA_REQ command.
The key used is the one used for the sector currently authenticated. In a symmetrical way,
PN7150 will automatically decrypt the data received from RF before it forwards to the DH
thanks to the XCHG_DATA_RSP response, again using the key of the sector currently
authenticated.
Fig 32 illustrates the use of the MFC_Authenticate_REQ & XCHG_DATA_REQ in a typical
NFC reader sequence for MIFARE Classic.