Open Piziwate opened 2 months ago
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 west update
and then west blobs fetch hal_espressif
? At least to make sure we have the same env. It works in here.
@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? Could you share your boot prompt for comparison purposes?
@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 esp32s3_devkitc
, Core is panicking on hello_world
sample. I can confirm it works on the commit where initial board support was added. git bisect
tells me:
a54f3832f5fc8fae55198045949e1991b3261450 is the first bad commit
commit a54f3832f5fc8fae55198045949e1991b3261450
Author: Marek Matej <marek.matej@espressif.com>
Date: Wed Jan 31 20:18:02 2024 +0100
kconfig.zephyr: Remove ESP_IDF bootloader option
Remove ESP_IDF bootloader option.
Default boot method is simple boot.
Signed-off-by: Marek Matej <marek.matej@espressif.com>
Kconfig.zephyr | 9 ---------
1 file changed, 9 deletions(-)
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:
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x403cdd3d
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3818,len:0x1664
load:0x403c9700,len:0x4
load:0x403c9704,len:0xb74
load:0x403cc700,len:0x2e8c
entry 0x403c98fc
I (31) boot: ESP-IDF v5.1-dev-3972-g1559b6309f 2nd stage bootloader
I (31) boot: compile time Mar 15 2023 12:14:10
I (32) boot: chip revision: v0.2
I (36) boot.esp32s3: Boot SPI Speed : 80MHz
I (41) boot.esp32s3: SPI Mode : DIO
I (45) boot.esp32s3: SPI Flash Size : 4MB
I (50) boot: Enabling RNG early entropy source...
I (56) boot: Partition Table:
I (59) boot: ## Label Usage Type ST Offset Length
I (66) boot: 0 factory factory app 00 00 00010000 00100000
I (74) boot: End of partition table
E (78) esp_image: image at 0x10000 has invalid magic byte (nothing flashed here?)
E (86) boot: Factory app partition is not bootable
E (92) boot: No bootable app partitions in the partition table
and on later commits (e.g. 7477636f0f9
):
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x7 (TG0WDT_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40050f3f
SPIWP:0xee
mode:DIO, clock div:2
load:0x3fc8d1f0,len:0x186c
load:0x40374000,len:0x91d0
SHA-256 comparison failed:
Calculated: f95d0f487ccb304b1dd846f910286b316bbdea6a20fd5784ce8741de861e8558
Expected: 0000000080550000000000000000000000000000000000000000000000000000
Attempting to boot anyway...
entry 0x4037779c
I (68) boot: ESP Simple boot
I (68) boot: compile time Jun 28 2024 17:49:44
W (68) boot: Unicore bootloader
I (69) spi_flash: detected chip: generic
I (70) spi_flash: flash io: dio
W (73) spi_flash: Detected size(16384k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I bootloader_flash: XM25QHxxC startup flow
E bootloader_flash: XMC flash startup fail
E (93) boot.esp32s3: failed when running XMC startup flow, reboot!
[esp32s3] [ERR] HW init failed, aborting
Guru Meditation Error: Core 0 panic'ed (IllegalInstruction)
Core 0 register dump:
PC : 0x4200202c PS : 0x00060730 A0 : 0x80045c04 A1 : 0x3fceb550
A2 : 0x00000011 A3 : 0x3ff1b1c2 A4 : 0x00000020 A5 : 0x00010000
A6 : 0x00010000 A7 : 0x0000aa90 A8 : 0x803777b4 A9 : 0x3fceb500
A10 : 0x0000002a A11 : 0x3fc8d481 A12 : 0x3fc8ea5c A13 : 0x600080b8
A14 : 0x00000008 A15 : 0xffffffff SAR : 0x00000004 EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x4037833d LEND : 0x40378341 LCOUNT : 0x00000000
Backtrace: 0x4200202c:0x3fceb550 0x40045c01:0x3fceb570 0x40043ab6:0x3fceb6f0 0x40034c45:0x3fceb710
I hope this helps. Any news regarding fixes? @sylvioalves
Edit: Can you fetch latest main and re-check it?
latest main (1159c2addaac) does not work, see second variant of log output
Would you also test this change? https://github.com/zephyrproject-rtos/hal_espressif/pull/297 I don't have a board with that particular XMC type right now to test it.
Still getting a boot loop, unfortunately:
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x7 (TG0WDT_SYS_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40050f3f
SPIWP:0xee
mode:DIO, clock div:2
load:0x3fc8d338,len:0x181c
load:0x40374000,len:0x9318
SHA-256 comparison failed:
Calculated: fa8b442bfad2529b395d9cf63152ed402cecaf4f5b0f559058e9962b92d550e9
Expected: 0000000090540000000000000000000000000000000000000000000000000000
Attempting to boot anyway...
entry 0x40377864
I (68) boot: ESP Simple boot
I (68) boot: compile time Jun 28 2024 18:20:31
W (69) boot: Unicore bootloader
I (69) spi_flash: detected chip: generic
I (70) spi_flash: flash io: dio
W (73) spi_flash: Detected size(16384k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I bootloader_flash: XM25QHxxC startup flow
E bootloader_flash: XMC flash startup fail
E (93) boot.esp32s3: failed when running XMC startup flow, reboot!
[esp32s3] [ERR] HW init failed, aborting
Guru Meditation Error: Core 0 panic'ed (IllegalInstruction)
Core 0 register dump:
PC : 0x42001ec8 PS : 0x00060730 A0 : 0x80045c04 A1 : 0x3fceb550
A2 : 0x00000011 A3 : 0x3ff1b1c2 A4 : 0x00000020 A5 : 0x00010000
A6 : 0x00010000 A7 : 0x0000ab80 A8 : 0x8037787c A9 : 0x3fceb500
A10 : 0x0000002a A11 : 0x3fc8d5c9 A12 : 0x3fc8eb54 A13 : 0x600080b8
A14 : 0x00000008 A15 : 0xffffffff SAR : 0x00000004 EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x40378405 LEND : 0x40378409 LCOUNT : 0x00000000
Backtrace: 0x42001ec8:0x3fceb550 0x40045c01:0x3fceb570 0x40043ab6:0x3fceb6f0 0x40034c45:0x3fceb710
Tested with main
(1159c2addaac) plus modified west.yml
.
=== updating hal_espressif (modules/hal/espressif):
HEAD is now at 7cdf0b4a8e test: flash: add XMC flash ID
WARNING: left behind hal_espressif branch "bugfix/xmc_flash"; to switch back to it (fast forward):
git -C ../modules/hal/espressif checkout bugfix/xmc_flash
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!
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 --pristine
To 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):