Dave,
I believe he does have the CCID firmware. The PID E001 is CCID and E000 is the only non-CCID firmware.
Michael,
Is there a difference in behavior if pcscd is started with the reader attached and plugging the reader in after starting pcscd?
Regards,
Vijay.
Vijay Kumar
Sr. Systems Engineer
SCM Microsystems Inc.
466 Kato Terrace,
Fremont CA 94539.
Ph: 510-360-2701
This email and any attachment may contain confidential information and are intended solely for the use of the named recipient(s). If you have received this information in error, you are prohibited from reading, copying, distributing and using the information. If you are not a named addressee or otherwise an intended recipient you are requested to immediately notify the sender and to delete this email and all attachments from your system.
[EMAIL PROTECTED] wrote on 07/19/2005 01:38:53 PM:
> Hi Michael,
>
> Are you aware of whether your reader has the firmware for CCID ?
> This is the USB specification for smart card readers and allows you
> to use
> the CCID driver for pcsc-lite.
>
> Thanks,
> Dave
>
>
> On Jul 19, 2005, at 3:33 PM, Michael Lee Yohe wrote:
>
> > I've done all the research on the Internet I can do to try to get
> > these two kids to cooperate with each other. I have run into a
> > brick-wall.
> >
> > I have a USB SCM Microsystems SCR331 smart card reader (apparently a
> > fairly common device). The device was loaded with the latest and
> > greatest firmware available from www.scmmicro.com. I have a Linux
> > 2.6.10 based system running pcsc-lite 1.2.0. I have the SCR33x driver
> > from www.scmmicro.com version 4.1.1.
> >
> > I installed all the files in the default paths (based on
> > /usr/local/pcsc). I have the manufacturer MUSCLE bundle installed
> > properly in /usr/local/pcsc/drivers/scr33xcciddriver.bundle. I have
> > commented out all the lines in /etc/reader.conf (as suggested that USB
> > only has no reader.conf requirement). Just in case, I modprobe'd the
> > scr33x kernel driver (which built with no difficulties).
> >
> > # lsusb
> > Bus 005 Device 004: ID 2001:f103 D-Link Corp. [hex]
> > Bus 005 Device 001: ID 0000:0000
> > Bus 004 Device 001: ID 0000:0000
> > Bus 003 Device 003: ID 04e6:e001 SCM Microsystems, Inc.
> > Bus 003 Device 001: ID 0000:0000
> > Bus 002 Device 001: ID 0000:0000
> > Bus 001 Device 001: ID 0000:0000
> >
> > I checked /usr/local/pcsc/drivers/scr33xcciddriver.bundle/Contents/
> > Info.plist
> > to see if the vendor (0x04E6) and product (0xE001) IDs were present.
> > They were.
> >
> > When I run "pcscd -a -f" I get the following:
> >
> > # pcscd -a -f
> > debuglog.c:188 Debug options: APDU
> > pcscdaemon.c:251 main: pcscd set to foreground
> > pcscdaemon.c:445 main: pcsc-lite daemon ready.
> > hotplug_libusb.c:344 Adding USB device: 003:003
> > readerfactory.c:1391 RFInitializeReader: Attempting startup of SCR331
> > USB Smart Card Reader 0 0.
> > readerfactory.c:1133 RFBindFunctions: Loading IFD Handler 2.0
> > readerfactory.c:1428 RFInitializeReader: Open Port 200000 Failed
> > readerfactory.c:1263 RFUnloadReader: Unloading reader driver.
> > readerfactory.c:245 RFAddReader: SCR331 USB Smart Card Reader init
> > failed.
> > (rinse, repeat at hotplug_libusb...)
> >
> > It has no problem associating 04e6:e001 with the SCR331 USB Smart Card
> > Reader entry in the Info.plist file. Yet, it reports a failure. I
> > have tested this device under Windows 2000 and XP and have no
> > difficulties using it.
> >
> > Any thoughts?
> >
> > Your help would be greatly appreciated.
> >
> > --
> > AksanSai
> >
> > _______________________________________________
> > Muscle mailing list
> > [email protected]
> > http://lists.drizzle.com/mailman/listinfo/muscle
> >
> >
>
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
