app_timer stop working after upgrade from 4.3 to 5.2

[julian]

it just the typical button_timeout, in 4.3 no problem to accept call back

	// Create button polling timer
	err_code = app_timer_create(&m_detection_button_timer_id,
													APP_TIMER_MODE_SINGLE_SHOT,
													button_timeout_handler);

	// Start the timer
	button_timeout_active_event = (1 << IO_PORT_INT_BUTTON);
	err_code = app_timer_start(m_detection_button_timer_id,
														 BUTTON_DETECTION_DELAY, NULL);

above call called but button_timeout_handler never called after upgrade to 5.2, clock is handled by sd:

	uint32_t p_is_running;
	
	sd_clock_hfclk_request();
	do
	{
		sd_clock_hfclk_is_running(&p_is_running);
	} while (p_is_running == 0);
	

[julian]

#define APP_TIMER_MAX_TIMERS            16                                       
#define APP_TIMER_OP_QUEUE_SIZE         8                                    

so app_timer size and queue size seem good enough. Two question for this

1. APP_TIMER_MAX_TIMERS is just my app's timer number? or it should include all app_timer_create I found in the code?
2. APP_TIMER_OP_QUEUE_SIZE, how to determine this size?

[julian]

I add below timer event just for test:

static void timer_hander(void * p_context) {
    LOG("timer\r\n");
}
static void timer_test(void) {
    app_timer_id_t timer_id;
    APP_ERROR_CHECK(app_timer_create(&timer_id,
                                                APP_TIMER_MODE_SINGLE_SHOT,
                                                timer_hander));
	APP_ERROR_CHECK(app_timer_start(timer_id, 30000, NULL));

}

I get NRF_ERROR_INVALID_LENGTH in line 340 of app_timer.c

        uint32_t err_code = m_evt_schedule_func(p_timer->p_timeout_handler, p_timer->p_context);
        APP_ERROR_CHECK(err_code);

[julian]

ok it is because I comment out APP_SCHED_INIT(SCHED_MAX_EVENT_DATA_SIZE, SCHED_QUEUE_SIZE); so I get the NRF_ERROR_INVALID_LENGTH, with this back,

same as before, no error, no call back

[julian]

ok, turn out I should remove

 nrf_gpio_cfg_input(IO_PORT_RTC_SCL, NRF_GPIO_PIN_PULLUP);
 nrf_gpio_cfg_input(IO_PORT_RTC_SDA, NRF_GPIO_PIN_PULLUP);

is it used by SD?

[julian]

well, after remove nrf_gpio_cfg_input(IO_PORT_RTC_SCL, NRF_GPIO_PIN_PULLUP); nrf_gpio_cfg_input(IO_PORT_RTC_SDA, NRF_GPIO_PIN_PULLUP);

the system can't stay on sd_app_evt_wait() it suppose to stay there until long press button, but now it fire out every second....