Functions used for card (or tag) data manipulation, such as obtaining some info, reading or writing data into card.
More...
|
| | General purpose card related commands |
| | Functions for getting common card data, not specific to card type.
|
| |
| | Java Card Application (JCApp) specific commands |
| | "Java Card" refers to a contactless or dual interface Java Cards. For now, we have supported two JCApps in our uFR Series NFC API. Those JCApps are DLSigner and DLStorage.
|
| |
| | Mifare Classic specific commands |
| | Functions specific to Mifare Classic® family of cards (Classic 1K and 4K). All functions are dedicated for use with Mifare Classic® cards. However, some functions can be used with other card types, mostly in cases of direct addressing scheme. E.g BlockReadM(), BlockWriteM(), LinearReadM(), LinearWriteM() can be used also with the NTAG2XX tags.
|
| |
| | Mifare DESFire Light specific commands |
| | Functions specific to Mifare DESFire® Light cards.
|
| |
| | Mifare DESFire specific commands |
| | Functions specific to Mifare DESFire® cards. All uFR Series readers support DESfire set of commands in AES encryption mode according to manufacturer's recommendations. In addition to AES, support for DES/2K3DES/3K3DES included.
|
| |
| | Mifare Plus specific commands |
| | Functions specific to Mifare Plus cards.
|
| |
| | NDEF related commands |
| | Functions for reading and writing common NDEF messages and records into various NFC tags. Currently, only NFC Type 2 Tags are supported, while support for other NFC Tag types will be added in future upgrades.
|
| |
| | NT4H (Type 4) specific commands |
| | Functions specific to NT4H (Type 4) chips (e.g NTAG424DNA, with TagTamper support)
|
| |
| | NTAG2XX (Type 2) related commands |
| | Functions specific to NTAG® family chips such as NTAG 203, 210, 212, 213, 215, 216. Due to the different memory sizes of various NTAG chips, we implemented functions for handling NTAG chips as generic NFC Type 2 Tag.
|
| |
| | Support for specific card features |
| | This is a group for specific card features (Originality checking, MRTD, EMV etc...)
|
| |
| | Ultralight C specific commands |
| | Functions specific to Ultralight C cards.
|
| |
|
| UFR_STATUS DL_API | GetMobileAdditionalDataM (UFR_HANDLE hndUFR, uint8_t data[32], uint32_t *len) |
| | Multi reader support. Function returns “mobile additional” data if the tag in the reader field is actually the selected HCE application in a mobile phone with the appropriate AID which can be set using the SetMobileUniqueIdAid() API. The indication that the HCE application in the mobile phone with the corresponding AID is actually selected is the card type code 0x60 (DL_MOBILE_AID) obtained by the previous call to the GetDlogicCardType() or GetCardIdEx() API.
|
| |
Functions used for card (or tag) data manipulation, such as obtaining some info, reading or writing data into card.
◆ GetMobileAdditionalDataM()
Multi reader support. Function returns “mobile additional” data if the tag in the reader field is actually the selected HCE application in a mobile phone with the appropriate AID which can be set using the SetMobileUniqueIdAid() API. The indication that the HCE application in the mobile phone with the corresponding AID is actually selected is the card type code 0x60 (DL_MOBILE_AID) obtained by the previous call to the GetDlogicCardType() or GetCardIdEx() API.
- Parameters
-
| hndUFR | handle of the uFR device |
| data | Array of bytes that should have at least 32 bytes previously allocated. |
| len | Pointer to the variable containing actual size of the data array before calling this function and after the successful execution contains size of the data returned by the reader (max. 32 bytes) |
- Returns
- Operation status
