SL2S6002_SDS

All information provided in this document is subject to legal disclaimers.

© NXP Semiconductors N.V. 2016. All rights reserved.

Product short data sheet

COMPANY PUBLIC

Rev. 3.0 — 16 June 2016

374730

6 of 14

NXP Semiconductors

SL2S6002

ICODE DNA

6.2.3 Configuration Memory

The configuration memory contains the security configuration information. Access to this

memory area is only possible with READ_CONFIG and WRITE_CONFIG commands

depending on the initialization status.

The configuration memory contains 48 blocks of 4 bytes.

6.2.3.1

Originality signature

The ICODE DNA offers a feature to verify the origin of a tag with a certain confidence with

the UID towards an originality signature which is stored in the configuration memory bank.

The originality signature can be read with the READ_SIGNATURE command or with the

READ_CONFIG command.

The ICODE DNA provides the possibility to customize the originality signature to

personalize the IC individually for specific application. At delivery the ICODE DNA is

pre-programmed with the NXP originality signature described below. This signature is

unlocked in the dedicated memory. If needed, the signature can be reprogrammed with a

custom-specific signature using the WRITE_CONFIG command during the

personalization process by the customer. The signature can be permanently locked

afterwards by setting the Config Header to “locked “with the WRITE_CONFIG command

to avoid further modifications.

Remark: If no customized originality signature is required, it is recommended to

permanently lock the NXP signature during the initialization process by setting the Config

Header to locked with the WRITE_CONFIG command.

6.2.3.2

Customer ID (CID)

The Customer ID is 0xC000 at delivery and can be reprogrammed and locked. In order to

distinguish between NXP programmed and customized CIDs, the 2 most significant bits of

CID_0 are automatically set to 1 when the CID is programmed with the WRITE_CONFIG

command (input CID is bit wise OR with 0xC000).

CID = 0xC000 | <input CID>, e.g. 0xD053 = 0xC000 | 0x1053

The CID can be permanently locked afterwards by setting the Config Header to “locked”

with the WRITE_CONFIG command to avoid further modifications.

Remark: If no customized originality signature is required, it is recommended to

permanently lock the CID during the initialization process by setting the Config Header to

“locked” with the WRITE_CONFIG command.

6.2.3.3

Authentication Limit

The Authentication Limit is a feature to limit the number of authentications (tag as well as

mutual authentications) with the CHALLENGE or AUTHENTICATE command.

6.2.3.4

Key Privileges

The key privileges define the privileges for the related key used with mutual

authentication. If the related privilege is enabled, the access for the depending feature is

granted after mutual authentication with the related key.