dash/proxmark3
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use block_after_ACK in flashmem too

Browse Source
This commit is contained in:
Philippe Teuwen
2019-04-26 13:53:11 +02:00
parent b12be75a5b
commit 01b31c742b
3 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
client/cmdflashmem.c
View File

@@ -280,11 +280,13 @@ static int CmdFlashMemLoad(const char *Cmd) {
//Send to device
uint32_t bytes_sent = 0;
uint32_t bytes_remaining = datalen;
while (bytes_remaining > 0) {
uint32_t bytes_in_packet = MIN(FLASH_MEM_BLOCK_SIZE, bytes_remaining);
clearCommandBuffer();
if (bytes_remaining > bytes_in_packet)
// fast push mode
conn.block_after_ACK = true;
SendCommandOLD(CMD_FLASHMEM_WRITE, start_index + bytes_sent, bytes_in_packet, 0, data + bytes_sent, bytes_in_packet);
bytes_remaining -= bytes_in_packet;
@@ -293,9 +295,11 @@ static int CmdFlashMemLoad(const char *Cmd) {
PacketResponseNG resp;
if (!WaitForResponseTimeout(CMD_ACK, &resp, 2000)) {
PrintAndLogEx(WARNING, "timeout while waiting for reply.");
conn.block_after_ACK = false;
free(data);
return PM3_ETIMEOUT;
}
conn.block_after_ACK = false;
uint8_t isok = resp.oldarg[0] & 0xFF;
if (!isok) {