From 9d197efe19568708b7e628642388f166d85a6e63 Mon Sep 17 00:00:00 2001
From: Angus Gratton <angus@espressif.com>
Date: Tue, 28 Nov 2017 16:54:34 +1100
Subject: [PATCH] md5sum: Increase md5sum timeout to 8 seconds/megabyte

This is probably extreme, I think it's only the case if the last block of a compressed written image
is a large number of zeroes, meaning the md5sum has to wait until the last write finishes.
---
 esptool.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/esptool.py b/esptool.py
index a0c0f1cce..329e5c644 100755
--- a/esptool.py
+++ b/esptool.py
@@ -43,7 +43,7 @@
 CHIP_ERASE_TIMEOUT = 120              # timeout for full chip erase
 MAX_TIMEOUT = CHIP_ERASE_TIMEOUT * 2  # longest any command can run
 SYNC_TIMEOUT = 0.1                    # timeout for syncing with bootloader
-MD5_TIMEOUT_PER_MB = 5                # timeout (per megabyte) for calculating md5sum
+MD5_TIMEOUT_PER_MB = 8                # timeout (per megabyte) for calculating md5sum
 ERASE_REGION_TIMEOUT_PER_MB = 30      # timeout (per megabyte) for erasing a region