|
@ -165,7 +165,9 @@ after it, here are troubleshooting recommendations: |
|
|
|
|
|
|
|
|
* If lower baud rate didn't help, you may want to try older version of |
|
|
* If lower baud rate didn't help, you may want to try older version of |
|
|
esptool.py, which had a different programming algorithm:: |
|
|
esptool.py, which had a different programming algorithm:: |
|
|
|
|
|
|
|
|
pip install esptool==1.0.1 |
|
|
pip install esptool==1.0.1 |
|
|
|
|
|
|
|
|
This version doesn't support ``--flash_size=detect`` option, so you will |
|
|
This version doesn't support ``--flash_size=detect`` option, so you will |
|
|
need to specify FlashROM size explicitly (in megabits). It also requires |
|
|
need to specify FlashROM size explicitly (in megabits). It also requires |
|
|
Python 2.7, so you may need to use ``pip2`` instead of ``pip`` in the |
|
|
Python 2.7, so you may need to use ``pip2`` instead of ``pip`` in the |
|
@ -180,8 +182,10 @@ after it, here are troubleshooting recommendations: |
|
|
* Additionally, you can check the firmware integrity from a MicroPython REPL |
|
|
* Additionally, you can check the firmware integrity from a MicroPython REPL |
|
|
prompt (assuming you were able to flash it and ``--verify`` option doesn't |
|
|
prompt (assuming you were able to flash it and ``--verify`` option doesn't |
|
|
report errors):: |
|
|
report errors):: |
|
|
|
|
|
|
|
|
import esp |
|
|
import esp |
|
|
esp.check_fw() |
|
|
esp.check_fw() |
|
|
|
|
|
|
|
|
If the last output value is True, the firmware is OK. Otherwise, it's |
|
|
If the last output value is True, the firmware is OK. Otherwise, it's |
|
|
corrupted and need to be reflashed correctly. |
|
|
corrupted and need to be reflashed correctly. |
|
|
|
|
|
|
|
|