NXP Semiconductors
UM10858
PN7462 family HW user manual
UM10858
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User manual
COMPANY PUBLIC
Rev. 1.4 — 14 May 2018
314514
168 of 345
Bit
Symbol
Access
Value
Description
1
Odd parity calculation is used
0
RX_PARITY_ENABL
E
D
0*, 1
If set to 1, a parity-bit for each byte is expected, will be
extracted from data stream and checked for correctness. In
case the parity-bit is incorrect, the
RX_DATA_INTEGRITY_ERROR flag is set.
Nevertheless, the reception is continued.
Note
: This bit is set by the mod-detector if automatic mode
detection is enabled and ISO14443A communication is
detected.
Table 206. CLIF_RX_STATUS_REG register (address 0060h)
* = reset value
Bit
Symbol
Access
Value
Description
31
RESERVED
R
0
Reserved
30:24
RX_COLL_POS
R
0* - 7Fh
These bits show the bit position of the first detected collision
in a received frame (only data bits are interpreted).
Note
: These bits shall only be interpreted in passive
communication mode at 106 kbit/s or reader/writer mode
supporting ISO14443A and MIFARE ICs or ICODE SLIX
reader/ writer mode if bit CollPosValid is set to 1.
Note
: If RX_ALIGN is set to a value different to 0, this value
is included in the RX_COLL_POS.
23
RX_WRITE_ERROR
R
0*, 1
This error flag is set to 1, if for an ongoing reception data is
not copied to RAM in time (BMA encountered write error)
and therefor the reception is aborted
22
RX_LATENCY_ERR
OR
R
0*, 1
This error flag is set to 1, if for an ongoing reception data is
not copied to RAM in time (BMA latency to big) and therefor
the reception is aborted
21
RX_BUFFER_OVFL_
ERROR
R
0*, 1
This flag is set to 1 when the number of received bytes
exceeds the size of the RXBuffer
20
RX_CL_ERROR
R
0*, 1
General contactless error, is a combination of data integrity,
protocol and collision error
19
RX_LEN_ERROR
R
0*, 1
This flag is set to 1, if RXMultiple is activate and the LEN
byte indicates more than 28 bytes
18
RX_COLLISION_DET
ECTED
R
0*, 1
This flag is set to 1, when a collision has accrued. The
position of the first collision is shown in the register
RX_COLLPOS
17
RX_PROTOCOL_ER
ROR
R
0*, 1
This flag is set to 1, when a protocol error has accrued. A
protocol error can be a wrong stop bit, a missing or wrong
ISO14443B EOF or SOF or a wrong number of received
data bytes.
Note
: When a protocol error is detected, data reception is
stopped.
Note
: The flag is automatically cleared at start of next
reception.