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?
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.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.