Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
yes and no. I haven't decided what timer to use. There are several to choose from:
* number of samples, has historically been used. Pretty useless.
* number of ssc_clock-ticks. Used in iso14443a. Uses all timers, depends on FPGA clock and FPGA-mode.
* number of microseconds. Has been used, uses up all ARM-timers. Could conflict with other things which uses timers.
* number of 'ticks'. Looks like a good 'generic' candidate.
The iso14443a timers are extremely finetuned, since piwis prng-attack relied on extreme timing. For generic tracing, I think it's ok with just some kind of decent timer. I don't know which I'll use, so I just used 0 for the moment. Previously, there was no timiing info at all on 'hf 14b list' (correct me if I'm wrong).
Offline
I may just put " < na > " in the timing column in case the value is 0. That makes it look less like a bug and more like unimplemented functionality, which is the case.
Offline
A good timing will be needed while studying 14b smartcard, otherwise i think <na> is more correct. Thank you for you reply.
Offline
The demodulation and modulation is done by the FPGA with a clock based on the 13,56MHz XTAL. Therefore the ssc_clock should be the only reasonable choice. All other clocks are not in sync with whatever happens in the FPGA and "on air".
Offline
Yes, but ssc_clk is not necessarily constant... Different modes may use different ssc_clks.
Offline
Also, you do a lot of black magic with delay lines and stuff to calc the correct time.. I am not sure what to use for e.g. 14443b ...
Offline
I've tested a bit, made some more tweaks. Hopefully it works now. I also added the extra annotations that you (asper) listed.
Offline
Thank you man ! I am low in time int hose days, I will test as soon as I can. The annotation is really a GREAT feature man !
Offline
Added more commands.
When parsing snooped bytes the real command in ISO15693 protocol, it is the second byte, the 1st one is a byte containing bit-flags; ex if you have 022001+2bytesCRC the real command is 20 (read block), 02 contains the flags, 01 is the block to read.
Last edited by asper (2015-02-05 14:06:09)
Offline
@asper, have you been able to test the generic-tracing since my changes (14b) ? I'd like to merge it into main before main-development goes too far ahead..
Offline
Yes, my reported tests were from the generic-tracing branch so it works... snooping is a bit difficult (antenna positioning choosiness) but it works !
Offline
Updated and added more custom commands.
Offline