
CLRC632_35
NXP B.V. 2009. All rights reserved.
Product data sheet
PUBLIC
Rev. 3.5 — 10 November 2009
073935
84 of 126
NXP Semiconductors
CLRC632
Multiple protocol contactless reader IC (MIFARE/I-CODE1)
Parity bits are not counted in the CollPos register because bit-collisions in parity bit occur
after bit-collisions in the data bits. If a collision is detected in the SOF, a frame error is
agged and no data is sent to the FIFO buffer. In this case, the receiver continues to
monitor the incoming signal. It generates the correct notications to the microprocessor
when the end of the faulty input stream is detected. This helps the microprocessor to
determine when it is next allowed to send data to the card.
11.2.2.4
Receiving bit oriented frames
The receiver can manage byte streams with incomplete bytes which result in bit-oriented
frames. To support this, the following values may be used:
BitFraming register’s RxAlign[2:0] bits select a bit offset for the rst incoming byte. For
example, if RxAlign[2:0] = 3, the rst 5 bits received are forwarded to the FIFO buffer.
Further bits are packed into bytes and forwarded. After reception, RxAlign[2:0] is
automatically cleared. If RxAlign[2:0] = logic 0, all incoming bits are packed into one
byte.
RxLastBits[2:0] returns the number of bits valid in the last received byte. For example,
if RxLastBits[2:0] evaluates to 5 bits at the end of the received command, the 5 least
signicant bits are valid. If the last byte is complete, RxLastBits[2:0] evaluates to zero.
RxLastBits[2:0] is only valid if a frame error is not indicated by the FramingErr ag. If
RxAlign[2:0] is not zero and ParityEn is active, the rst parity bit is ignored and not
checked.
11.2.2.5
Communication errors
The events which can set error ags are shown in
Table 140.
Table 139. Return values for bit-collision positions
Collision in bit
CollPos register value
(Decimal)
SOF
0
Least Signicant Bit (LSB) of the Least Signicant Byte (LSByte)
1
……
Most Signicant Bit (MSB) of the LSByte
8
LSB of second byte
9
……
MSB of second byte
16
LSB of third byte
17
……
Table 140. Communication error table
Cause
Flag bit
Received data did not start with the SOF pattern
FramingErr
CRC block is not equal to the expected value
CRCErr
Received data is shorter than the CRC block
CRCErr
The parity bit is not equal to the expected value (i.e. a bit-collision, not parity)
ParityErr
A bit-collision is detected
CollErr