BBBWL ifconfig...something missing?

Hello –

New post as @yahoo spam cluttered up previous.

Per RC Nelson suggestion of booting from different image obtainable at http://beagleboard.org/latest-images, I made three attempts at resolving lack of wifi on a new BBBWL.

Three images used in these tests:

  1. Debian 8.6 2016-11-06 4GB SD LXQT
    https://debian.beagleboard.org/images/bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz

  2. Debian 8.6 2016-12-09 4GB SD IoT
    https://debian.beagleboard.org/images/bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz
    NOTE: This image drops my shell connxn after a couple minutes.

  3. BBBW-blank-debian-8.6-lxqt-4gb-armhf-2016-12-05-4gb.img.xz, alluded to by RC Nelson in response to post “Setup Wifi on Beaglebone Black Wireless” this sub-forum.

Below terminal output is consistent across all three images listed above: If anyone has an idea what I am doing incorrectly, assistance will be very much appreciated.
Thank you,
Mark

root@beaglebone:~# ifconfig
eth0 Link encap:Ethernet HWaddr 50:65:83:d6:06:a5
UP BROADCAST MULTICAST DYNAMIC 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)
Interrupt:173

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

usb0 Link encap:Ethernet HWaddr 50:65:83:d6:06:a7
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::5265:83ff:fed6:6a7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:662 errors:0 dropped:0 overruns:0 frame:0
TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:179124 (174.9 KiB) TX bytes:30188 (29.4 KiB)

root@beaglebone:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

usb0 no wireless extensions.

can0 no wireless extensions.

can1 no wireless extensions.

root@beaglebone:~# connmanctl

technologies
/net/connman/technology/ethernet
Name = Wired
Type = ethernet
Powered = True
Connected = False
Tethering = False
tether wifi disable
Error disabling wifi tethering: Method “SetProperty” with signature “sv” on interface “net.connman.Technology” doesn’t exist

enable wifi
Error wifi: Method “SetProperty” with signature “sv” on interface “net.connman.Technology” doesn’t exist

scan wifi
Error /net/connman/technology/wifi: Method “Scan” with signature “” on interface “net.connman.Technology” doesn’t exist

services

quit
root@beaglebone:~#

Hi Mark,

Hello --

New post as @yahoo spam cluttered up previous.

Per RC Nelson suggestion of booting from different image obtainable at
http://beagleboard.org/latest-images, I made three attempts at resolving
lack of wifi on a new BBBWL.

Three images used in these tests:
1. Debian 8.6 2016-11-06 4GB SD LXQT
https://debian.beagleboard.org/images/bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz

2. Debian 8.6 2016-12-09 4GB SD IoT
https://debian.beagleboard.org/images/bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz
NOTE: This image drops my shell connxn after a couple minutes.

3. BBBW-blank-debian-8.6-lxqt-4gb-armhf-2016-12-05-4gb.img.xz, alluded to by
RC Nelson in response to post "Setup Wifi on Beaglebone Black Wireless" this
sub-forum.

Below terminal output is consistent across all three images listed above: If
anyone has an idea what I am doing incorrectly, assistance will be very much
appreciated.
Thank you,
Mark

root@beaglebone:~# ifconfig
eth0 Link encap:Ethernet HWaddr 50:65:83:d6:06:a5
          UP BROADCAST MULTICAST DYNAMIC 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)
          Interrupt:173

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

usb0 Link encap:Ethernet HWaddr 50:65:83:d6:06:a7
          inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
          inet6 addr: fe80::5265:83ff:fed6:6a7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:662 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:179124 (174.9 KiB) TX bytes:30188 (29.4 KiB)
root@beaglebone:~# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

usb0 no wireless extensions.

can0 no wireless extensions.

can1 no wireless extensions.

root@beaglebone:~# connmanctl
> technologies
/net/connman/technology/ethernet
  Name = Wired
  Type = ethernet
  Powered = True
  Connected = False
  Tethering = False
> tether wifi disable
Error disabling wifi tethering: Method "SetProperty" with signature "sv" on
interface "net.connman.Technology" doesn't exist

> enable wifi
Error wifi: Method "SetProperty" with signature "sv" on interface
"net.connman.Technology" doesn't exist

> scan wifi
Error /net/connman/technology/wifi: Method "Scan" with signature "" on
interface "net.connman.Technology" doesn't exist

> services

> quit
root@beaglebone:~#

can you test:

https://rcn-ee.net/rootfs/bb.org/testing/2016-12-12/iot/

made a few more changes to usb0 and wlan0, i'm still chasing down a
new wlcore issue i'm seeing on two of my boards.. (oddly on one, only
when using the microSD)

so, can you also share:

dmesg | grep wlcore

[ 48.035440] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[ 48.055657] genirq: Failed to request resources for wl18xx (irq 54)
on irqchip 44e07000.gpio
[ 48.170563] wlcore: ERROR interrupt configuration failed

Regards,

Hi Robert –

From the most recent 11-06-2016 image just returns…nothing

