ST25DV64K datasheet(79/220 Pages) STMICROELECTRONICS

79 / 220 page

DocID027603 Rev 4

79/220

ST25DV04K ST25DV16K ST25DV64K

ST25DVxxx specific features

219

Note:

Setting 00b in PWD_CTRL_Ai field means that RF user security session cannot be open by

any password for the corresponding area.

When updating RFAiSS registers, the new protection value is effective immediately after the

•

Rf blocks 0 and 1 are exceptions to this protection mechanism:

–

RF blocks 0 and 1 can be individually write locked by issuing a (Ext) Lock Single

Block RF command. Once locked, they cannot be unlock through RF.

LOCK_CCFILE register is automatically updated when using (Ext) Lock Single

Block command.

–

A RF user needs no password to lock blocks 0 and/or 1.

–

Locking blocks 0 and/or 1 is possible even if the configuration is locked

(LOCK_CFG=1).

–

Locking blocks 0 and/or 1 is possible even if the area is write locked.

–

Unlocking area1 (through RFA1SS register) does not unlock blocks 0 and 1 if they

have been locked though (Ext) Lock Block command.

–

Once locked, the RF user cannot unlock blocks 0 and/or 1 (can be done by I2C

host).

Note:

When areas size are modified (ENDAi registers), RFAiSS registers are not modified.

User memory protection from I2C access

In I2C mode, each area can also have individual Read/Write access conditions, but only one

I2C password is used to unlock I2C security session for all areas.

The I2CSS register is used to set protection against read and write operation for each area

(see Table 32: I2CSS for details about available read and write protections).

When updating I2CSS registers, the new protection value is effective immediately after the

I2C user memory Bytes 0000h to 0003h (RF Block 0) and 0004h to 0007h (RF Block 1) can

be individually locked and unlocked by writing in the LOCK_CCFILE register (by group of 4

Bytes), independently of Area 1 protection. Unlocking Area 1 (through I2CSS register) does

not unlock those bytes if they have been locked though the LOCK_CCFILE register.

Note:

When areas size are modified (ENDAi registers), I2CSS register is not modified.

Retrieve the security status of a user memory block or byte

RF user can read a block security status by issuing following RF commands:

•

(Ext) Get Multiple Blocks Security Status command.

•

(Ext) (Fast) Read Single Block with option flag set to 1.

•

(Ext) (Fast) Read Multiple Blocks with option flag set to 1.

ST25DV will respond with a Block security status containing a Lock_bit flag as specified in

ISO 15693 standard. This lock_bit flag is set to one if block is locked against write.

Lock_bit flag value may vary if corresponding RF user security session is open or closed.

I2C host can retrieve a block security status by reading the I2CSS register to get security

status of the corresponding area and by reading the I2C_SSO_Dyn register to know if I2C

security session is open or closed.

ST25DV64K Scheda tecnica(PDF) 79 Page - STMicroelectronics

ST25DV64K Scheda tecnica(HTML) 79 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Scheda tecnica Scarica

Link URL