Setting up APP_TIMER results in hardware fault

[perceptron]

I started with the ble_app_template example. This example uses the Button event and notifies it. I modified the project to send some other data as notification, instead of the button state. And for the data to be read an transmitted, I initialized a timer. My timer_init looks like this,

static void timers_init(void)
{
	uint32_t err_code;
    // Initialize timer module, making it use the scheduler
    APP_TIMER_INIT(APP_TIMER_PRESCALER, APP_TIMER_MAX_TIMERS,     APP_TIMER_OP_QUEUE_SIZE, true);
	
	err_code = app_timer_create(&m_ldc_timer_id,
                                APP_TIMER_MODE_REPEATED,
                                data_timeout_handler);
    APP_ERROR_CHECK(err_code);
}

where data_time_handler is the event handler for the timer.

My timer_start looks like this:

static void timers_start(void)
{
	  uint32_t err_code = app_timer_start(m_timer_id, HEART_RATE_MEAS_INTERVAL, NULL);
    APP_ERROR_CHECK(err_code);
}

Why would I be going in to a hard fault ?

[RK]

What's err_code in the timers_start() function? If not zero then APP_ERROR_CHECK() is sending you into an error.

Why is your variable called m_ldc_timer_id in the initialization and m_timer_id in the timers_start function? What is HEART_RATE_MEAS_INTERVAL?

[perceptron]

I see that the debugger goes in to data_timeout_handler once and thereafter it does not. And it also seems like the debugger does not get into data_event_handler.