#Help diagnosing ESP32-S3 Feather...
1 messages · Page 1 of 1 (latest)
I tried the Factory Reset, and that did not help.
I then tried the WebSerial ESPTool to update the bootloader. It freezes at "Stub running....".
Anything else I should try?
so you put it in ROM bootloader mode? (Held down BOOT and clicked RESET)?
is this fresh out of the bag?
was it working before?
Yes, I tried to update it. It was fresh out of the bag, but a couple of years old.
I just ordered five more, so I don't think this will hold me up, but it would be nice to sort out what happened.
would you feel comfortable running esptool.py on the command line? What's your host OS?
I am on Windows 11. Be happy to try. Have a USB cable in front of me, and I am not afraid to use it.
do you have python installed? You can do pip3 install esptool or maybe pip install esptool
Python 3.11 up and running.
let's just make sure the bottom of the board says ESP32-S3 and 4MB flash / 2 MB PSRAM
"pip install esptool" is running.
Confirmed 4/2
ok, open Device Manager -> Ports, and put it into rom bootloader mode by holding down the BOOT button and clicking RESET. Use the COMnn port that appears in Device Manager in a line like this:
C:\> esptool.py -p COMnn chip_id
esptool.py v4.8.1
Serial port COMnn
Connecting...
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded Flash 4MB (XMC), Embedded PSRAM 2MB (AP_3v3)
Crystal is 40MHz
MAC: f4:12:fa:59:fd:00
Uploading stub...
Running stub...
Stub running...
Warning: ESP32-S3 has no Chip ID. Reading MAC instead.
MAC: f4:12:fa:59:fd:00
Hard resetting via RTS pin...
(I am on Linux at the moment so I edited my output to match what I think you should see.)
paste what you do see, assuming it gets stuck
I have updated python to 3.13
I ran the pip install command, but I think I have PATH problems.
looking at my windows python install ...
try just esptool instead of esptool.py
my path to esptool is "C:\Users\halbe\AppData\Local\Programs\Python\Python312\Scripts\esptool.exe"
C:\Users\halbe\AppData\Local\Programs\Python\Python312\Scripts\ is in my PATH
pulling hair out
just say what's happening. do you have any other boards, btw?
I have a directory of " Directory of c:\Users\Spencer Webb\AppData\Roaming\Python\Python313\site-packages\esptool"
But there is no esptool.py
that's ok, it's esptool.exe on windows
and the executable is in a different place, see my post above at 4:37pm
so that place should be on your PATH
Looking
(this is why we made the web interface!)
you can search for "env" with Windows Search and find the Environment Var dialog boxes
try exiting from the terminal window and opening a new terminal window. The PATH may have been edited since you opened the terminal window, if it you opened it before python or pip was installed
ESPTOOL is found. I think closing and opening the term window was important.
btw, I sent you a DM on an unrelated matter
esptool v5.1.0
Connected to ESP32-S3 on COM20:
Chip type: ESP32-S3 (QFN56) (revision v0.1)
Features: Wi-Fi, BT 5 (LE), Dual Core + LP Core, 240MHz, Embedded Flash 4MB (XMC), Embedded PSRAM 2MB (AP_3v3)
Crystal frequency: 40MHz
USB mode: USB-Serial/JTAG
MAC: f4:12:fa:97:e2:dc
Stub flasher running.
Warning: ESP32-S3 has no chip ID. Reading MAC address instead.
MAC: f4:12:fa:97:e2:dc
Hard resetting via RTS pin...
C:\Users\Spencer Webb>
that looks absolutely fine. now try esptool -p COM20 erase_flash
this all looks good. You should be able to load the bootloader and CircuitPython.
circle back if trouble. I have to leave in about 15 minutes
OK.... WebSerial ESPTool is running, and still stops at "Stub running..."
it could be bad flash. Try the OPEN INSTALLER button here: https://circuitpython.org/board/adafruit_feather_esp32s3_4mbflash_2mbpsram/. It will guide you through an erase, flashing the UF2 bootloader, and loading CircuitPython.
also make sure Chrome is up to date. There was a bug several weeks ago that broke things.
Dan, you're awesome. I am going to take a break and attack this in the AM.
let me know!
New boards came in and I brought one of them up in my setup. Worked fine. So, failure board set aside for now.