Linux/WL1837MOD: Mesh + Access Point errors

Matt Barclay9

Part Number: WL1837MOD

Tool/software: Linux

Hello,

I am running a BeagleBone Black with StreamUnlimited WiFi cape. I have Mesh working and I can get Access Point mode working, but I cannot get Mesh and Access Point at the same time. The document "WiLink 8 WLAN Software - 802.11s Mesh" suggests it can be done:

www.ti.com/.../swaa166.pdf

Section 5.4 gives some instructions for setting it up. Here's what happens when I run the commands (Access Point first, then Mesh):

```

root@meshap4:~# cd /usr/share/wl18xx/
root@meshap4:/usr/share/wl18xx# ./ap_start.sh
adding wlan1 interface
Configuration file: /usr/share/wl18xx/hostapd.conf
wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Using interface wlan1 with hwaddr 7c:ec:79:cc:2a:6e and ssid "SitaraAP"
wlan1: interface state COUNTRY_UPDATE->ENABLED
wlan1: AP-ENABLED

root@meshap4:/usr/share/wl18xx# ./mesh_start.sh
adding mesh0 interface
Successfully initialized wpa_supplicant
root@meshap4:/usr/share/wl18xx# ./mesh_join.sh SitaraMesh 2462
netid=0
=========================
OK
OK
OK
OK
OK
root@meshap4:/usr/share/wl18xx# Using interface mesh0 with hwaddr 7e:ec:79:cc:2a:6d and ssid ""
mesh0: interface state UNINITIALIZED->ENABLED
AP-ENABLED
Could not set interface mesh0 flags (UP): Device or resource busy
nl80211: Failed to set interface into mesh mode
mesh0: Failed to init mesh in driver
mesh0: Failed to init mesh
mesh0: Could not join mesh

```

Or when I start Mesh First then start Access Point:

```

root@meshap4:~# cd /usr/share/wl18xx/
root@meshap4:/usr/share/wl18xx# ./mesh_start.sh
adding mesh0 interface
Successfully initialized wpa_supplicant
mesh0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
root@meshap4:/usr/share/wl18xx# ./mesh_join.sh SitaraMesh 2462
netid=0
=========================
OK
OK
OK
OK
OK
root@meshap4:/usr/share/wl18xx# Using interface mesh0 with hwaddr 7c:ec:79:cc:2a:6e and ssid ""
mesh0: interface state UNINITIALIZED->ENABLED
AP-ENABLED
mesh0: joining mesh SitaraMesh
mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
mesh0: MESH-GROUP-STARTED ssid="SitaraMesh" id=0

root@meshap4:/usr/share/wl18xx# ./ap_start.sh
adding wlan1 interface
Configuration file: /usr/share/wl18xx/hostapd.conf
Could not set interface wlan1 flags (UP): Device or resource busy
nl80211: Could not set interface 'wlan1' UP
nl80211: deinit ifname=wlan1 disabled_11b_rates=0
nl80211 driver initialization failed.
wlan1: interface state UNINITIALIZED->DISABLED
wlan1: AP-DISABLED
hostapd_free_hapd_data: Interface wlan1 wasn't started

```

I am using Yocto to build the TI SDK 04.02.00.09 with Wilink software R8.7_SP3

Has anyone gotten Mesh + AP to work?

Thanks,
Matt

over 8 years ago

0 Eyal Reizer over 8 years ago

TI__Mastermind 20285 points

Hi,

When you use Mesh + AP, they both have to be set on the same channel.
Did you make sure this is the case here?

BR,
Eyal

0 Matt Barclay9 over 8 years ago in reply to Eyal Reizer

Intellectual 795 points

Yes, they are both on channel 11

0 S over 8 years ago in reply to Matt Barclay9

TI__Mastermind 35795 points

Matt, Pls check if wlan0 interface is up as well. In case it is, bring it down before you start the second role.

Saurabh

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

Hello,

Yes, it was up. Taking wlan0 down first changes the error if AP is started before Mesh (hostapd.conf configured for channel 6):

root@meshap4:~# ifconfig wlan0 down

root@meshap4:/usr/share/wl18xx# ./ap_start.sh
adding wlan1 interface
Configuration file: /usr/share/wl18xx/hostapd.conf
wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Using interface wlan1 with hwaddr 7c:ec:79:cc:2a:6e and ssid "SitaraAP"
wlan1: interface state COUNTRY_UPDATE->ENABLED
wlan1: AP-ENABLED

root@meshap4:/usr/share/wl18xx# ./mesh_start.sh
adding mesh0 interface
Successfully initialized wpa_supplicant

root@meshap4:/usr/share/wl18xx# ./mesh_join.sh SitaraMesh 2437
netid=0
=========================
OK
OK
OK
OK
OK
Using interface mesh0 with hwaddr 7e:ec:79:cc:2a:6d and ssid ""

mesh0: interface state UNINITIALIZED->ENABLED
AP-ENABLED
mesh0: joining mesh SitaraMesh
mesh0: mesh join error=-16

mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
mesh0: Could not join mesh
mesh0: Driver failed to insert 7c:ec:79:cc:32:d6: -22

mesh0: Driver failed to insert 7c:ec:79:cc:32:d6: -22

Scanning wireless networks from my laptop reports:

Cell 10 - Address: 7C:EC:79:CC:2A:6E
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=70/70 Signal level=-30 dBm
                    Encryption key:off
                    ESSID:"SitaraAP"

After a power cycle, starting Mesh first and then AP has the same error as I originally reported:

root@meshap4:/usr/share/wl18xx# ifconfig wlan0 down
root@meshap4:/usr/share/wl18xx# ./mesh_start.sh
adding mesh0 interface
Successfully initialized wpa_supplicant
mesh0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
root@meshap4:/usr/share/wl18xx# ./mesh_join.sh SitaraMesh 2437
netid=0
=========================
OK
OK
OK
OK
OK
root@meshap4:/usr/share/wl18xx# Using interface mesh0 with hwaddr 7c:ec:79:cc:2a:6e and ssid ""
mesh0: interface state UNINITIALIZED->ENABLED
AP-ENABLED
mesh0: joining mesh SitaraMesh
mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
mesh0: MESH-GROUP-STARTED ssid="SitaraMesh" id=0

root@meshap4:/usr/share/wl18xx# ./ap_start.sh
adding wlan1 interface
Configuration file: /usr/share/wl18xx/hostapd.conf
wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Using interface wlan1 with hwaddr 7e:ec:79:cc:2a:6d and ssid "SitaraAP"
Failed to set beacon parameters
Interface initialization failed
wlan1: interface state COUNTRY_UPDATE->DISABLED
wlan1: AP-DISABLED
wlan1: Unable to setup interface.
wlan1: interface state DISABLED->DISABLED
wlan1: AP-DISABLED
hostapd_free_hapd_data: Interface wlan1 wasn't started
nl80211: deinit ifname=wlan1 disabled_11b_rates=0

0 S over 8 years ago in reply to Matt Barclay9

TI__Mastermind 35795 points

Matt ,
- reboot the board
- ifconfig - in case wlan0 is up , bring it down
- ./ap_start.sh
- ifconfig - in case wlan0 is up , bring it down
./mesh_start.sh
- ./mesh_join.sh on same channel as AP
share the results

Saurabh

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

hostap-mesh-supplicant-kernel-config.zip

Here is the output. My config files are attached as well...

root@meshap4:~# cd /usr/share/wl18xx/

root@meshap4:/usr/share/wl18xx# ifconfig

eth0 Link encap:Ethernet HWaddr 98:84:E3:9D:8A:92

inet addr:10.42.0.167 Bcast:10.42.0.255 Mask:255.255.255.0

inet6 addr: fe80::9a84:e3ff:fe9d:8a92%763612/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:89 errors:0 dropped:0 overruns:0 frame:0

TX packets:115 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:11490 (11.2 KiB) TX bytes:17562 (17.1 KiB)

Interrupt:48

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1%763612/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:166 errors:0 dropped:0 overruns:0 frame:0

TX packets:166 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:12670 (12.3 KiB) TX bytes:12670 (12.3 KiB)

wlan0 Link encap:Ethernet HWaddr 7C:EC:79:CC:2A:6D

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@meshap4:/usr/share/wl18xx# ifconfig wlan0 down

root@meshap4:/usr/share/wl18xx# ./ap_start.sh

adding wlan1 interface

