And you need to write fault-tolerant code (one of several points in this
area made by David Everett - ex Mondex/Multos technical supremo - and David
Birch of Consult Hyperion yesterday at the last meeting of the year of the
UK Smart Card Club).

Peter T
Bristol UK
----- Original Message -----
From: "Jean-Luc Giraud" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 19, 2001 12:49 AM
Subject: Re: MUSCLE Smartcard OS


>
> On Tuesday, December 18, 2001, at 12:05  pm, Ronald Mundell wrote:
>
> > Hi
> >
> > How difficult is it to write a Smartcard OS. I am thinking off writing
> > one
> > for the AT90SCC3232C atmel card.
>
> If you are not very familiar with development on micro-controllers (i.e.
> use of emulators or even oscilloscopes to validate you I/O routines), it
> is going to be very difficult.
>
> As a former SC OS developer, I can tell you that writing code for a
> micro-controller is really  a different experience from working on a PC:
> the memory constraints in terms of code size and RAM have a direct
> influence on your coding style!
>
> On the other hand, writing JavaCard applets is much easier.
>
> >  I any one off you out there can tell me
> > where to find tools e.g. compilers, assemblers for this AVR Smartcard I
> > would be great full.
>
> You would have to get them from the manufacturer of the card chip you
> choose.
>
> Good luck,
> JLuc.
>
> ***************************************************************
> Unix Smart Card Developers - M.U.S.C.L.E.
> (Movement for the Use of Smart Cards in a Linux Environment)
> http://www.linuxnet.com/
> To unsubscribe send an email to [EMAIL PROTECTED] with
> unsubscribe sclinux
> ***************************************************************
>

***************************************************************
Unix Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/
To unsubscribe send an email to [EMAIL PROTECTED] with
unsubscribe sclinux
***************************************************************

Reply via email to