Central HIDS example can't connect with BLE HOGP mouse

RE: Central HIDS example can't connect with BLE HOGP mouse

tadakado — Tue, 11 Oct 2022 23:19:28 GMT

Thank you for your comment. I'll take a look at the GATT Discovery Manager. Hopefully, it will handle HID peripherals similar to other OSs in the future release.

RE: Central HIDS example can't connect with BLE HOGP mouse

Einar Thorsrud — Thu, 06 Oct 2022 13:16:38 GMT

The central HIDS sample use the GATT Discovery Manager which handles the whole discovery procedure. I have not got to the bottom of this, but it seems you would have to replace the this and do discovery yourself without the discovery manager. I do not have an implementation of that, though, unfortunately. It could also be that this can be worked around in another way that I have not thought about..

RE: Central HIDS example can't connect with BLE HOGP mouse

tadakado — Tue, 04 Oct 2022 22:51:23 GMT

Sure, no problem. Thank you for your time.

RE: Central HIDS example can't connect with BLE HOGP mouse

Einar Thorsrud — Tue, 04 Oct 2022 14:02:02 GMT

Hi,

I am sorry for the delay. I need some more time to look into this but will get back to you.

RE: Central HIDS example can't connect with BLE HOGP mouse

tadakado — Sat, 01 Oct 2022 07:44:23 GMT

I found that the error comes from L417 "discovery_process_characteristic" in gatt_dm.c https://github.com/nrfconnect/sdk-nrf/blob/v2.1.0/subsys/bluetooth/gatt_dm.c#L417

However, this is not the reason why the Central HIDS example does not work with ELECOM mouse. Below is a list of attributes stored during the connection. In Logitech, all handles are stored sequentially, while ELECOM lacks some handles. This is a variation of behavior among BLE peripherals.

Logitech

### (bt_gatt_dm_attr) Attr store, pos: 0, handle: 0x001f, uuid: 0x2800, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 1, handle: 0x0020, uuid: 0x2803, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 2, handle: 0x0021, uuid: 0x2a4a, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 3, handle: 0x0022, uuid: 0x2803, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 4, handle: 0x0023, uuid: 0x2a33, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 5, handle: 0x0024, uuid: 0x2902, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 6, handle: 0x0025, uuid: 0x2803, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 7, handle: 0x0026, uuid: 0x2a4b, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 8, handle: 0x0027, uuid: 0x2803, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 9, handle: 0x0028, uuid: 0x2a4d, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 10, handle: 0x0029, uuid: 0x2902, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 11, handle: 0x002a, uuid: 0x2908, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 12, handle: 0x002b, uuid: 0x2803, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 13, handle: 0x002c, uuid: 0x2a4d, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 14, handle: 0x002d, uuid: 0x2902, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 15, handle: 0x002e, uuid: 0x2908, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 16, handle: 0x002f, uuid: 0x2803, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 17, handle: 0x0030, uuid: 0x2a4d, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 18, handle: 0x0031, uuid: 0x2908, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 19, handle: 0x0032, uuid: 0x2803, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 20, handle: 0x0033, uuid: 0x2a4c, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 21, handle: 0x0034, uuid: 0x2803, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 22, handle: 0x0035, uuid: 0x2a4e, uuid_size: 4

### (parse_characteristic) handle: 0x0020, uuid: 2a4a, properties: 0x02
### (bt_gatt_dm_attr) look for an attr with handle: 0x0020
### return: 1, handle:0x0020
===> It find the DM ently

ELECOM

### (bt_gatt_dm_attr) Attr store, pos: 0, handle: 0x0017, uuid: 0x2800, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 1, handle: 0x0019, uuid: 0x2a4e, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 2, handle: 0x001b, uuid: 0x2a4d, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 3, handle: 0x001c, uuid: 0x2902, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 4, handle: 0x001d, uuid: 0x2908, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 5, handle: 0x001f, uuid: 0x2a4d, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 6, handle: 0x0020, uuid: 0x2908, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 7, handle: 0x0022, uuid: 0x2a4b, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 8, handle: 0x0024, uuid: 0x2a33, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 9, handle: 0x0025, uuid: 0x2902, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 10, handle: 0x0027, uuid: 0x2a4a, uuid_size: 4
### (bt_gatt_dm_attr) Attr store, pos: 11, handle: 0x0029, uuid: 0x2a4c, uuid_size: 4

### (parse_characteristic) handle: 0x0018, uuid: 2a4e, properties: 0x06
### (bt_gatt_dm_attr) look for an attr with handle: 0x0018
===> It fails as handle 0x0018 does not exist.

Why, this happens? I capture BLE packets (1) ELECOM + Central HIDS example (2) ELECOM + iPad. The example reads GATT database by "Find Information 0x04", while iPad does by "Read by Type 0x08". (See details in the attached files. You need filter ATT packets by "btatt".) I also found that Windows 10 also use "Read by Type". This causes the lack of information in the Central HIDS example.

So, I wan to change the method to read GATT database by not "Find Information" but "Read by Type" like iPad does. How can I do this?

devzone.nordicsemi.com/.../elecom2.pcapng devzone.nordicsemi.com/.../ipad_5F00_elecom.pcapng

RE: Central HIDS example can't connect with BLE HOGP mouse

Einar Thorsrud — Fri, 30 Sep 2022 10:48:47 GMT

I am not able to pinpoint the exact issue from here. Have you attempted to debug to see exactly where the error comes from? Which API call returns -ENOMEM, and how far down can you track it? That should give a good indication on what needs to be adjusted.

RE: Central HIDS example can't connect with BLE HOGP mouse

tadakado — Thu, 29 Sep 2022 13:43:16 GMT

Hi,

This might be more detailed information for ELECOM mouse errors.

(1) Sniffer trace (decrypted) (2) Call stack (3) Debug log

I guess I need to set a larger buffer size somewhere as the last part of the log below says

(BT_MAX_PAIRED, BT_GATT_DM_MAX_ATTRS, BT_HOGP_REPORTS_MAX are not the answer to resolve the problem)

D: Getting net_buf from queue
D: buf 0x2000ca54 type 3 len 31
D: buf 0x2000ca54
D: handle 0 len 27 flags 2
D: handle 0 ref 2 -> 3
D: conn 0x20001b58
D: tx 0x20003438 cb 0x1aba9 user_data 0x20003720
D: conn 0x20001b58 chan 0x20009cac
D: chan 0x20009ca8
D: chan 0x20009ca8 chan->req 0x2000cd30
D: handle 0 len 27 flags 02
D: First, len 27 final 23
D: Successfully parsed 27 byte L2CAP packet
D: Packet for CID 4 len 23
D: chan 0x20009cac len 23
D: Received ATT chan 0x20009ca8 code 0x09 len 22
D:
D: chan 0x20009ca8 err 0x00 len 22: 0718000619004e2a1a00121b004d2a1e000a1f004d2a
D: req 0x2000cd30
D: err 0x00
D: handle 0x0018 uuid 2a4e properties 0x06
The discovery procedure failed with -3

devzone.nordicsemi.com/.../2656.elecom.pcapng

devzone.nordicsemi.com/.../elecom_5F00_log.txt

RE: Central HIDS example can't connect with BLE HOGP mouse

Einar Thorsrud — Mon, 26 Sep 2022 13:57:40 GMT

Hi,

The sniffer can both get packets in a connection and decrypt encrypted packets (see nRF Sniffer documentation for details). That is needed for it to tell us anything useful, but it may not be relevant in this case.

I suggest focusing on that bt_conn_set_security() returns -ENOMEM. Did you try to increase CONFIG_BT_MAX_PAIRED? Or can you try to dig deeper with a debugger to pinpoint more closely where the error originates?

RE: Central HIDS example can't connect with BLE HOGP mouse

tadakado — Sat, 24 Sep 2022 12:41:13 GMT

Hi,

The sniffer traces with data PDU are attached. Sorry for incomplete data in the previous post.

Also, below is the logs for different BT_MAX_PAIRED settings.

### CONFIG_BT_MAX_PAIRED=1

