Testing script for Proxmark3 RDV4 external flash

test-flash.sh

#!/bin/bash

for ((i=0; i<100; i++)); do
    echo -e "\n\nIteration $i"
    rm -f test_flash_in.bin test_flash_out.bin
    dd if=/dev/urandom of=test_flash_in.bin bs=65536 count=3
    ./proxmark3.sh -c "
        mem wipe p 0;
        mem wipe p 1;
        mem wipe p 2;
        mem load f test_flash_in o 0;
        mem dump f test_flash_out o 0 l 196608"
    rm test_flash_out.eml
    HASH1=$(cat test_flash_in.bin|sha1sum)
    HASH2=$(cat test_flash_out.bin|sha1sum)
    if [ "$HASH1" != "$HASH2" ]; then
        echo FAIL
        exit 1
    fi
    rm -f test_flash_in.bin test_flash_out.bin
done
echo SUCCESS

and here I thought I was atleast going to see the semicolon at work :)
./proxmark3.sh -c 'mem wipe p 0; mem wipe p 1; mem wipe p 2"

but nice script.. Working with the pm3 client isnt that bad anymore from the bash shell. Of course like slurdge mentioned that assigning values from commands would be better.

Hi @iceman1001 as said in RfidResearchGroup/proxmark3#244 we've still the issue that we should add some delay after erase and write operations, still need to figure how much...
So the easy trick was to call mem wipe in several calls to the client.
I'll add a msleep command in the client commands, it'll ease scripts.

updated with msleep command

removed msleep as now BUSY_TIMEOUT was increased

you can remove that sleep command you added ;)
Look at those semi colons... mm mm mm

you can remove that sleep command you added ;)

already done tonight, sir...

mem save no longer works, replaced it with mem dump : )

my bad, fixed, thanks @luminouw