Done:
here is the Bela/BoneBlackWireless dtb.
if you flash the image linked above, you can then put this file on the board on the BELABOOT partition and edit the uEnv.txt file in there to tell it to use this file rather than the default Bela one.

#dtb=am335x-bone-bela.dtb
dtb=am335x-boneblack-wireless.dtb

Then you could download this package (drivers for the WiFi module) and install it with

dpkg -i firmware-ti-connectivity_20161130-3_all.deb

OR you could just wait till tomorrow, as I am rebuilding the image now (with all the above changes) and will upload it on github tomorrow.

7 days later

Hi Guilio, thanks for this new image! I'm having troubles getting it to work though. I'm not sure if its a problem with the particular BBBW board i'm using. Basically the USB interface usb0 seems to be down; it isn't showing up on my laptop (which can see the normal BBB + bela version fine).

Using the UART serial headers (without the Bela cape) to debug, I can logon to the board, and run "ip a" which gives me this output
...
2: usb0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 6a:5a:59:be:a3:0a brd ff:ff:ff:ff:ff:ff
inet 192.168.7.2/24 brd 192.168.7.255 scope global usb0
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether de:ad:be:ef:00:00 brd ff:ff:ff:ff:ff:ff
...
I presume the DOWN means inactive?

With the default BeagleBone Debian 8.0 image the Wifi is working: the BBBW acts as an Access Point which I can connect to, and navigate to 192.168.8.1 for the default BeagleBone start page. But with the image you posted the the wlan0 does not seem to be active (and is not broadcasting an SSID). I assume that you have set it up as a client (rather than an access point), and I tried uncommenting the wlan0 example in /etc/network/interfaces but that resulted in receiving a lot of "unexpected IRQ trap at vector 38" errors (I tried both dhcp and static IP addresses, using an address on the local WIFI network).

I'm not sure if part of the issue is because I don't have the Bela cape plugged in. That is mainly because the only way I am able to get debug output is from the UART serial header, which gets in the way of plugging the Bela cape on. Does the Bela expose these pins somwhere? Or, if I make a special attachment that can fit onto the UART pins without getting in the way of the Bela cape, will that work? or is the cape using those pins for something else?

    dr-offig . Basically the USB interface usb0 seems to be down; it isn't showing up on my laptop (which can see the normal BBB + bela version fine).

    What operating system are you on? We expected problems with Windows, though the few machines we tested on worked fine. If that is on MacOS, then I guess it helps to do sudo kextunload /Library/Extensions/HoRNDIS.kext/; sudo kextload /Library/Extensions/HoRNDIS.kext/.
    Perhaps @LiamDonovan has some more thoughts on this.

    dr-offig I'm not sure if part of the issue is because I don't have the Bela cape plugged in.

    That should have no effect on the connection.

    dr-offig But with the image you posted the the wlan0 does not seem to be active (and is not broadcasting an SSID)

    This is expected: I did not put any effort in turning that into an access point, I only made sure that the interface works. Not sure how they do it in the original image, perhaps you can find out and reuse the method on this one.

          a month later

          Hi Julio,

          I have a problem with booting when the Bela cape is attached to my BBBW.

          I have flashed the image to the uSD card and edited the uEnv.txt to

          #dtb=am335x-bone-bela.dtb
          dtb=am335x-boneblack-wireless.dtb

          When I boot from the only power led blinks.

          When I detach Bela from BBBW, the boot is successful. I can load the IDE, but the driver doesn't load.

          btw, not sure if it is relevant but tried with both previous version of the Debian image (the one that came installed in eMMC) and the current (Debian 8.7 2017-03-19 4GB SD LXQT) which I’ve just flashed.

          I don't think this relates to issue #44 as it is a new board.

          Any suggestion on how to probe this problem?

          Best,
          F

            Hola cisco,
            do you know what version you had on the eMMC? Mine has
            BeagleBoard.org Debian Image 2016-11-06
            Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Linux

            I am wondering if anything changed in the bootloader on the eMMC.

            franciscobernardo When I boot from the only power led blinks.

            you are missing a (crucial) word here.

            franciscobernardo When I detach Bela from BBBW, the boot is successful. I can load the IDE, but the driver doesn't load.

            this is also funny.

            Can you try reverting the changes in uEnv.txt to:

            dtb=am335x-bone-bela.dtb
