Closed wh201906 closed 3 years ago
No bug. Its related to user handling error.
If you read the help text, you find that you need to specify that you don't want to download a trace from device per automatic by specifying -1
param.
You also seem to struggle with the params in general when loading file. Its quite simple.
trace load -f traces/hf_14a_reader_4b_rats.trace
trace list -1 -t 14b
@iceman1001 I didn't check the help text carefully. Sorry about that. I know how to load trace files now.
How about saving trace files? I called "hf 14a sniff" then "trace save -f xxx" for many times with different filenames, but the traces files are all the same(I used cmp command and it returned nothing, the size of them are also the same). You can look at the logs above. The traceLen was changing after each "hf 14a sniff" but the "trace save" always returned "saved 2298 bytes..." I just went through the help text about "trace load" and "trace save", I don't know whether I am operating wrongly. Thanks for your help!
I got the point. After "hf 14a sniff", I need to call "trace list -t xx" to dump the trace from device to the client buffer then list it, and "trace save" only save the data from the client buffer. "trace list --buffer -t xx" will NOT dump the trace from the device, it will use the data from client buffer directly.
Trace save
will download if graph buffer is empty. If you already downloaded something, it will save that.
if (g_traceLen == 0) {
download_trace();
if (g_traceLen == 0) {
PrintAndLogEx(WARNING, "trace is empty, nothing to save");
return PM3_SUCCESS;
}
}
data clear
will empty both graphbuffer and bigbuf on device side.
data clear
hf 14a sniff -cr
trace save -f xxxx
or
trace list -t 14a
trace save -f xxx
Describe the bug When I use "hf mf sniff" then "trace save" for many times, it will only save the first trace data, even I use different filename.
Also, the "trace load" cannot load the file into the trace buffer.
To Reproduce Just "hf mf sniff" and "trace save". The logs might be better to show how to reproduce.
Expected behavior The trace files should be different.
Screenshots For the bug in "trace save":
For the bug in "trace load"
Desktop (please complete the following information):
OS: Ubuntu Bionic with Armbian Linux 4.19.63-sunxi64
Commit: 5ddfade1f9ffac3620e0641907a26401ceca8fa8
inside proxmark3 client run the following commands and paste the output here.
hw version
hw status
data tune