RX95HF-VMD5T,PDF,RX95HF-VMD5T PDF资料,Datasheet,下载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

DocID023884 Rev 3

1/44

This is information on a product in full production.

www.st.com

Contents

RX95HF

Contents

1

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1

1.2

Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

List of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2

3

Pin and signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Power management and operating modes . . . . . . . . . . . . . . . . . . . . . . . 8

3.1

3.2

Operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Startup sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4

5

Communication protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1

Serial peripheral interface (SPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1.1

4.1.2

Polling mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Interrupt mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5.1

5.2

5.3

5.4

5.5

5.6

5.7

5.8

Command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

List of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

IDN command (0x01) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Protocol Select command (0x02) description . . . . . . . . . . . . . . . . . . . . . . 15

Pollfield command (0x03) description . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Listen command (0x05) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Send command (0x06) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Idle command (0x07) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.8.1

5.8.2

5.8.3

Idle command parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Optimizing wake-up conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

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 Improving RF performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.11 AcFilter command (0x0D) description . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.12 Echo command (0x55) description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2/44

DocID023884 Rev 3

RX95HF

Contents

6

Electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6.1

6.2

6.3

6.4

6.5

6.6

Absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

DC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Power consumption characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

SPI characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

RF characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Oscillator characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

7

8

Package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Appendix A Card emulation communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

DocID023884 Rev 3

3/44

3

Description

RX95HF

1

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

Host

Controller

(MCU)

RX95HF

SPI

1.1

Block diagram

Figure 2. RX95HF block diagram

4/44

DocID023884 Rev 3

RX95HF

Description

1.2

List of terms

Table 1. List of terms

Term

Meaning

GND

HFO

LFO

MCU

NFC

RFID

RFU

SPI

Ground

High frequency oscillator

Low frequency oscillator

Microcontroller unit

Near Field Communication

Radio Frequency Identification

Reserved for future use

Serial peripheral interface

Low frequency period

Reference time

t_L

t_REF

WFE

Wait For Event

DocID023884 Rev 3

5/44

7

Pin and signal descriptions

RX95HF

2

Pin and signal descriptions

Figure 3. RX95HF pinout description

25

1

ST_R3

ST_R4

NC

GND

NC

ST_R1

SSI_1

SSI_0

SPI_SCK

SPI_MOSI

RX1

RX2

NC

GND_RX

17

9

Shaded area represents the dissipation pad.

(Must be connected to ground.)

Table 2. RX95HF pin descriptions

Pin name

Type⁽¹⁾

Main function

ST Reserved

Alternate function

1

2

3

4

5

6

7

8

9

ST_R3

ST_R4

NC

ST Reserved

Not connected

Receiver input 1

Receiver input 2

Not connected

Ground (analog)

ST Reserved⁽²⁾

Not connected

Interrupt input

Main power supply

NC

RX1

RX2

NC

I

GND_RX

ST_R0

NC

P

O

10

11

12

13

NC

IRQ_IN

VPS

I ⁽³⁾

P

6/44

DocID023884 Rev 3

RX95HF

Pin and signal descriptions

Table 2. RX95HF pin descriptions (continued)

14

Pin name

IRQ_OUT

Type⁽¹⁾

Main function

Interrupt output

Alternate function

O ⁽⁴⁾

I ⁽⁵⁾

O ⁽⁵⁾

I ⁽⁵⁾

15

16

17

18

SPI_SS

SPI Slave Select (active low)

SPI Data, Slave Output

SPI Data, Slave Input ⁽⁵⁾

SPI serial clock

SPI_MISO

SPI_MOSI

SPI_SCK

I ⁽⁶⁾

Select serial communication

interface

19

20

SSI_0

SSI_1

I ⁽⁵⁾

Select serial communication

interface

21

22

23

24

25

26

27

28

29

30

31

32

ST_R1

GND

NC

I ⁽⁷⁾

P

ST Reserved

Ground (digital)

Not connected

NC

Not connected

NC

Not connected

NC

Not connected

NC

Not connected

NC

Not connected

XIN

Crystal oscillator input

Crystal oscillator output

Ground (RF drivers)

ST Reserved

XOUT

GND_TX

ST_R5

P

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

State

Description

This mode is accessible directly after POR.

Power-up

Low level on IRQ_IN pin (longer than 10 μs) is the only wakeup

source. LFO (low-frequency oscillator) is running in this state.

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.

Wait For

Event

(WFE)

Hibernate

Low power consumption state. Wakeup source is configurable:

– IRQ_IN pin

Sleep/Field

Detector

– Field Detector

LFO (low-frequency oscillator) is running in this state.

In this mode, the RX95HF waits for a command (PROTOCOLSELECT,

...) from the external host via the serial interface (SPI).

Ready

Active

The RX95HF can communicate as a tag with an external reader. The

Tag Emulation tag application is located in the Host and communicates with the

RX95HF via the serial interface (SPI).

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 (t ) before automatically selecting the external interface (SPI) and entering

1

Ready state after a delay (t ).

3

Figure 5. Power-up sequence

T_ꢄ

603

ꢁ6

33)?ꢁ

33)?ꢂ

T_ꢂ

)21?).

&IRST VALID

COMMAND

T_ꢁ

T_ꢃ

T_ꢀ

-3ꢀꢁꢁꢀꢂ6ꢀ

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,



t is the initial wake-up delay

100 μs (minimum)

10 μs (minimum)

250 ns (typical)

0

t is the minimum interrupt width

1

t is the delay for the serial interface selection

2

t is the HFO setup time (t

)

SU(HFO)

10 ms (maximum)

200 μs (minimum) and

10 ms (max. by design validation)

3

t is the V ramp-up time from 0V to VPS

4

PS

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

Serial interface (SPI)

SSI_0

SSI_1

1

0

10/44

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 f

.

SCK

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

MISO

0 0 0 0 0 0 0 0

CMD

LEN

DATA

Several data bytes

Control Byte

X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X

Figure 7. Polling the RX95HF until it is ready

MOSI

0 0 0 0 0 0 1 1 X X X X X X 1 1

Control Byte

X X X X X X 1 1 X X X X X X 1 1

Flag

MISO

X X X X X X X X 0 0 0 0 0 X X X

0 0 0 0 0 X X X 0 0 0 0 1 X X X

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

Meaning (Application point of view)

[7:4]

3

Not significant

Data can be read from the RX95HF when set.

Data can be sent to the RX95HF when set.

Not significant

2

[1:0]

Figure 8. Reading data from RX95HF

MOSI

MISO

0 0 0 0 0 0 1 0 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X

Control Byte

X X X X X X X X

Resp Code

LEN

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

0 0 0 0 0 0 0 1

Control Byte 01

X X X X X X X X

MISO

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:

SPI communication is MSB first.

12/44

DocID023884 Rev 3

RX95HF

Communication protocols

4.1.2

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.

SPI communication is MSB first.

Caution:

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 <Cmd>, <RespCode> and <Len> are always 1 byte long. <Data> 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

<<< Frame sent by the RX95HF to the Host

5.2

List of commands

Table 6 summarizes the available commands.

Table 6. List of RX95HF commands

Code

Command

Description

0x01

IDN

Requests short information about the RX95HF and its revision.

