ESP32_S3_N18R8—There is a burning problem

[DouerGan]

ELF file SHA256: a8daf50913e68211
Rebooting
O◆ESP- ROM: esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_ SW_ CPU_ RST) ,boot:0xa (SPI_ FAST_ FLASH BOOT)
Saved PC: 0x420dab2e
SPIWP: 0xee
mode:DIO, clock div:1
load: 0x3fcd0108, len: 0xf0c
load: 0x4 03b6000, len: 0xc2c
load: 0x403ba000，len: 0x2d44
SHA-256 comparison failed:
Calculated: 0b08bcd0ee 62aab8a2d117a35c50157b3c34e 66ad044d69b50d82369295927df
Expected: 9ba 8b312dccaa6ae5672707a3d684d03df04730664 f77be9191913302360b453
Attempting to boot anyway .
entry 0x403b61f4
E(242) psram: PSRAM ID read error: OxOOfffff
E(242) spi ram: SPI RAM enabled but initia lization fai led. Bai 1 ing out.
E(10) spiram: SPI RAM not initial i zed
abort ( ) was called at PC 0x42005f7c on core 1
Backt race : 0x403 75b6a: 0x3 fce 4b900x40380b29:0x3fce4bb00x40386e86:0x3fce4bd0 0x42005f7c:0x3fce4c40 0x42006743 : 0x3 fce4c60

[DouerGan]

I changed it to SPI FALSH 8MB on the basis of 'build-generic_s3_spiram', the hardware used is ESP32 N16R8 module, but error was reported
error 242 and 10

[tepalia02]

Not sure, but you may get some clues from here: https://www.esp32.com/viewtopic.php?t=26078
You can raise your issue in github too.