MFRC63002R datasheet(64/118 Pages) NXP

64 / 118 page

MFRC630

All information provided in this document is subject to legal disclaimers.

Product data sheet

COMPANY PUBLIC

Rev. 3.1 — 6 September 2012

227531

64 of 118

NXP Semiconductors

MFRC630

Contactless reader IC

9.6.2 Status

Status register.

Table 60.

Error bits

Bit

Symbol

Description

EE_Err

An error appeared during the last EEPROM command. For

details see the descriptions of the EEPROM commands

FIFOWrErr Data was written into the FIFO, during a transmission of a possible CRC,

during "RxWait", "Wait for data" or "Receiving" state, or during an

authentication command. The Flag is cleared when a new CL command is

started. If RxMultiple is active, the flag is cleared after the error flags have

been written to the FIFO.

FIFOOvl

Data is written into the FIFO when it is already full. The data that is already in

the FIFO will remain untouched. All data that is written to the FIFO after this

Flag is set to 1 will be ignored.

4Min

FrameErr

A valid SOF was received, but afterwards less then 4 bits of data were

received.

Note: Frames with less than 4 bits of data are automatically discarded and the

RxDecoder stays enabled. Furthermore no RxIrq is set. The same is valid for

less than 3 Bytes if the EMD suppression is activated

Note: MinFrameErr is automatically cleared at the start of a receive or

transceive command. In case of a transceive command, it is cleared at the

start of the receiving phase ("Wait for data" state)

NoDataErr

Data should be sent, but no data is in FIFO

CollDet

A collision has occurred. The position of the first collision is shown in the

Note: CollDet is automatically cleared at the start of a receive or transceive

command. In case of a transceive command, it is cleared at the start of the

receiving phase (“Wait for data” state).

Note: If a collision is part of the defined EOF symbol, CollDet is not set to 1.

ProtErr

A protocol error has occurred. A protocol error can be a wrong stop bit or SOF

or a wrong number of received data bytes. When a protocol error is detected,

data reception is stopped.

Note: ProtErr is automatically cleared at start of a receive or transceive

command. In case of a transceive command, it is cleared at the start of the

receiving phase (“Wait for data” state).

Note: When a protocol error occurs the last received data byte is not written

into the FIFO.

IntegErr

A data integrity error has been detected. Possible cause can be a wrong

parity or a wrong CRC. In case of a data integrity error the reception is

continued.

Note: IntegErr is automatically cleared at start of a Receive or Transceive

command. In case of a Transceive command, it is cleared at the start of the

receiving phase (“Wait for data” state).

Note: If the NoColl bit is set, also a collision is setting the IntegErr.

MFRC63002R датащи(PDF) 64 Page - NXP Semiconductors

MFRC63002R датащи(HTML) 64 Page - NXP Semiconductors

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

датащи скачать

ссылки URL