ESP32 Forum

I am trying to set up a simple bluetooth SPP profile communication with an industrial device via a serial interface. For this I am basically using the example from the BT-SPP-ACCEPTOR demo. Using this I am transferring short data frames in an inquiry and reply manner. Initially this works but after some time (e.g. 20seconds) I get error messages from the BT stack like:

E (31115) BT_OSI: alarm_set failed to start timer, err 0x103

These messages appear from time to time while the BT communication continues.
Unfortunately after some more time (e.g. 2 minutes) the ESP32 crashes with the error message:

ASSERT_ERR(0), in lc_lmppdu.c at line 66
Guru Meditation Error: Core 0 panic'ed (Interrupt wdt timeout on CPU0)
Core 0 register dump:
PC : 0x40086314 PS : 0x00060134 A0 : 0x8001c21a A1 : 0x3ffcec30

This is a log of the error messages only:

This is ESP32 chip with 2 CPU cores, WiFi/BT/BLE, silicon revision 1, 4MB external flash
ESP-IDF Version: v3.3-beta1-136-g97eecfa1b
W (12942) BT_APPL: new conn_srvc id:26, app_id:255
E (16538) BT_OSI: alarm_set failed to start timer, err 0x103

E (38741) BT_OSI: alarm_set failed to start timer, err 0x103

E (62163) BT_OSI: alarm_set failed to start timer, err 0x103

E (84275) BT_OSI: alarm_set failed to start timer, err 0x103

E (106456) BT_OSI: alarm_set failed to start timer, err 0x103

E (128690) BT_OSI: alarm_set failed to start timer, err 0x103

ASSERT_ERR(0), in lc_lmppdu.c at line 66
Guru Meditation Error: Core 0 panic'ed (Interrupt wdt timeout on CPU0)

I monitored this behaviour now many times. It is always the same picture: the error "err 0x103" appears roughly every 23 seconds and after the 6th time the ESP32 crashes.

Does someone have any idea where this comes from? What shall I do?

Does nobody have an idea how to solve this issue?

I am running into a similar issue, although it is not happening as frequently to me.

Have you had any luck in trying to resolve this issue?

With the latest version of esp-idf it seems to work (at least much better than before). But maybe I changed something unintentionally. One difference I have compared to my previous version that now freertos is working at 10ms and not at 1ms (like before). But I don't know if this is makes the difference.