Configuration file: /usr/share/wl18xx/hostapd.conf

wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE

Using interface wlan1 with hwaddr 7c:ec:79:cc:2a:6e and ssid "SitaraAP"

wlan1: interface state COUNTRY_UPDATE->ENABLED

wlan1: AP-ENABLED

root@meshap4:/usr/share/wl18xx# ifconfig

eth0 Link encap:Ethernet HWaddr 98:84:E3:9D:8A:92

inet addr:10.42.0.167 Bcast:10.42.0.255 Mask:255.255.255.0

inet6 addr: fe80::9a84:e3ff:fe9d:8a92%763612/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:198 errors:0 dropped:0 overruns:0 frame:0

TX packets:192 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:21933 (21.4 KiB) TX bytes:29056 (28.3 KiB)

Interrupt:48

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1%763612/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:172 errors:0 dropped:0 overruns:0 frame:0

TX packets:172 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:13180 (12.8 KiB) TX bytes:13180 (12.8 KiB)

wlan1 Link encap:Ethernet HWaddr 7C:EC:79:CC:2A:6E

inet addr:192.168.43.1 Bcast:192.168.43.255 Mask:255.255.255.0

inet6 addr: fe80::7eec:79ff:fecc:2a6e%763612/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:58 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:10648 (10.3 KiB)

root@meshap4:/usr/share/wl18xx# ./mesh_start.sh

adding mesh0 interface

Successfully initialized wpa_supplicant

root@meshap4:/usr/share/wl18xx# ifconfig

eth0 Link encap:Ethernet HWaddr 98:84:E3:9D:8A:92

inet addr:10.42.0.167 Bcast:10.42.0.255 Mask:255.255.255.0

inet6 addr: fe80::9a84:e3ff:fe9d:8a92%763612/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:312 errors:0 dropped:0 overruns:0 frame:0

TX packets:268 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:32934 (32.1 KiB) TX bytes:40304 (39.3 KiB)

Interrupt:48

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1%763612/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:172 errors:0 dropped:0 overruns:0 frame:0

TX packets:172 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:13180 (12.8 KiB) TX bytes:13180 (12.8 KiB)

mesh0 Link encap:Ethernet HWaddr 7E:EC:79:CC:2A:6D

inet addr:10.20.30.40 Bcast:10.20.30.255 Mask:255.255.255.0

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan1 Link encap:Ethernet HWaddr 7C:EC:79:CC:2A:6E

inet addr:192.168.43.1 Bcast:192.168.43.255 Mask:255.255.255.0

inet6 addr: fe80::7eec:79ff:fecc:2a6e%763612/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:69 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:12282 (11.9 KiB)

root@meshap4:/usr/share/wl18xx# ./mesh_join.sh SitaraMesh 2437

netid=0

=========================

root@meshap4:/usr/share/wl18xx# Using interface mesh0 with hwaddr 7e:ec:79:cc:2a:6d and ssid ""

mesh0: interface state UNINITIALIZED->ENABLED

AP-ENABLED

mesh0: joining mesh SitaraMesh

mesh0: mesh join error=-16

mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]

mesh0: Could not join mesh

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

Please see my results below. Are there any other suggestions on how to get this to work?

0 S over 8 years ago in reply to Matt Barclay9

TI__Mastermind 35795 points

May be supplicant is running on your platform that might be preventing it - run ./sta_stop.sh from /usr/share/wl18xx instead of 'ifconfig wlan0 down' and re-test .

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

wpa_supplicant is not running. Do you have hardware available to test this? I can provide my rootfs, kernel, u-boot, and dtb...

0 S over 8 years ago in reply to Matt Barclay9

TI__Mastermind 35795 points

I ran the test at my end and it works ok .

root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# ifconfig
eth0 Link encap:Ethernet HWaddr D0:5F:B8:7C:6F:73
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::d25f:b8ff:fe7c:6f73%132400/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3163 errors:0 dropped:2 overruns:0 frame:0
TX packets:3148 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:441987 (431.6 KiB) TX bytes:251562 (245.6 KiB)
Interrupt:173

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%132400/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:228 errors:0 dropped:0 overruns:0 frame:0
TX packets:228 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:18303 (17.8 KiB) TX bytes:18303 (17.8 KiB)