Selects the RF communication protocol and specifies certain

protocol-related parameters.

0x02

PROTOCOLSELECT

0x03

0x05

0x06

POLLFIELD

LISTEN

Returns the current value of the FieldDet flag.

Listens for data using previously selected protocol.

Sends data using previously selected protocol.

SEND

Switches the RX95HF into a low consumption Wait for Event (WFE)

mode (Power-up, Hibernate, or Sleep/Field Detector), specifies the

authorized wake-up sources and waits for an event to exit to Ready

state.

0x07

IDLE

Reads Wake-up event register or the Analog Register

Configuration (ACC_A) register.

0x08

0x09

0x0D

RDREG

WRREG

ACFILTER

Writes Analog Register Configuration (ACC_A) register or writes

index of ACC_A register address.

Enables or disables the anti-collision filter for ISO/IEC 14443 Type

A protocol.

RX95HF performs a serial interface ECHO command (reply data

0x55 or stops the Listening state when a listen command has been

sent without error).

0x55

ECHO

Other codes

ST Reserved

14/44

DocID023884 Rev 3

RX95HF

Commands

5.3

IDN command (0x01) description

The IDN command (0x01) gives brief information about the RX95HF and its revision.

Table 7. IDN command description

Direction

Data

0x01

Comments

Example

Command code

Length of data

Result code

Host to

RX95HF

>>>0x0100

0x00

<Len>

<<<0x000F4E4643204653324A415354

34002ACE

Length of data

Data in ASCII format (13

bytes)

In this example,

RX95HF to

Host

<<<0x4E4643204653324A4153543400

: ‘NFC FS2JAST4’, #4 (Last Character of

NFC FS2JAST4 means ROM code

revision 4.)

CRC calculated for ROM

content (2 bytes)

0x2ACE: CRC of ROM (real CRC may

differ from this example)

It takes approximately 6 ms to calculate the CRC for the entire ROM. The application must

allow sufficient time for waiting for a response for this command.

5.4

Protocol Select command (0x02) description

This command selects the RF communication protocol and prepares the RX95HF for

communication with a reader.

Table 8. PROTOCOLSELECT command description

Direction

Data

Comments

Command code

Example

0x02

<Len>

Length of data

See Table 9: List of <Parameters>

values for different protocols (Tag

Emulation) for a detailed example.

Protocol codes:

Host to

RX95HF

12: ISO/IEC 14443-A

Each protocol has a

>>>0x02021208

<Parameters> different set of

parameters. See Table 9.

0x00

0x82

0x00

0x83

0x00

Result code

<<<0x0000

RX95HF to

Host

Protocol is successfully selected

Length of data

Error code

<<<0x8200

RX95HF to

Host

Invalid command length

Length of data

Error code

<<<0x8300

RX95HF to

Host

Invalid protocol

Length of data

When the application selects a protocol, the RX95HF performs all necessary settings: it will

choose the appropriate reception and transmission chains.

DocID023884 Rev 3

15/44

43

Commands

RX95HF

Table 9. List of <Parameters> values for different protocols (Tag Emulation)

Parameters

Function

Examples of commands

Comments

Protocol

(Card)

Code

Byte Bit

Transmission data rate

00: 106 Kbps

01: 212 Kbps ⁽¹⁾

10: 424 Kbps ⁽¹⁾

11: RFU

7:6

Reception data rate

00: 106 Kbps

01: 212 Kbps ⁽¹⁾

10: 424 Kbps ⁽¹⁾

11: RFU

>>>0x02021208

<<<0x0000

ISO/IEC

14443

5:4

Tag Emulation for ISO/IEC

14443 Type A, Data rate is

106 Kbps for both up- and

down-links.

0x12

0

Type A

0: Return an error, if no RF field

1: Wait for RF field

3

2

1

0

RFU

0: HFO

1: ClkRec

RFU

1. Not qualified for this version.

16/44

DocID023884 Rev 3

RX95HF

Commands

5.5

Pollfield command (0x03) description

This command returns the current value of the FieldDet flag.

Table 10. POLLFIELD command description

Direction

Data

Comments

Command code

Example

03

>>>0x0300 Check if RF Field

is ON or OFF

<Len>

Length of data

RF field presence

(Optional):

>>> 0x0303010FFF - Wait for RF

Field appearance for (16*256)/13.56 μs

Host to

RX95HF

01: Wait for RF field

appearance

Flags, Presc and Timer parameters

are optional. They must be specidfied if

the application has to wait for RF field

appearance or disappearance.

<Flags>

00: Wait for RF field

disappearance

The time to wait is

(Presc+1)*(Timer+1)/13.56 μs.

<Presc>

<Timer>

00

Timer prescaler (Optional)

Timer time-out (Optional)

Result code

<<<0x0000 or 0x000100 (No RF

field detected) or 0x000101 (RF field

detected)

RX95HF to 01

Host

Length of data

01, if FieldDet is set.

Otherwise, 00.

Table 11. Response for <POLLFIELD> command

Response example

Function

Explanation

Comments

Response

00 01 01 or 00

This command returns the

current state of the RF

field.

Result code

Pollfield

Length of data field

<<<0x0000 or

0x000100 (No RF field

detected) or 0x000101

(RF field detected)

Bits [7:1]: RFU

Bit 0: Field detected (if set)

5.6

Listen command (0x05) description

In Tag Emulation mode, this command waits for a command from an external reader.

Before sending this command, the application must select a protocol.

Table 12. LISTEN command description

Direction

Host to

Data

Comments

Command code

Length of data

Example

05

00

0x0500: Enters a Listening mode

where the RX95HF waits for a

command from an external reader.

RX95HF

00

Result code

RX95HF to

Host

0x0000: No error. Confirmation that

RX95HF now is in Listening mode.

Length of data

DocID023884 Rev 3

17/44

43

Commands

RX95HF

Table 12. LISTEN command description (continued)

Data Comments Example

Error code

Direction

82

00

83

RX95HF to

Host

0x8200: Invalid command length

Length of data

Error code

RX95HF to

Host

0x8300: Invalid protocol or protocol is

not supported.

00

Length of data

8F

00

Error code

0x8F00: No field. Command cannot be

executed because there is no external

field.

RX95HF to

Host

Length of data

After reception of the LISTEN command and the return of a ‘No error’ confirmation, the

RX95HF enters Listening mode. The host controller has to use SPI Poll mode or IRQ_OUT

pin to detect when a receive frame is available in the RX95HF buffer. The RX95HF will exit

Listening mode as soon it receives the ECHO command (0x55) from the Host Controller

(MCU) or a command from an external reader (not including commands supported by the

ACFILTER command listed in Table 29).

In all cases, the RX95HF will send data or an error code to the Host controller (MCU).

The ECHO command (0x55) allows exiting Listening mode. In response to the ECHO

command, the RX95HF sends 0x55 + 0x8500 (error code of the Listening state cancelled by

the MCU).

Possible return codes are listed in Table 13.

Table 13. Response codes from the RX95HF in Listening mode

Direction

Data

Comments

Result code

Example

80

<<<0x8005E050BCA508

<Len>

Length of data

The request from the Reader is

decoded. This is an example of a

response in ISO/IEC 14443 Type A

protocol.

RX95HF to

Host

Data received.

