STMicroelectronics-ST25TB512-AT6F6

ST25TB512-AT  

Datasheet  

13.56 MHz short-range contactless memory chip with 512-bit EEPROM and  

anticollision functions  

Features  

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

ISO 14443-2 Type B air interface compliant  

ISO 14443-3 Type B frame format compliant  

13.56 MHz carrier frequency  

847 kHz subcarrier frequency  

106 Kbit/second data transfer  

-Unsawn wafer  

-Bumped and sawn wafer  

8 bit Chip_ID based anticollision system  

2 count-down binary counters with automated anti-tearing protection  

64-bit Unique Identifier  

512-bit EEPROM with write protect feature  

Read_block and Write_block (32 bits)  

Internal tuning capacitor: 68 pF  

1 million erase/write cycles  

40-year data retention  

Self-timed programming cycle  

5 ms typical programming time  

Application  

•

Transport  

Product status link  

DS11456

–

Rev 7

–

September 2018  

For further information contact your local STMicroelectronics sales office.  

ST25TB512-AT  

Description  

1

Description  

The

is a contactless memory, powered by an externally transmitted radio wave. It contains a 512-  

bit user EEPROM. The memory is organized as 16 blocks of 32 bits. The

is accessed via the  

13.56 MHz carrier. Incoming data are demodulated and decoded from the received amplitude shift keying (ASK)  

modulation signal and outgoing data are generated by load variation using bit phase shift keying (BPSK) coding of  

a 847 kHz sub-carrier. The received ASK wave is 10% modulated. The data transfer rate between the  

and the reader is 106 kbit/s in both reception and emission modes.  

The

follows the ISO 14443 – 2 Type B recommendation for the radio-frequency power and signal  

interface.  

Figure 1.

Logic diagram  

ST25TB512-AT  

AC1  

Power  

Supply  

Regulator  

ASK  

512-bit  

User  

Demodulator  

EEPROM  

BPSK  

Load  

Modulator  

AC0  

The

is specifically designed for short range applications that need re-usable products. The  

includes an anticollision mechanism that allows it to detect and select tags present at the same  

time within range of the reader. The anticollision is based on a probabilistic scanning method using slot markers.  

Table 1.

Signal names  

Signal names  

AC1  

Description  

Antenna coil  

Antenna coil  

AC0  

The

contact-less EEPROM can be randomly read and written in block mode (each block  

containing 32 bits). The instruction set includes the following nine commands:  

•

•

•

•

•

•

•

•

•

Read_block  

Write_block  

Initiate  

Pcall16  

Slot_marker  

Select  

Completion  

Reset_to_inventory  

Get_UID  

DS11456

–

Rev 7  

page 2/45  

ST25TB512-AT  

Description  

The

memory is organized in three areas, as described in

. The first area is an EEPROM  

area where all blocks behave as User blocks. The second area provides two 32-bit binary counters which can  

only be decremented. The last area is the EEPROM memory. It is accessible by block of 32 bits and includes an  

auto-erase cycle during each Write_block command.  

Die floor plan and physical options related to the die assembly are described in

.  

Figure 2.

Die floor plan and assembly options  

For the option 1 of the die assembly, the CTUN (referenced in

) can increase from 0.5pF to 1p

F

.

T

he  

option 2 of the die assembly is showing a tripod which can be used for physical stability, having no impact on  

CTUN parameter.  

DS11456

–

Rev 7  

page 3/45  

ST25TB512-AT  

Signal description  

2

Signal description  

2.1  

AC1, AC0  

The pads for the Antenna Coil. AC1 and AC0 must be directly bonded to the antenna.  

DS11456

–

Rev 7  

page 4/45  

ST25TB512-AT  

Data transfer  

3

Data transfer  

3.1  

Input data transfer from reader to ST25TB512-AT (request frame)  

The reader must generate a 13.56 MHz sinusoidal carrier frequency at its antenna, with enough energy to  

“remote-power” the memory. The energy received at the

’s antenna is transformed into a supply  

voltage by a regulator, and into data bits by the ASK demodulator. For the

to decode correctly the  

information it receives, the reader must 10% amplitude-modulate the 13.56 MHz wave before sending it to the  

. This is represented in

. The data transfer rate is 106 Kbits/s.  

In some figures of this datasheet the ST25TBxxx refers to

.  

Figure 3.

ST25TB512-AT 10% ASK modulation of the received wave  

DATA BIT TO TRASMIT  

TO THE ST25TBxxx  

10% ASK MODULATION  

OF THE 13.56MHz

 

WAVE,  

GENERATED BY THE READER  

Transfer time for one data bit is 1/106 kHz  

3.1.1  

Character transmission format for request frame  

The

transmits and receives data bytes as 10-bit characters, with the least significant bit (b

0

)  

transmitted first, as shown in

. Each bit duration, an ETU (elementary time unit), is equal to 9.44 µs (1/106  

kHz).  

These characters, framed by a start of frame (SOF) and an end of frame (EOF), are put together to form a  

command frame as shown in

. A frame includes an SO

F

,

c

ommands, addresses, data, a CRC and an  

EOF as defined in the ISO 14443-3 Type B Standard. If an error is detected during data transfer, the

does not execute the command, but it does not generate an error frame.  

Figure 4.

request frame character format  

b0  

b1  

b2  

b3  

b4  

b5  

b6  

b7  

b8  

b9  

Stop  

“1”  

Start  

“0”  

LSB  

MSB  

Information Byte  

1 ETU  

Table 2.

Bit description  

Bit  

Description  

Value  

b

b =

 

0  

0

Start bit used to synchronize the transmission  

Information byte (command, address or data)  

Stop bit used to indicate the end of a character  

0

b tob  

The information byte is sent with the least significant bit first  

1

8

b

b =

 

1  

9

9

DS11456

–

Rev 7  

page 5/45  

ST25TB512-AT  

Input data transfer from reader to ST25TB512-AT (request frame)  

3.1.2  

Request start of frame  

The SOF described in

is composed of:  

•

•

•

•

one falling edge,  

followed by 10 ETUs at logic-0,  

followed by a single rising edge,  

followed by at least 2 ETUs (and at most 3) at logic-1.  

Figure 5.

Request start of frame  

b0  

0

b1  

0

b2  

0

b3  

0

b4  

0

b5  

0

b6  

0

b7  

0

b8  

0

b9  

0

b10  

1

b11  

1

ETU  

3.1.3  

Request end of frame  

The EOF shown in

is composed of:  

•

•

•

one falling edge,  

followed by 10 ETUs at logic-0,  

followed by a single rising edge.  

Figure 6.

Request end of frame  

b0  

0

b1  

0

b2  

0

b3  

0

b4  

0

b5  

0

b6  

0

b7  

0

b8  

b9  

ETU  

0

0

DS11456

–

Rev 7  

page 6/45  

ST25TB512-AT  

Output data transfer from ST25TB512-AT to reader (answer frame)  

3.2  

Output data transfer from to reader ST25TB512-AT (answer frame)  

The data bits issued by the

use back-scattering. Back-scattering is obtained by modifying the  

current consumption at the antenna (load modulation). The load modulation causes a variation at  

the reader antenna by inductive coupling. With appropriate detector circuitry, the reader is able to pick up  

information from the

.

T

o

i

mprove load-modulation detection, data is transmitted using a BPSK  

encoded, 847 kHz subcarrier frequency ƒ

s

as shown in

, and as specified in the ISO 14443-2 Type B  

standard.  

