See: "00 00 D6 00 02 FF" FF implies a Data length of 255.
The rest of the data after that is in fact 245 Bytes long (not 255). This causes my higher level code to generate an array out of bounds exception. I.e. the LC field says the data should be longer than it is. As the data ends in 90 00, I'm beginning to suspect the phone as the culprit! On 14 May 2013 21:22, Ludovic Rousseau <[email protected]> wrote: > 2013/5/14 Sam Duke <[email protected]>: > > Retrying due to log being too large (download link here: > > http://www.sendspace.com/file/ndqiyv) > > > > > > On 14 May 2013 18:29, Sam Duke <[email protected]> wrote: > >> > >> > >> > >> On 14 May 2013 17:25, Ludovic Rousseau <[email protected]> > wrote: > >>> > >>> > >>> Are you using my CCID driver? > >> > >> Unknown. I've seen this acronym around. I know LibNFC is configured with > >> the acr122_pcsc driver. Apologies for my lack of knowledge - I don't > even > >> know what to Google for (i.e. I don't know what I don't know!). This is > >> below my knowledge. I'll be happy to provide any outputs you need. > >>> > >>> > >>> Can you follow http://pcsclite.alioth.debian.org/ccid.html#support ? > >> > >> CCID driver version - Unknown (see above) > >> pcsc-lite version - PC/SC lite version: 1.8.6 > >> smart card reader name - ACR122u > >> the output of the command "/usr/sbin/pcscd --version" -provided before > >> > >> Operating system or GNU/Linux distribution name and version - Linux > ubuntu > >> 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:19:42 UTC 2013 i686 i686 > i686 > >> GNU/Linux > >> Smart card middleware name and version - LibNFC? 1.6 release candidate > (an > >> old version) > >> Reader manufacturer name and reader model name - ACS ACR122u-A2 > >> Smart card name - N/A > >> > >> Generated Log attached (I believe the issue is here: "00000062 Control > >> RxBuffer:"). I notice the data ends with 90 00 and is in fact 249 bytes > >> long. > >> > > I don't see a problem (or error) with that command: > > 00000005 ifdhandler.c:1359:IFDHControl() ControlCode: 0x42000001, > usb:072f/2200:libudev:0:/dev/bus/usb/002/011 (lun: 0) > 00000004 Control TxBuffer: FF 00 00 00 02 D4 86 > 00000009 -> 000000 6B 07 00 00 00 00 81 00 00 00 FF 00 00 00 02 D4 86 > 00100617 <- 000000 83 F9 00 00 00 00 81 02 81 00 D5 87 00 00 D6 00 02 > FF C4 27 00 00 01 53 63 6F 6D 2E 65 78 61 6D 70 6C 65 2E 73 75 70 65 > 72 6D 61 72 6B 65 74 61 70 70 3A 6E 64 65 66 74 72 61 6E 73 66 65 72 > 04 AC ED 00 05 73 72 00 11 6A 61 76 61 2E 6C 61 6E 67 2E 49 6E 74 65 > 67 65 72 12 E2 A0 A4 F7 81 87 38 02 00 01 49 00 05 76 61 6C 75 65 78 > 72 00 10 6A 61 76 61 2E 6C 61 6E 67 2E 4E 75 6D 62 65 72 86 AC 95 1D > 0B 94 E0 8B 02 00 00 78 70 00 00 00 00 AC ED 00 05 73 72 00 1D 63 6F > 6D 2E 73 75 70 65 72 6D 61 72 6B 65 74 2E 73 68 61 72 65 64 2E 42 61 > 73 6B 65 74 7B 3F 30 EC AD C8 6B 3D 02 00 01 4C 00 05 69 74 65 6D 73 > 74 00 15 4C 6A 61 76 61 2F 75 74 69 6C 2F 41 72 72 61 79 4C 69 73 74 > 3B 78 70 73 72 00 13 6A 61 76 61 2E 75 74 69 6C 2E 41 72 72 61 79 4C > 69 73 74 78 81 D2 1D 99 C7 61 90 00 > 00000062 Control RxBuffer: D5 87 00 00 D6 00 02 FF C4 27 00 00 01 53 > 63 6F 6D 2E 65 78 61 6D 70 6C 65 2E 73 75 70 65 72 6D 61 72 6B 65 74 > 61 70 70 3A 6E 64 65 66 74 72 61 6E 73 66 65 72 04 AC ED 00 05 73 72 > 00 11 6A 61 76 61 2E 6C 61 6E 67 2E 49 6E 74 65 67 65 72 12 E2 A0 A4 > F7 81 87 38 02 00 01 49 00 05 76 61 6C 75 65 78 72 00 10 6A 61 76 61 > 2E 6C 61 6E 67 2E 4E 75 6D 62 65 72 86 AC 95 1D 0B 94 E0 8B 02 00 00 > 78 70 00 00 00 00 AC ED 00 05 73 72 00 1D 63 6F 6D 2E 73 75 70 65 72 > 6D 61 72 6B 65 74 2E 73 68 61 72 65 64 2E 42 61 73 6B 65 74 7B 3F 30 > EC AD C8 6B 3D 02 00 01 4C 00 05 69 74 65 6D 73 74 00 15 4C 6A 61 76 > 61 2F 75 74 69 6C 2F 41 72 72 61 79 4C 69 73 74 3B 78 70 73 72 00 13 > 6A 61 76 61 2E 75 74 69 6C 2E 41 72 72 61 79 4C 69 73 74 78 81 D2 1D > 99 C7 61 90 00 > > > I did not find any error message in the trace you sent. > > I don't know why you think something is wrong. > > >>> Have you read the notes at > >>> http://pcsclite.alioth.debian.org/ccid/unsupported.html#0x072F0x2200 ? > >> > >> I've just looked. I'm aware of the limitations with timeouts but I dont > >> know what the Extended APDU features are. > > See http://pcsclite.alioth.debian.org/ccid_extended_apdu.html > > Bye > > -- > Dr. Ludovic Rousseau > > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com >
_______________________________________________ Muscle mailing list [email protected] http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
