nRF52832 sleep mode issue

[Reshmi Marimganti]

Req: from the cap-sense board, different tap will be done by user (like 2 times tap, 3 three times tap etc). so the Bluetooth board (nrf52) will receive these taps as interrupt connected to a gpio configured from cap-sense board. Profile Used in Bluetooth board: Proximity . For the requirement stated,

1. firstly, i have added the interrupt functionality (pin_change_int code) into Proximity profile for checking the no of tap received through the gpio as interrupt.
2. secondly, when the tap is made from cap-sense side, the Bluetooth board will read the tap through the gpio assigned as interrupt. Bluetooth board will to do fast adv , slow adv and goes to sleep (separate function buttons_led_init is there in Proximity code), but when interrupt functionality is added to the proximity profile, Bluetooth device is not going to sleep. so what change in code should be done in order avoid this conflict.

[Stefan Birnir Sverrisson]

Hi

I think the ble_ias_c service is a client service. You can only send notifications from a server service. From a client service, you typically read and write to server characteristics.

Also, before sending a notification, you must enable the notification property. Try to look into how this is done in the battery service for the ble_app_proximity, which has notifications enabled and battery information is sent to the phone periodically. Specifically, look at the ble_bas_battery_level_update function. To see how to set the notification property, look at the bas_init function.