simtrace2

SIMtrace2 (based on AT91SAM3), firmware and host tools, including card emulation https://osmocom.org/projects/simtrace2

Go to file

Christina Quast f6bf349a53 CCID: Change cold to warm rst on PCtoRDRIccPowerOn Before this change pcsc_scan would always receive garbage from the stack when the reset button was pressed on the simtrace board. Because the return value of ISO7816_GetChar is never checked anywhere. If there is a timeout in this function, the non-initialized local variable values which happen to be lying around on the stack are inserted into the ATR message and send to the host. This only helps mitigating the symptoms but does not remove the reason for the behavior. On the other hand, is it really feasable to check the return value on EVERY call to ISO7816_GetChar..?	2015-01-15 14:42:04 +01:00
minimal	minimal testprog (not working)	2014-11-22 19:48:48 +01:00
sam3s_example	CCID: Change cold to warm rst on PCtoRDRIccPowerOn	2015-01-15 14:42:04 +01:00
clk_calc.py	Clock calculator python script	2014-12-05 15:51:13 +01:00

Christina Quast f6bf349a53 CCID: Change cold to warm rst on PCtoRDRIccPowerOn

Before this change pcsc_scan would always receive garbage
from the stack when the reset button was pressed on the
simtrace board. Because the return value of ISO7816_GetChar
is never checked anywhere. If there is a timeout in this function,
the non-initialized local variable values which happen to be
lying around on the stack are inserted into the ATR message
and send to the host.

This only helps mitigating the symptoms but does not remove
the reason for the behavior. On the other hand, is it really
feasable to check the return value on EVERY call to
ISO7816_GetChar..?

2015-01-15 14:42:04 +01:00

minimal

minimal testprog (not working)

2014-11-22 19:48:48 +01:00

sam3s_example

CCID: Change cold to warm rst on PCtoRDRIccPowerOn

2015-01-15 14:42:04 +01:00

clk_calc.py

Clock calculator python script

2014-12-05 15:51:13 +01:00