How MIFARE Uses Cookies

[mifaresdk]

Dear Sandor,

Yes, the MIFARE SDK is replaced by the TapLinx SDK. You can still use it, but the development has terminated.

The problem of supporting a SAM AV2 is the contact interface. Some phones has a separate SIM card slot, but the most don’t. If you use a contact reader connected via USB cable, you have to use the driver of the reader and every manufacturer provide its own driver. There is no standard interface for a SIM card on an Android system and this is the reason why you cannot support the SAM within from TapLinx on the phone.

I know, that the HID Omnikey 6121 Reader was supported by the MIFARE SDK. But the 6121 is not continued and the support has stopped. I have to check, if the 6121 is supported as hardware key store in the last release of the MIFARE SDK.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[mifaresdk]

Hi Narendc,

As a recommendation from my side: you have full access to the DESFire with the native commands. For cyclic record files there are special commands:
CreateCyclicRecordFile(),
WriteRecord(),
ReadRecords(),
ClearRecordFile()
and
CommitTransaction(),
AbortTransaction().

Regards,
The TapLinx Team

---

+ 0  |  - 0

[mifaresdk]

Hi Sandor,

Then you should start with TapLinx. But take in mind, the SAM AV2 is not supported by default. You have to implement the SAM interface and this depends on the driver of the contact interface.

Regards,
The TapLinx Team

---

+ 0  |  - 0

[mifaresdk]

Hi Arrowpass,

I will hand over your problem to the development team, but a short error log is not sufficient to understand what is going wrong. Please tell me the call method and arguments, the Android version and the model you use.

You can use this mail address for a direct feedback: mifaresdk@nxp.com

Regards,
The TapLinx Team

---

+ 0  |  - 0

[mifaresdk]

Hi Ali,

Please have a look at this post:

questions on MIFARE4MOBILE

Kind regards,
The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Arrowpass,

Did you see this post:

Trying to read DESFire EV1 Card, requires Authentication

It is working example of reading the MIFARE DESFire EV1 (without a null pointer exception).

Kind regards,
The MIFARE Team

---

+ 0  |  - 1

[mifaresdk]

Hi Libin,

Any phone with NXP PN547/PN548 is able to manage several MIFARE virtual cards (Classic and DESFire EV1). The point here is that you cannot use it out-of-box. The access to the SE is not allowed with a default Android OS. To use the SE, you have modify the Android Sources and flash your phone with this software. This requires always a “rooting” of your device.

Kind regards,
The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Arrowpass,

It seems the bug is bad using of the read method. Please check one of the detailed DESFire read/write examples of this forum.

Kind regards,
The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Avner,

Sorry, but explain how to get certificates for the production of own NFC products is beyond my capabilities. You are sure to manufacture NFC products instead of buying such products and personalize them?

Regards,
The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Onyekachi,

We will continue the support. But the final destination is not released yet. I expect that this site will be integrated into the new support site.

The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Dear Sandor,

Yes, we are in the process for releasing TapLinx now. You can expect the release in the next two weeks.

The architecture has changed. This means that you cannot change to TapLinx without code modifications. But the changes are moderate. The name and the meaning of most of the classes are the same.

The Advanced SDK contains an own keystore. This keystore does not exist in TapLinx anymore. You are free to use the crypto provider you want. The sample app, which comes with the SDK, uses Bouncy Castle as provider.

You are using the MIFARE SAM AV2. It might be interesting to know that you can use the SAM, if it is integrated in your system and you are able to initialize a Java key class from the SAM (javax.crypto.SecretKey it is used in TapLinx as key reference). Please take in mind, that there is no standard API to communicate with the SAM, therefore it cannot be integrated in the TapLinx SDK.

Regards,
The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Narendc,

The frame size for one APDU is limited to maximum 64 bytes in DESFire EV1. There is no possibility to increase this framesize. When subtracting the 4 bytes which are needed for ISO/IEC 14443-4, actually only 60 bytes can be used for one native DESFire EV1 command APDU. When using one of the ISO/IEC 7816-4 standard commands which are supported by DESFire EV1 (like Cmd.ISOReadBinary) additionally ISO 7816-4 bytes need to be included into the APDU. The needed bytes are: CLA, INS, P1, P2, Lc and Le. The INS byte reflects the native DESFire EV1 command code and the data section actually holds the command header and the command data.

Your conclusion of being able to write only 55 data bytes at a time when using ISO/IEC 7816-4 APDUs is correct. In one command frame you are limited to this size. If you want to send more data at once, you need to implement a so-called chaining mechanism which basically connects multiple command-response pairs. The ISO chaining mechanism according to ISO/IEC 14443-4 can be implemented in order to send/read larger chunks of data at once (by using multiple challenge-response pairs automatically).

The DESFire EV1 allows the creation of 28 applications (PICC = AID using 0x000000 is not included in counting). The reason that you were not able to create more applications could be the configuration of your applications – can you check how much memory is still available on the card? If you created each application with support of multiple keys it could be that you ran out of memory. If the maximum number of applications is reached and you try to create the 29th one, you get the error code 0xCE (count error) returned, which signalized that the application limit has been reached.

Regards,
The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Justin,

You refer to the NxpRdLib, right?

The team here are not the developers of the library, sorry.

The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Federico and Gabriel,

You can use the DESFire EV1 in your projects with the Lite and the Advanced edition. But it is true, in the Lite SDK it has classes from the Advanced SDK merged which cannot be used. I regret this design decision.

As you probably know we are in the process of releasing the modified Android SDK called TapLinX. Therefore we offer the MIFARE SDK Advanced for interested users until TapLinX is finally released.

The MIFARE Team

---

+ 0  |  - 0

[mifaresdk]

Hi Onyekachi,

Yes, you can set the count to any value, but you never can set a bit to 0 again if it was 1 before. Please take in mind, the counter is in function a “bit counter”.

For instance, you allow a user the usage of five times to use the ticket. Then you will set the counter to the initial value “11111…11100000”. At every usage you will set a “0” to “1”. If the OTP counter is “11111…111”, it cannot be used again.

Regards,
The MIFARE Team

---

+ 0  |  - 0

[Author]

Posts