# Elecom

Filters matched on UUID 0x1812.
Address: F1:C9:30:38:04:00 (random) connectable: yes
Connected: F1:C9:30:38:04:00 (random)
Failed to set security: -12
The discovery procedure failed with -3
Disconnected: F1:C9:30:38:04:00 (random) (reason 8)

# SANWA

Filters matched on UUID 0x1812.
Address: D0:F0:C8:CA:EF:30 (random) connectable: yes
Connected: D0:F0:C8:CA:EF:30 (random)
Failed to set security: -12
The service could not be found during the discovery
Disconnected: D0:F0:C8:CA:EF:30 (random) (reason 62)

# CONFIG_BT_MAX_PAIRED=2

# Elecom

Filters matched on UUID 0x1812.
Address: F1:C9:30:38:03:00 (random) connectable: yes
Connected: F1:C9:30:38:03:00 (random)
Security changed: F1:C9:30:38:03:00 (random) level 2
Pairing completed: F1:C9:30:38:03:00 (random), bonded: 1
The discovery procedure failed with -3
Disconnected: F1:C9:30:38:03:00 (random) (reason 8)

# SANWA

Filters matched on UUID 0x1812.
Address: D0:F0:C8:CA:EF:30 (random) connectable: yes
Connected: D0:F0:C8:CA:EF:30 (random)
Security failed: D0:F0:C8:CA:EF:30 (random) level 1 err 9
E: Discover failed, error: -128.
could not start the discovery procedure, error code: -128
Pairing failed conn: D0:F0:C8:CA:EF:30 (random), reason 9
Disconnected: D0:F0:C8:CA:EF:30 (random) (reason 62)

# CONFIG_BT_MAX_PAIRED=8

# Elecom

Filters matched on UUID 0x1812.
Address: F1:C9:30:38:03:00 (random) connectable: yes
Connected: F1:C9:30:38:03:00 (random)
Security changed: F1:C9:30:38:03:00 (random) level 2
Pairing completed: F1:C9:30:38:03:00 (random), bonded: 1
The discovery procedure failed with -3
Disconnected: F1:C9:30:38:03:00 (random) (reason 8)

# SANWA

Filters matched on UUID 0x1812.
Address: D0:F0:C8:CA:EF:30 (random) connectable: yes
Connected: D0:F0:C8:CA:EF:30 (random)
Security failed: D0:F0:C8:CA:EF:30 (random) level 1 err 9
E: Discover failed, error: -128.
could not start the discovery procedure, error code: -128
Pairing failed conn: D0:F0:C8:CA:EF:30 (random), reason 9
Disconnected: D0:F0:C8:CA:EF:30 (random) (reason 62)

devzone.nordicsemi.com/.../logitech_5F00_2.pcapng devzone.nordicsemi.com/.../sanwa_5F00_2.pcapng devzone.nordicsemi.com/.../elecom_5F00_2.pcapng

RE: Central HIDS example can't connect with BLE HOGP mouse

Einar Thorsrud — Fri, 23 Sep 2022 11:53:11 GMT

Hi,

The sniffer traces only shows advertising and nothing of the connection, so there is not much that can be seen from those.

Without sniffer traces we can still look at the errors though, and the first error for both devices is "Failed to set security: -12", which is -ENOMEM. As this happens for peripheral 2 and 3 this makes me wonder if the issue here is that you have a configuration issue where you do not support enough bonds. Can you try to add CONFIG_BT_MAX_PAIRED=4 to your prj.conf (or another number, which is at least as high as the number of bonds you need)? The default value here is 1.

RE: Central HIDS example can't connect with BLE HOGP mouse

tadakado — Fri, 23 Sep 2022 10:11:35 GMT

Now, Logitech M650 works with the Central HIDS example! I just recompile it with the default settings, and it works.

I have attached the files for Logitech (success), Elecom (fail) and SANWA (fail). Below are the outputs from the console.

# Logitech => Success

