BLE_HCI_CONNECTION_TIMEOUT with Linux Central

Hello,

I've flashed to my custom nRF52832 board the ble_app_hrs_pca10040_s132 example, it works fine with iOS and Android hosts but when I try to connect to my development host via bluetooth it disconnects almost instantaneously outputting BLE_HCI_CONNECTION_TIMEOUT. I've read in other threads that the RC low frequency clock could cause this problem, but with other hosts (even a Raspberry PI Zero 2 with linux running) is working fine. How can i address this issue?

SoftDevice version: S132 7.3.0
SoftDevice clock config:

#define NRF_SDH_CLOCK_LF_ACCURACY 1
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#define NRF_SDH_CLOCK_LF_SRC 0

Debug window output:

<debug> nrf_sdh_ble: BLE event: 0x10.
<debug> nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.
<debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.
<info> peer_manager_handler: Peer data updated in flash: peer_id: 1, data_id: Peer rank, action: Update, no change
<info> app: Connected.
<debug> nrf_sdh_ble: BLE event: 0x11.
<info> app: Fast advertising.
<info> app: Disconnected, reason 8.

bluetoothctl output while pairing:

[bluetooth]# pair FD:81:ED:2A:E3:26 
Attempting to pair with FD:81:ED:2A:E3:26
[CHG] Device FD:81:ED:2A:E3:26 Connected: yes
[DEL] Device 77:CD:7D:D0:7B:85 77-CD-7D-D0-7B-85
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[CHG] Device FD:81:ED:2A:E3:26 Connected: no
[DEL] Device 4A:81:81:64:3D:7C 4A-81-81-64-3D-7C
  • It shows the same as before - the master does not acknowledge packets sent by your slave for no apparent reason. I'm not sure if this points to an issue with the Bluez host or the controller. Have you been able to interface with other BT devices on this PC? 

    Edit:

    federunco said:
    I've tried two different BLE sticks but the board is not even discovered with both external sticks.

    What chipset does these dongles have? Broadcam, intel,..?

    Also, do you have a nordic DK you can test with in order to rule out any potential HW issues with your custom board?

Related