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

Configuring the WiLink8 Target

WiLink8 driver is provided with default wl18xx-conf.bin binary file. /lib/firmware/ti-connectivity/wl18xx-conf.bin configures the require RF parameters, number of antennas used, desired band of operation etc. This file needs to be altered based on the flavor of the WL18xx device or module used in the setup. To simply the process of generating the wl18xx-conf.bin (located at /lib/firmware/ti-connectivity), the R8.8 release includes a configuration script that can be used for making the right selections based on the HW configuration. The following section details the usage of the “configure-device.sh” script. The script will update the existing wlconf file with selected options. Note the values programmed affects RF performance and accurate values are needed for passing certification.

configure-device.sh is a menu driven script. The script will ask hardware dependent questions that will be used to correctly configure the target for use with the WiLink 8 device. This script uses 'wlconf' utility to create WiLink8 configuration binary. WiLink™ 8 Solutions WiLink8 – wlconf contains more details on 'wlconf' utility and how to modify this configuration.

To begin complete bring up procedure listed above and make sure WiLink8 device is booted. Establish a serial connection with the target device and log in as root.

Navigate to the location of the script /usr/sbin/wlconf and run configure-device.sh:

cd /usr/sbin/wlconf
./configure-device.sh

The script will take you through a series of hardware-dependent questions, and configure wlconf for your system. This script can be used for WiLink8 TI modules, non-TI modules or chip on board designs. Examples are shown below.

When using the WiLink8 TI module, the script will automatically pick the right INI file from /usr/sbin/wlconf/official_inis:

Example for WL1837 without Japanese Certification:

root@am335x-evm:/usr/sbin/wlconf# ./configure-device.sh

Please provide the following information.

Are you using a TI module? [y/n] : y
What is the chip flavor? [1801/1805/1807/1831/1835/1837 or 0 for unknown] : 1837
Should Japanese standards be applied? [y/n] : n
How many 2.4GHz antennas are fitted? [1/2] : 2
How many 5GHz antennas are fitted (using 2 antennas requires a proper switch)? [0/1/2] : 1
[  106.068069] wlcore: down
---------------------------------------------------------

The device has been successfully configured.
TI Module: y
Chip Flavor: 1837
Base INI file used: /usr/sbin/wlconf/official_inis/WL1837MOD_INI_FCC_CE.ini
Number of 2.4GHz Antennas Fitted: 2
Number of 5GHz Antennas Fitted: 1
Diversity Support: y
SISO40 Support: y
Japanese Standards Applied: n

---------------------------------------------------------
Example for WL1801 

root@am335x-evm:/usr/sbin/wlconf# ./configure-device.sh

Please provide the following information.

Are you using a TI module? [y/n] : y
What is the chip flavor? [1801/1805/1807/1831/1835/1837 or 0 for unknown] : 1801
Should SISO40 support be applied? [y/n] : y
[  539.778261] wlcore: down

---------------------------------------------------------
The device has been successfully configured.
TI Module: y
Chip Flavor: 1801
Base INI file used: /usr/sbin/wlconf/official_inis/WL1835MOD_INI_C2PC.ini
Number of 2.4GHz Antennas Fitted: 1
Number of 5GHz Antennas Fitted: 0
Diversity Support: n
SISO40 Support: y
Japanese Standards Applied: n
---------------------------------------------------------

The WiLink8 chip on board or non-TI Module configuration the script will pick /usr/sbin/wlconf/official_inis/WL8_COB_INI.ini. TI provides template of this file. Customers will need to modify RF parameters in this file as per their design or use the values from respective module vendor.

root@am335x-evm:/usr/sbin/wlconf# ./configure-device.sh

Please provide the following information.

Are you using a TI module? [y/n] : n
What is the chip flavor? [1801/1805/1807/1831/1835/1837 or 0 for unknown] : 1837
How many 2.4GHz antennas are fitted? [1/2] : 2
How many 5GHz antennas are fitted (using 2 antennas requires a proper switch)? [0/1/2] : 1
[  148.158965] wlcore: down

---------------------------------------------------------

The device has been successfully configured.
TI Module: n
Chip Flavor: 1837
Base INI file used: /usr/sbin/wlconf/official_inis/WL8_COB_INI.ini
Number of 2.4GHz Antennas Fitted: 2
Number of 5GHz Antennas Fitted: 1
Diversity Support: n
SISO40 Support: y
Japanese Standards Applied: n

---------------------------------------------------------