Re: [Muscle] Linux SC reader and drivers

Mon, 21 Jun 2010 08:38:08 -0700

Le 21/06/2010 11:39, Drasko DRASKOVIC a écrit :
BTW, the ATR I have gotten so far (though maybe wrong) is :

USIMPtr->scidata = 0x3b
USIMPtr->scidata = 0x9d
USIMPtr->scidata = 0x94
USIMPtr->scidata = 0x80
USIMPtr->scidata = 0x1f
USIMPtr->scidata = 0xc7
USIMPtr->scidata = 0x80
USIMPtr->scidata = 0x31
USIMPtr->scidata = 0xe0
USIMPtr->scidata = 0x65
USIMPtr->scidata = 0xd0
USIMPtr->scidata = 0
USIMPtr->scidata = 0x2b
USIMPtr->scidata = 0xe6
USIMPtr->scidata = 0x8
USIMPtr->scidata = 0x73
USIMPtr->scidata = 0xfe
USIMPtr->scidata = 0x21
USIMPtr->scidata = 0x13
USIMPtr->scidata = 0xcf

I have no idea at the moment if this is a correct ATR, as I have not
seen this pattern here:

(Reformated for the Ludovic's online ATR parser :
3B 9D 94 80 1F C7 80 31 E0 65 D0 00 2B E6 08 73 FE 21 13 CF
Check here : http://smartcard-atr.appspot.com/parse)

This ATR is definitely correct. There are 13 historical bytes.
  • TS = 3B
  • T0 = 9D
  • TA(1) and TD(1) are present (protocol T=0) (values: 94, 80)
  • TD(2) is present (protocol T=15) (value: 1F)
  • TA(3) is present (value: C7)
  • Follow : 13 historical bytes
  • Follow : correct checksum (value: CF)
Checking the information embedded in the historical bytes, this ATR looks very valid to me.

-- Emmanuel Deloget
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to