Interpretation depends on

protocol

<Data>

85

00

86

00

88

00

89

00

8A

00

Error code

RX95HF to

Host

<<<0x8500 Listening mode was

cancelled by the application

Length of data

Error code

RX95HF to

Host

<<<0x8600 Communication error

<<<0x8800 Invalid SOF

Length of data

Error code

RX95HF to

Host

Length of data

Error code

RX95HF to

Host

<<<0x8900 Receive buffer overflow

(too many bytes received)

Length of data

Error code

RX95HF to

Host

<<<0x8A00 Framing error (start bit=0,

stop bit=1)

Length of data

18/44

DocID023884 Rev 3

RX95HF

Commands

Table 13. Response codes from the RX95HF in Listening mode (continued)

Direction

Data

Comments

Error code

Length of data

Example

8E

00

RX95HF -

Host

<<<0x8E00 Reception lost without EOF

received

If the request from the Reader was received and decoded correctly, the RX95HF will send

data back to the Host (Tag Emulation application). This is explained in Table 14.

Table 14. Data format sent to the Host in Listening mode

Protocol

Explanation

Response example

Comments

Request example 80 0A 9370800F8C8E

Result code

8D 4E01 08

Length of entire data field

Data received from reader

Received value of BCC (if any)

Received value of CRC (if any)

ISO/IEC-

14443

Type A

<<<0x80 0A

9370800F8C8E

8D 4E01 08

7: RFU

6: RFU

5: CRC error

4: Parity error

3:0: number of significant bits in last byte

5.7

Send command (0x06) description

This command immediately sends data to the reader using the Load Modulation method

without waiting for a reply.

Before sending this command, the application must select a communication protocol.

Table 15. SEND command description

Direction

Data

Comments

Command code

Example

06

Depends on protocol previously

selected!

<Len>

Length of data

Host to

RX95HF

>>>0x0606D07387080028: Emulation

of TAG response in ISO/IEC 14443

Type A protocol

Data and additional

parameter to be sent

<Data>

00

82

00

83

00

Result code

Length of data

Error code

<<<0x0000

RX95HF to

Host

Data was successfully sent

RX95HF to

Host

<<<0x8200 Invalid length (for example,

Length=0 where it is not possible)

Length of data

Error code

RX95HF to

Host

<<<0x8300 Invalid protocol previously

selected by Select Protocol command

Length of data

DocID023884 Rev 3

19/44

43

Commands

RX95HF

Table 16. Format of data to be sent using SEND command

Protocol

Explanation

Response example

06 03 0400 08

Comments

Send example

Command code

Length of entire data field

Data

ISO/IEC-

14443

Type A

>>>0x0603040008

Parameter:

7:6: RFU

5: Append CRC

4: RFU (Do not append parity)

3:0: Number of significant bits in first

byte

5.8

Idle command (0x07) description

This command switches the RX95HF into low consumption mode and defines the way to

return to Ready state.

The Result code contains the Wake-up flag register value indicating to the application the

wake-up event that caused the device to exit WFE mode.

Table 17. IDLE command description

Direction

Data

Comments

Command code

Example

07

0E

Example of switch from Active

mode to Hibernate state (wake-up

by low pulse on IRQ_IN pin):

Length of data

Specifies authorized wake-

up sources and the LFO

frequency

>>>0x07 0E 08 04 00 04 00

18 00 00 00 00 00 00 00 00

Example of switch from Active to

WFE mode (Sleep) (wake-up by

low pulse on IRQ_IN pin):

EnterCtrlL

EnterCtrlH

WUCtrlL

Settings to enter WFE

mode: 0x0400, 0x0100 or

0x0142

Host to

RX95HF

>>>0x07 0E 08 01 00 38 00

18 00 00 60 00 00 00 00 00

Settings to wake-up from

WFE mode: 0x0400 or

0x3800

WUCtrlH

Example of switch from Active

mode to WFE mode (Field

Detector) with wake-up by Field

Detection:

LeaveCtrlL

Settings to leave WFE

mode (Default value =

0x1800)

LeaveCtrlH

>>> 0x07 0E 04 01 42 38 00

18 00 00 60 00 00 00 00

0x00

0x01

Result code

This response is sent only when

RX95HF exits WFE mode.

Length of data

RX95HF to

Host

<<<0x000104 Wake-up by field

detect

Data (Wake-up source):

0x04: Field detect

0x08: Low pulse on

IRQ_IN pin

<Data>

<<<0x000108 Wake-up by low

pulse on IRQ_IN pin

20/44

DocID023884 Rev 3

RX95HF

Commands

Table 17. IDLE command description (continued)

Data Comments Example

Error code

Length of data

Direction

0x82

0x00

RX95HF to

Host

<<<0x8200 Invalid command

length

5.8.1

Idle command parameters

The Idle command (Host to RX95HF) has the following structure (all values are

hexadecimal):

Table 18. Idle command structure

07

0E

xx

yy zz

Command

code

Data length

WU source

Enter Control

WU Control

Leave Control

Table 19. Summary of Idle command parameters

Description

Parameter

This byte is the command code. ‘07’ represents the Idle command. This

command switches the device from Active mode to WFE mode.

Command code

Data length

This byte is the length of the command in bytes. Its value depends on the

following parameter values.

This byte defines the authorized wake-up sources in the Wake-up source

register. Predefined values are:

WU Source

0x04: Field Detector0x08: Low pulse on IRQ_IN

These two bytes (EnterCtrlL and EnterCtrlH) define the resources when

entering WFE mode.

Enter Control

WU Control

0x0400: Hibernate0x0142: Sleep (if Field Detector source is enabled)

These two bytes (WuCtrlL and WuCtrlH) define the wake-up resources.

0x0400: Hibernate

0x3800: Sleep

These two bytes (LeaveCtrlL and LeaveCtrlH) define the resources when

returning to Ready state.

Leave Control

0x1800: Hibernate

0x1800: Sleep

5.8.2

5.8.3

Optimizing wake-up conditions

Using the Wake-up source register, it is possible to cumulate sources for a wake-up event. It

is strongly recommended to always set an external event as a possible wake-up source.

To cumulate wake-up sources, simply set the corresponding bits in the Wake-up source

register. For example, to enable a wake-up when an RF field is detected (bit 1 set to ‘1’) or

on a low pulse on pin IRQ_IN (bit 3 set to ‘1’), set the register to 0x0A.

Using various techniques to return to Ready state

The Idle command and reply set offers several benefits to users by enabling various

methods to return the RX95HF to Ready state. Some methods are nearly automatic, such

as waiting for a timer overflow or a field detection, but others consume more power

compared to the ones requesting a host action. A description of each method follows below.

DocID023884 Rev 3

21/44

43

Commands

RX95HF

Default setting: from POR to Ready state

After power-on, the RX95HF enters Power-up state.

To wake up the RX95HF and set it to Ready state, the user must send a low pulse on the

IRQ_IN pin. The RX95HF then automatically selects the external interface (SPI) and enters

Ready state and is able to accept commSands after a delay of approximately 6 ms (t ).

3

From Ready state to Hibernate state and back to Ready state

In Hibernate state, most resources are switched off to achieve an ultra-low power

consumption.

The only way the RX95HF can wake-up from Hibernate state is by an external event (low

pulse on pin IRQ_IN).

A basic Idle command is:

>>>0x07 0E 08 04 00 04 00 18 00 00 00 00 00 00 00 00

Note:

The Wake-up flag value is NOT significant when returning to Ready state from Hibernate

state or after a POR.

From Ready state to Sleep state and back to Ready state

Wake-up by external event (low pulse on IRQ_IN)

In Sleep or Power-up states, operating resources are limited in function of the selected

wake-up source to achieve a moderate power consumption level.

An Idle command example when wake-up source is pin IRQ_IN:

>>>0x07 0E 08 01 00 38 00 18 00 00 60 00 00 00 00 00

5.9

Read Register (RdReg) command (0x08) description

This command is used to read the Wakeup register.

Table 20. RDREG command description

Direction

Data

Comments

Example

0x08

0x03

Command code

Length of data

Ex 1. >>>0x0803690100

Reads the ACC_A register. ⁽¹⁾

Host to

RX95HF

0x62 or 0x69 Register address

0x01

0x00

<Len>

Register size

ST Reserved

Result code

<<<0x000127

RX95HF to

Host

See Section 5.10: Write Register (WrReg)

command (0x09) description for more

information on received register data.

Length of data

<RegData> Register data

0x82

0x00

Error code

RX95HF to

Host

<<<0x8200 Invalid command length

Length of data

1. This command must be preceded by the setting of the ACC_A register index (0x0903680004).

22/44

DocID023884 Rev 3

RX95HF

Commands

Note:

The Management of the Analog Register Configuration register (ACC_A) is described in

Section 5.10: Write Register (WrReg) command (0x09) description.

5.10

Write Register (WrReg) command (0x09) description

The Write Register (WRREG) command (0x09) is used to:



set the Analog Register Configuration address index value before reading or

overwriting the Analog Register Configuration register (ACC_A) value



set the Analog Register Configuration register (ACC_A) value

–

Bits [7:6] are ST Reserved and must be set to ‘0’

Bits [5:4] set the Demodulator Sensitivity (‘00’ = AM 10% or ‘10’ = AM 100%)

Bits [3:0] set the Load Modulation Index (‘0001’ = minimum load modulation, ‘0111’

= default value, ‘1111’ = maximum load modulation). The user can adjust this value

to better fit his application.

5.10.1

Improving RF performance

Adjusting the Load Modulation Index and Demodulator Sensitivity parameters in Card

Emulation mode helps improve application behavior.

The default value of these parameters (Table 21) is set by the PROTOCOLSELECT command,

but they can be overwritten using the Write Register (WRREG) command (0x09). Table 22

and Table 23 list possible values for the Load Modulation Index and Demodulator Sensitivity

parameters respectively.

This new configuration is valid until a new PROTOCOLSELECT or Write Register (of register

ACC_A) command is executed. Register values are cleared at power off.

Table 21. WRREG command description (Load Modulation Index and Demodulator

Sensitivity)

Direction

Data

Comments

Example

0x09 Command code

0x03 or

Length of data

0x04

>>>0x0903680004

Analog Register Configuration address

index

0x68

Set Analog Register Index to

0x04 (ACC_A) ⁽¹⁾

0x00 or Flag Increment address or not after Write

0x01 command

Host to

RX95HF

Index pointing to the Demodulator

Sensitivity and Load Modulation values in

ACC_A register (0x04) (See

>>>0x090468010425

0x04

Update ACC_A to 0x25

Section 5.10.1)

New value for Demodulator Sensitivity and

0xXX

Load Modulation (See Section 5.10.1)

0x00 Result code

<<<0x0000

RX95HF to

Host

Register written

0x00 Length of data (= RegCount)

1. This command must be executed before reading the ACC_A register (0x0903680004).

DocID023884 Rev 3

23/44

43

Commands

RX95HF

How to modify Analog Register Configuration register (ACC_A) values

1. Use the PROTOCOLSELECT command (0x02) to select the correct communication

protocol.

For example, to select the ISO/IEC 14443-A card emulation protocol:

Send PROTOCOLSELECT command:

RX95HF reply:

>>>0x02021208

<<<0x0000

2. Read the Analog Register Configuration register (ACC_A) value.

a) Write the ACC_A register index at 0x04:

RX95HF reply:

>>>0x0903680004

<<<0x0000

b) Read the ACC_A register value:

RX95HF reply:

>>>0x0803690100

<<<0x0127

In this example, the ACC_A register value is 0x27, where “2” is the Demodulator

Sensitivity and “7” is the Load Modulation Index.

3. Modify the Load Modulation Index values with 0x25.

Write the ACC_A register index:

RX95HF reply:

>>>0x090468010425

<<<0x0000

4. Read the Analog Configuration register (ACC_A) value.

a) Write the ACC_A register index at 0x04:

RX95HF reply:

>>>0x0903680004

<<<0x0000

b) Read the ACC_A register value:

RX95HF reply:

>>>0x0803690100

<<<0x0125

Load Modulation Index and Demodulator Sensitivity values

.

Table 22. Possible Load Modulation Index values

Code (bits [3:0] of ACC_A register)

1

2

...

7

...

E

F

Load Modulation Index

Min.

Default

Max.

Table 23. Possible Demodulator Sensitivity values

Code (bits [5:4] of ACC_A register)

Demodulator Sensitivity ⁽¹⁾

0x1

0x2

100%

10%

1. Characterized by design simulation.

Note:

Bits [7:6] of ACC_A register are RFU and must set to ‘0’.

24/44

DocID023884 Rev 3

RX95HF

Commands

5.11

AcFilter command (0x0D) description

This command activates/deactivates the anti-collision filter in Type A Tag Emulation mode.

The following tables define the command and response fields depending on the AC filter

command length.

Table 24. AC filter command description (Command <Len> > 0x02)

Direction

Data

Comments

Command code

Example

0D

General case (LEN 0x00, 0x01 or

0x02)

<Len>

Length of data

>>>0D0B440320880251744AEF2280

Unused and proprietary

bits of SAK (protocol bits

will be handled by

firmware)

Activate filter for 2-cascade anti-collision

<ATQA>

(2 bytes)

Note that the command length can be 7,

11 or 15 bytes depending on UID length:

Unused and proprietary

bits of SAK (protocol bits

will be handled by

firmware)

7: for 1-cascade level filter

11: for 2-cascade levels filter

15: for 3-cascade levels filter

<SAK>

All other values greater than 2 will result

in an ‘Invalid command length’ error.

Values 0, 1 and 2 are defined in the

following tables.

UID for cascade level 1

(Mandatory)

UID for cascade level 2

(Optional)

Host to

RX95HF

*** Special cases of command ***

LEN = 0x00

>>>0x0D00 De-activate AC Filter (LEN

= 0x00)

<<< 0x0001XX0000 AC Filter is

successfully deactivated (XX: Table 28)

LEN = 0x01

UID for cascade level 3

(Optional)

>>>0x0D01XX - Set AC state (see table

below)

<<< 0x0000 AC state successfully set

LEN = 0x02

>>> 0x0D020000 - Returns AC state

without deactivating filter

<<< 0x0001XX AC state (XX: Table 28)

00

Result code

AC Filter is successfully activated.

<<<0x0000

RX95HF to

Host

AC Filter is successfully deactivated

(LEN = 0x00).

Length of data

<<<0x0001XX0000 (where XX is ST

Reserved)

82

00

Error code

<<<0x8200

RX95HF to

Host

Invalid command length

Length of data

DocID023884 Rev 3

25/44

43

Commands

RX95HF

Table 25. AC filter command description (Command <Len> = 0x00)

Direction

Data

Comments

Command code

Example

0D

If <Len> = 0x00, AC filter is deactivated

and response will return Tag Emulation

state.

Host to

RX95HF

<Len>

Length of data (0x00)

>>>0x0D00 Deactivate AC Filter

00

01

Result code

AC filter is deactivated and response will

return Tag Emulation state.

Length of data

RX95HF to

Host

<<<0x0001yy

where yy is the Tag Emulation state

(Table 28).

yy

Tag Emulator state

82

00

Error code

<<<0x8200

RX95HF to

Host

Invalid command length

Length of data

Table 26. AC filter command description (Command <Len> = 0x01)

Direction

Data

Comments

Command code

Example

0D

If <Len> = 0x01, AC Filter state will be

forced to yy state (Table 28).

Host to

RX95HF

<Len>

yy

Length of data (0x01)

Tag Emulator state

Result code

>>>0x0D01yy Force new Tag

Emulation state (yy).

00

If <Len> = 0x01, Tag Emulation state is

successfully set.

RX95HF to

Host

00

Length of data

<<<0x0000

82

00

Error code

<<<0x8200

RX95HF to

Host

Invalid command length

Length of data

Table 27. AC filter command description (Command <Len> = 0x02)

Direction

Data

Comments

Command code

Example

0D

If <Len> = 0x02, response will return

Tag Emulation state without de-

activating the AC filter.

Host to

RX95HF

<Len>

0000

00

Length of data (0x02)

ST Reserved

>>>0x0D020000

Result code

If <Len> = 0x02, returns Tag Emulation

state (Table 28) without de-activating

the AC filter.

RX95HF to

Host

01

Length of data

Tag Emulator state

Error code

yy

<<<0x0001yy

82

<<<0x8200

RX95HF to

Host

Invalid command length

00

Length of data

26/44

DocID023884 Rev 3

RX95HF

Commands

Table 28. RX95HF state

Tag

Emulation

state

ISO/IEC 14443 - 3 Type A

definition

Emulation

state

definition

0x00

0x01

0x02

0x03

0x04

Idle

0x80

0x81

0x82

0x83

Halt

ReadyA

ReadyB

ReadyC

Active

ReadyA* ⁽¹⁾

ReadyB* ⁽¹⁾

ReadyC* ⁽¹⁾

1. After a ISO/IEC 14443 - 3 Type A WakeUp command.

The ACFILTER command activates or deactivates an anti-collision filter for ISO/IEC 14443A

tag protocol. This command also forces or indicates the Card Emulator state.

If the AC filter is not activated, all received commands are stored in the RX95HF buffer

before being read by the external microcontroller.

If the AC filter is activated, internal firmware will try to interpret the commands sent by the

reader itself and perform an anti-collision sequence. Non-interpreted commands are stored

in the RX95HF buffer before being read by the external microcontroller to perform Level 4 of

the ISO/IEC 14443 Type A protocol.

The RX95HF is able to interpret and respond to the commands listed in the table below. The

device remains in Listening mode after executing these commands.

Table 29. Commands to which the device is able to respond

Command

Code

Definition

SENS_REQ

ALL_REQ

SDD_REQ

SEL_REQ

26 (7-bit)

52 (7-bit)

93, 95, 97

Sense request

WakeUp All request

Single device detection request

Select request

9370, 9570, 9770

5.12

Echo command (0x55) description

The ECHO command verifies the possibility of communication between a Host and the

RX95HF. This command also can be used to exit Listening mode without an error when the

RX95HF has received a Listen command.

Table 30. ECHO command description

Direction

Data

Comments

Example

Host to RX95HF

0x55

Command code

>>> 0x55: Sends an ECHO command

RX95HF to Host

0x55

Code response

<<< 0x55: Response to an ECHO

command

DocID023884 Rev 3

27/44

43

Electrical characteristics

RX95HF

6

Electrical characteristics

6.1

Absolute maximum ratings

Table 31. Absolute maximum ratings

Symbol

VPS_Main Supply voltage ⁽¹⁾

V_IOInput or output voltage relative to ground

Parameter

Value

Unit

–0.3 to 7.0

–0.3 to VPS_Main +0.3

±14.0

V

V_MaxCarrierMaximum input voltage (pins RX1 and RX2)

Ambient operating temperature

T_A

–25 to +85

°C

Ambient operating temperature (RF mode)

–25 to +85

Storage temperature (Please also refer to package

specification).

T_STG

–65 to +150

See note⁽²⁾

2000

°C

V

T_LEAD

V_ESD

Lead temperature during soldering

Electrostatic discharge voltage according to

JESD22-A114, Human Body Model

(3)

P_TOT

Total power dissipation per package

1

W

1. To properly reset the device, VPS_Main must be tied to 0V before executing the start-up sequence.

2. Compliant with JEDEC standard J-STD-020D (for small-body, Sn-Pb or Pb assembly), the ST ECOPACK®

7191395 specification, and the European directive on Restrictions on Hazardous Substances (RoHS

directive 2011/65/EU of July 2011).

3. Depending on the thermal resistance of package.

Note:

Stresses listed above may cause permanent damage to the device. This is a stress rating

only and functional operation of the device at these or any other conditions above those

indicated in the operational sections of the specification is not implied.

Exposure to absolute maximum rating conditions for extended periods may affect device

reliability.

6.2

DC characteristics

Table 32. DC characteristics

Symbol

Parameter

Condition

Min.

Typ.

Max.

Unit

VPS_Main Supply voltage

2.7

3.0

5.5

V

V_IL

V_IH

Input low voltage (I/Os)

Input high voltage (I/Os)

Output high voltage (I/Os) I_OH= - 8 μA

0

0.2 x VPS_Main

VPS_Main

0.7 x VPS_Main

V_OH

VPS_Main

0.15 x

VPS_Main

V_OL

Output low voltage (I/Os)

Power-on reset voltage

I_OLMAX= 500 μA

0

V

POR

1.8

28/44

DocID023884 Rev 3

RX95HF

Electrical characteristics

6.3

Power consumption characteristics

T = –25°C to 85°C, unless otherwise specified.

A

Table 33. Power consumption characteristics (VPS_Main from 2.7 to 5.5 V)

Symbol

I_CC(V_PS

Parameter

Condition

Typ.

Max.

Unit

)

Supply current in power-up state

T_A= 25°C

200

600

μA

Power-up

I_CC(V_PS

Tag Emulation

I_CC(V_PS

Hibernate

I_CC(V_PS

)

Supply current in Tag Emulation mode

Supply current in Hibernate state

T_A= 25°C

2.5

1

5.0

5

mA

)

μA

)

Sleep/Field

Detector

Supply current in Sleep/Field Detector state

T_A= 25°C

20/25

2.5

80

μA

I_CC(V_PS) Ready Supply current in Ready state

5.0

mA

DocID023884 Rev 3

29/44

43

Electrical characteristics

RX95HF

6.4

SPI characteristics

The RX95HF supports (CPOL = 0, CPHA = 0) and (CPOL = 1, CPHA = 1) modes.

Table 34. SPI interface characteristics

Symbol

Parameter

Condition

Min.

Max.

Unit

f_SCK

SPI clock frequency

2.0

MHz

1/ t_c(SCK)

V_IL

V_IH

Input low voltage

0.3 x V_PS

Input high voltage

Output low voltage

Output high voltage

NSS setup time

0.7 x V_PS

V

V_OL

V_OH

0.4 x V_PS

0.7 x V_PS

(1)

t_SU(NSS)

70

0

ns

(1)

t_h(NSS)

NSS hold time

(1)

t_CH(SCKL)

Clock low time

200

20

t_CH(SCKH)

Clock high time

(1)

t_SU(SI)

Data slave Input setup time

Data slave Input hold time

Data slave output valid time

(1)

t_h(SI)

80

(1)

t_v(SO)

80

ns

After enable

edge

(1)

t_h(SO)

Data slave output hold time

Capacitive load for input pins NSS,

CLK, MOSI

C_{b_SPI_IN}

3

pF

Capacitive load for input pins

MOSI

C_{b_SPI_OUT}

20

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

Figure 10. SPI timing diagram (Slave mode and CPOL = 0, CPHA = 0)

.33 INPUT

T

Hꢈ.33ꢉ

35ꢈ.33ꢉ

Cꢈ3#+ꢉ

#0/, ꢊ ꢁ

#0(! ꢊ ꢁ

T

#(ꢈ3#+(ꢉ

#(ꢈ3#+,ꢉ

T

6ꢈ3/ꢉ

Hꢈ3/ꢉ

-3" /UT

"IT ꢆ /UT

,3" /UT

-)3/

-/3)

T

SUꢈ3)ꢉ

,3" )N

-3" )N

T

"IT ꢂ )N

-3ꢂꢅꢂꢆꢇ6ꢀ

Hꢈ3)ꢉ

30/44

DocID023884 Rev 3

RX95HF

Electrical characteristics

Figure 11. SPI timing diagram (Slave mode and CPOL = 1, CPHA = 1)

166ꢄLQSXW

W

Kꢅ166ꢆ

Fꢅ6&.ꢆ

68ꢅ166ꢆ

W

&+ꢅ6&.+ꢆ &+ꢅ6&./ꢆ

&32/ꢄ ꢄꢀ

&3+$ꢄ ꢄꢀ

W

Kꢅ62ꢆ

W

Yꢅ62ꢆ

06%ꢄ2XW

%LWꢄꢂꢄ2XW

/6%ꢄ2XW

0,62

026,

W

VXꢅ6,ꢆ

Kꢅ6,ꢆ

/6%ꢄ,Q

06%ꢄ,Q

%LWꢄꢀꢄ,Q

06ꢀꢁꢀꢂꢂ9ꢃ

DocID023884 Rev 3

31/44

43

Electrical characteristics

RX95HF

6.5

RF characteristics

Test conditions are T = 0°C to 50°C, unless otherwise specified.

A

Table 35. Tag Emulation characteristics

Symbol

Parameter

Condition

Min.

Typ.

Max.

Unit

Frequency of operating

field (carrier frequency)

f_C

13.553 13.56 13.567 MHz

Carrier Modulation Index

from reader

MI Carrier

%

ISO/IEC 14443 -Type A

100

Operating field strength in

ISO/IEC 14443

HField ⁽¹⁾

1.5

7.5

18

A/m

V

Input voltage between RX1

and RX2

V_MaxCarrier

Frequency of Subcarrier

modulation (ISO/IEC

14443)

(2)

f_S

f_C/ 16

Load Modulation Amplitude

ISO 10373-6 test

methods for ISO/IEC

14443-A @ 1.5 A/m

18

f_C+ f_S

f_C- f_S

mV

ALoad

ISO 10373-6 test

methods for ISO/IEC

14443-A @ 7.5A/m

f_C+ f_S

f_C- f_S

8

Load Modulation Amplitude

ECMA 356 test

methods for ECMA

340 @ 1.5 A/m

18

f_C+ f_S

f_C- f_S

ALoad

DataR

ECMA 356 test

methods for ECMA

340 @ 7.5 A/m

f_C+ f_S

f_C- f_S

8

mV

ISO/IEC 14443 Type A

106

Kbps

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

2. Parameter measured on samples using recommended output matching network.

Table 36. Field detection characteristics

Symbol

Parameter

Level of detection ⁽¹⁾

Min.

Typ.

Max.

Unit

0.5

8

A/m

1. Parameter measured using recommended output matching network for ISO/IEC 14443 communication.

32/44

DocID023884 Rev 3

RX95HF

Electrical characteristics

6.6

Oscillator characteristics

The external crystal used for this product is a 27.12 MHz crystal with an accuracy of

± 14 kHz.

(1) (2)

Table 37. HFO 27.12 MHz oscillator characteristics

Symbol

Parameter

Oscillator frequency

Conditions

Min. Typ. Max. Unit

f_XTAL

R_F

27.12

2

MHz

Feedback resistor

M

Recommended load capacitance

C

versus equivalent serial resistance of R_S= 30

6

pF

the crystal (R_S)⁽³⁾

(4)

t_SU(HFO)

Startup time

V_PSis stabilized

10

ms

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

2. Based on characterization, not tested in production.

3. The relatively low value of the R resistor offers a good protection against issues resulting from use in a

F

humid environment, due to the induced leakage and the bias condition change. However, it is

recommended to take this point into account if the Host is used in tough humidity conditions.

4.

t

is the startup time measured from the moment it is enabled (by software) to a stabilized 27.12 MHz

SU(HFO)

oscillation is reached. This value is measured for a standard crystal resonator and it can vary significantly

with the crystal manufacturer.

For C and C , it is recommended to use high-quality external ceramic capacitors in the

L1

L2

10 pF to 20 pF range (typ.), designed for high-frequency applications, and selected to match

the requirements of the crystal or resonator (see Figure 12). C and C are usually the

L1

L2

same size. The crystal manufacturer typically specifies a load capacitance which is the

series combination of C and C .

L1

L2

Figure 12. Typical application with a 27.12 MHz crystal

&

/ꢀ

I

;,1

+)2

ꢃꢉꢊꢀꢃꢄ0+]

FU\VWDO

5

)

1)&ꢄGHYLFH

;287

&

/ꢃ

DLꢀꢇꢀꢇꢈE9ꢃ

Note:

For C and C it is recommended to use high-quality ceramic capacitors in the 10 pF to

L1 L2

20 pF range selected to match the requirements of the crystal or resonator. C and C are

L1

L2,

usually the same size. The crystal manufacturer typically specifies a load capacitance which

is the series combination of C and C .

L1

L2

Load capacitance C has the following formula: C = C x C / (C + C ) + C where

L

L1

L2

L1

L2

stray

C

is the pin capacitance and board or trace PCB-related capacitance. Typically, it is

stray

between 2 pF and 7 pF.

DocID023884 Rev 3

33/44

43

Package mechanical data

RX95HF

7

Package mechanical data

In order to meet environmental requirements, ST offers these devices in different grades of

