Sébastien Lorquet a écrit :
just some remarks

-APDU are stored in a dedicated apdu buffer, separated from the main ram

the chip may have different RAM types, this is only relevant for the VM
(coded in C), the applets only know RAM thru the JCSystem.makeTransient
functions.

-cards that support both T=0 and T=1 are generally used in T=0 mode since the readers try this one before ;)

depends on the reader, Omnikey drivers - because they are german -
always use T=1 if both are available.

-command apdu is sent as a whole even if only the 5 first bytes are available before setIncomingAndReceive, this is what the oscilloscope said to me yesterday.

-new Truc() creates an eeprom object. To get a RAM object, create it as a local variable and give this local variable as a parameter to other methods that will use it.

you are not very precise, if "create it" means allocate a new Truc(),
it always occurs in EEPROM, the only local variables that are allocated
from the RAM stack are the integer types (so byte, short) and
references.

-muscle card spec: the best I know is http://www.linuxnet.com/musclecard/files/mcardprot-1.2.1.pdf

Great, if it is not outdated, it's a perfect reference.
Thank.

Sylvain.


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

Reply via email to