Hi,
...
Can you send output on the formatting failures due to driver transactions ? I'm assuming you wrote
a reader driver for pcscd ?
Here is the output of pcscd when try to format using muscleTool:
winscard.c:123:SCardConnect() Attempting Connect to Hitachi M-520U 00 00 using protocol: 3
winscard.c:228:SCardConnect() Active Protocol: unknown 0
winscard.c:238:SCardConnect() hCard Identity: 16f45
winscard_msg.c:263:SHMProcessEventsContext() correctly processed client: 7
winscard_msg.c:263:SHMProcessEventsContext() correctly processed client: 7
winscard.c:1375:SCardTransmit() Send Protocol: T=4
^^^^^^^^^^^^^^^^^^^
ifdwrapper.c:595:IFDControl_v2() Card not transacted: 612
winscard.c:1402:SCardTransmit() Card not transacted: -2146435050
winscard_msg.c:263:SHMProcessEventsContext() correctly processed client: 7
winscard.c:1375:SCardTransmit() Send Protocol: T=4
^^^^^^^^^^^^^^^^^^^
ifdwrapper.c:595:IFDControl_v2() Card not transacted: 612
winscard.c:1402:SCardTransmit() Card not transacted: -2146435050
winscard_msg.c:263:SHMProcessEventsContext() correctly processed client: 7
winscard.c:620:SCardDisconnect() Active Contexts: 1
winscard.c:679:SCardDisconnect() Reset complete.
The "Send Protocol: T=4" looks particularly suspicious.
muscleTools says only:
Formatting token [****] : Failed (Internal Error)
My own debug logs show:
pcscd: ifdhandler.c 216 IFDHControl: Lun 0 TxLength 11 Rx Length 264, hexdump follows pcscd: 0000: 00 a4 04 00 06 a0 00 00 00 01 01 pcscd: ifdhandler.c 216 IFDHControl: Lun 0 TxLength 45 Rx Length 264, hexdump follows pcscd: 0000: b0 2a 00 00 28 08 2c 15 e5 26 e9 3e 8a 19 04 01 pcscd: 0010: 04 31 32 33 34 04 31 32 33 34 03 02 04 31 32 33 pcscd: 0020: 34 04 31 32 33 34 00 00 08 00 00 02 01
just before it fails. IFDHControl is said to be optional so I just set RxLength to zero and return IFD_COMMUNICATION_ERROR.
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