usb0 Link encap:Ethernet HWaddr 5A:08:DB:82:D9:90
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr 54:4A:16:38:37:93
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# ifconfig wlan0 down
[ 1961.594098] wlcore: down
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# ./mesh_start.sh
adding mesh0 interface
Successfully initialized wpa_supplicant
[ 1964.703055] wlcore: version = 100860185
[ 1964.706986] wlcore: PHY firmware version: Rev 8.2.0.0.242
[ 1964.849276] wlcore: firmware booted (Rev 8.9.0.0.78)
[ 1964.907584] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready

mesh0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# ./mesh_join.sh wl8mesh 2462
netid=0
=========================
OK
OK
OK
OK
OK
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# Using interface mesh0 with hwaddr 54:4a:16:38:37:94 and ssid ""[ 1976.410484] wlcore: down

mesh0: interface state UNINITIALIZED->ENABLED
AP-ENABLED
[ 1976.950615] wlcore: version = 100860185
[ 1976.954604] wlcore: PHY firmware version: Rev 8.2.0.0.242

root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# [ 1977.216827] wlcore: firmware booted (Rev 8.9.0.0.78)

[ 1977.261881] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# mesh0: joining mesh wl8mesh
[ 1977.297235] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
mesh0: MESH-GROUP-STARTED ssid="wl8mesh" id=0

root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# ./ap_start.sh
adding wlan1 interface
Configuration file: /usr/share/wl18xx/hostapd.conf
[ 1982.972573] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Using interface wlan1 with hwaddr 56:4a:16:38:37:93 and ssid "wl8test"
[ 1983.169025] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
wlan1: interface state COUNTRY_UPDATE->ENABLED
wlan1: AP-ENABLED

root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx#
root@am335x-evm:/usr/share/wl18xx# ifconfig
eth0 Link encap:Ethernet HWaddr D0:5F:B8:7C:6F:73
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::d25f:b8ff:fe7c:6f73%131824/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3243 errors:0 dropped:2 overruns:0 frame:0
TX packets:3228 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:453027 (442.4 KiB) TX bytes:257642 (251.6 KiB)
Interrupt:173

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%131824/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:240 errors:0 dropped:0 overruns:0 frame:0
TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:19383 (18.9 KiB) TX bytes:19383 (18.9 KiB)

mesh0 Link encap:Ethernet HWaddr 54:4A:16:38:37:94
inet addr:10.20.30.41 Bcast:10.20.30.255 Mask:255.255.255.0
inet6 addr: fe80::564a:16ff:fe38:3794%131824/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:9433 (9.2 KiB)

usb0 Link encap:Ethernet HWaddr 5A:08:DB:82:D9:90
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan1 Link encap:Ethernet HWaddr 56:4A:16:38:37:93
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::544a:16ff:fe38:3793%131824/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:7268 (7.0 KiB)

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

Thanks for sharing that!

It looks like there's a difference in firmware versions. I have:

[ 137.399797] wlcore: PHY firmware version: Rev 8.2.0.0.240
[ 137.522093] wlcore: firmware booted (Rev 8.9.0.0.76)

Can you confirm your config files and software versions:

# /usr/sbin/hostapd -v
hostapd v2.6-devel-R8.7_SP3
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2016, Jouni Malinen <j@w1.fi> and contributors

# /usr/sbin/wpa_supplicant -v
wpa_supplicant v2.6-devel-R8.7_SP3+
Copyright (c) 2003-2016, Jouni Malinen <j@w1.fi> and contributors

My config files and ap_start.sh, etc, scripts are attached...

Can you please do the same?

Lastly, please confirm you are using BeagleBone Black with Stream Unlimited TIDC-WL1837MOD-AUDIO-MULTIROOM-CAPE

Thanks!

wl18xx-config-and-scripts.zip

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

I replied to the wrong comment. Please see my questions above:
e2e.ti.com/.../2482026

0 S over 8 years ago in reply to Matt Barclay9

TI__Mastermind 35795 points

- You may also update to latest wl8 firmware git.ti.com/.../wl18xx_fw
- I am using bbb + e14 cape

root@am335x-evm:/usr/share/wl18xx# wpa_supplicant -v
wpa_supplicant v2.6-devel-R8.7_SP3
Copyright (c) 2003-2016, Jouni Malinen <j@w1.fi> and contributors

