Closed bogiton closed 6 years ago
... I suggest you use the RDV40 dedicated repo. https://github.com/rfidresearchgroup/proxmark3
There is a few changes coming to flashmem :) Among others a better driver thanks to @cjbrigato Look inside his PR for flashmem use inside a standalone mode.
Your standalone mode seem interesting, does it have anything to do about a greek transport system ;) ANyway, I would think your issues here has something to do about the debug printing.
Ah, ok! I will check it out, thanks! :) It has much to do with the transportation system, yeah :P Would definitely make my life easier if this works as planned.
Amazing! It was indeed the debug messages that caused the issue. Works nicely now! Thanks a lot! :)
Hello. Stay tuned for a strong pass2 on my own first modification of the flashmem driver. In the meantime, you can take a look on how I manage recording/recalling the last tag broken in pass1, it works flawlessly.
Edit : HA debug printing. Yes. Had the very same issue.
The Flash_WriteData function doesn't seem to be working while on standalone mode with no connected client. I will try to describe my issue. I was playing around with the new mem commands that work perfectly through the client. I then had a thought to try and write bytes on the flash while sniffing (e.g. just the auth commands). So I did some quick changes to the SniffIso14443a function to achieve just that. In order to see the debug messages, my first step was to try it out while connected to the client. I pressed the button for over 1 second and I got the message that the sniffing started (that was my standalone mode). I then tested sniffing over a reader and the flash memory was successfully written.
Memory before the sniffing session:
Then I started sniffing by holding the button
Stopped sniffing with button press and viewed the flash mem:
The auth_pwd was successfully written. I then wiped the flash mem, disconnected the rdv4 and powered it up with a powerbank. Did exactly the same thing (although no client connected), but nothing got written in the flash mem. Any idea why this might be happening?