Figure 7.

Wave transmitted using BPSK subcarrier modulation  

Data Bit to be Transmitted  

to the Reader  

Or  

847kHz BPSK Modulation  

Generated by the ST25TBxxx  

BPSK Modulation at 847kHz  

During a One-bit Data Transfer Time (1/106kHz)  

3.2.1  

3.2.2  

Character transmission format for answer frame  

The character format is the same as for input data transfer (

). The transmitted frames are made up of an  

SO

F

,

d

ata, a CRC and an EOF (

). As with an input data transfer, if an error occurs, the reader does not  

issue an error code to the

, but it should be able to detect it and manage the situation. The data  

transfer rate is 106 Kbits/second.  

Answer start of frame  

The SOF described in

is composed of:  

•

•

followed by 10 ETUs at logic-0  

followed by 2 ETUs at logic-1  

Figure 8.

Answer start of frame  

b0  

0

b1  

0

b2  

0

b3  

0

b4  

0

b5  

0

b6  

0

b7  

0

b8  

0

b9  

0

b10  

1

b11  

1

ETU  

DS11456

–

Rev 7  

page 7/45  

ST25TB512-AT  

Transmission frame  

3.2.3  

Answer end of frame  

The EOF shown in

is composed of:  

•

•

followed by 10 ETUs at logic-0,  

followed by 2 ETUs at logic-1.  

Figure 9.

Answer end of frame  

b0  

0

b1  

0

b2  

0

b3  

0

b4  

0

b5  

0

b6  

0

b7  

0

b8  

0

b9  

0

b10  

1

b11  

1

ETU  

3.3  

Trasmission frame  

Between the request data transfer and the answer data transfer, all ASK and BPSK modulations are suspended  

for a minimum time of t

0

= 128/ƒ

S

. This delay allows the reader to switch from Transmission to Reception mode. It  

is repeated after each frame. After t

0

, the 13.56 MHz carrier frequency is modulated by the

at  

847 kHz for a period of t

1

= 128/ƒ

S

to allow the reader to synchronize. After t

1

, the first phase transition generated  

by the

forms the start bit (‘0’) of the answer SO

F

.

A

fter the falling edge of the answer EO

F

,

t

he  

reader waits a minimum time, t

2

, before sending a new request frame to the

.  

Figure 10.

Example of a complete transmission frame  

Sent by the  

Reader  

SOF  

Cmd  

Data  

CRC CRC  

EOF  

SOF  

12 bits  

10 bits

 

10 bits

 

10 bits

 

10 bits

 

10 bits  

t

DR  

f

S

= 847.5 kHz  

at 106 kb/s  

Sync  

t

1  

SOF  

Data CRC

 

CRC EOF  

Sent by the  

ST25TBxxx  

12 bits

 

10 bits

 

10 bits

 

10 bits

 

12 bits  

t

0  

t

2  

Input data transfer using ASK  

Output data transfer using BPSK  

DS11456

–

Rev 7  

page 8/45  

ST25TB512-AT  

CRC  

3.4  

CRC  

The 16-bit CRC used by the

is generated in compliance with the ISO14443 Type B  

recommendation. For further information, please see Appendix A

. The initial  

register contents are all 1s: FFFFh.  

The two-byte CRC is present in every request and in every answer frame, before the EO

F

.

T

he CRC is calculated  

on all the bytes between SOF (not included) and the CRC field.  

Upon reception of a request from a reader, the

verifies that the CRC value is valid. If it is invalid,  

the

discards the frame and does not answer the reader.  

Upon reception of an answer from the

, the reader should verify the validity of the CRC. In case of  

error, the actions to be taken are the reader designer’s responsibility.  

The CRC is transmitted with the least significant byte first and each byte is transmitted with the least significant bit  

first.  

Figure 11.

CRC transmission rules  

LSByte  

MSByte  

LSbit  

MSbit LSbit  

MSbit  

CRC 16 (8 bits)  

CRC 16 (8 bits)  

DS11456

–

Rev 7  

page 9/45  

ST25TB512-AT  

Memory mapping  

4

Memory mapping  

The

is organized as 16 blocks of 32 bits as shown in

. All blocks are accessible by the  

Read_block command. Depending on the write access, they can be updated by the Write_block command. A  

Write_block updates all the 32 bits of the block.  

Table 3.

ST25TB512-AT memory mapping  

MSB  

b31  

32-bit block  

b16 b15  

LSB  

b0  

Block Address  

Description  

b24 b23  

b8 b7  

0

1

User area  

User area  

2

User area  

Lockable EEPROM  

Count down counter  

3

User area  

4

User area  

5

32 bits binary counter  

32 bits binary counter  

User area  

6

7

8

User area  

9

User area  

10  

11  

12  

13  

14  

15  

255  

UID0  

UID1  

User area  

User area  

Lockable EEPROM  

User area  

User area  

User area  

User area  

OTP_Lock_Reg  

1

ST Reserved  

System OTP bits  

ROM  

64 bits UID area  

DS11456

–

Rev 7  

page 10/45  

ST25TB512-AT  

EEPROM area  

4.1  

EEPROM area  

4.1.1  

Block 0-4  

Blocks 0 to 4 define a User area. They behave as standard EEPROM blocks, like blocks 7 to 15 as described in  

. Each block can be individually write-protected using the OTP_Lock_Reg bits of the system area. Once a  

block has been protected, it can no longer be unprotected.  

Table 4.

Lockable EEPROM area (addresses 0 to 4)  

MSB  

b31  

32-bit block  

b16 b15  

LSB  

b0  

Block Address  

Description  

b24 b23  

b8 b7  

0

1

2

3

4

User area  

User area  

User area  

User area  

User area  

Lockable EEPROM  

4.1.2  

block 7-15  

The 9 blocks between addresses 7 and 15 are EEPROM blocks of 32 bits each (36 bytes in total). (See not found  

for a map of the area.) These blocks can be accessed using the Read_block and Write_block commands. The  

Write_block command for the EEPROM area always includes an auto-erase cycle prior to the write cycle.  

Blocks 7 to 15 can be write-protected. Write access is controlled by the 9 bits of the OTP_Lock_Reg located at  

block address 255 (see “OTP_Lock_Reg” for details). Once protected, these blocks (7 to 15) cannot be  

unprotected.  

Table 5.

EEPROM area (addresses 7 to 15)  

MSB  

b31  

32-bit block  

b16 b15  

LSB  

b0  

Block Address  

Description  

b24 b23  

b8 b7  

7

User area  

User area  

User area  

User area  

User area  

User area  

User area  

User area  

User area  

8

9

10  

11  

12  

13  

14  

15  

Lockable EEPROM  

DS11456

–

Rev 7  

page 11/45  

ST25TB512-AT  

32-bit binary counters  

4.2  

32-bit binary counters  

The two 32-bit binary counters are located at block addresses 5 and 6. The

uses dedicated logic  

that only allows the update of a counter if the new value is lower than the previous one. This feature allows the  

application to count down by steps of 1 or more. The initial value in Counter 5 is FFFF FFFEh and is FFFF FFFFh  

in Counter 6. When the reached value is 0000 0000h, the counter is empty and cannot be reloaded. For each  

counter 5 and 6, the update is done by issuing the Write_block command. The Write_block command writes the  

new 32-bit value to the counter block address.

shows examples of how the counters operate.  

The counter programming cycles are protected by automated antitearing logic. This function allows the counter  

value to be protected in case of power down within the programming cycle. In case of power down, the counter  

