-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
ESP32-S3 Powercycling right after uploading a sketch using Arduino IDE and Arduino Core 2.0.4 #7165
Comments
Can it be related to #7125 ? |
The S3 that works fine has this output and doesn't reset:
|
Both seem to be exactly the same CHIP! Both have the same output when booting, but one of them keeps restating after 1st stage bootloader. But, when I run IDF HelloWorld example.... it works perfectly well in both boards. |
Using IDF 4.4.1, I can run it on Both bards. Log Output for the "Good board" is
|
IDF 4.4.1 Log Output for the "BAD board" is
|
Comparing IDF output for both boards.... there is no difference. Both work fine under IDF. |
Testing it with all possible ESP32-S3 Arduino Cores (upload speed minimum at 115200):
@me-no-dev --- This seems to be a REGRESSION. |
@SuGlider Have you tried PlatformIO? Install is done in a few minutes if you have not used before. If both devices runs with Platformio and core 2.0.4. it is probably Arduino IDE. |
Hi @Jason2866 - Thanks for the suggestion. Same issue. Power Cycle - reseting. platformio.ini
|
From the Platform.txt in the PIO environment I can tell that it is using Core 2.0.4 to build it. |
Can you please try:
i did some changes in Platformio to use latest esptool v4.2.1 and some small fixes which are not in the official Platformio espressif32 framework. |
@Jason2866 - Same problem... power cycle. PIO Terminal Ouput:
|
Weird, and the other device works here too? This "2MB" is more than fishy in the log !!
|
Yes.... That's really weird... I think that the issue lies on something related to the second-stage bootloader, because it fails with WDT. |
Another important information is that both boards work with Arduino Creo 2.0.3... which has the "wrong" S3 bootloader. |
Mhh, another strange thing. I builded a framework where the IDF bootlog is enabled. This does work as it should for the ESP32, ESP32-S2 and the ESP32-C3 and i see messages from the 2nd stage bootlloader. |
And why is it Flash Mode |
Already tried it. No change. |
@me-no-dev I have this error log message during a framework build run with the arduino lib builder. It does not stop the building.
Idk if this is related, anyhow it is not nice to see |
@Jason2866 this is unrelated and probably caused by awk version or file encoding/line endings |
This issue will be investigated at the end of September, it's postponed due to HW location. |
Any idea how to get logs from the 2nd stage bootloader for the S3 ? |
I come to the comclusion that OPI flash mode is not working whether in IDF nor in Arduino. Probably OPI device crashes since the init procedure is missing OPI support. |
@Jason2866 no issue with OPI here |
@me-no-dev How do you know it is really! running in mode OPI? Thats why i made the PR (flash mode detection) since we did not know for Edit: Still the question is not answered. Why are no bootlogs possible with the S3 ? |
@Jason2866 OPI can run only in OPI mode. Performance improvement is also visible. What kind of sign do you need? Try to boot OPI chip in another mode and you will see :) There are no more inconsistencies in flash modes in Arduino. That has all been fixed (in bootloaders and linked libs). How are you trying to enable boot logs? |
@me-no-dev In IDF sdkconfig. Used a simple Blink sketch. Got bootlogs for ESP32, ESP32-C3 and ESP32-S2. For ESP32-S3 no way to get something. |
@Jason2866 you can poke IDF team about that, though I see no reason... you are using the UART port right? Not the USB one? |
Yes, Uart and i have connected for tests the USB port too to a terminal.
I am sarcastic, this issue is not real? |
@Jason2866 issue here is something totally different. We do not know yet what is causing it. It happens so far on only one board that @SuGlider has. |
Sorry for double postings. Internet issues |
No not a single issue, a team member from us (Tasmota @Staars) has the same issue. His board a S3 maple eye doing the same bootloop. |
That's quite important info. |
### Releases v1.3.0 1. Remove hard-code if possible 2. Improve debug messages by adding functions to display `error/state messages` instead of `cryptic error/state number` 3. Clean up 4. Add support to `ESP32_S3`, using ESP32 core `v2.0.3`. **Don't use `ESP32_S3` with core v2.0.4**. Check [ESP32-S3 Powercycling right after uploading a sketch using Arduino IDE and Arduino Core 2.0.4 #7165](espressif/arduino-esp32#7165)
### Releases v1.3.0 1. Remove hard-code if possible 2. Improve debug messages by adding functions to display `error/state messages` instead of `cryptic error/state number` 3. Clean up 4. Add support to `ESP32_S3`, using ESP32 core `v2.0.3`. **Don't use `ESP32_S3` with core v2.0.4**. Check [ESP32-S3 Powercycling right after uploading a sketch using Arduino IDE and Arduino Core 2.0.4 #7165](espressif/arduino-esp32#7165)
@SuGlider Please write what have been investigated and what is current resolution. |
The issue was related to a bad SoC. |
Board
ESP32-S3
Device Description
ESP32-S3-DevkitC-1 1.0
Hardware Configuration
None
Version
v2.0.4
IDE Name
Arduino IDE 1.8.15
Operating System
Windows 11
Flash frequency
QIO 80MHz
PSRAM enabled
no
Upload speed
Tried 115200 and 921600
Description
I have two, apparently equal, ESP32-S3 boards.
For one of them I can upload any sketch and it works fine right after reset.
The other one keeps reseting after uploading and I can't make it work.
BUT.... when I use IDF examples (HelloWorld and Blink RGB LED) both works fine!
So it seems that something may be wrong with Arduino second-stage bootloader or some boot configuration.
No error message even with DEBUG turned on.
IMPORTANT NOTE: it runs fine with Arduino Core 2.0.3 but fails with 2.0.4 --- REGRESSION
Sketch
Debug Message
Other Steps to Reproduce
As simple as that. I get TG0WDT_SYS_RST or RTCWDT_RTC_RST in the second-stage bootloader execution.
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: