On Fri, 2007-12-21 at 14:49 +0100, Ludovic Rousseau wrote:
> On Dec 18, 2007 10:22 PM, Sebastien Chassot <[EMAIL PROTECTED]> wrote:
> > On Tue, 2007-12-18 at 21:45 +0100, Ludovic Rousseau wrote:
> > > And with which reader?
> > >
> > It's a SCR335 (SCM Microsystems Inc. SCR33x USB Smart Card Reader, rev
> > 2.00/5.18, addr 2)
> >
> > I choose this model to avoid any difficulties  ;)
> 
> I don't remember having a time out problem with this reader.
> 

> The driver is correctly managing wtx requests (time extension) from
> the card. And then the reader decides to report a dead card after some
> time.
> 
> Maybe the card is too long to respond.
> Maybe the reader is too quick to declare the card dead.
> 

Could downgrade the firmware have any effect ?



> If you can you may try with a reader from another manufacturer.
> 

next time maybe?


> It MAY be possible to solve the problem by changing the BWI (block
> waiting interval) configured by the driver.
> Edit the file ccid/src/ifdhandler.c like this:
> Index: ccid/src/ifdhandler.c
> ===================================================================
> --- ccid/src/ifdhandler.c     (revision 2714)
> +++ ccid/src/ifdhandler.c     (working copy)
> @@ -681,7 +681,8 @@ EXTERNAL RESPONSECODE IFDHSetProtocolPar
>                       {
>                               DEBUG_COMM3("BWI/CWI (TB%d) present: 0x%02X", 
> i+1,
>                                       atr.ib[i][ATR_INTERFACE_BYTE_TB].value);
> -                             param[3] = 
> atr.ib[i][ATR_INTERFACE_BYTE_TB].value;
> +//                           param[3] = 
> atr.ib[i][ATR_INTERFACE_BYTE_TB].value;
> +                             param[3] = 0x9F;
> 
>                               /* only the first TBi (i>2) must be used */
>                               break;
> 
> This will change the value of BWI from 4 to 9 (maximal value) and the
> CWI value from 5 to F.
> 

It work slightly better ;) but I still have some failure...

I don't understand where it's coming from. It's a timeout in
reading/writing one block not the globale generation's time, isn't it  ?
So it could happens at any times in the generation process ?

Anyway, may I expect other reading/writing problems in the future ? if
not I'm going to use it like that.

Thanks




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

Reply via email to