root@am335x-evm:/usr/share/wl18xx# hostapd -v
hostapd v2.6-devel-R8.7_SP3
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2016, Jouni Malinen <j@w1.fi> and contributors

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

Upgraded my firmware, but no change. I've got e14 capes on order, so I can test them when they arrive.

Can you share your /usr/share/wl18xx/hostapd.conf and /usr/share/wl18xx/mesh_supplicant.conf ?

0 S over 8 years ago in reply to Matt Barclay9

TI__Mastermind 35795 points

I am using default config files that comes with sdk fs : software-dl.ti.com/.../index_FDS.html . I just changed the channel to 11 for testing .

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

I've got the e14 cape installed, but seeing the same behavior as the StreamUnlimited cape. I recompiled the kernel with the DTB patch from here:

processors.wiki.ti.com/.../Enable-TI-WiFi-Bluetooth-am335x-boneblack-WL1837.zip

Can you send me your file system, kernel, and dtb? I'd like to pick them apart to see how it differs from mine.

Thanks,
Matt

0 S over 8 years ago in reply to Matt Barclay9

TI__Mastermind 35795 points

Matt,

You can try default fs that comes with Sitara SDK :

In my case I updated libnl and hostapd/wpa_supplicant using build utils : config

I have attached my kernel config

Saurabh

0 Matt Barclay9 over 8 years ago in reply to S

Intellectual 795 points

OK, I finally got it!!

Looks like it was your Kernel config that ultimately did the trick. Here is the complete set of commands necessary to Mesh+AP working:

./ti-processor-sdk-linux-am335x-evm-04.02.00.09-Linux-x86-Install.bin --prefix $(pwd)/ti-processor-sdk-linux-am335x-evm-04.02.00.09

cd ti-processor-sdk-linux-am335x-evm-04.02.00.09/board-support/linux-4.9.59+gitAUTOINC+a75d8e9305-ga75d8e9305/

patch -p1 < ../../../Enable-TI-WiFi-Bluetooth-am335x-boneblack-WL1837.patch

patch -p1 < ../../../v6-wlcore-add-missing-nvs-file-name-info-for-wilink8.patch

# Kernel config from @Saurabh
cp /tmp/config arch/arm/configs/tisdk_am335x-evm_defconfig

cd ../../

make linux

cd bin

sudo ./create-sdcard.sh
(2 paritions)
(Use pre-built image from SDK)

# Eject then re-insert card so the partitions get mounted again...

cd ../board-support/linux-4.9.59+gitAUTOINC+a75d8e9305-ga75d8e9305/

sudo cp arch/arm/boot/zImage /media/mbarclay/rootfs/boot/zImage

sudo cp arch/arm/boot/dts/am335x-boneblack.dtb /media/mbarclay/rootfs/boot/am335x-boneblack.dtb

sudo make ARCH=arm INSTALL_MOD_PATH=/media/mbarclay/rootfs modules_install

cd ../../../

# Back at home directory
mkdir -p wl8-build/fs
cd wl8-build
git clone git://git.ti.com/wilink8-wlan/build-utilites.git
cd build-utilities
cp setup-env.sample setup-env
nano setup-env
# Change TOOLCHAIN_PATH, ROOTFS, KERNEL_PATH

./build_wl18xx.sh init

# Otherwise I get errors like @INC can't find strict.pm
export PERL5LIB=/usr/lib/x86_64-linux-gnu/perl-base:/usr/share/perl:/usr/lib/x86_64-linux-gnu/perl

./build_wl18xx.sh openssl
./build_wl18xx.sh libnl
./build_wl18xx.sh hostapd
./build_wl18xx.sh wpa_supplicant
./build_wl18xx.sh scripts

cd ../fs

tar -c . | sudo tar -xv -C /media/mbarclay/rootfs

umount /dev/mmcblk0*

Thank you!!

0 S over 8 years ago in reply to Matt Barclay9

TI__Mastermind 35795 points

Matt,
Good to know you have it working now. Thank you for listing the steps.
Best of luck !

Saurabh

Wi-Fi

Wi-Fi forum

Linux/WL1837MOD: Mesh + Access Point errors