OSAL timer stops working after some time (z-stack with cc2531)

zpl

Other Parts Discussed in Thread: Z-STACK

This is a very simple test of z-stack: toggle the LED light every second. It works fine, till about after 10-15 toggles. then it stops responding. any idea where I did wrong? thanks in advance.

this is what I did:

void zclUartApp_Init( uint8 task_id )
{
  UartApp_TaskID = task_id;
  osal_start_timerEx(UartApp_TaskID, UARTAPP_SEND_MSG, 2000); 
}

Event loop:

uint16 zcl_UartApp_event_loop( uint8 task_id, uint16 events )
{
  unsigned char x[5];
  if ( events & SYS_EVENT_MSG )
  {
    ...
    // Return unprocessed events
    return ( events ^ SYS_EVENT_MSG );
  }

  if ( events & UARTAPP_SEND_MSG )
  {
    HalLedSet(HAL_LED_1,HAL_LED_MODE_TOGGLE); 
    osal_start_timerEx( UartApp_TaskID, UARTAPP_SEND_MSG,
        UARTAPP_SEND_MSG_REPEAT );
    return ( events ^ UARTAPP_SEND_MSG );
  }

}

constants:

#define UARTAPP_SEND_MSG       0x0004
#define UARTAPP_SEND_MSG_REPEAT       1000

Initialization here:

const pTaskEventHandlerFn tasksArr[] = {

macEventLoop,
nwk_event_loop,
Hal_ProcessEvent,
#if defined( MT_TASK )
MT_ProcessEvent,
#endif
APS_event_loop, 
ZDApp_event_loop,
zcl_event_loop,
zcl_UartApp_event_loop
};

const uint8 tasksCnt = sizeof( tasksArr ) / sizeof( tasksArr[0] );
uint16 *tasksEvents;

void osalInitTasks( void )

{
uint8 taskID = 0;

tasksEvents = (uint16 *)osal_mem_alloc( sizeof( uint16 ) * tasksCnt);
osal_memset( tasksEvents, 0, (sizeof( uint16 ) * tasksCnt));

macTaskInit( taskID++ );
nwk_init( taskID++ );
Hal_Init( taskID++ );
#if defined( MT_TASK )
MT_TaskInit( taskID++ );
#endif
APS_Init( taskID++ );
ZDApp_Init( taskID++ );
zcl_Init( taskID++ );
zclUartApp_Init( taskID );
}

over 11 years ago

0 YiKai Chen over 11 years ago

Guru 735695 points

Try to check the return value of osal_start_timerEx to see if the timer is created successfully.

0 zpl over 11 years ago

Prodigy 155 points

One more note:

did some experiment as well as debugging. seems that when it freezes, the event loop osal_run_system() does not even return to the calling function osal_start_system() to start the next iteration. It seems that it is stuck at AESLoadKey, which I have no idea what it is, how it got there, and why it is stuck.

Any one?

0 zpl over 11 years ago in reply to YiKai Chen

Prodigy 155 points

Yes, the timer is indeed created successfully, and the event did pop up every second. but it just stops after ~10 seconds.

0 zpl over 11 years ago in reply to zpl

Prodigy 155 points

To be exact, always 17 seconds, no matter the toggling frequency.

0 YiKai Chen over 11 years ago in reply to zpl

Guru 735695 points

I mean you need to check return value of osal_start_timerEx every time you call it. It might fail to create the timer after 10 seconds because your application use up all timer somewhere else.

0 zpl over 11 years ago in reply to YiKai Chen

Prodigy 155 points

Just checked, timer is always created successfully, even the last one. the problem is that for whatever reason, the event loop stopped.

0 zpl over 11 years ago in reply to zpl

Prodigy 155 points

one new discovery: compiler option HAL_AES=0 will trigger the problem, taking it away solves it. what is HAL_AES anyway?

0 YiKai Chen over 11 years ago in reply to zpl

Guru 735695 points

HAL_AES is for hardware AES encryption/decryption acceleration. Would you specify which ZStack version do you use ?

0 zpl over 11 years ago in reply to YiKai Chen

Prodigy 155 points

z-stack 1.2. thanks a lot for your help.

0 YiKai Chen over 11 years ago in reply to zpl

Guru 735695 points

You should always enable HAL_AES in ZStack if you use Zigbee security, because Zigbee security need to use it.

0 zpl over 11 years ago in reply to YiKai Chen

Prodigy 155 points

yes... thanks... got it now...

Zigbee & Thread

Zigbee & Thread forum

OSAL timer stops working after some time (z-stack with cc2531)