NRF52840 connecion problem with windows 10

[alireza11048]

Hi to all,

i am developing a device with nrf52840 soc and i want connect to Windows 10 though ble connection. in my device i had implemented an HID service that should act as Mouse device and also i have other services. but i have a problem in connection with windows that sometimes happen and the problem is in this manner that 30 sec after that connection stablished windows terminate the connection and after termination my device start to advertise and then windows auto-connect to my device then immediately terminate the connection!! and then follow the auot-connect disconnect permanentl,but sometimes after the pairing all things work good without problem. when all things work good windows list my device under Mouse,Keyboard, & Pen list and when the problem happen windows list my device under other device list. i also attached the Ble connection dump between windows and my device when this problem happen.

there is anyone that can give me a advice to solve this problem??

UPDATE: after some investigation i noticed that disconnection is happen because windows try to read some thing from a char in one of my services that has (notify/read) properties and nrf52 did not respond to this request, and then after some time disconnection happen. then remove read prop from that char, but after that disconnection happen again because windows try to read from another char from HID service and agin NRF did not respond and again disconnection happen, in below screen shot you can see the sequence:

and also i attached BLE dump of this process again.

2_Connect_Disconnect_Always.pcapng

HidServiceReadProblem.pcapng

[Einar Thorsrud]

Hi,

I am not able to find the packet exchange from the screenshot (or anything similar) when I look at the traces on my side. Can you point at where it is (packet number) in which trace file?

[alireza11048]

in HidServiceReadProblem.pcapng trace file, packet number 1179 master send a read request from Boot  Mouse Input Report Characteristic and nrf did not respond to it. in my own service this problem was exist also but when i remove the read properties from that characteristic then windows did not try to read this characteristic and dc dose not happen. and also when i set the rd_auth to 0 for this characteristic with read properties is on, nrf send response to read request from this characteristic. i am new in BLE and NRF so i do not know what is exact meaning of rd_auth flag and why nrf did not respond when this flag is 1.

thanks

[Einar Thorsrud]

Hi,

I see. The application need to provide the data when the rd_auth flag is set. The application will get a BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST  event for the SoftDevice (BLE stack), and need to provide the reply using sd_ble_gatts_rw_authorize_reply(). It seems you do not do that. Then the SoftDevice does not know what to do, and as there is no reply, the peer disconnects after the GATT characteristic read timeout (30 s).

[alireza11048]

yes, you are right. as i said i am new in BLE in soft device so excuse me for the bad question.