RX95HF-VMD5T

RX95HF Near field communication transceiver for tag emulation Datasheet - production data Applications Typical protocols supported:  ISO/IEC 14443-3 Type A tag emulation Typical RX95HF applications include:  Keyboard, laptop, set top box, printer, TV, etc.  Identification, item pairing and data exchange VFQFPN32 5x5 mm Features  Operating mode supported: – Tag Emulation for passive peer-to-peer communication  Hardware features – Dedicated internal frame controller – Highly integrated Analog Front End (AFE) for RF communications – Transmission and reception modes in Tag Emulation mode – Optimized power management – Field Detection mode  RF communication @13.56 MHz – ISO/IEC 14443 Type A in Tag Emulation mode  Communication interfaces with a Host Controller – Serial peripheral interface (SPI) Slave interface – Up to 256-byte command/reception buffer (FIFO)  32-lead, 5x5 mm, very thin fine pitch quad flat (VFQFPN) ECOPACK®2 package June 2014 This is information on a product in full production. DocID023884 Rev 3 1/44 www.st.com Contents RX95HF Contents 1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1 Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 List of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2 Pin and signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3 Power management and operating modes . . . . . . . . . . . . . . . . . . . . . . . 8 4 3.1 Operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.2 Startup sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Communication protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1 5 Serial peripheral interface (SPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.1 Polling mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.2 Interrupt mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.1 Command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.2 List of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.3 IDN command (0x01) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.4 Protocol Select command (0x02) description . . . . . . . . . . . . . . . . . . . . . . 15 5.5 Pollfield command (0x03) description . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.6 Listen command (0x05) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.7 Send command (0x06) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.8 Idle command (0x07) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.8.1 Idle command parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.8.2 Optimizing wake-up conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.8.3 Using various techniques to return to Ready state . . . . . . . . . . . . . . . . 21 5.9 Read Register (RdReg) command (0x08) description . . . . . . . . . . . . . . . 22 5.10 Write Register (WrReg) command (0x09) description . . . . . . . . . . . . . . . 23 5.10.1 2/44 Improving RF performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.11 AcFilter command (0x0D) description . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.12 Echo command (0x55) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 DocID023884 Rev 3 RX95HF 6 Contents Electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.1 Absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.2 DC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.3 Power consumption characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.4 SPI characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.5 RF characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.6 Oscillator characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 7 Package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 8 Part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Appendix A Card emulation communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 DocID023884 Rev 3 3/44 3 Description 1 RX95HF Description The RX95HF is an integrated transceiver IC for contactless applications. The RX95HF embeds an Analog Front End to provide the 13.56 MHz Air Interface. The RX95HF supports ISO/IEC 14443 Type A communication in Tag Emulation mode. Figure 1. RX95HF application overview Interrupt Management RX95HF SPI 1.1 Block diagram Figure 2. RX95HF block diagram 4/44 DocID023884 Rev 3 Host Controller (MCU) RX95HF 1.2 Description List of terms Table 1. List of terms Term Meaning GND Ground HFO High frequency oscillator LFO Low frequency oscillator MCU Microcontroller unit NFC Near Field Communication RFID Radio Frequency Identification RFU Reserved for future use SPI Serial peripheral interface tL Low frequency period tREF Reference time WFE Wait For Event DocID023884 Rev 3 5/44 7 Pin and signal descriptions 2 RX95HF Pin and signal descriptions ST_R3 NC NC NC NC XIN XOUT ST_R5 GND_TX Figure 3. RX95HF pinout description 25 1 ST_R4 NC NC NC GND NC ST_R1 RX1 SSI_1 RX2 SSI_0 NC GND_RX SPI_SCK 17 9 SPI_MISO SPI_SS IRQ_OUT VPS IRQ_IN NC NC ST_R0 Shaded area represents the dissipation pad. (Must be connected to ground.) SPI_MOSI Table 2. RX95HF pin descriptions Pin 6/44 Pin name Type(1) Main function 1 ST_R3 ST Reserved 2 ST_R4 ST Reserved 3 NC Not connected 4 NC Not connected 5 RX1 I Receiver input 1 6 RX2 I Receiver input 2 7 NC 8 GND_RX P Ground (analog) 9 ST_R0 O ST Reserved(2) 10 NC 11 NC 12 IRQ_IN 13 VPS Not connected Not connected Not connected I (3) Interrupt input P Main power supply DocID023884 Rev 3 Alternate function RX95HF Pin and signal descriptions Table 2. RX95HF pin descriptions (continued) Pin Pin name Type(1) (4) 14 IRQ_OUT O 15 SPI_SS I (5) 16 SPI_MISO O (5) (5) Main function Interrupt output SPI Slave Select (active low) SPI Data, Slave Output SPI Data, Slave Input (5) 17 SPI_MOSI I 18 SPI_SCK I (6) SPI serial clock 19 SSI_0 I (5) Select serial communication interface 20 SSI_1 I (5) Select serial communication interface 21 ST_R1 I (7) ST Reserved 22 GND 23 NC Not connected 24 NC Not connected 25 NC Not connected 26 NC Not connected 27 NC Not connected 28 NC Not connected 29 XIN Crystal oscillator input 30 XOUT Crystal oscillator output 31 GND_TX 32 ST_R5 P P Alternate function Ground (digital) Ground (RF drivers) ST Reserved 1. I: Input, O: Output, and P: Power 2. Must add a capacitor to ground (~1 nF). 3. Pad internally connected to a Very Weak Pull-up to VPS. 4. Pad internally connected to a Weak Pull-up to VPS. 5. Must not be left floating. 6. Pad internally connected to a Weak Pull-down to GND. 7. Pad input in High Impedance. Must be connected to VPS. DocID023884 Rev 3 7/44 7 Power management and operating modes RX95HF 3 Power management and operating modes 3.1 Operating modes The RX95HF has 2 operating modes: Wait for Event (WFE) and Active. In Active mode, the RX95HF communicates actively with an NFC reader or an external host (an MCU, for example). The RX95HF can switch from one mode to another. Table 3. RX95HF operating modes and states Mode Wait For Event (WFE) State Description Power-up This mode is accessible directly after POR. Low level on IRQ_IN pin (longer than 10 μs) is the only wakeup source. LFO (low-frequency oscillator) is running in this state. Hibernate Lowest power consumption state. The RX95HF has to be woken-up in order to communicate. Low level on IRQ_IN pin (longer than 10 μs) is the only wakeup source. Sleep/Field Detector Low power consumption state. Wakeup source is configurable: – IRQ_IN pin – Field Detector LFO (low-frequency oscillator) is running in this state. Ready In this mode, the RX95HF waits for a command (PROTOCOLSELECT, ...) from the external host via the serial interface (SPI). Tag Emulation The RX95HF can communicate as a tag with an external reader. The tag application is located in the Host and communicates with the RX95HF via the serial interface (SPI). Active Hibernate, and Sleep/Field Detector states can only be activated by a command from the external host. As soon as any of these three states are activated, the RX95HF can no longer communicate with the external host. It can only be woken up. 8/44 DocID023884 Rev 3 RX95HF Power management and operating modes Figure 4. RX95HF initialization and operating state change 3.2 Startup sequence After the power supply is established at power-on, the RX95HF waits for a low pulse on the pin IRQ_IN (t1) before automatically selecting the external interface (SPI) and entering Ready state after a delay (t3). Figure 5. Power-up sequence T 603 6 33)? T 33)? )21?). T T &IRSTVALID COMMAND T -36 1. Pin IRQ_IN low level < 0.2 VPS_Main. Note: When RX95HF leaves WFE mode (from Power-up, Hibernate, or Sleep/Field Detector) following an IRQ_IN low level pulse. DocID023884 Rev 3 9/44 43 Power management and operating modes RX95HF Figure 5 shows the power-up sequence for a RX95HF device; where,  t0 is the initial wake-up delay 100 μs (minimum)  t1 is the minimum interrupt width 10 μs (minimum)  t2 is the delay for the serial interface selection 250 ns (typical)  t3 is the HFO setup time (tSU(HFO)) 10 ms (maximum)  t4 is the VPS ramp-up time from 0V to VPS 200 μs (minimum) and 10 ms (max. by design validation) Note: VPS must be 0V before executing the start-up sequence. The serial interface is selected after the following falling edge of pin IRQ_IN when leaving from POR or Hibernate state. Table 4 lists the signal configuration used to select the serial communication interface. Table 4. Select serial communication interface selection table Pin 10/44 Serial interface (SPI) SSI_0 1 SSI_1 0 DocID023884 Rev 3 RX95HF Communication protocols 4 Communication protocols 4.1 Serial peripheral interface (SPI) 4.1.1 Polling mode In order to send commands and receive replies, the application software has to perform 3 steps. 1. Send the command to the RX95HF. 2. Poll the RX95HF until it is ready to transmit the response. 3. Read the response. The application software should never read data from the RX95HF without being sure that the RX95HF is ready to send the response. The maximum allowed SPI communication speed is fSCK. A Control byte is used to specify a communication type and direction:  0x00: Send command to the RX95HF  0x03: Poll the RX95HF  0x02: Read data from the RX95HF  0x01: Reset the RX95HF The SPI_SS line is used to select a device on the common SPI bus. The SPI_SS pin is active low. When the SPI_SS line is inactive, all data sent by the Master device is ignored and the MISO line remains in High Impedance state. Figure 6. Sending command to RX95HF MOSI 00000000 CMD LEN DATA Several data bytes Control Byte MISO DATA XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX Figure 7. Polling the RX95HF until it is ready MOSI 00000011 XXXXXX11 Control Byte MISO XXXXXXXX 00000XXX XXXXXX11 XXXXXX11 Flag Flag 00000XXX 00001XXX Flags are polled until data is ready (Bit 3 is set when data is ready) DocID023884 Rev 3 11/44 43 Communication protocols RX95HF Table 5. Interpretation of flags Bit [7:4] Meaning (Application point of view) Not significant 3 Data can be read from the RX95HF when set. 2 Data can be sent to the RX95HF when set. [1:0] Not significant Figure 8. Reading data from RX95HF MOSI 00000010 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX Control Byte MISO XXXXXXXX Resp Code LEN DATA DATA Several data bytes Data must be sampled at the rising edge of the SCK signal. ‘Sending’, ‘Polling’ and ‘Reading’ commands must be separated by a high level of the SPI_SS line. For example, when the application needs to wait for data from the RX95HF, it asserts the SPI_SS line low and issues a ‘Polling’ command. Keeping the SPI_SS line low, the Host can read the Flags Waiting bit which indicates that the RX95HF can be read. Then, the application has to assert the SPI_SS line high to finish the polling command. The Host asserts the SPI_SS line low and issues a ‘Reading’ command to read data. When all data is read, the application asserts the SPI_SS line high. The application is not obliged to keep reading Flags using the Polling command until the RX95HF is ready in one command. It can issue as many 'Polling' commands as necessary. For example, the application asserts SPI_SS low, issues 'Polling' commands and reads Flags. If the RX95HF is not ready, the application can assert SPI_SS high and continue its algorithm (measuring temperature, communication with something else). Then, the application can assert SPI_SS low again and again issue 'Polling' commands, and so on, as many times as necessary, until the RX95HF is ready. Note that at the beginning of communication, the application does not need to check flags to start transmission. The RX95HF is assumed to be ready to receive a command from the application. Figure 9. Reset the RX95HF MOSI 00000001 Control Byte 01 MISO XXXXXXXX To reset the RX95HF using the SPI, the application sends the SPI Reset command (Control Byte 01, see Figure 9) which starts the internal controller reset process and puts the RX95HF into Power-up state. The RX95HF will wake up when pin IRQ_IN goes low. The RX95HF reset process only starts when the SPI_SS pin returns to high level. Caution: 12/44 SPI communication is MSB first. DocID023884 Rev 3 RX95HF 4.1.2 Communication protocols Interrupt mode When the RX95HF is configure to use the SPI serial interface, pin IRQ_OUT is used to give additional information to user. When the RX95HF 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 host reads the data. The application can use the Interrupt mode to skip the polling stage. Caution: SPI communication is MSB first. DocID023884 Rev 3 13/44 43 Commands RX95HF 5 Commands 5.1 Command format   The frame from the Host to the RX95HF has the following format: The frame from the RX95HF to Host has the following format: These two formats are available in SPI mode. Fields , and are always 1 byte long. can be from 0 to 253 bytes. Note: The ECHO command is an exception as it has only one byte (0x55). The following symbols correspond to: >>> Frame sent by the Host to RX95HF >0x0100