Other Parts Discussed in Thread: WL1271, TPS62360, TPS65023, TPS65217, TPS65910, TWL6030, TPS65218, TWL6040, WL1835
Hi,
So after much debugging I got to the point where device is detected and firmware seems to be loaded with no error, but there is still no wlan0 interface!
I'm working on a custom distro based on Yocto. I use the latest firmware from linux-firmware git. Note that there is no wl18xx-conf.bin, so fallback config is used:
[ 10.573595] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl18xx-conf.bin failed with error -2
[ 10.584843] wlcore: ERROR could not get configuration binary ti-connectivity/wl18xx-conf.bin: -2
[ 10.594057] wlcore: WARNING falling back to default config
I'm not sure if that is fatal? It does not seem like it when looking at the log.
Kernel is 4.4.10. The wl18xx and related drivers are built as modules so that they can be loaded after the root filesystem (with the firmware binaries ) is mounted.
Any hints on how to debug this?
Here's the part of kernel log where the device is probed and driver loaded:
[ 7.915811] udevd[129]: starting version 182
[ 8.663573] bus: 'sdio': add driver wl1271_sdio
[ 8.668426] bus: 'sdio': driver_probe_device: matched device mmc1:0001:1 with driver wl1271_sdio
[ 8.856672] XXXXXXXXXXXXXXXXXXXX not using max clock!
[ 8.887789] bus: 'sdio': really_probe: probing driver wl1271_sdio with device mmc1:0001:1
[ 8.944626] wl1271_sdio: probe of mmc1:0001:1 rejects match -19
[ 8.950994] bus: 'sdio': driver_probe_device: matched device mmc1:0001:2 with driver wl1271_sdio
[ 8.960312] bus: 'sdio': really_probe: probing driver wl1271_sdio with device mmc1:0001:2
[ 9.099374] device: 'wl18xx.0.auto': device_add
[ 9.105596] driver: 'wl1271_sdio': driver_bound: bound to device 'mmc1:0001:2'
[ 9.113312] bus: 'sdio': really_probe: bound device mmc1:0001:2 to driver wl1271_sdio
[ 10.329010] bus: 'platform': add driver wl18xx_driver
[ 10.334663] bus: 'platform': driver_probe_device: matched device wl18xx.0.auto with driver wl18xx_driver
[ 10.477705] XXXXXXXXXXXXXXXXXXXX not using max clock!
[ 10.483854] bus: 'platform': really_probe: probing driver wl18xx_driver with device wl18xx.0.auto
[ 10.494508] driver: 'wl18xx_driver': driver_bound: bound to device 'wl18xx.0.auto'
[ 10.502589] bus: 'platform': really_probe: bound device wl18xx.0.auto to driver wl18xx_driver
[ 10.512659] XXXXXXXXXXXXX loading firmware ()
[ 10.529560] XXXXXXXXXXXXX loaded firmware from abs path (/lib/firmware/ti-connectivity/wl1271-nvs.bin)
[ 10.539931] XXXXX Enter wl18xx_setup
[ 10.543736] XXXXX In wl18xx_setup step 1
[ 10.547834] XXXXX In wl18xx_setup step 2
[ 10.551962] XXXXX In wl18xx_setup step 3
[ 10.556064] XXXXX Enter wl18xx_conf_init
[ 10.560164] XXXXX Enter wl18xx_load_conf_file
[ 10.564773] XXXXXXXXXXXXX loading firmware (/lib/firmware/ti-connectivity/wl1271-nvs.bin)
[ 10.573595] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl18xx-conf.bin failed with error -2
[ 10.584843] wlcore: ERROR could not get configuration binary ti-connectivity/wl18xx-conf.bin: -2
[ 10.594057] wlcore: WARNING falling back to default config
[ 10.599788] XXXXX wl18xx_conf_init step 1
[ 10.603997] XXXXX wl18xx_conf_init step 2
[ 10.608193] XXXXX wl18xx_conf_init step 3
[ 10.612400] XXXXX Leaving wl18xx_conf_init
[ 10.616681] XXXXX In wl18xx_setup step 4
[ 10.620781] XXXXX In wl18xx_setup step 5
[ 10.624920] XXXXX In wl18xx_setup step 6
[ 10.629019] XXXXX In wl18xx_setup step 7
[ 10.633132] XXXXX In wl18xx_setup step 8
[ 10.637229] XXXXX In wl18xx_setup step 9
[ 10.641325] XXXXX Leaving wl18xx_setup
[ 10.759832] EXT4-fs (mmcblk0p2): re-mounted. Opts: nodelalloc,data=journal
[ 10.813909] XXXXXXXXXXXXXXXXXXXX not using max clock!
All the 'XXXXX' are my debugging printk statements.