The ST25TA02K-D device is a dynamic NFC/RFID tag that can be accessed from the RF interface. The RF interface is based on the ISO/IEC 14443 Type A standard. The

ST25TA02K-D is compatible with the NFC Forum Type 4 Tag specifications and supports all corresponding commands.

Figure 1 displays the block diagram of the ST25TA02K-D device.

Figure 1. ST25TA02K-D block diagram

3RZHU

PDQDJHPHQW

XQLW h/ΘƐǇƐƚĞŵ

ĂƌĞĂ

5)LQWHUIDFH

EDVHGRQ

,62,(&

7\SH$

VWDQGDUG

$QDORJ)URQWHQG

EDVHGRQ

,62,(&

7\SH$VWDQGDUG

,QWHUQDOWXQLQJ

FDSDFLWDQFH hƐĞƌŵĞŵŽƌǇ

*32

'LJLWDOXQLW

1)&)RUXP

7\SH7DJ

SURWRFRO

06Y9

8/66 DocID027817 Rev 5

ST25TA02K-D Functional description

Figure 2. Applicative schematic example

DQWHQQD

*32

677$.'

0LFURFRQWUROOHU

069

1. Decoupling capacitor

Signal name

Table 1. Signal names

Function

AC0, AC1

GPO

Antenna coils

Ground

Interrupt output

(1)

1. An external pull-up > 4.7 k Ω is required.

Figure 3. 8-pin package connections

9VV

*32

Direction

Open drain output

(1)

06Y9

1. See

Section 13: Package information for package dimensions, and how to identify pin 1.

Figure 4. 5-pin package connections

*32

9VV

$%&'

;<=:

7RSYLHZ

PDUNLQJVLGH

9VV

%RWWRPYLHZ

SDGVVLGH

1. See

Section 13: Package information for package dimensions, and how to identify pin 1.

06Y9

DocID027817 Rev 5 9/66

Functional description ST25TA02K-D

The ST25TA02K-D has just one functional mode available (see Table 2 ).

Mode

Tag mode

Supply source

Table 2. Functional mode

Comments

RF field only

The RF interface is connected, GPO Open drain transistor request an external Pull-up (>4.7 KOhm) to operate.

The ST25TA02K-D is supplied by the RF field and can communicate with an RF host (RFID reader or an NFC phone). The User memory can be accessed by the RF commands.

10/66 DocID027817 Rev 5

ST25TA02K-D Signal descriptions

2.1 Antenna coil (AC0, AC1)

These inputs are used to connect the device to an external coil exclusively. It is advised not to connect any other DC or AC path to AC0 or AC1.

When correctly tuned, the coil is used to access the device using NFC Forum Type 4 commands.

2.2 Ground )

, when connected, is the reference for the GPO and the other pads, even AC0 and AC1.

DocID027817 Rev 5 11/66

Signal descriptions

2.3 General Purpose Output (GPO)

ST25TA02K-D

The GPO pad is an open drain pad and a external pull-up resistor shall be connected to it.

This pad is a configurable output signal, driven a low level when configured event occurs, otherwise it remains in an high impedance state. Its behavior is consistent with the RF session activated and with the mode chosen by the user.

The user can select one of these configurations

(a)

• SessionOpen: an RF session is ongoing.

• MIP (NDEF Message updating In Progress): the RF host is writing an NDEF length different from 0x0000. This mode can be used to detect when the RF host changes the

NDEF message as defined by the NFC Forum.

• WIP (Writing In Progress): the ST25TA02K-D is executing a writing operation.

• INT (interrupt): the RF host can force the ST25TA02K-D to send an alternate pulse on the GPO pin.

• State mode: the RF host can control the state of the GPO pad during the RF session.

• RF busy: an RF host is communicating with the ST25TA02K-D.

• Field detection: the RF field is sufficient to establish an RF communication with the

ST25TA02K-D.

GPO configuration byte can be locked, by setting its Most Significant Bit to 1 (1xxx 0000 b).

Once locked, this byte cannot be changed anymore.

12/66 a. See

Table 65: GPO timings measurement for more details.

DocID027817 Rev 5

ST25TA02K-D Signal descriptions

When the GPO is configured as "Session Open", it goes to the low state when an RF session is ongoing (see

Figure 5 ).

An RF session is taken when ST25TA02K-D receives a valid Select Application. The session is released when:

• ST25TA02K-D receives a valid Deselect command

• RF field becomes OFF

GPO is driven low after a delay ( 1.

) when the session is open.

GPO is released after a delay (

) when the session is released.

Figure 5. GPO configured as Session Open (GPO field = 0x10 or 0x90)

5)FKDQQHO

*32DV

6HVVLRQ2SHQ

5)6HVVLRQ 5)6HVVLRQ

069

1. CmdEOFtoGPlow (RF command End of frame to GPORF Session pad low)

2. CmdEOFtoGPHZ (RF command End of frame to GPORF Session pad HZ)

DocID027817 Rev 5 13/66

Signal descriptions

2.3.2

ST25TA02K-D

WIP Writing in Progress configuration (GPO field = 0x20 or 0xA0)

When the GPO is configured as "WIP", it goes to the low state during an RF writing operation (see

Figure 6 ).

During an RF session, when ST25TA02K-D updates a file, GPO is driven low after a delay

( 1.

) following the beginning of the correspondent UpdateBinary command execution.

GPO will remain low during the writing time ( 2.

), before being released.

Figure 6. GPO configured as WIP (GPO field = 0x20 or 0xA0)

5)FKDQQHO

*32DV:,3

8SGDWH

FRPPDQG

(QGRIZULWLQJ

RSHUDWLRQ

$Q\RWKHU

FRPPDQG

069

1. CmdEOFtoGPlow (RF Command End of frame to GPO low)

2. Writing time duration

14/66 DocID027817 Rev 5

ST25TA02K-D Signal descriptions

NDEF

(GPO field = 0x30 or 0xB0)

When the GPO is configured as MIP, its state goes to the low state when the RF host writes the NDEF length to another value than 0x0000 (see

Figure 7 ).

During an RF session, when ST25TA02K-D changes an NDEF file and updates the NDEF length with a value different from 0x0000, GPO is driven low after a delay ( 1.

) following the beginning of the correspondent UpdateBinary command execution.

GPO will remain low during the writing time ( 2.

), before being released.

5)FKDQQHO

Figure 7. GPO configured as MIP (GPO field = 0x30 or 0xB0)

8SGDWHWKH1'()

OHQJWK [

677$[.'

UHVSRQVH

$Q\RWKHU

FRPPDQG

*32DV0,3

069

1. CmdEOFtoGPlow (RF command End of frame to GPO low)

2. Writing time duration

DocID027817 Rev 5 15/66

Signal descriptions ST25TA02K-D

The RF host can send a negative pulse on the GPO pad. The GPO pad goes to high state at the end of the command and goes to the high state at the end of the ST25TA02K-D response (see

Figure 8

During an RF session, when ST25TA02K-D receives a valid Interrupt command,

ST25TA02K-D GPO pin is driven low after ( 1.

). Then GPO pin is released at the end of the response (

Figure 8. GPO configured as INT (GPO field = 0x40 or 0xC0)

5)FKDQQHO

6HQG

,QWHUUXSW

677$[.'

UHVSRQVH

$Q\RWKHU

RSHUDWLRQ

*32DV,17

069

1. CmdEOFtoGPlow (RF command End of frame to GPO low)

2. RespEOFGPlow

16/66 DocID027817 Rev 5

ST25TA02K-D

2.3.5

Signal descriptions

State Control configuration (GPO field = 0x50 or 0xD0)

When the GPO is configured as State Control, the RF host can control the state of the GPO by sending a dedicated command (see

Figure 9 ).

During an RF session, the ST25TA02K-D can control the GPO pin. After receiving a valid reset GPO command, GPO pin is driven low after a delay ( 1.

). GPO will be released after a valid Set command or after a Power off.

Figure 9. GPO configured as State Control (GPO field = 0x50 or 0xD0)

5)FKDQQHO

5HVHW*32

FRPPDQG

$Q\RWKHU

FRPPDQG

6HW*32

FRPPDQG

*32DV

6WDWH&RQWURO

069

1. CmdEOFtoGPlow (RF Reset GPO command End of frame to GPO low)

2. CmdEOFtoGPHZ (RF Set GPO command End of frame to GPO HZ)

DocID027817 Rev 5 17/66

Signal descriptions

2.3.6 RF busy configuration (GPO field = 0x60 or 0xE0)

ST25TA02K-D

When the GPO is configured as RF busy, the GPO goes to the low state, both when the

ST25TA02K-D is processing an RF command or when an RF session is ongoing (see

Figure 10

When an RF field is present, GPO is driven low after a delay ( 1.

) when ST25TA02K-D detects the first command. If the RF session is ongoing and ST25TA02K-D receives a notsupported command, GPO remains low. It will be released only at the end of the RF

session, after ( 2.

Figure 10. GPO configured as RF busy (GPO field = 0x60 or 0xE0)

5)FKDQQHO

*32DV

5)EXV\

5)FRPPDQGQRW

VXSSRUWHG

6HQV5HT

6HQV5HV

5)FRPPDQG

6/3B5(4RU

6'(6RU

EDGFRPPDQG

RU5))LHOG2))

