Resolving ESP32 Bluetooth BLE Stack Crashes

What causes this

ESP32 Bluetooth BLE stack crashes are primarily due to improper handling of memory and stack overflows. Specifically, these crashes often occur when the BLE stack runs out of heap memory or when tasks exceed their allocated stack size. In the ESP-IDF, this can be traced to the ESP_ERR_NO_MEM error code, indicative of a failed memory allocation attempt during BLE operations. Another common cause is the mishandling of GATT operations, particularly when sending notifications or responses that exceed the MTU size limit without proper segmentation. The register BT_BLUEDROID_STATUS_ENABLED and the task btu_task often show up in crash logs with stack overflow or access violations when the BLE stack is improperly configured or overwhelmed.

Minimal reproduction

To reproduce the BLE stack crash, consider the following minimal example that improperly configures the BLE stack and attempts to send oversized data:

```cpp

#include

#include

#include

BLEServer* pServer = NULL;

BLECharacteristic* pCharacteristic = NULL;

void setup() {

Serial.begin(115200);

BLEDevice::init("ESP32_CRASH_TEST");

pServer = BLEDevice::createServer();

pCharacteristic = pServer->createCharacteristic(

BLEUUID((uint16_t)0xFFE1),

BLECharacteristic::PROPERTY_NOTIFY

);

pCharacteristic->setValue("Long data that exceeds MTU size. This should crash.");

pCharacteristic->notify();

}

void loop() {

delay(2000);

}

```

Expected Serial Output (Backtrace):

```

Guru Meditation Error: Core 1 panic'ed (Unhandled debug exception)

Register dump:

PC : 0x400d1b9c PS : 0x00060530 A0 : 0x800d0f5a A1 : 0x3ffb1f10

...

ESP_ERR_NO_MEM

```

The fix

To prevent the BLE stack from crashing, ensure that you are handling memory allocations properly and that your data doesn't exceed the maximum allowable MTU size. Here are some code changes:

Before:

```cpp

pCharacteristic->setValue("Long data that exceeds MTU size. This should crash.");

pCharacteristic->notify();

```

After:

```cpp

pCharacteristic->setValue("Short data");

pCharacteristic->notify();

```

Additionally, configure the BLE stack to handle larger MTU sizes if necessary:

```cpp

BLEDevice::setMTU(517);

```

How SerialDoctor catches this

SerialDoctor efficiently connects to your ESP32 via Web Serial and analyzes the crash logs in under 3 seconds. By parsing error codes, stack traces, and register dumps, SerialDoctor instantly identifies memory allocation issues and stack overflows in the BLE stack. Visit serialdoctor.com to diagnose your ESP32 crashes with ease.

Quick checklist

• [ ] Verify BLE heap memory allocation and task stack sizes.
• [ ] Use BLEDevice::setMTU() to adjust MTU size appropriately.
• [ ] Monitor for ESP_ERR_NO_MEM and handle exceptions gracefully.
• [ ] Ensure characteristic data fits within the MTU limit.
• [ ] Regularly check and update your ESP-IDF to the latest stable version.

Seeing this crash on your board right now?

Connect it to SerialDoctor and get a root cause + code fix in under 3 seconds.