Closed doegox closed 5 years ago
Confirmed.
Increasing timeouts solved it on my setup.
The problem is wider, any command requiring a swap of FPGA images will get an increased delay every time we go LF<>HF.
E.g.
[usb] pm3 --> lf read
[...]
[usb] pm3 --> hf search
[=] Checking for known tags...
[!] timeout while waiting for reply.
I implemented a mechanism of waiting time extension request where the Pm3 indicates to the client that it will take exceptionally more time than usual. Usage: https://github.com/RfidResearchGroup/proxmark3/blob/bc28eb04e437e65c94f86e94c4da7b0ef58cf92e/armsrc/fpgaloader.c#L398-L399
@cjbrigato maybe you could add a send_wtx() into spiffs_gc with a proper timing? how much can take the garbage collector in worst cases ?
I still don't understand why we get an increasing timeout instead of a fixed timeout.
Your workaround solves some issues,
we can discuss it if it's not clear.
./proxmark3.sh -c "lf read s d 100;hf tune;hf tune"
First call to
hf tune
after alf read
fails, second call works fine.