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
40 of 127
5
. Initialization & Operation configuration
5.1 Reset / Initialization
[
NCI] defines a Reset/Initialization sequence, which is based on two different commands:
CORE_RESET_CMD
CORE_INIT_CMD
These two commands have to be called by the DH in an “atomic” way: there cannot be any
other command in-between and the PN7150 operation cannot start any operation
(Reader/Writer, Card Emulation, P2P, Combined modes etc…) if it does not first receive
these 2 commands.
[NCI] defines 2 modes for the Reset command: Keep Configuration & Reset Configuration.
Here is the detail of the difference between the 2 reset modes:
T
able 20. Comparison of the 2 Reset Modes
F
eatures
R
eset
C
onfiguration
K
eep
C
onfiguration
C
PU reboot Yes Yes
NCI Configuration parameters Back to default Kept
Proprietary Configuration parameters Kept Kept
I
nterface Mapping Table Lost Kept
D
iscovery activity Lost Lost
!
PN
7150 may delay the CORE_RESET_RSP
If the DH sends a CORE_RESET_CMD while PN7150 has already indicated that it has
some data available to be read by the DH (IRQ pin activated), the DH has first to read the
data available from PN7150 before it can get the CORE_RESET_RSP. The reason is that
the NCI output buffer in PN7150 needs to be flushed before PN7150 can apply a Reset
and then send the CORE_RESET_RSP.
5
.2 Manufacturer Specific Information in [NCI] CORE_INIT_RSP
T
he NCI command CORE_INIT_RSP contains a field “Manufacturer Specific Information”
with 4 bytes.
Here are the values of these 4 Bytes:
T
able 21. Manufacturer specific information in CORE_INIT_RSP
By
te
M
eaning
C
ondition to increment
0 H
ardware Version number New silicon
1 ROM Code Version number New ROM Code
2 F
irmware Major version New Firmware, adding features
3 F
irmware Minor version New Firmware, solving bugs on existing features.