[prev in list] [next in list] [prev in thread] [next in thread]
List: ms-smartcardddk
Subject: Re: G&D test card used in T=1 at 115kbauds
From: Christophe Chausset <Christophe.Chausset () SUR ! SC ! PHILIPS ! COM>
Date: 1999-03-16 12:51:24
[Download RAW message or body]
Klaus,
I have been in contact with a person from G&D. And it appears that the
G&D card is working with a CWT of 15 etus = 126 µs, whereas the ATR indicates a
CWT of 43 etus (TB3 = 35 implies CWI of 5). That is explaining the problem some
people and I have encountered. G&D should modify their ATR to be ISO compliant
(TB3=32).
Best regards,
Christophe Chausset
Philips Semiconductors
____________________________ Séparateur Réponse ________________________________
Objet : RE: G&D test card used in T=1 at 115kbauds
Auteur : Klaus Schutz <kschutz@microsoft.com> ŕ #SMTP
Date : 25/02/99 09:46
Christophe,
We're using this card with several readers here at Microsoft
and have not encountered the problem you describe. I can
successfully use this card at 115200 Baud. Apperently, the
reader I use for the test (Bull TLP3) has no problems with
the G&D card.
You say that several people have the same problem. I know only of
three reported problems and those have been solved. I would like
to know who these people are, so I can contact them and see if
this is really a card issue.
There is no plan to update the card currently. If your reader
cannot support the high data rate of the card, I suggest that
you issue the PPS for a lower data rate.
Klaus U. Schutz
Microsoft
-----Original Message-----
From: Christophe.Chausset@sur.sc.philips.com
[mailto:Christophe.Chausset@sur.sc.philips.com]
Sent: Thursday, February 18, 1999 1:13 AM
To: SmartCardDDK@DISCUSS.MICROSOFT.COM
Cc: Klaus Schutz
Subject: G&D test card used in T=1 at 115kbauds
Hello,
I am encountering a problem with G&D test card. TA1 returned in ATR is
18h
(Fi=372 and Di=12). The card is working correctly in T=0 protocol at
115
kbauds after a PPS negotiation, but not in T=1 protocol.
A successful PPS exchange is returned when Fi/Di and protocol T=1
negotiation is performed. But when sending the PCB of the APDU 00 A4 00
00
02 00 01, the card is answering a R-block 00 82 00 82 in the same time.
So
there is a conflict on I/O line. (Our reader is respecting all the
timings)
The card is working correctly at 9600 bauds in T=1 protocol.
I know this problem has been seen by several people.
My questions are:
- will the G&D card be updated, as it is not working correctly at 115
kbauds in T=1 protocol ? (returning an unsuccesful PPS),
- and can I just negotiate the protocol and not the parameters to
bypass
this bug knowing this feature will be applied for all other cards
supporting a Fi/Di different from 372/1 and two protocols (T=0/T=1) ?
In other words, what Microsoft is expecting from the reader in this
specific case ?
Thank you for your support.
Kind regards.
Christophe Chausset
Smart Card Coupler Application Engineer
Applications Laboratory PARis (ALPAR)
Philips Semiconductors
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic