Unable to get WiFi working on BBBW using the latest Debian image

[Hamza Khan]

Hey All,

I'm a newb on Linux and having issues getting WiFi to work using the latest Debain image Debian 9.1 2017-08-31 4GB SD LXQT (Stretch). When I try to see the the network interfaces using ifconfig I get only the following 4 and no wlan- 

eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC>  mtu 1500

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

usb1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

I don't know if this will help but the eprom from my version.sh file is -  

eprom:[A335BNLTBBWG0491

Any thoughts on how to fix this or should I start all over again with a new image flash? Any tips/resources on Bluetooth communication on BBBW will also be appreciated. 

[Robert Nelson]

On Thu, Oct 5, 2017 at 7:12 AM, Hamza Khan <hamz...@gmail.com> wrote:
>
> Hey All,
>
> I'm a newb on Linux and having issues getting WiFi to work using the latest
> Debain image Debian 9.1 2017-08-31 4GB SD LXQT (Stretch). When I try to see
> the the network interfaces using ifconfig I get only the following 4 and no
> wlan-
>
> eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500
>
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
>
> usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>
> usb1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
>
> I don't know if this will help but the eprom from my version.sh file is -
>
> eprom:[A335BNLTBBWG0491

another case of mis-programed:

GND TP1 then run as root:

dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom

reboot and everything will be okay..

Regards,

--
Robert Nelson
https://rcn-ee.com/

[George McFie]

Hi Robert,

I have a BBB wireless that also seems to have the same problem as Hamze. 

How do I confirm whether or not I also have a faulty eprom version?

Here are some details relating to my installation ...

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

Version of installed OS:

bone-debian-9.2-iot-armhf-2017-10-10-4gb.img.xz

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

debian@beaglebone:~$ hostnamectl

   Static hostname: beaglebone

         Icon name: computer

        Machine ID: 8c4801f3fa70a9c50b1eee4559dcb80d

           Boot ID: bb021b895e264ea6977fe8585c35f1e4

  Operating System: Debian GNU/Linux 9 (stretch)

            Kernel: Linux 4.4.91-ti-r133

      Architecture: arm

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

debian@beaglebone:~$ cat /etc/issue

Debian GNU/Linux 9 \n \l

BeagleBoard.org Debian Image 2017-10-10

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:*******]

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

debian@beaglebone:~$ connmanctl technologies

/net/connman/technology/ethernet

  Name = Wired

  Type = ethernet

  Powered = True

  Connected = False

  Tethering = False

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

debian@beaglebone:~$ ifconfig

eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC>  mtu 1500

        ether 50:65:83:d0:8d:d0  txqueuelen 1000  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 181

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 1  (Local Loopback)

        RX packets 12001  bytes 806316 (787.4 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 12001  bytes 806316 (787.4 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3

        inet6 fe80::5265:83ff:fed0:8dd2  prefixlen 64  scopeid 0x20<link>

        ether 50:65:83:d0:8d:d2  txqueuelen 1000  (Ethernet)

        RX packets 1163  bytes 130029 (126.9 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 658  bytes 153722 (150.1 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3

        inet6 fe80::5265:83ff:fed0:8dd5  prefixlen 64  scopeid 0x20<link>

        ether 50:65:83:d0:8d:d5  txqueuelen 1000  (Ethernet)

        RX packets 859  bytes 103072 (100.6 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 491  bytes 119224 (116.4 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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

debian@beaglebone:~$  lsusb -v

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Couldn't open device, some information will be missing

Device Descriptor:

  bLength                18

  bDescriptorType         1

  bcdUSB               2.00

  bDeviceClass            9 Hub

  bDeviceSubClass         0 Unused

  bDeviceProtocol         1 Single TT

  bMaxPacketSize0        64

  idVendor           0x1d6b Linux Foundation

  idProduct          0x0002 2.0 root hub

  bcdDevice            4.04

  iManufacturer           3

  iProduct                2

  iSerial                 1

  bNumConfigurations      1

  Configuration Descriptor:

    bLength                 9

    bDescriptorType         2

    wTotalLength           25

    bNumInterfaces          1

    bConfigurationValue     1

    iConfiguration          0

    bmAttributes         0xe0

      Self Powered

      Remote Wakeup

    MaxPower                0mA

    Interface Descriptor:

      bLength                 9

      bDescriptorType         4

      bInterfaceNumber        0

      bAlternateSetting       0

      bNumEndpoints           1

      bInterfaceClass         9 Hub

      bInterfaceSubClass      0 Unused

      bInterfaceProtocol      0 Full speed (or root) hub

      iInterface              0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x81  EP 1 IN

        bmAttributes            3

          Transfer Type            Interrupt

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0004  1x 4 bytes

        bInterval              12

debian@beaglebone:~$

Regards

George

[Robert Nelson]

On Sun, Nov 5, 2017 at 5:58 AM, George McFie <gsm...@gmail.com> wrote:
> Hi Robert,
>
> I have a BBB wireless that also seems to have the same problem as Hamze.
> How do I confirm whether or not I also have a faulty eprom version?
> Here are some details relating to my installation ...

sudo /opt/scripts/tools/version.sh

[res...@tenxertech.com]

Hi All,
Same problem here. Which is TP1. I could not find it on the header information .

[Robert Nelson]

On Sun, Nov 12, 2017 at 11:02 PM, <res...@tenxertech.com> wrote:
> Hi All,
> Same problem here. Which is TP1. I could not find it on the header
> information .

Look at the pcb, it's on the silkscreen..

[Reshmi Chandran]

Still no luck .

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for debian:
git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
eeprom:[A335BNLT00C05315BBBK1677]
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-rc2-00002-g7c9353]
kernel:[4.9.45-ti-r57]
nodejs:[v6.11.2]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

debian@beaglebone:~$ iwconfig
eth0      no wireless extensions.

usb0      no wireless extensions.

usb1      no wireless extensions.

lo        no wireless extensions.

can0      no wireless extensions.

can1      no wireless extensions.

I downloaded the Debain image Debian 9.1 2017-08-31 4GB SD LXQT (Stretch)
debian@beaglebone:~$ connmanctl
connmanctl> tether wifi off
Error disabling wifi tethering: Method "SetProperty" with signature "sv" on interface "net.connman.Technology" doesn't exist

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

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

connmanctl> agent on
Agent registered
connmanctl> services

connmanctl> quit

[Robert Nelson]

On Wed, Nov 15, 2017 at 12:56 AM, Reshmi Chandran <res...@tenxertech.com> wrote:
> Still no luck .
>
> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
>
> We trust you have received the usual lecture from the local System
> Administrator. It usually boils down to these three things:
>
> #1) Respect the privacy of others.
> #2) Think before you type.
> #3) With great power comes great responsibility.
>
> [sudo] password for debian:
> git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
> eeprom:[A335BNLT00C05315BBBK1677]

What do you mean? "you" ^^^ have a BeagleBone Black, NOT the
BeagleBone Black Wireless

The "BeagleBone Black Wireless" is a new model:

[luc...@lucienbrule.com]

Chiming in, this combined with updating to the latest provided release of debian stretch fixed the wireless issues.

> GND TP1 then run as root: 

```
dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 

```

My /opt/scripts/tools/version.sh after applying the fix for posterity:

git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]

eeprom:[A335BNLTBWA50000BBWG*]

dogtag:[BeagleBoard.org Debian Image 2017-08-31]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-rc2-00002-g7c9353]

kernel:[4.9.45-ti-r57]

nodejs:[v6.11.2]

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]

uboot_overlay_options:[enable_uboot_cape_universal=1]

pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]

pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]

pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

Thank you!

[William]

Hello, this is what I have done, no result for now:

1. Flashed BBBW with last image Debian 9.2 2017-10-10 4GB SD IoT 

2. Grounded TP1 

3.

dd if=/opt/scripts/device/bone/bbbw-eeprom.dump

4. 

of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom

5.

root@beaglebone:~# sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[d36fe9a7be9ebfc872b10a470e904ab4c61c4516]
eeprom:[A335BNLTBWA51712EW005259]
dogtag:[BeagleBoard.org Debian Image 2017-10-10]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-00002-g0f3f1c7907]
kernel:[4.4.91-ti-r133]
nodejs:[v6.11.4]
device-tree-override:[dtb=am335x-boneblack-emmc-overlay.dtb]
pkg:[bb-cape-overlays]:[4.4.20171013.2-0rcnee1~stretch+20171013]

pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

6. Reboot

After reboot:

root@beaglebone:~# cat /proc/device-tree/model
TI AM335x BeagleBone Black

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

eth0      no wireless extensions.


usb0      no wireless extensions.


usb1      no wireless extensions.

can0      no wireless extensions.

It seems that no wireless interface is detected. Am I missing something?

[Reshmi Chandran]

are you using beagle bone black or beagle bone black wireless .wireless works only on beaglebone wireless

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/a1V_8dLoGXs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f3f7b1ce-9ed1-4789-96b3-32b463da71ee%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[William]

I am using a BB wireless from element14. 

[Robert Nelson]

On Mon, Nov 20, 2017 at 4:32 AM, William <pana...@gmail.com> wrote:
> Hello, this is what I have done, no result for now:
> 1. Flashed BBBW with last image Debian 9.2 2017-10-10 4GB SD IoT
>
> 2. Grounded TP1
>
> 3.
> dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
>
> 4.
> of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom
>
> 5.
> root@beaglebone:~# sudo /opt/scripts/tools/version.sh
> git:/opt/scripts/:[d36fe9a7be9ebfc872b10a470e904ab4c61c4516]
> eeprom:[A335BNLTBWA51712EW005259]
> dogtag:[BeagleBoard.org Debian Image 2017-10-10]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2017.09-00002-g0f3f1c7907]
> kernel:[4.4.91-ti-r133]
> nodejs:[v6.11.4]
> device-tree-override:[dtb=am335x-boneblack-emmc-overlay.dtb]

