Timer for CC2530

Hey,

One more thing, I am using IAR embedded workbenchversion 7.60

Thanks 

S I

The best way is to create a task and add it to the OSAL initialization file.  I will assume you are using SampleApp that comes with the CC2530 ZStack download, but the methodology follows for any project using AF.h, the ZStack application framework.

First, I would create a new task in new .c and .h files.

In the header file, say new_task.h, I would add the events, the public prototypes and public variables:

//////
/// Events.
//////
#define EVENT_new_task_start 0x0001
#define EVENT_new_task_stop 0x0002

#if  ( HAL_LED == TRUE  )
#define EVENT_new_task_blink 0x0004
#endif

//////
/// Public variables.
//////
extern uint8 PUBLIC_task_id_new_task;


//////
/// Public prototypes.
//////
void new_task_init ( uint8 task_id );
uint16 new_task_process_event ( uint8 task_id, uint16 events );

Then, in new_task.c, I would add local variables, the initialization function and the event process function.

//////
/// Includes.
//////

#include "AF.h"

#if (HAL_LED == TRUE)
#include "hal_led.h"
#endif

#include "new_task.h"


//////
/// Variables.
//////

// The task ID.
T_uint8 PUBLIC_task_id_new_task;


/**
 * Initialize the task.
 */
void new_task_init ( T_uint8 task_id )
{

	PUBLIC_task_id_new_task = task_id;

}

/**
 * Event handler.
 */
T_uint16 new_task_process_event ( T_uint8 task_id, T_uint16 events )
{

	/**
	 * Start event.
	 */
	if ( events & EVENT_new_task_start )
	{

		// Start a periodic blink event at 1Hz.
		osal_start_reload_timer ( PUBLIC_task_id_new_task, EVENT_new_task_blink, 1000 );

		// Clear event and return.
		return ( events ^ EVENT_new_task_start);

	}


	/**
	 * Stop event.
	 */
	if ( events & EVENT_new_task_stop )
	{

		// 10ms blink, I think.
		osal_stop_timerEx ( PUBLIC_task_id_new_task, EVENT_new_task_blink );

		// Clear event and return.
		return ( events ^ EVENT_new_task_stop);


	}


	/**
	 * Blink event.
	 */
	#if ( HAL_LED == TRUE )
	if ( events & EVENT_new_task_blink )
	{

		// 10ms blink, I think.
		HalLedBlink(HAL_LED_1, 1, 10, 1000);

		// Clear event and return.
		return ( events ^ EVENT_new_task_blink);


	}
	#endif

	// Return unrecognized events.
	return (0);

}

Finally, you will need to register the task wil the OSAL, which is done in OSAL_SampleApp.c by adding the initialization function and process_event function references.  I have copied in the code from OSAL_SampleApp.c and highlighted the lines added to register new_task in red:

/*********************************************************************
 * INCLUDES
 */

#include "ZComDef.h"
#include "hal_drivers.h"
#include "OSAL.h"
#include "OSAL_Tasks.h"

#if defined ( MT_TASK )
  #include "MT.h"
  #include "MT_TASK.h"
#endif

#include "nwk.h"
#include "APS.h"
#include "ZDApp.h"
#if defined ( ZIGBEE_FREQ_AGILITY ) || defined ( ZIGBEE_PANID_CONFLICT )
  #include "ZDNwkMgr.h"
#endif
#if defined ( ZIGBEE_FRAGMENTATION )
  #include "aps_frag.h"
#endif

#include "SampleApp.h"

#include "new_task.h"

/*********************************************************************
 * GLOBAL VARIABLES
 */

// The order in this table must be identical to the task initialization calls below in osalInitTask.
const pTaskEventHandlerFn tasksArr[] = {
  macEventLoop,
  nwk_event_loop,
  Hal_ProcessEvent,
#if defined( MT_TASK )
  MT_ProcessEvent,
#endif
  APS_event_loop,
#if defined ( ZIGBEE_FRAGMENTATION )
  APSF_ProcessEvent,
#endif
  ZDApp_event_loop,
#if defined ( ZIGBEE_FREQ_AGILITY ) || defined ( ZIGBEE_PANID_CONFLICT )
  ZDNwkMgr_event_loop,
#endif
  new_task_process_event,
  SampleApp_ProcessEvent
};

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

/*********************************************************************
 * FUNCTIONS
 *********************************************************************/

/*********************************************************************
 * @fn      osalInitTasks
 *
 * @brief   This function invokes the initialization function for each task.
 *
 * @param   void
 *
 * @return  none
 */
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++ );
#if defined ( ZIGBEE_FRAGMENTATION )
  APSF_Init( taskID++ );
#endif
  ZDApp_Init( taskID++ );
#if defined ( ZIGBEE_FREQ_AGILITY ) || defined ( ZIGBEE_PANID_CONFLICT )
  ZDNwkMgr_Init( taskID++ );
#endif
  new_task_init (taskID++);
  SampleApp_Init( taskID );
}

You need to call osal_set_event ( PUBLIC_task_id_new_task, EVENT_new_task_start ), in SampleApp.c you could do that in state change:

       case ZDO_STATE_CHANGE:
          SampleApp_NwkState = (devStates_t)(MSGpkt->hdr.status);
          if ( (SampleApp_NwkState == DEV_ZB_COORD)
              || (SampleApp_NwkState == DEV_ROUTER)
              || (SampleApp_NwkState == DEV_END_DEVICE) )
          {

            // Start new_tast.
            osal_set_event( PUBLIC_task_id_new_task,
                              EVENT_new_task_start );

            // Start sending the periodic message in a regular interval.
            osal_start_timerEx( SampleApp_TaskID,
                              SAMPLEAPP_SEND_PERIODIC_MSG_EVT,
                              SAMPLEAPP_SEND_PERIODIC_MSG_TIMEOUT );

          }

To be more interactive, you could set the start and stop events using key handler.  Add osal_set_event ( PUBLIC_task_id_new_task, EVENT_new_task_start ) to one key, and osal_set_event ( PUBLIC_task_id_new_task, EVENT_new_task_stop ) to another.  Despite such limited functionality, I be there's something deeply satisfying about it.  :)

I hope this helps.

iR.

I should just point out that you could just drop the HalLedBlink(HAL_LED_1, 1, 10, 1000) into the existing event handler for SAMPLEAPP_SEND_PERIODIC_MSG_EVT in SampleApp but I am assuming that you want to do more than just blink an LED, in the long run.  Indeed, you might not be using the SampleApp, in which case I hope that this translates meaningfully into whatever application context you are working in.  By building a new task I think you get a much better and more useful feel for using the ZStack Application Framework.

I hope I didn't scare you off with the large post and that you find it helpful.

iR.