| Electronic Components Datasheet Search |
|
NTP53X2 Datasheet(PDF) 108 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
NTP53X2 Datasheet(HTML) 108 Page - NXP Semiconductors |
|
108 / 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 108 / 133 aaa-035476 tuning cap optional open drain control signal to control host Rpu 1 µF HOST VCC VOUT VDD GND VOUT configurable to 1.8 V, 2.4 V or 3 V ED LA LB GND Figure 13. Energy harvesting example circuit How to use energy harvesting in applications is described in AN12365. 8.6 Security NTAG 5 link implements different levels to protect data. The easiest, but efficient method is to lock EEPROM to read only. With the plain password authentication scheme, the memory can be split in three different parts with different access conditions. With NTP5332's mutual AES authentication the memory is split in three different parts again, but with the advantage, that the password will never be transmitted in plain text. Configuration area and SRAM can be protected from both interfaces as well. Further implementation details can be found in AN12366. 8.6.1 Locking EEPROM to read only Independent on the split of the memory, the user memory may be locked to read-only. If the user EEPROM shall stay in read/write state, the LOCK BLOCK command can be disabled (see Table 39) and lock block sections can be locked (see Table 80). With these features, it can be ensured, NTAG 5 link stays in read/write state. Locking the complete EEPROM to read-only as defined in NFC Forum Type 5 Tag specification is quite time consuming. Every single block needs to be addressed by a LOCK BLOCK command (see Section 8.2.3.5). To accelerate this locking, NTAG 5 link stores the information in the configuration area. With this feature, locking the EEPROM can be accelerated by a factor of 16. Note, that these bits are one time programmable (see Section 8.1.3.30) and blocks are indicated as locked in the Get Multiple Block Security Status response. As long as I2C Lock Block Configuration bytes are not set to 1b, the user EEPROM may still be modified from I2C perspective. |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List 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 |