#dtb=am335x-boneblack-wireless.dtb

            and see if that boots with the cape attached?

                Thanks Giulio,

                I had the same version of yours.

                I think with Bela attached, boot simply doesn't happen. The PWR led blinks every second or so but the others don't lit or blink as normal

                I tried reverting the changes in uEnv.txt and the symptoms are the same.

                Just to check, is the Bela cape plugged in the right way around?
                The U-shaped slot on the cape should be on the side of the 5V barrel connector, while the Bela audio connectors should sit on top of the SD card.
                This is pretty obvious on the Beaglebone Black, where the ethernet connector prevents you from inserting the cape the wrong way around, but I see how it could be not straightforward on the BBBW.
                This is what it should look like (just a bit less blurred in real life):

                alt text

                @LiamDonovan may have some more ideas as to what is happening during boot/non-boot.

                Yep, everything correct.

                Is there any way of loading the Bela driver after the boot?

                if it's the PWR led flashing, then probably boot is not happening at all. It may be that the board is shutting down for whatever reason. Perhaps a defective Bela cape which is drawing too much current? Or perhaps your power supply is not providing enough? Or a defective cable? Are you powering this off your MacBook like the other day?
                Do you still have your BeagleBone Green Wireless? Perhaps see if that boots with the cape attached (boot from the eMMC, it does not really matters what operating system it loads, as long as it loads one)?

                Also, did you try booting with the cape attached but without the SD card?

                We left a Bela at Goldsmiths after the Anvil Hack if you want to try if that cape works. Not sure who has it but it should be around, Kevin will know. Otherwise, you could come over to QM and I can look into that.

                  giuliomoro Perhaps a defective Bela cape which is drawing too much current? Or perhaps your power supply is not providing enough? Or a defective cable? Are you powering this off your MacBook like the other day?

                  I have to admit that I've never experienced my Bela running... I have been dealing only with Wireless BBs as you know, and I'm afraid I can't get a BBB to try it out.

                  I'm powering it from my MBP usb port and I've tried out 3 different cables for that. My BBGW is Porto so I can't use it.

                  giuliomoro Perhaps see if that boots with the cape attached (boot from the eMMC, it does not really matters what operating system it loads, as long as it loads one)?

                  Also, did you try booting with the cape attached but without the SD card?

                  That doesn't work either.

                  Tomorrow I'm flying back to Porto in the afternoon, but if you're available in morning at QMUL that would be great, I can come by.

                  Let me know,

                  Thanks!

                      Virtual follow-up after in-person meeting: Francisco's BBBW seems to have some troubles with the PMIC (e.g.: "PWR" would flash tens of times before managing to boot when powered from the barrel connector), so I suggested he gets a replacement.

                      9 months later

                      hi,

                      i would really need wifi for my project, what is the most recommended way to get wifi on bela ? usb dongle or bbbw ?

                      I think the USB dongle solution would turn out to be cheaper. Also I am not really going to recommend the BBBW because I have heard from a couple of people that they were sometimes having problems booting it with the Bela cape attached, as if the power IC could not provide enough inrush current. It seems to be a problem with the bbbw, but I have not had a chance to test it myself. In the discussion above it turned out it was a defective bbbw that eventually got replaced by the manufacturer.

                      I would say: if you don't need the USB port for other uses, go for a USB wifi dongle that is supported by Linux 4.4.

                      If you get a BeagleBone Black wifi, check that it works fine with the Bela cape as soon as you receive it, so that you can ask for a replacement if it does not work as expected.

                      7 days later

                      Hi....in my case the BBBW acts as an Access Point which I can connect to, and navigate to some IP for the default BeagleBone start page. But with the image you posted the the wlan0 does not seem to be active. I assume that you have set it up as a client.

                      turnkey pcb assembly

                      yes, that's correct. There is no access point functionality enabled by default.
                      Someone gave me some instructions on how to do that, here are the details (but I have not tested them myself):

                      For this first part you need internet access on the board *:
                      NOTE: this is not needed for images >= v0.3.3

                      apt-get upgrade