root@beaglebone:~# cat /etc/dogtag
BeagleBoard.org Debian Image 2016-11-06
root@beaglebone:~# dmesg | grep wlcore

root@beaglebone:~#

BTW, search of an earlier dmesg output (12-05img) showed no results on “wl*”, “wl18*” in the text file. See attached.

Will test your 12-12 IOT and respond back here.

12-05img_out.txt (26 KB)

Hi Robert –

Flashed your 12-12 image “BBB-blank-debian-8.6-iot-armhf-2016-12-12-4gb.img.xz”.

Recv following:

root@beaglebone:~# dmesg | grep wlcore
root@beaglebone:~#

And…

root@beaglebone:~# ifconfig -a
can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

-00
NOARP MTU:16 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:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:198

can1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

-00
NOARP MTU:16 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:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:199

eth0 Link encap:Ethernet HWaddr 50:65:83:d6:06:a5
UP BROADCAST MULTICAST DYNAMIC 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)
Interrupt:173

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

usb0 Link encap:Ethernet HWaddr 50:65:83:d6:06:a7
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::5265:83ff:fed6:6a7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1106 errors:0 dropped:0 overruns:0 frame:0
TX packets:163 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:294464 (287.5 KiB) TX bytes:37349 (36.4 KiB)

What do you think?
Mark

12-12img_out.txt (29.9 KB)

Uhoh!!

[ 2.351843] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,'

We have a miss-programmed eeprom!!

Mark, is this a pre-production BeagleBone Black Wireless?

(is the pcb green or black?)

First let's double check the wl1835 works, then i'll walk you thru
re-programing the eeprom..

in /boot/uEnv.txt

add:

dtb=am335x-boneblack-wireless.dtb

and reboot..

Regards,

Robert!

Much better. I get WL/BT leds fully lit, which I neglected to mention were previously unresponsive. But USR0 led is kind of in tachycardia. OK, heart rate is down now.

Added your line below line for 1835 which was commented out…

##BeagleBone Black: wl1835
#dtb=am335x-boneblack-wl1835mod.dtb

##Added per RCN
dtb=am335x-boneblack-wireless.dtb

On the reboot, am unable to shell in. So, will reflash your 12-12, swap the comment lines in uEnv.txt and reboot for a looksee.

Thank you for catching that line in the output I attached.
Mark

Hi Robert –

Follow up response from earlier.

Board in hand is a production model black received two days ago.

Attached file is result of further testing. In summary, per your suggestion in re add line to uEnv.txt, achieve some success. Ifconfig output is now populated with tether, wlan0, and in one instance softAP0. I can see the MAC address of the BBBWL in my router’s browser window. Connman is functional, without significant errors. Shell connxn is dropped after couple minutes, fairly consistently. Hexdump of eeprom at 0-0050 also included.

Thank you for your assistance,
Mark

RCNuENV.txt (5.07 KB)

Hi Robert –

So yes, success. Although I will still beg your advice on the eeprom problem. I have found that booting from SD card causes some problem with dropping my shell connxn, something not encountered if I just flash the onboard eMMC. I wonder if this is going to be a problem down the road when I want to boot off an 8 or 16 GB card.

root@beaglebone:~# dmesg | grep wlcore
[ 43.191825] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[ 43.272449] wlcore: loaded
[ 43.734400] wlcore: PHY firmware version: Rev 8.2.0.0.236
[ 43.783333] wlcore: firmware booted (Rev 8.9.0.0.69)
[ 48.563112] wlcore: Association completed.
root@beaglebone:~#

services wifi_my-hash_managed_psk
/net/connman/service/wifi_my-hash_managed_psk
Type = wifi
Security = [ psk, wps ]
State = online
Strength = 57
Favorite = True
Immutable = False
AutoConnect = True
Name = SBG6580A9
Ethernet = [ Method=auto, Interface=wlan0, Address=50:65:83:D6:06:A5, MTU=1500 ]
IPv4 = [ Method=manual, Address=192.168.0.133, Netmask=255.255.255.0, Gateway=192.168.0.1 ]
IPv4.Configuration = [ Method=manual, Address=192.168.0.133, Netmask=255.255.255.0,
Gateway=192.168.0.1 ]

IPv6 = [ ]
IPv6.Configuration = [ Method=auto, Privacy=disabled ]
Nameservers = [ 8.8.8.8, 8.8.4.4 ]
Nameservers.Configuration = [ 8.8.8.8, 8.8.4.4 ]
Timeservers = [ 192.168.0.1 ]
Timeservers.Configuration = [ ]
Domains = [ www.google.com ]
Domains.Configuration = [ www.google.com ]
Proxy = [ Method=direct ]
Proxy.Configuration = [ ]
Provider = [ ]

quit
root@beaglebone:~#
root@beaglebone:~# uname -a
Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Linux
root@beaglebone:~# cat /etc/dogtag
BeagleBoard.org Debian Image 2016-11-06

Hello,

