diff options
| author | Paul Sokolovsky <pfalcon@users.sourceforge.net> | 2016-06-12 18:50:24 +0300 |
|---|---|---|
| committer | Paul Sokolovsky <pfalcon@users.sourceforge.net> | 2016-06-12 18:50:24 +0300 |
| commit | 236838a9fc564291b67c54a4eacf7450dd5f9a7e (patch) | |
| tree | da41e17e423128e5b73455f0ace512d6a9f750ec /esp8266 | |
| parent | 9f8b788fe556579684d7f888e7196002f2fc8e00 (diff) | |
| download | micropython-236838a9fc564291b67c54a4eacf7450dd5f9a7e.tar.gz micropython-236838a9fc564291b67c54a4eacf7450dd5f9a7e.zip | |
esp8266/Makefile: Enable --verify option for esptool.py write_flash.
Based on my experience, there's rather non-zero chance to have an image be
flashed incorrectly. As --verify option is now works well in teh latest
esptool.py, enable it by default.
Diffstat (limited to 'esp8266')
| -rw-r--r-- | esp8266/Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/esp8266/Makefile b/esp8266/Makefile index 65093d819b..946440bee9 100644 --- a/esp8266/Makefile +++ b/esp8266/Makefile @@ -167,7 +167,7 @@ $(BUILD)/frozen.c: $(wildcard $(SCRIPTDIR)/*) $(CONFVARS_FILE) deploy: $(BUILD)/firmware-combined.bin $(ECHO) "Writing $< to the board" - $(Q)esptool.py --port $(PORT) --baud $(BAUD) write_flash --flash_size=8m 0 $< + $(Q)esptool.py --port $(PORT) --baud $(BAUD) write_flash --verify --flash_size=8m 0 $< #$(Q)esptool.py --port $(PORT) --baud $(BAUD) write_flash --flash_size=8m 0 $(BUILD)/firmware.elf-0x00000.bin 0x9000 $(BUILD)/firmware.elf-0x0[1-f]000.bin reset: |