SWRU561A September   2020  – October 2020 WL1801MOD , WL1805MOD , WL1807MOD , WL1831 , WL1831MOD , WL1835MOD , WL1837MOD

 

  1.   Trademarks
  2. 1Driver Supported Features
  3. 2WL18xx Linux Driver Architecture Overview
  4. 3Platform Integration
    1. 3.1 Configuration required for Board Device Tree (DTS/DTB)
    2. 3.2 Configuring the Kernel for TI WLAN Drivers
    3. 3.3 Configuration required for Board Device Tree (DTS/DTB)
    4. 3.4 Building R8.8 Release Using Build Utilities
    5. 3.5 Building WiLink8 Driver Release Binaries Individually
  5. 4Booting and WLAN Bring-Up
    1. 4.1 Configuring the WiLink8 Target
  6. 5Testing Basic WLAN Functionality
    1. 5.1 STA Mode
      1. 5.1.1 Station Mode Procedure for Unsecured AP
      2. 5.1.2 Station Mode Procedure for Secured AP
      3. 5.1.3 Verifying Connectivity
    2. 5.2 AP Mode
      1. 5.2.1 AP Mode Procedure
      2. 5.2.2 Starting the AP
      3. 5.2.3 Verifying Connectivity
    3. 5.3 Multirole (AP +STA mode)
      1. 5.3.1 General Procedure for Multirole Connection
    4. 5.4 IEEE802.11s Mesh Mode
  7. 6References
  8.   A FAQ and Debug Hints

5.3.1 General Procedure for Multirole Connection

  1. Start station role.
  2. Connect to an access point.
  3. Start AP role.

The following scripts needs to be run to enable STA and AP role. hostapd.conf updates mentioned in AP role are applicable to this procedure as well. 

./sta_start.sh
./sta_connect-ex.sh exampleSSID WPA-PSK examplepassword
udhcpc -i wlan0
./ap_start.sh

If the default hostapd.conf settings were not changed, the AP should now be broadcasting as SitaraAP while also being connected as a Station to the AP specified in the "Start Station Role" section. To verify the station connectivity, invoke:

iw wlan0 link

The details of the AP you are connected to should show up. To verify the AP broadcast, use any commercial Station (smart phone, laptop, etc.) and connect. You should see a prompt (AP_STA_CONNECTED) when the station successfully connects to the WiLink AP.