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

[Chencheng]

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

[Chencheng]

Error log:

$ ./heart_rate_collector_v6 /dev/ttyACM1
Serial port used: /dev/ttyACM1
Baud rate used: 1000000
Info: Successfully opened /dev/ttyACM1. Baud rate: 1000000. Flow control: none. Parity: none.
Status: 6, message: Target Reset performed
Status: 7, message: Connection active
Scan started
Received advertisement report with device address: 0x1F3DA468EEAD
Scan started
Received advertisement report with device address: 0xA48E0AE00002
Scan started
Received advertisement report with device address: 0x0A464AD29336
Scan started
Received advertisement report with device address: 0x58C4ABA13778
Scan started
Received advertisement report with device address: 0x1F3DA468EEAD
Scan started
Received advertisement report with device address: 0xF69A3331F222
Connection established
Discovering primary services
Received an un-handled event with ID: 35
Received service discovery response
Discovered heart rate service. UUID: 0x180D, start handle: 0x000E, end handle: 0x0013
Discovering characteristics
Received characteristic discovery response, characteristics count: 2
Characteristic handle: 0x000F, UUID: 0x2A37
Characteristic handle: 0x0012, UUID: 0x2A38
Discovering characteristic's descriptors
Received descriptor discovery response, descriptor count: 5
Descriptor handle: 0x000F, UUID: 0x2803
Descriptor handle: 0x0010, UUID: 0x2A37
Descriptor handle: 0x0011, UUID: 0x2902
Press enter to toggle notifications on the HRM characteristic
Descriptor handle: 0x0012, UUID: 0x2803
Descriptor handle: 0x0013, UUID: 0x2A38

Setting HRM CCCD
Received write response.
Received heart rate measurement: 140
Received heart rate measurement: 150
Received heart rate measurement: 160
Received heart rate measurement: 170
Received heart rate measurement: 180
Received heart rate measurement: 190
Connection interval updated: 0x208, 0x208. (This trace is added by me to get rid of the un-handled event complaint)
Disconnected, reason: 0x22

[Edvin]

Hello,

Regarding your main issue with the nRF52840 dongle:

I believe that this is still related to the unhandled event with ID 35, which would be a BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST. I have replicated this on both the connectivity_4.0.0_usb_for_s140_6.1.0.hex and the connectivity_4.0.0_1m_with_s132_6.1.0.hex serialization backends, so it doesn't seem to be related to usb + s140, but rather the application. 

I have forwarded this to our pc-ble-driver team. I will keep you updated with their response. Thank you for reporting this.

 

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.

Do you refer to the same issue with this .hex file? 

Best regards,

Edvin 

[Chencheng]

Hi Edvin,

Thanks for your reply.

Edvin said:

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.

Do you refer to the same issue with this .hex file? 

No, I don't think it is the same problem:

Serial port used: /dev/ttyACM2
Baud rate used: 1000000
Info: Successfully opened /dev/ttyACM2. Baud rate: 1000000. Flow control: none. Parity: none.
Status: 6, message: Target Reset performed
Error: h5_decode error, code: 0x802b, H5 error count: 1. raw packet: c0 00 ff c0
Status: 7, message: Connection active
Status: 4, message: Error sending packet to target. Code: 0x802a
Scan start failed with error code: 0x8005

BR/Chencheng

[Chencheng]

Edvin said:

I believe that this is still related to the unhandled event with ID 35, which would be a BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST. I have replicated this on both the connectivity_4.0.0_usb_for_s140_6.1.0.hex and the connectivity_4.0.0_1m_with_s132_6.1.0.hex serialization backends, so it doesn't seem to be related to usb + s140, but rather the application. 

Just a quick update.

I implemented according to this. But I get an error:

BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST received: sd_ble_gap_data_length_update failed, err_code 19 NRF_ERROR_RESOURCES

BR/Chencheng

[Edvin]

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