| Electronic Components Datasheet Search |
|
MF2DLX0 Datasheet(PDF) 12 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
MF2DLX0 Datasheet(HTML) 12 Page - NXP Semiconductors |
|
12 / 132 page ![]() NXP Semiconductors MF2DL(H)x0 MIFARE DESFire Light contactless application IC MF2DL_H_x0 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2019. All rights reserved. Product data sheet Rev. 3.3 — 5 April 2019 COMPANY PUBLIC 430733 12 / 132 been computed yet. Note that this value will never be used in a Transaction MAC computation. • Transaction MAC Value (TMV) 8 bytes. The TMV is initialized to all zero bytes on file creation. A TransactionMAC file is created with the CreateTransactionMACFile command, see Section 11.7.6. A TransactionMAC file can be read with a ReadData command, protected by the Read access right, see below. The behavior is identical as reading a StandardData file of 12 bytes. A TransactionMAC file cannot be written directly. The TMC and TMV are related with the latest successful transaction and are updated automatically on successful CommitTransaction command. In addition, the last calculated TransactionMAC values can be read out from the TransactionMAC file, in case the response to the CommitTransaction command has not been received correctly by the PCD. Therefore, the implementation of this file type supports the integrated backup mechanism for anti- tearing protected atomic update of these values together with the rest of the transaction updates. In addition, the following content is stored in the TransactionMAC file: • optionally the TransactionMAC ReaderID (TMRIPrev), see Section 11.9.3, as a committed value becomes valid together with the updated TMC and TMV on CommitTransaction. • the AppTransactionMACKey, as it is specified when creating the TransactionMAC file. However, these values are never immediately accessible on the command interface via the file (e.g. using ReadData). 8.2.3.5 File access rights management File data is accessed with 3 different access rights Read, Write and ReadWrite. In addition, an access right called Change is specified per file permitting ChangeFileSettings to change the file access rights. An access right is granted if at least one condition associated to it is satisfied. Such conditions are called access conditions. Access conditions are associated with an access right and evaluated to decide whether the access right is granted or not. There are three kinds of access conditions: • The access condition where a valid authentication with a given AppKey of the targeted application is needed to access related commands listed in Table 9. The access condition is satisfied if the current valid authentication has been performed with the given AppKey and not satisfied in all other cases. The AppKey is specified with its number. • The free access condition meaning the related commands listed in Table 9 can be accessed without an active authentication. • The no access condition meaning no access to related commands listed in Table 9. The access conditions are specified on 4 bits as defined in the following table. Table 6. Access condition Condition value Description 0h..4h key number of a AppKey |
|
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 |