Frozen modules attempt failed

All ESP8266 boards running MicroPython.
Official boards are the Adafruit Huzzah and Feather boards.
Target audience: MicroPython users with an ESP8266 board.
davef
Posts: 180
Joined: Thu Apr 30, 2020 1:03 am
Location: Christchurch, NZ

Re: Frozen modules attempt failed

Post by davef » Sat Feb 20, 2021 7:37 pm

The board is an ESP-07S. The standard v1.14 image loads and works with the quoted esptool command.
Sometimes it helps to lower to he baud rate. I use 460800. Sometimes even 230400.
These are higher than the default 115200. I did try 74,400 as I saw that mentioned somewhere.
I will try dout.

Thanks

.

User avatar
Roberthh
Posts: 2462
Joined: Sat May 09, 2015 4:13 pm
Location: Rhineland, Europe

Re: Frozen modules attempt failed

Post by Roberthh » Sat Feb 20, 2021 7:56 pm

For firmware update higher baud rates are used. The default is 921600, but that's to fast for many boards. 115200 should work at least. If that does not work, the problem is not th baud rate. The baud rate of 74880 is used during the start phase of the module by the esp8266 itself, not for firmware upgrades by the PC.

davef
Posts: 180
Joined: Thu Apr 30, 2020 1:03 am
Location: Christchurch, NZ

Re: Frozen modules attempt failed

Post by davef » Sat Feb 20, 2021 8:15 pm

Ah, thanks for the clarification on baudrates.

dout gives the same result.

Fortunately, I have something useful without frozen modules. I need to determine what is wrong in the build process for the default image.

For the standard micropython v1.14 image both dio and dout work.

Code: Select all

sudo esptool.py --port /dev/ttyUSB0 --baud 115200 write_flash --flash_size=1MB -fm dout 0x0 esp8266-1m-20210202-v1.14.bin

Post Reply