MLX90132 13.56MHz RFID / NFC Transceiver Features and Benefits Application Examples

MLX90132

13.56MHz RFID / NFC Transceiver

Features and Benefits

 Conforms with ISO/IEC 18092 (NFC)

 Conforms with ISO/IEC 14443A and B,

 Conforms with ISO/IEC 15693

 Conforms with ISO/IEC 18000-3 mode 1

 High speed communication (up to 848kbit/s)

 Standard SPI/UART interfaces

 Built-in Field and TAG detectors

Ordering Information

Part Code

MLX90132

MLX90132

MLX90132

MLX90132

Temperature Code

R (-40°C to 105°C)

R (-40°C to 105°C)

S (-20°C to 85°C)

S (-20°C to 85°C)

Application Examples

 NFC enabled car for access and start

 Combo NFC and Wireless Power Charging solutions

 NFC applications in Industrial area (e.g. White goods, security …)

Package Code Option Code Packing Form Code

LQ (Lead free QFN 5x5 32 leads) AEA-000 RE

LQ (Lead free QFN 5x5 32 leads) AEA-000 TU

LQ (Lead free QFN 5x5 32 leads) AEA-000 RE

LQ (Lead free QFN 5x5 32 leads) AEA-000 TU

Functional Diagram

RX1

TX1

TX2

RX2

MLX90132

Analog section

Figure 1: MLX90132 functional diagram

Description

Digital section

SPI/UART microcontroller

The MLX90132 is a 13.56MHz, fully integrated, multi-protocol RFID/NFC transceiver IC. It has been designed to handle sub-carrier frequencies from 106 to 848 kHz and baud rates up to

848kbit/s.

The dual driver architecture of the MLX90132 requires minimal external support components and allows the transmitter to provide up to

300milliwatts RF power to an appropriate antenna load. This delivered power is suitable for most short to mid-range applications.

The MLX90132 embeds tag emulation functionality to support NFC Peer to Peer passive communication mode. Enhanced tag and field detection capabilities provide significant power consumption reduction in RFID reader configuration and in NFC mode.

The digital section of the MLX90132 handles the low protocol layers from API to physical layer using advanced bit and frame encoding/decoding functions. It contains a digital demodulator based on sub-carrier detection and a programmable bit/symbol encoder/decoder. It also encodes and decodes the start and stop bits, parity bits, extra guard time (EGT), start and end of frame

(SOF/EOF) and CRC.

Its 528 byte buffer handles an entire RFID frame.

The SPI/UART communication ports guarantee easy interface with the majority of microcontrollers.

3901090132

Rev. 009

Page 1 of 44 Jan-2014

MLX90132


Table of Contents

1 Pin and signal descriptions ............................................................................................................................... 3

2 General Description .......................................................................................................................................... 4

3 Power Management and Operating modes...................................................................................................... 6

4 Start-up sequence ............................................................................................................................................ 8

5 Communication Interface & protocol ................................................................................................................ 9

5.1 UART ......................................................................................................................................................... 9

5.2 SPI ........................................................................................................................................................... 10

5.2.1 Polling mode ...................................................................................................................................... 10

5.2.2 IRQ mode .......................................................................................................................................... 11

6 Commands ..................................................................................................................................................... 12

6.1 Command format ..................................................................................................................................... 12

6.2 List of commands ..................................................................................................................................... 12

6.3 IDN command (0x01) ............................................................................................................................... 13

6.4 Protocol select command (0x02) ............................................................................................................. 13

6.5 PollField command (0x03) ....................................................................................................................... 18

6.6 SendRecv command (0x04) .................................................................................................................... 19

6.6.1 Support of extended frames .............................................................................................................. 21

6.6.2 List of Error codes ............................................................................................................................. 22

6.7 Listen command (0x05) ........................................................................................................................... 23

6.8 Send command (0x06)............................................................................................................................. 25

6.9 Idle command (0x07) ............................................................................................................................... 26

6.10 BaudRate command (0x0A) .................................................................................................................. 28

6.11 SubFreqRes command (0x0B) .............................................................................................................. 28

6.12 AcFilter command (0x0D) ...................................................................................................................... 29

7 Modifying internal settings for optimal performances ..................................................................................... 30

7.1.1 Example: How to modify the ARC_B register ................................................................................... 30

7.1.2 Example how to read back WUFlags content ................................................................................... 31

8 Tag Detector ................................................................................................................................................... 32

8.1 Operating Principle .................................................................................................................................. 32

8.2 Calibration procedure............................................................................................................................... 33

9 Field Detector ................................................................................................................................................. 33

10 Electromagnetic support (EMD) ................................................................................................................... 34

11 Application Information ................................................................................................................................. 37

11.1 External Antenna network ...................................................................................................................... 37

11.2 Application schematic ............................................................................................................................ 37

12 Electrical Specifications ................................................................................................................................ 38

12.1 Absolute Maximum Ratings ................................................................................................................... 38

12.2 DC Characteristics ................................................................................................................................. 38

12.3 Power Consumption Characteristics ...................................................................................................... 38

12.4 RF Characteristics ................................................................................................................................. 39

12.5 SPI Characteristics ................................................................................................................................ 40

12.6 Oscillator Characteristics ....................................................................................................................... 41

14 ESD Precautions .......................................................................................................................................... 42

15 Standard information regarding manufacturability of Melexis products with different soldering processes 42

16 Package Information ..................................................................................................................................... 43

17 Disclaimer ..................................................................................................................................................... 44

18 Contact Information ...................................................................................................................................... 44

3901090132

Rev. 009


1 Pin and signal descriptions

The device is packaged in a 32 pin lead free QFN package.

MLX90132


GND_DIG

XIN

XOUT

GND_TX

VDD_TX

TX1

TX2

NC

1

9

Exposed Pad

(EXP)

VDD

UART

RX

/IRQ

IN

VDC

RX1

RX2

GND_RX

NC

17

NC

Pin Symbol Pin Type Description

3

4

5

1

2

6

7

19

20

21

22

GND_dig

XIN

XOUT

GND_TX

VDD_TX

TX1

TX2

GND_RX

RX2

RX1

VDC

23

24

25

26

27

UART_RX / IRQ_in

VDD

UART_TX / IRQ_out

NSS

MISO

28

29

30

MOSI

SCK

SSI_0

31 SSI_1

8-18, 32 NC

EXP

Supply

Analog

Analog

Supply

Supply

Analog

Analog

Supply

Analog

Analog

Analog

Digital I

Supply

Digital O

Digital I

Digital O

Digital I

Digital I

Digital I

Digital I

Exposed Pad

Ground (Digital)

Xtal oscillator input

Xtal oscillator output

Ground (Drivers)

Drivers Power Supply

Driver output_1

Driver output_2

Ground (analog)

Receiver input_2

Receiver input_1

Melexis Reserved

UART Receive pin/Interrupt input

Main Power Supply

UART Transmit pin/Interrupt output

SPI Slave Select

SPI data output

SPI data input

SPI clock

Select serial communication interface

Must be set to GND

Not connected

Must be set to GND

Table 1: Pin definitions and descriptions

3901090132

Rev. 009


MLX90132


2 General Description

MLX90132

GND_TX GND_RX

VDD_TX

GND_dig

VDD

XIN XOUT

Power Supply Clock

Status & Control register

Rx Reader

RX1

RX2

Digital demodulation

TX1

TX2

Tag

Front-End

Tag/Field detector

Digital control

& protocol handling

Interface block

NSS

SCK

MISO

MOSI

IRQ_IN (UART_RX)

IRQ_OUT (UART_TX)

Tx Drivers

Digital Modulation

Figure 2: MLX90132 simplified block diagram

Power Supply

The MLX90132 is supplied with the 2 pins V supply of the TX Drivers), each requiring a nominal stable external power supply from 2.7 to 5.5 volt. Both pins V

DD

and V

DD_TX

DD

(supply of the digital and analog blocks) and V

DD_TX

