Problem with osal timerEx

Hi Sarvana,

Please re-test with 2 different event ids and check if you see the same issue i.e.

if(Get_Val == 0)
{
  --------//Some Process
Get_Val= 1;
osal_start_timerEx( zcl_TaskID , SENSOR_STATUS_1  , 5000);
}

else if(Get_Val == 1)
{
  --------//Some Process
Get_Val= 0;
osal_start_timerEx( zcl_TaskID , SENSOR_STATUS_2  , 13000);
}

Thanks,

Saurabh

Check if you keep creating event but never stop it.

Hello Yikai Chen,

           I didn't get you. What should I stop. Is there any restriction in Coordinator. Which is not working this timer properly.

Sarubh,

        I created different Events, but I am getting same problem.

I mean do you keep calling osal_start_timerEx to create event timer? By the way, I suggest you check if you allocate memory without free it. Memory leak might be another reason.

Yes, I want that event to run after 5 sec if Coord_bit = 0 anf run after 13 sec if Coord_bit =1. This should continuously happen. There is no dynamic memory allocation I have done. 

Try to add osal_stop_timerEx() before you call osal_start_timerEx() like the followings:

if(Get_Val == 0)
{
  --------//Some Process
Get_Val= 1;

osal_stop_timerEx( zcl_TaskID , SENSOR_STATUS);
osal_start_timerEx( zcl_TaskID , SENSOR_STATUS  , 5000);
}

else if(Get_Val == 1)
{
  --------//Some Process
Get_Val= 0;

osal_stop_timerEx( zcl_TaskID , SENSOR_STATUS);
osal_start_timerEx( zcl_TaskID , SENSOR_STATUS  , 13000);
}

Yikai, I have done what you suggested. Then also it is stopping after some times. What may be the problem.

As Yikai alludes, the symptom that you are describing could be caused by a memory allocation failure. The osal_start_timerEx() function does provide an error return and your code should be checking it. If you get a return value that is not SUCCESS, then the timer is not scheduled, and your application will "hang" as you are seeing.