Bad ATR in direct convention result on card died !


[ Follow Ups ] [ BasicCard User Forum ]

Posted by guillaumeb (82.224.58.44) on July 14, 2010 at 12:49:09:

Hello all,

I Declare Binary ATR=&H3B,&H66,&H00,&H00,_
&H05,&H12,&H01,&H01,&H01,&HB1,&H01

On a BC 5.5 rev H
no problem, my card was working well.

Now I Declare Binary ATR=&H3B,&H6F,&H00,&H00, _
&H80,&H5A,&H08,&H03,&H04,&H00,&H02, _
&H00,&H24,&HE2,&H79,&H78,&H82,&H90,&H00

on the same card...
My card died !
The ATR is the same, isn't it ??? (3B 6x 00 00), only historical bytes are differents...

What happened ?

Best regards,

Guillaume

PS. I use an ACS ACR38US SAM on XP pro SP3 (X86) with PC/SC standard drivers.

PS2.
The EEPROM programmation was Ok :

C:\Documents and Settings\Gigi\Mes documents\Smartcard experiment\BC>bcload -D
P100 -ST myprog
BCLOAD BasicCard Loader Utility Version 6.24 (c) ZeitControl 2009
SET STATE LOAD
EEPROM SIZE
CLEAR EEPROM
WRITE EEPROM &H0700
...
WRITE EEPROM &H2980
EEPROM CRC
SET STATE TEST

C:\Documents and Settings\Gigi\Mes documents\Smartcard experiment\BC>bcload -D
P100 -ST myprog
BCLOAD BasicCard Loader Utility Version 6.24 (c) ZeitControl 2009
SET STATE LOAD
Communications error: SW1-SW2 = swCardTimedOut



Follow Ups:


[ Follow Ups ] [ BasicCard User Forum ]