Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to flash ESP32 S3 #76

Open
slimcdk opened this issue Jan 30, 2023 · 1 comment
Open

Unable to flash ESP32 S3 #76

slimcdk opened this issue Jan 30, 2023 · 1 comment

Comments

@slimcdk
Copy link

slimcdk commented Jan 30, 2023

Hello

mos incorrectly reads the esp32 s3 chip id (or variant). The module is a genuine ESP32-S3-WROOM-1-N8 module. Purchased through mouser (Mouser No: 356-ESP32-S3WROOM1N8). mos flash recognizes the chip as a ESP32-D0WDQ6 while esptool recognizes it correctly. What would be the approach forward to make this work? I'll gladly test stuff in order to have mos fully support ESP32-S3.

$ mos version
The Mongoose OS command line tool
Version: 202208082325
Build ID: 202208082325+0671608~jammy0
Update channel: latest
// mos.yml
libs_version: latest
modules_version: latest
mongoose_os_version: latest
manifest_version: 2020-08-02
platform: esp32
$ mos flash
Loaded <project>/esp32 version 202301300945 (20230130-094530/g6a44982-master-dirty)
Using port /dev/ttyUSB0
Opening /dev/ttyUSB0 @ 115200...
Connecting to ESP32 ROM, attempt 1 of 10...
  Connected, chip: ESP32D0WDQ6 R0
Running flasher @ 921600...
E0130 13:09:15.375553   12104 common.go:73] failed to run flasher @ 921600, falling back to ROM baud rate...
Opening /dev/ttyUSB0 @ 115200...
Connecting to ESP32 ROM, attempt 1 of 10...
  Connected, chip: ESP32D0WDQ6 R0
Running flasher @ 0...
Error: /build/mos-latest-6vrzAq/mos-latest-202208082325+0671608~jammy0/cli/flash/esp/flasher/flasher_client.go:274: flasher did not respond
/build/mos-latest-6vrzAq/mos-latest-202208082325+0671608~jammy0/cli/flash/esp/flasher/flasher_client.go:136: failed to talk to flasher
/build/mos-latest-6vrzAq/mos-latest-202208082325+0671608~jammy0/cli/flash/esp/flasher/flasher_client.go:91: 
/build/mos-latest-6vrzAq/mos-latest-202208082325+0671608~jammy0/cli/flash/esp/flasher/common.go:78: failed to run flasher
/build/mos-latest-6vrzAq/mos-latest-202208082325+0671608~jammy0/cli/flash/esp/flasher/flash.go:80: 
/build/mos-latest-6vrzAq/mos-latest-202208082325+0671608~jammy0/cli/flash.go:237: 
/build/mos-latest-6vrzAq/mos-latest-202208082325+0671608~jammy0/cli/main.go:194: flash failed
$ esptool.py chip_id
esptool.py v4.4
Found 1 serial ports
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (revision v0.1)
Features: WiFi, BLE
Crystal is 40MHz
MAC: f4:12:fa:ec:c4:54
Uploading stub...
Running stub...
Stub running...
Warning: ESP32-S3 has no Chip ID. Reading MAC instead.
MAC: f4:12:fa:ec:c4:54
Hard resetting via RTS pin...
@Eugene-SvitSolutions
Copy link

Eugene-SvitSolutions commented Oct 19, 2024

Have similar problem

$ mos flash
Loaded app1/esp32 version 1.0 (20241019-060115)
Opening COM7 @ 115200...
Connecting to ESP32 ROM, attempt 1 of 10...
Connected, chip: ESP32D0WDQ6 R0
Running flasher @ 921600...

And hanged....

Pls help, we are doing a pilot project, and need to understand is this platform working for us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants