2010/9/1 Forest Bond <[email protected]>:
> On Tue, Aug 31, 2010 at 09:25:12PM +0200, Ludovic Rousseau wrote:
>> 2010/8/31 Forest Bond <[email protected]>:
>> > 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.
Precise is lying to you about T=1 problems.
Here is a diff between the USB descriptor of your device and the latest one.
--- /Users/rousseau/Downloads/output.txt 2010-09-01 16:42:31.000000000
+0200
+++ Precise_200_MC.txt 2009-12-03 18:20:34.000000000 +0100
@@ -2,7 +2,7 @@
iManufacturer: Precise Biometrics
idProduct: 0x0402
iProduct: Precise 200 MC
- bcdDevice: 4A.95 (firmware release?)
+ bcdDevice: 50.00 (firmware release?)
bLength: 9
bDescriptorType: 4
bInterfaceNumber: 0
@@ -37,14 +37,15 @@
dwSynchProtocols: 0x00000000
dwMechanical: 0x00000000
No special characteristics
- dwFeatures: 0x000400BA
+ dwFeatures: 0x000404BA
....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.. Automatic IFSD exchange as first exchange (T=1)
04.... Short and Extended APDU level exchange
- dwMaxCCIDMessageLength: 524288 bytes
+ dwMaxCCIDMessageLength: 65550 bytes
bClassGetResponse: 0x00
bClassEnveloppe: 0x00
wLcdLayout: 0x0000
Note the new line in the dwFeatures parsing:
+ ..04.. Automatic IFSD exchange as first exchange (T=1)
It is exactly linked to T=1 and should be the source of your problem.
The bug has been corrected in later readers so they are aware of the problem.
Maybe you should request for a reader exchange.
If you use a recent enough CCID driver the driver will refuse to work
with your reader because of the bogus firmware. It would then be
obvious the problem is on the reader side.
Bye
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
