Mifare Desfire as Type 4 card

[leon_su]

Hi all

I want to read the customized data of Mifare Desfire EV2 card on PN7150, but it fails on CC Select, what should I do?

Thanks in advance
Leon

The following message logs

Running the NXP-NCI project.

NCI >> 20 00 01 01

NCI << 40 00 03 00 11 01

NCI >> 20 01 00

NCI << 40 01 19 00 03 1e 03 00 08 00 01 02 03 80 81 82 83 02 d0 02 ff 02 00 04 88 10 01 a0

NCI >> 20 02 05 01 00 02 00 01

NCI << 40 02 02 00 00

NCI >> 2f 00 01 01

NCI << 4f 00 01 00

NCI >> 20 03 03 01 a0 14

NCI << 40 03 25 00 01 a0 14 20 46 72 69 20 41 70 72 20 32 34 20 31 35 3a 31 35 3a 34 36 20 32 30 ...

NCI >> 20 00 01 00

NCI << 40 00 03 00 11 00

NCI >> 20 01 00

NCI << 40 01 19 00 03 1e 03 00 08 00 01 02 03 80 81 82 83 02 d0 02 ff 02 00 04 88 10 01 a0

NCI >> 21 00 13 06 04 02 02 01 01 01 02 01 01 03 01 01 04 01 02 80 01 80

NCI << 41 00 01 00

NCI >> 21 01 07 00 01 01 03 00 01 04

NCI << 41 01 01 00

NCI >> 20 02 04 01 32 01 20

NCI << 40 02 02 00 00

NCI >> 21 03 0d 06 00 01 02 01 01 01 06 01 80 01 81 01

NCI << 41 03 01 00

WAITING FOR DEVICE DISCOVERY

NCI << 61 05 1d 01 02 04 00 ff 01 0c 44 03 07 04 32 75 02 0b 59 80 01 20 00 00 00 06 05 75 77 81 ...

 - POLL MODE: Remote T4T activated

          SENS_RES = 0x44 0x3

          NFCID = 4 32 75 2 b 59 80

          SEL_RES = 0x20

NCI >> 00 00 0d 00 a4 04 00 07 d2 76 00 00 85 01 01 00

NCI << 60 06 03 01 00 01

NCI << 00 00 26 6f 22 85 20 d6 2c 77 ab f1 aa 04 f0 16 33 55 e9 cc ad 4f 35 02 89 b9 8a b4 85 a3 ...

NCI >> 00 00 07 00 a4 00 0c 02 e1 03

NCI << 60 06 03 01 00 01

NCI << 00 00 02 6a 86

NCI >> 21 06 01 01 Deactivate

NCI << 41 06 01 00 Break Out Card Processing?

NCI << 61 06 02 01 00

NCI >> 21 04 03 01 04 02 Waiting For A Notification From The Peer Device

NCI << 41 04 01 00

NCI << 61 05 1d 01 02 04 00 ff 01 0c 44 03 07 04 32 75 02 0b 59 80 01 20 00 00 00 06 05 75 77 81 ...

NCI >> 00 00 0d 00 a4 04 00 07 d2 76 00 00 85 01 01 00

NCI << 60 06 03 01 00 01

NCI << 00 00 26 6f 22 85 20 09 40 6a d0 ce 79 26 7f ae 86 5b 70 64 a2 27 fc 6e e7 9a bf d1 75 c0 ...

NCI >> 00 00 07 00 a4 00 0c 02 e1 03

NCI << 60 06 03 01 00 01

NCI << 00 00 02 6a 86

NCI >> 2f 11 00 Repeat

NCI << 4f 11 01 00 Repeat

NCI << 6f 11 01 01 Repeat

NCI >> 2f 11 00 Repeat

NCI << 4f 11 01 00 Repeat

CARD REMOVED

NCI >> 21 06 01 00

NCI << 41 06 01 00

NCI << 60 08 02 b2 00

NCI >> 21 03 0d 06 00 01 02 01 01 01 06 01 80 01 81 01

NCI << 61 06 02 00 00

WAITING FOR DEVICE DISCOVERY

NCI << 41 03 01 00

[nxf58474]

Hi Leon,

Hope you are doing well. I replicated your situation, and it happens because the MIFARE DESFire EV2 is not in NDEF format.

From your log,

 - POLL MODE: Remote T4T activated

        SENS_RES = 0x44 0x3

        NFCID = 4 46 68 62 6e 4d 80

        SEL_RES = 0x20

NCI >> 00 00 0d 00 a4 04 00 07 d2 76 00 00 85 01 01 00

NCI << 60 06 03 01 00 01

NCI << 00 00 26 6f 22 85 20 de e8 c5 ab eb df 81 ff eb b5 30 fb f9 5d 5e 5d d9 a8 60 68 36 c1 1d …

NCI >> 00 00 07 00 a4 00 0c 02 e1 03 // Select the CC File

NCI << 60 06 03 01 00 01

NCI << 00 00 02 6a 86 // CC File not found

Generally a T4T like DESFire, doesn't have a segmented memory structure. You generate applications and inside the applications, you generate files. So if in the Tag is an application with the same name, maybe is not in NDEF format, or even is no one with the same name.

If you have an Android phone with NFC, you can format your DESFire with the NFC TagWriter by NXP, so you can correctly read your custom information.

In the App, you need to select the Erase tags option, and then Erase and Format to NDEF.

Hope this helps.

Regards,

Ricardo

[leon_su]

Hi  Ricardo

Thanks for your message.

I hope to use PN7150 to read the Mifare Desfire card, so I used the PN7150 example(NXPNCI-K64F_example) to test this.

At present, it seems that the example does not support this function. Can you please tell me how to read the Mifare Desfire card with the PN7150?

P.S I use is standard Mifare Desfire card

Thanks in advance
Leon

[nxf58474]

Hi Leon,

I used the same example NXPNCI-K64F_example for the test. You can read a MIFARE DESFire, but only if it is in NDEF Format. If you want to read DESFire that it's not in an NDEF format, the current examples can't handle it, for that case the implementation should be done by every customer.

Regards,

Ricardo