Guru meditation error (core 0 panic loadprohibited) when building with log level -> no output

[bewatermyfriendxd]

Hello,

Today I erased the flash of my esp32-wroom device using esptool.ty erase_flash.
Afterwards I uploaded my program which was built before with menuconfig option log level -> no output.

Since then the bootloader still runs succesfully, but after trying to start the app partition the device crashes with the following error:

Code: Select all

Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x400847a9  PS      : 0x00060031  A0      : 0x40082414  A1      : 0x3ffbe590  
0x400847a9: spi_intr at /home/michael/20190206/esp-idf/components/driver/spi_master.c:547

0x40082414: _xt_lowint1 at /home/michael/20190206/esp-idf/components/freertos/xtensa_vectors.S:1154

A2      : 0x3ffb3920  A3      : 0x00000001  A4      : 0x800f9729  A5      : 0x40091dcc  
0x40091dcc: _frxt_int_enter at /home/michael/20190206/esp-idf/components/freertos/portasm.S:119

A6      : 0x04c4b400  A7      : 0x00000001  A8      : 0x00000001  A9      : 0x3ffbe570  
A10     : 0x00000000  A11     : 0x3ffb3934  A12     : 0x3ffbe590  A13     : 0x3ffb3a30  
A14     : 0x00060021  A15     : 0x00060021  SAR     : 0x0000001e  EXCCAUSE: 0x0000001c  
EXCVADDR: 0x00000005  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0xffffffff  
Core 0 was running in ISR context:
EPC1    : 0x400847a9  EPC2    : 0x00000000  EPC3    : 0x00000000  EPC4    : 0x00000000
0x400847a9: spi_intr at /home/michael/20190206/esp-idf/components/driver/spi_master.c:547

Backtrace: 0x400847a9:0x3ffbe590 0x40082411:0x3ffbe5c0 0x40156e99:0x3ffb1cd0 0x400f98b4:0x3ffb1d10 0x400d3451:0x3ffb1d50 0x400d2aba:0x3ffb1da0 0x400d15e8:0x3ffb1dc0 0x4008ff96:0x3ffb1de0

Before I used log level 'Info' and had not any crashes at all.

BTW: Im using secure boot with encrypted flash

I'll appreciate any help in fixing this issue.
Thanks for the support.

[WiFive]

Make your task stack bigger

[yanosz]

Heilo,

I'd seems like I'm running into the same issue using a different firmware. Unfortunately, I don't understand your hint for increasing the task size.

What are refereing to exactly. Is there a build configuration option?

Thanks,
yanosz

[bewatermyfriendxd]

@yanosz
You can modify the size of the task stack in a submenu (dont remember the name) with 'make menuconfig'.
Unfortunately this didnt resolve my problem.

The error occured on my device because of a conflict with the SPI bus.
I use my ESP32 as a SPI master for several slaves. At one line of code I created a task which will feed a watchdog of a peripheral device via SPI. Directly after the task creation I performed another access on the SPI bus. This caused my device to crash. By adding a
vTaskDelay(10) after the first SPI access, I was able to prevent the crash and get my application to start properly. Before I had some implicit delay because of the logging, when I turned off logging, the crash started to occur.