BLE_HS_ETIMEOUT_HCI and BLE_HS_ENOTSYNCED seen, stack inoperative #394
Description
esp-idf v5.4.2, esp-nimble-cpp v2.3.3
User testing with Android had this case occur where it looks like something is wrong with the controller and BLE is unresponsive after this point.
Is there something that should be done at the user space level to cause the stack to reinitialize? I'm not sure why this might have occurred, however this system is using Wifi AP + wifi sta + ble. I wonder if it's somehow related to connecting to ble early in the boot process where the cpu is loaded down.
I (3292) NimBLE: GAP procedure initiated: stop advertising.
I (3292) NimBLE: GAP procedure initiated: stop advertising.
I (3292) NimBLE: GAP procedure initiated: stop advertising.
I (3292) NimBLE: GAP procedure initiated: stop advertising.
I (3302) BLE: device mtu 251
I (3302) BLE: thread(): 1727 characteristics and callbacks configured in 612 ms
I (3302) WhiteListManager: Num Bonds: 3
I (3312) NimBLE: GAP procedure initiated: set whitelist;
I (3312) NimBLE: count=1
I (3312) NimBLE: entry-0={addr_type=0 addr=
I (3312) NimBLE: 18:fa:b7:2f:1e:ce
I (3312) NimBLE: }
I (3312) NimBLE:
I (3322) NimBLE: GAP procedure initiated: set whitelist;
I (3322) NimBLE: count=2
I (3322) NimBLE: entry-0={addr_type=0 addr=
I (3322) NimBLE: 18:fa:b7:2f:1e:ce
I (3322) NimBLE: }
I (3322) NimBLE: entry-1={addr_type=0 addr=
I (3322) NimBLE: 70:b3:06:12:ca:44
I (3322) NimBLE: }
I (3322) NimBLE:
I (3332) NimBLE: GAP procedure initiated: set whitelist;
I (3332) NimBLE: count=3
I (3332) NimBLE: entry-0={addr_type=0 addr=
I (3342) NimBLE: 18:fa:b7:2f:1e:ce
I (3342) NimBLE: }
I (3342) NimBLE: entry-1={addr_type=0 addr=
I (3352) NimBLE: 70:b3:06:12:ca:44
I (3352) NimBLE: }
I (3352) NimBLE: entry-2={addr_type=0 addr=
I (3352) NimBLE: 68:df:e4:df:9c:77
I (3362) NimBLE: }
I (3362) NimBLE:
I (3382) BLE: WhiteListManager::Restore() complete
I (3382) BLE: connectMode -> whitelist only
I (3392) NimBLE: GAP procedure initiated: advertise;
I (3392) NimBLE: disc_mode=2
I (3402) NimBLE: adv_channel_map=0 own_addr_type=0 adv_filter_policy=2 adv_itvl_min=0 adv_itvl_max=0
I (3402) NimBLE:
I (3402) BLE: thread(): 1787 finished initialization
I (13872) BLE: onConnect()
I (13872) BLE: mtu: 23
I (13872) BLE: OTA address 74:75:d5:8d:b8:51, type 1
I (13872) BLE: ID address 68:df:e4:df:9c:77, type 0
I (13872) BLE: Bonded: no, Authenticated: no, Encrypted: no, Key size: 0
I (13872) BLE: BLE lastState (Restricted) != state (Connecting)
E (33872) NimBLE: HCI wait for ack returned 19
I (33872) NimBLE: ogf=0x08, ocf=0x0022, core_err=0x13 : BLE_HS_ETIMEOUT_HCI (HCI request timed out; controller unresponsive)
I (33872) BLE: onAuthenticationComplete()
W (33872) BLE: Encrypt connection failed - disconnecting client
I (33872) NimBLE: GAP procedure initiated: terminate connection; conn_handle=1 hci_reason=19
I (33872) NimBLE: ogf=0x01, ocf=0x0006, core_err=0x16 : BLE_HS_ENOTSYNCED (Attempt to use the host before it is synced with controller)
E (33872) BLE: onAuthenticationComplete(): NimBLEDevice::getServer()->disconnect()
I (33872) BLE: onDisconnect(), Client disconnected - reason 0x13 (19)
I (33882) NimBLE: GAP procedure initiated: stop advertising.
I (33882) NimBLE: GAP procedure initiated: stop advertising.
I (33882) NimBLE: GAP procedure initiated: stop advertising.
I (33882) NimBLE: GAP procedure initiated: stop advertising.
I (33882) NimBLE: GAP procedure initiated: advertise;
I (33882) NimBLE: disc_mode=2
I (33882) NimBLE: adv_channel_map=0 own_addr_type=0 adv_filter_policy=2 adv_itvl_min=0 adv_itvl_max=0
I (33882) NimBLE: