Enter an ATR (Answer To Reset) and I will parse it for you.
Parsing ATR:
TS = 0x3B | Direct Convention |
---|---|
T0 = 0xFF | Y(1): b1111, K: 15 (historical bytes) |
TA(1) = 0x95 | Fi=512, Di=16, 32 cycles/ETU (125000 bits/s at 4.00 MHz, 156250 bits/s for fMax=5 MHz) |
TB(1) = 0x00 | VPP is not electrically connected |
TC(1) = 0xFF | Extra guard time: 255 (special value) |
TD(1) = 0xC0 | Y(i+1) = b1100, Protocol T=0 |
---- | |
TC(2) = 0x0A | Work waiting time: 960 x 10 x (Fi/F) |
TD(2) = 0x1F | Y(i+1) = b0001, Protocol T=15 |
---- | |
TA(3) = 0x43 | Clock stop: state L - Class accepted by the card: (3G) A 5V B 3V |
---- | |
Historical bytes | 80 31 E0 73 36 21 13 57 4A 33 20 07 33 41 41 |
Category indicator byte: 0x80 | (compact TLV data object) Tag: 3, Len: 1 (card service data byte) Card service data byte: 224 - Application selection: by full DF name - Application selection: by partial DF name - BER-TLV data objects available in EF.DIR - EF.DIR and EF.ATR access services: by GET RECORD(s) command - Card with MF Tag: 7, Len: 3 (card capabilities) Selection methods: 54 - Record number supported - Short EF identifier supported - DF selection by file identifier - DF selection by path Data coding byte: 33 - Behaviour of write functions: proprietary - Value 'FF' for the first byte of BER-TLV tag fields: invalid - Data unit in quartets: 1 Command chaining, length fields and logical channels: 19 - Logical channel number assignment: by the card - Maximum number of logical channels: 4 Tag: 5, Len: 7 (card issuer's data) Card issuer data: 4A 33 20 07 33 41 41 "J3 .3AA" |
TCK = 0x1F | correct checksum |
Possibly identified card:
3B FF 95 00 FF C0 0A 1F 43 80 31 E0 73 36 21 13 57 4A 33 20 07 33 41 41 1F
Swisscom 3G SIM card
The parsing code is part of pyscard and is available at parseATR.py.
The list of known ATR is also available online at smartcard_list.txt.
My blog contains a serie of artickes about ATR bytes.