Hi Ludovic, Thanks for your reply.
On Tue, Aug 31, 2010 at 09:25:12PM +0200, Ludovic Rousseau wrote: > 2010/8/31 Forest Bond <[email protected]>: > > The interesting thing is that I can get the reader to work properly (albeit > > slowly) by forcing pcscd to use the T=0 protocol with the following patch: > > > > -------------------------------------------------------------------------------- > > --- pcsc-lite-1.5.3.orig/src/prothandler.c > > +++ pcsc-lite-1.5.3/src/prothandler.c > > @@ -124,6 +124,9 @@ > > /* App wants unsupported protocol */ > > return SET_PROTOCOL_WRONG_ARGUMENT; > > > > + /* XXX */ > > + ucChosen = SCARD_PROTOCOL_T0; > > + > > Log2(PCSC_LOG_INFO, "Attempting PTS to T=%d", > > (SCARD_PROTOCOL_T0 == ucChosen ? 0 : 1)); > > rv = IFDSetPTS(rContext, ucChosen, 0x00, 0x00, 0x00, 0x00); > > -------------------------------------------------------------------------------- > > Your card is T=1 only. But the reader is APDU so it may work somewhat. > I guess the card is talking at the default speed of 9600 kbits/s > instead of 250 kbits/s. It is *very* slow. > > I have contacted Precise Biometrics and they have said that their reader > > has no > > problems with the T=1 protocol and that it passes the PC/SC test suites > > v1.0 and > > v2.0. > > > > Any ideas where the problem might be? > > Precise 200 MC firmware was bogus [2]. Maybe you have an "old" reader > with a bogus firmware. But the bug I reported was not the same as > yours. > > Can you follow [3] so I can check the firmware version? Attached output.txt. > Bye > > [1] http://ludovicrousseau.blogspot.com/2010/08/how-to-help-my-projects.html > [2] http://pcsclite.alioth.debian.org/supported.html#0x08C30x0402 > [3] http://pcsclite.alioth.debian.org/ccid.html#CCID_compliant Thanks, Forest -- Forest Bond http://www.alittletooquiet.net http://www.pytagsfs.org
idVendor: 0x08C3 iManufacturer: Precise Biometrics idProduct: 0x0402 iProduct: Precise 200 MC bcdDevice: 4A.95 (firmware release?) bLength: 9 bDescriptorType: 4 bInterfaceNumber: 0 bAlternateSetting: 0 bNumEndpoints: 3 bulk-IN, bulk-OUT and Interrupt-IN bInterfaceClass: 0x0B [Chip Card Interface Device Class (CCID)] bInterfaceSubClass: 0 bInterfaceProtocol: 0 bulk transfer, optional interrupt-IN (CCID) iInterface: ? CCID Class Descriptor bLength: 0x36 bDescriptorType: 0x21 bcdCCID: 1.00 bMaxSlotIndex: 0x00 bVoltageSupport: 0x03 5.0V 3.0V dwProtocols: 0x0000 0x0003 T=0 T=1 dwDefaultClock: 4.000 MHz dwMaximumClock: 7.500 MHz bNumClockSupported: 0 (will use whatever is returned) IFD does not support GET CLOCK FREQUENCIES request: Broken pipe dwDataRate: 10753 bps dwMaxDataRate: 241936 bps bNumDataRatesSupported: 0 (will use whatever is returned) IFD does not support GET_DATA_RATES request: Broken pipe dwMaxIFSD: 254 dwSynchProtocols: 0x00000000 dwMechanical: 0x00000000 No special characteristics dwFeatures: 0x000400BA ....02 Automatic parameter configuration based on ATR data ....08 Automatic ICC voltage selection ....10 Automatic ICC clock frequency change according to parameters ....20 Automatic baud rate change according to frequency and Fi, Di params ....80 Automatic PPS made by the CCID 04.... Short and Extended APDU level exchange dwMaxCCIDMessageLength: 524288 bytes bClassGetResponse: 0x00 bClassEnveloppe: 0x00 wLcdLayout: 0x0000 bPINSupport: 0x00 bMaxCCIDBusySlots: 1
signature.asc
Description: Digital signature
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
