As an industry outsider who found himself "doing it"
1) it was easy to program a minimal I2C link to communicate
T0-style Pdus to a sync device. It was harder to program T0
to so the same over the same device's async; and it defeated
a colleague of mine who has done microprocessor bit banging
for years. (Admittedly, he failed over the "intelligence" in
the 7816 SIE support in the terminal's micro, which was
incredibly optimized to save a register or two...and made
doing obvious things (like wait and reset a guard time..in
ETUs) incredibly hard in practice
2) all the musclecard chips I used had an USB SIE and
protocol handler onboard. So the ICC-side stack, to receive
256 bytes only got larger... In my case, the verilog was
doing most of the hard work, assuming I knew how write
firmware for a USB port. The enumeration code took so much
code space...tho!
3) my computer nicely streams data at HDTV line speed down
to my sony memory stick, with on the fly DRM encryption by
the magicgate logic. Its effortless. Its reader is
convenient (working in PCs, cameras, etc), and is supported
in a gazillion $5 "19-in-1" "memory" reader/writers. The 1GB
magicgate sells for $25 retail. The 2G is available now.
That flash is fast!
----- Original Message -----
From: "Andreas Schwier" <[EMAIL PROTECTED]>
To: "MUSCLE" <[email protected]>
Sent: Thursday, January 18, 2007 12:30 AM
Subject: Re: [Muscle] Question on T=1 protocol card.
I say flush the protocol sections of ISO-7816 down the
toilet and
come up with a protocol that works for the 21st Century.
like what: TCP/IP ? Don't be unfair, these protocols need
to be
implemented in devices with quite limited computing
capabilities. They
have to be robust and simple to implement. If you think,
that T=1 is to
complex, I suggest to take a look at our T=1
implementation done for the
ECO5000 card reader. In just 700 lines of source it
implements a
reliable protocol with error correction, buffer size
negotiation,
chaining, timeout handling and clean transmission
abortion. Please show
me a simpler protocol that does all this.
Andreas
mike
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
--
--------- CardContact Software & System Consulting
|.##> <##.| Andreas Schwier
|# #| Schülerweg 38
|# #| 32429 Minden, Germany
|'##> <##'| Phone +49 171 8334920
--------- http://www.cardcontact.de
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
