How do I interface external IO pins when app_button is used?

RE: How do I interface external IO pins when app_button is used?

Susheel Nuguru — Thu, 16 Jul 2015 13:48:52 GMT

Yes, override before calling the app_button_init function. If you have energy to experiment more, then you can even reduce debounce_time for that specific pin in app_button.c->gpiote_event_handler replace

err_code = app_timer_start(m_detection_delay_timer_id, m_detection_delay, NULL);

with

  if(external_pin) err_code = app_timer_start(m_detection_delay_timer_id, 5, NULL);
  else err_code = app_timer_start(m_detection_delay_timer_id, m_detection_delay, NULL);

Then you interrupt needs to stay active just for 5 ticks ...

RE: How do I interface external IO pins when app_button is used?

syntroniks — Thu, 16 Jul 2015 13:34:18 GMT

Thanks Aryan and thank you for helping these forums. Can you confirm that this means modifying bsp.c in the RTE folder as opposed taking a weak reference to buttons and overriding it in main.c?

Thankfully my input signal is 100ms long so it will work with the debouncing logic.

RE: How do I interface external IO pins when app_button is used?

Susheel Nuguru — Thu, 16 Jul 2015 07:31:29 GMT

You can configure pin with different trigger level and different pulls with app_buttons static app_button_cfg_t buttons[] = { {BSP_BUTTON_0, APP_BUTTON_ACTIVE_HIGH, NRF_GPIO_PIN_NOPULL, button0_event_handler}, {BSP_BUTTON_1, APP_BUTTON_ACTIVE_LOW, NRF_GPIO_PIN_PULL, button1_event_handler}, };

Else your solution should work well if you use the merge fix.