| Electronic Components Datasheet Search |
|
MF2DLX0 Datasheet(PDF) 11 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
MF2DLX0 Datasheet(HTML) 11 Page - NXP Semiconductors |
|
11 / 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 11 / 132 A StandardData file is not covered by the transaction mechanism and therefore does not implement a transaction-based backup mechanism. Thus data are available to read as soon as they are written in the file. The writing operations of single frames up to 128 bytes with a WriteData or ISOUpdateBinary command are also tearing protected. 8.2.3.2 Value file The Value file stores the data as a 4 byte signed integer. The Value file can be read with the GetValue command. The value can be manipulated with Credit, Debit and LimitedCredit commands, respectively. The value is restricted by an upper and lower limit that the current value of the file cannot exceed. The Value file can support a LimitedCredit feature as defined in Section 11.8.6. The free GetValue allows a user to get freely the value of a value file bypassing an authentication if necessary as long as there is one access condition associated with GetValue command that is different from "no access" condition, see Section 11.5.1 The Value file implements a backup mechanism. All operations executed on a value file within the current transaction will be effective only when a successful CommitTransaction will be executed. Meanwhile or if the transaction is aborted or not successfully committed, the previous value remains effective and is returned by a GetValue. 8.2.3.3 Record file The record file is a CyclicRecord file which allows storing latest 4 records of 16-byte (each record) size. The record file adds up new records when a successful WriteRecord command is executed. When the maximum number of records of the file is reached, the next new record overwrites the oldest record as defined Section 11.8.8. The record file implements a backup mechanism. All operations executed on a record file within the current transaction are effective only when a successful CommitTransaction command is executed. If the transaction is aborted or not successfully committed the previous file image is effective and returned by a ReadRecords command. Within a record file, records are numbered starting with the latest record written. Meaning that the latest record written has the number 0, the second latest record written has the number 1 and so on. Its valid range is from 0 to the number of existing records ExistingRecCount- 1 in the record file. This indexing is used in the data management commands to address records within the Record file. Note that when reading out records, the records are returned in the chronological order that they have been written, i.e. the oldest record is returned first. 8.2.3.4 TransactionMAC file A TransactionMAC file is used to store Transaction MAC-related information. It consists of the following items: • Transaction MAC Counter (TMC) 4 byte unsigned integer. The TMC is initialized to 00000000h on file creation. This value means that no Transaction MAC has |
|
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 |