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

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

Edvin — Fri, 08 Mar 2019 14:02:20 GMT

Then your application is doing something that it isn't allowed to. It would be nice if you can start a new ticket, yes, then someone will help you out.

BR,

Edvin

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

Chencheng — Thu, 07 Mar 2019 08:54:51 GMT

Tried. No luck.

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

Edvin — Wed, 06 Mar 2019 17:29:21 GMT

Do you reset the nRF after programming it with the .hex file? Try to power cycle it before you run your project from the terminal. Any luck?

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

Chencheng — Wed, 06 Mar 2019 17:06:04 GMT

Tried flashed under Linux with nRF connect programmer. Didn't work:

$ ./heart_rate_collector_v6 /dev/ttyACM2 
Serial port used: /dev/ttyACM2
Baud rate used: 1000000
Info: Successfully opened /dev/ttyACM2. Baud rate: 1000000. Flow control: none. Parity: none.
Log: State change: STATE_START -> STATE_RESET
Log:        1 ->  [N/A] type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
Status: 6, message: Target Reset performed
Log: State change: STATE_RESET -> STATE_UNINITIALIZED
Log:        2 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
Log:        3 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
Log:        4 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
Log:        5 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
Log:        6 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
Log:        7 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
Status: 0, message: No response from device. Tried to send packet 6 times.
Log: State change: STATE_UNINITIALIZED -> STATE_NO_RESPONSE
Failed to open nRF BLE Driver. Error code: 0x0D

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

Edvin — Wed, 06 Mar 2019 16:31:13 GMT

devzone.nordicsemi.com/.../connectivity_5F00_4.0.0_5F00_1m_5F00_with_5F00_s132_5F00_6.1.0.hex

Just for fun, can you try to flash this image instead? The pc-ble-driver has some patches for the connectivity firmware, so depending on how you compiled it, these patches were might not included. Let me know if it still behaves the same.

BR,

Edvin

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

Chencheng — Wed, 06 Mar 2019 13:51:44 GMT

As I mentioned earlier, I run everything under Ubuntu 18.04. I follow the instruction to compile from source. I compiled connectivity firmware hex file as well. I flashed it using nrf-connect AppImage under Linux with latest updates.

I am running heart_rate_colletcor_v6 by:

$ ./heart_rate_collector_v6 /dev/ttyACM2

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

Edvin — Wed, 06 Mar 2019 13:30:42 GMT

what command did you write to get this message? What example are you running? Please post the command like this:

heart_rate_collector_v6.exe COM7

that you used to start the example.

The example is running. It looks like you failed scan start with error code 32773 (=0x8005).

As far as I can tell, this should not be possible. But let me know what example you are running.

BR,

Edvin

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

Chencheng — Wed, 06 Mar 2019 12:42:00 GMT

Shall I open another ticket for PCA10040 issue?

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

Chencheng — Wed, 06 Mar 2019 12:24:33 GMT

Yes, I am sure PCA10040 nRF52832 DK not working with ..._with_s132_... for release 4.0.0.

More debug error log:

Serial port used: /dev/ttyACM2
Baud rate used: 1000000
Info: Successfully opened /dev/ttyACM2. Baud rate: 1000000. Flow control: none. Parity: none.

Log: State change: STATE_START -> STATE_RESET

Log:        1 ->  [N/A] type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
Status: 6, message: Target Reset performed
Log: State change: STATE_RESET -> STATE_UNINITIALIZED

Log:        2 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
Log:     1/ 0 <-  [02 7d ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC_RESP]
Log: State change: STATE_UNINITIALIZED -> STATE_INITIALIZED

Log:        3 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log:        4 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log:        5 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log:        6 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log:     2/ 0 <-  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
Log:        7 ->  [02 7d ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC_RESP]
Log:        8 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log:     3/ 0 <-  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log:        9 ->  [04 7b 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG_RESP [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log:       10 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log:     4/ 0 <-  [04 7b 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG_RESP [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
Log: State change: STATE_INITIALIZED -> STATE_ACTIVE

Status: 7, message: Connection active
Log:       11 ->  [00 69 40 00 00 00 01 00 01 00 01 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:0 ack#:0 payload_length:c data_integrity:1 header_checksum:72 err_code:0x0
Log:     5/ 0 <-  [N/A] type:                 ACK reliable: no seq#:0 ack#:1 payload_length:0 data_integrity:0 err_code:0x0
Log:     6/ 0 <-  [01 69 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:0 ack#:1 payload_length:6 data_integrity:1 header_checksum:ca err_code:0x0
Log:       12 ->  [N/A] type:                 ACK reliable: no seq#:0 ack#:1 payload_length:0 data_integrity:0 err_code:0x0
Log:       13 ->  [00 69 23 00 00 00 01 01 96 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:1 ack#:1 payload_length:a data_integrity:1 header_checksum:89 err_code:0x0
Log:     7/ 0 <-  [N/A] type:                 ACK reliable: no seq#:0 ack#:2 payload_length:0 data_integrity:0 err_code:0x0
Log:     8/ 0 <-  [01 69 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:1 ack#:2 payload_length:6 data_integrity:1 header_checksum:c1 err_code:0x0
Log:       14 ->  [N/A] type:                 ACK reliable: no seq#:0 ack#:2 payload_length:0 data_integrity:0 err_code:0x0
Log:       15 ->  [00 60 ] type:     VENDOR_SPECIFIC reliable:yes seq#:2 ack#:2 payload_length:2 data_integrity:1 header_checksum:0 err_code:0x0
Log:     9/ 0 <-  [N/A] type:                 ACK reliable: no seq#:0 ack#:3 payload_length:0 data_integrity:0 err_code:0x0
Log:    10/ 0 <-  [01 60 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:2 ack#:3 payload_length:6 data_integrity:1 header_checksum:b8 err_code:0x0
Log:       16 ->  [N/A] type:                 ACK reliable: no seq#:0 ack#:3 payload_length:0 data_integrity:0 err_code:0x0
Log:       17 ->  [00 8a 01 00 01 01 00 00 00 00 00 a0 00 50 00 00 00 01 01 00 00 00 64 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:3 ack#:3 payload_length:7d data_integrity:1 header_checksum:40 err_code:0x0
Log:       18 ->  [00 8a 01 00 01 01 00 00 00 00 00 a0 00 50 00 00 00 01 01 00 00 00 64 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:3 ack#:3 payload_length:7d data_integrity:1 header_checksum:40 err_code:0x0
Log:       19 ->  [00 8a 01 00 01 01 00 00 00 00 00 a0 00 50 00 00 00 01 01 00 00 00 64 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:3 ack#:3 payload_length:7d data_integrity:1 header_checksum:40 err_code:0x0
Log:       20 ->  [00 8a 01 00 01 01 00 00 00 00 00 a0 00 50 00 00 00 01 01 00 00 00 64 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:3 ack#:3 payload_length:7d data_integrity:1 header_checksum:40 err_code:0x0
Log:       21 ->  [00 8a 01 00 01 01 00 00 00 00 00 a0 00 50 00 00 00 01 01 00 00 00 64 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:3 ack#:3 payload_length:7d data_integrity:1 header_checksum:40 err_code:0x0
Log:       22 ->  [00 8a 01 00 01 01 00 00 00 00 00 a0 00 50 00 00 00 01 01 00 00 00 64 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:3 ack#:3 payload_length:7d data_integrity:1 header_checksum:40 err_code:0x0
Status: 4, message: Error sending packet to target. Code: 0x802a
Scan start failed with error code: 32773

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

Edvin — Wed, 06 Mar 2019 11:34:37 GMT

Can you describe what you mean by connectivity_4.0.0_1m_with_s132_6.1.0.hex not working? Are you sure you are using the PCA10040 board? The nRF52832 DK?

Are you sure you are using the ...4.0.0_1m_with_s132... and not the ...4.0.0_1m_for_s132... ?

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

Chencheng — Wed, 06 Mar 2019 09:20:18 GMT

Hi Edvin,

I've tested Sigurd's suggesttion. It (27) works. I guess there's ongoing work to fix this issue right?

And I think the rest of my problem is how to get connectivity_4.0.0_1m_with_s132_6.1.0.hex working for PCA10040.

BR/Chencheng

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

Edvin — Tue, 05 Mar 2019 17:05:48 GMT

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

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

Chencheng — Tue, 05 Mar 2019 15:55:03 GMT

[quote userid="26071" url="~/f/nordic-q-a/44372/pc-ble-driver-example-heart_rate_collector-get-disconnected-with-error-0x22/174324"]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. [/quote]

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

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

Chencheng — Tue, 05 Mar 2019 15:06:38 GMT

Hi Edvin,

Thanks for your reply.

[quote userid="26071" url="~/f/nordic-q-a/44372/pc-ble-driver-example-heart_rate_collector-get-disconnected-with-error-0x22/174324"][/quote]

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

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

Edvin — Tue, 05 Mar 2019 14:59:24 GMT

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.

[quote user=""]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.[/quote]

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

Best regards,

Edvin

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

Chencheng — Mon, 04 Mar 2019 13:15:21 GMT

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