-
compiling with the latest PN532 Lib gives me the following error
no matching function for call to 'PN532::readPassiveTargetID
-
In mifare_desfire.c line 574 reads
*max_keys = p[1] & 0x0F;
The masking discards the encryption type indicated in the top two bits by an EV1 card.
Rewriting the line as
*max_keys =…
-
```
Reported by emanuele.bertoldi, Apr 11, 2011
Currently, there are equivalent examples for MIFARE classic and desfire.
It would be great to add an example for MIFARE ultralight too.
```
Original i…
-
```
Reported by emanuele.bertoldi, Apr 11, 2011
Currently, there are equivalent examples for MIFARE classic and desfire.
It would be great to add an example for MIFARE ultralight too.
```
Original i…
-
I'm happy to help out reverse engineering this where necessary. Here's an initial dump of data from the card (via the NFC TagInfo app).
```
Type A (ISO/IEC 14443 Type A)
ISO/IEC 14443-4 Smart Card,
M…
-
```
4.23
2017-08-05 22:39:53
NXP Semiconductors MIFARE DESFire EV1 tag
04:2E:7B:1A:14:4D:80
false
NXP Semiconductors
MIFARE DESFire EV1
Mult…
-
Hi,
In my app I used nfc_initiator_transceive_bytes() (libnfc) function to read Desfire tag and building each APDU but in my tests, the reading that uses the read_data() (libfreefare) function is fas…
-
Dear,
we have been running DESFIRE test from tests, testing all the commmands and somewhere we created some error on the card.
Now the key version returns C0, which is unknown. 2 Cards are havin…
-
_NXP MIFARE DESFIRE tags are encrypted by default (DES, 2K3DES, 3K3DES and AES) to secure transmission data._
When I write to an tag `(command : nfc.write)` , nothing can make my data invisible to …
-
Read write mifare desfire cards, or iso14443 type a cards, send receive apdu commands
As you know android support read write
iOS only support read currently, as far as I know