Espressif HAL5.1 - Core panic'ed on EPS32S3 with hello_world sample #71397
Comments
|
Hi @Piziwate! We appreciate you submitting your first issue for our open-source project. 🌟 Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙 |
|
@Piziwate would you please sync your main to latest, run |
|
@sylvioalves I reinstalled everything, to the latest version, but the problem persists! I'm getting exactly the same error. Which ESP32 did you test on? In my case, I can get the hello_world to work fine on a regular ESP32, but no success on the ESP32S3. Could it be related to the fact that my module has 32Mb of flash and 8Mb of PSRAM? |
|
@Piziwate I used a N16R8 here, not N32R8. Let me check again, the issue you described sounds related to octal flash. |
|
@Piziwate you mentioned this is a custom board. Is it using USB interface or there is a usb-serial converter? That would explain things. |
|
@sylvioalves Yes, I'm using USB (uart0 is available on a debug header, but currently not used) |
|
@Piziwate I was able to reproduce now in a octal flash SPI (same as yours). Will check the issue. |
|
@sylvioalves Whether octal SPIRAM has been resolved. If not, is it possible to refine it together? |
|
@sylvioalves Do you have any news regarding this bug? I'm really stuck because of it! I'm willing to help but I admit I don't really know where to start looking! |
|
I am currently stuck at a similar looking issue with my So maybe it's not the transition to HAL 5.1 that is causing the problem? I see two kinds of log output on problematic commits: and on later commits (e.g. I hope this helps. Any news regarding fixes? @sylvioalves |
|
Edit: Can you fetch latest main and re-check it? |
|
latest main (1159c2a) does not work, see second variant of log output |
|
Would you also test this change? zephyrproject-rtos/hal_espressif#297 |
|
Still getting a boot loop, unfortunately: Tested with |
|
Which board is that? |
|
A supposedly ESP32-S3-DevKitC-1 compatible board off of Amazon, branded DollaTek. Supposedly contains an ESP32-S3-WROOM-1-N16R8, according to the engraving on the ESP module. |
|
@sylvioalves , I don't know if your modifications also concerned my issue. I ran a test again this morning and I'm still experiencing continuous restarts with the same message! |
|
I got the same issue on latest main, anything new ? |
|
I also have the same issue (genuine ESP32-S3-DevKitC-1 v1.1) and from the module marking it has a ESP32-S3-WROOM-2-N32R8V module... |
|
I am also eager for a fix. If anyone has a workaround please share! |
|
FWIW it appears that it was fixed (there are a few recent commits in the Espressif's hal): |
|
Very glad to hear that. Indeed the current In the ESP HAL, a bisect between the commit from the HAL update reveals that commit This commit is not currently on @sylvioalves any chance to get this change backported? I would love to be able to use the LTS release on my ESP32S3. |
|
@celinakalus Sounds we should. Although that change fixed the issue, I do need to verify it properly. |
ESP32-S3 initialization code should apply the errata after cache initialization. This fixes it making sure data and cache instruction are properly handled and let following calls to work as needed. This also update hal_espressif to force gcc to treat register bitfield structs declared as volatile to ensure writes on 32 bit peripheral registers. Fixes zephyrproject-rtos#71397 Fixes zephyrproject-rtos#76325 Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com>
ESP32-S3 initialization code should apply the errata after cache initialization. This fixes it making sure data and cache instruction are properly handled and let following calls to work as needed. This also update hal_espressif to force gcc to treat register bitfield structs declared as volatile to ensure writes on 32 bit peripheral registers. Fixes #71397 Fixes #76325 Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com>
|
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Describe the bug
When I compile the hello_world example with the main version of Zephyr, the MCU crashes. This issue has arisen since a few days ago (transition to HAL5.1).
I'm using a custom board based on the ESP32S3 SOC (ESP32-S3-WROOM-2-N32R8V), but to check I used the board esp32s3_devkitc/esp32s3/procpu in Zephyr, since hello_world doesn't use any external hardware and drivers.
Compiled with :
west build -b esp32s3_devkitc/esp32s3/procpu .\samples\hello_world --pristineTo Reproduce
Steps to reproduce the behavior:
Impact
Zephyr doesn't start well. (Guru Meditation Error: Core 0 panic'ed (IllegalInstruction))
Logs and console output
and booting in a loop !
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: