Command 0x1102 – Pass Through Command for MIFARE DESFire, Type 4

After a MIFARE DESFire Light/EV1/EV2/EV3 Tag is activated, the host uses this command to send commands and receive responses to and from a MIFARE DESFire Tag.

There will be a fixed 30 second timeout for commands that require multiple command/responses.

Timeout: 30 seconds for commands that require multiple command/responses.

Table - Request Data for Command 0x1102 – Pass Through Command for MIFARE DESFire, Type 4

Tag
Len
Value / Description
Typ
Req
Default

Beginning of any wrappers, at minimum including Request Message

1102

Command 0x1102 – Pass Through Command for MIFARE DESFire, Type 4

81

var

Command to Send. See DESFire Data Sheet (MF2DLHX0). Should follow ISO 7816-4 APDU format:

  • C-APDU

    • CLA INS P1 P2 Lc Data Le

B

R

82

01

00 – No Encrypt 01 - Encrypt

83

01

00 – Expect More Commands 01 – FF (Last Command). If last command, Device will provide a single beep after receiving a successful response from tag; otherwise, device will provide a double beep.

B

R

End of any wrappers, at minimum including Request Message

Table - Response Data for Command 0x1102 – Pass Through Command for MIFARE DESFire, Type 4

Tag
Len
Value / Description
Typ
Req
Default

Beginning of any wrappers, at minimum including Response Message

1102

Command 0x1102 – Pass Through Command for MIFARE DESFire, Type 4

81

02

Tag Response (SW1 SW2). See DESFire Data Sheet (MF2DLHX0). Should follow ISO 7816-4 APDU format:

  • SW1 and SW2 of R-APDU

If card is not able to respond:

  • SW1 = 0x64, SW2 = 0x00

B

R

N/A

82

var

Tag Data:

  • Data of R-APDU

Encryption Control: If encrypted, see Table 107 - Payload for Encrypted NFC/MIFARE Data. If unencrypted, see Table 108 – Unencrypted NFC/MIFARE Data.

B

O

N/A

End of any wrappers, at minimum including Response Message

If the request started successfully, the Request Status in the message wrapper is: OK, Started / Running, All good / requested operation was successful.

Table - Request Example (Get Version Part 1)

Table - Response Example (Get Version Part 1)

Encrypted Data Format

Table - Payload for Encrypted NFC/MIFARE Data

Tag
Len
Value / Description
Typ
Req
Default

/DFDF59

var

Encrypted Data Primitive. Decrypt the value of this TLV data object using the algorithm and variant specified in the Encrypted Data KSN parameter and the Encrypted Data Encryption Type parameter to read its contents. The format of the decrypted data is shown in Table 360.

B

R

/DFDF50

var

Encrypted Data KSN

B

R

/DFDF51

01

Encrypted Data Encryption Type. See section 4.4 Encryption Type for a list of valid values.

B

R

End of Notification Message

Table – Unencrypted NFC/MIFARE Data

Tag
Len
Value / Description
Typ
Req
Default

FC

var

NFC/MIFARE Data Container

T

R

/DF7A

var

NFC/MIFARE Data

B

O

Last updated