cc2530 znp uart program flow

Hi Yikai,

here i have included sniffer log file. I am facing problem that device is getting disconnected from  the network after sometimes. I have attached part of my event handling code also which i suspect may be reason for this behaviour.

#define TEMPERATURE_SENSING_EVENT       0XFF00

//function for setting event when data is received at ZED
void zb_ReceiveDataIndication( uint16 source, uint16 command, uint16 len, uint8 *pData )
{
    osal_set_event ( sapi_TaskID, TEMPERATURE_SENSING_EVENT);	//setting event for sensing temperature
}

//function for event handling for ZED
void zb_HandleOsalEvent( uint16 event )
{
  uint8 *pData,sensor_data;
  if ( event & MY_START_EVT )
  {
    zb_StartRequest();
  }
 
  if ( event & MY_FIND_COLLECTOR_EVT )
  {
    // Find and bind to a collector device
    zb_BindDevice( TRUE, SENSOR_REPORT_CMD_ID2, (uint8 *)NULL );
  }

  if( event & TEMPERATURE_SENSING_EVENT)
  {
    sensor_data = 0x01;
    pData = "@TEM####" ;
    zb_SendDataRequest( 0xFFFE, SENSOR_REPORT_CMD_ID2, 8, pData, 0, AF_ACK_REQUEST, 0 );//(for now using broadcast but will change at later stage
    event |= (event ^ TEMPERATURE_SENSING_EVENT);	//resetting temperature sensing event
  }
}



I had tried above handling event like this also but then also result is same

  if( event & TEMPERATURE_SENSING_EVENT)
  {
    pData = "@TEM####" ;
    zb_SendDataRequest( 0xFFFE, SENSOR_REPORT_CMD_ID, 8, pData, 0, AF_ACK_REQUEST, 0 );    
    event &= ~TEMPERATURE_SENSING_EVENT;	//resetting temperature sensing event
  }

snif_log_23jan_7pm.psd

OSAL event uses bit flag on uint16. You can't define TEMPERATURE_SENSING_EVENT 0xFF00. You should define TEMPERATURE_SENSING_EVENT 0x0001.

Ya, 0x0004 and 0x0008 are being used for other events also.

1) I don't have more knowledge about z-stack but if you don't mind why they have specified range for events as you can see below?

Bit mask of events ( from 0x0000 to 0x00FF ) in SimpleSensor.c file

Below are some definition of pre-defined events in z-stack and these are not defined by me.

// Application osal event identifiers

// Bit mask of events ( from 0x0000 to 0x00FF )

#define MY_START_EVT                0x0001

#define MY_REPORT_TEMP_EVT          0x0002

#define MY_REPORT_BATT_EVT          0x0004

#define MY_FIND_COLLECTOR_EVT       0x0008

These events are also pre-defined in z-stack in hal_drivers.h file

#define HAL_KEY_EVENT 0x0001
#define HAL_LED_BLINK_EVENT 0x0002
#define HAL_SLEEP_TIMER_EVENT 0x0004
#define PERIOD_RSSI_RESET_EVT 0x0008

2)Why they have defined two events as you can see above with same value? Is it due to two events are defined in seperate files or for two different layers(HAL and OSAL) so there is no problem with its use.

3)So will these events not disturb other event if i use 0x0001,0x0002?

Thanks

Hi Yikai,

Here i have included sniffer log file of communication in between coordinator and philips hue. As you can see in the log file the hue is constantly and repeatedly sending beacon request, short address is being assigned to the hue but end point request and response is not made. I had tried to debug but control doesn't come to either of the three cases case Device_annce:, case Active_EP_rsp:,case Simple_Desc_rsp: .

Can you please suggest some idea how to troubleshoot it. Which application is required for communicating with these types of devices(readymade)?

Thanks

snif_log_28Jan15_11am.psd

• Ya, i had tried to download new z-stack example code but result is same. here i have included snapshot of setting for erasing flash. Do i need to erase secondary memory also?  

So, your program still runs well on old HW, right? You can try to debug and see if your end device program stuck in ZDAppCheckForHoldKey() in ZDApp.c using new HW.

I had left my new device powered on for last one hour and sniffer captured some data. here i have included sniffer log file for my new device. I don't know what it is. May be you can get something from it. my device is configured as end device.

a.psd