LBEE5XV1YM 4.19 kernel driver and firmware for imx7d

[benjmcgee]

Hello I am using the IMX7D running yocto warrior with a 4.19 kernel. I am trying to get the LBEE5XV1YM WiFi/BT module working. I have enabled the existing driver, loaded firmware that I found online:sdsd8997_combo_v4.bin

The driver seems to load successfully:

=====

root@imx7dsabresd:~# dmesg | grep fiex

[    5.500156] bus: 'sdio': add driver mwifiex_sdio
[    5.500191] bus: 'sdio': driver_probe_device: matched device mmc0:0001:1 with driver mwifiex_sdio
[    6.038011] bus: 'sdio': really_probe: probing driver mwifiex_sdio with device mmc0:0001:1
[    6.038149] mwifiex_sdio mmc0:0001:1: no init pinctrl state
[    6.038170] mwifiex_sdio mmc0:0001:1: no sleep pinctrl state
[    6.038178] mwifiex_sdio mmc0:0001:1: no idle pinctrl state
[    6.115848] driver: 'mwifiex_sdio': driver_bound: bound to device 'mmc0:0001:1'
[    6.116250] bus: 'sdio': really_probe: bound device mmc0:0001:1 to driver mwifiex_sdio
[    8.106079] mwifiex_sdio mmc0:0001:1: info: FW download over, size 623240 bytes
[    8.945345] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[    9.034665] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.68.1.p197)  
[    9.068328] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (16.68.1.p197)

======

I try to enable wifi by using these commands (these commands worked on our previous hardware using a differenc wifi module):

wpa_supplicant -Dnl80211 -imlan0 -c/etc/wpa_supplicant.conf -B
sleep 5
udhcpc -i mlan0

Running these commands results in the following output:

Successfully initialized wpa_supplicant
rfkill: Cannot open RFKILL control device
IPv6: ADDRCONF(NETDEV_UP): mlan0: link is not ready
udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
ieee80211 phy0: sched_scan start : n_ssids=1 n_match_sets=1  
ieee80211 phy0: n_channels=41 interval=10 ie_len=0

The "udhcpc: sending discover" message prints forever and  no network is created

Any thoughts on this? Do I need a different device firmware or driver perhaps?

Thanks,

Ben

[benjmcgee · Accepted solution]

I was able to resolve the issue, it was a general configuration issue. 

[benjmcgee]

I forgot to mention in the previous post I am trying to use the SDIO interface