(direct

are independent and could be connected together to the same power supply level or to different ones. The current drain depends on the antenna impedance and on the output matching network configuration.

Special attention should be paid to the filtering of V

DD_TX added close to the MLX90132 device.

. Typically, a ferrite and a decoupling capacitor will be

TX Drivers

The transmission stage of the MLX90132 is composed of two differential outputs T

X1

and T square waves with a frequency of f

HFO

(typ. 13.56MHz), an amplitude of V

DD_TX degrees. Each output is featuring an equivalent serial resistance R when calculating the antenna matching network.

X2

, providing

ON

and with a phase shift of 180

which has to be taken into account

The transmission stage of the MLX90132 could be modulated using Amplitude Shift Keying (ASK) with a modulation index between 10% and 100%. The modulation index is automatically set with the selection of the

protocol of communication, using the command Protocol select command (0x02) . The modulation index could

be fine adjusted by following the procedure described in the section Modifying internal settings for optimal performances .

In TAG emulation mode, the two outputs TX1 and TX2 are internally connected together, insuring a proper parallel resonance of the antenna. In this configuration, the two serial capacitors CS are put in parallel to the parallel capacitor CP. This operation is done automatically when selecting TAG emulation modes and should also be taken into account when defining an EMI filter for EMC considerations.

3901090132

Rev. 009


MLX90132


RX Reader

The reception stage of the MLX90132 is used in Reader mode to receive information from a transponder or an NFC/RFID device. This stage performs the analog demodulation using two internal diode detectors on

RX1 and RX2.The information is then filtered with the appropriate bandwidth and finally digitized for further processing. The receiver inputs RX1 and RX2 are typically connected to the resonance point of the antenna, through two external attenuation resistors or capacitors to avoid saturation of the internal detector set to

V

RXMAX

. The complete receiver stage is automatically configured according to the protocol in use ( Protocol select command (0x02) ).

Tag Front-end

This block is enabled in Tag emulation mode and performs all operations related to Tag emulation functionality with low power consumption. The modulated information coming from an NFC/RFID device is demodulated through the two built-in detectors connected on RX1 and RX2, filtered with the appropriate bandwidth and finally digitized for further processing. The full settings of the Tag front-end stage are

automatically set with the selected protocol using the Protocol select command (0x02) . The load modulation

used to send back the information in TAG emulation mode is also performed by the Tag front-end block. In this case, an internal resistor is connected between the two inputs RX1 and RX2, modifying the antenna load.

Digital control & protocol handling

This block is responsible for the control of the device, as well as the frame coding and decoding parts of the protocols supported by the MLX90132. The MLX90132 exchanges with the application microcontroller, pure payload information after adding/removing frame related information such as SOF, EOF, EGT … It can also be configured to calculate the CRC for each communication protocol.

Interface Block

The MLX90132 is addressed through SPI or UART (Reader mode only) interfaces with a specific and simple set of commands. The built-in 528 byte buffer allows minimum interaction with the application microcontroller.

This reduces the burden of the microcontroller whose resources can be fully dedicated for the application.

Tag/Field Detector

This block manages the enhanced Tag and Field detection capabilities. It generates a detection signal that is available for the application microcontroller through the interrupt pin IRQ_OUT. It allows the use of the

MLX90132 with low power consumption constraints.

Reference clock and internal oscillator

The built-in reference oscillator works with a reference crystal f

XTAL nominal system clock frequency f

HFO

frequency f

LFO

of 27.12MHz from which the internal of 13.56 MHz is derived. An internal low frequency RC oscillator of 32 kHz is used for low-power operating modes, for example to control the internal timings.

In TAG emulation mode the clock is recovered from the HF field, through the built-in Clock Recovery block. In case of field loss (e.g. during Reader modulation), an internal backup clock of ~10MHz is used instead.

Power management

The MLX90132 features 2 modes of operation (Active and Idle), subdivided in 6 different states of operation:

 Hibernate, the device typically consumes 1µA

 Sleep, the device typically consumes 20µA

 TAG detection, the device typically consumes 45µA.

 TAG emulation, the device typically consumes 2.5mA.

 Ready (RF field OFF), the device typically consumes 2.5mA.

 Reader, the consumption depends on the antenna load and on the operating conditions

3901090132

Rev. 009


MLX90132


3 Power Management and Operating modes

The MLX90132 features 2 main operating modes: Idle and Active, with 6 different states of operation, as described on the table below:

Mode State Description

Hibernate

Lowest power consumption, the MLX90132 wakes-up with low level pulse on IRQ_IN pin

Idle

Sleep

Tag detection

Low Power consumption: Wake-up source to exit from this mode is configurable:

- Timer

- IRQ_in pin (low-level)

- NSS pin (low-level)

- Field detector

Low power consumption: Tag detection feature, wake up source is configurable

- Timer

- IRQ_in pin (low level)

- NSS pin (low level)

- Tag detector (mandatory)

Active

Ready

Reader

TAG Emulation

High frequency oscillator (HFO) is running. In this mode the

MLX90132 is in reader mode with its HF field turned OFF. The

MLX90132 waits for a command from the external application, through the selected serial interface SPI or UART


MLX90132 is selected in reader mode with its HF field set ON. The

MLX90132 is able to receive and execute commands through the selected serial interface SPI or UART and is able to communicate with transponders and NFC devices, according to the selected protocol. In Reader mode, the command “SendRecv” is used to send and receive information from an NFC/RFID transponder or devices


MLX90132 is selected in Tag emulation mode with its HF field set

OFF. The MLX90132 is able to receive and execute commands through the serial interface SPI and is able to communicate with an

NFC/RFID reader, according to the selected protocol. In TAG emulation mode, the commands “Listen” and “Send” will be used to respectively receive/send the information from/to an NFC/RFID reader. The information is returned to the NFC/RFID reader by using load modulation method

Table 2: MLX90132 Operating modes & States

Entering in Hibernate, Sleep and Tag detector states is done with the Idle command (0x07) . As soon as one

of these states is activated, an appropriate source signal is required to wake-up the device (see description above). The wake-up time from Sleep or Hibernate to Ready state is typically of 2ms. This time is mainly due to settling time of XTAL oscillator (HFO).

3901090132

Rev. 009


MLX90132


In Reader state, the MLX90132 is able to communicate with Transponder (TAG). In TAG emulation state, the

MLX90132 is able to communicate with a reader by emulating a Transponder. Both states could be entered

using the Protocol select command (0x02) . In Ready state, the MLX90132 is fully enabled but waiting for the required command to enter either the Reader or the TAG Emulation state, without settling time penalty.

Please note the IDLE mode could be entered directly from Reader/Tag emulation state by sending the Idle command (0x07) , no need to return to READY state to access the IDLE mode.

The command Protocol select command (0x02) with the option field OFF is used to return from Reader/Tag

emulation state to Ready state.

START

Supply OFF

POR

Power-up

Start-up events:

- Low pulse IRQ_IN

Sleep

Wake-up events:

- Low pulse IRQ_IN

- Low pulse SPI_NSS

- Timer

- Field detector

Co

LE

” m m an d

“ID

W ak eup

Ready

Hibernate

Wake-up events:

- Low pulse IRQ_IN

ACTIVE

Command

“PROTOCOL SELECT”

Reader/TAG emulation

Co

W ak m m an d “

ID e-u p

Note: Command “Protocol Select, field

OFF” is used to return to Ready state

LE

”

IDLE

TAG detector

Wake-up events:

- Low pulse IRQ_IN

- Low pulse SPI_NSS

- Timer

- TAG detector

Figure 3: MLX90132 Power modes transitions

3901090132

Rev. 009


MLX90132


4 Start-up sequence

Once powered-up, the MLX90132 waits for a low pulse on the pin IRQ_IN (greater than 10μs) before automatically selecting the external interface (SPI or UART) and entering Ready state after a delay of approximately 2ms. t

4

VDD

SSI_0

SSI_1

t

1

IRQ

IN

t

0 t

2 t

3

First valid command

Figure 4: MLX90132 operating states transition

Figure 4 above shows the power-up sequence for a MLX90132 device where:

 t

0 is the initial wake-up delay

1)

 t

1 is the minimum pulse width in IRQ

 t

3

 t

4 is the

VDD

ramp-up time

1) Value specified by design

1)

IN

pin

1)

 t

2 is the delay for the serial interface selection

1) is the delay before the MLX90132 could accept commands

1)

100μs (minimum)

10μs (minimum)

250ns (typical)

2ms (minimum)

10ms (maximum)

The following configuration at power on reset (POR) is required to select the communication interface to be used.

Interface/Pin SSI_1 SSI_0

SPI

UART

0

0

1

0

Table 3: Selection of the serial communication interface

Notes:

 The Serial Interface is selected after the following falling edge of the pin IRQ_IN when leaving from POR

or Hibernate states.

 When the MLX90132 leaves the IDLE state following a UART_RX/IRQ

NOT interpreted as the UART start bit character.

IN

low level pulse, this pulse is

3901090132

Rev. 009


5 Communication Interface & protocol

MLX90132


Whatever the communication protocol selected (SPI or UART), the principle of communication is always the same: The application sends a command to the MLX90132 and waits for the appropriate answer. A simple and specific set of commands allows the configuration and control of the MLX90132.

Application MLX90132

Select protocol

(e.g. ISO15693, Single Sub-carrier)

→

←

Protocol selected, ready for communicate

Send protocol related data, CRC automatically added (e.g. “022000” + CRC)

→

←

Return TAG answer

(e.g. “001234ABCD”, CRC correct)

Select another protocol

(e.g. ISO14443A, 7-bit mode)

→

Send protocol related data, CRC automatically

(e.g. “26”)

←

→

Protocol selected, ready for communicate

Turn field OFF

←

→

←

Return TAG answer

(e.g. “0400” , Parity is OK, CRC ignored)

Field is OFF

Figure 5: Example of communication with MLX90132

In order to start RFID communication, the application has to choose the protocol and specify some parameters, using the command

Protocol select command (0x02) . When the protocol is selected, the

application sends data and parses response until the next protocol is selected or a specific parameter is changed.

5.1 UART

The default baud rate is 57.6kbps and the maximum allowed baud rate is 2 Mbps.

Sending command to MLX90132

Several data bytes

Receiving answer from MLX90132

Several data bytes

Figure 6: UART communication

Notes:

 Option “clock recovery” (“ClkRec” in

Table 11 ) should not be used when UART interface is selected.

Therefore the UART mode is not recommended for TAG emulation mode

 Length of data field can be zero, in this case no data is sent.

Warning: The UART communication is least significant bit (LSB) first.

3901090132

Rev. 009


MLX90132


5.2 SPI

5.2.1 Polling mode

In order to send commands and receive answers, the application software has to pass 3 stages:

1.



Send the command to the MLX90132

2.



Poll the MLX90132 until it is ready to transmit the response.

3.



Read the response.

The application software should never read the MLX90132 without being sure that the MLX90132 is ready to send its response.

The maximum allowed communication speed is 2Mbps. Please note that the communication speed is limited

to 1.5Mbps in case of TAG emulation mode with “clock recovery” option selected (“ClkRec” in Table 11 ,

TAG/Card emulation mode).

A Control byte is used to specify the communication type and direction (see pictures below):

– 00: Send command to the MLX90132

– 11: Poll the MLX90132

– 10: Read data from the MLX90132

– 01: Reset the MLX90132

The SPI_NSS line is used to select a device on the common SPI bus; the SPI_NSS active level is LOW.

When the SPI_NSS line is inactive, all data sent by the application will be ignored and the SPI_MISO line will be set in high impedance state.

Sending command to the MLX90132

MOSI

Control byte Several data bytes

MISO

Polling the MLX90132 until it is ready

MOSI

Control byte

MISO

Polling Flags until ready

Figure 7: SPI communication, sending command & polling method

The following table shows the meaning of the flags returned by the MLX90132 device.

Bit Description

[4:7]

3

2

[1:0]

RFU, will be set to “0000”

Data can be read from MLX90132 when set

Data can be sent to MLX90132 when set

MLX Reserved

Table 4: Interpretation of SPI flags

3901090132

Rev. 009


MLX90132


Reading data from the MLX90132

MOSI

Control byte

MISO

Several data bytes

Figure 8: SPI communication, reading data from the MLX90132

Data must be sampled by the rising edge of the SPI_SCK signal.

‘Sending’, ‘Polling’ and ‘Reading’ commands must be separated by a high level of the SPI_NSS line.

For example, when the application needs to wait for data from the MLX90132, it sets to low the pin SPI_NSS and issues a ‘Polling’ command. By keeping the SPI_NSS “low”, the application can continuously read the

Flags waiting for the bit indicating that the MLX90132 is ready (the flags will be automatically updated, no need to send several polling commands).Then, the application has to set high the pin SPI_NSS to finish the polling sequence. The application puts low again the pin SPI_NSS to issue a ‘Reading’ command to read data. When all data is read, the application sets high the pin SPI_NSS to terminate the communication.

The MLX90132 can issue as many 'Polling' commands as necessary.

For example, the application sets low the pin SPI_NSS to issue a 'Polling' commands. If the MLX90132 is not ready, the application can put high the pin SPI_NSS and continue its operations. Then, as soon as the application is ready again, it sets low the pin SPI_NSS to issue a 'Polling' commands, to see if the MLX90132 is ready. These operations are not time critical which makes it easy to insert in the application flow.

Reset MLX90132

MOSI

Control byte

MISO

Figure 9: SPI communication reset the MLX90132

Control byte 0x01 resets the MLX90132 and places the device in Power-up state. A wake-up sequence is then necessary to start again the communication with the MLX90132.

Warning: The SPI communication is most significant bit (MSB) first.

5.2.2 IRQ mode

When the MLX90132 is configured to use the SPI serial interface, the pin IRQ_OUT is used to give additional information to the application. When the MLX90132 is ready to send back a reply it sends an Interrupt request by setting a low level on pin IRQ_OUT, which remains low until the application reads the data. The application can use the IRQ mode to skip the polling stage.

3901090132

Rev. 009


MLX90132


6 Commands

6.1

Command format

The structure of the command sent by the application is almost identical to the structure of the answer from the MLX90132, as shown below:

 Command: [CMD] + [LEN] + [DATA]

 Answer:

[RESPCODE] + [LEN] + [DATA]

- [CMD] = Command (1byte)

- [LEN] = Length including only the field DATA, zero if no data sent (1byte)

-

[RESPCODE] = Response code, depends on the command (1byte)

- [DATA] = Data information, depends on the command (0 to 528bytes)

6.2

List of commands

Code Command Description

0x01

0x02 Protocol Select

0x03

IDN

Poll field

Requests short information about device and its FW version

Selects communication protocol and specifies some protocol-related parameters

Returns the current value of the field detector flag (“FieldDet”)

0x04

0x05

SendRecv

Listen

Sends data using previously selected protocol and receives the response of the TAG.

Listens to the data using previously selected protocol.

0x06

0x07

0x0A

0x0B

0x0D

0x55

Send

Idle

Sends data using previously selected protocol.

Switches device into Idle/Sleep/Hibernate mode and specifies which condition is used to exit from these modes

BaudRate Sets UART baud rate

SubFreqRes

Gets the last value of sub-carrier frequency received during ISO/IEC18092 and NFC Tag Type 3 (Felica) communications

AC-Filter

Echo

Other codes

Activates/deactivates anti-collision filter

MLX90132 replies with an Echo of 0x55 to this command. In this specific

case, the command format is not respected as the data is only 0x55

MELEXIS reserved

Table 5: MLX90132 list of commands

3901090132

Rev. 009


MLX90132


6.3 IDN command (0x01)

The IDN command gives information about the MLX90132 and the internal firmware version

IDN0x01

Direction Example

MCU – device

Data

01

00

00

<Len>

<Device ID>

Comment

Command code

Length of data

Result code

Length of data

Data in ASCII format

0100

device - MCU

000F4E4643204653324A41535434002ACE:

4E4643204653324A4153543400= Device ID

2ACE= CRC of internal ROM

<ROM CRC> CRC calculated for ROM content

Table 6: “IDN” command description

Note: It takes about 6ms to calculate the CRC for the entire ROM. Application must allow sufficient time before waiting for an answer for this command.

6.4 Protocol select command (0x02)

The “Protocol Select” command automatically configures the internal registers of the MLX90132 for the best communication performances. It also prepares the MLX90132 by automatically setting the HF field ON

(except in TAG emulation state). The field will be automatically switched OFF either by sending a “Protocol select” command with “Field OFF”, or when the MLX90132 returns to “Idle” mode using the “Idle” command or by selecting TAG emulation.

Protocol Select 0x02

Direction Example Data

02

<Len>

Comment

Command code

Length of data

MCU – device

<Protocol>

Protocol codes (Reader)

00 = Field OFF

01 = ISO/IEC15693

02 = ISO/IEC14443-A / NFC-A

03 = ISO/IEC14443-B / NFC-B

04 = ISO/IEC18092 (212,424Kbps) / NFC-F

Refer to examples in table:

Table 8

,

below

Device - MCU

Device - MCU

Device - MCU

Protocol codes (TAG)

12 = ISO/IEC14443-A/ NFC-A

13 = ISO/IEC14443-B / NFC-B

14 = ISO/IEC18092 (212,424kbps)/ NFC-F

<Parameters>

Depends on protocol selected, refer to Table 8

00

00

82

00

Result code

Length of data

Error code

Length of data

83

00

Error code

Length of data

0000–

Protocol successfully selected

8200-

Invalid command length

8300 -

Invalid protocol

Table 7: “Protocol select” command description

3901090132

Rev. 009


MLX90132


Parameter list for different protocols (Reader)

Protocol

(Reader)

Code

Parameters

Byte Bit Function

Field OFF 00 0

ISO15693

01 0

0

7:0 RFU, set to ‘0’


5:4

00 – 26kbps

01 – 52kbps

10 – 6kbps

11 – RFU

3

2

1

0

7:6

5:4

0 – Respect delay 312us

1 – Wait for SOF

0 - 100% modulation

1 – 10% modulation

0 – Single Sub-Carrier (SSC)

1 – Dual Sub-Carrier (DSC)

0 – No CRC added

1 – CRC auto. Added

Transmission data rate

00 – 106kbps

01 – 212kbps

10 – 424kbps

11 – 847kbps

Reception data rate

00 – 106Kbps

01 – 212Kbps

10 – 424Kbps

11 – 847Kbps


ISO14443A

NFC-A

Examples of commands

02020000

02020101 – Select ISO/IEC15693, SSC,

26kbps, modulation of 100%, CRC automatically added

02020107 – Select ISO/IEC15693, DSC,

26kbps, modulation 10%, CRC automatically added

02020200 – ISO/IEC14443A, 106kbps transmission & reception, Frame Delay Time

(FDT) of 86/90µs

02

1

2

3

4

5

7:0 PP (max 14, i.e. 0x0E)

7:0 MM (max 255, i.e. 0xFF)

7:0 DD (max 127, i.e. 0x7F)

7:0 N

EMD

7:0 N

EMDRES

Frame Delay Time (FDT) definition: These 3 bytes are optional. When PP, MM and DD are not specified or set to 0x00, the default value corresponds to FDT of 86/90us, used during anti-collision process.

Otherwise, the following formula applies:

FDT



2

PP 



MM



1

 

DD



128





32

[



s

]

13.56

If PP is defined, MM must be also set, but DD still remains optional

Related to EMD algorithm, please refer to

chapter Electromagnetic support (EMD)



Table 8: Parameter values for “Protocol select” command (Reader)

3901090132

Rev. 009


MLX90132



Protocol

(Reader)

Code

Parameters

Byte Bit Function

7:6


00 – 106kbps

01 – 212kbps

10 – 424kbps

11 – 847kbps

ISO14443B

NFC-B


0

5:4

Reception data rate

00 – 106kbps

01 – 212kbps

10 – 424kbps

11 – 847kbps

02020301 – ISO/IEC14443B, 106kbps transmission & reception, Frame Waiting Time

(FWT) of 302µs, CRC automatically added

020403010400 – ISO/IEC14443B, 106kbps transmission & reception, Frame Waiting Time

(FWT) of 4.8ms, CRC automatically added


0

0 – No CRC added

1 – CRC auto. added

03

1

2

3

7:0 PP (max 14, i.e. 0x0E)

7:0 MM (max 255, i.e. 0xFF)

7:0 DD (max 127, i.e. 0x7F)

5:4 15:0 TTTT

6

7

8

9

7:0 YY

7:0 ZZ

7:0 N

EMD

7:0 N

EMDRES

Frame Waiting Time (FWT) definition:

These 2 bytes are optional. The default value corresponds to a FWT of 4949ms, answer to

ATTRIB.

FWT



2

PP 



MM



1

 

DD



128





32

[



s

]

13.56

If PP is defined, MM must be also set, but DD still remains optional

Timing: TR0 = TTTT/13.56 us

Coded with LSB first, default value 1023 = 0x3FF

Timing: Min_TR1 = 128 * YY / 13.56us.

Default value: 0

Timing: Max_TR1 = 128 * ZZ / 13.56us.

Default value:26 , i.e. 0x1A






3901090132

Rev. 009


MLX90132



Protocol

(Reader)

Code

Parameters

Byte Bit Function

7:6


00 – RFU

01 – 212kbps

10 – 424kbps

11 – RFU

0 5:4

Reception data rate

00 – RFU

01 – 212Kbps

10 – 424Kbps

11 – RFU

ISO18092

(212,424Kb)

NFC-F

04


0

4

0 – No CRC added



0 - RWT = 2.4ms

1 – RWT is specified by PP:MM


02020451 – ISO/IEC18092, 212kbps for transmission & reception, CRC automatically added

Parameter ‘Slot counter’ is optional, the default value 00 (1 slot) will be used, if not present in the command.

For command SDD (Single Device

Detection), the bit 4 must be set to 0, In this case RWT is 2.4ms for the 1 st

slot and 1.2ms more for each following slot as specified in protocol ISO18092

1

3:0

Slot counter

0x0 – 1 slot

0x1 – 2 slots

…

0xF – 16 slots

2

3

4

7:0 PP (max 14, i.e. 0x0E)

7:0 MM (max 255, i.e. 0xFF)

7:0 DD (max 127, i.e. 0x7F)

Request Waiting Time (RWT) definition:

These 3 bytes are optional. The default value corresponds to a RWT of 302µs.

RWT



2

PP





MM



1

 

DD

13.56



128





32

[



s

] if PP is defined, then MM must be also defined while, DD remains optional


3901090132

Rev. 009


MLX90132


Parameter list for different protocols (TAG Emulation)

Protocol Code

Parameters

Byte Bit

7:6

Function


00 – 106kbps

01 – 212kbps

10..11 - RFU

ISO14443A

NFC-A

12 0

5:4

Reception data rate

00 – 106kbps

01 – 212kbps

10..11 – RFU

ISO14443B

NFC-B

13 0

3

2

1

0

3

3

1)

1)

1)

7:6

5:4

2

1

0

7:4

2

1

0 = Return an error, if no field

