Hi, in my own experience I could see that the last PCSC lite 1.2.0 has some bugs, then I use the 1.1.2, download the last version of the Validation Kit, you can downloat it from the CVS of the project.
About the PCSC Test Card from Siemens, I believe that it is a bug in the Test program, because in the ATR returned you can't connect in T0 protocol, drop the lines with T0 Connection, and the rest of the code functions OK. I use my own driver and the Mako LT3500 USB Reader to do the tests. Best Regards Alexandre Davi Silva www.mako-tech.com -----Mensagem original----- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nome de Damien Sauveron Enviada em: quinta-feira, 22 de abril de 2004 20:19 Para: MUSCLE Assunto: Re: [Muscle] Siemens Card failed PC/SC Driver Validation Kit Hi Tony, > I'm going to use the PC/SC test suite cards and PC/SC Driver > Validation Kit(1.0.0) to test my PC/SC reader. However, I > find the Siemens card always failed the following 2 tests > with the validation kit. Did anyone find similar problems > and know the root causes ? Which is the version of PC/SC Lite used? Could you try the last version (or better the CVS version) of PC/SC Lite [1] if you don't use it? Which is the reader? Which is the driver version? Have you the same problems with an other reader? > ------------------------------------------------------------------------- > 1. failed the "Try to set protocol T0" test > - as I studied the "testSIEMENS.c" file in the Validation Kit, > it's the returned value(= -1) of "protocol" parameter of > "SCardReconnect" function, that causes the failure. > > printit( "Try to set protocol T0" ); > rv = SCardReconnect( hCard, > SCARD_SHARE_SHARED, > SCARD_PROTOCOL_T0, > SCARD_RESET, > &protocol ); > > if( rv != SCARD_S_SUCCESS ) > { > myprintf( "Failed\n" ); > return -1; > } > > myprintf( "%s\n", ((protocol == 2) ? "Passed" : "Failed") ); > > - as I studied the "prothandler.c" file in PCSC Lite, it's the > "PHSetProtocol" function which changes the content of "rContext-> > dwProtocol" to -1 (for setting T=1 Simens card to T=0 protocol). > In turn, it makes "SCardReconnect" function(in the Validation Kit) > returns -1 in "protocol" parameter. > > - the above failure seems nothing to do with my device driver. Do you think that the first problem is due to a bug is in the function PHSetProtocol of PC/SC Lite? Have you the same problem on Windows? > ------------------------------------------------------------------------- > 2. failed the "WRITE BINARY 255 bytes" test in "Test No. 5" > - as I compared the T=1 TPDU commands & responses of my device drivers > on Linux & MS-Windows, they'd exchanged the same data in the same > sequence. But, the test program on MS-Windows returns passed, while > the validation kit on Linux returns failed. See my test logs as > below. Here, it is too late to understand the log I think ;-) Good night! [1] http://alioth.debian.org/projects/pcsclite/ Best Regards, -- Damien Sauveron ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