value is not updated and the previous value continues to be stored.  

Blocks 5 and 6 can be write-protected using the OTP_Lock_Reg bits (block 255). Once a block has been  

protected, its contents cannot be modified. A protected counter block behaves like a ROM block.  

Table 6.

Binary counter (addresses 5 to 6)  

MSB  

b31  

32-bit block  

b16 b15  

LSB  

b0  

Block Address  

Description  

b24 b23  

b8 b7  

5

6

32-bit Boolean area  

32-bit Boolean area  

Count down  

counter  

Figure 12.

Countdown example (binary format)  

b31  

b0  

1

Initial data  

1

1

1

1

1

1

…  

…  

…  

…  

…  

…  

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

1

0

1

1

1

1

0

0

0

0

1-unit decrement  

1-unit decrement  

1-unit decrement  

8-unit decrement  

Increment not allowed  

1

1

1

1

0

0

1

0

0

0

DS11456

–

Rev 7  

page 12/45  

ST25TB512-AT  

System area  

4.3  

System area  

This area is used to modify the settings of the

. It contains 2 registers: OTP_Lock_Reg and ST  

Reserved. See

for a map of this area.  

A Write_block command in this area will not erase the previous contents. Selected bits can thus be set from 1 to  

0. All bits previously at 0 remain unchanged. Once all the 32 bits of a block are at 0, the block is empty and  

cannot be updated any more.  

Table 7.

System area  

MSB  

b31  

32-bit block  

b16 b15  

LSB  

b0  

Block Address  

Description  

b24  

b23  

b14  

b7  

ST reserved  

255  

OTP_Lock_Reg  

1

OTP  

4.3.1  

OTP_Lock_Reg  

The 16 bits, b

31

to b

16

, of the System area (block address 255) are used as OTP_Lock_Reg bits in the  

. They control the write access to the 16 EEPROM blocks with addresses 0 to 15 as follows:  

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

When b

16

is at 0, blocks 0 is write-protected  

When b

17

is at 0, block 1 is write-protected  

When b

18

is at 0, block 2 is write-protected  

When b

19

is at 0, block 3 is write-protected  

When b

20

is at 0, block 4 is write-protected  

When b

21

is at 0, block 5 is write-protected  

When b

22

is at 0, block 6 is write-protected  

When b

23

is at 0, block 7 is write-protected.  

When b

24

is at 0, blocks 8 is write-protected  

When b

25

is at 0, block 9 is write-protected  

When b

26

is at 0, block 10 is write-protected  

When b

27

is at 0, block 11 is write-protected  

When b

29

is at 0, block 12 is write-protected  

When b

29

is at 0, block 13 is write-protected  

When b

30

is at 0, block 14 is write-protected  

When b

31

is at 0, block 15 is write-protected.  

The OTP_Lock_Reg bits cannot be erased. Once write-protected, EEPROM blocks behave like ROM blocks and  

cannot be unprotected.  

After any modification of the OTP_Lock_Reg bits, it is necessary to send a Select command with a valid Chip_ID  

to the

in order to load the block write protection into the logic.  

DS11456

–

Rev 7  

page 13/45  

ST25TB512-AT  

ST25TB512-AT operation  

5

ST25TB512-AT operation  

All commands, data and CRC are transmitted to the

as 10-bit characters using ASK modulation.  

The start bit of the 10 bits, b

0

, is sent first. The command frame received by the

at the antenna is  

demodulated by the 10% ASK demodulator, and decoded by the internal logic. Prior to any operation, the  

must have been selected by a Select command. Each frame transmitted to the

must start with a start of frame, followed by one or more data characters, two CRC bytes and the final end of  

frame. When an invalid frame is decoded by the

(wrong command or CRC error), the memory  

does not return any error code.  

When a valid frame is received, the

may have to return data to the reader. In this case, data is  

returned using BPSK encoding, in the form of 10-bit characters framed by an SOF and an EO

F

.

T

he transfer is  

ended by the

sending the 2 CRC bytes and the EO

F

.  

DS11456

–

Rev 7  

page 14/45  

ST25TB512-AT  

ST25TB512-AT states  

6

ST25TB512-AT states  

The

can be switched into different states. Depending on the current state of the

,  

its logic will only answer to specific commands. These states are mainly used during the anticollision sequence, to  

identify and to access the

in a very short time. The

provides 6 different states, as  

described in the following paragraphs and in

.  

6.1  

6.2  

Power-off state  

The

is in Power-off state when the electromagnetic field around the tag is not strong enough. In  

this state, the

does not respond to any command.  

Ready state  

When the electromagnetic field is strong enough, the

enters the Ready state. After Power-up, the  

Chip_ID is initialized with a random value. The whole logic is reset and remains in this state until an Initiate()  

command is issued. Any other command will be ignored by the

.  

6.3  

6.4  

Inventory state  

The

switches from the Ready to the Inventory state after an Initiate() command has been issued.  

In Inventory state, the

will respond to any anticollision commands: Initiate(), Pcall16() and  

Slot_marker(), and then remain in the Inventory state. It will switch to the Selected state after a Select(Chip_ID)  

command is issued, if the Chip_ID in the command matches its own. If not, it will remain in Inventory state.  

Selected state  

In Selected state, the

is active and responds to all Read_block(), Write_block() and Get_UID()  

commands. When an

has entered the Selected state, it no longer responds to anticollision  

commands. So that the reader can access another tag, the

can be switched to the Deselected  

state by sending a Select(Chip_ID) with a Chip_ID that does not match its own, or it can be placed in Deactivated  

state by issuing a Completion() command. Only one

can be in Selected state at a time.  

6.5  

Deselected state  

Once the

is in Deselected state, only a Select(Chip_ID) command with a Chip_ID matching its  

own can switch it back to Selected state. All other commands are ignored.  

DS11456

–

Rev 7  

page 15/45  

ST25TB512-AT  

Deactivated state  

6.6  

Deactivated state  

When in this state, the

can only be turned off. All commands are ignored.  

Figure 13.

State transition diagram  

Power-off  

Out of  

field  

On field  

Ready  

Chip_ID =

 

RND  

8bits  

Initiate()  

Out of  

field  

Initiate() or Pcall16()  

or Slot_marker(SN) or  

Select(wrong Chip_ID)  

Inventory  

Out of  

field  

Select(Chip_ID)  

Reset_to_inventory()  

Selected  

Out of  

field  

Out of  

field  

Select(Chip_ID)  

Deselected  

Completion()  

Deactivated  

Select(

≠

Chip_ID)  

Select(Chip_ID)  

Read_block()  

Write_block()  

Get_UID()  

DS11456

–

Rev 7  

page 16/45  

ST25TB512-AT  

Anticollision  

7

Anticollision  

The

provides an anticollision mechanism that searches for the Chip_ID of each device that is  

present in the reader field range. When known, the Chip_ID is used to select an

individually, and  

access its memory. The anticollision sequence is managed by the reader through a set of commands described in  

:  

•

•

•

Initiate()  

Pcall16()  

Slot_marker().  

The reader is the master of the communication with one or more

device(s). It initiates the tag  

communication activity by issuing an Initiate(), Pcall16() or Slot_marker() command to prompt the

to answer. During the anticollision sequence, it might happen that two or more

devices respond  

simultaneously, so causing a collision. The command set allows the reader to handle the sequence, to separate  

transmissions into different time slots. Once the anticollision sequence has completed,  

communication is fully under the control of the reader, allowing only one

to  

