NXP Semiconductors
UM10883
PN7462 family Quick Start Guide - Development Kit
UM10883
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
Rev. 1.6 — 14 May 2018
319816
53 of 120
•
ISO14443-3B:
Contactless proximity card air interface communication at 13.56MHz
for the Type B contactless cards.
•
ISO14443-4:
Specifies a half-duplex block transmission protocol featuring the special
needs of a contactless environment and defines the activation and deactivation
sequence of the protocol.
•
ISO14443-4A
: Transmission protocol for Type A contactless cards.
•
MIFARE (R):
Contains support for MIFARE authentication and data exchange.
•
ISO15693:
Contactless protocol for vicinity RFID. It operates on 13.56MHz and uses
magnetic coupling between the reader and transponder.
•
ISO18000-3M3:
Contactless protocol for vicinity RFID. It is especially suited for
applications where reliable identification and high anti-collision rates are required.
•
FeliCa
(JIS: X6319): Contactless RFID smart card system from Sony.
•
ISO/IEC 18092:
NFC Interface and Protocol standard that enables NFC Data
Exchange protocol.
The contact protocol library implements the components for the contactless protocol,
such as EMV ATR Parser, T=0 protocol, T=1 protocol. This library also handles the
timing compliance violations.
7.3 Application layer – AL
In the application layer customer applications, shall be implemented and can directly use
HAL APIs or APIs from the PAL libraries.
The contactless example (or application) is either NFC Forum Polling Loop or EMV
Polling Loop that branches to dedicated examples depending on the card detected such
as MIFARE Classic, MIFARE Ultralight, MIFARE DESFire, EMV PayPass transactions
(PPSE). There exists a compile time macro phExMain_Cfg.h to decide whether the
example is NFC Forum or EMV Polling Loop.
The contact example (or application) is an EMV contact (PPSE application on JCOP
card) application that uses the T=1 protocol and the ATR processing of the protocol
library.
7.4 OSAL and utilities layer
The OSAL and Utilities layer is used to abstract Free-RTOS messages, to handle events,
signals and messages between HW functions and to handle HW ISR.
Utilities layer includes a set of utilities which are grouped and encapsulated together in
an independent set of functions. Utilities components provide an interface for protocol
libraries to use HAL APIs such as CRC, RNG etc.
Note:
Detailed description how to use OSAL and utilities layer refer to the CHM help file.
