RE: GPIOTE INPUT simple use with SDK 11.0.0

Bee — Mon, 29 Aug 2016 06:10:51 GMT

I've tried your codes. Thank you for help. It works!

RE: GPIOTE INPUT simple use with SDK 11.0.0

Bee — Fri, 26 Aug 2016 14:49:05 GMT

Thank you. So it means that the event function I wrote is in the right type, is it?

RE: GPIOTE INPUT simple use with SDK 11.0.0

Petter Myhre — Fri, 26 Aug 2016 14:25:15 GMT

Firstly I recommend you to test peripheral without the SoftDevice first. Secondly I recommend checking the returned error codes of functions calls. Anyways:

On PCA10028 Button 1 is not connected to pin 13, but pin 17.

Pin 17 will be high when the button is not pushed, and it will be low when the button is pushed, so maybe you want to use HITOLO instead of LOTOHI.

You should check the returned error code of nrf_drv_gpiote_in_init(), it will give an error because the BSP module has connected a GPIOTE channel to pin 17. Comment out buttons_leds_init() to avoid this.

You need to enable the in event for the pin.

You should have something like this:

//buttons_leds_init(&erase_bonds);

const nrf_drv_gpiote_in_config_t config = GPIOTE_CONFIG_IN_SENSE_HITOLO(true);

err_code = nrf_drv_gpiote_init();
APP_ERROR_CHECK(err_code);

err_code = nrf_drv_gpiote_in_init(17, &config, event);
APP_ERROR_CHECK(err_code);

nrf_drv_gpiote_in_event_enable(17, true);