Page 2 of 2

Re: What is APDU to read ATR ?

Posted: Tue Jul 25, 2017 10:34 pm
by UNKNwYSHSA
As I read in ISO 7816, if cards support extended length it should be store in ATR

Where's the position of this description in the specification?

What is your requirement?
What you want to do to use the ATR/ATS/ATTRIB? Because they are need for readers to get protocol parameters to communicate with the card.
Did you want to get the History Bytes?

Re: What is APDU to read ATR ?

Posted: Fri Jul 28, 2017 1:14 am
by leonard
I have a 1443 type B card and currently I can read ATR by send SELECT command with file id is 0x2F01 and then send READBINARY command

00 B0 00 00 00
This is response:
4301F84703F741E07F6608020205F0020205F09000

But why the command 00 B0 81 00 00 does not work?. According to ISO/IEC 7816-4 this command use to read EF with 5 bits of P1xP2 as file short ID (00001), and Le = 0x00 specify that need to read all bytes of file. Do I miss something? How to read file with short ID?

About the returned ATR, it is defined in SC17_N5781_ISO_IEC_FDIS_7816-62_Identification. It shows that:

Tag 43 --> Card Service Data
Length 01 --> 1 byte
Value F8 --> See ISO/IEC 7816-4 12.1.1.5

Tag 47 --> Card Capabilities
Length 03 --> 3 bytes
Value F7 41 E0 --> See ISO/IEC 7816-4 12.1.1.9

Tag 7F66 --> Extended Length APDU
Length 08 --> 8 bytes
Value --> See ISO/IEC 7816-4 12.7.1
Tag 02
Length 02
Value 05 F0
Tag 02
Length 02
Value 05 F0
But I can not find 7816-4 section 12 which is mentioned above. Therefore, I can not clarify definition of values in the returned ATR although I can read ATR successful now. Is this standard published?

Re: What is APDU to read ATR ?

Posted: Sat Aug 05, 2017 1:10 pm
by UNKNwYSHSA
:roll:
You didn't tell me what you want to do using the ATR value?