MF2DL1000DA4SLASH02 datasheet(38/132 Pages) NXP

38 / 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.

Product data sheet

Rev. 3.3 — 5 April 2019

COMPANY PUBLIC

430733

38 / 132

calculated TMV, as defined in Section 10.3.2.4 and the increased TMC which was used

for the calculation of SesTMACKey.

In case the application is configured for LRP, this means the used actTMC and sesTMC,

see Section 10.3.2.1, are written into the file. On successful CommitTransaction,

the sesTMC is also reset to zero and written to the non-user-accessible NVM for

future session key generation. If TMC reached the TMCLimit, see Section 10.3.2.2,

the application remains selected, but with limited functionality: no data management

commands, see Section 11.8 can be executed anymore, except ReadData targeting

the TransactionMAC file. Also CommitReaderID will be rejected. All these file updates

are processed as a single atomic operation. In case of tearing, either all or none of the

changes are applied to the memory.

After execution of this command a new transaction is started.

The command is rejected if no application has been selected.

An error code is also returned if no write access has been done to any of the backup

file types and, in case the application is protected by the Transaction MAC feature (see

Section 10.3), no Transaction MAC calculation update has been done. This means no

command that is included in the Transaction MAC calculation has been executed, i.e.

the TMI is still the empty string. So note that if Transaction MAC is enabled, successful

execution of CommitTransaction updating the TransactionMAC is possible without any

write operation, as read operations are also included in the Transaction MAC calculation.

If CommitReaderID is required according to access right configuration of the

TransactionMAC, this command will be rejected if no ReaderID has been committed

during the ongoing transaction, i.e. if TMRICur is still the empty string. If a ReaderID

was committed in an authenticated state (EV2 authenticated state or LRP authenticated

state), this value TMRICur is stored in non-volatile memory as TMRIPrev as part of the

atomic operation. If the ReaderID was committed when not authenticated, TMRIPrev is

not updated.

The CommitTransaction requires MAC if there is an active authentication. Information on

authentication and secure messaging-dependent structure of the command can be found

in Section 9.

The CommitTransaction is typically the last command of a transaction before deselecting

the card with the ISO/IEC 14443-4 deselect command [3].

Note that TMC and TMV can also be read out encrypted, if preferred. In this case,

the TransactionMAC file should be configured for CommMode.Full. One can then use

ReadData to retrieve this information, instead of requesting it within the response of

CommitTransaction.

10.2.2 AbortTransaction

A transaction can be aborted by explicitly issuing a AbortTransaction command.

Next to this any ongoing transaction is also automatically aborted after:

• unsuccessful execution of a command

• selecting an application with the ISOSelectFile command, even if the same application

is reselected.

• creating/deleting the TransactionMAC file with CreateTransactionMACFile or

DeleteTransactionMACFile

• enabling LRP with SetConfiguration

• renaming files with SetConfiguration

MF2DL1000DA4/02 Datasheet(PDF) 38 Page - NXP Semiconductors

MF2DL1000DA4/02 Datasheet(HTML) 38 Page - NXP Semiconductors

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL