BT832 BLE sample disconnect immediately

RE: BT832 BLE sample disconnect immediately

Alexey — Mon, 26 Feb 2018 15:04:06 GMT

Sigurd, thanks, this magic numbers helped me! Now it works fine.
Could you please advice if I can read about this magic numbers or overall about sdk_config.h configuration strategy somewhere?

RE: BT832 BLE sample disconnect immediately

Sigurd — Mon, 26 Feb 2018 14:12:28 GMT

What type of Android device is this? It could be a timing issue. With SDK 14.2, could you try the following configuration in sdk_config.h

// </h> 
//==========================================================

// <h> Clock - SoftDevice clock configuration

//==========================================================
// <o> NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source.
 
// <0=> NRF_CLOCK_LF_SRC_RC 
// <1=> NRF_CLOCK_LF_SRC_XTAL 
// <2=> NRF_CLOCK_LF_SRC_SYNTH 

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

// <o> NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. 
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#endif

// <o> NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. 
// <i> How often (in number of calibration intervals) the RC oscillator shall be calibrated
// <i>  if the temperature has not changed.

#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#endif

// <o> NRF_SDH_CLOCK_LF_XTAL_ACCURACY  - External crystal clock accuracy used in the LL to compute timing windows.
 
// <0=> NRF_CLOCK_LF_XTAL_ACCURACY_250_PPM 
// <1=> NRF_CLOCK_LF_XTAL_ACCURACY_500_PPM 
// <2=> NRF_CLOCK_LF_XTAL_ACCURACY_150_PPM 
// <3=> NRF_CLOCK_LF_XTAL_ACCURACY_100_PPM 
// <4=> NRF_CLOCK_LF_XTAL_ACCURACY_75_PPM 
// <5=> NRF_CLOCK_LF_XTAL_ACCURACY_50_PPM 
// <6=> NRF_CLOCK_LF_XTAL_ACCURACY_30_PPM 
// <7=> NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM 

#ifndef NRF_SDH_CLOCK_LF_XTAL_ACCURACY
#define NRF_SDH_CLOCK_LF_XTAL_ACCURACY 1
#endif

RE: BT832 BLE sample disconnect immediately

Alexey — Mon, 26 Feb 2018 13:37:18 GMT

Hi Sigurd.
Here is what I get after applying extra logging:

 0> <info> app: Template example started.
 0> <info> app: Fast advertising.
 0> <info> app: Connected.
 0> <info> app: Fast advertising.
 0> <info> app: Disconnected.
 0> <info> app: Disconnect reason: 62

I tried to dig 62 code, and looks like this is ble_hci.h:

#define BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED          0x3E       /**< Connection Failed to be Established. */

Am I correct? If so, still not clear what is wrong.

RE: BT832 BLE sample disconnect immediately

Sigurd — Mon, 26 Feb 2018 12:53:40 GMT

Hi,

The disconnect reason should give us some more information about why the disconnect happened.

Could you try to print the reason when you get the disconnect event ? i.e. add this code-line under the BLE_GAP_EVT_DISCONNECTED event in ble_evt_handler()

NRF_LOG_INFO("Disconnect reason: %d",p_ble_evt->evt.gap_evt.params.disconnected.reason);

RE: BT832 BLE sample disconnect immediately

Søren Mikkelsen — Sun, 25 Feb 2018 14:45:13 GMT

Hello

BT832 doesn’t seem to have 32khz clock within the module. Nordic DK examples uses 32khz by default. Can’t say that this your issue, but you could check that.

Best regards

Søren