Persistent Boot Failure on ESP32-S3 #9874
Comments
|
Yes, I looked carefully before posting the issue and it seems that I'm the first with this problem. I can't go back to version 2, I've already migrated my firmware to version 3 and it's not possible to build it. As I'm an idiot, when I updated I didn't look to see which commit I was on... I'm currently testing them one by one to see when the bug appeared. If I find it, I'll post the info here. If it can help here my plaformio.ini : |
|
remove the not working settings in build_flags. This are compile time settings only working with IDF. The are useless with Arduino. Pin the used Arduino libs with commit SHA I personally wouldn't use the Adafruit boards.json at all since it uses the imho flash wasting |
|
OK I'm going to test the build flag, but it's not my choice to use Adafruit board json, for this specific chip I don't know what to use as a board file. If you have one to recommend to me, I'm open ! Edit : |
|
copy this one in folder |
|
If it still bootloops one of your used libraries is to blame. Probably the breaking change PR #9453 introduces problems in many extern libraries |
|
Can you disable anything related to PSRAM? |
|
|
|
@me-no-dev As far as I know is that he reported he is unable to flash this board using the web flasher. |
|
I've tested it with @Jason2866 new board file (thanks for that), but the bug is exactly the same. BUT I disabled the PSRAM by removing the flag in the board file and the problem disappeared. So it's the PSRAM management that's at fault here. It's a bit off the subject for this issue (if I find the time I'll do an issue on it), but on master the WiFi isn't working at all, and it's impossible to enable WPS. I think it's because there is no more ram |
|
How was the PSRAM configured? Can you compare your board JSON with what I'm using for 4M S3 boards: {
"build": {
"arduino":{
"ldscript": "esp32s3_out.ld",
"memory_type": "qio_qspi"
},
"core": "esp32",
"extra_flags": "-DARDUINO_TASMOTA -DBOARD_HAS_PSRAM -DARDUINO_USB_MODE=1 -DUSE_USB_CDC_CONSOLE -DESP32_4M -DESP32S3 -DARDUINO_USB_CDC_ON_BOOT=1",
"f_cpu": "240000000L",
"f_flash": "80000000L",
"flash_mode": "qio",
"hwids": [
[
"0x303A",
"0x1001"
]
],
"mcu": "esp32s3",
"variant": "esp32s3",
"partitions": "boards/partitions/esp32_partition_app1810k_spiffs316k.csv"
},
"connectivity": [
"wifi",
"bluetooth",
"ethernet"
],
"debug": {
"default_tool": "esp-builtin",
"onboard_tools": [
"esp-builtin"
],
"openocd_target": "esp32s3.cfg"
},
"frameworks": [
"espidf",
"arduino"
],
"name": "Espressif Generic ESP32-S3 USB CDC >= 4M Flash QSPI PSRAM, ESPEasy 1810k Code/OTA 316k FS",
"upload": {
"flash_size": "4MB",
"maximum_ram_size": 327680,
"maximum_size": 4194304,
"require_upload_port": true,
"before_reset": "usb_reset",
"speed": 460800
},
"url": "https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/hw-reference/esp32s3/",
"vendor": "Espressif"
}You may have some options different, like partitions and maybe some specific flags. |
|
You can see mine here : #9874 (comment) |
|
Then I honestly have no idea why it would not work with PSRAM enabled. |
It is, because we did not change anything that can influence the result. You say you can not debug, how come? What do you get in Serial? |
|
Thanks for the feedback, @me-no-dev. You mentioned that the issues might be linked to precompiled libraries, as there have been no changes that could directly affect this outcome. However, I'm facing a lack of serial output post-crash, which complicates pinpointing the exact cause. Here the only message I get from the serial : And it's restart loop like this. Here’s a quick rundown of what I’m observing:
Could you clarify if there have been any recent changes in the ESP-IDF that might affect memory or PSRAM handling specifically? Or where I can search for that ? Maybe I need to post my issue somewhere else ? Also, are there recommended tools or methods for diagnosing this issue more effectively in the absence of clear serial debug outputs? |
I can not. We can not follow the changes in ESP-IDF. Big project, many people and changes.
ESP-IDF's issue tracker is a good place to post such issue with all details that you have figured out thus far. |
|
Ok, I will try to post my issue over there. |
Board
ESP32-S3-WROOM-1U-N4R2
Device Description
Plain module
Hardware Configuration
Irrelevant
Version
v3.0.1
IDE Name
PlatformIO
Operating System
Linux Ubuntu 22.04
Flash frequency
80
PSRAM enabled
yes
Upload speed
115200
Description
Hello,
I am experiencing a consistent boot failure issue with my ESP32-S3, regardless of the complexity or simplicity of the firmware I attempt to upload. This issue persists across both my pretty complex custom firmware and basic example code, such as the WiFi connection example. The behavior suggests a fundamental problem related to the boot process.
Issue Description
The device fails to boot properly. The error message that is consistently output is as follows:
My point of view is that it's linked to the model chip I have.
I'm currently stuck on this model of chip, but it's not the first time I've had to unravel memory-related boot problems with this model of chip ESP32-S3-WROOM-1U-N4R2.
Additional Context
This seems to be a regression or a newly introduced bug associated with the latest updates. Any guidance or suggestions on how to mitigate this issue would be greatly appreciated. Thank you for your attention to this matter.
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: