Below is the screen dump....

I believe the IDF supports up to 7 connections. It is an option the the "make menuconfig"

The same crash again with another dump.... =============================================================== ==================== ESP32 CORE DUMP START ==================== ================== CURRENT THREAD REGISTERS =================== pc 0x40084835 0x40084835 <r_assert_param+309> lbeg 0x4008476d 107...

I have a similar issue ASSERT_PARAM(2051 0), in llc_util.c at line 289 Guru Meditation Error: Core 0 panic'ed (Interrupt wdt timeout on CPU0) BLE is running on core 0 The core dump ==================== ESP32 CORE DUMP START ==================== ================== CURRENT THREAD REGISTERS ===========...

I have also experienced both of these crashes.
In my example I am connecting and disconnecting to two BLE sensors and then sending the data over wifi to a server. I basically only have two tasks running, so nothing too complex...

I am still suffering from this issue, I do however have a better thread trace which has pointed me into the place were the crashing is always occurring. When calling the function esp_ble_gattc_write_char_descr() in the callback to ESP_GATTC_REG_FOR_NOTIFY_EVT the data which is passed through to this...

Using IDF 3.1 I am observing a Load Prohibited unhanded exception, whilst running some ble and wifi code. Analysing the core dump yields the following. The crash takes some time to occur and seems that the function which is causing the crash is within the IDF (L2CA_CheckIsCongest). Any ideas? ======...

I seem to have miss interpreted the dump, from what I understand it is that the idle task was never able to kick the task watchdog. Since posting this issue I have possibly eliminated this crash from happening by the following; - Pinning bluedroid and BLE to core 0 - I had a task which was starting ...

Currently I have a project running BLE connecting to a few sensors, making a measurement and then dropping the connection. I am running into an issue were a bit of pre compiled code is getting stuck and triggering the watchdog. It seems strange though since it is saying that CPU 1 is in the idle tas...