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

[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