I am having a problem with getting the USB Ethernet bridge working with the suggestion 12-05-2016 image. When I connect the BBBWL I get the windows partion to show up, which usually means the virutal ethernet port is loaded. Which it does load, but it doesn’t get a 192.168.7.1 address, instead it gets a 169.254.244.251 address. Usually a disconnect and reconnect will fix this problem, but no such luck. I am downloading some of the latest images to try, but I am curious if this is a known issue?

Please note, the driver seems to be working as a my Rev C board is connecting up correctly.

Cheers,

Gregg

Hello Gregg –

Sorry to hear you are having problems with your new board.

What do you get when you type 192.168.7.2 into your web browser? These boards prefer Chrome.

Are you booting from the SD card, or flashing the eMMC and booting from there?

Mark

Mark,

Thank you. However, I just found at solution. I was trying to SSH into the 192.168.7.2 address which wouldn’t work because the virutal adapter didn’t have an address on the same subnet. However, after reading some other threads I switched to the 12-12-2016 image and everything seems to be working perfectly now. the 12-05-2016 didn’t work after several tries.

I believe it’s probably just an issue with the configuration of that image. The factory image worked as well as the 12-12-2016 image.

To answer your question directly, I was flashing the eMMC and booting from eMMC. The boot seams to work, but I don’t have a serial connector with me to check any settings in the OS.

Thanks,

Gregg

Perhaps I spoke too soon, after rebooting, things seem to be failing again. There appears to be a problem with it providing the IP address to the interface:

Ethernet adapter Ethernet 5:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::399c:f19:9a23:f4fb%14
Autoconfiguration IPv4 Address. . : 169.254.244.251
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Is the USB bridge connection on windows. This is working off of the 12-12-2016 image. The only thing I did with the operating system was log into the connmanctl and connect to a wifi network which required me to turn off the tethering. However, I can SSH into it via the wifi connect that was made. Not sure if this is expected behavior, but I thought I would mention it.

Cheers,

Gregg

Hi Gregg,

Perhaps I spoke too soon, after rebooting, things seem to be failing again.
There appears to be a problem with it providing the IP address to the
interface:

Ethernet adapter Ethernet 5:

   Connection-specific DNS Suffix . :
   Link-local IPv6 Address . . . . . : fe80::399c:f19:9a23:f4fb%14
   Autoconfiguration IPv4 Address. . : 169.254.244.251
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

Is the USB bridge connection on windows. This is working off of the
12-12-2016 image. The only thing I did with the operating system was log
into the connmanctl and connect to a wifi network which required me to turn
off the tethering. However, I can SSH into it via the wifi connect that was
made. Not sure if this is expected behavior, but I thought I would mention
it.

The usb bridge should be working again after this change for the
12-12-2016 image

https://github.com/rcn-ee/repos/commit/ab56e3706b9bc3ce5cedd1fbb01818b9651aff56

the netmask we had setup for usb0 wasn't working with dnsmasq-dhcp

usb0 Link encap:Ethernet HWaddr 50:65:83:d0:e0:d6
          inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252

Dec 14 21:26:35 beaglebone systemd[1]: Started dnsmasq - A lightweight
DHCP and caching DNS server.
Dec 14 21:26:42 beaglebone dnsmasq-dhcp[2382]: DHCPDISCOVER(usb0)
192.168.7.1 50:65:83:d0:e0:d5
Dec 14 21:26:42 beaglebone dnsmasq-dhcp[2382]: DHCPOFFER(usb0)
192.168.7.1 50:65:83:d0:e0:d5
Dec 14 21:26:42 beaglebone dnsmasq-dhcp[2382]: DHCPREQUEST(usb0)
192.168.7.1 50:65:83:d0:e0:d5
Dec 14 21:26:42 beaglebone dnsmasq-dhcp[2382]: DHCPACK(usb0)
192.168.7.1 50:65:83:d0:e0:d5 hades
Dec 14 21:28:47 beaglebone dnsmasq-dhcp[2382]: DHCPDISCOVER(usb0)
50:65:83:d0:e0:d5
Dec 14 21:28:47 beaglebone dnsmasq-dhcp[2382]: DHCPOFFER(usb0)
192.168.7.1 50:65:83:d0:e0:d5
Dec 14 21:28:47 beaglebone dnsmasq-dhcp[2382]: DHCPREQUEST(usb0)
192.168.7.1 50:65:83:d0:e0:d5
Dec 14 21:28:47 beaglebone dnsmasq-dhcp[2382]: DHCPACK(usb0)
192.168.7.1 50:65:83:d0:e0:d5 hades
Dec 14 21:29:17 beaglebone dnsmasq-dhcp[2382]: DHCPDISCOVER(usb0)
50:65:83:d0:e0:d5
Dec 14 21:29:17 beaglebone dnsmasq-dhcp[2382]: DHCPOFFER(usb0)
192.168.7.1 50:65:83:d0:e0:d5
Dec 14 21:29:17 beaglebone dnsmasq-dhcp[2382]: DHCPREQUEST(usb0)
192.168.7.1 50:65:83:d0:e0:d5
Dec 14 21:29:17 beaglebone dnsmasq-dhcp[2382]: DHCPACK(usb0)
192.168.7.1 50:65:83:d0:e0:d5 hades

Regards,