BeagleBone AI-64 unable to connect to WiFi

General Discussion
,
#1

Hello Devs,

I am trying to connect wifi using this M.2 wifi module on BB AI-64. However, with no success.

Subject
Subject815×1047 1.11 MB

I am following steps from here.

wpa_suppliment-wlan0.conf file:

ctrl_interface=DIR=/run/wpa_supplicant GROUP=netdev
update_config=1
#country=US
p2p_disabled=1

network={
	ssid="abcdefgh"
	psk="abcd-alpha-Num3ic"
}

Command:

 sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf

The wpa_supplicant output:

debian@BeagleBone:~$ sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf 
Successfully initialized wpa_supplicant
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
^Cnl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: CTRL-EVENT-TERMINATING 
debian@BeagleBone:~$

Please help me to get through this.

Thank you

Best
Shubham

#2

HI @ss13ms110 looks like the chipset is from broadcom/cypress, i’m grabbing one to see if we can get it to work…

Regards,

#3

Hi @RobertCNelson

Thank you for the reply.

Indeed it is a chipset from cypress connected to M.2 slot.

The strange thing is, it is connected connected to M.2 slot but not showing in lspci. It is showing in lsusb

debian@BeagleBone:~$ lspci
00:00.0 PCI bridge: Texas Instruments Device b00d
debian@BeagleBone:~$ 
debian@BeagleBone:~$ 
debian@BeagleBone:~$ lsusb
Bus 002 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 04b4:0bdc Cypress Semiconductor Corp. Cypress USB 802.11 Wireless Adapter
Bus 001 Device 004: ID 04b4:bd30 Cypress Semiconductor Corp. 
Bus 001 Device 003: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
debian@BeagleBone:~$

Thank you

#4

Welcome to M.2 E-key! M.2 - Wikipedia

what does dmesg | grep brcm show?

Might just be missing the firmware…

Regards,

#5

Hi @RobertCNelson

Here is the output:

debian@BeagleBone:~$ dmesg | grep brcm
[   10.611618] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4373 for chip BCM4373/0
[   10.618368] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   10.621954] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4373/0 wl0: Oct 25 2017 03:07:25 version 13.10.246.79 (r674291 CY) FWID 01-6d5ea084
[   10.689863] ieee80211 phy0: brcmf_fws_attach: failed to set bdcv2 tlv signaling
[   10.907852] usbcore: registered new interface driver brcmfmac
[   11.250415] ieee80211 phy0: brcmf_cfg80211_add_iface: iface validation failed: err=-16
debian@BeagleBone:~$

Regards
Shubham