BT - ESP32 Dev / Guru Meditation Error: Core 1 panic'ed (StoreProhibited) - OMG 1.5.0

Boards
1

Hello there!

First of all, a big congrats to everyone involved in this great project!

I’m facing Guru Meditation Error: Core 1 panic’ed (StoreProhibited), whenever I try to write BLE characteristics over MQTT to an ESP32 relay. Specifically, when I try to publish something, format like below :

Topic: home/OpenMQTTGateway_ESP32_BLE/commands/MQTTtoBT/config

JSON:

{
“ble_write_address”:“xx:xx:xx:xx:xx:xx”,
“ble_write_service”:“”,
“ble_write_char”:“”,
“ble_write_value”:“1”,
“value_type”:“HEX”,
“ttl”:4,
“immediate”:true }

ESP32 crashes and reboots with error:

Guru Meditation Error: Core 1 panic’ed (StoreProhibited). Exception was unhandled.

Core 1 register dump:
PC : 0x4019348f PS : 0x00060e30 A0 : 0x801935c2 A1 : 0x3ffcfe60
A2 : 0x00000000 A3 : 0x3ffcfef4 A4 : 0x00000001 A5 : 0x00000000
A6 : 0x00ff0000 A7 : 0xff000000 A8 : 0x00000031 A9 : 0x3ffcfe30
A10 : 0x00000000 A11 : 0x3ffcfef4 A12 : 0x00000001 A13 : 0x3ffcfe6c
A14 : 0x000000b7 A15 : 0xb7f5ea07 SAR : 0x00000012 EXCCAUSE: 0x0000001d
EXCVADDR: 0x00000000 LBEG : 0x40091cbd LEND : 0x40091ccd LCOUNT : 0xffffffff

Backtrace: 0x4019348c:0x3ffcfe60 0x401935bf:0x3ffcfe80 0x400e11c9:0x3ffcfea0 0x400e13cf:0x3ffcffc0 0x400e2622:0x3ffd0000 0x400e26e7:0x3ffd03d0 0x401b09ef:0x3ffd03f0 0x400e3b2d:0x3ffd0410 0x400df9e1:0x3ffd0450 0x40103b35:0x3ffd0470

Any help would be much appreciated.

Thank you

Konstantinos

2

Hello @halk1982,

While someone else will be better suited to address and investigate the Guru Meditation Error you are experiencing, I’d still like to point out a possible missing "mac_type" in the write command, if it might be different from the default "mac_type":0 for your device.

You can view the mac_type in the device’s advertising broadcasts when you set pubadvdata to true, as described at

3

Hello @DigiH,

Thank you very much for your response. I just followed your advice and found out that mac_type is indeed 0, therefore default should be ok (check below):

image
image750×140 32.5 KB

Any other thoughts/ideas are more than welcome.

Thank you

4

Hello,

What is the log saying before the Guru Medication Error ?

5

I think this is unrelated to your issue. But for what it’s worth, we also saw a Guru Meditation error in the ESP32-C3 experiments. There it was related to the FastLED code. We fixed it by disabling FastLED, see FastLED seems broken for ESP32C3 boards.

6

Hello @1technophile ,

Thank you very much for your reply. I’m pasting below the complete logfile (write after the first line, I’m sending the MQTTtoBT command and on the second line and after you see the crash and reboot):

N: Found 15 devices, scan number 1 end
N: [ MQTT->OMG ]: {“ble_write_address”:“40:91:51:ba:d1:b2”,“ble_write_service”:“4fafc201-1fb5-459e-8fcc-c5c9c331914b”,“ble_write_char”:“beb5483e-36e1-4688-b7f5-ea07361b26a8”,“ble_write_value”:“01”,“value_type”:“HEX”,“ttl”:4,“immediate”:true}
N: Send on /BTtoMQTT msg {“bleconnect”:true,“interval”:55555,“adaptivescan”:true,“intervalacts”:55555,“intervalcnct”:3600000,“scanduration”:10000,“onlysensors”:false,“randommacs”:false,“hasspresence”:false,“presenceTopic”:“presence/”,“presenceUseBeaconUuid”:false,“minrssi”:-100,“extDecoderEnable”:false,“extDecoderTopic”:“undecoded”,“filterConnectable”:false,“pubadvdata”:false,“pubBeaconUuidForTopic”:false,“ignoreWBlist”:false,“presenceawaytimer”:120000,“btqblck”:2,“btqsum”:5,“btqsnd”:2,“btqavg”:2.5}
Guru Meditation Error: Core 1 panic’ed (StoreProhibited). Exception was unhandled.

Core 1 register dump:
PC : 0x40090ff5 PS : 0x00060e30 A0 : 0x801933f9 A1 : 0x3ffcfe30
A2 : 0x00000000 A3 : 0x3ffcfef6 A4 : 0x00000002 A5 : 0x00000000
A6 : 0x00003130 A7 : 0x00000000 A8 : 0x00000000 A9 : 0x3ffcfdf0
A10 : 0x3ffcfef4 A11 : 0x3fff519b A12 : 0x00000002 A13 : 0x0000ffff
A14 : 0x00000000 A15 : 0x0000ffff SAR : 0x00000018 EXCCAUSE: 0x0000001d
EXCVADDR: 0x00000000 LBEG : 0x40090fb0 LEND : 0x40090fc6 LCOUNT : 0xffffffff

Backtrace: 0x40090ff2:0x3ffcfe30 0x401933f6:0x3ffcfe40 0x40193495:0x3ffcfe60 0x401935bf:0x3ffcfe80 0x400e11c9:0x3ffcfea0 0x400e13cf:0x3ffcffc0 0x400e2622:0x3ffd0000 0x400e26e7:0x3ffd03d0 0x401b09ef:0x3ffd03f0 0x400e3b2d:0x3ffd0410 0x400df9e1:0x3ffd0450 0x40103b35:0x3ffd0470

ELF file SHA256: cf9ffdc7b906fcf4

Rebooting…
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (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:0x3fff0030,len:1184
load:0x40078000,len:13192
load:0x40080400,len:3028
entry 0x400805e4
N:
************* WELCOME TO OpenMQTTGateway **************
N: OpenMQTTGateway Version: version_tag
N: Config uselaststate unchanged: true
N: Config cmd unchanged: true
N: ONOFF config loaded
N: Target state on restart: true
N: Use last state on restart: true

After reboot, everything’s back to normal and there is no crash or any other issue as long as I’m not trying to write BLE characteristics over MQTT.

Hope that helps

Thanks

Konstantinos

7

Hello @argafal ,

Thanks for sharing this one, feels unrelated though, you are right.

8

Have anybody found the solution? I have the same issue: OpenMQTTGateway running on ESP32 crashes when I try to write BLE characteristic (the same sympthomps and message). I tried various things suggested on this forum and other. Nothing helps.
I have OMG v1.6.0 on ESP32 (first chip version I believe, wroom dev board) and installed ready-to-go binaries esp32dev-ble-*.bin

Does anybody know the solution?