Re: MUSCLE ATR parameters "F" and "D"
For a card reader/writer on a serial interface or similar (e.g. USB), I believe that the old antitrust rule of mandatory publication of interface specs applies - thus all commands between the PC and the reader/writer should be published. But then I'm looking at this from the other side of the pond, where it has been very difficult to obtain this sort of information from some reader/writer manufacturers. Maybe one could use the same rule to force the publication of the interface between card and reader/writer - and thus force application and card OS suppliers to publish all the commands to, and responses from, the cards. Peter Tomlinson - Subject: Re: MUSCLE ATR parameters "F" and "D" To: Smart Muscleheads <[EMAIL PROTECTED]> From: Jim Rees <[EMAIL PROTECTED]> Date sent: Fri, 21 Jul 2000 09:54:25 -0400 Send reply to: [EMAIL PROTECTED] > The problem is that the commands for changing the > serial speed are not going to be published by the > manufacturer... > > Does their Windows driver do higher speeds? If so, it should be possible to > discover the Chipdrive command by snooping. > > It might also be possible to figure it out without the spec. I would start > by trying the unused bits in the set parity command. > *** > Linux Smart Card Developers - M.U.S.C.L.E. > (Movement for the Use of Smart Cards in a Linux Environment) > http://www.linuxnet.com/smartcard/index.html > *** > ++ Iosis, 34 Strathmore Road, Bristol BS7 9QJ, UK Phone & fax +44 (0)117 951 4755 Mobile +44 (0)7968 947021 Email [EMAIL PROTECTED] or [EMAIL PROTECTED] ++ *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE ATR parameters "F" and "D"
The problem is that the commands for changing the serial speed are not going to be published by the manufacturer... Does their Windows driver do higher speeds? If so, it should be possible to discover the Chipdrive command by snooping. It might also be possible to figure it out without the spec. I would start by trying the unused bits in the set parity command. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE ATR parameters "F" and "D"
Bad news: It seems that besides doing the PTS protocol with the card and increasing the speed of the serial port, Chipdrive controler needs to be informed of the new serial por speed. The problem is that the commands for changing the serial speed are not going to be published by the manufacturer, so we'll have to conform with a fixed speed of 9600, event if the driver successfully does PTS protocol. The upcoming release 2.0.0-pre5 T=0 module will come with serial speed fixed to 9600 bps. I apologize for the inconveniences. Thanks, Carlos. --- Jim Rees <[EMAIL PROTECTED]> escribió: > does this means that bitrate shold be set to D* > 9600 > when the parameter "D" is sent in the ATR ? > > No. The atr offers a set of possible protocols that > the card can speak. > The terminal gets to choose among them by sending a > pps request. If it does > not send such a request, default values of F and D > are used. Those defaults > (372, 1) result in a speed of 9600 bps if you use > the common 3.57 MHz clock. > > If the terminal does send a pps, it gets to choose > any F and D up to the > maximum supported by that protocol, as given in the > atr. See 7816-3 > sections 6.6.3 and 6.5.2. > > I think the max for Cyberflex is FI=9, DI=4, which > gives you 55928 bps. Or > maybe that's just the fastest that's compatible with > a standard 550 uart. > > I have never seen a card with internal clock so I > don't know how those work. > *** > Linux Smart Card Developers - M.U.S.C.L.E. > (Movement for the Use of Smart Cards in a Linux > Environment) > http://www.linuxnet.com/smartcard/index.html > *** __ Do You Yahoo!? Get Yahoo! Mail Free email you can access from anywhere! http://mail.yahoo.com/ *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE ATR parameters "F" and "D"
does this means that bitrate shold be set to D* 9600 when the parameter "D" is sent in the ATR ? No. The atr offers a set of possible protocols that the card can speak. The terminal gets to choose among them by sending a pps request. If it does not send such a request, default values of F and D are used. Those defaults (372, 1) result in a speed of 9600 bps if you use the common 3.57 MHz clock. If the terminal does send a pps, it gets to choose any F and D up to the maximum supported by that protocol, as given in the atr. See 7816-3 sections 6.6.3 and 6.5.2. I think the max for Cyberflex is FI=9, DI=4, which gives you 55928 bps. Or maybe that's just the fastest that's compatible with a standard 550 uart. I have never seen a card with internal clock so I don't know how those work. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
MUSCLE ATR parameters "F" and "D"
Hello, I was wondering about the interpretation of the ATR parameters "F" and "D". ISO 7816-3 says work etu = 1/D * 1/9600 s does this means that bitrate shold be set to D* 9600 when the parameter "D" is sent in the ATR ? (for instance in Cyberflex TA1 = 0x94, and this means that the bitrate should be 9600 * 8 = 76800) Also it is said that F parameter must be used for external clock cards. Exactly when does a card have internal or external clock? I'm a bit confused with this. Thanks for any response. Carlos. __ Do You Yahoo!? Get Yahoo! Mail Free email you can access from anywhere! http://mail.yahoo.com/ *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
