RE: Issue connecting with slower advertising intervals

krog1 — Wed, 13 Nov 2019 12:48:09 GMT

Thanks Kenneth! That took care of it.

Cheers,

Chris.

RE: Issue connecting with slower advertising intervals

Kenneth — Wed, 13 Nov 2019 12:04:31 GMT

What you are seeing is that the connect operation was canceled. Successfully.

So it seems that the connect procedure timed out because the advertising interval was too high. The cancel operation was most likely coming from this: CONFIG_BT_CREATE_CONN_TIMEOUT, which is default 3. You should increase it in this use case.

Best regards,
Kenneth

RE: Issue connecting with slower advertising intervals

krog1 — Wed, 13 Nov 2019 00:39:45 GMT

Hi Kenneth,

The error code is on the nrf9160, coming from the HCI code to the connect callback. the HCI_CORE debug trace is below. Hopefully it's enough; unfortunately some logs were dropped.

Thanks,

Chris.

[00:03:24.380,493] <dbg> bt_hci_core.bt_hci_cmd_create: opcode 0x200d param_len 25
[00:03:24.380,523] <dbg> bt_hci_core.bt_hci_cmd_create: buf 0x200386d0
[00:03:24.380,615] <dbg> bt_hci_core.bt_hci_cmd_send_sync: buf 0x200386d0 opcode 0x200d len 28
[00:03:24.380,798] <dbg> bt_hci_core.process_events: count 2
[00:03:24.380,828] <dbg> bt_hci_core.process_events: ev->state 4
[00:03:24.380,859] <dbg> bt_hci_core.send_cmd: calling net_buf_get
[00:03:24.380,889] <dbg> bt_hci_core.send_cmd: calling sem_take_wait
[00:03:24.380,920] <dbg> bt_hci_core.send_cmd: Sending command 0x200d (buf 0x200386d0) to driver
[00:03:24.381,011] <dbg> bt_hci_core.bt_send: buf 0x200386d0 len 28 type 0
[00:03:24.381,134] <dbg> bt_hci_core.process_events: ev->state 0
[00:03:24.381,225] <dbg> bt_hci_core.hci_tx_thread: Calling k_poll with 2 events
[00:03:24.381,958] <dbg> bt_hci_core.bt_buf_get_cmd_complete: sent_cmd 0x200386d0
[00:03:24.382,019] <dbg> bt_hci_core.hci_cmd_status: opcode 0x200d
[00:03:24.382,080] <dbg> bt_hci_core.hci_cmd_done: opcode 0x200d status 0x00 buf 0x200386d0
[00:03:24.382,232] <dbg> bt_hci_core.bt_hci_cmd_send_sync: opcode 0x200d status 0x00
[00:03:27.378,936] <dbg> bt_hci_core.bt_hci_cmd_create: opcode 0x200e param_len 0
--- 1 messages dropped ---
[00:03:27.379,180] <dbg> bt_hci_core.send_cmd: Sending command 0x200e (buf 0x200386d0) to driver
--- 5 messages dropped ---
[00:03:27.379,211] <dbg> bt_hci_core.bt_send: buf 0x200386d0 len 3 type 0
[00:03:27.379,302] <dbg> bt_hci_core.process_events: ev->state 0
[00:03:27.379,364] <dbg> bt_hci_core.hci_tx_thread: Calling k_poll with 2 events
[00:03:27.379,699] <dbg> bt_hci_core.bt_buf_get_cmd_complete: sent_cmd 0x200386d0
[00:03:27.379,730] <dbg> bt_hci_core.hci_cmd_complete: opcode 0x200e
[00:03:27.379,760] <dbg> bt_hci_core.hci_cmd_done: opcode 0x200e status 0x00 buf 0x200386d0
[00:03:27.380,218] <dbg> bt_hci_core.bt_recv: buf 0x20038798 len 21
[00:03:27.380,218] <dbg> bt_hci_core.hci_event: event 0x3e
[00:03:27.380,249] <dbg> bt_hci_core.hci_le_meta_event: subevent 0x01
[00:03:27.380,371] <dbg> bt_hci_core.le_legacy_conn_complete: status 2 role 0 00:00:00:00:00:00 (public)
[00:03:27.380,493] <dbg> bt_hci_core.enh_conn_complete: status 2 handle 0 role 0 00:00:00:00:00:00 (public)
[00:03:27.380,584] <wrn> ble: Failed to connect to cf:ae:17:85:49:78 (random) (error 2)

RE: Issue connecting with slower advertising intervals

Kenneth — Tue, 12 Nov 2019 19:34:32 GMT

We do not currently provide support for NCS for the nRF52-series, even if there are some Bluetooth related samples and libraries in NCS.

That said, it may be useful if you can enable debug logs, especially for CONFIG_BT_DEBUG_HCI_CORE. Also please clarify which side is seeing the error code.