[Pcsclite-muscle] Jinmuyu MR800 card reader problem

[Frédéric Marchal]

On lundi 12 juin 2017 9 h 15 min 36 s CEST Ludovic Rousseau wrote:
> 2017-06-12 6:33 GMT+02:00 Fr?d?ric Marchal <fmarchal at perso.be>:
> > The requested output.txt file is attached to this e-mail.
> 
> The reader indicates it has 2 slots:
>   bMaxSlotIndex: 0x01
> 
> From what you wrote earlier I guess it is wrong and the reader can only use
> 1 smart card. Exact?

The reader can read one RFID card but it has two internal slots for SAM cards. 
Does that account for the second reported slot?


> > The technical documentation is here: http://www.jinmuyu.com/
> > download/JINMUYU
> > %20Compatible%20USB%20PCSC%20IC%20Card%20Reader%20General%20Technical
> > <http://www.jinmuyu.com/download/JINMUYU%0A%20Compatible%20USB%20PCSC%20IC
> > %20Card%20Reader%20General%20Technical> %20Manual.pdf (in bad English and
> > the documentation is lacking).
> > 
> > The pictures on the manufacturer site are accurate.
> > 
> > Please let me know if you need additional information.
> 
> I don't think the problem is that the reader does not support T=1
> communication.
> In your second email the error occurred when the driver tried to negotiate
> IFSD:
> 00000135 ifdhandler.c:1089:IFDHSetProtocolParameters() Negotiate IFSD at 254
> 00000123 sending: 00 C1 01 FE 3E
> 00000143 -> 000000 6F 05 00 00 00 00 2D 00 00 00 00 C1 01 FE 3E
> 00009549 <- 000000 80 02 00 00 00 00 2D 00 00 00 FF FF
> 00000026 received: FF FF
> 00000011 sending: 00 C1 01 FE 3E
> 00000011 -> 000000 6F 05 00 00 00 00 2E 00 00 00 00 C1 01 FE 3E
> 00008298 <- 000000 80 02 00 00 00 00 2E 00 00 00 FF FF
> 00000043 received: FF FF
> 00000021 sending: 00 C1 01 FE 3E
> 00000023 -> 000000 6F 05 00 00 00 00 2F 00 00 00 00 C1 01 FE 3E
> 00008344 <- 000000 80 02 00 00 00 00 2F 00 00 00 FF FF
> 00000064 received: FF FF
> 00000033 prothandler.c:124:PHSetProtocol() PTS failed (612), using T=0
> 
> I guess the USB CCID descriptor has other problems (in dwFeatures), not
> just the value bMaxSlotIndex.
> 
> I will add this reader in the "Disabled CCID readers" list for now.

Windows can communicate with the MR800 without any additional driver so I 
won't blame the reader at this stage.

I'll try to investigate and see if I can submit a patch.

Fr?d?ric