1 = Wait for field

RFU, set to ‘0’

0 = HFO

1 = ClkRec

RFU, set to ‘0’


00 – 106kbps

01 – 212kbps

10 – 424kbps

11 – 847kbps

Reception data rate

00 – 106kbps

01 – 212kbps

10 – 424kbps

11 – 847kbps


1 = Wait for field

RFU, set to ‘0’

0 = HFO

1 = ClkRec

0 – No CRC added


RFU, set to ‘0’


1 = Wait for field

RFU, set to ‘0’

0 = HFO

1 = ClkRec

ISO18092

(212,424kb)

NFC-F

14 0

0

0 – No CRC added



Comments

02021200

– TAG/Card emulation

ISO/IEC14443A, 106kbps for transmission & reception, return error if no

HF field detected, HFO used as master clock

0202120A


ISO/IEC14443A, 106kbps for transmission & reception, wait for HF field,

CLKREC use as master clock

02021300


ISO/IEC14443B, 106kbps for transmission & reception, return error if no

HF field detected, HFO use as master clock, CRC automatically added

0202130A


ISO/IEC14443B, 106kbps for transmission & reception, wait for HF field,

CLKREC use as master clock, CRC automatically added

02021400


ISO/IEC18092, return error if no HF field detected, HFO use as master clock, CRC automatically added

Note that it is not necessary to select a data-rate for ISO18092card mode, Datarate will be automatically detected and adjusted during reception (application can read this information by sending

“SubfreqRecv” command).

Table 11: Parameter values for “Protocol select” command (TAG Emulation)

1)

This option will be executed only after a “listen” command has been sent. Please refer to the chapter Listen command (0x05) for more information.

3901090132

Rev. 009


MLX90132


6.5 PollField command (0x03)

The “PollField” command is used to detect the presence of an HF field by monitoring the flag “FieldDet”. This command returns the current value of the flag “FieldDet”. The parameters <Presc> and <Timer> can also be used to define a time during which the MLX90132 continuously scans for the presence of HFfield. The answer to the “PollField” command is available with the flag <FieldDet> updated accordingly, after the scanning period is terminated.

PollField0x03

Direction

MCU – device

Data

03

<Len>

<Flags>

<Presc>

<Timer>

Comment

Command code

Length of data

Timer flag (Optional)

01 – Wait for field appearance

00 – Wait for field disappearance

Timer prescaler (Optional)

Timer time-out (Optional)

Example

0300 – Check if Field is ON or OFF

0303010FFF– Wait for field appearance during(16*256)/13.56=302µs

Parameters Flags, Presc and Timer are optional.

They must be specified if application has to wait for field appearance or disappearance.

The time to wait is:

T ime



( Presc



1)



(Timer



1)

13.56

[

 s ]

Device - MCU

00

01

<FieldDet>

Result code

Length of data

[7:1] – RFU

[0] – 0 : No HF field detected

1 : HF field detected

000101 – HF field is detected

Table 12: “PollField” command

Note: When the MLX90132 is selected in reader mode (protocol select command), the HF field will be automatically turned ON and the flag “FieldDet” will be set to ‘1’ (the MLX90132 detects its own field). Consequently, the PollField command should be used in Tag/Card Emulation state or in Reader state with the HF field set OFF.

3901090132

Rev. 009


MLX90132


6.6 SendRecv command (0x04)

This command is used to send specific protocol data and receives corresponding answer. Before sending this command, the application must select a protocol using the Protocol select command. If the response of the

Transponder was successfully received and decoded, the field <Data> will contain additional information

which is protocol specific. This is explained in the Table 14 below.

SendRecv0x04

Direction Data

04

Comment

Command code

MCU – device

Device - MCU

<Len>

<Data>

<ResultCode>

<Len>

<Data>

Length of data

Data to be sent

Result code

Length of data

Data received. Interpretation depends on protocol

Example

Depends on protocol previously selected!

0403022012– Command “Read single block 12”

(ISO/IEC15693 protocol)

8008000000000077CF00 -

The response of the

TAG is successfully decoded. This is an example of response from an ISO15693 TAG.

The result code might contain additional information on the extended size of received

data. Please refer to paragraph Support of

extended frames

below.

Device - MCU

<ErrorCode>

<ErrorBufLen>

<ErrorBuf>

Error code

Length of Error Buffer stored during

EMD algorithm

Error Buffer stored during EMD algorithm

Please refer to the error code table summary in the chapter

List of Error codes

Table 13: “SendRecv" command description

Data format for transmission

Protocol Explanation

ISO15693

Response example

Send example

Command code

04 03 022000

Length of entire data field

Data

Send example 04 07 9370800F8C8E 28

Command code


Data

Comments

If length of data is Zero, only EOF will be sent. This can be used for anti-collision procedure

ISO14443A

NFC-A

Transmission flags:

7 – 0 : ISO14443A

1: Topaz format (use EOF instead of P, use

SOF at the beginning of each byte, make

pause between bytes, assume 1 st

byte as 7-bit)

6 – SplitFrame if set

5 – append CRC if set

4 – Auto. add the parity bit in if set to ‘0’

1)

3:0 – number of significant bits in last byte

For bit oriented protocol, frames could be split by setting the bit

SplitFrame to one. In this case, the MLX90132 will send the last byte of the command with none integer number of bits, according to the field number of significant bits in last byte.

In reception, the MLX90132 expects to receive the complement

(8 – “number of significant bits in last byte”).

This option is used during anti-collision procedure.

ISO14443B

NFC-B

Send example 04 03 050000

Command code


Data

Send example 04 05 00FFFF0000

Command code

ISO18092

(212,424Kb)

NFC-F

Data


3901090132

Rev. 009

Table 14: Parameter values for “SendRecv” command


MLX90132


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

ISO15693

ISO14443A

NFC-A

Response example 80 08 0000000000 77CF 00

Result code


Data received from TAG

Original (received) value of CRC

7:2 – RFU

1 – CRC error if set

0 – Collision is detected if set

Response example 80 09 80B30B8DB500 00 00 00

Result code


7 – Collision is detected

6 – RFU

5 – CRC error

detected

7:4 – RFU


4 – parity error

3:0 – shows how many significant bits are there

in the first byte

7:0 – Index of the first byte where collision is

3:0 – Index of the first bit where collision is detected

000000000077CF- this is a response on

Read Single Block command for Iso15693

TAG. Other fields are added by the device

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.

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.

ISO14443B

NFC-B

Response example 80 0F 5092036A8D00000000007171 3411 00

Result code




7:2 – RFU


0 – RFU

Response example 80 12 01010105017B06941…93FF 00

Result code

ISO18092

(212,424Kb)

NFC-F


7:2 – RFU


0 – RFU


801201010105017B06941004014B024F4

993FF00 – typical answer with no error detected

Table 15: “SendRecv” command, interpretation of <data> field for different protocol

3901090132

Rev. 009


MLX90132


6.6.1 Support of extended frames

In reader mode it is possible to receive up to 528 bytes of frame data. The extended size is included in the command code as follows:

7

ResultCode

0

1 L L 0 0 0 0 0

7

Len

0

L L L L L L L L

7

Data byte 0

0 x x x x x x x x

L L

9 8

L L L L L L L L

7

Number N of data bytes

0

Figure 10: Coding of Length of extended frames

Consequently, the ResultCode returned depends on the length of the decoded frame received by the

MLX90132.

Direction Result Code Length (LEN) Effective length of received data Comment

MCU - device

0x80

0xA0

0xC0

0x90

0xB0

0xD0

0x00 – 0xFF

0 – 255 bytes

256 – 511 bytes

512 – 528 bytes

0 – 255 bytes

256 – 511 bytes

512 – 528 bytes

In ISO/IEC14443A only in case of none integer number of bytes

Table 16: Coding of Length of extended frames

3901090132

Rev. 009


MLX90132


6.6.2 List of Error codes

The error code returned in the case of a“SendRecv” command includes the last error raised by the device in the field<ErrorCode>. But, it could also include a buffer of error if the EMD algorithm is enabled. This list of errors is stored into the dedicated buffer of maximum 8-bytes <ErrorBuf> with its length indicated in the error buffer length value <ErrorBufLen>. The list of error codes which could be returned after a “SendRecv” command is shown in the table below. The error codes marked with a * could be raised during the EMD process and stored in the Error buffer. For more information related to the EMD algorithm, please refer to the

chapter Electromagnetic support (EMD) below.

Direction Error Code Definition

Device - MCU

0x61*

0x62*

0x63*

0x65*

0x66*

0x67*

0x68*

0x86

0x82

0x83

0x87

0x88

0x89

SOF error during the EMD process

CRC error during the EMD process

SOF error in ISO14443B occurs during high part (duration of 2 to 3 Elementary Unit Time, ETU)

SOF error in ISO14443B occurs during low part (duration of 10 to 11 Elementary Unit Time, ETU)

Extra Guard Time (EGT) error in ISO14443B

TR1 set by card too long in case of protocol ISO14443B

TR1 set by card too short in case of protocol ISO14443B

Hardware Communication error

Invalid command Length

Invalid Protocol

Frame waiting timeout (no valid reception) or no TAG

Invalid SOF

Receive buffer overflow (too many bytes received)

0x8A

0x8B

0x8C

0x8D

0x8E

Protocol Framing error as follows:



ISO14443A & ISO18092 (106kbps) : Modified Miller, wrong symbol sequence



ISO14443B: Start/Stop bit polarity



ISO18092 (212,424kbps): SYNC ≠ 0xB24D

EGT time out (ISO14443B)

Invalid length received during ISO18092 (212,424kbps) communication (2 < Length < 255)

CRC error in case of protocolISO18092 (212,424kbps)

Reception lost without EOF received

Table 17: List of error codes for “SendRecv” command

3901090132

Rev. 009


MLX90132


6.7 Listen command (0x05)

This command is used with the MLX90132 in Tag emulation state to listen for the command from the reader.

Before sending this command the application has to select a protocol using “Protocol Select” command with the related options.

Listen0x05

Direction Example

MCU – device

Device - MCU

Device - MCU

Data

05

00

00

00

82

00

83

Comments

Command code

Length of data

Result code

Length of data

Error code

Length of data

Error code

0500 – Listen for a request from reader

0000-

No error. Confirmation that device now is in listening mode

8200 -


Device - MCU

00 Length of data

8300 -

Invalid protocol or protocol is not supported.

