sd_ble_gap_adv_start from gpiote_event_handler (button) not working

[Maik]

hi, I currently stuck in the follow section:

static void gpiote_event_handler(uint32_t pins_low_to_high, uint32_t pins_high_to_low)
{
    if (pins_high_to_low & (1 << BUTTON_0))
    {
    	if(!is_advertising){
    		//NRF_TWI1->ENABLE = TWI_ENABLE_ENABLE_Disabled;
                err_code = sd_ble_gap_adv_start(&m_adv_params);
    		is_advertising = ((err_code == 0) ? true : false);
    	}
    }
}

where sd_ble_gap_adv_start(..) never turns back from

SVCALL(SD_BLE_GAP_ADV_START, uint32_t, sd_ble_gap_adv_start(ble_gap_adv_params_t const * const p_adv_params));

If I put err_code = sd_ble_gap_adv_start(&m_adv_params); in the main loop for the main "for" loop e.g. like in hrs sample is done, it is working fine.

Regards

[Janek Mann]

gpiote_event_handler is called from the GPIOTE_IRQHandler interrupt context so it's not surprising that sd_ble_gap_adv_start doesn't work there. You could either set a flag in gpiote_event_handler and check for the flag in your main loop, or use the app_button.c library with the scheduler.

[Ole Morten]

It has to do with priorities, and is described in the section Application Program Interface section of the appendix of the nRF51 Reference Manual. Beware that you can also work around this by reducing the priority of the GPIOTE interrupt to 3.