• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 40 subscribers
  • Views 251 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Choice of Masking Events

KrithikChandrashekar
Expert 1010 points

I see this function: wlan_set_event_mask(HCI_EVNT_WLAN_KEEPALIVE | HCI_EVNT_WLAN_UNSOL_INIT | HCI_EVNT_WLAN_ASYNC_PING_REPORT); being called in the application files. 

1. Is there any reason for those particular events being chosen?
2. What would be the consequence of not masking those events? 
3. Is the order in which the function is called, important?  

  • 0
    Genius 3320 points

    K,

    Those events are chosen so that we are not handling events constantly that we don't need to service.  The keepalive is a heartbeat to the device, the ping shows up when we are pinging the device.  The ordering in which this mask is set is not important.  There is no priority, but a bit level mask that includes whether or not that event is going to be sent back from the CC3000.  The consequence of not masking those events is that we may be recieving more events than we would care to recieve from the CC3000.  If you have the bandwidth with the rest of your application then feel free to comment out the masking of those events.

    -Jason