You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only 106k is supported. Unfortunately, to properly emulate newer cards it would be required to support 212k and 424k at the very least; this would allow for proper emulation of DESFire (the first model). Until we have that, we would either have a different ATS stating we only support 106k OR the ATS would lie a bit in order to mimic the original card and risk the reader setting comm rate higher than 106k.
How much work would it take to implement the higher data rates? From my very limited experience with codecs in Chameleon, I would writing a new one for each speed setting?
The text was updated successfully, but these errors were encountered:
First of all: I would suggest to get the DESFire emulation (and other things) stable first and then think about adding new features more specifically. But we have this on our agenda.
Technically this brings us to a dilemma: We could either implement a new codec, but then we would have the problem that we would have to alter the codec functions during a configuration which is used. This could cause big problems.
Or: we could change the existing codec so we can alter the data rate during emulation. But this also could cause big problems.
To me, the latter option makes more sense, since the codec is basically the same but only the data rate is higher.
Actually I am rather skeptical whether the processing power of the ATxmega can handle data rates higher than 106kbit/s. From what I remember developing the ISO14443A codec, the way its implemented is already using a lot of CPU grunt to do what it is supposed to do.
Currently, only 106k is supported. Unfortunately, to properly emulate newer cards it would be required to support 212k and 424k at the very least; this would allow for proper emulation of DESFire (the first model). Until we have that, we would either have a different ATS stating we only support 106k OR the ATS would lie a bit in order to mimic the original card and risk the reader setting comm rate higher than 106k.
How much work would it take to implement the higher data rates? From my very limited experience with codecs in Chameleon, I would writing a new one for each speed setting?
The text was updated successfully, but these errors were encountered: