El 22/03/2013 14:13, Bruno Jesus escribió:
> On Fri, Mar 22, 2013 at 9:58 AM, Diego Delgado <[email protected]> wrote:
>> Well, I edit my last post.
>>
>> I have the firmware source code of the readers and I can modify it. So I
>> think the best and fast solution would be to develop de CCID application
>> layer at firware level. I'm right?
>> Are there some resources, information, etc. to support the CCID developing?
> You can refer to the documentation in
> http://www.pcscworkgroup.com/specifications/specdownload.php
> You can also see some sample code from Atmel. If you look for
> cciddriver.c in google you will find several projects using their
> files, for example:
> http://makecontroller.googlecode.com/svn/firmware/trunk/core/usb/device/ccid/

> It may be easier to write a CCID driver for pcsclite than try to write
> the CCID for the device.
But the reader must to be CCID compliant, isn't? Is not theCCID driver a
generic driver for all CCID readers?
Moreover these readers are used in a Windows environment.
>> Thanks.
>>
>> Diego.
>>
> Best wishes,
> Bruno
>
>> El 22/03/2013 12:40, Diego Delgado escribió:
>>> Hi there,
>>>
>>> I have two smartcard contactless readers not PC/SC compliant.
>>> The two readers communicate with the computer using a proprietary serial
>>> protocol. One of the readers connects using a serial cable and the other
>>> an USB cable although it's seen by Windows as a serial device (COMxx).
>>>
>>> I would like to make these readers PC/SC compliant. I think the only way
>>> is to make the PCSC driver for the reader, but I don't know how hard is
>>> to develop a PC/SC driver from scratch and if it would be possible if
>>> the reader (hardware and firmware) was not designed with PC/SC in mind.
>>>
>>> If not, what about developing a "bridge layer" between the PCSC
>>> framework and the propietary reader driver? In this case the bridge
>>> layer redirects the PC/SC calls to to the propietary reader serial driver.
>>> Maybe is this second approach more appropriate?
>>>
>>> Thanks.
>>>
>>>
>>> _______________________________________________
>>> Muscle mailing list
>>> [email protected]
>>> http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
>>>
>>
>>
>>
>>
>> _______________________________________________
>> Muscle mailing list
>> [email protected]
>> http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com



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

Reply via email to