MLX90132 Datasheet, PDF (20/44 Pages) Melexis Microelectronic Systems – 13.56MHz RFID / NFC Transceiver

MLX90132
13.56MHz RFID / NFC Transceiver
1)_{The process of automatically calculating and adding the parity bit by the MLX90132 can be disabled by}
setting the bit 4 of the flags to ‘1’. In this case, the application must add one byte to the data with the most
significant bit corresponding to the parity bit. The other bits of these additional bytes are not considered and
can be set to ‘0’ or ‘1’. The datastream will then look like: <DataByte><Parity><DataByte><Parity>.
Interpretation of <Data> field for different protocols
Protocol Explanation
Response example
Comments
Response example 80 08 0000000000 77CF 00
Result code
ISO15693
Length of entire data field
Data received from TAG
Original (received) value of CRC
7:2 – RFU
1 – CRC error if set
0 – Collision is detected if set
000000000077CF- this is a response on
Read Single Block command for Iso15693
TAG. Other fields are added by the device
Response example 80 09 80B30B8DB500 00 00 00
Result code
Length of entire data field
Data received from TAG
7 – Collision is detected
6 – RFU
5 – CRC error
4 – parity error
ISO14443A _{3:0 – shows how many significant bits are there}
NFC-A
in the first byte
7:0 – Index of the first byte where collision is
detected
ISO/IEC14443A is bit oriented protocol,
and non-integer amount of bytes can be
received. Number of significant bits in
the 1st byte is the same as indicated in
Send command.
To calculate a position of a collision,
application has to take index of byte first.
Index of bit indicates a position inside
this byte. Note that both indices start from
0 and bit index can be 8, meaning that
collision could also affect the parity bit.
7:4 – RFU
3:0 – Index of the first bit where collision is detected
Note that collision information is only
present when protocol ISO/IEC14443A
with a data rate of 106kbps for
transmission and reception is selected.
When others protocols are selected, the
two additional bytes are not transmitted.
Response example 80 0F 5092036A8D00000000007171 3411 00
Result code
Length of entire data field
ISO14443B _{Data received from TAG}
NFC-B _{Original (received) value of CRC}
7:2 – RFU
1 – CRC error if set
0 – RFU
Response example 80 12 01010105017B06941…93FF 00
Result code
ISO18092 ^{Length of entire data field}
(212,424Kb) Data received from TAG
NFC-F _{7:2 – RFU}
1 – CRC error if set
0 – RFU
801201010105017B06941004014B024F4
993FF00 – typical answer with no error
detected
Table 15: “SendRecv” command, interpretation of <data> field for different protocol
3901090132
Rev. 009
Page 20 of 44
Jan-2014