Inkplate 6 Plus crashes with Guru Meditation Error when SD card inserted

Customer:

I received my Inkplate 6 Plus and when I insert an SD card, the device crashes with Core panic errors. The screen flashes and I get these messages on the serial monitor. Without an SD card, everything works fine. I tested with 2 different SD cards formatted in FAT32.

The error output:

ets Jun 8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x32 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x32 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1100
load: ,len:10900
load: ,len:6360
entry 0x400806b4
SD Card OK! Reading image...
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC : 0x400de286 PS : 0x00060d30 A0 : 0x800da3c3 A1 : 0x3ffcca60
A2 : 0x0000003f A3 : 0x000000ff A4 : 0x0000003f A5 : 
A6 : A7 : 0x3ffcacc0 A8 : A9 :
A10 : A11 : A12 : A13 :
A14 : A15 : 0x3ffcacc0 SAR : 0x0000000a EXCCAUSE: 0x0000001c
EXCVADDR: LBEG : 0x4000c349 LEND : 0x4000c36b LCOUNT :
ELF file SHA256:
Backtrace: 0x400de286:0x3ffcca60 0x400da3c0:0x3ffcca80 0x400d6cf5:0x3ffccaa0 0x400d70a4:0x3ffccac0 0x400d599e:0x3ffccae0 0x400d41a0:0x3ffccb10 0x400d4212:0x3ffccb60 0x400d3bc9:0x3ffccbb0 0x400d2060:0x3ffccbe0 0x400df8e2:0x3ffccc10 0x4008aaea:0x3ffccc30
Rebooting...
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x32 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1100
load: ,len:10900
load: ,len:6360
entry 0x400806b4
SD Card OK! Reading image...
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC : 0x400de286 PS : 0x00060d30 A0 : 0x800da3c3 A1 : 0x3ffcca60
A2 : 0x0000003f A3 : 0x000000ff A4 : 0x0000003f A5 : 0x000087c0
A6 : 0x000000ff A7 : 0x3ffcacc0 A8 : A9 :
A10 : A11 : A12 : A13 :
A14 : A15 : 0x3ffcacc0 SAR : 0x0000000a EXCCAUSE: 0x0000001c
EXCVADDR: LBEG : 0x4000c349 LEND : 0x4000c36b LCOUNT :
ELF file SHA256:
Backtrace: 0x400de286:0x3ffcca60 0x400da3c0:0x3ffcca80 0x400d6cf5:0x3ffccaa0 0x400d70a4:0x3ffccac0 0x400d599e:0x3ffccae0 0x400d41a0:0x3ffccb10 0x400d4212:0x3ffccb60 0x400d3bc9:0x3ffccbb0 0x400d2060:0x3ffccbe0 0x400df8e2:0x3ffccc10 0x4008aaea:0x3ffccc30
Rebooting...
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x32 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1100
load: ,len:10900
load: ,len:6360
entry 0x400806b4

Originally submitted via email support on 7 January 2022. Migrated to the forum for community visibility.

Customer:

After multiple on/off cycles and reloading the examples, the error is now gone and one of the SD cards is recognized.

Soldered Support:

The SD card registers as OK on the serial monitor, so the problem occurs when trying to read the image, which causes the ESP to reset. This suggests corrupted memory on the ESP, or the code attempting to write to a memory address that is not allowed to be written to. Since reloading the code multiple times resolved the issue, it was likely a case of corrupted memory that cleared after the reloads.