069

1. CmdSOFtoGPlow (RF command Start of frame to GPO low)

2. CmdEOFtoGPHZ (RF command End of frame to GPO HZ)

18/66 DocID027817 Rev 5

ST25TA02K-D Signal descriptions

When the GPO is configured as Field detect, the GPO goes to the low state when

ST25TA02K-D detects an RF Field (see

Figure 11 ).

When an RF field is present, GPO is driven low after a delay when ST25TA02K-D detects this field. Whatever the activity during the RF field detection (communication with the reader or not), GPO will stay low. It will be released when ST25TA02K-D leaves the RF field.

Figure 11. Field detect (GPO field = 0x70 or 0xF0)

PLQ

5)ILHOG

*32

)'(721

)'(72))

069

DocID027817 Rev 5 19/66

ST25TA02K-D memory management

3 ST25TA02K-D memory management

ST25TA02K-D

The ST25TA02K-D supports the NDEF Tag Application as defined in the NFC Forum Type 4

Tag. The ST25TA02K-D is composed of three files:

• a Capability Container (CC) file

• an NDEF file

• a System file: this file is an ST-proprietary file

The System file contains some information on the configuration of the ST25TA02K-D device. The CC file gives some information about the ST25TA02K-D itself and the NDEF file. The NDEF file contains the User data.

The file identifier is the value used in the Select command to select a file.

File identifier

0xE101

0xE103

0x0001

System file

CC file

NDEF file

Table 3. File identifier

Meaning

The CC file gives some information about the ST25TA02K-D and the NDEF file. This file is a read-only file for the RF host and cannot be modified by issuing a write command.

