2012/5/26 Nguyễn Hồng Quân <[email protected]>: > Hi Ludovic, > > Here are 2 log files: > - Only pcscd on USB2.0 > - pcscd + libusb on USB3.0
Very nice logs. In the USB 3.0 case we have: - the command is sent to the reader/card - the reader/card send a first block of response - a request to send the next block is sent to the reader/card with a timeout of 13824ms - the timeout expires and libusb returns an timeout error - some hypothesis 1. the token did not receive the command 2. the token did not sent the answer 3. the answer got lost somewhere In the USB 2.0 case we have the same sequence but without a timeout. The reader/card send the second block 21,706ms after the command. Every thing looks normal at the CCID and libusb level. You should now activate and capture logs at the kernel level using usbmon [1]. But I can't help at this level. You really have to ask for help on the libusb mailing list. I am also on the libusb list (but not a USB expert). Also you can try using the very latest Linux kernel. Maybe your bug is already known and fixed. Bye [1] http://www.kernel.org/doc/Documentation/usb/usbmon.txt -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