Filters matched on UUID 0x1812.
Address: D7:A8:39:0D:F2:C8 (random) connectable: yes
Connected: D7:A8:39:0D:F2:C8 (random)
Security changed: D7:A8:39:0D:F2:C8 (random) level 2
The discovery procedure succeeded
HIDS is ready to work
Subscribe to report id: 2
Subscribe to report id: 17
Subscribe to boot mouse report
Notification, id: 2, size: 7, data: 0x0 0x0 0x0 0xf0 0xff 0x0 0x0
Notification, id: 2, size: 7, data: 0x0 0x0 0x3 0xe0 0xff 0x0 0x0
Notification, id: 2, size: 7, data: 0x0 0x0 0x8 0xa0 0xff 0x0 0x0
Notification, id: 2, size: 7, data: 0x0 0x0 0x8 0xa0 0xff 0x0 0x0
Disconnected: D7:A8:39:0D:F2:C8 (random) (reason 19)
HIDS client active - releasing

# Elecom => Fail

Filters matched on UUID 0x1812.
Address: F1:C9:30:38:03:00 (random) connectable: yes
Connected: F1:C9:30:38:03:00 (random)
Failed to set security: -12
The discovery procedure failed with -3

# SANWA => Fail

Filters matched on UUID 0x1812.
Address: D0:F0:C8:CA:EF:30 (random) connectable: yes
Connected: D0:F0:C8:CA:EF:30 (random)
Failed to set security: -12
The service could not be found during the discovery
Disconnected: D0:F0:C8:CA:EF:30 (random) (reason 62)

I want to connect keyboard and mouse to nRF52. My problem is that some mice can't connect with the Central HIDS example. I want to support various BLE mice to connect. (I can use Logitech but I want to use other mouse.)

devzone.nordicsemi.com/.../logitech.pcapng devzone.nordicsemi.com/.../elecom.pcapng devzone.nordicsemi.com/.../sanwa.pcapng

RE: Central HIDS example can't connect with BLE HOGP mouse

Einar Thorsrud — Thu, 22 Sep 2022 13:49:03 GMT

Can you upload the full sniffer trace instead (the pcap file)?

Also, it could be interesting to see a trace with both the working and failing mouse to compare. And just to be sure, the problem here is different behavior with the two mouses right? And not the order of which mouse you try to connect? (Reading the initial question again I was a bit unsure). If you can elaborate that would be good.

RE: Central HIDS example can't connect with BLE HOGP mouse

tadakado — Wed, 21 Sep 2022 14:43:07 GMT

Hi, thanks for the replay. I have attached a sniffer capture data for another mouse (Logitech M650). It seems not much information. Is this the data for the next step? I used nrf_sniffer_for_bluetooth_le_4.1.0 with nrf52840 dongle and Wireshark 3.6.8. The connection information is as follows:

# Logitech M650

Filters matched on UUID 0x1812.
Address: D7:A8:39:0D:F2:C8 (random) connectable: yes
Connected: D7:A8:39:0D:F2:C8 (random)
Failed to set security: -12
The discovery procedure succeeded
E: HID information read error
ERROR: HIDS client preparation failed!
Disconnected: D7:A8:39:0D:F2:C8 (random) (reason 19)
HIDS client active - releasing

devzone.nordicsemi.com/.../central_5F00_hids_5F00_packet.txt

RE: Central HIDS example can't connect with BLE HOGP mouse

Einar Thorsrud — Mon, 19 Sep 2022 12:00:22 GMT

Hi,

With the first mouse you get "The discovery procedure failed with -3". 3 is -ESRCH, and lookin gat the implementation of gatt_dm.c this is only used in one case:

	cur_attr = attr_find_by_handle(dm, attr->handle);
	if (!cur_attr) {
		/* We should never be here is the server is working properly */
		discovery_complete_error(dm, -ESRCH);
		return BT_GATT_ITER_STOP;
	}

which is when the attribute handle is not found. I cannot see from the log which attribute this is though, but it would seem that the mouse GATT server does not have it.

With the second mouse you get "Failed to set security: -12" (BT_HCI_ERR_CMD_DISALLOWED), which is the same as in this thread. We cannot say more about the cause from the error, so a sniffer trace would be the natural next step.