The T field, Read Access and Write Access fields can be changed by the RF host by issuing a specific process (refer to

Section 7: Functional procedures

File offset

0x0000

0x0002

0x0003

0x0005

Table 4. CC file layout for 1 NDEF file

Meaning Value

Length CC file

Mapping version

(1)

Maximum number of bytes that can be read

0x000F

0x20 or 0x10

0x00FF

Maximum number of bytes that can be written 0x0036

Comments

15 bytes

V 2.0 or V 1.0

255 bytes

54 bytes

20/66 DocID027817 Rev 5

ST25TA02K-D ST25TA02K-D memory management

File offset

0x0007

0x0008

0x0009

0x000B

0x000D

0x000E

Table 4. CC file layout for 1 NDEF file (continued)

Meaning Value

NDEF file control TLV

0x04

(2)

0x06

0x0001

0x0100

0x00

(2)

0x00

(2)

Comments

T field

L field

FileID

Maximum NDEF file size in Byte

Read access

Write access

1. According to the reader command format ST25TA02K-D will automatically align to the corresponding NFC

Forum version.

2. Delivery state.

The NDEF file contains the NDEF message which contains the User data. The RF host can read and write data inside the file. The first two bytes named NDEF Message Length define the size of the NDEF message. The NDEF Message Length shall be managed by the application and the ST25TA02K-D device does not check if its value is relevant vs the data written by the RF host. The ST25TA02K-D device uses the NDEF Message Length, e. g. the standard read can be processed only inside the NDEF message; otherwise, the

ST25TA02K-D device returns an error code. For more details about the read command, refer to

Section 5.6.7: ReadBinary command .

File offset

0x0000

0x0004

...

0x00FC

Byte 0

Table 5. NDEF file layout

Byte 1 Byte 2

NDEF Message Length

User data User data

...

User data

...

Byte 3

User data

...

User data

DocID027817 Rev 5 21/66

ST25TA02K-D memory management ST25TA02K-D

The system file specifies the configuration of the ST25TA02K-D. Table 6

lists the different fields.

File offset Field name

Table 6. Field list

No. of bytes Read access Write access Delivery state

0x0000 Length system file

0x0002 GPO Config

0x0003 Event Counter

(3)

Config

0x0004

20 bits counter

(MS nibble 0x0)

0x0007 Product version

3 yes yes yes yes

yes

(1) yes

(1) none

0x0012

0x70

(2)

0x00

0x000000

0x0008 UID

0x000F Memory Size - 1

0x0011 IC reference code

1 yes yes yes yes none none none none

0x13

(4)

0x02F2 xx xx xx xx xx

(5)

0x00FF

0xF2

1. Configuration bytes can be locked by setting the Most significant bit to 1. Once locked, these bytes cannot be changed anymore.

2. Field detect as default GPO configuration.

3. Counter is not activated by default.

4. ST reserved.

5. x values are defined by ST to ensure UID unicity.

Table 7. Details about the GPO field b7 b6-b4 b3-b0 File offset

0x0002

GPO config lock bit:

0b0: unlocked

0b1: locked

GPO configuration:

0b000: Not used

0b001: Session opened

0b010: WIP

0b011: MIP

0b100: Interrupt

0b101: State Control

0b110: RF Busy

0b111: Field Detect

0b0000 ST Reserved

22/66 DocID027817 Rev 5

ST25TA02K-D ST25TA02K-D memory management

Warning: When GPO config lock bit is set to “1”, the whole byte cannot be changed anymore.

3.2

3.2.1

File offset

0x0003

Counter config lock bit:

0b0: unlocked

0b1: locked

0b00000: ST reserved

Counter enable:

0b0: disable

0b1: enable

Counter increment:

0b0: on Read

0b1: on Write

Table 8. Details about the Counter config field b7 b6-b2 b1 b0

Read and write access rights to the NDEF File

The NDEF file can be locked for read or write accesses. It is also protected by a 128-bit password that the host shall present before accessing the NDEF file. There are two 128-bit passwords, one for the read access and the other one for the write access.

An NDEF file can be permanently locked for read or write accesses. Thus, the host cannot access the NDEF file.

The read password shall be sent to the ST25TA02K-D device before reading a read-locked

NDEF file.

The write password shall be present on the ST25TA02K-D device before writing a write-locked NDEF file. The write password shall be sent to change the read or write access. The read or write access right is defined for the NDEF file.

State of the Read and Write access rights

Two bytes in the CC file are used to define the Read and Write access rights to the NDEF file. For more details, refer to

Section 3.1.2: CC file layout .

Value

Table 9. Read access right

Meaning

0x00

0x80

0xFE

Read access without any security

Locked

(1)

Read not authorized

1. The read password shall be sent before reading in the NDEF file.

DocID027817 Rev 5 23/66

ST25TA02K-D memory management ST25TA02K-D

Value

Table 10. Write access right

Meaning

0x00

0x80

0xFF

Write access without any security

Locked

(1)

Write not authorized

1. The write password shall be sent before writing in the NDEF file.

The state 0xFF and 0xFE cannot be changed by using the Read or Write passwords.

The state diagram in

Figure 12 shows how to change the access right to read an NDEF file.

Figure 12. Changing the read access right to an NDEF file

[

/RFNWKH1'()ILOH

8QORFNWKH1'()ILOH

[ [)(

3HUPDQHQWO\ORFNWKH1'()ILOH

1. See the procedure to lock the read access ( Section 7.4: Locking an NDEF file ).

2. See the procedure to unlock the read access (

Section 7.5: Unlocking an NDEF file

3. See the procedure to permanently lock the read access.

4. Proprietary state, not defined by NFC Forum Type 4 Tag.

069

24/66 DocID027817 Rev 5

ST25TA02K-D ST25TA02K-D memory management

The state diagram on

Figure 13

shows how to change the write access right to an NDEF file.

Figure 13. Changing the write access right to an NDEF file

[

/RFNWKH1'()ILOH

8QORFNWKH1'()ILOH

3.3

[

3HUPDQHQWO\ORFNWKH1'()ILOH

[))

069

1. See the procedure to lock the write access.

2. See the procedure to unlock the write access.

3. See the procedure to permanently lock the write access (

Section 7.6: Reaching the read-only state for an

NDEF file ).

4. Proprietary state, not defined by NFC Forum Type 4 Tag.

Access right life time

The access right life time is validated while the NDEF file is selected or until the end of the

RF session. Once the read or write access right is granted, the host can send one or more

ReadBinary or UpdateBinary commands.

At the end of a session or when the host selects another file, the read and write access rights are initialized.

Note:

The NDEF file passwords protect the read or write access from an RF interface from/to an

NDEF file.

Two NDEF file passwords are available for each NDEF file:

• Read password

• Write password

The length of a password is 128 bits (16 bytes).

The delivery state for all passwords = 0x00000000000000000000000000000000.

DocID027817 Rev 5 25/66

ST25TA02K-D memory management ST25TA02K-D

A 20 bits counter can track the read or write events on the NDEF file.

It benefits from an anti-tearing mechanism, that ensures the consistency of the counter, even if there has been an electrical problem during its increment.

The value of the Read/Write counter can be checked by any application, by reading suitable bytes in System file (see

Section 3.1.4

If enabled, the Read/Write counter will be incremented on first event (exclusively Read or

Write) which is performed on the NDEF File, inside an RF session (an RF session is entered when ST25TA02K-D receives a valid "Select Application" command).

The counter is reset when it is disabled.

Apart from these procedures, there is no way to act on the value of this counter.

The Read/Write counter can be configured through a specific byte in System file (see

Section 3.1.4

This configuration byte allows to:

• Enable or disable this counter

• Define if the counter must be incremented on a read or write sequence

• Definitively lock this configuration byte

Warning: Once this configuration byte is locked, it cannot be changed anymore: the counter will behave accordingly.

If enabled, the Read/Write counter will have an impact on the execution time of the event which is countered: the counter increment needs some write cycles of specific EEPROM cells automatically managed by ST25TA02K-D, which increase the total time before the response is sent to the reader.

As a consequence, an S(WTX) request can be issued on the command that will increment

the counter (see Section 5.4: S-Block format

26/66 DocID027817 Rev 5

ST25TA02K-D Communication mechanism

4.1

This section describes the principle of communication between an RF host and the

ST25TA02K-D device.

Master and slave

The ST25TA02K-D acts as a slave device on the RF channel and therefore waits for a command from the RF host before sending its response.

The RF host shall generate the RF field and the RF commands.

DocID027817 Rev 5 27/66

RF command sets

5 RF command sets

ST25TA02K-D

This section describes the ST25TA02K-D command sets that can be issued by the RF host.

There are three command families:

• the NFC Forum Type 4 Tag command set

• the ISO/IEC 7816-4 command set

• the proprietary command set

The NFC Forum Type 4 Tag command set and the ISO/IEC 7816-4 command set use the I-

Block format. For more details about the I-Block format, refer to Section 5.2: I-Block format .

Two other command formats exist:

• the commands using the R-Block format

• the commands using the S-Block format

For more details about these formats, refer to

Section 5.3: R-Block format

and to

Section 5.4: S-Block format .

This section gives a brief description of the RF host commands. The format of these command sets is the I-Block format.

Table 11 lists the RF command sets.

Family command set

NFC Forum

Type 4 Tag

ST proprietary

Table 11. RF command sets

Command name

Class byte

Instruction code

NDEF Tag Application Select

CC select

NDEF select

System select

ReadBinary

UpdateBinary

0x00

0xA4

0xB0

0xD6

Verify

ISO/IEC 7816-4

ChangeReferenceData

EnableVerificationRequirement

DisableVerificationRequirement

EnablePermanentState

ExtendedReadBinary

UpdateFileType

SendInterrupt

StateControl

0x00

0xA2

0x20

0x24

0x28

0x26

0x28

0xB0

0xD6

Brief description

NDEF Tag Application Select

Selects the CC file

Selects the NDEF file

Selects the system file

Reads data from file

Writes or erases data to an NDEF file

Checks the right access of an NDEF file or sends a password

Changes a Read or write password

Activates the password security

Disables the password security

Enables the Read Only or Write Only security state

Reads data from file

Sets file type to NDEF or proprietary

Generates a pulse on the GPO pin

Drives the state of the GPO pin

28/66 DocID027817 Rev 5

ST25TA02K-D

5.1

RF command sets

Structure of the command sets

The exchange of data between the RF host and the ST25TA02K-D uses three kinds of data formats, called blocks:

• I-Block (Information block): to exchange the command and the response

• R-Block (Receive ready block): to exchange positive or negative acknowledgment

• S-Block (Supervisory block): to use either the Deselect command or the Frame Waiting eXtension (WTX) command or response

This section describes the structure of I-Block, R-block and S-Block. This format is used for the application command set.

The I-Block is used to exchange data between the RF host and the ST25TA02K-D. It is composed of three fields.

Table 12 details the I-Block format.

Name

PCB

Length 1 byte

PCB field

DID field (optional)

RF host to ST25TA02K-D: C-APDU

ST25TA02K-D to RF host: R-APDU

2 CRC bytes

Table 12. I-Block format

SoD Payload

DID

1 byte

1 to 251 bytes

EoD

CRC

2 bytes

DocID027817 Rev 5 29/66

RF command sets

Note:

ST25TA02K-D b7-b6

Table 13. PCB field of the I-Block format b5 b4

0b00 0 0

I-Block

RFU

Must be set to 0

DID field is present, if bit is set

Must be set to 0

Must be set to 1

Block number (1)

1. Follow ISO 14443_4 Block numbering rules (see note) b3

X b2

0 b1

1 b0

Block numbering rules:

Reader rules:

Rule A: The Reader block number shall be initialized to 0.

Rule B: When an I-block or an R(ACK) block with a block number equal to the current block number is received, the Reader shall toggle the current block number before optionally sending a block to the

ST25TA02K-D.

ST25TA02K-D rules:

Note:

Rule C: The ST25TA02K-D block number shall be initialized to 1 at activation.

Rule D: When an I-block is received, the ST25TA02K-D shall toggle its block number before sending a block.

The ST25TA02K-D may check if the received block number is not in compliance with Reader rules to decide neither to toggle its internal block number nor to send a response block.

Rule E: When an R(ACK) block with a block number not equal to the current

ST25TA02K-D block number is received, the ST25TA02K-D shall toggle its block number before sending a block.

There is no block number toggling when an R(NAK) block is received.

When the RF host sends a command to the ST25TA02K-D the format of the payload is the

C-APDU.

When the ST25TA02K-D sends a command to the RF host, the format of the payload is the

R-APDU.

30/66 DocID027817 Rev 5

ST25TA02K-D

5.2.1

RF command sets

C-APDU: payload format of a command

The C-APDU format is used by the RF host to send a command to the ST25TA02K-D.

Table 14 describes its format.

Name

CLA INS

Table 14. C-APDU format

Payload field

P1 P2 L

1 byte Length 1 byte 1 byte 1 byte 1 byte

Class byte

- 0x00: standard command

- 0xA2: ST command (1)

Instruction byte

Param Byte 1

Param Byte 2

Number of bytes of the Data field

Data bytes

Number of bytes to be read in the ST25TA02K-D memory

1. See

Table 11

Data

Lc byte

1 byte the ST25TA02K-D uses the I-Block format to reply to a command that used the I-Block format. This format is described in

Table 15 .

Name

Table 15. R-APDU format

Payload field

Data (optional)

Le byte

SW1

1 byte Length

Data

Status byte 1

Status byte 2

SW2

1 byte

DocID027817 Rev 5 31/66

RF command sets ST25TA02K-D

The R-Block is used to convey positive or negative acknowledgment between the RF host and the ST25TA02K-D.

NFC frame

Table 16. R-Block format

SoD

PCB DID

Length 1 byte

R(ACK) without the DID field: 0xA2 or 0xA3

R(ACK) with the DID field: 0xAA or 0xAB

R(NAK) without the DID field: 0xB2 or 0xB3

R(NAK) with the DID field: 0xBA or 0xBB

DID field (optional)

2 CRC bytes

1 byte

Payload

0 byte

EoD

CRC

2 bytes

There are two kinds of R-Blocks:

• R(ACK): the acknowledgment block sent by the RF host or by the ST25TA02K-D

• R(NAK): the non-acknowledgment block sent by the RF host b7-b6

0b10

R-Block

Must be set to 1.

0: ACK

1: NAK

0: DID field is not present

1: DID field is present

Must be set to 0

Must be set to 1

Block number

Table 17. R-Block detailed format b5 b4 b3 b2

1 X X 0 b1

1 b0

32/66 DocID027817 Rev 5

ST25TA02K-D RF command sets

The S-Block is used to exchange control information between a reader and a contactless tag.

NFC frame

Table 18. S-Block format

PCB

SoD

DID

Payload

EoD

CRC

Length 1 byte 1 byte 1 byte 2 bytes

0xC2: for S(DES) when the DID field is not present

0xCA: for S(DES) when the DID field is present

0xF2: for S(WTX) when the DID field is not present

0xFA: for S(WTX) when the DID field is present

DID field (optional)

WTX field (optional)

(1)

2 CRC bytes

1. This field is present when b5-b4 bits are set to 0b11 (S-Block is a WTX). See

Table 19: S-Block detailed format

There are two requests using the S-Block format:

• S(DES): the deselect command

• S(WTX): the Waiting Frame eXtension command or response.

A Waiting Time eXtension request occurs in RF when the operating time needed by

ST25TA02K-D is greater than 19.2 ms.

The WTX field indicates the increase time factor to be used in this command execution

(FDTtemp = WTX * 19.2 ms). WTX depends on FWI.

Table 19. S-Block detailed format b5-b4 b3 b2

X X 0 b1

1 b0

0 b7-b6

0b11

S-Block

0b00: Deselect

0b11: WTX

0: DID field is not present

1: DID field is present

Must be set to 0

Must be set to 1

Must be set to 0

DocID027817 Rev 5 33/66

RF command sets

Note:

ST25TA02K-D

After receiving the deselect command, the session is released and ST25TA02K-D enters the Standby power mode.

In response to a RATS command, ST25TA02K-D returns FWI parameter (default frame waiting time used); when ST25TA02K-D needs more time for a command execution, it requests a frame waiting time extension by responding 0xF2 0xWTX (Request waiting time =

FWI * WTX). If the reader accepts the ST25TA02K-D request, it acknowledges it by sending the command 0xF2 0xWTX. The frame waiting time becomes FWI * WTX for the current command only.

5.5

5.6 CRC of the RF frame

The two CRC bytes check the data transmission between the RF host and the

ST25TA02K-D. For the RF frame, the CRC is computed on all the data bits in the frame, excluding parity bits, SOF and EOF, and the CRC itself.

The CRC is as defined in ISO/IEC 13239. The initial register content shall be 0x6363 and the register content shall not be inverted after calculation.

NFC Forum Type 4 Tag protocol

5.6.2

ST25TA02K-D command set is built to easily support the NFC Forum Type 4 Tag protocol.

Command name

NDEF Tag Application Select

Capability Container Select

NDEF Select

System File Select

ReadBinary

UpdateBinary

Table 20. Command set overview

Brief description

Select the NDEF Tag Application

Select the capability container (CC) file using the Select command

Select the NDEF file using the Select command.

Select the system file using the Select command.

Read data from a file

Write new data to a file

Status and error codes

This section lists the status and the error code of the ST25TA02K-D.

Value

Table 21. Status code of the ST25TA02K-D

SW1 SW2 Comment

0x90 0x00 Command completed successfully

34/66 DocID027817 Rev 5

ST25TA02K-D

Length

Value

RF command sets

Table 22. Error codes of the ST25TA02K-D

SW1 SW2

Comment

1 byte 1 byte

0x62

0x63

0x65

0x67

0x69

0x6A

0x6D

0x6E

0x82

0x00

0xCX

0x81

0x00

0x81

0x82

0x84

0x80

0x82

0x84

0x86

0x00

End of file or record reached before reading Le bytes

Password is required

Password is incorrect, X additional retries allowed (X can take values 0,

1 and 2)

Unsuccessful updating

Wrong frame length

Command is incompatible with the file structure

Security status not satisfied

Reference data not usable

Incorrect parameters Le or Lc

File or application not found

File overflow (Lc error)

Incorrect P1 or P2 values

INS field not supported

Class not supported

DocID027817 Rev 5 35/66

RF command sets ST25TA02K-D

5.6.3 NDEF Application Select command the RF host shall send this command to activate the NDEF Tag Application.

To activate the NDEF Tag Application, the RF host sends the Select command (see

Table 23 ) in addition to the sequence defined in the NFC Forum digital protocol.

Table 23 defines the C-APDU of the Select command to select the NDEF Tag Application

(called NDEF Tag Application Select).

Name

Table 23. C-APDU of the NDEF Tag Application Select command

CLA INS P1 P2 Lc Data

0x00 0xA4 0x04 0x00 0x07

0xD27600

00850101

Class byte

Select instruction code

P1 field

P2 field

Number of bytes of data

Application ID

Le field

0x00

Table 24 defines the R-APDU of the NDEF Tag Application Select command.

Length

Value

Table 24. R-APDU of the NDEF Tag Application Select command

Data SW1 SW2 Comment

1 byte

0x90

0x6A

0x6D

1 byte

0x00

0x82

0x00

Command completed

NDEF Tag Application not found

Class not supported

Note:

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

The RF host uses the Capability Container Select procedure to select the capability container (CC) file.

The CC file is selected when this command returns "command completed" in the R-APDU.

Table 25 defines the C-APDU of the Select command to select the CC file (called Capability

Container Select).

36/66 DocID027817 Rev 5

ST25TA02K-D

Note:

RF command sets

Name

Table 25. C-APDU of the Capability Container Select command

CLA

Class byte

0x00

Select instruction code

P1 field

P2 field

Number of bytes of data

CC file ID

(empty field)

INS

0xA4

0x00

0x0C

0x02

Data

0xE103

Table 26 defines the R-APDU of the CC Select command.

Length

Value

Table 26. R-APDU of the Capability Container Select command

Data SW1 SW2 Comment

1 byte

0x90

0x6A

0x6D

1 byte

0x00

0x82

0x00

Command completed

File or application not found

Class not supported

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

The RF host uses the NDEF Select command to select the NDEF file.

The NDEF file is selected when this command returns "command completed" in the

R-APDU.

Table 27 defines the C-APDU of the Select command to select the NDEF file

(called NDEF Select).

Name CLA

Table 27. C-APDU of the NDEF Select command

0x00

Class byte

Select instruction code

P1 field

P2 field

Number of bytes of data

0x0001: NDEF file

(empty field)

INS

0xA4

0x00

0x0C

0x02

Data

0x0001

DocID027817 Rev 5 37/66

RF command sets

Table 28 defines the R-APDU of the NDEF Select command.

Length

Value

Data

Table 28. R-APDU of the NDEF Select command

SW1 SW2 Comment

1 byte

0x90

0x6A

1 byte

0x00

0x82

Command completed

File or application not found

ST25TA02K-D

Note:

5.6.6

Note:

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

System File Select command

The RF host uses this command to select the system file.

The System file is selected when this command returns “command completed” in the

R-APDU.

Table 29 defines the C-APDU of the command to select the System file (called System

Select).

Name

Table 29. C-APDU of the System File Select command

CLA

Class byte

0x00

Select instruction code

P1 field

P2 field

Number of bytes of data

System file ID

(empty field)

INS

0xA4

0x00

0x0C

0x02

Data

0xE101

Table 30 defines the R-APDU of the System File Select command.

Length

Value

Table 30. R-APDU of the System File Select command

Data SW1 SW2 Comment

1 byte

0x90

0x6A

1 byte

0x00

0x82

Command completed

System file not found, no data is returned

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

38/66 DocID027817 Rev 5

ST25TA02K-D RF command sets

Note:

On receiving the ReadBinary command, the ST25TA02K-D reads the requested memory field and sends back its value in the R-APDU response.

Before sending a ReadBinary command, a file shall be selected by using a Select command.

The Response of the ReadBinary command is successful when the data to be read is within the selected file

(a)

, that is when the sum of P1-P2 and Le fields is equal to or lower than the selected file length.

Table 31 defines the ReadBinary command.

Name

Table 31. C-APDU of the ReadBinary command

CLA INS P1 and P2

0x00

Class byte

Read instruction code

0xB0

Offset in the file selected

(empty field)

Number of bytes to read between

0x01 ≤ Le ≤ max(Selected File length, 0xFFh)

2 bytes

Data

1 byte

Table 32 defines the R-APDU of the ReadBinary command.

Length

Value

Table 32. R-APDU of the ReadBinary command

Data SW1 SW2 Comment

Content read

1 byte

0x90

0x67

0x69

0x6A

0x6E

1 byte

0x00

0x82

0x00

Command completed

Wrong length

Security status not satisfied

File or application not found

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

a. For more details about CC file, refer to

Section 3.1.2: CC file layout .

For more details about NDEF file, refer to

Section 3.1.3: NDEF file layout

For more details about System file, refer to Section 3.1.4: System file layout .

DocID027817 Rev 5 39/66

RF command sets ST25TA02K-D

Note:

On receiving the UpdateBinary command, the ST25TA02K-D writes the data field into the selected file and sends back a status in the R-APDU response. If needed, ST25TA02K-D

will request a timing extension (see Section 5.4

Before sending an UpdateBinary command, a file shall be selected by issuing a Select command.

Table 33 defines the UpdateBinary command.

Name

Table 33. C-APDU of the UpdateBinary command

CLA INS P1 and P2 Lc Data

2 bytes 1 byte Lc bytes 0x00

Class byte

Write instruction code

0xD6

Offset in the file selected

Number of bytes of data (0x01 ≤ Lc ≤

Data to write in the ST25TA02K-D memory

(empty field)

Length

Value

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

Table 34 defines the R-APDU of the UpdateBinary command.

Table 34. R-APDU of the UpdateBinary command

Data SW1 SW2 Comment

1 byte

0x90

0x65

0x67

0x69

0x6A

0x6E

1 byte

0x00

0x81

0x00

0x82

0x00

Command completed

Unsuccessful updating

Security status not satisfied

File or application not found

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

40/66 DocID027817 Rev 5

ST25TA02K-D

5.7

RF command sets

ISO/IEC 7816-4 commands

The ISO/IEC 7816-4 command set offers some extended features such as the protection of the NDEF file. This command set is used to manage the right access of the NDEF file.

The Verify command has two functions:

Check if a password is required to access to the NDEF file (the LC field = 0x00).

2. Check that the password embedded in the Verify command enables the access to the memory (the Lc field = 0x10 and the password is present).

When the Lc field if equal to 0x00, the verify command returns a success code (0x90 00) provided that the access to the NDEF file does not require a password. When the access to the NDEF file is protected, the response to the Verify command returns an error code

(0x63 00).

When the Lc field equals 0x10, on receiving the Verify command, the ST25TA02K-D compares the requested password with the data contained in the request and reports whether the operation has been successful in the response.

Before sending this command, an NDEF file shall be selected by issuing the NDEF Select command. Thus, this command checks the right access condition of the last NDEF file selected.

After a successful command, an access is granted for the whole NDEF file.

Table 35 defines the Verify command.

Name CLA

Table 35. Verify command format

INS P1 and P2

0x00 0x20

Class byte

Instruction code

Password identification

0x0001: Read NDEF password transmit

0x0002: Write NDEF password transmit

Other: RFU

(1)

0x00: the password is not present

0x10: the password is present in the data field

Password

(empty field)

2 bytes

1. Return ERROR code when used.

1 byte

Data

Lc bytes

DocID027817 Rev 5 41/66

RF command sets

Note:

5.7.2

ST25TA02K-D

Table 36 defines the R-APDU of the Verify command.

Data

Table 36. R-APDU of the Verify command

SW1 SW2 Comment

Length

Value

1 byte

0x90

0x69

0x6A

0x63

1 byte

0x00

0x84

0x81

0x82

0x80

0x00

0xCX

(1)

Command completed, the password is correct

The conditions of use are not satisfied (e.g. no

NDEF file was selected or Write access equal to

FFh (write lock) or read access equal to FEh (read lock)

Command incompatible with file structure

Security status not satisfied

Incorrect parameter in command data field

A password is required

The password transmitted is incorrect and X encodes the number of further allowed retries.

1. At each session, the RF host can check a password 3 times.

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

Change Reference Data command

The Change Reference Data command replaces the read or write password related to the

NDEF files previously selected. It can be performed only if the security status satisfies the security attributes for this command.

Before sending this command, the verify command with the correct NDEF write password shall be issued. Thus, this command changes the reference data of the NDEF file.

Table 37 defines the Change Reference Data command.

Name

Table 37. Change reference data command format

CLA INS P1 and P2

Class byte

Instruction code

0x00 0x24

Password identification

0x0001: Read password transmit

0x0002: Write password transmit

Other: RFU

(1)

0x10: the password is present in the data field

NDEF new file Password

(empty field)

2 bytes

1. Return ERROR code when used.

0x10

Data

Lc bytes

42/66 DocID027817 Rev 5

ST25TA02K-D RF command sets

Length

Value

Table 38 defines the R-APDU of the Change Reference Data command.

Table 38. R-APDU of the Change Reference Data command

Data SW1 SW2 Comment

0 1 byte 1 byte

0x90

0x69

0x65

0x69

0x6A

0x00

0x81

0x82

0x80

0x82

0x86

Command completed, the access right has been changed

Command is incompatible with the file structure

Unsuccessful updating

Security status not satisfied

Incorrect parameter in file structure

File or application not found

Incorrect P1 or P2 values

Note:

5.7.3

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

Enable Verification Requirement command

The Enable Verification Requirement command activates the protection by password of the

NDEF file. When this command is successful, the read or write access to the NDEF file is protected by a 128-bit password. It can be performed only if the security status satisfies the security attributes for this command.

This command can update the right access of the NDEF file by writing into the EEPROM. In this case, the response timing will be around 5 ms.

Before sending this command, the verify command with the correct NDEF write password shall be issued. Thus, this command changes the access right of the NDEF file.

Table 39 defines the Enable Verification requirement command.

Name

Table 39. Enable Verification Requirement command format

CLA INS P1 and P2

Class byte

Instruction code

0x00 0x28 2 bytes

New security attributes

0x0001: Enable the read protection of the NDEF file

0x0002: Enable the write protection of the NDEF file

Other: RFU

(empty field)

Data

The last five bits identify the password sent in the Verify command.

DocID027817 Rev 5 43/66

RF command sets ST25TA02K-D

Table 40 defines the R-APDU of the Enable Verification Requirement command.

Length

Value

Table 40. R-APDU of the Enable Verification Requirement command

Data SW1 SW2 Comment

1 byte

0x90

0x69

0x6A

1 byte

0x00

0x81

0x82

0x80

0x82

0x86

Command completed, the password is correct

Command is incompatible with the file structure

Security status not satisfied

Incorrect parameter in command data field

File or application not found

Incorrect P1 or P2 values

Note:

5.7.4

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

Disable Verification Requirement command

The Disable Requirement command deactivates the protection by password of the NDEF file. When this command is successful, the read or write access to the NDEF file is granted without security requirements. It can be performed only if the security status satisfies the security attributes for this command.

Before sending this command, the verify command with the correct NDEF write password shall be issued. Thus, this command changes the access right of the NDEF file.

This command can update the right access of the NDEF file by writing into the EEPROM. In this case, the response timing will be around 6 ms.

Table 41 defines the Disable Verification Requirement command.

Name

Table 41. Disable Verification Requirement command format

CLA INS P1 and P2

Class byte

0x00 0x26 2 bytes

Instruction code

New security attributes

0x0001: Disable the read protection of the NDEF file

0x0002: Disable the write protection of the NDEF file

Other: RFU

(empty filed)

Data

Table 42 defines the R-APDU of the Disable Verification Requirement command.

44/66 DocID027817 Rev 5

ST25TA02K-D

Note:

RF command sets

Length

Value

Table 42. R-APDU of the Disable Verification Requirement command

Data SW1 SW2 Comment

1 byte

0x90

0x69

0x6A

0x65

1 byte

0x00

0x81

0x82

0x80

0x82

0x86

0x81

Command completed, the password is correct

Command is incompatible with the file structure

Security status not satisfied

CC file or System file selected

File or application not found

Incorrect P1 or P2 values

Update failed

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

5.8 ST proprietary command set

The RF host can be issued with the command set described in this section.

Upon receiving the ExtendedReadBinary command, the ST25TA02K-D reads the requested memory field and sends back its value in the R-APDU response.

Before sending an ExtendedReadBinary command, a file shall be selected by issuing an

NDEF select command.

The response of the ExtendedReadBinary command will be successful even if the data to be read is beyond the NDEF message. The command returns an error code if the data to be read goes beyond the end of the file.

Name

Table 43. C-APDU of the ExtendedReadBinary command

CLA INS P1 and P2

ST Class byte

0xA2

Read instruction code

Offset in the file selected

0xB0 2 bytes

(empty field)

Number of bytes to read between 0x01 ≤ Le ≤ 0xFF

Data

1 byte

Table 44 defines the R-APDU of the read binary command.

DocID027817 Rev 5 45/66

RF command sets

Note:

ST25TA02K-D

Length

Value

Table 44. R-APDU of the ExtendedReadBinary command

Data SW1 SW2 Comment

Le bytes

Content read

1 byte

0x90

0x67

0x69

0x6A

1 byte

0x00

0x82

0x86

Command completed

Wrong length

Security status not satisfied

File or application not found

Incorrect P1 or P2 values

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

The command configures the NDEF file to the ReadOnly or to the WriteOnly State.

This command can update the right access to the NDEF file by writing into the EEPROM. In this case, the response timing will be around 6 ms.

Table 45 defines the EnablePermanentState requirement command.

Name

Table 45. EnablePermanentState command format

CLA INS

Class byte

0xA2 0x28

Instruction code

New security attributes

0x0001: Lock the NDEF file in read mode

0x0002: Lock the NDEF file in write mode

Other: RFU

(empty field)

P1 and P2

2 bytes

Data

Table 46 defines the R-APDU of the EnablePermanentState command.

Length

Value

Table 46. R-APDU table of the EnablePermanentState command

Data SW1 SW2 Comment

1 byte

0x90

0x65

0x69

1 byte

0x00

0x81

0x82

Command completed

Update failed

Security status not satisfied

46/66 DocID027817 Rev 5

ST25TA02K-D RF command sets

Value

Table 46. R-APDU table of the EnablePermanentState command (continued)

Data SW1 SW2 Comment

0x6A

0x82

0x86

File or application not found

Incorrect P1 or P2 values

Note:

For further return codes and definitions, refer to Section 5.6.2: Status and error codes

This command allows to modify the file type of a selected file to Proprietary file (0x05) or

NDEF file (0x04).

This command is granted only, when application and file are selected and if the file length and access right have previously been set to 0X00h (message invalid, all access rights granted).

This command will update the file type located in the CC file by writing into the EEPROM. In this case, the response timing will be around 6 ms.

Table 47 defines the UpdateFileType command.

Name CLA

Table 47. UpdateFileType command format

INS P1 P2 Lc Le

0xD6 0x00 0x00 0x01

Data

0x04 or

0x05

Value 0xA2

Class byte

Select instruction code

P1 field

P2 field

Number of bytes of data

File type

Table 48 describes the R-APDU of the UpdateFileType command.

Length

Value

Data

Table 48. R-APDU of the UpdateFileType command

SW1 SW2 Comment

1 byte

0x90

0x69

0x6A

1 byte -

0x00 Command completed

0x82 Security status not satisfied

0x80

0x82

0x86

CC file or System file selected

File or application not found

Incorrect P1 or P2 values

DocID027817 Rev 5 47/66

RF command sets ST25TA02K-D

On receiving the SendInterrupt command, the ST25TA02K-D generates a negative pulse on the GPO pin. It starts at the end of the command and ends at the end of the RF response.

Before sending this command, the system file shall be selected by issuing the System

Select command.

Table 49 defines the SendInterrupt command.

Length

Value

CLA

Table 49. SendInterrupt command format

INS P1 and P2 Lc Data

1 byte

0xA2

1 byte

0xD6

2 bytes

0x001E

1 byte

0x00 -

Table 50 describes the R-APDU of the SendInterrupt command.

Length

Value

Data

Table 50. R-APDU of the SendInterrupt command

SW1 SW2 Comment

1 byte

0x90

0x6A

0x6E

1 byte -

0x00 The interrupt has been sent

0x80 The GPO is not configured as an interrupt mode

0x82

0x86

0x00

File or application not found

Incorrect P1 or P2 values

Class not supported

On receiving the StateControl command with reset value: data 0x00, the ST25TA02K-D drives the GPO pin low. On receiving the StateControl command with set value: data 0x01, the ST25TA02K-D releases the GPO pin that returns to HZ.

Before sending this command, the system file shall be selected by issuing the System

Select command.

Table 51 defines the State Control command.

Length

Reset value

Set value

CLA

1 byte

0xA2

Table 51. StateControl command format

INS P1 and P2 Lc

1 byte

0xD6

2 bytes

0x001F

1 byte

0x01

Data

0x00

0x01

48/66 DocID027817 Rev 5

ST25TA02K-D

Length

Value

RF command sets

Data

Table 52. R-APDU of the StateControl command

SW1 SW2 Comment

1 byte

0x90

0x6A

0x6E

1 byte -

0x00 The set or reset has been sent

0x80

0x82

The GPO is not configured in StateControl mode

File or application not found

0x86

0x00

Incorrect P1 or P2 values

Class not supported

5.9

5.9.1

Specific RF command set

This section describes the command set that can be issued only by the RF host.

Anticollision command set

Table 53 lists the commands that can be issued only by the RF host. The format of these

commands is described in the NFC Forum Digital Protocol specification.

Family command set

NFC-A technology

Table 53. Commands issued by the RF host

ALL_REQ

SENS_REQ

SDD_REQ

SEL_REQ

SLP_REQ

Command name Instruction code

0x52

(1)

0x26

(1)

0x93 or 0x95

0x50

1. Code on 7 bits.

Note:

Command

SENS_REQ or ALL-REQ

In response to a SDD_REQ Command with a SEL_PAR value equal to 20h, ST25TA02K-D in the Operating Field transmit the requested cascade level of their NFCID1 (NFCID1 CLn, with n = 1 or 2). The NFCID1 of ST25TA02K-D consists of 7 bytes. The length of the

Response containing a complete NFCID1 cascade level (i.e., NFCID1 CL1, or NFCID1 CL2) is always 5 bytes. The coding of the Response depends on the value of the SEL_CMD byte and the size of the NFCID1.

Refer to the example below for more details.

Table 54. Example of anticollision sequence

Comment Response Code Code

ATQA 42 00

Comment

UID double size bit frame anticollision

DocID027817 Rev 5 49/66

RF command sets ST25TA02K-D

Command

SDD_REQ 1

SEL_REQ 1

SDD_REQ 2

SEL_REQ 1

Table 54. Example of anticollision sequence (continued)

Code Comment Response Code Comment

93 20

93 70 CT uid1 uid2 uid3 BBC

95 20

NVB 20 Number Valid bit

(2 bytes Code and NVB)

CT uid1 uid2 uid3

BCC

CT Cascade Tag “0x88”

(UID 7bytes)

BCC Block Check

Character (XOR of previous Bytes)

NVB 70

(cmd NVB Uid lower bytes)

CT Cascade Tag “0x88”

SAK and CRC 04 DAD7 UID Not complete

NVB 20 Number Valid bit

(2 bytes Code and NVB)

uid4 uid5 uid6 uid7

BCC

(UID 7bytes) BCC Block

Check Character (XOR of previous Bytes)

95 70 uid4 uid5 uid6 uid7

BBC

NVB 70

(cmd NVB Uid upper bytes)

SAK and CRC 20 FC70 UID complete

50/66

RATS command and ATS response are used for NFC Forum Type 4A Tag Platform Device

Activation (as defined in NFC Forum Digital Protocol specification).

Table 55 details the RATS command. This command shall be sent after the anticollision

process.

Name

Byte field

Bit field

Instruction code

FSDI

DID (0 ≤ DID ≤ 14)

2 CRC bytes

INS

0xE0

Table 55. RATS command

Param

1 byte

b7-b4 b3-b0

CRC

2 bytes

The FSDI field codes the FSD, which defines the maximum size that an RF host is able to receive.

Table 56 gives the conversion from FSDI to FSD.

FSDI 0x0

FSD 16

0x1

Table 56. Conversion from FSDI to FSD

0x2 0x3 0x4 0x5 0x6 0x7 0x8

32 40 48 64 96 128 256

0x9h-

0xE

RFU

0xF

256

The DID (Dynamic ID, optionally affected to the ST25TA02K by the host to address

ST25TA02K-D in all commands) field defines the value of the addressed ST25TA02K-D.

DocID027817 Rev 5

ST25TA02K-D RF command sets

If DID is not ‘0’, the ST25TA02K-D ignores the command if it contains a DID different from the one affected to ST25TA02K-D during RATS.

Name TL T0

Table 57. ATS response

TA(1)

Byte field 0x05 0x75 0x80

Bit field -

Length of the ATS response

FSCI = 5 → FSC = 64 bytes

The maximum ascending data rate is 106 kbps

The maximum descending data rate is 106 kbps

FWI field (FWI = 6 → FWT = 19.2 ms)

SFGI field (SFGI = 0 → SFGT =302 µs)

The DID is supported

2 CRC bytes b8-b5

TB(1)

0x60 b4-b1

TC(1)

0x02

CRC

2 bytes

5.9.3

The FSCI codes the FSC, which stands for the maximum frame size that the ST25TA02K-D is able to receive. The ST25TA02K-D is able to receive up to 64 bytes of command. If the

RF host sends a command with more than 64 bytes, the ST25TA02K-D will not be able to treat the command and will not reply.

The FWI (Frame Waiting time Integer) codes the FWT, which stands for the Frame Waiting

Time. This time corresponds to the maximum duration while an RF host shall send before sending the next command.

The SFGI codes the SFGT, which stands for the Start-up Frame Guard Time. This is the minimum time that the reader shall wait after receiving the response of the ST25TA02K-D.

PPS command and response

(b)

PPS (Protocol and Parameter Selection) command and response are defined in ISO/IEC

14443-4, in the Protocol Activation of PICC Type A.

The PPS command allows to change the data rates of the ascending (RF host to

ST25TA02K-D) and descending (ST25TA02K-D to RF host) data rates. Usage of this command is optional, ST25TA02K-D only supports 106 Kb/s in both directions.

b. Not useful in case of ST25TA02K-D which only supports a Data Rate of 106 Kb/s in both directions.

DocID027817 Rev 5 51/66

RF command sets ST25TA02K-D

Name

Table 58. PPS command

INS (PPSS) PPS0

INS

PPS1

Byte field 0xDX 0x11

Bit field b7-b4 b3-b0

Instruction code

DID

PPS1 is present

RFU

Descending data rate (106 kb/s) = 0b00

Ascending data rate (106 kb/s) = 0b00

2 CRC bytes

0b0000

PPS1

1 byte b3-b2 b1-b0

CRC

2 bytes

The ascending and descending data rates shall be coded as described in

Table 59 .

Value

Data rate

Table 59. Ascending and descending data rate coding

0b00 0b01 0b10

106 kbps RFU RFU

0b11

RFU

When the ST25TA02K-D is able to change both data rates, it returns the response detailed in

Table 60 . The data rate of this response is 106 kbps; then, the ST25TA02K-D changes

the ascending and descending data rates.

Name

Byte field

Bit field

Response code

DID field

2 CRC bytes

Table 60. PPS response

RESPONSE (PPSS)

0xDX b8-b5 b4-b1

CRC

2 bytes

52/66 DocID027817 Rev 5

ST25TA02K-D

6 RF device operation

6.1

RF device operation

Anticollision and Device Activation command set for the RF interface

The ST25TA02K-D device supports the command set defined in the NFC-A Technology and the Type 4A Tag Platform chapters of the NFC Digital Protocol V1.0 specification.

6.2 Open an RF session

Once the RF host has terminated the anticollision procedure and retrieve the ATS response, it shall send the SelectApplication command. The ST25TA02K-D will open an RF session.

At this point, the RF host can send the applicative command set.

6.3

6.4 Close an RF session

The RF host can close the RF session by issuing one of these methods:

• send an S(DES) command

• turn off the RF field

Applicative command set

The applicative command set is composed of the following command sets:

• the NFC Forum Type 4 Tag command set

• the ISO/IEC 7816-4 command set

• the proprietary command set

DocID027817 Rev 5 53/66

Functional procedures ST25TA02K-D

7.1

7.2

7.3

7.4

This section describes some procedure to access the memory or manage its protection.

Selection of an NDEF message

The RF host shall use this procedure to detect the NDEF message inside an ST25TA02K-D.

The NDEF detection procedure is as follows:

Open an RF session

2. Send the SelectNDEFTagApplication command

3. Select the CC file

4. Read the CC file

5. Select the NDEF file.

Reading of an NDEF message

The RF host executes the NDEF read procedure to read the NDEF file.

Detect successfully the NDEF file using the NDEF detection procedure

2. Check that the read access without any security is granted for the NDEF file from the information provided by the CC file

3. Select the NDEF file

4. Read the NDEF file.

Reading a locked NDEF file

The RF host executes this procedure to read an NDEF file which has been locked previously.

Select the NDEF Tag Application

2. Select the NDEF file

3. Present the Read password by using the Verify command

4. Read the data in the NDEF file.

Locking an NDEF file

The RF host executes this procedure to protect an NDEF file.

Select the NDEF Tag Application

2. Check the right access provided by the CC file

3. Select the NDEF file

4. Present the NDEF file Write password by using the Verify command

5. Lock the NDEF file by sending the Enable verification command.

54/66 DocID027817 Rev 5

ST25TA02K-D

7.5

Functional procedures

Unlocking an NDEF file

The RF host executes this procedure to unlock an NDEF file which has been locked previously.

Select the NDEF Tag Application

2. Select the NDEF file

3. Present the NDEF file Write password by using the Verify command

4. Unlock the NDEF file by sending the Disable verification command.

7.6 Reaching the read-only state for an NDEF file

The RF host executes this procedure to permanently lock an NDEF file that has been previously locked with password.

Select the NDEF Tag Application

2. Select the NDEF file

3. Transmit the NDEF file Write password by using the Verify command

4. Send an EnablePermanentState command

7.7 Creating or Updating an NDEF file

Select the NDEF Tag Application

2. Select the NDEF file

3. Set the File Length to 0x00 using the UpdateBinary command

4. Write NDEF message content using the UpdateBinary command

5. Set the new File Length (must be always two written bytes)

0x0001)

The RF host executes this procedure to change the File Type of a file for which all access rights were previously granted.

Select the NDEF Tag Application

2. Select the file 0x0001

3. Set the File Length to 0x00 using the UpdateBinary command

4. Send an UpdateFileType command with the New file Type as data

DocID027817 Rev 5 55/66

UID: Unique identifier ST25TA02K-D

The ST25TA02K-D is uniquely identified by a 7 bytes unique identifier (UID). The UID is a read-only code and comprises:

• The IC manufacturer code on 1 byte (0x02 for STMicroelectronics).

• The Product code on 1 byte.

• A device number on 5 bytes.

Table 61 describes the UID format.

Table 61. UID format

0x02 0xF2 5 bytes -

IC manufacturer code

ST25TA02K-D product code

Device number

56/66 DocID027817 Rev 5

ST25TA02K-D Maximum ratings

Stressing the device above the ratings listed in

Table 62

may cause permanent damage to the device. These are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not implied.

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

Symbol

Table 62. Absolute maximum ratings

Parameter Min.

Max.

Unit

STG h

STG t

STG

Ambient operating temperature

Storage conditions

Sawn wafer on UV tape

-40

(1)

°C

°C months

Kept in its original packing form

STG

LEAD

DCG

(4)

MAX_1

(4)

MAX_2

(4)

ESD

Storage temperature

Storage temperature Sawn bumped

Storage time wafer

(kept in its antistatic bag)

Lead temperature during soldering

UFDFPN8 or

UFDFPN5

GPO Power Supply

UFDFPN8 or

UFDFPN5

RF supply current AC0 - AC1

RF input voltage amplitude between

AC0 and AC1, V

SS left floating

pad

VAC0-VAC1

(Peak to Peak)

AC voltage between

AC0 and V

SS and V

, or AC1

Electrostatic discharge voltage (human body model) (5)

VAC0-V

VAC1-V

AC0-AC1

Electrostatic discharge voltage (human body model)

(5)

Other pads

–65

-0.5

See note

(3)

150

9 (2)

5.5

4.5

2000

3500

V mA

1. Counted from ST shipment date.

2. Counted from ST production (taping) date.

3. Compliant with JEDEC Std J-STD-020D (for small body, Sn-Pb or Pb assembly), the ST ECOPACK directive 2011/65/EU, July 2011).

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

4. Based on characterization, not tested in production. Maximum absorbed power = 100 mW @ 7.5 A/m

5. AEC-Q100-002 (compliant with JEDEC Std JESD22-A114A, C1 = 100 pF, R1 = 1500 Ω , R2 = 500 Ω )

°C

°C months

°C

DocID027817 Rev 5 57/66

GPO characteristics ST25TA02K-D

This section summarizes the operating and measurement conditions of the GPO feature.

The DC and AC characteristics are derived from tests performed under the measurement conditions summarized in the following tables. GPO I/O is CMOS compliant.

Symbol

DCG

Table 63. GPO operating conditions

Parameter Min.

GPO Power Supply 1.65

Max.

5.5

Unit

Symbol

(1)

Parameter

Table 64. DC characteristics

Test condition

Output Low voltage (GPO)

= 1 mA,

Pull-up supply = 1.65 to 5.5 V

1. Characterized only

Min.

Max.

Unit

0.4 V V

58/66 DocID027817 Rev 5

ST25TA02K-D GPO parameters

This section lists the timing of the GPO according to its configuration.

GPO field I/F

Table 65. GPO timings measurement (1)

Condition Command Symbol Typ.

Unit

Session Open

WIP

0x10 or

0x90

0x20 or

0xA0

GPO when session active

GPO return

GPO when programming

NDEF select

Deselect

Update Binary

CmdEOFtoGP

CmdEOFtoGPlow

Writing time duration

(No time extension)

170

370

(2)

µs

µs ms

Message In

Progress

Interrupt

State Control

0x30 or

0xB0

0x40 or

0xC0

0x50 or

0xD0

GPO when modifying NDEF

GPO after receiving an

Interrupt command

GPO when reset

GPO return when set

UpdateBinary (Msg

Length #0)

UpdateBinary

SendInterrupt

Reset GPO

Set GPO

CmdEOFtoGP

Writing time duration

(No time extension)

CmdEOFtoGP

Pulse duration

CmdEOFtoGP

(2)

540

µs ms

µs

RF Busy

0x60 or

0xE0

GPO after receiving an RF command

GPO return after deselection or RF command in another protocol

Anticollision command or start of

RF disturb

(command using another RF protocol)

Deselect or end of

RF disturb

(command using another RF protocol)

CmdSOFtoGP

CmdEOFtoGP

460

µs

Field detect

0x70 or

0xF0

GPO when RF field is present

FDETON t

FDETOFF

140

µs

1. Characterized only.

2. Writing time is function of the message length and is automatically manage by ST25TA02K-D. NDEF message is mapped on memory blocks of 16 bytes. Each basic block has a typical update time duration of 6 ms including the internal verify.

DocID027817 Rev 5 59/66

RF electrical parameters

12 RF electrical parameters

ST25TA02K-D

This section summarizes the operating and measurement conditions, and the DC and AC characteristics of the device in RF mode.

The parameters in the DC and AC characteristics tables that follow are derived from tests performed under the measurement conditions summarized in the relevant tables. Designers should check that the operating conditions in their circuit match the measurement conditions when relying on the quoted parameters.

Symbol

Table 66. Default operating conditions

Parameter Min.

Ambient operating temperature –40

Max.

Unit

°C

Symbol Parameter

Table 67. RF characteristics

(1)

Condition Min Typ Max Unit f

H_ISO

H_Extended

H min

CARRIER t

1 t

2 t

3 t

External RF signal frequency

Operating field according to ISO

Operating field in extended temperature range

Field detect, Set-up field (1)

100% carrier modulation index

Pause A length

Pause A low time

Pause A rise time

= 0 °C to 50 °C

= -40 °C to 85 °C

MI=(A-B)/(A+B)

13.553

1500

100

28 / f

7 / f

1.5 x t

13.56

115

MIN CD

Pause A rise time section

Minimum time from carrier generation to first data

From H-field min -

W t

TUN

(3) t

RF_OFF

RF write time (including internal

Verify) for one page

Internal tuning capacitor

RF OFF time

(4) f

= 13.56 MHz

Chip reset

4.468

(2)

1. All timing characterizations were performed on a reference antenna with the following characteristics:

External size: 75 mm x 48 mm

Number of turns: 4

Width of conductor: 0.5 mm

Space between two conductors: 0.5 mm

Value of the tuning capacitor: 50 pF (ST25TA02K-D)

Value of the coil: 2.5 µH

Tuning frequency: 14.2 MHz.

2. Time between command EOF and Response SOF when Updating NDEF Message Length

3. See

Capacitor value

4. Characterized only, at room temperature only, measured at VAC0-VAC1 = 5 V peak to peak at 13.56 MHz.

13.567

7500

100

40.5 / f t

16 / f

6 / f

0.1

MHz mA/m mA/m mA/m

µs

µs ms ms pF ms

60/66 DocID027817 Rev 5

ST25TA02K-D Package information

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.

13.1 UFDFPN8 package information

Figure 14. UFDFPN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package outline

' $ %

3LQ

,'PDUNLQJ

(

FFF

HHH &

6HDWLQJSODQH

6LGHYLHZ

[ DDD &

7RSYLHZ

H E

'DWXP$

/ /

3LQ

,'PDUNLQJ

(

'HWDLO³$´

(YHQWHUPLQDO

7HUPLQDOWLS

1'[ H

%RWWRPYLHZ

6HH'HWDLO³$´

=:DB0(B9

1. Max. package warpage is 0.05 mm.

2. Exposed copper is not systematic and can appear partially or totally according to the cross section.

3. Drawing is not to scale.

4. The central pad (the area E2 by D2 in the above illustration) must be either connected to VSS or left floating (not connected) in the end application.

DocID027817 Rev 5 61/66

Package information ST25TA02K-D

Table 68. UFDFPN8 - 8-lead, 2 × 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package mechanical data millimeters inches

(1)

Symbol

Min Typ Max Min Typ Max e

L3 aaa bbb ccc ddd eee

(3)

A1 b

(2)

0.450

0.000

0.200

1.900

1.500

2.900

0.100

0.800

0.400

0.300

0.550

0.020

0.250

2.000

1.600

3.000

0.200

0.500

0.450

0.600

0.050

0.300

2.100

1.700

3.100

0.300

0.500

0.150

0.100

0.050

0.080

0.0177

0.0000

0.0079

0.0748

0.0591

0.1142

0.0039

0.0315

0.0157

0.0118

0.0217

0.0008

0.0098

0.0787

0.0630

0.1181

0.0079

0.0197

0.0177

0.0236

0.0020

0.0118

0.0827

0.0669

0.1220

0.0118

0.0197

0.0059

0.0039

0.0020

0.0031

1. Values in inches are converted from mm and rounded to 4 decimal digits.

2. Dimension b applies to plated terminal and is measured between 0.15 and 0.30 mm from the terminal tip.

3. Applied for exposed die paddle and terminals. Exclude embedding part of exposed die paddle from measuring.

62/66 DocID027817 Rev 5

ST25TA02K-D Package information

13.2 UFDFPN5 package information

Figure 15. UFDFPN5 - 5-lead, 1.7 × 1.4 mm, 0.55 mm thickness package outline

N /

3LQ 3LQ

(

7RSYLHZ

PDUNLQJVLGH

6LGHYLHZ

%RWWRPYLHZ

SDGVVLGH

$8.B0(B9

1. Max. package warpage is 0.05 mm.

2. Exposed copper is not systematic and can appear partially or totally according to the cross section.

3. Drawing is not to scale.

Table 69. UFDFPN5 - 5-lead, 1.7 × 1.4 mm, 0.55 mm thickness package mechanical data millimeters inches

(1)

Symbol

Min Typ Max Min Typ Max

A1 b

(2) e

L1 k

0.500

0.000

0.175

1.600

1.400

1.300

0.175

0.500

0.550

0.200

1.700

1.500

1.400

0.200

0.400

0.550

0.100

0.400

0.600

0.050

0.225

1.800

1.600

1.500

0.225

0.600

0.0197

0.0000

0.0069

0.0630

0.0551

0.0512

0.0069

0.0197

0.0217

0.0079

0.0669

0.0591

0.0551

0.0079

0.0157

0.0217

0.0039

0.0157

1. Values in inches are converted from mm and rounded to 4 decimal digits.

2. Dimension b applies to plated terminal and is measured between 0.15 and 0.30mm from the terminal tip.

0.0236

0.0020

0.0089

0.0709

0.0630

0.0591

0.0089

0.0236

DocID027817 Rev 5 63/66

Ordering information ST25TA02K-D

Table 70. Ordering information scheme for packaged devices

ST25 T A 02K D - C 6 G/H/C 5

Device type

ST25 = RF memory

Product Type

T = Tags + RFID

Protocol

A = ISO14443-A

Memory density

02K (binary)

Customization type

None = Standard product

K = Customized product

Interface

D = OD GPO

Features

C = Counter as option

Operating temperature

6 = -40 o C to +85 o C

Package / Packing

G = Sawn and bumped wafer, 120 ± 15 µm

H = DFN5

C = DFN8

Capacitor value

5 = 50 pF

Note: Parts marked as “ES”, “E” or accompanied by an Engineering Sample notification letter, are not yet qualified and therefore not approved for use in production. ST is not responsible for any consequences resulting from such use. In no event will ST be liable for the customer using any of these engineering samples in production. ST’s Quality department must be contacted prior to any decision to use these engineering samples to run a qualification activity.

64/66 DocID027817 Rev 5

ST25TA02K-D Revision history

Date

03-Aug-2015

12-Feb-2016

02-Sep-2016

21-Feb-2017

05-Oct-2017

Revision

Table 71. Document revision history

Changes

Initial release.

Updated Section 2.2: Ground (VSS) ,

Section 2.3.3: MIP NDEF Message writing in Progress configuration (GPO field = 0x30 or 0xB0)

Section 2.3.4: INT Interrupt configuration (GPO field = 0x40 or 0xC0) ,

Section 2.3.5: State Control configuration (GPO field = 0x50 or 0xD0)

Section 2.3.6: RF busy configuration (GPO field = 0x60 or 0xE0) ,

Section 5.9.2: RATS command and ATS response ,

Section 7.5:

Unlocking an NDEF file , Section 7.6: Reaching the read-only state for an

NDEF file

and

Section 7.8: Changing a File Type Procedure (applicable only on file 0x0001)

Added Section 5.8.3: UpdateFileType command

Section 5.8.4:

SendInterrupt command

Section 5.8.5: StateControl command and

Section 7.7: Creating or Updating an NDEF file .

Updated Figure 5: GPO configured as Session Open (GPO field = 0x10 or 0x90) and its footnote 2 .

Updated footnote

Figure 9: GPO configured as State Control (GPO field = 0x50 or 0xD0)

Updated Figure 10: GPO configured as RF busy (GPO field = 0x60 or

0xE0) and its footnote 2 .

Updated Figure 11: Field detect (GPO field = 0x70 or 0xF0)

and

Figure 12: Changing the read access right to an NDEF file .

Added footnote

Table 6: Field list .

Updated Table 62: Absolute maximum ratings and

Table 70: Ordering information scheme for packaged devices .

Updated Features

and image on cover page.

Updated footnotes of figures

and

4 .

Updated Section 5.9.2: RATS command and ATS response ,

Section 5.9.3: PPS command and response and

Section 10: GPO characteristics .

Updated Table 11: RF command sets

Table 62: Absolute maximum ratings and

Table 70: Ordering information scheme for packaged devices

Updated title of

Section 14: Ordering information and of

Table 56:

Conversion from FSDI to FSD

Updated Table 67: RF characteristics and its footnote 4 .

Updated Section 13.1: UFDFPN8 package information .

Updated Features

Updated Table 6: Field list ,

Table 11: RF command sets and

Table 17: R-

Block detailed format

Updated footnote

Figure 12 and

Note: in Section 14 .

DocID027817 Rev 5 65/66

ST25TA02K-D

IMPORTANT NOTICE – PLEASE READ CAREFULLY

STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, enhancements, modifications, and improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on

ST products before placing orders. ST products are sold pursuant to ST’s terms and conditions of sale in place at the time of order acknowledgement.

Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or the design of Purchasers’ products.

No license, express or implied, to any intellectual property right is granted by ST herein.

Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.

ST and the ST logo are trademarks of ST. All other product or service names are the property of their respective owners.

Information in this document supersedes and replaces information previously supplied in any prior versions of this document.

66/66 DocID027817 Rev 5

Download

Just a friendly reminder. You can view the document right here. But most importantly, our AI has already read it. It can explain complex things in simple terms, answer your questions in any language, and help you quickly navigate even the longest or most compilcated documents.

No, still want to look it up myself

Hello! I am an AI chatbot specifically trained to assist you with the STMicroelectronics ST25TA02K-D Data Sheet. I have thoroughly reviewed the document and can help you locate the exact information you need or explain the content in clear and simple terms. Whether you’re looking for guidance on specific features, troubleshooting steps, or general usage, feel free to ask your questions. The more details you provide about your concerns or needs, the more accurately and effectively I can assist you!