? Flasher did not respond - Cannot Flash ESP32 Board?

#1

I am trying to flash my ESP32 board with the demo-js example. I am failing with every example I try so this is not specific to the demo-js.

I am running on Windows 7. I updated my USB driver so that the board is recognized in the mos.exe tool and the COM port appears. I am able to boot up the board and it is running its factory code which changes a LED from green->blue->red->green->repeat. There is also an output to the output window that prints the color - so that all works on the mos.exe tool.

I was able to build the demo-js and even the demo-c codes successfully. But when I try to flash, I get the following error, no matter what I try:

$ mos flash esp32 --port COM6 --esp-baud-rate 921600
Fetching https://github.com/mongoose-os-apps/demo-js/releases/download/2.18.0/demo-js-esp32.zip...
  done, 1863551 bytes.
Loaded demo-js/esp32 version 1.0 (20200820-185447/latest-ge4ecb17-master)
Opening COM6 @ 115200...
Connecting to ESP32 ROM, attempt 1 of 10...
  Connected, chip: ESP32-PICO-D4 R0
Running flasher @ 921600...
E1222 23:36:29.691382    7964 common.go:73] failed to run flasher @ 921600, falling back to ROM baud rate...
Opening COM6 @ 115200...
Connecting to ESP32 ROM, attempt 1 of 10...
  Connected, chip: ESP32-PICO-D2 R0
Running flasher @ 0...
Error: /src/cli/flash/esp/flasher/flasher_client.go:264: flasher did not respond
/src/cli/flash/esp/flasher/flasher_client.go:126: failed to talk to flasher
/src/cli/flash/esp/flasher/flasher_client.go:85: 
/src/cli/flash/esp/flasher/common.go:78: failed to run flasher
/src/cli/flash/esp/flasher/flash.go:76: 
/src/cli/flash.go:231: 
/src/cli/main.go:198: flash failed
exit status 1
Command completed.
#2

I bought the ESP32-S2-WROVER.

Specifically this one: 356-ESP32-S2-SAOLA-R from Mouser.com

https://www.mouser.com/ProductDetail/espressif/esp32-s2-saola-1r/?qs=GBLSl2AkirsMIxW%2FKjKKRw%3D%3D&countrycode=US&currencycode=USD

#3

Also, can someone explain why this is fetching that zip file not using the one I just built?!

I ran it again using my locally built fw.zip and still get the same useless error message:

$ mos flash esp32 --port COM6 --esp-baud-rate 921600 build/fw.zip
Loaded app1/esp32 version 1.0 (20201223-052208)
Opening COM6 @ 115200...
Connecting to ESP32 ROM, attempt 1 of 10...
  Connected, chip: ESP32-PICO-D2 R0
Running flasher @ 921600...
E1223 00:01:22.911789    7776 common.go:73] failed to run flasher @ 921600, falling back to ROM baud rate...
Opening COM6 @ 115200...
Connecting to ESP32 ROM, attempt 1 of 10...
  Connected, chip: ESP32-PICO-D4 R0
Running flasher @ 0...
Error: /src/cli/flash/esp/flasher/flasher_client.go:264: flasher did not respond
/src/cli/flash/esp/flasher/flasher_client.go:126: failed to talk to flasher
/src/cli/flash/esp/flasher/flasher_client.go:85: 
/src/cli/flash/esp/flasher/common.go:78: failed to run flasher
/src/cli/flash/esp/flasher/flash.go:76: 
/src/cli/flash.go:231: 
/src/cli/main.go:198: flash failed
exit status 1
Command completed.
#4

AFAIK, the ESP32-S2 is not supported by Mongoose OS.
ESP32-S2 only supports ESP-IDF master or version v4.2 and higher
Mongoose OS uses a modified version of ESP-IDF 3.3-r6.

mos flash esp32 will always download an ESP32 pre-built version of the demo-js application.

To flash an application built on the local system, use

mos flash
#5

any expectation that it will support the S2 version? I presume it has to at some point since that’s the newest/latest version. thx for the info.

One other question - a newbie question - since Mongoose doesn’t currently support the S2 chips, it wouldn’t make sense to flash the test codes with some other method. But, say I wanted to flash it, what other alternatives could I use besides the mos.exe tool? Also, if I can’t utilize mongoose os at all on the S2, at the moment, what alternatives do you suggest for development on the S2 boards? Sorry for newbie questions but I am a true newbie.