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.
Hi, I had some questions about the simulator. The current implentation seems quite slow for read (15 ms vs about 1.2 ms for the card) so I was seeing if some changes could be made to allow the simulator to process requests more quickly. I think that some reader implementations are programmed to be impatient in order to prevent emulations from opening the lock.
1) How is testing for execution time done in the ARM code? I noticed that FpgaEnableTracing is in the loop for Mifare1ksim() - is this expensive?
2) How expensive are the debug calls in this loop?
I'm just starting to look at this, and it looks like I could use my horrible hack methods of editing and compiling things to try and make it better, but if there are any debugging hints anyone has it would be greatly appreciated.
I did some measurement of other mifare 1k classic implementations, and I've found that the Chameloeon Ultra is between 5-6 ms and the Flipper Zero is 10-12 ms for a block read.
If someone could give me hints to what profiling tools/editors are used to work with this, it would be much appreciated. If not, I guess I'm stuck with edit/build/run to see if I can improve performance.
--Ted
Offline