Device -MCU

Device - MCU

85

00

8F

00

Error code

Length of data

Error code

Length of data

8500 -

Canceled by user using “Echo” command

8F00 -

No HF field detected, command cannot be executed

Table 18: “Listen” command description

When the “listen” command is executed and the option “Waits for field” is activated, the MLX90132 waits for the HF field activation and corresponding request coming from an RFID reader.

If the option “Return an error if no field” is activated, the MLX90132 directly returns an error if no HF field is detected.

If the HF field is interrupted by the reader while the MLX90132 is waiting for the request, it will leave the listen command and return the error code 0x8F00.To wait for new request, the application must issue a new “listen” command.

The user can cancel the “listen” mode by issuing an “echo” command 0x55. When cancelled, the MLX90132 replies with a code 0x55 (as a sync reply) plus “Cancelled by user” message corresponding to 0x85, 0x00. To cancel the “listen” mode, the following procedure should be followed:

 Send the ECHO command 0x55 to cancel the “listen” mode

 Set the pin SPI_NSS to low, to read back the buffer content

 Read the sync reply 0x55

 By keeping SPI_NSS low, read the rest of the buffer (could be cancelled by user 0x8500 message or correct data information 0x80<LEN><DATA>)

 Set the pin SPI_NSS high to continue the operation

3901090132

Rev. 009


MLX90132


Possible return codes are listed in the table below.

Respond codes from the device in Listen mode

Direction Data Comments

Device - MCU

80

<Len>

<Data>

Result code

Length of data

Data received. Interpretation depends on protocol

Device - MCU

86

00

Error code

Length of data

Device - MCU

Device - MCU

Device – MCU

87

00

88

00

89

00

8A

Error code

Length of data

Error code

Length of data

Error code

Length of data

Error code

Device – MCU

00 Length of data

Example

800605000071FF00 -

The request from the Reader is decoded. This is an example of Request in Iso14443-B protocol

8600 -

Communication error

8700 -

Listening mode was cancelled by the application

8800 -

Invalid SOF

8900 -

Receive buffer overflow

8A00 -

Protocol Framing error:

- ISO14443A & ISO18092 (106kbps): Mod. Miller, wrong symbol sequence

- ISO14443B: Start/Stop bit polarity

- ISO18092 (212,424kbps): SYNC ≠ 0xB24D

Device – MCU

Device - MCU

8B

00

8E

00

Error code

Length of data

Error code

Length of data

8B00 -

EGT time out (ISO14443B)

8E00 -

Reception lost without EOF received

Table 19: “Listen” command, possible return codes

If the request from the Reader was successfully received and decoded, the MLX90132 will send data back to the application, as shown in the following table.

Data format sent to the application in ‘Listen’ mode

Protocol Explanation Response example

Request example 80 0A 9370800F8C8E 8D 4E01 08

ISO14443A

NFC-A

Result code


Data received from reader

Received value of BCC (if any)

Received value of CRC (if any)

7 – RFU

6 – RFU

5 – CRC error

4 – Parity error

3:0 – number of significant bits in last byte

ISO14443B

NFC-B

Request example 80 06 050000 71FF 00

Result code


Data received from Reader


7:2 – RFU


0 – RFU

Request example 80 06 00FFFF0000 00

Result code

ISO18092

(212, 424kbp)

NFC-F


Data received from reader

7:2 – RFU


0 – RFU

Comments

The anti-collision filter could be activated with the command “AcFilter”. In this case, the complete anti-collision process is supported by the

MLX90132 as soon as a “Listen” command is initiated. The information will be automatically sent by the MLX90132

Table 20: Data format sent to the application in “Listen” mode

3901090132

Rev. 009


MLX90132


6.8 Send command (0x06)

This command is used with the MLX90132 in TAG emulation state, to send data back to the reader. This command sends specific protocol data without waiting for an answer.

Send 0x06

Direction Example

MCU – device

Device - MCU

Device - MCU

Data

06

<Len>

<Data>

00

00

82

00

Comments

Command code

Length of data

Data to be sent

Result code

Length of data

Error code

Length of data

Depends on protocol previously selected!

040C50920E997500000000B37171 – Emulation of TAG response in

ISO14443-B protocol

0000 -

Data was successfully sent

8200 -

Invalid length

Device - MCU

83

00

Error code

Length of data

8300 -

Invalid protocol previously selected by Select Protocol command

Table 21: “Send” command description

Format of data to be sent using ‘Send’ command

Protocol

ISO14443A

NFC-A

Explanation Response example

Send example

Command code

06 03 0400 08


Data

7:6 – RFU

5 – Append CRC

4 – RFU

3:0 – number of significant

bits in first byte

Send example 06 04 01020304

ISO14443B

NFC-B

Command code


Data

Send example 06 05 01020304 00

Command code


ISO18092

(212,424Kb)

NFC-F

Data

Slot number (in which to reply)

Comments

The anti-collision filter could be activated with the command “AcFilter”. In this case, the complete anti-collision process is supported by the

MLX90132 as soon as a “Listen” command is initiated. The information will be automatically sent by the MLX90132

The number of slot in which to reply is entered by the application in the field <Slot number>. In this case, the MLX90132 automatically manages the related timings defined by the protocol, to answer to the corresponding slot. This parameter is used for the Single Device Detection (SDD) process,

For other commands, the field <Slot number> should simply be set to zero.

Table 22: Format of data to be sent using “Send” command

3901090132

Rev. 009


MLX90132


6.9 Idle command (0x07)

This command is used to switch the MLX90132 into low-power mode. Several sub-modes or states could be selected as shown in the table below. Please note that except when an error occurs (the answer is then directly sent), the response to an Idle command is sent only when the MLX90132 exits the low-power mode.

Idle0x07

Direction Data

07

Comments

Command code

Example

0E Length of data

<WUFlags>

Specifies wake-up sources and LFO

frequency. Refer to Table 24

MCU – device

<EnterCtrlL>

<EnterCtrlH>

<WUCtrlL>

<WUCtrlH>

<LeaveCtrlL>

<LeaveCtrlH>

<WUPeriod>

<OscStart>

<DacStart>

2 bytes: Settings to enter Idle mode, refer to

Table 25 below

2 bytes: Settings to wake-up from Idle mode

(recommended value = 0x3800), refer to

Table 25 below

2 bytes: Settings to leave Idle mode

(recommended value = 0x1800), refer to

Table 25 below

Period of time between two TAG detection bursts. Also used to specify the duration before

timeout. Refer to Equation 1

Waiting time for the HFO to stabilize (based time: LFO), recommended value = 0x60

Waiting time for the DAC to stabilize (based time: LFO), recommended value = 0x60

0x070E 0A 210038011800086060

54603F00

– Tag detector with

LFO set at 32kHz. Possibility to

WU on low level IRQ

IN

0x070E CB 210038011800086060

54603F10

– Tag detector with

LFO set at 4kHz

.

Possibility to

WU on low level IRQ

IN

and timeout (MaxSleep set to 0x10)

Device– MCU

Device – MCU

<DacDataL>

<DacDataH>

<SwingsCnt>

<MaxSleep4:0>

0x00

0x01

<WUFlags>

0x82

0x00

Lower compare value for TAG detection. Note:

Only the 6 MSB bits are available

Higher compare value for TAG detection. Note:

Only the 6 MSB bits are available

Number of HF periods during TAG detection.

Refer to Equation 2 .

Maximal number of TAG detection trials before timeout. Value set to 0 during TAG detection calibration.

0x00 <MaxSleep< 0x1F (bit 7 to 5 are RFU and must be set to 0)

Also used to specify duration before timeout,

refer to Equation 3

.

Result code

Length of data

Content of WUFlags, please refer to Table 24

below

Error code

Length of data

Table 23: “Idle” command description

0x0001XX -

Here XX is a value of

WUFlags, please note that this

response is sent only when device exits idle mode

0x8200 –


3901090132

Rev. 009


MLX90132


Meaning of Wake-up settings <WUFlags>

A Register Bit

7:6 – LfoPresc

Function

LFO prescaler. Divides LFO for state machine.

00 – 32 KHz

01 – 16 KHz

10 – 8 KHz

11 – 4 KHz

2 WUFlags

5 – RFU, set to ‘0’

4:0 – WUFlags

Specifies the possible source on which to exit from idle mode, incase SLEEP state is selected. Each bit corresponds to one wake-up source which is updated and returned when the MLX90132 leaves the Idle routine without error bit4 - Low level on SPI_NSS bit3 – Low level on IRQ_IN, must be set to ‘1’ bit2 – Field Detector bit1 – TAG Detector bit0 – WakeUp(WU at the end of MaxSleep cycles even if no event detected)

Table 24: Field <WUFlags> definition in “Idle” command

Meaning of power settings <EnterCtrlH:EnterCtrlL>, <WUCtrlH:WUCtrlL> and <LeaveCtrlH:LeaveCtrlL>

A Register

0 CtrlL

Comment

7 – Initial DAC compare index (‘0’ = DacDataL, ‘1’ = DacDataH used for the 1 st

6 – RFU, must be set to ‘0’

comparison)

5 – LFO enable(needs to be set to ‘1’ in WUCtrl)

4 – HFO enable (needs to be set to ‘1’ in WUCtrl)

3 – VDDA enable (needs to be set to use HFO, see recommended values in Table 23 above)

2 – Hibernate state enable

1 – RFU

0 – Sleep state enable

1 CtrlH

7:2 – RFU, must be set to ‘0’

1 – Field detector enable

0 – IREF (needs to be set to ‘1’ in WUCtrl, otherwise must be put to ‘0’)

Table 25: Fields <EnterCtrl>, <WUCtrl> and <LeaveCtrl> definition in “Idle” command

Notes:

 The bytes <EnterCtrl> define the configuration when entering the IDLE mode. The bytes <WUCtrl> define

the configuration when the device wakes-up from the IDLE mode (recommended value 0x3801). The bytes <LeaveCtrl> define the configuration when leaving the IDLE mode, after wake-up.

 The Hibernate state is entered by setting the “Hibernate state enable” flag to ‘1’ and the Sleep state is

entered by setting the “sleep state enable” flag to ‘1’, both in the WUFlags register.

Equation 1: Sleep period

( )

Equation 2: HF ON period

Equation 3: Duration before Timeout

With:

( ) ( )

and

[s]

3901090132

Rev. 009


MLX90132


6.10 BaudRate command (0x0A)

