| データシートサーチシステム |
|
NTP53X2 データシート(PDF) 21 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
NTP53X2 データシート(HTML) 21 Page - NXP Semiconductors |
|
21 / 133 page ![]() NXP Semiconductors NTP53x2 NTAG 5 link - NFC Forum-compliant I2C bridge NTP53x2 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2020. All rights reserved. Product data sheet Rev. 3.3 — 3 July 2020 COMPANY PUBLIC 544533 21 / 133 Value Mode Write Access All others Invalid No 8.1.3.3 Customer ID (CID) The Customer ID at delivery is C000h and can be reprogrammed and locked. It might be used to identify the product. The two most significant bits (b7 and b6 of CID (MSB)) are always equal to 11b. Only CID[13-0] may be written by customer. Note, that other values of the two most significant bits are RFU. When the CID is written with WRITE CONFIG command, the 2 most significant bits are always set to 11b. The input CID in WRITE CONFIG command (see Section 8.2.3.2.2) is bit wise ORed with C000h. As long as not locked by the I2C section lock, CID maybe updated from I2C perspective with the same logic as from NFC perspective. Example: When setting CID to 10AAh, resulting customer-specific CID is D0AAh. Table 15. Customer ID (CID) location Block Address NFC I2C Byte 0 Byte 1 Byte 2 Byte 3 09h 1009h CID (LSB) CID (MSB) RFU The CID can be permanently locked by setting the Configuration Header to Locked state (see Table 14) using WRITE CONFIG command. Note, that Originality Signature gets locked, too. 8.1.3.4 NFC Global Crypto Header The NFC Global Crypto Header (NFC_GCH) defines the status and access of the • NFC passwords in plain password mode and all other NFC features listed below • NFC Keys • NFC Protection Pointer • NFC Protection Pointer Conditions • NFC Key Headers • NFC Key Privileges • NFC Crypto Configuration Header • EAS and AFI protection As long as not locked by the RF section lock, the NFC Global Crypto Header can be written with WRITE CONFIG command (see Section 8.2.3.2.2). The programming of NFC Global Crypto Header can be done in only one direction from lower state to higher independently from the interface and it is irreversible. Same rules apply from I2C perspective, as long as not locked by the I2C section lock. Once locked (as per table below), GCH cannot be updated anymore. |
|
リンク URL |
| ALLDATASHEETはお客様のビジネスに役立ちますか? [ DONATE ] |
Alldatasheetは | 広告 | お問い合わせ | プライバシーポリシー | データシートへのリンク | リンク交換 | メーカーリスト All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |