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.

WiLink 3.6 API documentation?

Other Parts Discussed in Thread: AM3517

We have a customer who wishes to write user space application software on Linux (kernel 2.6.32) that will interface to the WiLink 3.6 API to perform AP scanning, initiate association, etc. and we are having great difficulty finding documentation for the APIs into the WiLink stack.

The customer has written code that conforms to the standard Linux WiFi API and the wpa_supplicant behavior.  However this code does not work correctly with the WiLink stack.  For example, scanning for access points retrieves at most 13 access points and if the AP you are interested in is not on that list of 13, then you are unable to associate with it.  Customer is having to unload and reload WiLink stack and initiate another scan, with the hope that the AP of interest will end up on the list.  If it doesn't, they unload, reload and try again.  This is the only way they have found that they can get association with a specific access point in the presence of a large number of them.

Customer believes that the API into the WiLink stack is different and requires pointers to documentation on how to correctly develop a Linux application that will function with this stack.  Where do they go for that information?  They are not interested in "shelling out" to wlan_cu or other command line tools but instead wish to code directly to the WiLink stack and build a well behaved application.

The platform is OMAP 3503 + WL1273 and so we have both 2.4 and 5 GHz bands to scan and it is likely that a large number of access points will always be present in the environment where the system will be used.

Where do people go to get WiLink application development support?

 

Chris Elmquist

LogicPD

 

  • Hi Chris,

    Were you referring to WiLink 6.0.3 release (as there is no WiLink 3.6 release)?

    In addition, can you send the ini file? I would like to verify if you work with Manual mode (were the supplicant handles the connection) or Auto mode (were the Driver handles the connection).  As for your question in case someone had requested a Scan and the Scan list is full  then it will be impossible to connect to Access point which is not in the Scan list. However then one will have to request scan with specific SSID in order to perform scan for the desired SSID only, and in case the Driver receives Probe responses from that specific SSID it will enter the Scan results table and then it will be possible to connect to it.

    Please note that if the RSSI of that Access point is very low then it might take time till the Aging mechanism will enter that SSID to the AP scan list since there are other AP in the list with higher RSSI, so in that case it requires to perform several Scans with specific SSID till it appears in the list. Any way to unload the Driver and then loading is not the way to handle that situation.

    Regards,

    Eyal

  •  

    Hi Eyal…

    I certainly admit to being confused by the WiLink version numbers.  We have always refered to it as “i3.6” and it comes from this GIT tree,

    http://dev.omapzoom.org/?p=vijay/wlan.git;a=commit;h=ca16fa9650abcce671f225c290ce20f46d2b4055

     

    which you find along with these other WLAN feature trees,

    http://dev.omapzoom.org/?p=vijay/wlan.git;a=summary

     

    We refer to this in all of our documentation for things like AM3517 Dev Kit, etc.

     

    Where is _THE_ definitive source for the latest WiLink tree for Linux 2.6.32?

     

    Chris

  • Hi Chris,

    Let me verify about that release and get back to you.

    Regards,

    Eyal

  • Thank you Eyal...

     

    Ultimately, what we really need is a pointer to the latest WiLink stack, firmware and INI files for WL1273 and Linux 2.6.32 kernel.

    We have encountered a number of issues with application software incompatibility into the stack (WiLink 3.6 as we know it) and

    proper functioning of band scan on 2.4 and 5.7 GHz (such as a maximum of 13 access points only visible) as well as calibration

    difficulty on 5.7 GHz such as lower than expected output power, etc.

     

    So, we would like to make sure that we have the latest and best software stack that TI are recommending for this device on Linux 2.6.32.

     

    Thank you.

     

    Chris

    LogicPD