transmit at a time.  

The Anticollision scheme is based on the definition of time slots during which the

devices are  

invited to answer with minimum identification data: the Chip_ID. The number of slots is fixed at 16 for the  

Pcall16() command. For the Initiate() command, there is no slot and the

answers after the  

command is issued.

devices are allowed to answer only once during the anticollision sequence.  

Consequently, even if there are several

devices present in the reader field, there will probably be  

a slot in which only one

answers, allowing the reader to capture its Chip_ID. Using the Chip_ID,  

the reader can then establish a communication channel with the identified

. The purpose of the  

anticollision sequence is to allow the reader to select one

at a time.  

The

is given an 8-bit Chip_ID value used by the reader to select only one among up to 256 tags  

present within its field range. The Chip_ID is initialized with a random value during the Ready state, or after an  

Initiate() command in the Inventory state.  

The four least significant bits (b

0

to b

3

) of the Chip_ID are also known as the Chip_slot_number. This 4-bit value is  

used by the Pcall16() and Slot_marker() commands during the anticollision sequence in the Inventory state.  

Figure 14.

ST25TB512-AT Chip_ID description  

b7  

b6  

b5  

b4  

b3  

8-bit Chip_ID  

b2  

b1  

b0  

b0 to b3:Chip_slot_n umber  

Each time the

receives a Pcall16() command, the Chip_slot_number is given a new 4-bit random  

value. If the new value is 0000

b

, the

returns its whole 8-bit Chip_ID in its answer to the Pcall16()  

command. The Pcall16() command is also used to define the slot number 0 of the anticollision sequence. When  

the

receives the Slot_marker(SN) command, it compares its Chip_slot_number with the  

Slot_number parameter (SN). If they match, the

returns its Chip_ID as a response to the  

command. If they do not, the

does not answer. The Slot_marker(SN) command is used to define  

all the anticollision slot numbers from 1 to 15.  

DS11456

–

Rev 7  

page 17/45  

ST25TB512-AT  

Description of an anticollision sequence  

Figure 15.

Description of a possible anticollision sequence  

Slot 0  

Slot 1  

Slot 2  

Slot N  

Slot 15  

S

S

O

F

S

S

O

F

E

O

F

S

E

O

F

E

O

F

E

O

F

Slot  

Slot  

Slot  

PCALL 16  

Request  

Reader  

O Marker  

O Marker  

O Marker  

…  

(2)  

(15)  

(1)  

F

F

F

Answer  

Chip_ID  

X1h  

S

O

F

E

O

F

ST25TBxxx  

devices  

Answer  

Chip_ID  

X0h  

Answer  

Chip_ID  

X1h  

Answer  

S

O

F

E

O

F

S

O

F

E

O

F

S

O

F

E

O

F

E

O

F

…  

Chip_ID  

XFh  

Timing  

t

0

+t

1  

t

2  

t

0

+t

1  

t

2  

t

3  

t

2  

t

0

+t

1  

t

2  

No  

collision  

No  

collision  

No  

Answer  

Comment  

Time  

Collision  

1.  

The value X in the answer Chip_ID means a random hexadecimal character from 0 to

F

.  

7.1  

Description of an anticollision sequence  

The anticollision sequence is initiated by the Initiate() command which triggers all the

devices that  

are present in the reader field range, and that are in Inventory state. Only

devices in Inventory  

state will respond to the Pcall16() and Slot_marker(SN) anticollision commands.  

A new

introduced in the field range during the anticollision sequence will not be taken into  

account as it will not respond to the Pcall16() or Slot_marker(SN) command (Ready state).

T

o

b

e considered  

during the anticollision sequence, it must have received the Initiate() command and entered the Inventory state.  

shows the elements of a standard anticollision sequence. (See

for an example.)  

Table 8.

Standard anticollision sequence  

Send Initiate().  

•

•

If no answer is detected, go to step1.  

Step 1

 

Init:  

If only 1 answer is detected, select and access the

. After accessing the

, deselect the tag and go to step1.  

•

If a collision (many answers) is detected, go to step2.  

Send Pcall16().  

Step 2

 

Slot 0  

Step 3

 

Slot 1  

•

•

If no answer or collision is detected, go to step3.  

If 1 answer is detected, store the Chip_ID, Send Select() and go to step3.  

Send Slot_marker(1).  

•

•

If no answer or collision is detected, go to step4.  

If 1 answer is detected, store the Chip_ID, Send Select() and go to step4.  

DS11456

–

Rev 7  

page 18/45  

ST25TB512-AT  

Description of an anticollision sequence  

Send Slot_marker(2).  

Step 4

 

Slot 2  

Step N

 

Slop N  

Step 17

 

Slot 15  

•

•

If no answer or collision is detected, go to step5.  

If 1 answer is detected, store the Chip_ID, Send Select() and go to step5.  

Send Slot_marker(3 up to 14) …  

•

•

If no answer or collision is detected, go to stepN+1.  

If 1 answer is detected, store the Chip_ID, Send Select() and go to stepN+1.  

Send Slot_marker(15).  

•

•

If no answer or collision is detected, go to step18.  

If 1 answer is detected, store the Chip_ID, Send Select() and go to step18.  

All the slots have been generated and the Chip_ID values should be stored into the reader memory. Issue  

the Select(Chip_ID) command and access each identified

one by one. After accessing each  

, switch them into Deselected or Deactivated state, depending on the application needs.  

Step 18  

–

•

•

If collisions were detected between Step2 and Step17, go to Step2.  

If no collision was detected between Step2 and Step17, go to Step1.  

After each Slot_marker() command, there may be no answer, one or several answers from the

devices. The reader must handle all the cases and store all the Chip_IDs, correctly decoded. At the end of the  

anticollision sequence, after Slot_marker(15), the reader can start working with one

by issuing a  

Select() command containing the desired Chip_ID. If a collision is detected, the reader has to generate a new  

sequence in order to identify all unidentified

devices in the field. The anticollision sequence can  

stop when all

devices have been identified.  

gives an example of anticollision sequence, the cells containing (*) highlight the fact that the related tags  

are not yet identified. When the tag is identified, in the table the (*) changes to bold character.  

Table 9.

Example of an anticollision sequence  

Tag1  

Tag2  

Tag3  

Tag4  

Tag5  

Tag6  

Tag7  

Tag8  

Command  

Comment  

Chip_ID Chip_ID Chip_ID Chip_ID Chip_ID Chip_ID Chip_ID Chip_ID  

READY state  

INITIATE()  

28h(*)  

40h(*)  

75h(*)  

13h(*)  

40h(*)  

3Fh(*)  

01h(*)  

4Ah(*)  

02h(*)  

50h(*)  

FEh(*)  

48h(*)  

A9h(*)  

52h(*)  

7Ch(*)  

7Ch(*)  

Each tag gets a random Chip_ID  

Each tag get a new random Chip_ID.  

All tags answer: collisions  

All CHIP_SLOT_ NUMBERs get a  

new random value  

PCALL16()  

45h(*)  

(*)  

12h(*)  

30h(*)  

43h(*)  

55h(*)  

43h(*)  

53h(*)  

73h(*)  

SELECT(30h)  

(*)  

(*)30h  

(*)  

(*)  

(*)  

(*)  

(*)  

Slot0: only one answer  

Slot1: no answer  

Slot2: only one answer  

T

a

g2 is identified  

Slot3: collision  

SLOT_MARKER(1) (*)  

SLOT_MARKER(2) (*)  

(*)  

