Thank you @jhnlmn @ESP_Angus for your valuable inputs. I have raised an internal MR to address this issue.

Glad that your problem was solved !!

@colinives , It looks a little strange to be honest. Are you conducting experiments in a very noisy RF environment ? Can you please confirm if you are facing this issue only for specific phone/model (e.g. iPhone6) ? Can you please provide debug logs with enabling debug logs from menuconfig ? Please ...

@shirogeek, Apologies for delayed response. Can you please try following points:

Though highly unlikely but as a starting debug point can you please increase NIMBLE_STACK size from 512 to say 4096 (`CONFIG_BT_NIMBLE_TASK_STACK_SIZE`)?


I suspect the error might be coming from `ble_buf_alloc ...

Hi @iosixllc ,
f I initialize wifi and then call esp_nimble_hci_and_controller_init() I get an abort. If I initialize NIMBLE and then call esp_wifi_start() I get an abort as well. I've pulled the trace but the stack is corrupted

I could not reproduce the issue, I used `bleprph` example for ...

Hi @nirmal.lad,

From logs, I do not see any obvious issue, except Disconnection Complete: status=0 handle=0 reason=8
disconnect; reason=520
The disconnection is happening because of supervision timeout or BLE_ERR_CONN_SPVN_TMO . Now in your application code, I do not see anything after service ...

Hi @nirmal.lad,

I could see the encryption state changed to encrypted in your logs

Encrypt change: status=0 handle=0 state=1


I don't see any issue with pairing/bonding from BLE central.

From the logs, I could see disconnection reason = 546, which is BLE_ERR_LMP_LL_RSP_TMO(LMP Response ...

Hi @nirmal.lad, It seems I referred to some other log and made that last comment. Sorry for that, please disregard my earlier comment. Can you please provide complete logs after `make erase_flash flash monitor` again ? I could only think of reason for this error might be because you are switching ...

Hi @nirmal.lad,

Could you please confirm that you are not enabling `BLE_SM_PAIR_KEY_DIST_ID` for key distribution ?
Though I can see from your code that ble_hs_cfg.sm_our_key_dist = 1;
However from the logs I can see rxed sm command: id addr info; conn=0 addr_type=0 addr=40:9c:28:d2:67:93 which is ...

Thank you for the logs @nirmal.lad

From your logs

error persisting our sec; too many entries (3)

Although this should have been handled by `ble_hs_cfg.store_status_cb` callback by un-pairing oldest peer, somehow the space was not freed up, will update about this point. Can you please issue ...