This command is used to change the UART baud rate.

Set UART baud rate 0x0A

Direction Data

0A

01

Comments

Command code

Length of data

MCU – device

<BR_Ratio>

New BR ratio = <BR_Ratio>*2+2

See following table:

Baud rate ratio

255 – 13.56/512 ~26.48kbps

254 – 13.56/510 ~26.59kbps

253 – 13.56/508 ~26.7kbps

. . .

117 – 13.56/236 ~57.7kbps (default value)

. . .

2 – 13.56/6 ~2.26Mbps

1:0 – Not used

Example

Device - MCU 55 “Echo” code of 0x55

55 -

New baud rate is used to reply

Table 26: “Baudrate” command description

6.11 SubFreqRes command (0x0B)

This command returns the last sub-carrier frequency measured during communication. It is used to measure the data-rate for protocols ISO/IEC18092 (212,424Kbps) / NFC-F. Please note that this operation is automatically performed by the MLX90132 when configured in Tag emulation mode, ISO/IEC18092 & NFC-F.

SubFreqRes0x0B

Direction Data

MCU – device

0B

00

00

01

Device - MCU

<FreqSc_Ratio>

Comments

Command code

Length of data

Result code

Length of data

Ratio of measured sub-carrier

frequency, refer to

Equation

4

Example

0B00

00010F -

Here 0F is a frequency divider. Use this value to configure the MLX90132

Table 27: “SubFreqRes” command description

SubFreqRes reports the frequency divider. To calculate the real frequency use this formula

Equation 4: Byte FreqSc_Ratio calculation:

( )

3901090132

Rev. 009


MLX90132


6.12 AcFilter command (0x0D)

This command is used with the MLX90132 in TAG emulation, ISO/IEC14443-A. If activated, it autonomously handles the anti-collision algorithm. If not activated, all received commands will be sent to the application.

If the filter is activated, the MLX90132 will interpret the ISO/IEC14443-A commands sent by the reader and performs the anti-collision procedure. In this case, data will be sent to the external microcontroller only when the anti-collision procedure is finished.

Activate/deactivate anti-collision filter 0x0D

Direction Data Comments

0D

<Len>

Command code

MCU – device

<ATQA>

(2bytes, LSByte 1st)

<SAK>

<UID part 1>


<UID part 2>


Length of data

Coding of ATQA, answer to

REQA command (refer to

ISO/IEC14443A standard)

Coding of SAK, select acknowledgement (refer to

ISO/IEC14443A standard)

UID for cascade level 1

(Mandatory)


(Optional)

<UID part 3>



(Optional)

Example

0D0B4400AA8804485BA1120000 -

Activate filter for 2-cascade anti-collision

Note that length can be

7 – for 1-cascade level filter

11 – for 2-cascade levels filter

15 – for 3-cascade levels filter

All other values will cause ‘Invalid command length’ error.

0D00 – Return AC state and deactivate AC filter

0D01XX – Force AC state to XX value

0D020000 – Returns AC state without deactivating filter

00 Result code

Device - MCU

00 Length of data = 0

0000 -

Filter is successfully activated/deactivated

Device - MCU

Device - MCU

82

00

83

00

Error code

Length of data

Error code

Length of data

8200 -


8300 -

Invalid protocol

Table 28: “AcFilter” command description

The MLX90132 is able to interpret and respond to the following commands:

Anti-collision commands supported by the MLX90132

Command Code

REQA 26 (7-bit)

WUPA

ANTICOLL

SELECT

52 (7-bit)

93, 95, 97

9370, 9570, 9770

Definition

Sense request

WU all request

Single device detection request

Select request

Table 29: ISO/IEC14443-A anti-collision commands supported by the MLX90132

Notes:

 The current anti-collision state can be forced using the command 0x0D01XX, with XX selected according

to Table 30 below.

 Command 0x0D020000 can be used to return the current anti-collision state without deactivating the anti-

collision filter. Please refer to Table 30 below for the anti-collision state.

 The command 0x0D00 will be used to return the current anti-collision state and deactivate the anticollision filter.

 UID part 2 and 3 are optional and may not be included in the command. The UID size, as defined in the

ISO/IEC14443A standard (part of the ATQA), will be updated automatically by the MLX90132 according to the UID length.

3901090132

Rev. 009


MLX90132


Actual state returned by the MLX90132

Value State

0x00

0x01

IDLE

READY_1

0x02

0x03

0x04

READY_2

READY_3

ACTIVE

0x80

0x81

0x82

0x83

0x84

HALT

READY*_1

READY*_2

READY*_3

ACTIVE*

Comment

IDLE state

READY state after 1 st

part of UID is verified

READY state after 2

READY state after 3 nd

part of UID is verified rd

part of UID is verified

ACTIVE state

HALT state

READY* state after 1

READY* state after 2 st nd

part of UID is verified part of UID is verified

READY* state after 3 rd part of UID is verified

ACTIVE* state

Table 30: Current state returned by the MLX90132 (as defined in ISO/IEC14443-A standard)

7 Modifying internal settings for optimal performances

7.1.1 Example: How to modify the ARC_B register

The internal registers of the MLX90132 are automatically set when the protocol is selected with the command

Protocol select command (0x02) . To get optimal performance, the internal register ARC_B containing the

modulation index of the RFID request and the analog gain for the reception chain in reader mode can be modified. The following example shows the specific commands to be sent to read/write the register ARC_B:

Use the “Protocol Select” command (0x02) to select the appropriate communication protocol.



Send Protocol Select command (for example ISO/IEC14443A):



MLX90132 reply:

Read Analog Configuration register (ARC_B) value



Write the ARC_B register index to 0x01:



MLX90132 reply:



MLX90132 reply:

Modify the value of Analog Register Configuration (ARC_B) to 0x23



Write the ARC_B register:



Read the ARC_B register value:



MLX90132 reply:

Read back the Analog Configuration register (ARC_B) value



Write the ARC_B register index to 0x01:



MLX90132 reply:



Read the ARC_B register value:



MLX90132 reply:

0x02020200

0x0000

0x0903680001

0x0000

0x0803690100

0x01DF

(1)

0x090468010123

0x0000

0x0903680001

0x0000

0x0803690100

0x0123

(1)

In this example, the ARC_B register = 0xDF with ‘D’ = Modulation Index & ‘F’ = Rx amplifier gain.

3901090132

Rev. 009


MLX90132


The content of the register ARC_B is shown in Table 31 below with the default values in Table 32 :

ARC_B register of the MLX90132

A Register Bit

69 ARC_B

7:4 ModIdx

(1)

3:0 Rx Gain

(2)

Function

ASK Modulation Index :

Code 1 = 10%

Code 2 = 14%

Code 3 = 18%

Code 4 = 21%

Code 5 = 24%

Code 6 = 26%

Code 7 = 30%

Code 8 = 35%

Code 9 = 39%

Code A = 40%

Code B = 43%

Code C = 45%

Code D = 96%

Reception chain amplifier Gain:

Code 0 = 34dB

Code 1 = 32dB

Code 3 = 27dB

Code 7 = 20dB

Code F = 8dB

Table 31: Register ARC_B description

(1) Characterized using ISO/IEC10373-6 setup and DVK90132 antenna matching

(2) Defined by design simulations

Communication protocol Default value

ISO/IEC14443 Type A

ISO/IEC14443 Type B

ISO/IEC18092 (Felica)

ISO/IEC 15693 – 10%

0xDF

0x20

0x50

0x53

ISO/IEC15693 – 100% 0xD3

Table 32: Default value of ARC_B per protocol (Reader mode)

7.1.2 Example how to read back WUFlags content

WUFlags byte (refer to

Table 24 ) is automatically updated after the MLX90132 wakes-up from an Idle

command. In SPI mode, this byte is available to read in the FIFO register. In UART mode, this byte is asynchronously sent after wake-up. In some cases, it is useful to be able to check the WUFlags separately; the example below shows how to do it:

Read WUFlags register value



Read the WUFlags register value:



MLX90132 reply:

0x0803620100

0x0001XX

(1)

(1)

XX equal the WUFlags register value

3901090132

Rev. 009


MLX90132


8 Tag Detector

8.1

Operating Principle

The objective of the TAG detector function is to be able to detect the presence of an RFID label/tag or an

NFC device in front of the reader’s antenna, with reduced power consumption.

The TAG detector function is based on the detection of any variation of the HF field. If an RFID transponder or an NFC device approaches the reader’s antenna, it influences the amplitude of the generated HF by a loading effect. This variation can be monitored by the MLX90132 to inform the external host microcontroller that an RFID transponder or an NFC device is approaching the antenna.

When set in TAG detector state, the MLX90132 periodically generates a few periods (pulses) of HF carrier frequency and measures the amplitude’s field. This value is then compared to reference levels

DacDataH[7:0] and DacDataL[7:0] defined by the user.

If the measured level is above DacDataH[7:0] or below DacDataL[7:0], - i.e. a change in the amplitude of the

HF field occurs - the MLX90132 automatically informs the external application MCU by: either generating an

IRQ on the pin IRQOUT (SPI interface), or directly sending the WUFlag register value (UART interface).In the

same time it enters to Ready state and waits for a Protocol select command (0x02) command. Therefore,

either the application MCU takes the control of the MLX90132 by sending a command

Protocol select command (0x02) and can decide to start communicating with the TAG, or the MLX90132 goes back in idle

(tag detector) mode. This mechanism is repeated until a new object is detected in the field or another kind of event appears (e.g. max number of trials reached, wake-up from host MCU …).

Before using this feature it is necessary to perform a calibration by using the MCU

The TAG detector state is entered using the

Idle command (0x07) command. The values of

DacDataH/DacDataL[7:0] are defined in this command, as well as the number of HF pulses and the time between two HF bursts with respectively the bytes SwingsCnt[7:0] and WUPeriod[7:0]. The MLX90132 can be forced to wake-up after a certain number of trials, even if no TAG has been detected. This number of trials is set using the bits MaxSleep[4:0].

The bit “initial DAC compare index” in register EnterCtrlL is used to select the first comparison to be performed when starting the TAG detector state. When set to ‘0’, the TAG detector feature is started with a comparison to DacDataL[7:0].If set to ‘1’, the TAG detector feature is started with a comparison to

DacDataH[7:0]. Please note that the IREF bit in EnterCtrlH byte has to be set to allow a proper functionality of the TAG detector feature.

The following picture illustrates the TAG detector operation described above.

TAG detection function

New-calibration

DacDataH

DacDataL

3901090132

Rev. 009

Very short impulses of HF field are generated (defined by the byte

SwingsCnt in IDLE command)

WUPeriod

If the field is detected out of the range defined by DacDataL and DacDataH, the device wakes-up

Device wakes-up again if detected out of the new range defined by

DacDataL and DacDataH

Then the host MCU can take the control of the communication, trying to detect any TAG. If no TAG is detected, a new calibration might be done to compensate any change of environment

Figure 11: MLX90132 TAG detection principle


MLX90132


8.2 Calibration procedure

The calibration process should be performed with no tag in the environment. It consists of executing a successive tag detection sequence using a well-known configuration. This to determine the two specific reference thresholds: DacDataL and DacDataH which will be programmed in the device before entering Tag

Detector Mode. Both thresholds are coded in 6 bits.

During the calibration process, DacDataH value is fixed to 0xFCand the software will vary the DacDataL value from its minimum value (0x00) to its maximum value (0xFC). At each step, the WUflags byte is read to know if the HF level is above or below the low threshold (“tag detected flag” set or not).

At the end of the calibration process, the reference level DacDataRef is found and corresponds to the value of DacDataL for which the wake-up event switches from “WakeUp at the end of MaxSleep cycles” (no tag in the RF field) to “tag detected”.

To avoid too much sensitivity in the tag detection process, the use of a guard band is recommended. This value should correspond to at least 2 DAC steps.

Final recommended values with guard band:

 DacDataL= DacDataRef– Guard

 DacDataH= DacDataRef+ Guard

The parameters used to define the tag detection calibration sequence (clocking, set-up time, burst duration, etc.) must be the same as those used for the future tag detection sequences. MaxSleep has to be set to ‘0’ for the calibration

Another and faster way (binary search: 6 steps) to calibrate the Tag Detector is described in the application note AN2_MLX90130_32_TagDetector .

9 Field Detector

The MLX90132 embeds a field detector block to measure the field level of an external HF RFID reader. This is used to be able to monitor the availability of the channel and perform the collision avoidance feature before switching ON the HF field.

The command “Poll field” can be used to monitor the HF field, the device directly returns a bit indicating that an HF field has been detected or not. The field detector can also be configured as an option to wake-up from

“Idle” mode, in order to reduce the power consumption as much as possible.

3901090132

Rev. 009


MLX90132


10 Electromagnetic support (EMD)

The electromagnetic disturbance results in the noise that a passive/active TAG or NFC device generates before answering to a corresponding request. This disturbance is generally due to the digital processing of the passive/active TAG or NFC device which appears just before sending back the response.

The MLX90132 device supports a specific algorithm to filter EMD disturbances to successfully receive the frame from a passive/active TAG or NFC device. This algorithm is supported within the MLX90132 in Reader modes ISO14443 type-A and type-B.

The following flow-charts illustrate the algorithm which is implemented in the MLX90132 device for these 2

modes of operation. The corresponding EMD algorithm is selected with the Protocol select command (0x02)

by configuring the parameter <N

EMD

> with a non-null value. The definition of the two values <N

> used in the algorithm are defined below:

EMD

> and

<N

EMD,RES

 <N

EMD

>: Maximum Number of non-valid Bytes received, before the system leaves the EMD algorithm routines with an error message. Typically, this value is set to 3 or 4, meaning that failing reception with less than 3 or 4 Bytes will be considered as EMD disturbance by the algorithm without interrupting the reception process.

 <N

>: Maximum Number of non-valid and non-Integer Bytes received, before the system leaves

EMD,RES

the EMD algorithm routines with an error message. Typically, this value is set identical to the N

EMD

value.

When processing the EMD algorithm, the MLX90132 is in kind of “standalone” mode, waiting for the presence of a valid <Start Of Frame> coming for the passive/active TAG or NFC device. This “standalone” mode only terminates with the following conditions:

1) At the end of a valid reception

2) In case a timeout error occurs (FDT/FWT time reached without valid SOF)

3) In case the identified error could be assimilated as a protocol error and not to EMD

During the whole EMD process, the MLX90132 is buffering the incoming errors which will be returned to the host application in case one of the conditions 2) or 3) above is reached. In this case, the error code returned will be as follows:

<ErrorCode> + <ErrorBufLen> + <ErrorBuf> with

 <ErrorCode>: Last error code raised during the EMD algorithm

 <ErrorBufLen>: Length of the following Buffer of Errors (max. 8 bytes)

 <ErrorBuf>: Buffer of Errors stored during the EMD algorithm (max. 8 bytes)

3901090132

Rev. 009


MLX90132


Start ISO14443 Type A

Reception

Initialize CRC calculation

Error 0x61 stored in Buffer

SOF error or invalid

Wait for SOF

Reception Timeout (FDT expires)

YES, Valid SOF received

Error 0x87 returned

NO

Store received data

& wait for EOF

YES, Valid EOF received

Residual bits found?

NO, data received equals to an entire nbr of symbols (1Byte + Parity bit)

YES, data received NOT equal to an entire nbr of symbols (1Byte + Parity bit)

Return code 0x90 or 0xB0

or 0xD0 (Data Rx without an integer nbr of byte)

Nbr of Byte >

NemdRes?

YES

NO, Manchester violation detected

Successful data received?

YES

CRC error?

YES

NO

Return code 0x80 or

0xA0, or 0xC0

(reception OK)


0xA0 or 0xC0

(CRC error bit is set)

Nbr of Byte <

Nemd?

YES


End of Algorithm

Return Flag + Data or Error code

Figure 12: MLX90132 EMD Algorithm Reader/Writer ISO14443 Type A

3901090132

Rev. 009


MLX90132


Start ISO14443 Type B

Reception

Initialize CRC calculation

Wait for Sub-carrier

Reception Timeout (FWT expires)


TR1 < TR1_MIN

Check TR1

TR1 > TR1_MAX


1 st part of SOF not correctly received

Decode 1 st part of

SOF

1 st part of SOF correctly received

(between 10 and 11 ETUs)


2 nd part of SOF not correctly received

Wait for 2 nd part of

SOF

2 nd part of SOF correctly received

(between 2 and 3 ETUs)

NO

Nbt Byte > Nemd

YES


EGT incorrect

Receive data

Framing error or

EOF received

Error 0x8A stored in Buffer

NO

EOF received?

YES


CRC error

NO

YES

NO

NemdRes = 0?

YES


0xA0 or 0xC0



0xA0, or 0xC0

(reception OK)

Return code 0x67 Return code 0x87

3901090132

Rev. 009


0xA0 or 0xC0


End of Algorithm

Return Flag + Data or Error code

Figure 13: MLX90132 EMD Algorithm Reader/Writer ISO14443 Type B

Jan-2014 Page 36 of 44

MLX90132


11 Application Information

11.1 External Antenna network

RF communication performance depends on the external system antenna network and resonance conditions.

The antenna matching of the MLX90132 is reduced to a minimal component count, composed of two serial capacitors Cs and one parallel capacitor Cp. A parallel resistor Rp can also be added to adjust the antenna damping thus reducing detuning effect provoked by the presence of TAGs or Readers in front of the

MLX90132. Two serial resistors R

RX

have to be adjusted in order to avoid entering the clamping region (see

Table 36 below). Finally, depending on EMC constraints, an EMI filter can be added to reduce the emission

of harmonics generated by the square wave at the outputs TX1 and TX2.

Figure below gives an example of the external matching network to connect the antenna. For more information, please refer to the application note AN1_MLX90130_32_AntennaDesignGuidelines available on the Melexis website.

R

RX

R

X1

L

EMI

C

S

T

X1

C

EMI

C

P

R

P

MLX90132

L

EMI

C

EMI

C

S

T

X2

R

RX

R

X2

Figure 14: External antenna matching network example

11.2 Application schematic

VDD

Antenna Matching

27.12MHz

GND_DIG

XIN

XOUT

GND_TX

VDD_TX

TX1

TX2

NC

Example of

EMI Filter

MLX90132

VDD

IRQ

IN

VDC

RX1

RX2

GND_RX

NC

NC

VDD

Figure 15: MLX90132 application schematic in SPI mode

Application

Microcontroller

3901090132

Rev. 009


MLX90132


12 Electrical Specifications

12.1 Absolute Maximum Ratings

Parameter

Supply Voltage

Supply Voltage

Input or Output voltage relative to Ground

Operating Temperature Range

Storage Temperature Range

Electrostatic discharge according to AEC-Q100-

002 Human Body Model

Symbol

V

DD

V

DD_TX

VIO

T

A

T

S

V

ESD_HBM

Value

-0.3 to 7.0

-0.3 to 7.0

-0.3 to VDD+0.3

-40 to 105

-40 to 150

2

Units

V

V

V

C

C kV

Table 33: Absolute maximum ratings

Note: Exceeding the absolute maximum ratings may cause permanent damage. Exposure to absolute-maximum-rated conditions for extended periods may affect device reliability.

12.2 DC Characteristics

Operating Parameters T

A

Parameter

= -40 o

C to 105 o

C

Supply voltage

Supply voltage of TX driver

Symbol

V

DD

V

DD_TX

Conditions Min Typ Max Units

Table 34: DC characteristics

2.7

2.7

5

5

5.5

5.5

V

V

12.3 Power Consumption Characteristics


A

Parameter

= -40 o

C to 105 o

Supply current in Hibernate state

C(2.7 < VDD/VDD_TX <5.5V)

Symbol

Icc

Hibernate


1 8 μA

Supply current in Sleep state

Supply current in Ready state

Supply current in RF Reader ON

Supply current in Card Emulation state

Supply current in Tag Detection state

Icc

Sleep

Icc

Ready

Icc

RF Reader ON

Icc

Card Em

Icc

Tag Det

20

2.5

100

(1)

1

45

(1,2)

30

3

3

μA mA mA mA

μA

Table 35: Power consumption characteristics

1. Parameter measured at applicative level only, using recommended output matching network

2. Following specific conditions for TAG detection: T

A

SwingCnt = 0x3F

= 25°C, WUPeriod = 0x1A (4x per seconds), OscStart= 0x60, DACStart= 0x60,

3901090132

Rev. 009


MLX90132


12.4 RF Characteristics


A

Symbol

= -40 o

C to 105 o

C (2.7 <VDD/VDD_TX<5.5V)

Parameter

