Could not flash my ESP32 board

[UserChristian]

I am a littel bit frustrated now, because yesterday I got my new ESP32 board and I am not able to flash it.
It’s a TTgo board with onboard Lora module, see here: http://www.lilygo.cn/prod_view.aspx?Typ ... t3:50003:3
With the flash tool from the board (ESP Easy Flasher) I am getting always that error message, see here:

Code: Select all

######2020-04-08######
#######0.04.007#######
######FLASH INFO######
BIN file: ESP_Easy_mega-20200328_test_ESP32_4M316k.bin
COM port: (COM2) Silicon Labs CP210x USB to UART Bridge (Port_#0001.Hub_#0006)
Baud rate: 115200
######POST FLASH######
No post flash information entered...
######FLASH LOG######
[esptool.exe -vv -cd nodemcu -cb 115200 -cp COM2 -ca 0x00000 -cf "C:\Temp\ESP\bin\ESP_Easy_mega-20200328_test_ESP32_4M316k.bin"]
[08.04.2020 12:22:24] esptool v0.4.12 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>
[08.04.2020 12:22:24] 	setting board to nodemcu
[08.04.2020 12:22:24] 	setting baudrate from 115200 to 115200
[08.04.2020 12:22:24] 	setting port from  to COM2
[08.04.2020 12:22:24] 	setting address from 0x00000000 to 0x00000000
[08.04.2020 12:22:24] 	espcomm_upload_file
[08.04.2020 12:22:24] 	espcomm_upload_mem
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] opening bootloader
[08.04.2020 12:22:24] resetting board
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	serialport_receive_C0: 0D instead of C0
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	read 0, requested 1
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	read 0, requested 1
[08.04.2020 12:22:24] resetting board
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	serialport_receive_C0: 0D instead of C0
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	read 0, requested 1
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	read 0, requested 1
[08.04.2020 12:22:24] resetting board
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	serialport_receive_C0: 0D instead of C0
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	read 0, requested 1
[08.04.2020 12:22:24] trying to connect
[08.04.2020 12:22:24] 	flush start
[08.04.2020 12:22:24] 	setting serial port timeouts to 1 ms
[08.04.2020 12:22:24] 	setting serial port timeouts to 1000 ms
[08.04.2020 12:22:24] 	flush complete
[08.04.2020 12:22:24] 	espcomm_send_command: sending command header
[08.04.2020 12:22:24] 	espcomm_send_command: sending command payload
[08.04.2020 12:22:24] 	read 0, requested 1
[08.04.2020 12:22:24] warning: espcomm_sync failed
[08.04.2020 12:22:24] error: espcomm_open failed
[08.04.2020 12:22:24] error: espcomm_upload_mem failed
[2020-04-08 12:22:24] STOPPED due to 2 errors! (try reset on the unit, then start a new flash attempt)
 

Later I made a second try with programming tool from Espressif and I followed the instructions, see here: https://www.letscontrolit.com/forum/vie ... php?t=6354
The first three bin files from that link above and on the last bin file from Github.

Espressif

20200403_Programmer.gif (74.38 KiB) Viewed 11009 times

Could not flash ESP32 board

Code: Select all

main.py:96: wxPyDeprecationWarning: Using deprecated class PySimpleApp.
[19.5, 19.0, 18.5, 17.0, 15.0, 13.0]
('self.chip: ', 'ESP32')
RF option applied...
C:\Temp\Flash\flash_download_tools_v3.6.8\flash_download_tools_v3.6.8\Bin\bootloader.bin
C:\Temp\Flash\flash_download_tools_v3.6.8\flash_download_tools_v3.6.8\Bin\boot_app0.bin
C:\Temp\Flash\flash_download_tools_v3.6.8\flash_download_tools_v3.6.8\Bin\partitions2.bin
2 kill
test offset :  57344 0xe000
case ok
3 kill
test offset :  32768 0x8000
case ok
4 kill
test offset :  65536 0x10000
case ok
C:\Temp\Flash\flash_download_tools_v3.6.8\flash_download_tools_v3.6.8\Bin\ESP_Easy_mega-20191208_custom_ESP32_4M316k.bin
1 kill
test offset :  4096 0x1000
case ok
test offset :  4096 0x1000
case ok
test offset :  4096 0x1000
case ok
test offset :  57344 0xe000
case ok
test offset :  32768 0x8000
case ok
test offset :  65536 0x10000
case ok
======
CONNECT BAUD: 115200
============
...Efuse CONSOLE_DEBUG_DISABLE is already burned.
Uploading stub...
Running stub...
Stub running...

 is stub and send flash finish
 

After an restart I tried to find the board over WIFI but I could not found it.
I looks that the bord is not starting?
What can I do now?

[TD-er]

The documentation really should be updated on ESP32 flashing.
See https://www.letscontrolit.com/forum/vie ... 706#p43706

[UserChristian]

Thank you for the link, but I tried it already, based on that description.

A few things are not clear to me:

1. Are the settings of files and adresses are correct?

• bootloader.bin = 0x1000
  boot_app0.bin = 0xe000
  partitions2.bin = 0x8000
  ESP_Easy_mega-20200328_test_ESP32_4M316k.bin = 0x10000

2. What does the following message mean?

• "..Efuse CONSOLE_DEBUG_DISABLE is already burned"

3. Must I select or deselect the following flag?

• DoNotChgBin = Off
  SpiAutoSet = Off

4. Makes it differences from SpiAutoSet to the default?
At the moment I use the following settings:

• SpiAutoSet = Off
  SPI Speed 40Mhz
  SPI Mode = DIO

The following coud I got from the serial monitor:

Code: Select all

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0010,len:4
load:0x3fff0014,len:812
load:0x40078000,len:0
load:0x40078000,len:10164
entry 0x400789f8
¬U52 : Info  :

INIT : Booting version: mega-20200328 (ESP32 SDK v3.2.3-14-gd3e562907)
53 : Info  : INIT : Free RAM:291468
53 : Info  : INIT : Cold Boot - Restart Reason: CPU0: Vbat power on reset CPU1: for APP CPU, reseted by PRO CPU
62 : Info  : FS   : Mounting...
102 : Info  : CRC  : No program memory checksum found. Check output of crc2.py
124 : Info  : CRC  : SecuritySettings CRC   ...OK
125 : Info  : WIFI  : Start network scan

Is that message "No program memory checksum found. Check output of crc2.py" normal?

I hope it will help to find my failure

[TD-er]

[...]
Is that message "No program memory checksum found. Check output of crc2.py" normal?
[...]

Yep, the Python script we use after building to generate the CRC (and put filename in the build) does not work well for ESP32, so those binaries are not patched after build and thus do not have the correct CRC.

[UserChristian]

Okay know I know that the crc message is normal.
I think the transfer was working, but the program is not starting yet (no wifi yet).
Some other idea?