Hi Hari and all,
Thank's to Hari's reply.
We kind of figure out what is the problem.
In Test D, the ifdtest not even call our driver IFHTransmitICC() at all and
get failed on MUSCLE Resource Manager.
After speding one weeks, we found the value of dwRecvLength is not setting
correct as below:
Module: ifdtest - command.h
#define DO_TRANSMIT(PROTOCOL,NEG) if( more_details ) { \
myprintf("\n") ; \
for(j=0;j<dwSendLength ;j++) \
myprintf("%0x ",buffer[j]); \
} \
dwRecvLength = 256; /*?????????????????*/\
rv = SCardTransmit( hCard, PROTOCOL, buffer,
dwSendLength, \
&sRecvPci, r, &dwRecvLength ); \
....... Skip .....
After set dwRecvLength to 256, the call can be pass to the driver as it
should.
Any comments ?
Beside that we also encounter another failed item on ifdtest, ie, Test B No
5..
We are wondering if anyone have test the ifdtest and can provide us more
advise ...
Thank's in advance.
Lees.
-----Original Message-----
From: hariharan swaminathan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 03, 2002 10:52 PM
To: [EMAIL PROTECTED]
Subject: Re: MUSCLE ifdtest ... please help.
Hi,
Can you be more specific ?
Tell me where exactly it's failing. Try to build ifdtest with debug flags
and get the line number.
Try to print the hContext and return values from the IFD calls.
usually the return value from function calls are stored in a variable rv.
Try to print it after each call and see if it's failing.
Regards
Hari
--
On Thu, 3 Jan 2002 18:59:58
Shyh-Shin Lee(TP) wrote:
>Dear MUSCLE guys,
>
>We try to run the ifdtest from MUSCLE web site with the reader driver we
>developed.
>
>While excute Test D with any PC/SC test card inserted, the program suppose
>talk to the
>card which been inserted.
>
>However we found the Transmit in ifdtest are always faild and did not even
>call IFDHTransmitICC().
>If we are using test.c from pcsc-lite-0.8.4.tar we can see the
>IFDHTransmitICC() been called as it should.
>So we assume the connection between the driver to MUSCLE is ok.
>
>==== More Informatin ========
>The only functions been calling are .....
>
>IFDHICCPresence --- been calling all the time.
>IFDHSetCapabilities -- been calling all the time.
>IFDPowerICC -- been calling correctly while card inserted.
>
>Anyone have done this before and could share or give some advise to us?
>
>Lees.
>***************************************************************
>Unix Smart Card Developers - M.U.S.C.L.E.
>(Movement for the Use of Smart Cards in a Linux Environment)
>http://www.linuxnet.com/
>To unsubscribe send an email to [EMAIL PROTECTED] with
>unsubscribe sclinux
>***************************************************************
>
--
Click here for your very own create-a-date adventure from MatchMaker
Go to http://ecard.matchmaker.com/dating.html
***************************************************************
Unix Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/
To unsubscribe send an email to [EMAIL PROTECTED] with
unsubscribe sclinux
***************************************************************
