How MIFARE Uses Cookies

[mifaresdk]

Hello Implicete1796,
Yes, single file access is the limitation with the LITE version of MIFARE SDK. But we are working on Advanced version SDK which will be released soon. Please bear with us.


Thank you.

---

+ 0  |  - 0

[mifaresdk]

Hi,
Below are the steps to create application and writing and reading from it for factory default card.

public void onDESFIRECardDetected(final DESFire objDesfire) {
NxpLogUtils.i(TAG, "Desfire Card Detected!!");
desfire = objDesfire;
/* Insert your logic here by commenting the function call below. */
// New Card Master Key.
byte[] cardKey = new byte[] { 0x11, 0x11, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 };
// New Application Key.
byte[] appKey = new byte[] { 0x22, 0x22, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 };

// Application ID.
byte[] appID = new byte[] { 0x12, 0x12, 0x12 };
// Data to write.
byte[] data = new byte[] { 0x11, 0x11, 0x11, 0x11, 0x11, 0x11, 0x11,
0x11 };
try {
objDesfire.connect();
objDesfire.setTimeOut(2000);
// Only Use First personalize API, for subsequent use with the same card replace
// personalize with authenticate API.
objDesfire.personalize(cardKey, appID, appKey);
objDesfire.write(data);
byte[] Readdata = objDesfire.read(5);
objDesfire.close();
} catch (Exception t) {
showMessage("Unknown Error Tap Again!", 't');
}

}

Note: please refer sample application code for further information.
Regards,
MIFARE SDK Team

---

+ 0  |  - 0

[mifaresdk]

Hi,
Before using any DESFire Lite API please follow the following steps. for these steps to work, you should have either factory default card ( New card where card master key is set to all zeros and key is of type 3DES.) OR you must know the Card Master Key and it must be of type AES.

1) Use format API of the DESFire class, this API erases all the data in the card. [ this Step is not required if you have factory default card. ]

2) Use personalize API of the DESFire class, this creates default application with std file in it for reading and writing. And changes the card master key to AES type.This API should be used once for each new card. OR this should be used after formatting the card.

3) After personalize you can able to read and write to the new card. For future reading and writing with the already personalized card, please authenticate the card before reading and writing.

For Factory default card.
a) Personalize --> Read/Write.
b) authenticate --> Read/Write.

For Personalizing again with different APP Id and key.
a) format --> personalize --> Read/Write.

NOTE: Lite SDK Limitations:
1) you cant use the card personalized with different application.
2) you dont have control on creating multiple applications and files.
Regards,
MIFARE SDK Team

---

+ 0  |  - 0

[mifaresdk]

Hi fsurleau,
No, MIFARE SDK does not emulate any card, as of now MIFARE SDK is meant to communicate with NXP cards.

Regards,
Team

---

+ 0  |  - 0

[mifaresdk]

Hi dwainealingarog,
Thanks for the suggestion , currently there is no way to get the APDU command from the SDK.

Regards,
Team

---

+ 0  |  - 0

[mifaresdk]

Hi Akash,

Please visit www.nxp-rfid.com for more information of NTAG product, and please see the java document available with Lite SDK for more information about the concerned APIs.

Regards,
Team

---

+ 0  |  - 0

[mifaresdk]

Hi JulianRa,
In the Lite version of the MIFARE SDK library [ nxpnfcliblite.jar] we are not providing access to the keystore APIs, the manual that your referring describes the sample code of the Full version of MIFARE SDK. So while using Lite SDK please manage your keys in your application.

Thanks and Regards,
Team
MIFARE SDK

---

+ 0  |  - 0

[mifaresdk]

Hi ckchan47,

We are curious to know why it crashes on Note 3. For DEsfire card usage, having non-nxp controller phone will not be an issue. Could you please share with us the crash log so that we could check? Thank you.

---

+ 0  |  - 0

[mifaresdk]

Hello sathishs,
Set password is not applicable to DesFire cards. If you are referring to changing the key of the card, then please use updatePICCMasterKey() or updateApplicationMasterKey() API. Let us know if you still have any problems.

Thank you.

---

+ 0  |  - 0

[mifaresdk]

Hello thezed,
Please confirm if you are able to download the SDK. Nobody has reported any problems so far.

Thank you.

---

+ 0  |  - 0

[mifaresdk]

Mifare 1K may not be supported in non-NXP controller based devices. As you rightly mentioned, there is no such limitation with NTAG2xx series.

---

+ 0  |  - 0

[mifaresdk]

Thank you for the patience. We shall be releasing it in couple of weeks.

---

+ 0  |  - 0

[mifaresdk]

As of now, we are restricting the applications developed using MIFARE SDK to run on rooted devices. We might allow it in future but not at present.

We are sorry for the inconvenience caused, if any.

Thank you.

---

+ 0  |  - 0

[mifaresdk]

Thank you Maruthi Konda for answering chintanrathod's query.

Hi chintanrathod,

Factory default card can definitely[/b] be used with LITE SDK provided it is personalized using LITE SDK's personalize API. Otherwise, it is not allowed.

But our advanced version SDK will definitely help you in this scenario where you are free to personalize the way you want and use/read contents if you know the keys, app id and file id.

Advanced version will be announced soon.

---

+ 0  |  - 0

[mifaresdk]

Hi Joel,
This feature is not supported in Lite SDK even though it is free read area. You will need to wait for the advanced version.

Thank you.

---

+ 0  |  - 0

[Author]

Posts