mifare

Currently we are developing NFC applications for Android. 　Our experience Developed POS NFC control system using NXP PN5xx chips for control of Mifare Classic (1K) and CEPAS standard Developed Android NFC control system for MiFareClassic and Ultralight C in Galaxy Nexus (using NXP NFC chipset) Developed Android NFC control system for Ultralight C in Nexus 4 Our challenge: we want to control MiFareClassic 1K card in our POS machine (with NXP chip) and in new Android tablets (with Broadcom chip), we already have the installed card base and can not replace them. 　-　We know Nexus 4 has　changed the

Is there any way to distinguish a NTAG213 from a MF0ICU2 tag based on its UID, ATQA or SAK values? As I have to program the tags differently (PWD/PACK for NTAG213 or 3DES for MF0ICU2) there must be a way to call either one or another method. Unfortunately, the Android framework tells me that both tags are MifareUltralight with type TYPE_ULTRALIGHT_C . The ATQA ( 0x0044 ) and SAK ( 0x00 ) are identical, too. Other apps like NFC TagInfo by NXP can tell me the exact type of a tag, so I know that there must be some way. Once you know that the tag is an NXP tag (UID starts with 0x04), you would

I am working on an app that scans just the UID of MIFARE Classic cards to facilitate attendance registration. I have got it working. However, every time I scan a card on my Galaxy S4, I get a toast stating "NFC tag type not supported". I want to either block or hide that message while the app is open. I noticed there was one other question asking for the same thing on a Galaxy S6 but it was down-voted once and then ignored. I found this conversation on the Samsung Developers forum, however, I could not extract an answer from what is written there: if (NfcAdapter.ACTION_TECH_DISCOVERED.equals

Say I want to authenticate to Mifare Classic. How do I know the exact kind of APDU to send to the card? Example. This code: bcla = 0xFF; bins = 0x86; bp1 = 0x0; bp2 = 0x0; // currentBlock len = 0x5; sendBuffer[0] = bcla; sendBuffer[1] = bins; sendBuffer[2] = bp1; sendBuffer[3] = bp2; sendBuffer[4] = len; sendBuffer[5] = 0x1; // Version sendBuffer[6] = 0x0; // Address MSB sendBuffer[7] = currentBlock; if(keyradioButton->Checked==true) // Address LSB sendBuffer[8] = 0x60; // Key Type A else if(keynumberradioButton->Checked ==true) sendBuffer[8] = 0x61; // Key Type B sendBuffer[9] = keynumber; //

I have experience in java cards, but new in programming host application for Desfire, How or Where can I find command set description of Desfire? (I do not need general information like what NXP has mentioned in It's "Product short data sheet"s), I need the commands Instruction code and parameter details and responses (Like APDU or something). thanks. I am having exact same trouble as you. The closest thing to documentation of the commands is a blog post that shows a couple of examples of what the desfire communication looks like. http://ridrix.wordpress.com/2009/09/19/mifare-desfire

I have mistakenly overwritten sector 1 block 7 of one of my Mifare classic 1k tags. It was meant for testing and the 16 byte data that I wrote on block 7 is shown below: 0xaa 0xaa 0xaa 0xaa 0xbb 0xbb 0xbb 0xbb 0xcc 0xcc 0xcc 0xcc 0xdd 0xdd 0xdd 0xdd If not mistaken, by doing so, my access keys and permission bits have become as following: Key-A: 0xaa 0xaa 0xaa 0xaa 0xbb 0xbb Key-B: 0xcc 0xcc 0xdd 0xdd 0xdd 0xdd Permisssion Bits: --> 0xbb 0xbb 0xcc I have tried to use Key-A and Key-B as shown above to read/write block 7 in sector 1 . But I am no longer able to access (no read or write) any