apt-get update
apt-get install hostapd
# - press Y when prompted. This will install the service which will turn Bela into a WiFi access point.
nano /etc/default/hostapd # open text editor

                      Then the actual configuration (for all images).

                      Find the line that starts with DAEMON_CONF in /etc/default/hostapd, uncomment it and change it so it looks like this:

                      DAEMON_CONF="/etc/hostapd/hostapd.conf"

                      Now we've told hostapd to look for a configuration file, so we need to create it:

                      nano /etc/hostapd/hostapd.conf

                      Put the following into this file:

                      interface=wlan0
hw_mode=g
channel=1
wmm_enabled=1
ssid=MyBelaAccessPoint
auth_algs=1
wpa=2
wpa_passphrase=wifipassword
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP
ieee80211d=1
country_code=DK
ieee80211n=1

                      Remember to change the ssid= and wpa_passphrase= lines.

                      nano /etc/network/interfaces

                      Now we need to change the network configuration so that Bela advertises its network instead of trying to connect to one (the internet connection that was initially set up). To do that, replace the wlan0 configuration with the following:

                      allow-hotplug wlan0
iface wlan0 inet static
    hostapd /etc/hostapd/hostapd.conf
    address 192.168.30.1
    netmask 255.255.255.0

                      Now, restart Bela by typing shutdown -r now. Once Bela reboots, you should be able to see a network called MyBelaAccessPoint. You would need static IP configuration (usually IP addresses from 192.168.30.2 to 192.168.30.254) and a subnet mask of 255.255.255.0 on each connecting client. Ideally, a DHCP server using dnsmasq would be needed so that you don't worry about IP configuration, but I haven't tried that yet.

                      Once you have connected and set up the client device's IP configuration, you are able to access Bela IDE in the browser at 192.168.30.1, as well as connect to it via SSH.

                      * if you don't have internet access on the board, you can download the package on your computer from [here](
                      http://httpredir.debian.org/debian/pool/main/w/wpa/hostapd_2.4-1+deb9u1_armhf.deb), scp it over and install it with dpkg -i hostapd_2.4-1+deb9u1_armhf.deb)

                      11 days later

                      In case anyone else is trying to do this: I got the Bela+BeagleboneBlack with Edimax Wifi USB dongle working as an access point using the instructions above. Also got DHCP working using the existing isc-dhcp-server (the one that serves up 192.168.7.1 over USB via RNDIS).

                      I've been using node.js web apps (listening on ports other than 80) on the Bela as GUIs for projects. This makes it easier to configure a Bela buried inside an installation or instrument. Having DHCP is handy since it is easier for other people to logon with their smart phone for example (without so much faffing about).

                      To get DHCP working I needed to edit two other files:
                      (1) /etc/default/isc-dhcp-server changed line from
                      INTERFACESv4="usb0"
                      to
                      INTERFACESv4="usb0 wlan0"

                      (2) /etc/dhcp/dhcpd.conf added in extra lines
                      subnet 192.168.30.0 netmask 255.255.255.0 {
                      range 192.168.30.2 192.168.30.254;
                      }
                      and commented out these lines
                      #option domain-name "example.org";
                      #option domain-name-servers ns1.example.org, ns2.example.org;

                      The Bela is not connected to the internet (i.e. i'm not trying to use it as an internet access point) so these DNS entries were freaking my mac laptop out and stuffing up the connection. Now when I connect over my macbook airport to the Bela Access Point the wifi icon looks like it is trying to connect (since it can't find internet) but is actually connected (can ssh onto bela over it)

                      a month later

                      I've finally solved my BeagleBone Black Wireless problems, have it working with Bela and acting as a WiFi access point.

                      I was having the same problems as @franciscobernardo with the Power light just feebly flashing. It would boot fine from SD card (holding down the boot button - but that's a problem because you have to take the Bela cape off to get to that button).

                      The issue turned out to be related to the bela_flash_emmc.sh script. I had changed uEnv.txt on the SD card boot partition, commenting out dtb=am335x-bone-bela.dtb, and uncommenting dtb=am335x-bone-bela-black-wireless.dtb. BUT, the bela_flash_emmc script reads from a file called uEnv-emmc.txt in the same folder as the script, which I HADN'T updated, which has the old dtb=am335x-bone-bela.dtb. So it couldn't boot from emmc boot partition because it was using the wrong dtb file.