^^^ so you just forced it to be a BeagleBone Black here...

YOU need to use:

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

This will give you what you want:

enable_uboot_overlays=1
disable_uboot_overlay_video=1

[William]

Added

enable_uboot_overlays=1 
disable_uboot_overlay_video=1 

to /boot/uEnv.txt

Now it does not boot, leds for BT, WL and USR0 stay on.

beaglebone login: [   64.841141] Error: Driver 'ecap' is already registered, aborting...

[   65.139009] Error: Driver 'ecap' is already registered, aborting...

This is last messages on debug pins.

[Robert Nelson]

"login" yes 'clearly' it did not boot.. end sarcasm..

What's your real issue, as it did boot.

Regards,

[William]

Ok, my mistake, I 'appreciate' your sarcasm, but still cannot see any wifi interface.

How can I find the real issue since I cannot ssh connect to BB?

I only have debug messages and a stuck BB.

[Robert Nelson]

On Tue, Nov 21, 2017 at 6:15 AM, William <pana...@gmail.com> wrote:
> Ok, my mistake, I 'appreciate' your sarcasm, but still cannot see any wifi
> interface.
> How can I find the real issue since I cannot ssh connect to BB?
> I only have debug messages and a stuck BB.

Okay, now with your /boot/uEnv.txt changes, let's see version.sh again:

sudo /opt/scripts/tools/version.sh

[William]

BB is completely freeze with those leds on.

Tried to re-flash, same issue.

I am not able to run any script.

[Robert Nelson]

How are you powering it?

Use a 5volt DC barrel connector.

Grab this image:

https://rcn-ee.net/rootfs/bb.org/testing/2017-11-19/stretch-iot/BBBL-blank-debian-9.2-iot-armhf-2017-11-19-4gb.img.xz

use etcher.io

it'll flash the eMMC..

[William]

I always use a 5V power supply.

Got the image, flashed SD with Etcher, flashed the BBBW.

Same result as before: it runs until "beaglebone login:", then freezes.

bbbw.jpg

bbbw_debug_messages - Pass: 1234

It can be a problem with my board? I have only one to test.

Thank you for your support.

[Dennis Lee Bieber]

On Wed, 22 Nov 2017 02:38:40 -0800 (PST), William
<pana...@gmail.com> declaimed the following:

>I always use a 5V power supply.
>Got the image, flashed SD with Etcher, flashed the BBBW.
>

>Same result as before: it runs until "*beaglebone login:", *then freezes.
>bbbw.jpg
><https://lh3.googleusercontent.com/-VqQoGSiS58M/WhVTCynW_dI/AAAAAAAAD0E/j34cRxqZ3AAhjwv7djCG76JnXvYy91QXQCLcBGAs/s1600/bbbw.jpg>
>

Probably too late now, but I have to wonder why you are starting the
procedure with a flasher-image.

I'd consider it safer (presuming one has a working eMMC already) to use
a "run on SD card" image for testing. That way, if it hangs, one can remove
the SD card and reboot to the working image.

Only after getting the SD card image to run properly would I convert it
to a flasher.
--
Wulfraed Dennis Lee Bieber AF6VN
wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/

[Robert Nelson]

Well, you only have the "TX" and "GND" pin connected on the debug usart..

Hook up the "RX" and then you can login...

[William]

I have only a 5V TTL serial cable, used only for receiving debug messages on PC (I don't want to burn something connecting the TX and V since voltage is different).

For a normal SSH connection I use the mini USB cable and here is the problem. 

Since now I used with no problem BBB rev C and BBB industrial. 

Also this BBBW worked properly when recognized as BBB. (with #enable_uboot_overlays=1 disabled from /boot/uEnv.txt)

[Kakarla Srinivas]

Hi ,

I was also facing same issue. I tried with different images( 8iot and LXQT.6,8.7,9.1,9.2,9.3) debian LXQT 8.6 able to detect the wlna0 some times ,But unable to configure the wifi using connmanctl commands

Last login: Sun Nov  6 15:29:31 UTC 2016 on ttyGS0
Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l
                                                                               
The programs included with the Debian GNU/Linux system are free software;      
the exact distribution terms for each program are described in the             
individual files in /usr/share/doc/*/copyright.                                

ifconfig
wlan0     Link encap:Ethernet  HWaddr 50:65:83:e1:e5:ff                        
          inet6 addr: fe80::5265:83ff:fee1:e5ff/64 Scope:Link                  
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1           
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0                   
          TX packets:52 errors:0 dropped:0 overruns:0 carrier:0                
          collisions:0 txqueuelen:1000                                         
          RX bytes:0 (0.0 B)  TX bytes:13486 (13.1 KiB) 

debian@beaglebone:~$ sudo connmanctl                                           
connmanctl> enable wifi                                                        
Error wifi: Already enabled                

connmanctl> scan wifi   // not working                                                       
connmanctl> scan wifi    // not working                                                      
connmanctl> scan wifi   // not working                                                        
connmanctl> scan wifi   // not working

Here the image details
uname -a                                                  
Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Lix
debian@beaglebone:~$ cat /etc/dogtag                                           
BeagleBoard.org Debian Image 2016-11-06                                    
connmanctl> scan wifi                                                          
connmanctl>


interface configuration ( /et/networ/interface)

iface wlan0 inet dhcp
auto wlan0
        wpa-ssid "xxxx"
        wpa-psk "xxxxxx"

connmanctl
connmanctl> tether wifi disable
connmanctl> enable wifi
connmanctl> scan wifi
connmanctl> services
connmanctl> agent on
connmanctl> connect wifi_*_managed_psk
connmanctl> quit

Please let me know any one have solutions. This little bit urgent. I am working on this issue from 10 days .I didn't find any solution.

Thank you,

Regards,
Srinivas




                                                                               
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent              
permitted by applicable law.  

On Thursday, October 5, 2017 at 5:42:00 PM UTC+5:30, Hamza Khan wrote:

Hey All,

I'm a newb on Linux and having issues getting WiFi to work using the latest Debain image Debian 9.1 2017-08-31 4GB SD LXQT (Stretch). When I try to see the the network interfaces using ifconfig I get only the following 4 and no wlan- 

eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC>  mtu 1500

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

usb1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

I don't know if this will help but the eprom from my version.sh file is -  

eprom:[A335BNLTBBWG0491

Any thoughts on how to fix this or should I start all over again with a new image flash? Any tips/resources on Bluetooth communication on BBBW will also be appreciated.