µC/TCP-IP supports only wireless devices which include an integrated wireless supplicant (i.e., the client-side software that performs scan and login requests). This kind of hardware requires you to send management commands to the device to accomplish some operation such as scan, join, set MAC address, etc. Some of these management commands may take a while to be completed. For those commands most of the wireless devices return the command result via a management frame which must be received like a packet. So, the Wireless Manager must provide mechanisms to send management commands, and then return once the management command is completed.
The Wireless Manager API should be implemented as follows:
μC/TCP-IP provides code that is compatible with most wireless device that embed the wireless supplicant. However, extended functionality must be implemented on a per wireless device basis. If additional functionality is required, it may be necessary to create an application specific Wireless Manager.
Note: It is the Wireless Manager developers’ responsibility to ensure that all of the functions listed within the API are properly implemented and that the order of the functions within the API structure is correct.
This sections that follow describe the interactions between the device driver and the Wireless Manager layer provided with µC/TCP-IP.