User's Manual

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
47 of 127
6.
1.2 [PN7150-NCI] extension: TAG-CMD Interface
I
n addition to the incompatibility of the Frame RF Interface with the MIFARE Classic
Authenticate command described in the previous chapter, the intention when introducing
the TAG-CMD interface was to add some commands such as ReadN/WriteN which would
allow to read/write multiple bytes, and would rely on the NFCC to call several times the
basic read/write commands defined in the T1T, T2T or MIFARE Classic protocols.
Unfortunately, we had to withdraw this concept and the TAG-CMD as implemented in
PN7150 is limited to MIFARE Classic operation in Reader/Writer and T2T operation in
Reader/Writer when the Sector Select command is required.
The figure bellow represents the location of the TAG-CMD RF Interface:
Fig 30. TAG-CMD RF Interface
6.
1.3 [PN7150-NCI] extension: Payload structure of the TAG-CMD RF Interface
T
he TAG-CMD RF Interface is using the same data mapping as the one defined for the
[NCI] Frame RF Interface (see section 8.2.1 in [NCI]). However, for the TAG-CMD RF
Interface, the Payload is defined differently.
Two different structures are defined:
1. REQ (requests) : these are commands from the DH to the NFCC
2. RSP (responses): these are responses from the NFCC to the DH.
The diagram below details how the Payload is modified to insert a header, which carries
the REQ ID or the RSP ID and some parameters, if required.