ST25R95 datasheet(24/61 Pages) STMICROELECTRONICS

24 / 61 page

Protocol

Explanation

Response example

Comments

ISO/IEC 14443

Type A

NFC Forum Tag

Type 4A

NFC Forum Tag

Type 1

(Topaz)

NFC Forum Tag

Type 2

Response

example

80 or

90 (1)

80B30B8DB500

ISO/IEC 14443-A is bit

oriented protocol, so we can

receive non-integer amount of

bytes. Number of significant

bits in the 1st byte is the same

as indicated in the command

sent.

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

indexes start from 0 and bit

index can be 8, meaning that

collision affected parity.

Note that collision information

is only valid when bit ‘Collision

is detected’ is set (2).

Result code

Length of entire data field

Data received from TAG (including CRC if present)

7: Collision is detected

6: RFU

5: CRC error

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 detected

[7:4]: RFU

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

ISO/IEC 14443

Type B

NFC Forum Tag

Type 4B

Response

example

5092036A8D

0000000000

7171

3411

Result code

Length of entire data field

Data received from tag

Original (received) value of CRC

[7:2]: RFU

1: CRC error if set

0: RFU

FeliCa™

NFC Forum Tag

Type 3

Response

example

01010105017B0...93FF

<<<0x801201010105017

B06941004014B024F499

3FF00

Result code

Length of entire data field

Data received from tag (not including CRC)

[7:2]: RFU

1: CRC error if set

0: RFU

1. Result code 90: Response is decoded but number of byte is not an integer.

2. The collision information is only present for ISO14443A protocol with a bit rate of 106 kbps for transmission

and reception. When other protocols or bit rates are selected, the two additional bytes are not transmitted.

If Parity Framing mode is used, the parity bit stays unchanged. On transmission, it is not encoded and on

reception it is not decoded. The length of Data must be even. Each data byte is accompanied by an additional

byte which encodes the parity:

<DataByte>, <Parity>, <DataByte>, <Parity> …

Table 18. Structure of Parity byte

Bit

Description

Parity bit

[6:0]

Reserved for future use

ST25R95

Send receive (SendRecv) command (0x04) description

DS12807 - Rev 4

page 24/61

ST25R95 数据表(PDF) 24 Page - STMicroelectronics

ST25R95 数据表(HTML) 24 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61

数据表下载

链接网址

ST25R95 数据表(PDF) 24 Page - STMicroelectronics

ST25R95 数据表(HTML) 24 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61

数据表 下载

链接网址

数据表下载