30h  

(*)  

(*)  

(*)-  

(*)  

(*)-  

(*)  

(*)  

12h(*)  

–

–

–

–

–

–

–

–

(*)  

(*)  

(*)  

SELECT(12h)  

(*)  

12h  

(*)  

(*)  

(*)  

(*)  

(*)  

SLOT_MARKER(3) (*)  

SLOT_MARKER(4) (*)  

SLOT_MARKER(5) 45h(*)  

SLOT_MARKER(6) (*)  

SLOT_MARKER(N) (*)  

SLOT_MARKER(F) (*)  

–

–

–

–

–

–

43h(*)  

(*)  

(*)  

43h(*)  

(*)  

53h(*)  

(*)  

73h(*)  

(*)  

(*)  

Slot4: no answer  

Slot5: collision  

(*)  

55h(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

Slot6: no answer  

SlotN: no answer  

SlotF: no answer  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

All CHIP_SLOT_ NUMBERs get a  

new random value  

40h(*)  

–

–

41h(*)  

53h(*)  

42h(*)  

50h(*)  

74h(*)  

PCALL16()  

40h(*)  

–

–

–

–

(*)  

(*)  

(*)  

(*)  

(*)  

50h(*)  

(*)  

(*)  

(*)  

Slot0: collision  

SLOT_MARKER(1) (*)  

41h(*)  

Slot1: only one answer  

DS11456

–

Rev 7  

page 19/45  

ST25TB512-AT  

Description of an anticollision sequence  

Tag1  

Tag2  

Tag3  

Tag4  

Tag5  

Tag6  

Tag7  

Tag8  

Command  

Comment  

T

a

g4 is identified  

Chip_ID Chip_ID Chip_ID Chip_ID Chip_ID Chip_ID Chip_ID Chip_ID  

SELECT(41h)  

(*)  

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

41h  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

(*)  

SLOT_MARKER(2) (*)  

SELECT(42h) (*)  

SLOT_MARKER(3) (*)  

SELECT(53h) (*)  

SLOT_MARKER(4) (*)  

SELECT(74h) (*)  

SLOT_MARKER(N) (*)  

–

–

–

–

–

–

–

(*)  

42h(*)  

(*)  

Slot2: only one answer  

T

a

g6 is identified  

(*)  

42h  

(*)  

53h(*)  

–

–

–

–

–

(*)  

Slot3: only one answer  

T

a

g5 is identified  

53h  

(*)  

–

–

–

74h(*)  

74h  

–

Slot4: only one answer  

T

a

g8 is identified  

SlotN: no answer  

All CHIP_SLOT_ NUMBERs get a  

new random value  

41h(*)  

–

–

–

–

–

50h(*)  

–

PCALL16()  

(*)  

(*)  

–

–

–

–

–

–

–

–

–

–

50h(*)  

–

–

Slot0: only one answer  

T

a

g7 is identified  

SELECT(50h)  

50h  

Slot1: only one answer but already  

found for tag4  

SLOT_MARKER(1) 41h(*)  

SLOT_MARKER(N) (*)  

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

SlotN: only one answer  

All CHIP_SLOT_ NUMBERs get a  

new random value  

43h(*)  

PCALL16()  

(*)  

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

–

Slot0: only one answer  

Slot3: only one answer  

T

a

g1 is identified  

SLOT_MARKER(3) 43h(*)  

SELECT(43h)  

–

43h  

(*)  

All tags are identified  

DS11456

–

Rev 7  

page 20/45  

ST25TB512-AT  

ST25TB512-AT commands  

8

ST25TB512-AT commands  

See the paragraphs below for a detailed description of the commands available on the

. The  

commands and their hexadecimal codes are summarized in

. A brief is given in  

Appendix B

.  

Table 10.

Command code  

Hexadecimal code  

Command  

06h-00h  

06h-04h  

x6h  

Initiate()  

Pcall16()  

Slot_marker (SN)  

Read_block(Addr)  

Write_block(Addr, Data)  

Get_UID()  

08h  

09h  

0Bh  

0Ch  

Reset_to_inventory  

Select(Chip_ID)  

Completion()  

0Eh  

0Fh  

DS11456

–

Rev 7  

page 21/45  

ST25TB512-AT  

Initiate() command  

8.1  

Initiate() command  

Command code = 06h – 00h  

Initiate() is used to initiate the anticollision sequence of the

. On receiving the Initiate() command,  

all

devices in Ready state switch to Inventory state, set a new 8-bit Chip_ID random value, and  

return their Chip_ID value. This command is useful when only one

in Ready state is present in the  

reader field range. It speeds up the Chip_ID search process. The Chip_slot_number is not used during Initiate()  

command access.  

Figure 16.

Initiate request format  

SOF  

Initiate  

CRC  

CRC  

EOF  

L

H

06h  

00h  

8 bits  

8 bits  

Request parameter:  

No parameter  

•

Figure 17.

Initiate response format  

SOF  

Chip_ID  

8 bits  

CRC  

CRC  

EOF  

L

H

8 bits  

8 bits  

Response parameter:  

Chip_ID of the

•

Figure 18.

Initiate frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

06h  

00h  

CRC  

CRC EOF  

L H  

ST25TBxxx  

<-t -><-t  

->  

1

SOF Chip_ID CRC

 

CRC  

EOF  

H

0

L

DS11456

–

Rev 7  

page 22/45  

ST25TB512-AT  

Pcall16() command  

8.2  

Pcall16() command  

Command code = 06h – 04h  

The

must be in Inventory state to interpret the Pcall16() command.  

On receiving the Pcall16() command, the

first generates a new random Chip_slot_number value  

(in the 4 least significant bits of the Chip_ID). Chip_slot_number can take on a value between 0 an 15 (1111

b

).  

The value is retained until a new Pcall16() or Initiate() command is issued, or until the

is powered  

off. The new Chip_slot_number value is then compared with the value 0000

b

. If they match, the

returns its Chip_ID value. If not, the

does not send any response.  

The Pcall16() command, used together with the Slot_marker() command, allows the reader to search for all the  

Chip_IDs when there are more than one

device in Inventory state present in the reader field  

range.  

Figure 19.

Pcall16 request format  

SOF  

PCALL16  

CRC  

CRC  

EOF  

L

H

06h  

04h  

8 bits  

8 bits  

Request parameter:  

No parameter  

•

Figure 20.

Pcall16 response format  

SOF  

Chip_ID  

8 bits  

CRC  

CRC  

EOF  

L

H

8 bits  

8 bits  

Response parameter:  

Chip_ID of the

•

Figure 21.

Pcall16 frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

06h  

04h  

CRC  

CRC  

EOF  

L

H

ST25TBxxx  

<-t -><-t ->  

SOF Chip_ID CRC  

CRC  

EOF  

0

1

L

H

DS11456

–

Rev 7  

page 23/45  

ST25TB512-AT  

Slot_marker(SN) command  

8.3  

Slot_marker(SN) command  

Command code = x6h  

The ST25TB512-AT must be in Inventory state to interpret the Slot_marker(SN) command.  

The Slot_marker byte code is divided into two parts:  

•

•

•

b

3

to b

0

: 4-bit command code  

with fixed value 6.  

b

7

to b

4

: 4 bits known as the Slot_number (SN). They assume a value between 1 and 15. The value 0 is  

reserved by the Pcall16() command.  

On receiving the Slot_marker() command, the

compares its Chip_slot_number value with the  

Slot_number value given in the command code. If they match, the

returns its Chip_ID value. If  

not, the

does not send any response.  

The Slot_marker() command, used together with the Pcall16() command, allows the reader to search for all the  

Chip_IDs when there are more than one

device in Inventory state present in the reader field  

range.  

Figure 22.

Slot_marker request format  

SOF  

Slot_marker  

X6h  

CRC  

CRC  

EOF  

L

H

8 bits  

8 bits  

Request parameter:  

x: Slot number  

•

Figure 23.

Slot_marker response format  

SOF  

Chip_ID  

8 bits  

CRC  

CRC  

EOF  

L

H

8 bits  

8 bits  

Response parameters:  

Chip_ID of the

•

Figure 24.

Slot_marker frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

X6h  

CRC  

CRC  

EOF  

L

H

ST25TBxxx  

<-t –

>

<

-t ->  

SOF Chip_ID CRC  

CRC  

EOF  

0

1

L

H

8.4  

Select(Chip_ID) command  

Command code = 0Eh  

DS11456

–

Rev 7  

page 24/45  

ST25TB512-AT  

Select(Chip_ID) command  

The Select() command allows the

to enter the Selected state. Until this command is issued, the  

will not accept any other command, except for Initiate(), Pcall16() and Slot_marker(). The Select()  

command returns the 8 bits of the Chip_ID value. An

in Selected state, that receives a Select()  

command with a Chip_ID that does not match its own is automatically switched to Deselected state.  

Figure 25.

Select request format  

SOF  

Select  

0Eh  

Chip_ID  

8 bits  

CRC  

CRC  

EOF  

L

H

8 bits  

8 bits  

Request parameter:  

•

8-bit Chip_ID stored during the anticollision sequence  

Figure 26.

Select response format  

SOF  

Chip_ID  

8 bits  

CRC  

CRC  

EOF  

L

H

8 bits  

8 bits  

Response parameters:  

•

Chip_ID of the selected tag. Must be equal to the transmitted Chip_ID  

Figure 27.

Select frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

0Eh  

Chip_ID CRC  

CRC  

EOF  

L

H

ST25TBxxx  

<-t –

>

<

-t ->  

SOF Chip_ID CRC  

CRC  

EOF  

0

1

L

H

DS11456

–

Rev 7  

page 25/45  

ST25TB512-AT  

Completion() command  

8.5  

Completion() command  

Command code = 0Fh  

On receiving the Completion() command, an

in Selected state switches to Deactivated state and  

stops decoding any new commands. The

is then locked in this state until a complete reset (tag  

out of the field range). A new ST25TB512-AT can thus be accessed through a Select() command without having  

to remove the previous one from the field. The Completion() command does not generate a response.  

All

devices not in Selected state ignore the Completion() command.  

Figure 28.

Completion request format  

SOF  

Completion  

0Fh  

CRC  

CRC  

EOF  

L

H

8 bits  

8 bits  

Request parameters:  

No parameter  

•

Figure 29.

Completion response format  

No Response  

Figure 30.

Completion frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

0Fh  

CRC  

CRC  

EOF  

L

H

ST25TBxxx  

No Response  

DS11456

–

Rev 7  

page 26/45  

ST25TB512-AT  

Reset_to_inventory() command  

8.6  

Reset_to_inventory() command  

Command code = 0Ch  

On receiving the Reset_to_inventory() command, all

devices in Selected state revert to Inventory  

state. The concerned

devices are thus resubmitted to the anticollision sequence. This command  

is useful when two

devices with the same 8-bit Chip_ID happen to be in Selected state at the  

same time. Forcing them to go through the anticollision sequence again allows the reader to generates new  

Pcall16() commands and so, to set new random Chip_IDs.  

The Reset_to_inventory() command does not generate a response.  

All

devices that are not in Selected state ignore the Reset_to_inventory() command.  

Figure 31.

Reset_to_inventory request format  

SOF  

RESET_TO_INVENTORY  

0Ch  

CRC  

CRC  

EOF  

L

H

8 bits  

8 bits  

Request parameter:  

No parameter  

•

Figure 32.

Reset_to_inventory response format  

No Response  

Figure 33.

Reset_to_inventory frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

0Ch  

CRC  

CRC  

EOF  

L

H

ST25TBxxx  

No Response  

DS11456

–

Rev 7  

page 27/45  

ST25TB512-AT  

Read_block(Addr) command  

8.7  

Read_block(Addr) command  

Command code = 08h  

On receiving the Read_block command, the

reads the desired block and returns the 4 data bytes  

contained in the block. Data bytes are transmitted with the least significant byte first and each byte is transmitted  

with the least significant bit first.  

The address byte gives access to the 16 blocks of the

(addresses 0 to 15). Read_block  

commands issued with a block address above 15 will not be interpreted and the

will not return  

any response, except for the System area located at address 255.  

The

must have received a Select() command and be switched to Selected state before any  

Read_block() command can be accepted. All Read_block() commands sent to the

before a  

Select() command is issued are ignored.  

Figure 34.

Read_block request format  

SOF  

Read_block  

08h  

Address  

8 bits  

CRC

L  

8 bits  

CRC

H  

8 bits  

EOF  

Request parameter:  

Address: block addresses from 0 to 15, or 255  

•

Figure 35.

Read_block response format  

SOF  

Data 1  

8 bits  

Data 2  

8 bits  

Data 3  

8 bits  

Data 4  

8 bits  

CRC

L  

8 bits  

CRC

H  

8 bits  

EOF  

Response parameters:  

•

•

•

•

Data 1: Less significant data byte  

Data 2: Data byte  

Data 3: Data byte  

Data 4: Most significant data byte  

Figure 36.

Read_block frame exchange between reader and ST25TB512-AT  

E

O

F

S

O

F

Reader  

08h Address

 

CRC

L

CRC

H  

S

O

F

E

O

F

Data 1

 

Data 2

 

Data 3

 

Data 4

 

CRC

L

CRC

H  

<-t -><-t ->  

ST25TBxxx  

0

1

8.8  

Write_block (Addr, Data) command  

Command code = 09h  

On receiving the Write_block command, the

writes the 4 bytes contained in the command to the  

addressed block, provided that the block is available and not write-protected. Data bytes are transmitted with the  

least significant byte first, and each byte is transmitted with the least significant bit first.  

DS11456

–

Rev 7  

page 28/45  

ST25TB512-AT  

Get_UID() command  

The address byte gives access to the 16 blocks of the

(addresses 0 to 15). Write_block  

commands issued with a block address above 15 will not be interpreted and the

will not return  

any response, except for the System area located at address 255.  

The result of the Write_block command is submitted to the addressed block. See the following Figures for a  

complete description of the Write_block command:  

•

•

•

.  

The Write_block command does not give rise to a response from the

. The reader must check  

after the programming time, t

W

, that the data was correctly programmed. The

must have received  

a Select() command and be switched to Selected state before any Write_block command can be accepted. All  

Write_block commands sent to the

before a Select() command is issued, are ignored.  

Figure 37.

Write_block request format  

SOF  

Write_block  

09h  

Address  

8 bits  

Data 1  

8 bits  

Data 2

 

Data 3  

Data 4  

8 bits  

CRC

L  

8 bits  

CRC

H

EOF  

8 bits  

8 bits  

8 bits  

•

•

•

•

•

•

Request parameters:  

Address: block addresses from 0 to 15, or 255  

Data 1: Less significant data byte  

Data 2: Data byte  

Data 3: Data byte  

Data 4: Most significant data byte.  

Figure 38.

Write_block response format  

No Response  

Figure 39.

Write_block frame exchange between reader and ST25TB512-AT  

Reader  

SOF 09h

 

Address Data

 

1 Data

 

2 Data

 

3 Data

 

4 CRC

L

CRC

H

EOF  

ST25TBxxx  

No Response  

8.9  

Get_UID() command  

Command code = 0Bh  

On receiving the Get_UID command, the

returns its 8 UID bytes. UID bytes are transmitted with  

the least significant byte first, and each byte is transmitted with the least significant bit first.  

DS11456

–

Rev 7  

page 29/45  

ST25TB512-AT  

Get_UID() command  

The

must have received a Select() command and be switched to Selected state before any  

Get_UID() command can be accepted. All Get_UID() commands sent to the

before a Select()  

command is issued, are ignored.  

Figure 40.

Get_UID request format  

SOF  

Get_IUD  

0Bh  

CRC

L  

8 bits  

CRC

H

EOF  

8 bits  

Request parameter:  

No parameter  

•

Figure 41.

Get_UID response format  

SOF UID

 

0 UID

 

1  

8 bits

 

8 bits  

UID 2  

8 bits  

UID 3  

8 bits  

UID 4  

8 bits  

UID 5  

8 bits  

UID 6  

8 bits  

UID 7  

8 bits  

CRC

L  

8 bits  

CRC

H

EOF  

8 bits  

Response parameters:  

•

•

•

UID 0: Less significant UID byte  

UID 1 to UID 6: UID bytes  

UID 7: Most significant UID byte.  

Unique identifier (UID)  

Members of the

family are uniquely identified by a 64-bit unique identifier (UID). This is used for  

addressing each

device uniquely after the anticollision loop. The UID complies with ISO/IEC  

15963 and ISO/IEC 7816-6. It is a read-only code, and comprises (as summarized in

):  

•

•

•

•

an 8-bit prefix, with the most significant bits set to D0h  

an 8-bit IC manufacturer code (ISO/IEC 7816-6/AM1) set to 02h (for STMicroelectronics)  

a 8-bit product ref code set to 33h for

a 40-bit unique serial number  

Figure 42.

64-bit unique identifier of the ST25TB512-AT  

MSB  

63  

LSB  

55  

47  

39  

0

D0h  

02h  

33h  

Unique Serial Number  

DS11456

–

Rev 7  

page 30/45  

ST25TB512-AT  

Power-on state  

Figure 43.

Get_UID frame exchange between reader and ST25TB512-AT  

S

O

F

E

O

F

Reader  

CRC

L

CRC

H  

0Bh  

E

O

F

S

O

F

ST25TBxxx  

<-t -><-t ->  

UID 0

 

UID 1

 

UID 2 UID 3 UID 4

 

UID 5

 

UID 6

 

UID 7

 

CRC

L

CRC

H  

0

1

8.10  

Power-on state  

After power-on, the

is in the following state:  

•

•

•

•

It is in the low-power state.  

It is in Ready state.  

It shows highest impedance with respect to the reader antenna field.  

It will not respond to any command except Initiate().  

DS11456

–

Rev 7  

page 31/45  

ST25TB512-AT  

Maximum ratings  

9

Maximum ratings  

Stressing the device above the ratings listed in the absolute maximum ratings table 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  

ratings conditions for extended periods may affect device reliability. Refer also to the STMicroelectronics SURE  

Program and other relevant quality documents.  

Table 11.

Absolute maximum ratings  

Symbol  

Parameter  

Min. Max.

 

Unit  

15  

–

25  

°C  

Sawn wafer  

9

25  

(kept in its original packing form)  

months  

°C  

T

, t  

Storage conditions  

STG STG  

19  

–

Unsawn wafer  

(kept in its antistatic bag)  

23  

months  

mA  

I

Supply current on AC0 / AC1  

–

–

40  

CC  

RF input voltage amplitude between AC0 and AC1, GND  

pad left floating  

V

V

–

–

–

10  

V

V

MAX  

Human Body Model

Electrostatic discharge voltage  

2000  

ESD  

1. Counted

 

from ST shipment date.  

2. Based

 

on characterization, not tested in production.  

3. Positive

 

and negative pulses applied on different combinations of pin connections, according to AEC-Q100-002 (compliant  

with ANSI/ESDA/JEDEC JS-001-2012, C1=100 p

F

,

R

1=1500 Ω, R2=500 Ω).  

DS11456

–

Rev 7  

page 32/45  

ST25TB512-AT  

RF electrical parameters  

10  

RF electrical parameters  

Table 12.

Operating conditions  

Parameter  

Symbol  

Min.  

Max.  

Unit  

T

Ambient operating temperature  

-40  

85  

°C  

A

Table 13.

Electrical characteristics  

Symbol  

Parameter  

Operating field according to ISO  

Operating field in extended temperature range  

Back-scattering induced voltage  

Internal tuning capacitor  

Condition  

Min Typ Max  

Unit  

T =

 

0 °C to 50 °C  

H_ISO  

1500  

1500  

20  

–

7500  

7500  

–

A

mA/m  

T =

 

-40 °C to 85 °C  

H_extended  

–

A

V

ISO 10373-6  

13.56 MHz

–

mV  

pF  

RET  

C

62  

68  

74  

TUN  

1. The

 

tuning capacitance value is measured with ST characterization equipement at chip Power On Reset. This value is to be  

used as reference for antenna design. Min and Max value are deduced from correlation with industrial tester limits.  

Note:  

For inlay implementation, the antenna design applied for SRT512 can be re-used as-is for

:  

typical 68pF value for the

is equivalent to what was specified in the SRT512 data-sheet as 64p

F

.  

This change is related to a different measurement methodology between SRT512 and

.  

Table 14.

RF characteristics  

Symbol  

Parameter  

RFcarrier frequency  

Condition  

Min  

Typ  

Max Unit  

f

–

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

–

13.553  

–

11  

–

13.567 MHz  

CC  

MI  

Carrier modulation index  

10% Rise and Fall times  

8

0.1  

–

14  

1.25  

–

%

µs  

µs  

µs  

CARRIE R  

t

, t  

RFR RFF  

t

Minimum pulse width for Start bit  

ASK modulation data jitter  

ETU = 128/fCC  

Coupler to

9.44  

–

RFSBL  

t

JIT  

–2  

+2  

Minimum timefrom carrier generation to first  

data  

t

–

5

–

–

ms  

MIN CD  

f

Subcarrier frequency  

fCC/16  

–

847.5  

–

–

kHz  

µs  

S

t

Antenna reversal delay  

–

–

–

159  

0

t

Synchronization delay  

–

151  

–

µs  

1

t

Answer to new request delay  

Time between request characters  

14 ETU  

132  

0

–

–

–

µs  

2

t

Coupler to

57  

µs  

DR  

to  

coupler  

t

Time between answer characters  

–

0

–

µs  

DA  

With no auto-erase cycle (OTP)  

With auto-erase cycle (EEPROM)  

–

–

–

–

3

5

ms  

ms  

t

Programming time for write  

W

Binarycounter decrement with  

tearing condition  

–

–

7

ms  

DS11456

–

Rev 7  

page 33/45  

ST25TB512-AT  

RF electrical parameters  

1.  

All timing measurements were performed on a reference antenna with the following characteristics:  

–

–

–

–

–

External size: 76 mm x 46 mm  

Number of turns: 4  

Width of conductor: 0.9 mm  

Space between 2 conductors: 0.9 mm  

Tuning Frequency: 13.58 MHz  

Figure 44.

ST25TB512-AT synchronous timing, transmit and receive  

ASK Modulated signal from the Reader to the Contactless device  

t

RFF  

t

A

B

RFR  

ƒcc  

t

RFSBL  

t

MIN CD  

FRAME Transmission

 

between the reader and the contactless device  

t

t

DR  

DR  

DATA  

EOF  

1

1

0

FRAME

T

r

ansmitted by the reader in ASK  

847KHz  

1 1  

0

DATA  

1

0

DATA  

1

0

SOF  

FRAME Transmitted

 

by the  

ST25TBxxx in BPSK  

t

t

t

t

DA  

0

1

DA  

Data jitter on FRAME

 

Transmitted by the reader in ASK  

t

t

JIT  

t

t

t

JIT  

JIT  

JIT  

JIT  

0

START  

t

t

t

t

t

RFSBL  

RFSBL  

RFSBL  

RFSBL  

RFSBL  

DS11456

–

Rev 7  

page 34/45  

ST25TB512-AT  

Ordering information  

11  

Ordering information  

Table 15.

Ordering information scheme  

Example:  

ST25  

T

B

512  

-A  

T

6

G

6

Device type  

ST25 = RF  

memory  

Product type  

T =

T

a

gs + RFID  

Protocol  

B = ISO14443-B  

Memory density  

512 (binary)  

Interface  

A = None  

Features  

T = Transport (+ counter option)  

Device grade  

6 = – 40 to 85 °C  

Package/Packaging  

G = Bumped 120 μm  

U = Unsawn 725 μm  

Capacitor value  

6 = 68 pF  

Note:  

Devices are shipped from the factory with the memory content bits erased to 1.  

For a list of available options (speed, package, etc.) or for further information on any aspect of this device, please  

contact your nearest ST sales office.  

DS11456

–

Rev 7  

page 35/45  

ST25TB512-AT  

ISO-14443 Type B CRC calculation  

A

ISO-14443 Type B CRC calculation  

#include <stdio.h>  

#include <stdlib.h>  

#include <string.h>  

#include <ctype.h>  

#define BYTE unsigned char  

#define USHORT unsigned short  

unsigned short UpdateCrc(BYTE ch, USHORT *lpwCrc)  

{

ch = (ch^(BYTE)((*lpwCrc) & 0x00FF));  

ch = (ch^(ch<<4));  

*lpwCrc = (*lpwCrc >> 8)^((USHORT)ch <<  

8)^((USHORT)ch<<3)^((USHORT)ch>>4);  

return(*lpwCrc);  

}

void ComputeCrc(char *Data, int Length, BYTE *TransmitFirst, BYTE  

*TransmitSecond)  

{

BYTE chBlock; USHORTt wCrc;  

wCrc = 0xFFFF; // ISO 3309  

do  

{

chBlock = *Data++;  

UpdateCrc(chBlock, &wCrc);  

} while (–Length);  

wCrc = ~wCrc; // ISO 3309  

*TransmitFirst = (BYTE) (wCrc & 0xFF);  

*TransmitSecond = (BYTE) ((wCrc >> 8) & 0xFF);  

return;  

}

int main(void)  

{

BYTE BuffCRC_B[10] = {0x0A, 0x12, 0x34, 0x56}, First, Second, i;  

printf(“Crc-16 G(x) = x^16 + x^12 + x^5 + 1”);  

printf(“CRC_B of [ “);  

for(i=0; i<4; i++)  

printf(“%02X “,BuffCRC_B[i]);  

ComputeCrc(BuffCRC_B, 4, &First, &Second);  

printf(“] Transmitted: %02X then %02X.”, First, Second);  

return(0);  

DS11456

–

Rev 7  

page 36/45  

ST25TB512-AT  

ST25TB512-AT command brief  

B

ST25TB512-AT command brief  

Figure 45.

Initiate frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

06h  

00h  

CRC  

CRC EOF  

L H  

ST25TBxxx  

<-t -><-t  

->  

1

SOF Chip_ID CRC

 

CRC  

EOF  

0

L

H

Figure 46.

Pcall16 frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

06h  

04h  

CRC  

CRC  

EOF  

L

H

ST25TBxxx  

<-t -><-t ->  

SOF Chip_ID CRC  

CRC  

EOF  

0

1

L

H

Figure 47.

Slot_marker frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

X6h  

CRC  

CRC  

EOF  

L

H

ST25TBxxx  

<-t –

>

<

-t ->  

SOF Chip_ID CRC  

CRC  

EOF  

0

1

L

H

Figure 48.

Select frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

0Eh  

Chip_ID CRC  

CRC  

EOF  

L

H

ST25TBxxx  

<-t –

>

<

-t ->  

SOF Chip_ID CRC  

CRC  

EOF  

0

1

L

H

Figure 49.

Completion frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

0Fh  

CRC  

CRC  

EOF  

L

H

ST25TBxxx  

No Response  

DS11456

–

Rev 7  

page 37/45  

ST25TB512-AT  

ST25TB512-AT command brief  

Figure 50.

Reset_to_inventory frame exchange between reader and ST25TB512-AT  

Reader  

SOF  

0Ch  

CRC  

CRC  

EOF  

L

H

ST25TBxxx  

No Response  

Figure 51.

Read_block frame exchange between reader and ST25TB512-AT  

E

O

F

S

O

F

Reader  

08h Address

 

CRC

L

CRC

H  

S

O

F

E

O

F

Data 1

 

Data 2

 

Data 3

 

Data 4

 

CRC

L

CRC

H  

<-t -><-t ->  

ST25TBxxx  

0

1

Figure 52.

Write_block frame exchange between reader and ST25TB512-AT  

Reader  

SOF 09h

 

Address Data

 

1 Data

 

2 Data

 

3 Data

 

4 CRC

L

CRC

H

EOF  

ST25TBxxx  

No Response  

Figure 53.

Get_UID frame exchange between reader and ST25TB512-AT  

S

O

F

E

O

F

Reader  

CRC

L

CRC

H  

0Bh  

E

O

F

S

O

F

ST25TBxxx  

<-t -><-t ->  

UID 0

 

UID 1

 

UID 2 UID 3 UID 4

 

UID 5

 

UID 6

 

UID 7

 

CRC

L

CRC

H  

0

1

DS11456

–

Rev 7  

page 38/45  

ST25TB512-AT  

Revision history  

Table 16.

Document revision history  

Changes  

Date  

Version  

8-Jun-2016  

09-Feb-2016  

1

2

Initial release  

Updated Section 1 Description  

Updated Figure 26. Select response format, Figure 39. Write_block frame exchange between reader  

and ST25TB512-AT  

03-Mar-2016  

19-Apr-2016  

3

4

Changed confidentiality level from ST restricted to public  

Updated:  

•

Figure 42. 64-bit unique identifier of the ST25TB512-A

T

,  

Figure 44. ST25TB512-AT synchronous timing, transmit and receive  

16-Sep-2016  

5

•

•

Section 8.9 Get_UID() command  

T

a

ble 11. Absolute maximum ratings,  

T

a

ble 15. Ordering information scheme  

11-Nov-2016  

20-Sep-2018  

6

7

Updated Features in cover page  

Updated

, added

and

DS11456

–

Rev 7  

page 39/45  

ST25TB512-AT  

Contents  

Contents  

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

.

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .