nrf51822EK on kit button triggering

RE: nrf51822EK on kit button triggering

Hamza — Fri, 18 Sep 2015 20:15:22 GMT

YOu deserve noble prize for this Stefan. I had the same problem , and now it is solved. Thankyou so much.... :)

RE: nrf51822EK on kit button triggering

Stefan Birnir Sverrisson — Fri, 18 Sep 2015 16:34:12 GMT

Hi Mohib

Since you are using the evaluation kit, my guess is that you are using SDK 6.1.0 or older, since that is still compatible with the nRF51 revision 2, which resides on the evaluation kit.

For SDK 6.1.0, you can take a look at e.g. the pin_change_int_example, which I think does exactly what you are asking for. It uses GPIOTE directly. However, the example does not implement any de-bounce function, so when pressing the button on the ev-kit, you will occasionally not see the led turn on, because the signal possibly bounces and the led is both turned on and off by a single button press.

The app_button library does however implement a de-bounce function. The debounce function of app_button is very simple

When a button is pressed, a timer is started
when the timer expires, button state is read and an event to the application is given with the state of the button
same is done when a button is released as when button is pressed

You can see an example how app_button library is used by looking at the ble_app_bsp example which is set up with softdevice. The steps required to include a button function is:

include the app_button library in your project
The app_button library uses both app_timer and app_gpiote libraries, so you need to initialize those before initializing app_button library in a similar way as done in the ble_app_bps example with call to the APP_TIMER_INIT and APP_GPIOTE_INIT macros
Create app_button array, as done in button_init() function in the ble_app_bps example
Create button handler, as done with button_event_handler in the ble_app_bps example. The app_button_handler will fire both when you press the button and release the button. Read what button state triggered the handler by reading button_action
Initialize the button library with call to APP_BUTTON_INIT macro. There you define with BUTTON_DETECTION_DELAY how long time should elapse from the button press until reading the button state and give event to the application
Enable buttons with call to app_button_enable(), which is done in ble_app_bps when BLE connection has been established, but you could also do it right away after calling APP_BUTTON_INIT
You may need to increase the APP_TIMER_MAX_TIMERS constant since the button library uses one app_timer per button.

For more advanced de-bounce function than app_button implements, you can look at the debouncer_example in nRF51 SDK 6.1.0. It implements so-called integrator debouncer. The method is fairly simple and its basics are explained on this link and the method is best explained with the following:

real signal 0000111111110000000111111100000000011111111110000000000111111100000
corrupted   0100111011011001000011011010001001011100101111000100010111011100010
integrator  0100123233233212100012123232101001012321212333210100010123233321010
output      0000001111111111100000001111100000000111111111110000000001111111000

RE: nrf51822EK on kit button triggering

Stefan Birnir Sverrisson — Fri, 18 Sep 2015 12:17:16 GMT

Hi Mohib

Can you report what SDK version you are using and what softdevice and what version you are working with. Also, what version of the evaluation kit you have. How is your setup, do you have two evaluation boards, one multilink central and one for multilink peripheral?

RE: nrf51822EK on kit button triggering

Mohib — Wed, 16 Sep 2015 14:50:10 GMT

I couldnot find any function like bsp_event_handler .

RE: nrf51822EK on kit button triggering

MartinBL — Thu, 10 Sep 2015 12:41:32 GMT

You can look into the GPIOTE functionality and drivers. I don't think we have any good examples for GPIOTE right now. There is just this. I can only advice you to read the GPIOTE chapter in the Reference Manual and the driver documentation. What you want to do is to make an interrupt that triggers on both high-to-low and low-to-high events on a pin. Then look at the code in the bsp_event_handler() function in the multilink peripheral and implement it in your GPIOTE interrupt handler.

RE: nrf51822EK on kit button triggering

Mohib — Wed, 09 Sep 2015 15:42:38 GMT

What this routine should be like ? and where should it be coded ?

RE: nrf51822EK on kit button triggering

MartinBL — Wed, 09 Sep 2015 08:59:48 GMT

It looks like the Board Support Package (bsp) used in the example to handle the button events only supports button presses or button releases. In the example the button event handler is configured to trigger only on button pushes. So to make your peripheral to act like want you will need to write your own gpiote interrupt routine that triggers on both events.