apdu

I have found in docs they are referring to SIMPLE-TLV and BER-TLV . I was look into most of the EMV and GP docs but they have not mentioned the different. Could anyone help me to understand the difference of two ? Data fields in ISO/IEC 7816-4 for smart cards BER encoding This is the specification of the more common BER encoding used by ISO/IEC 7816-4: Each BER-TLV data object shall consists of 2 or 3 consecutive fields (see ISO/IEC 8825 and annex D). The tag field T consists of one or more consecutive bytes. It encodes a class, a type and a number. The length field consists of one or more

I am writing an application for read the mifare card,but when I pass the APDU the error occur that on emulator "java.lang.nullpointerexception".I have successfully detect the ISO14443_CARD after that I pass the APDU like if (tp.hasTargetType(TargetType.ISO14443_CARD)){ form.append("Target is ISO14443_CARD\n"); try { static byte[] APDU_AUTH1 = { (byte) 0xff, (byte) 0x86, (byte) 0x00, (byte) 0x00, (byte) 0x05,(byte)0x01,(byte)0x00,(byte)0xfc,(byte)0x60,(byte)0x00}; static byte[] STATUS_BYTE = {(byte)0x90,(byte)0x00}; if(STATUS_BYTE == iso14443.exchangeData(APDU_LOAD_KEY)) { String value1 = new

I can't find anywhere a valid APDU list for SLE5542 smartcard. Actually I found this: http://www.acs.com.hk/drivers/eng/PMA_ACR38x(CCID)_v6.01.pdf but it's not working. I've searched also for SLE4442 which is compatible, I've searched some standardization, but nothing. (I found some comprehensive datasheets about SLE4442 but they don't contain APDU data) I'm novice in this domain, so maybe I'm missing something. In the end I want to be able to read/write some data to the card. (including Programmable Security Code PSC Verfication) guidot The SLE5528 and 4428 are no SMARTcards, just dumb

What APDU command gets 7 byte of card ID? I use T=CL (ISO7816) pritocol with ISO14443 layer. On detect card I can see only 4 byte of card ID. I searched, that is APDU command for gets card ID. For example its: 0xFF, 0xCA, 0x00, 0x00, 0x00 but result of thouse command is: 6E 00 , that on specifications of APDU answers tell that "Class not supported" Then I find, that its APDU command may be as: 0x00, 0xCA, 0x00, 0x00, 0x00 this command return 6A 88 where 6A XX - "Wrong parameter(s) P1-P2" and 88 - "Referenced data not found" What you think about it? Thank you! p.s. All command as: CLA, INS, P1,

I am working on an Application using the IsoDep Tag Tech to issue APDU commands to an NFC enabled card. UPDATE: So the issues seen below seem related to the power requirements of the cards I am using, when I use a different card with lower power requirements the below symptoms don't occur as frequently. I have followed the documentation explicitly and have a successful managed to implement the protocol. However with mixed success I am experiencing some issues with the NFC lower level libraries beyond the control of my code. I have implemented the following: Foreground dispatching of a Pending

I'm developing with the Open Mobile API but so far haven't found a list of devices that support the API by default (by default being using the OEM ROM). I realise that since API level 21, Android telephony supports sending APDUs via basic and logical channels dirctly through the TelephonyManager. But I'd like to know about devices running pre-API level 21 too. So, has a list already been compiled of devices with built-in support or is there a way to find out for myself? I'm not aware of any complete list. However, there is a not so comprehensive one in our report Open Mobile API: Accessing the

I'm using the SMARTCARD API from CardWerk. How can I change the default key ( (byte)0xFF, (byte)0xFF, (byte)0xFF, (byte)0xFF, (byte)0xFF, (byte)0xFF ) using an APDU? The APDU consits of a CLASS, an INSTRUCTION, P1, P2. I have been reading documentation but I'm unable to find what parameters do I need to change the actual key to a new one. The process for changing the keys of a MIFARE Classic card is like this: Authenticate to the secor for which you want to change the key. Read the sector trailer using normal read operation (or generate a new sector trailer containing the access bytes you want

I'm trying to use an ACR122 NFC reader to select an application emulated in one Nexus 5 using Android Host Card Emulation. However, small AIDs are not recognized. My goal is to use a three byte long AID, as I do in a DESfire card. My first goal is only to be able to do a SELECT command. My test app uses the following configuration for AIDs: <host-apdu-service xmlns:android="http://schemas.android.com/apk/res/android" android:description="@string/service_descr" android:requireDeviceUnlock="false" > <aid-group android:category="other" android:description="@string/aid_descr" > <aid-filter android

I'm trying to emulate an NFC tag with my Nexus 5 according to this document , but my service is never invoke. Should I turn off Android beam? I'd like to emulate a simple tag containing a url. The reader is a Nexus 7 (2012) and I've figured out the process like a simple scan of a NFC tag using Android beam on Nexus 7. In addition I'm a bit confused about aid-filter name. Is there a list of them? I'm sure that I don't understand something. Thanks First of all (though this does not directly answer your question), the preferred way to transfer a URL between two Android NFC device is to use