nrf51822 How to bond about hid device for windows

RE: nrf51822 How to bond about hid device for windows

Hung Bui — Tue, 02 Aug 2016 12:27:13 GMT

Hi mizuho, I assume that it worked now. The CCCD is set locally when reconnected to a bonded device by calling sd_ble_gatts_sys_attr_set() with the correct attribute value.

RE: nrf51822 How to bond about hid device for windows

mizuho — Tue, 02 Aug 2016 07:18:55 GMT

Thank you very much! It was confirmed that you can communicate thanks to you. When the peripheral went on Bonding, I can understand that the peripheral can communicate without confirmation of BLE_HIDS_EVT_NOTIF_ENABLED. That needed only to call "sd_ble_gatts_hvx".

RE: nrf51822 How to bond about hid device for windows

mizuho — Tue, 02 Aug 2016 02:08:33 GMT

Hi, Thank you very much for your answer. I understand movement of the central. And I don't understand a way of start sending notification after reconnection. After the peripheral did bonding and event entered BLE_GAP_EVT_SEC_INFO_REQUEST and exchanged key, event enter BLE_GAP_EVT_CONN_SEC_UPDATE. Is a special way necessary between those? Or is there a way to make an event by "on_hids_evt" begin intentionally in the peripheral? (Sorry, I don't have development dongle.)

RE: nrf51822 How to bond about hid device for windows

Hung Bui — Mon, 01 Aug 2016 12:10:19 GMT

@mizuho: If the device is bonded and get reconnected, the central doesn't have to enable notification again. The peripheral should detect it's a reconnection and start sending notification. If you can capture a sniffer trace (from the time you first connect and bond, then disconnect and reconnect) it would be easier to understand what could be wrong here.