About the log at http://www.sendspace.com/file/ndqiyv
On 15/05/2013 14:02, Ludovic Rousseau wrote > 2013/5/15 Sam Duke <[email protected]>: >> The trace begins " 00000062 Control RxBuffer: D5 87 00 00 D6 00 02 FF" > It is part of the _response_ from the reader. It is not an APDU. Sam Duke is using an ACR122U in card emulation mode, using ScardControl. The emulated card receives a message from an initiator, that includes 1) a TgGetData response header D5 87 00, explained on page 160 of that public document on the NXP chip (or a similar one) used by the ACR122U http://www.nxp.com/documents/user_manual/141520.pdf 2) a Command APDU header CLA/INS/P1/P2/Lc, 00 D6 00 02 FF 3) some incomplete incoming data (there should be 255 bytes, there are 239) 4) 90 00, which is an artifact in all Control RxBuffer in the log. The truncation could be a) by the initiator of the APDU b) by NXP chip, but the public document quoted indicates that the size limit of of data block following the TgGetData response header is 262 bytes. c) the ACR122U firmware d) whatever chain is involved in the ScardControl Whatever adds the 90 00 is likely the cause of the truncation. My bets are on the ACR122U firmware. Francois Grieu _______________________________________________ Muscle mailing list [email protected] http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
