to # einar thorsrud
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,
-
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.
-
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.
