bladox.com

[hayy]

Hi,

Is the solution to trace ME<--->SIM interface based on the Turbo-programmer + TurboLIte2 is able to trace the GSM commands only???
Suppose that someone write an application and install it into his terminal and then write an applet and install it into a SIM (a blank SIM). Does the solution described above allow him to trace the commands (so non GSM) that go through the Terminal-SIM interface?

Thanks.

[hayy]

Another important question.
What is the behaviour of the Lite2 when the terminal sends commands that are not GSM commands. Do these comands arrive to the original SIM or are they rejected by the Lite2? NB: that in this question I don't consider the tracing of the terminal <--->SIM interface: The senario concerns the use of a turboLite2 only.

Thanks in advance.

[pz]

Only class 0xA0 is implemented, we are wotking on generic iso 7816 0x00.

TL2 (and other devices) reject other then 0xA0 as not supported class. You cannot implement it in generic way without knowing commands/protocol for given class.

[hayy]

Thanks for your answer.
But Is there a data row mode in which the TL2 transmits and dumps the trafic without trying to understand it? I was wondering that this might not be difficult to develop, isn't it?

Thanks.

[pz]

We have "raw" kernel, which doesn't not interfere but it's also 0xA0 only. It's protocol - you cannot be just passing without knowing who/what is sending/receiving. You need to know e.g. this command is sending data not receiving and so.

[hayy]

Do you have any idea about when the wev version supporting 0x00 class will be released?
And would this version support any command (not Necessarily standard) provided that it is defined as 0x00 class command?

Finally, is-it possible to have access to your kernel source code in order to try to add changes in order to support non 0xA0 class commands?

Thanks.

[pz]