slompf18 opened a new issue #745: Problem connecting - how to read logs? URL: https://github.com/apache/mynewt-nimble/issues/745 Hi, I'm trying to connect with a Apple Homekit device to a ESP32 using Nimble. I've managed to make the device visible and I see it connects successfully. But after a while the device is terminating the connection (reason 531). Now I wonder what might be wrong. In order to find out I'm trying to understand the logs in order to find out: - What connection parameters are used, that might not fit? - Has it already asked for GATT? But thats quite hard. Maybe someone here can state whats going on: ``` GAP procedure initiated: advertise; disc_mode=2 adv_channel_map=0 own_addr_type=0 adv_filter_policy=0 adv_itvl_min=0 adv_itvl_max=0 ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0006 len=15 0x06 0x20 0x0f 0x30 0x00 0x60 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x07 0x00 Command complete: cmd_pkts=5 ogf=0x8 ocf=0x6 status=0 ble_hs_hci_cmd_send: ogf=0x08 ocf=0x000a len=1 0x0a 0x20 0x01 0x01 Command complete: cmd_pkts=5 ogf=0x8 ocf=0xa status=0 LE connection complete. handle=0 role=1 paddrtype=1 addr=6b.59.61.56.9f.9f local_rpa=0.0.0.0.0.0 peer_rpa=0.0.0.0.0.0 itvl=20 latency=0 spvn_tmo=72 mca=1 ---> I (15123) NimBLE_BLE_PRPH: connection established; status=0 handle=0 our_ota_addr_type=0 our_ota_addr=cc:50:e3:9a:15:8e our_id_addr_type=0 our_id_addr=cc:50:e3:9a:15:8e peer_ota_addr_type=1 peer_ota_addr=6b:59:61:56:9f:9f peer_id_addr_type=1 peer_id_addr=6b:59:61:56:9f:9f conn_itvl=20 conn_latency=0 supervision_timeout=72 encrypted=0 authenticated=0 bonded=0 ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0016 len=2 0x16 0x20 0x02 0x00 0x00 Command Status: status=0 cmd_pkts=5 ocf=0x16 ogf=0x8 LE Remote Used Features. handle=0 feat=ff 00 00 00 00 00 00 00 LE Data Length Change. handle=0 max_tx_bytes=27 max_tx_time=328 max_rx_bytes=251 max_rx_time=2120 LE Remote Connection Parameter Request. handle=0 min_itvl=24 max_itvl=24 latency=0 timeout=200 ble_hs_hci_cmd_send: ogf=0x08 ocf=0x0020 len=14 0x20 0x20 0x0e 0x00 0x00 0x18 0x00 0x18 0x00 0x00 0x00 0xc8 0x00 0x00 0x00 0x00 0x00 Command complete: cmd_pkts=5 ogf=0x8 ocf=0x20 status=0 ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=7 data=0x03 0x00 0x04 0x00 0x02 0x0f 0x02 rxed att command: mtu req; conn=0 mtu=527 txed att command: mtu rsp; conn=0 mtu=256 host tx hci data; handle=0 length=7 ble_hs_hci_acl_tx(): 0x00 0x00 0x07 0x00 0x03 0x00 0x04 0x00 0x03 0x00 0x01 ---> I (15393) NimBLE_BLE_PRPH: mtu update event; conn_handle=0 cid=4 mtu=256 Number of Completed Packets: num_handles=1 handle:0 pkts:1 LE Connection Update Complete. handle=0 itvl=24 latency=0 timeout=200 ---> I (15573) NimBLE_BLE_PRPH: connection updated; status=0 ble_hs_hci_evt_acl_process(): conn_handle=0 pb=2 len=11 data=0x07 0x00 0x04 0x00 0x08 0x01 0x00 0x05 0x00 0x00 0x2a rxed att command: read type req; conn=0 start_handle=0x0001 end_handle=0x0005 txed att command: read type rsp; conn=0 length=5 host tx hci data; handle=0 length=11 ble_hs_hci_acl_tx(): 0x00 0x00 0x0b 0x00 0x07 0x00 0x04 0x00 0x09 0x05 0x03 0x00 0x62 0x6c 0x61 Number of Completed Packets: num_handles=1 handle:0 pkts:1 Disconnection Complete: status=0 handle=0 reason=19 ---> W (20703) NimBLE_BLE_PRPH: disconnect; reason=531 ``` Best regards
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
