Forum Replies Created
-
Re: Reply To: DESFireEV1 Authentication error
2. January 2017 at 11:22 in reply to: DESFireEV1 Authentication errorHi Jesús,
You can configure the permission of each file. If you set the read permission to “free”, the file can be read without authentication. In your case you (probably) give as permission “0” (which means use card key number 0). You should set the permission to “0x0E” (which means free access).
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: Check Password Protection
2. January 2017 at 11:17 in reply to: Check Password ProtectionHi Dinesh,
Please refer to the data sheet:
http://www.nxp.com/documents/data_sheet/MF1S50YYX_V1.pdf
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: SAM Authentication using Taplinx Advanced Library
2. January 2017 at 11:15 in reply to: SAM Authentication using Taplinx Advanced LibraryHi Saravana,
Unfortunately the MIFARE SAM AV2 is currently NOT supported by TapLinx SDK. The reason is no standardized contact interface. TapLinx is a library for the Android user space. If you want to deal with the PN547 directly, you cannot use TapLinx.
The PN547 has separate slots to communicate with a contact card and the SAM is able to handle the authentication of a contactless card. Please refer the user manuals and application notes.
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: QT Development with DESfire EV1
2. January 2017 at 11:05 in reply to: QT Development with DESfire EV1Hi Dinesh,
Please have a look to the datasheet:
http://www.nxp.com/documents/data_sheet/MF1S50YYX_V1.pdf
You will see that the memory space is divided in sectors and blocks. Each sector has its own so called “sector trailer”. In the sector trailer the access permission including two passwords are set.
If someone has used a sector and protect this sector with one of the passwords, you can read or write only, if you know the password.
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: QT Development with DESfire EV1
28. December 2016 at 12:44 in reply to: QT Development with DESfire EV1Hi Mark,
ISO 7816-4 is the standard for contact cards. If you want to communicate with MIFARE products, you need to know the standard for contactless cards: ISO 14443.
The TapLinx Team
+ 0 | - 0
Re: Reply To: Minimum Android SDK Version
28. December 2016 at 12:40 in reply to: Minimum Android SDK VersionHi Jesús,
You are right, we did not published an “official” minimum version. As I know, the “absolute” minimum version is KitKat (Android 4.4). But all tests are running on Lollipop (Android 5) and Marshmallow (Android 6) devices.
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: Starting Development, Help with DESFire EV1 (Basics)
28. December 2016 at 12:36 in reply to: Starting Development, Help with DESFire EV1 (Basics)Hi drwxr,
It is always a good idea to have a look into the samples coming with the SDK. If you are familiar with Android programming and with the Android framework, you will understand the samples very easily.
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: Mutual Three Pass Authentication with TapLinx
28. December 2016 at 12:31 in reply to: Mutual Three Pass Authentication with TapLinxHi Jeong,
The TapLinx SDK is a convince library to make your life easier. But you are free to use the byte stream directly to communicate with the MIFARE product. In this case you have to implement the byte sequences directly, methods to check, if the taped card really is the card you expect.
Yes, the datasheet of the DESFire EV1 which explains the native commands is NDA protected. You can write to this forum (taplinx@nxp.com), I will hand over the request to the appropriate instance. Please take in mind, currently we have Christmas and New Year holiday and it takes some time to get a response.
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: What does registerActivity do?
28. December 2016 at 12:19 in reply to: What does registerActivity do?Francisco,
The TapLinx SDK sit on top of the NFC Android library. Your app has to declare to receive NFC intents and implement a callback method onNewIntent() which is used by Android to feed your app with any kind of intents. This is the Android architecture. You can love it or hate it, but you have to live with this architecture if you want to build Android apps.
TapLinx is a library layer inside of your app to process NFC data. All our examples shows to feed TapLinx directly in onNewIntent() and use the data stream in your application code. If you need the NFC data stream in several activities, I would use the Android inter-app-communication mechanisms to handover to the different endpoints. If this is not acceptable for you, you can try to implement several onNewIntent() methods in your app and use also several instances of TapLinx to handle the NFC data. But I am in doubt this is a good idea.
Anyway, all this has nothing to do with serious customer questions about TapLinx using pattern. I regard the matter as closed.
The TapLinx Team
+ 0 | - 0
Re: Reply To: Mutual Three Pass Authentication with TapLinx
27. December 2016 at 12:29 in reply to: Mutual Three Pass Authentication with TapLinxHi Jeong,
Currently TapLinx act as initiator in reader mode to authenticate to a MIFARE DESFire EV1/2. Therefore, the DESFire class needs a reference to a key object to fulfil the authentication.
If you want to allow an embedded MIFARE SAM AV2 on your phone to do the authentication, there must be a way to split the authenticate() to handover the single token to the SAM. This the case you described in your post. We are discussing to support the SAM in future releases. But in the current release it is NOT possible.
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: What does registerActivity do?
27. December 2016 at 12:15 in reply to: What does registerActivity do?Hi Francisco,
Yea, this is the better column for your question. Anyway, your questions seems unclear for me. We have tested TapLinx on various phones—without any problems.
As you can see in the example app and in the skeletons, enclosed with the AN, the library is initialized in onCreate() (like all other libraries would do it) and the library is located in the main activity, because only the main activity will receive NFC intents from Android. Of course, you can have more activities in your app, but only the main activity should be able to receive NFC intents. If you need processing of NFC data in other activities of your app, you should do it via separate threads or use other mechanisms of inter-app-communication.
I do not see any “design flaws” to locate the library instance in the main activity, when only the main activity will receive NFC intents from Android. The attempt to try to get NFC intents to multiple activities of the same app makes no sense for me, because this opens synchronization troubles and as I know, it is not supported by Android.
I will do my best to support you, but I do not have time to download customer code and start investigations on this code. Sorry.
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: Mifare Clasic 1K UID All 0 trouble
27. December 2016 at 11:31 in reply to: Mifare Clasic 1K UID All 0 troubleHi Naoki,
It seems that you have trouble with your reader device and the MIFARE Classic is not detected properly (the Classic send never a UID of zeros).
Kind regards,
The TapLinx Team
+ 0 | - 0
Re: Reply To: QT Development with DESfire EV1
27. December 2016 at 11:28 in reply to: QT Development with DESfire EV1Hi Mark,
I am very sorry, but this questions cannot be answered here in the forum.
You need more investigations about the architecture of the MIFARE DESFire EV1/2, about security mechanisms and algorithms and of the used readers. I recommend to start your investigations with the reader device ACR1252U. Download the user manual and check the available commands.
Kind regards,
The TapLinx Team
+ 1 | - 0
Re: Reply To: What is MIFARE Classic 1K Access Bits means? How to calculate and use it?
19. December 2016 at 9:15 in reply to: What is MIFARE Classic 1K Access Bits means? How to calculate and use it?Hi Onyekachi,
The both diagrams in the post shows the access condition bits for the data blocks and for the sector trailer. You go into the diagrams and select the best aligned condition for your application. Not all conditions are possible! For instance, if you need separate keys (a read key and a write key), only the lines with “read = key A or key B” and “write = key B” are possible. There exist no condition “read = key B only” and “write = key A only”!
For instance, if you decide C1 = 1, C2 = 1 and C3 = 0, all data blocks can be read with key A or B and can be written only with key B. This is a typical use-case where the terminal (which has key A) can read data and decrement account values. But to write or renew account values is only possible on a special terminal (which has key B).
With the definitions of C1, C2 and C3 you have to fill the appropriate bits in bytes 6, 7 and 8. Please have a look into the datasheet. There is a table “Access Conditions” where is shown how the bits of C1, C2 and C3 (inverted and not) are put into the bytes 6, 7, and 8. You have to use this table and you cannot arrange the bits in a different order!
The TapLinx Team
+ 0 | - 0
Re: Reply To: Documentation Desfire EV1
19. December 2016 at 8:43 in reply to: Documentation Desfire EV1Hi Teun,
The DocStore is the NXP platform for delivery restricted datasheets to customers. For getting all features of the MIFARE DESFire EV1/EV2 you need the DESfire Native Datasheet which is restricted under a NDA. If you mail to this platform, I will hand over your request.
The TapLinx Team
+ 2 | - 0
-
AuthorPosts
