VAR-SOM-AM33 Wireless LAN: Difference between revisions

From Variscite Wiki
(Created page with "= WLAN = ''' VAR-SOM-AM33 V2.X only:''' <br> When using VAR-SOM-AM33 v2.x, SOM has a WL183x module. In that case you should configure the WL183x module as follows (only in th...")
 
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
= WLAN =
= WiLink WLAN module configuration =
''' VAR-SOM-AM33 V2.X only:''' <br>
''' VAR-SOM-AM33 V2.X only:''' <br>
When using VAR-SOM-AM33 v2.x, SOM has a WL183x module. In that case you should configure the WL183x module as follows (only in the first boot):
When using VAR-SOM-AM33 v2.x, SOM has a WL183x module. In that case you should configure the WL183x module as follows (only in the first boot):
Line 5: Line 5:
$ cd /usr/bin/wlconf/
$ cd /usr/bin/wlconf/
$ ./configure-device.sh
$ ./configure-device.sh
Then choose the correct number of module and antennas on board
</pre>
 
Then choose the correct number of module and antennas on board. For example:</br>
 
For WL1831:
For example for WL1831:
<pre>
 
root@varsomam33:/usr/bin/wlconf# ./configure-device.sh
root@varsomam33:/usr/bin/wlconf# ./configure-device.sh


Line 29: Line 28:
root@varsomam33:/usr/bin/wlconf# [  713.882024] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
root@varsomam33:/usr/bin/wlconf# [  713.882024] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[  713.909501] wlcore: loaded
[  713.909501] wlcore: loaded
</pre>


 
For WL1837:
For example for WL1837:
<pre>
 
root@varsomam33:/usr/bin/wlconf# ./configure-device.sh
root@varsomam33:/usr/bin/wlconf# ./configure-device.sh


Line 54: Line 53:
root@varsomam33:/usr/bin/wlconf# [  872.471817] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
root@varsomam33:/usr/bin/wlconf# [  872.471817] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[  872.499145] wlcore: loaded
[  872.499145] wlcore: loaded
</pre>


</pre>
= General usage =
'''General usage:''' <br>
List SSIDs, from Linux shell type:  
List SSIDs, from Linux shell type:  
<pre>$&nbsp;ifconfig wlan0 up
<pre>$&nbsp;ifconfig wlan0 up
Line 72: Line 71:
</pre>
</pre>


* WL12xx calibration tool
= MAC address settings =
Calibration of TI WL12xx wireless device is required and is saved into the NVS file. The NVS file is then used by the wl12xx driver.
In order to use the built-in TI unique mac address of the module, change the wl1271-nvs.bin file using the calibrator application:
For more details please read [http://processors.wiki.ti.com/index.php/WL12xx_NLCP_Calibration_Process NLCP Calibration Process]
 
First time need to set mac address to be used automatically
<pre>
<pre>
$ calibrator set nvs_mac /lib/firmware/ti-connectivity/wl1271-nvs.bin 00:00:00:00:00:00
$ calibrator set nvs_mac /lib/firmware/ti-connectivity/wl1271-nvs.bin 00:00:00:00:00:00
reboot system!
</pre>
</pre>
Note: This operation should be done only once
The WLAN MAC addresses for the supported devices are derived as follows:
*BD_ADDR: 08:00:28:00:00:00
*WLAN 1: 08:00:28:00:00:01
*WLAN 2: 08:00:28:00:00:02
When deriving the WLAN addresses from the BD_ADDR, ensure that the organizational unique identifier (OUI) is not changed. <br>
The OUI (first 3 bytes) is pre-assigned by the IEEE to different companies (for example, the TI OUI is 08:00:28). The company that owns the OUI assigns the network identification card (NIC) address (last 3 bytes).

Latest revision as of 13:55, 24 December 2015

WiLink WLAN module configuration

VAR-SOM-AM33 V2.X only:
When using VAR-SOM-AM33 v2.x, SOM has a WL183x module. In that case you should configure the WL183x module as follows (only in the first boot):

$ cd /usr/bin/wlconf/
$ ./configure-device.sh

Then choose the correct number of module and antennas on board. For example:
For WL1831:

root@varsomam33:/usr/bin/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] : 1831
Should SISO40 support be applied? [y/n] : n

The device has been successfully configured.
TI Module: y
Chip Flavor: 1831
Number of 2.4GHz Antennas Fitted: 1
Number of 5GHz Antennas Fitted: 0
Diversity Support: n
SISO40 Support: n
Japanese Standards Applied: n

root@varsomam33:/usr/bin/wlconf# [  713.882024] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[  713.909501] wlcore: loaded

For WL1837:

root@varsomam33:/usr/bin/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? [0/1/2] : 2

The device has been successfully configured.
TI Module: y
Chip Flavor: 1837
Number of 2.4GHz Antennas Fitted: 2
Number of 5GHz Antennas Fitted: 2
Diversity Support: y
SISO40 Support: y
Japanese Standards Applied: n

root@varsomam33:/usr/bin/wlconf# [  872.471817] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[  872.499145] wlcore: loaded

General usage

List SSIDs, from Linux shell type:

$ ifconfig wlan0 up
$ iw wlan0 scan

Connecting to an encrypted network:

Find your network from the above scan command.

$ wpa_passphrase <YourAP> <YourPassword> >wpa.conf
$ ps | grep wpa_supplicant
*kill the wpa_supplicant process if exist.
$ wpa_supplicant -Dnl80211 -iwlan0 -c./wpa.conf -B
$ udhcpc -iwlan0
$ ifconfig

MAC address settings

In order to use the built-in TI unique mac address of the module, change the wl1271-nvs.bin file using the calibrator application:

$ calibrator set nvs_mac /lib/firmware/ti-connectivity/wl1271-nvs.bin 00:00:00:00:00:00
reboot system!

Note: This operation should be done only once


The WLAN MAC addresses for the supported devices are derived as follows:

  • BD_ADDR: 08:00:28:00:00:00
  • WLAN 1: 08:00:28:00:00:01
  • WLAN 2: 08:00:28:00:00:02

When deriving the WLAN addresses from the BD_ADDR, ensure that the organizational unique identifier (OUI) is not changed.
The OUI (first 3 bytes) is pre-assigned by the IEEE to different companies (for example, the TI OUI is 08:00:28). The company that owns the OUI assigns the network identification card (NIC) address (last 3 bytes).