From: jp (jp0rignalyahoo.com)
Date: Thu Mar 24 2005 - 21:14:22 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

I'm new to muscle pc/sc. I wrote already some small
application which simply communicate with card.

All is ok until card not need to switch baudrate
after atr. Here is a card example:

PC/SC device scanner
V 1.4.0 (c) 2001-2004, Ludovic Rousseau
<ludovic.rousseaufree.fr>
PC/SC lite version: 1.2.9-beta6
Scanning present readers
0: GemPC Twin 00 00

Fri Mar 25 04:05:26 2005
 Reader 0 (GemPC Twin 00 00)
        Card state: Card removed,

Fri Mar 25 04:05:39 2005
 Reader 0 (GemPC Twin 00 00)
        Card state: Card inserted,
        ATR: 3B 9C 13 11 81 64 72 65 61 6D 63 72 79 70
74 00 04 08

ATR: 3B 9C 13 11 81 65 82 65 61 2D 33 72 19 70 74 00
04 08
+ TS = 3B --> Direct Convention
+ T0 = 9C, Y(1): 1001, K: 12 (historical bytes)
  TA(1) = 13 --> Fi=372, Di=4, 93.000 cycles/ETU
  TD(1) = 11 --> Y(i+1) = 0001, Protocol T = 1
-----
  TA(2) = 81 --> Protocol to be used in spec mode: T=1
- Unable to change - defined by interface bytes
+ Historical bytes: 65 82 65 61 2D 33 72 19 70 74 00
04 08

As you can see: Di=4 and thus etu=93 after reset.
I thought that driver is responsible for etu change,
but for me it looks like etu wasn't changed, because
card didn't responding to any command after reset.

I must note that card is running OK in different
hardware (powerpc-based controller), so problem
is most likely in my code :-/

PS: Generic CCID 0.9.3 is used.

Regards.

Jan Petrou.s

                
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
_______________________________________________
Muscle mailing list
Musclelists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]