pc-ble-driver example heart_rate_collector get disconnected with error 0x22

Question

Hi,

I am running on pc-ble-driver master branch.

https://github.com/NordicSemiconductor/pc-ble-driver

Currently I am using abce7974fe983c23930d362b1769e51c8fa13cbf.

I am trying to verifying the newly added connectivity firmware for nRF52840 Dongle PCA10059.

So I compiled and loaded hex/sd_api_v6/connectivity_<ver>_usb_with_s140_6.1.0.hex

I am now getting error 0x22 which is BLE_HCI_STATUS_CODE_LMP_RESPONSE_TIMEOUT, once I connect to a Nordic_HRM peripheral. Peripheral is built with nRF5_SDK_15.2.0_9412b96 and run on PCA10040.

My host is Ubuntu 18.04.

I am doing this because the release note 4.0.0 says:"Support SoftDevice API version 2, 3, 5 and 6 in the same release". And I am aware that PCA10059 works fine with https://github.com/NordicSemiconductor/pc-ble-driver/blob/release/v2.3.2/hex/sd_api_v3/connectivity_1.2.3_usb_with_s132_3.1.hex

Beside this problem, I also found that hex/sd_api_v6/connectivity_<ver>_1m_with_s132_6.1.0.hex does not work anymore on PCA10040. Does not know when this has started.

Thanks & best regards,

Chencheng

Edvin · Accepted Answer

Hello Chengcheng, 
 I just saw the ticket that you linked to. Did you set: 
 ble_gap_data_length_params_t const dlp =
	{
 .max_rx_octets = 27,
 .max_tx_octets = 27,
 .max_rx_time_us = BLE_GAP_DATA_LENGTH_AUTO,
 .max_tx_time_us = BLE_GAP_DATA_LENGTH_AUTO,
	}; 
 Like Sigurd suggested? Or did you set it according to the length update request? 
 As Sigurd just posted (after you saw his post), the max length for the connectivity firmware is 27, so that is why you need to use this. This should also be why sd_ble_gap_data_length_update fails with NRF_ERROR_RESOURCES. 
 
 Can you try setting it to 27? 
 
 Best regards, 
 Edvin

pc-ble-driver example heart_rate_collector get disconnected with error 0x22

Top Replies