f

C

Frequency of operating field (carrier frequency)

Carrier modulation index

(3)

ISO/IEC14443A

ISO/IEC14443B

ISO/IEC18092

ISO/IEC15693 (10% modulation)

ISO/IEC15693 (100% modulation)

Min Typ Max Units

13.553 13.56 13.567 MHz

8

8

10

80

100

14

14

30

100

%

Transmitter specifications

R

ON_3V

R

ON_5V

P

OUT_3V

P

OUT_5V

Equivalent resistor of driver output TXn

(2)

Equivalent resistor of driver output TXn

(2)

Output power for 3V operation

(2)

Output power for 5V operation

(2)

Receiver specifications

Z

OUT

Differential. input resistance between RX1/RX2

(2)

C

INPUT

Differential. input capacitance between RX1/RX2

(2)

V

SENS

V

RXMAX

Sensitivity

(3)

Clamping voltage on RX1 (RX2) relative to

Ground

(2)

Table 36: Reader characteristics

9.5

Symbol

H

Threshold

Parameter

HF field level of detection

(2,3)

Min

0.1875

Table 37: Field detection characteristics

1. Parameter measured using recommended output matching network

2. Value based on design simulation and/or characterization results, and not tested in production

3. Based on ISO/IEC 10373-6 & 22536 protocol measurements

80

22

6

11

13

8

70

317

Typ

13.2

Max

Ω

Ω mW mW kΩ pF mVp

Vp

Units

A/m

3901090132

Rev. 009


MLX90132


12.5 SPI Characteristics

Symbol

f

SCK

V

IL

V

IH

V

OL

V

OH t

SU(NSS)

(1) t h(NSS)

(1) t

CH(SCKL)

(1) t

CH(SCKH)

(1) t

SU(SI)

(1) t h(SI)

(1) t v(SO)

(1) t h(SO)

(1)

C b_SPI_IN

C b_SPI_OUT

Parameter

SPI clock frequency

Input low voltage

Input high voltage

Output low voltage

Output high voltage

NSS setup time

NSS hold time

Clock low time

Clock high time

Data slave Input setup time

Data slave Input hold time

Data slave output valid time

Data slave output hold time

Capacitive load for input pins NSS, CLK, MOSI

Capacitive load for input pins MOSI

Table 38: SPI interface characteristics

1. Values based on design simulation and/or characterization results, not tested in production

Min

0.7*V

DD

0.7*V

DD

Typ

200

200

20

150

280

70

0

Max Units

2 MHz

80

3

20

0.3*V

DD

0.4*V

DD

V ns pF

Figure 16: SPI timing diagram (Slave mode and CPOL = 0, CPHA = 0)

3901090132

Rev. 009

Figure 17: SPI timing diagram (Slave mode and CPOL = 1, CPHA = 1)


MLX90132


12.6 Oscillator Characteristics

Symbol Parameter

Low Frequency Oscillator (LFO)


f

LFO

Low-frequency oscillator (LFO)

XTAL Oscillator

20 32 43 kHz f

XTAL

R

F

C

L

XTAL Oscillator frequency

Feedback resistor

Recommended load capacitance versus equivalent serial resistance of the crystal

(RS)

(3)

Rs = 30Ω

27.12

2

12

MHz

MΩ pF

I

2

XTAL driving current

(2)

VDD = 3.3V with

12pF load

600 750 µA g m t

SU(HFO)

(4)

Oscillator transconductance

(2)

Oscillator start-up time

Start-up

VDD is stabilized

0.04 0.32

2

1.41 mA/V ms

Table 39: Oscillator characteristics

1. Resonator characteristics given by the crystal/ceramic resonator manufacturer.

(1) (2)

2. Based on characterization, not tested in production.

3. The relatively low value of the RF resistor offers good protection against issues resulting from use in a humid environment, due to the induced leakage and the bias condition change. However, it is recommended to take this point into account if the application is used in severe humidity conditions.

4. tSU (HFO) is the startup time measured from the moment it is enabled (by software) until a stabilized 27.12MHz oscillation is reached.

This value is measured for a standard crystal resonator and it can vary significantly with the crystal manufacturer.

For C

L1 and C

L2

, it is recommended to use high-quality external ceramic capacitors in the 10 pF to 20 pF range, designed for high-frequency applications, and selected to match the requirements of the crystal or

resonator (see Figure 18 ). C

L1 and C

L2 are usually the same size. The crystal manufacturer typically specifies a load capacitance which is the series combination of C

L1 and C

L2

.

MLX90132

CL1

X

IN

R

F

CL2

X

OUT

÷2 f

HFO

Figure 18: Typical application with a 27.12MHz crystal

3901090132

Rev. 009


MLX90132


14 ESD Precautions

Electronic semiconductor products are sensitive to Electro Static Discharge (ESD).

Always observe Electro Static Discharge control procedures whenever handling semiconductor products.

15 Standard information regarding manufacturability of Melexis products with different soldering processes

Our products are classified and qualified regarding soldering technology, solderability and moisture sensitivity level according to following test methods:

Reflow Soldering SMD’s (Surface MountDevices)

 IPC/JEDEC J-STD-020

Moisture/Reflow Sensitivity Classification for Nonhermetic Solid State Surface MountDevices

(classification reflow profiles according to table 5-2)

 EIA/JEDEC JESD22-A113

Preconditioning of Nonhermetic Surface MountDevices Prior to Reliability Testing

(reflow profiles according to table 2)

Wave Soldering SMD’s (Surface MountDevices) and THD’s (Through Hole Devices)

 EN60749-20

Resistance of plastic- encapsulated SMD’s to combined effect of moisture and soldering heat

 EIA/JEDEC JESD22-B106 and EN60749-15

Resistance to soldering temperature for through-hole mounted devices

Iron Soldering THD’s (Through Hole Devices)

 EN60749-15

Resistance to soldering temperature for through-hole mounted devices

Solderability SMD’s (Surface MountDevices) and THD’s (Through Hole Devices)

 EIA/JEDEC JESD22-B102 and EN60749-21

Solderability

For all soldering technologies deviating from above mentioned standard conditions (regarding peak temperature, temperature gradient, temperature profile etc) additional classification and qualification tests have to be agreed upon with Melexis.

The application of Wave Soldering for SMD’s is allowed only after consulting Melexis regarding assurance of adhesive strength between device and board.

Melexis recommends reviewing on our web site the General Guidelines soldering recommendation

( http://www.melexis.com/Quality_soldering.aspx

) as well as trim&form

(http://www.melexis.com/Assets/Trim-and-form-recommendations-5565.aspx).

recommendations

Melexis is contributing to global environmental conservation by promoting lead free solutions. For more information on qualifications of RoHS compliant products (RoHS = European directive on the Restriction Of the use of certain Hazardous Substances) please visit the quality page on our website: http://www.melexis.com/quality.aspx

3901090132

Rev. 009


16 Package Information

MLX90132


Page 43 of 44

Moisture Sensitivity Level is MSL3, according as per IPC/JEDEC J-STD-20.

This table in mm

Type DxE N e A A1 A3 D2 E2

3.00

3.20

3.00

3.20 quad 5 x 5

32

(Opt B)

Tolerance of D, E: +/- 0.1mm

0.50 min 0.80 0.00

0.20 max 1.00 0.05

REF

3901090132

Rev. 009

L K

0.35 0.20

0.45 –

b

0.18

0.30

Jan-2014

MLX90132


17 Disclaimer

Devices sold by Melexis are covered by the warranty and patent indemnification provisions appearing in its

Term of Sale. Melexis makes no warranty, express, statutory, implied, or by description regarding the information set forth herein or regarding the freedom of the described devices from patent infringement.

Melexis reserves the right to change specifications and prices at any time and without notice. Therefore, prior to designing this product into a system, it is necessary to check with Melexis for current information. This product is intended for use in normal commercial applications. Applications requiring extended temperature range, unusual environmental requirements, or high reliability applications, such as military, medical lifesupport or life-sustaining equipment are specifically not recommended without additional processing by

Melexis for each application.

The information furnished by Melexis is believed to be correct and accurate. However, Melexis shall not be liable to recipient or any third party for any damages, including but not limited to personal injury, property damage, loss of profits, loss of use, interrupt of business or indirect, special incidental or consequential damages, of any kind, in connection with or arising out of the furnishing, performance or use of the technical data herein. No obligation or liability to recipient or any third party shall arise or flow out of Melexis’ rendering of technical or other services.

© 2012 Melexis NV. All rights reserved.

18 Contact Information

For the latest version of this document, go to our website at:

www.melexis.com

Or for additional information contact Melexis Direct:

Europe, Africa, Asia: Americas:

Phone: +32 1367 0495 Phone: +1 248-306-5400

E-mail: [email protected]

E-mail: [email protected]

ISO/TS 16949 and ISO14001 Certified

3901090132

Rev. 009


Mouser Electronics

Authorized Distributor

Click to View Pricing, Inventory, Delivery & Lifecycle Information:

Melexis

:

MLX90132RLQ-AEA-000-RE MLX90132SLQ-AEA-000-RE MLX90132RLQ-AEA-000-SP MLX90132SLQ-AEA-000-

SP

MLX90132 13.56MHz RFID / NFC Transceiver Features and Benefits Application Examples

Features and Benefits

Ordering Information

Application Examples

Functional Diagram

Description

START

Supply OFF

Power-up

Sleep

Ready

Hibernate

ACTIVE

Reader/TAG emulation

IDLE

TAG detector

5.2.1 Polling mode

5.2.2 IRQ mode

6.6.1 Support of extended frames

6.6.2 List of Error codes

7.1.1 Example: How to modify the ARC_B register

7.1.2 Example how to read back WUFlags content

www.melexis.com

Mouser Electronics

Authorized Distributor

Click to View Pricing, Inventory, Delivery & Lifecycle Information:

Melexis

:

Related manuals

Third Millennium Systems

UTJ-RX60

IFM

CR3130

Melexis

DVK90132

An Energy Technology

W015CN-01 Vehicle-Mounted 15W Wireless Charging Seat

GIGA-TMS

WXAUHF860

Fuji Film

W2Z-03000001

STMicroelectronics

UHF, EPCglobal Class 1b, Contactless Memory Chip 96 bit ePC

STMicroelectronics

Near field communication transceiver

STMicroelectronics

ST25R95

STMicroelectronics

CR95HF

STMicroelectronics

ST95HF