ESP32 Forum

I encountered an issue where my central device could connect to my peripheral but was unable to read any of my characteristics on my peripheral. I was initially able to connect and read my characteristics with no issues but eventually ended up with this issue. I was able to resolve this by completely erasing the flash on my esp32 and re-flashing the same firmware. My initial thoughts is that it could be memory related but I am not entirely sure. Could anyone who has worked with Nimble BLE have any input on what could cause this on an esp32? For more context I have my BLE operations running in a FreeRTOS task.

Memory issues could be one of the potential reasons. It's possible that your application is leaking memory or not freeing up memory properly, which can lead to memory fragmentation and eventually cause the BLE stack to behave unexpectedly. You can use heap memory profiling tools like ESP-IDF's heap_caps_get_free_size() function to check the available heap memory and identify any memory leaks or fragmentation issues.