®

ECOPACK packages, depending on their level of environmental compliance. ECOPACK

specifications, grade definitions and product status are available at: www.st.com.

®

ECOPACK is an ST trademark.

This device is available in a 32-lead, 5x5 mm, 0.5 mm pitch, very thin fine pitch quad flat

pack no-lead package (VFQFPN).

Figure 13. 32-lead VFQFPN package outline

6HDWLQJꢄSODQH

&

GGG

&

$

$ꢀ

$ꢋ

'

H

ꢀꢂ

ꢌ

ꢀꢉ

ꢁ

E

(

(ꢃ

ꢃꢇ

/

ꢀ

ꢋꢃ

3LQꢄꢍꢄꢀꢄ,'

5ꢄ ꢄꢎꢊꢋꢎ

'ꢃ

/

%RWWRPꢄYLHZ

ꢇꢃB0(

34/44

DocID023884 Rev 3

RX95HF

Package mechanical data

Table 38. 32-pin VFQFPN package mechanical data

millimeters

Typ.

inches⁽¹⁾

Symbol

Note

Min.

Max.

Min.

Typ.

Max.

A

0.800

0.000

0.900

0.020

0.200

0.250

5.000

3.600

5.000

3.600

0.500

0.400

1.000

0.050

0.0315

0.0000

0.0354

0.0008

0.0079

0.0098

0.1969

0.1417

0.1969

0.1417

0.0197

0.0157

0.0394

0.0020

A1

A3

b

0.180

4.850

3.500

4.850

3.500

0.300

5.150

3.700

5.150

3.700

0.0071

0.1909

0.1378

0.1909

0.1378

0.0118

0.2028

0.1457

0.2028

0.1457

D

D2 (AMK_B)

1

E

E2 (AMK_B)

e

L

0.300

0.500

0.050

0.0118

0.0197

0.0020

ddd (AMK)

2

1. Values in inches are rounded to 4 decimal digits.

Note:

1) AMKOR Variation B. Dimensions are not in accordance with JEDEC.

2) AMKOR and MUAR.

DocID023884 Rev 3

35/44

43

Part numbering

RX95HF

8

Part numbering

Table 39. Ordering information scheme

Example:

RX

95

HF

– V

MD

5

T

Device type

RX = NFC transceiver for Tag Emulation

Wired access

95 = SPI

Frequency band

HF = High frequency (13.56 MHz)

Operating voltage

V = 2.7 to 5.5 V

Package

MD = 32-pin VFQFPN (5 x 5 mm)

Operating temperature

5 = –25° to +85° C

Packaging

T = Tape and Reel

Not all combinations are necessarily available. For a list of available options (speed,

package, etc.) or for further information on any aspect of this device, please contact your

nearest STMicroelectronics Sales Office.

36/44

DocID023884 Rev 3

RX95HF

Card emulation communication

Appendix A

Card emulation communication

The following information is a log of basic exchanges between the CR95HF transceiver and

RX95HF card emulator.

CR95HFDLL_STCMD: Is the standard RX95HF frame exchange command. In this command,

the first byte 01 is not sent, it is only requested by the RX95HF development software in

order to recognize if it is a user or service command.

CR95HFDLL_SENDRECV: Is the encapsulated CR95HF SendReceive command for which

command codes, number of bytes, and CRC are automatically appended to the parameter.

In this section,



The CR95HF data exchanges are in blue.

The RX95HF card emulation data exchanges are in green.

The CR95HF and RX95HF command overhead (command code, length of data and

transmission flag) is in bold.



The CRC value is in red.

When the CRC append option is set in the Protocol Select command, the CRC is

automatically appended by the RX95HF, but the CRC is not visible in the instruction log file.

When the CRC is present in the command or response, CRC reply is in italics.

The following symbols correspond to:

>>> Frame sent by Host to RX95HF

<<< Frame received by Host from RX95HF

DocID023884 Rev 3

37/44

43

Card emulation communication

RX95HF

Comment

Table 40. Example logs

Direc

Comment

CR95HF Reader

RX95HF Card Emulation

-tion

CR95

RX95

Exchange: Host -> Reader

Exchange: Host -> Card Emulator

REM, DEMO RX95HF for Card

Emulation Exchange

REM, 0A

REM, Check serial com with host

Check

RX95HF

connection

to Host

>>> RX95HFDLL_ECHO

<<< 5500

>>> RX95HFDLL_IDN

Set

Reader

Config.

<<<

000F4E4643204653324A41535434002

ACE

REM, POLLFIELD

ISO/IEC

14443

No Field

detected

Type A at

106 Kbps

>>> RX95HFDLL_STCMD, 01 0300

<<< 000100

REM, Reader for Card Emulation Test

Max waiting time for manual exchange

REM, Select Emulation Tag Mode

14443A

Set

RX95HF

config.

REM, 0B

Card Emu-

lator

ISO/IEC

14443 Type

A at 106

Kbps

>>> CR95HFDLL_STCMD, 01

020402000A05

>>> RX95HFDLL_STCMD, 01

02021208

<<< 0000

38/44

DocID023884 Rev 3

RX95HF

Comment

Card emulation communication

Table 40. Example logs (continued)

Direc

CR95HF Reader

RX95HF Card Emulation

Comment

-tion

REM, 02000180

REM, Read Default value Card

Emulator Configuration register ACCA

REM, CR95HFDll_STCmd

REM, CR95HFDll_STCmd 01

09043A00xx04

REM, ACCA (7:6 card clamp 00 default

REM, Default xx 52 Max 5A

REM, ACCA (5:4 Card Demod 01

noise immunity low sensitivity 10%

>>> CR95HFDLL_STCMD, 01

09043A005804

REM, ACCA (3:0 mod depth default 7

mon 0 max F)

<<< 0000

REM, READ Default value Reg ACCA

Set Reg Index @4

REM, Increase demodulator gain D3

Check Con-

figuration

>>> CR95HFDLL_STCMD, 01

0904680101D3

>>> RX95HFDLL_STCMD, 01

0903680004

<<< 0000

REM, increase Dec tolerance

REM, READ Reg ACCA card config 1

Reg @69 index 4

>>> CR95HFDLL_STCMD, 01

09110B00241204880F1F3F3F0100050

5005500

Set

Reader

Config.

>>> RX95HFDLL_STCMD, 01

0803690100

<<< 0000

<<< 000127

ISO/IEC

14443

Type A at

106 Kbps

BREAK

REM, CONFIGURE CARD

EMULATOR (Set UID)

REM, Set Anti-collision Filter Type A

UID 0251744AEF2280

(cont.)

REM, ATQA 4403 SAK 20 UID1

88025174 UID2 4AEF2280

Set

RX95HF

Identity

>>> RX95HFDLL_STCMD, 01

0D0B440320880251744AEF2280

<<< 0000

BREAK

REM, POLLFIELD

Check RF

Field On

>>> RX95HFDLL_STCMD, 01 0300

<<< 000101

RX95HF

Set in Lis-

tening

REM, LISTEN

>>> RX95HFDLL_STCMD, 01 0500

<<< 0000

mode

BREAK

DocID023884 Rev 3

39/44

43

Card emulation communication

RX95HF

Comment

Table 40. Example logs (continued)

Direc

Comment

CR95HF Reader

RX95HF Card Emulation

-tion

>>>

CR95HFDLL_ANTICOLSELECT123

------ ISO14443-A Start of Anti-Collision

Algorithm ------

ISO14443-A REQA

>>> CR95HFDLL_SENDRECV, 2607

<<< 80054403280000

>

<

ISO14443-A ANTICOL 1

Anti-colli-

sion Pro-

cess on RX

side (no

return to

Host)

>>> CR95HFDLL_SENDRECV,

932008

>

<<< 800888025174A9280000

ISO14443-A SELECT 1

<

>

<

Execute

Anti-colli-

sion Pro-

cess

>>> CR95HFDLL_SENDRECV,

937088025174A928

<<< 800624D836080000

Response

automati-

cally sent to

reader

ISO/IEC

14443

Type A

ISO14443-A ANTICOL 2

>>> CR95HFDLL_SENDRECV,

952008

>

<

<<< 80084AEF228007280000

ISO14443-A SELECT 2

ISO/IEC

14443-3

>>> CR95HFDLL_SENDRECV,

95704AEF22800728

>

<

<<< 800620FC70080000

--> UID = 0251744AEF2280

--> TAG selected

------ ISO14443-A End of Anti-Collision

Algorithm ------

BREAK

40/44

DocID023884 Rev 3

RX95HF

Comment

Card emulation communication

Table 40. Example logs (continued)

Direc

CR95HF Reader

RX95HF Card Emulation

Comment

-tion

Applicative Communication ISO/IEC 14443-4: Data Exchange between Reader (CR95HF) & Card Emulator

(RX95HF)

RX95HF is

in Listening

mode

REM, RATS 1A

>>> CR95HFDLL_SENDRECV,

E05028

>

<

>>>

After

capture,

Data is

transferred

to Host

which

RX95HFDLL_POLLING_READING

<<< 8005E050BCA508

REM,

1B

SEND ATS

060706757781028028

defines the

response

<<< 800F06757781028002F00800

>>> RX95HFDLL_STCMD, 01

060B06757781028002F0080028

BREAK

<<< 0000

REM, LISTEN

Applica-

tion comm

protocol

setup

RX95HF

returns to

Listening

mode

>>> RX95HFDLL_STCMD, 01 0500

<<< 0000

ISO/IEC

14443-4

BREAK

REM, PPS 2A

>>> CR95HFDLL_SENDRECV,

D0110028

>

<

>>>

After

capture,

Data is

transferred

to Host

which

RX95HFDLL_POLLING_READING

<<< 8006D0110052A608

REM,

2B

PPS

defines the

response

>>> RX95HFDLL_STCMD, 01

0606D07387080028

<<< 800AD073870800

<<< 0000

BREAK

REM, LISTEN

RX95HF

returns to

Listening

mode

>>> RX95HFDLL_STCMD, 01 0500

<<< 0000

BREAK

DocID023884 Rev 3

41/44

43

Card emulation communication

RX95HF

Comment

Table 40. Example logs (continued)

Direc

Comment

CR95HF Reader

RX95HF Card Emulation

-tion

REM, IBLOCK Exchange 3A

>>>

RX95HFDLL_POLLING_READING

>>> CR95HFDLL_SENDRECV,

0200A4040007D276000086010028

>

After

capture,

Data is

transferred

to Host

<<<

80100200A4040007D27600008601004

BF708

which

REM,

3B

IBLOCK

defines the

response

Applica-

tion comm

protocol

setup

<<< 800C029000F1090800

<

>>> RX95HFDLL_STCMD, 01

0608029000F109080028

<<< 0000

REM, LISTEN

ISO/IEC

14443-4

(cont.)

RX95HF

returns to

Listening

mode

>>> RX95HFDLL_STCMD, 01 0500

<<< 0000

BREAK

REM, Set RF OFF

No Field

error

>>> CR95HFDLL_STCMD, 01

02020000

>>>

RX95HFDLL_POLLING_READING

<<< 0000

<<< 8F00

BREAK

REM,

4B

Close SPI

link

Close SPI

link

>>> CR95HFDLL_RESET_SPI

<<< 0000

>>> RX95HFDLL_RESET_SPI

<<< 0000

42/44

DocID023884 Rev 3

RX95HF

Revision history

Table 41. Document revision history

Date

Revision

Changes

04-Jan-2013

1

Initial release.

Updated Section 5.3: IDN command (0x01) description on

page 15, Section 8: Part numbering on page 36 and title of

Appendix A: Card emulation communication on page 37.

15-Oct-2013

02-Jun-2014

2

Updated Section 3.2: Startup sequence on page 9, Table 31:

Absolute maximum ratings on page 28 and Appendix A: Card

emulation communication on page 37.

3

DocID023884 Rev 3

43/44

43

RX95HF

Please Read Carefully:

Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the

right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any

time, without notice.

All ST products are sold pursuant to ST’s terms and conditions of sale.

Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no

liability whatsoever relating to the choice, selection or use of the ST products and services described herein.

No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this

document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products

or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such

third party products or services or any intellectual property contained therein.

UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED

WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS

OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.

ST PRODUCTS ARE NOT DESIGNED OR AUTHORIZED FOR USE IN: (A) SAFETY CRITICAL APPLICATIONS SUCH AS LIFE

SUPPORTING, ACTIVE IMPLANTED DEVICES OR SYSTEMS WITH PRODUCT FUNCTIONAL SAFETY REQUIREMENTS; (B)

AERONAUTIC APPLICATIONS; (C) AUTOMOTIVE APPLICATIONS OR ENVIRONMENTS, AND/OR (D) AEROSPACE APPLICATIONS

OR ENVIRONMENTS. WHERE ST PRODUCTS ARE NOT DESIGNED FOR SUCH USE, THE PURCHASER SHALL USE PRODUCTS AT

PURCHASER’S SOLE RISK, EVEN IF ST HAS BEEN INFORMED IN WRITING OF SUCH USAGE, UNLESS A PRODUCT IS

EXPRESSLY DESIGNATED BY ST AS BEING INTENDED FOR “AUTOMOTIVE, AUTOMOTIVE SAFETY OR MEDICAL” INDUSTRY

DOMAINS ACCORDING TO ST PRODUCT DESIGN SPECIFICATIONS. PRODUCTS FORMALLY ESCC, QML OR JAN QUALIFIED ARE

DEEMED SUITABLE FOR USE IN AEROSPACE BY THE CORRESPONDING GOVERNMENTAL AGENCY.

Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void

any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any

liability of ST.

ST and the ST logo are trademarks or registered trademarks of ST in various countries.

Information in this document supersedes and replaces all information previously supplied.

The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.

STMicroelectronics group of companies

Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan -

Malaysia - Malta - Morocco - Philippines - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America

www.st.com

44/44

DocID023884 Rev 3

厂商	型号	描述	页数
SUMIDA	RX9PNP-102J-35	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-102J-80	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-102J-80TL	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-102K-35	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-102K-80	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-102K-80TL	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-103J-35	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-103J-80	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-103J-80TL	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页
SUMIDA	RX9PNP-103K-35	功率电感\u003c引脚类型： RX系列\u003e[ POWER INDUCTORS < Pin Type: RX Series> ]	7 页