Forums - insmod wifi module failed

33 posts / 0 new
Last post
insmod wifi module failed
arnold0kang
Join Date: 4 May 19
Posts: 3
Posted: Sun, 2019-06-02 23:18

hi ,

  I download the QCA 9377 driver from website which is "QCA9377.LEA.3.0_QDN_r3000017.1" . I have build the driver and copy the firmware to my board. when i insmod the mdoule. something wrong. it seems that I miss some firmware. but these firmwre not exist in download package, and im not sure.   please help me .  thanks!

my env: 

  kernel: linux 4.9.37

  arch: arm

  

  the error log: 

     

Quote:
/udisk # insmod wlan.ko

wlan: loading driver v4.0.11.213V
hifDeviceInserted: Dumping clocks (50000000,100000000)
HIFDumpCCCR 0(43) 1(3) 2(0) 3(0) 4(0) 5(0) 6(0) 7(6) 8(17) 9(0) A(10) B(0) C(0) D(0) E(0) F(0) 10(0) 11(0) 12(1) 13(3) 14(7) 15(37) 16(3)
AR6000: Set async interrupt delay clock as 2.
R0: wlan: [234:E :HDD] hdd_apply_cfg_ini: Reg Parameter gRrmOperChanMax > allowed Maximum [8 > 7]. Enforcing Default= 4
R0: wlan: [234:E :HDD] hdd_apply_cfg_ini: Reg Parameter gRrmNonOperChanMax > allowed Maximum [8 > 7]. Enforcing Default= 4
R0: wlan: [234:E :HDD] Name = [gEnableHostapdEdcaLocal] Value = [0]
R0: wlan: [234:E :HDD] Name = [g_sta_change_cc_via_beacon] Value = [0]
R0: [insmod][01:18:14.694004]  wlan: [234:E :HDD] Name = [gEnableHostapdEdcaLocal] Value = [0]
R0: [insmod][01:18:14.702871]  wlan: [234:E :HDD] Name = [g_sta_change_cc_via_beacon] Value = [0]
AR6000: configuration opcode 3 is not used for Linux SDIO stack
NUM_DEV=1 FWMODE=0x2 FWSUBMODE=0x0 FWBR_BUF 0
ol_download_firmware: Using 0x1234 for the remainder of init
R0: [insmod][01:18:14.976617]  wlan: [234:E :VOS] __ol_transfer_bin_file: transferring file: otp30.bin size 25057 bytes done!
ol_download_firmware: chip_id:0x5020001 board_id:0x0
ar6k_wlan mmc2:0001:1: Direct firmware load for bdwlan30.b00 failed with error -2
__ol_transfer_bin_file: Failed to get bdwlan30.b00:-2
__ol_transfer_bin_file: Trying to load default bdwlan30.bin
Board extended Data download address: 0x0
R0: [insmod][01:18:15.051981]  wlan: [234:E :VOS] __ol_transfer_bin_file: transferring file: bdwlan30.bin size 8124 bytes done!
__ol_transfer_bin_file: Loading setup file epping30.bin
ar6k_wlan mmc2:0001:1: Direct firmware load for epping30.bin failed with error -2
__ol_transfer_bin_file: Failed to get epping30.bin:-2
R0: [insmod][01:18:15.416903]  wlan: [234:E :VOS] __ol_transfer_bin_file: transferring file: qwlan30.bin size 619364 bytes done!
+HTCCreate ..  HIF :c4d90000
HIF Interrupt processing is SYNC ONLY
AR6000: configuration opcode 7 is only used for RTOS systems, not Linux systems
AR6000: configuration opcode 5 is not used for Linux SDIO stack
-HTCCreate (0xc4342000)
R0: [insmod][01:18:15.451026]  wlan: [234:F :WDA] WMA --> wmi_unified_attach - success
ol_if_dfs_attach: called; ptr=c4009e68, radar_info=c5397954
R0: [insmod][01:18:15.465171]  wlan: [234:E :SAP] dfs_init_radar_filters[217]: Unknown dfs domain 0
+HWT
send_filled_buffers_to_user: Send Failed -3 drop_count = 1
Target Ready! : transmit resources : 3 size:1792, MaxMsgsPerHTCBundle = 32
HTC Service Index : 1 TX : 0x100 : alloc:3
HTC Service:0x0001, ULpipe:1 DLpipe:0 id:0 Ready
-HWT
MAILBOX SWAP Service is enabled!
is_full_reorder_offloaded? 0
HTC Service TX : 0x300 : allocation is zero!
HTCConnectService, host indicate support b2b bundle
HTCConnectService, firmware decide to disabled b2b bundle
HTC Service:0x0300, ULpipe:1 DLpipe:0 id:1 Ready
TXRX: page_divider 0x5, offset_filter 0x1f num elem 4800, ol desc num page 150, ol desc per page 32HTCConnectService, host indicate support b2b bundle
HTCConnectService, firmware decide to disabled b2b bundle
HTC Service:0x0100, ULpipe:3 DLpipe:2 id:2 Ready
R0: [insmod][01:18:15.559688]  wlan: [234:F :WDA] WMA --> wmi_unified_connect_htc_service - success
R0: [VosMCThread][01:18:15.568533]  wlan: [239:F :WDA] McThread: WNI_CFG_DNLD_REQ
HTC using TX credit flow control
__wmi_control_rx: WMI UNIFIED SERVICE AVAILABLE event
R0: [kworker/1:0][01:18:15.605088]  wlan: [15:F :WDA] WMA <-- WMI_SERVICE_AVAILABLE_EVENTID
__wmi_control_rx: WMI UNIFIED SERVICE READY event
R0: [kworker/1:0][01:18:15.617708]  wlan: [15:F :WDA] WMA <-- WMI_SERVICE_READY_EVENTID
R0: [kworker/1:0][01:18:15.625474]  wlan: [15:E :WDA] wma_rx_service_ready_event: Firmware build version : 00000017
R0: [kworker/1:0][01:18:15.635654]  wlan: [15:E :WDA] wma_rx_service_ready_event: Board version: 0.2201400a
R0: [kworker/1:0][01:18:15.645168]  wlan: [15:F :WDA] WMA --> WMI_INIT_CMDID
ol_target_failure: Loading/Unloading is in progress, ignore!
R0: [insmod][01:18:17.589981]  wlan: [234:F :WDA] wma_wait_for_ready_event: Timeout waiting for ready event from FW
R0: [insmod][01:18:17.600174]  wlan: [234:F :SYS] Failed to get ready event from target firmware
VOS ASSERT in vos_preStart Line 976
------------[ cut here ]------------
WARNING: CPU: 0 PID: 234 at /root/enforce_cam_v2/ec_driver/QCA9377.LEA.3.0_QDN_r3000017.1/fixce/AIO/build/../drivers/qcacld-new/CORE/VOSS/src/vos_api.c:976 vos_preStart+0x398/0x3a0 [wlan]
Modules linked in: wlan(O+) mac80211 cfg80211 g_mass_storage usb_f_mass_storage libcomposite
CPU: 0 PID: 234 Comm: insmod Tainted: G        W  O    4.9.37 #20
Hardware name: Generic DT based system
[<c010fdf0>] (unwind_backtrace) from [<c010b3d8>] (show_stack+0x10/0x14)
[<c010b3d8>] (show_stack) from [<c033007c>] (dump_stack+0x84/0x98)
[<c033007c>] (dump_stack) from [<c0118c00>] (__warn+0xe8/0x100)
[<c0118c00>] (__warn) from [<c0118cc8>] (warn_slowpath_null+0x20/0x28)
[<c0118cc8>] (warn_slowpath_null) from [<bf7e63e4>] (vos_preStart+0x398/0x3a0 [wlan])
[<bf7e63e4>] (vos_preStart [wlan]) from [<bf675c50>] (hdd_wlan_startup+0x75c/0x22fc [wlan])
[<bf675c50>] (hdd_wlan_startup [wlan]) from [<bf878ce0>] (ath_hif_sdio_probe+0x374/0x390 [wlan])
[<bf878ce0>] (ath_hif_sdio_probe [wlan]) from [<bf879c04>] (HIFSetMboxSleep+0x56c/0x808 [wlan])
[<bf879c04>] (HIFSetMboxSleep [wlan]) from [<bf87c5e4>] (hifDeviceInserted+0x468/0x9c8 [wlan])
[<bf87c5e4>] (hifDeviceInserted [wlan]) from [<c04744bc>] (sdio_bus_probe+0x108/0x11c)
[<c04744bc>] (sdio_bus_probe) from [<c03aff5c>] (driver_probe_device+0x204/0x2b0)
[<c03aff5c>] (driver_probe_device) from [<c03b00c0>] (__driver_attach+0xb8/0xbc)
[<c03b00c0>] (__driver_attach) from [<c03ae338>] (bus_for_each_dev+0x68/0x9c)
[<c03ae338>] (bus_for_each_dev) from [<c03af3d0>] (bus_add_driver+0x108/0x214)
[<c03af3d0>] (bus_add_driver) from [<c03b07e8>] (driver_register+0x78/0xf4)
[<c03b07e8>] (driver_register) from [<bf879360>] (HIFInit+0x84/0x118 [wlan])
[<bf879360>] (HIFInit [wlan]) from [<bf878688>] (hif_register_driver+0xac/0x124 [wlan])
[<bf878688>] (hif_register_driver [wlan]) from [<bf66860c>] (hdd_hif_register_driver+0x34/0xf8 [wlan])
[<bf66860c>] (hdd_hif_register_driver [wlan]) from [<bfae2118>] (init_module+0x118/0x1d4 [wlan])
[<bfae2118>] (init_module [wlan]) from [<c010173c>] (do_one_initcall+0x44/0x16c)
[<c010173c>] (do_one_initcall) from [<c0194f48>] (do_init_module+0x60/0x380)
[<c0194f48>] (do_init_module) from [<c0185be8>] (load_module+0x19ec/0x1fdc)
[<c0185be8>] (load_module) from [<c018632c>] (SyS_init_module+0x154/0x16c)
[<c018632c>] (SyS_init_module) from [<c0107400>] (ret_fast_syscall+0x0/0x3c)
---[ end trace 6c1aec9493298d16 ]---
R0: [insmod][01:18:17.865163]  wlan: [234:F :HDD] hdd_wlan_startup: vos_preStart failed
R0: [VosMCThread][01:18:17.872953]  wlan: [239:E :VOS] VosMCThread: MC Thread exiting!!!!
R0: [VosTlshimRxThre][01:18:17.880955]  wlan: [240:E :VOS] VosTlshimRxThread: Shutting down tl shim Tlshim rx thread
R0: [VosTlshimRxThre][01:18:17.891247]  wlan: [240:E :VOS] VosTlshimRxThread: Exiting VOSS Tlshim rx thread
R0: [insmod][01:18:17.904097]  wlan: [234:E :VOS] vos_get_context: Module ID 17 context is Null
R0: wlan: [234:F :HIF]  hdd_wlan_startup failed
ar6k_wlan: probe of mmc2:0001:1 failed with error -1
ath_hif_sdio: HIF (Atheros/multi-bss)
R0: wlan: [234:E :HDD] hdd_hif_register_driver: 17769: hdd_wlan_startup failed status:-11 jiffies_left:14000
R0: wlan: [234:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
AR6000: Unregistering with the bus driver
AR6000: Unregistered!insmod: can't insert 'wlan.ko': No such device
 

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Mon, 2019-06-03 05:28

Hi Paul,

Some of the firmware .bin files are not needed. Whichever are needed, they got downloaded successfully.

The real problem in your setup is related to SDIO. The transactions might be failing but it's not visible in dmesg logs.

R0: [insmod][01:18:17.589981]  wlan: [234:F :WDA] wma_wait_for_ready_event: Timeout waiting for ready event from FW
R0: [insmod][01:18:17.600174]  wlan: [234:F :SYS] Failed to get ready event from target firmware

Please enable SDIO logs and check what's going wrong.
 
Thanks.

 

  • Up0
  • Down0
arnold0kang
Join Date: 4 May 19
Posts: 3
Posted: Wed, 2019-06-05 00:28

hi , 

  thanks your reply. I think i get the real error. Unable to read HOST_INT_STATUS_ADDRESS register. can you give me some adivces?  when I install modules. the wlan.ko stopped. I have to press CTRL+C to interrupte it.

   /udisk/ko # insmod wlan.ko

wlan: loading out-of-tree module taints kernel.
wlan: loading driver v4.0.11.213V
hifDeviceInserted: Dumping clocks (50000000,50000000)
HIFDumpCCCR 0(43) 1(3) 2(0) 3(0) 4(0) 5(0) 6(0) 7(6) 8(17) 9(0) A(10) B(0) C(0) D(0) E(0) F(0) 10(0) 11(0) 12(1) 13(7) 14(7) 15(37) 16(1)
AR6000: Set async interrupt delay clock as 2.
R0: wlan: [115:E :HDD] hdd_apply_cfg_ini: Reg Parameter gRrmOperChanMax > allowed Maximum [8 > 7]. Enforcing Default= 4
R0: wlan: [115:E :HDD] hdd_apply_cfg_ini: Reg Parameter gRrmNonOperChanMax > allowed Maximum [8 > 7]. Enforcing Default= 4
R0: wlan: [115:E :HDD] Name = [gEnableHostapdEdcaLocal] Value = [0]
R0: wlan: [115:E :HDD] Name = [g_sta_change_cc_via_beacon] Value = [0]
R0: [insmod][01:53:02.113487]  wlan: [115:E :HDD] Name = [gEnableHostapdEdcaLocal] Value = [0]
R0: [insmod][01:53:02.122391]  wlan: [115:E :HDD] Name = [g_sta_change_cc_via_beacon] Value = [0]
AR6000: configuration opcode 3 is not used for Linux SDIO stack
NUM_DEV=1 FWMODE=0x2 FWSUBMODE=0x0 FWBR_BUF 0
ol_download_firmware: Using 0x1234 for the remainder of init
R0: [insmod][01:53:03.997106]  wlan: [115:E :VOS] __ol_transfer_bin_file: transferring file: utf30.bin size 372688 bytes done!
random: crng init done
^CUnable to read HOST_INT_STATUS_ADDRESS register
BMI : Unable to read response from device
Unable to read from the device
ol_download_firmware: chip_id:0x5020001 board_id:0x0
Unable to decrement the command credit count register
BMI : Unable to Send Message to device
Unable to read from the device
ar6k_wlan mmc2:0001:1: loading /lib/firmware/otp30.b00 failed with error -4
ar6k_wlan mmc2:0001:1: Direct firmware load for otp30.b00 failed with error -4
__ol_transfer_bin_file: Failed to get otp30.b00:-4
__ol_transfer_bin_file: Trying to load default otp30.bin
ar6k_wlan mmc2:0001:1: loading /lib/firmware/otp30.bin failed with error -4
ar6k_wlan mmc2:0001:1: Direct firmware load for otp30.bin failed with error -4
__ol_transfer_bin_file: Failed to get otp30.bin:-4
ol_download_firmware: Board Data Download Failed
R0: [insmod][01:53:28.185404]  wlan: [115:F :VOS] vos_open: BMI failed to download target
R0: [VosMCThread][01:53:28.193349]  wlan: [120:E :VOS] VosMCThread: MC Thread exiting!!!!
R0: [VosTlshimRxThre][01:53:28.201314]  wlan: [121:E :VOS] VosTlshimRxThread: Shutting down tl shim Tlshim rx thread
R0: [VosTlshimRxThre][01:53:28.211593]  wlan: [121:E :VOS] VosTlshimRxThread: Exiting VOSS Tlshim rx thread
R0: [insmod][01:53:28.223640]  wlan: [115:F :HDD] hdd_wlan_startup: vos_open failed
R0: wlan: [115:F :HIF]  hdd_wlan_startup failed
ar6k_wlan: probe of mmc2:0001:1 failed with error -1
ath_hif_sdio: HIF (Atheros/multi-bss)
R0: wlan: [115:E :HDD] hdd_hif_register_driver: 17769: hdd_wlan_startup failed status:-11 jiffies_left:14000
R0: wlan: [115:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
AR6000: Unregistering with the bus driver
AR6000: Unregistered!
/udisk/ko #
 
  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Wed, 2019-06-05 04:58

Hi Arnold,

Which is the platform on which you are trying the card? Does it support SDIO 3.0?

Also, can you comment out  the line having "-DSDIO_3_0 \" in the qcacld-2.0/Kbuild file, build the driver and test with it?

 

The error you are seeing is most likely related to your interface , SDIO in this case. You may want to enable SD/MMC logs in your kernel to confirm. There is a better way to have the logs dynamically enabled. Here are the steps:

Enable "CONFIG_MMC_DEBUG" in kernel .config file and then rebuild the kernel.
If "CONFIG_DYNAMIC_DEBUG" is enabled in the kernel config, then simply run these 2 commands before you insmod wlan.ko. 

#echo -n 'module mmc_core +p' > /sys/kernel/debug/dynamic_debug/control 

#echo -n 'file sdio_irq.c +p' > /sys/kernel/debug/dynamic_debug/control 

 

Thanks.

  • Up0
  • Down0
arnold0kang
Join Date: 4 May 19
Posts: 3
Posted: Thu, 2019-06-06 08:08

hi  sir, 

  thanks for your reply. when i disable sdio 3.0. it still failed.   can you give me some advice again. thanks!

 

mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
mmc2: starting CMD53 arg 14100a04 flags 000001b5
mmc2:     blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
mmc2: starting CMD53 arg 14100a04 flags 000001b5
mmc2:     blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
mmc2: starting CMD53 arg 14100a04 flags 000001b5
mmc2:     blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
mmc2: starting CMD53 arg 14100a04 flags 000001b5
mmc2:     blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
mmc2: starting CMD53 arg 14100a04 flags 000001b5
mmc2:     blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
mmc2: starting CMD53 arg 14100a04 flags 000001b5
mmc2:     blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
mmc2: starting CMD53 arg 14100a04 flags 000001b5
mmc2:     blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
BMI Communication timeout - bmiBufferReceive FIFO empty
Unable to read Target Version from the device
R0: [insmod][18:29:37.120599]  wlan: [113:F :VOS] vos_open: BMI failed to download target
R0: [VosMCThread][18:29:37.128537]  wlan: [118:E :VOS] VosMCThread: MC Thread exiting!!!!
R0: [VosTlshimRxThre][18:29:37.136498]  wlan: [119:E :VOS] VosTlshimRxThread: Shutting down tl shim Tlshim rx thread
R0: [VosTlshimRxThre][18:29:37.146779]  wlan: [119:E :VOS] VosTlshimRxThread: Exiting VOSS Tlshim rx thread
R0: [insmod][18:29:37.158782]  wlan: [113:F :HDD] hdd_wlan_startup: vos_open failed
R0: wlan: [113:F :HIF]  hdd_wlan_startup failed
mmc2: starting CMD53 arg 9410d004 flags 000001b5
mmc2:     blksz 4 blocks 1 flags 00000100 tsac 1000 ms nsac 0
mmc2: req done (CMD53): 0: 00001000 00000000 00000000 00000000
mmc2:     4 bytes transferred: 0
SDIO: Disabling device mmc2:0001:1...
mmc2: starting CMD52 arg 00000400 flags 00000195
mmc2: req done (CMD52): 0: 00001002 00000000 00000000 00000000
mmc2: starting CMD52 arg 80000400 flags 00000195
mmc2: req done (CMD52): 0: 00001000 00000000 00000000 00000000
SDIO: Disabled device mmc2:0001:1
ar6k_wlan: probe of mmc2:0001:1 failed with error -1
ath_hif_sdio: HIF (Atheros/multi-bss)
R0: wlan: [113:E :HDD] hdd_hif_register_driver: 17769: hdd_wlan_startup failed status:-11 jiffies_left:14000
R0: wlan: [113:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
AR6000: Unregistering with the bus driver
AR6000: Unregistered!
 

 

 

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Mon, 2019-06-10 04:10

Hi Arnold,

Which Embedded platform are you using?

Such errors are due to SDIO clocks also. Could you please try below different clocks during driver load and let us know if any improvements:

#insmod wlan.ko mmcclock=X

mmcclock=12500000 means 12.5 MHz. You can change it to 5, 10, 12.5, 15, 20, 25, 50, 75 ... and see if you get better results. 

Thanks.

  • Up0
  • Down0
xhlaw
Join Date: 5 Mar 20
Posts: 5
Posted: Mon, 2020-03-23 00:44

Hi,

I think I faced same issue exactly with Arnold when insmod wlan.ko. I had cross compiled QCA9377 driver (wlan.ko) for ARM architecture by using the package as shown below and copied it to my ARM platform board. In this post had attached the error log when insmod wlan.ko. 

The error log seem like deliver the message that SDIO failed to be communicated, and I had tried out the previous suggested methods but still failed when insmod wlan.ko.

May I have some other suggetions to solve this issue? 
 

The followings are the environment on my site to insert wlan.ko:

Kernel Version: 4.4.15

Platform arch: ARM

QCA9377 driver package: qca9377.lea_.3.0_qdn_r3000017.1.tgz

WLAN driver version: 4.5.25.38

Here is the kernel log:

[ 1403.006886] vmap allocation for size 4558848 failed: use vmalloc=<size> to increase size.
[ 1403.026441] wlan: loading driver v4.5.25.38
[ 1403.026872] hifDeviceInserted: Dumping clocks (50000000,192000000)
[ 1403.031246] R0: wlan: [2552:E :HDD] hdd_apply_cfg_ini: Reg Parameter gRrmOperChanMax > allowed Maximum [8 > 7]. Enforcing Default= 4
[ 1403.035692] R0: wlan: [2552:E :HDD] hdd_apply_cfg_ini: Reg Parameter gRrmNonOperChanMax > allowed Maximum [8 > 7]. Enforcing Default= 4
[ 1403.169530] mmci-pl18x 12180000.sdcc: unsupported block size (12 bytes)
[ 1403.169565] AR6000: SDIO bus operation failed! MMC stack returned : -22 
[ 1403.174994] __HIFReadWrite, addr:0X0017F4, len:00000012, Write, Sync 
[ 1403.182153] Unable to send the BMI data to the device
[ 1403.188278] BMI : Unable to Send Message to device 
[ 1403.193259] Unable to read from the device
[ 1403.198024] BMIReadMemory for setting fwmode failed 
[ 1403.202124] R0: [insmod][06:08:35.941832]  wlan: [2552:F :VOS] vos_open: BMI failed to download target
[ 1403.207360] R0: [VosMCThread][06:08:35.947062]  wlan: [2557:E :VOS] VosMCThread: MC Thread exiting!!!!
[ 1403.216786] R0: [VosTlshimRxThre][06:08:35.956495]  wlan: [2558:E :VOS] VosTlshimRxThread: Shutting down tl shim Tlshim rx thread
[ 1403.225654] R0: [VosTlshimRxThre][06:08:35.965364]  wlan: [2558:E :VOS] VosTlshimRxThread: Exiting VOSS Tlshim rx thread
[ 1403.241281] R0: [insmod][06:08:35.980985]  wlan: [2552:F :HDD] hdd_wlan_startup: vos_open failed
[ 1403.249486] R0: wlan: [2552:F :HIF]  hdd_wlan_startup failed
[ 1403.257446] tx_completion_task: tx completion task stopping
[ 1403.264386] ar6k_wlan: probe of mmc0:0001:1 failed with error -1
[ 1403.268536] ath_hif_sdio: HIF (Atheros/multi-bss)
[ 1403.274311] R0: wlan: [2552:E :HDD] hdd_hif_register_driver: 18314: hdd_wlan_startup failed status:-11 jiffies_left:14000
[ 1403.279167] R0: wlan: [2552:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
[ 1403.290086] AR6000: Unregistering with the bus driver
[ 1403.298048] AR6000: Unregistered!failed to insert wlan.ko
Thanks 
XH
 
  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Mon, 2020-03-23 03:58

Hi XH,

Your issue is different than Arnold.

[ 1403.169530] mmci-pl18x 12180000.sdcc: unsupported block size (12 bytes)
[ 1403.169565] AR6000: SDIO bus operation failed! MMC stack returned : -22 
[ 1403.174994] __HIFReadWrite, addr:0X0017F4, len:00000012, Write, Sync 
 
1. What's the Board you are using?
2. What's the inbuilt SDIO Controller in that board?
3. Did you try to use the driver on an x86 laptop? The QCA9377 SDIO module works well with these laptops:
 
HP EliteBook 8460p
HP EliteBook 8470w
Dell Latitude E6330
Dell E5430
Lenovo T430
Lenovo T420
Lenovo T410
Lenovo SL400

 

Thanks.

  • Up0
  • Down0
xhlaw
Join Date: 5 Mar 20
Posts: 5
Posted: Mon, 2020-03-23 20:35

Hi,

First of all, thanks for your reply.

1. Currently I am using the board with Qualcomm chipset IPQ8065

2. The board have a micro SD card slot and I use an adapter (TFtoSD) connect with QCA 9377 SDIO

3. Unfortunately, I don't have any laptop stated above. But I had tried the driver on x86 pc with linux kernel 4.4.15 but failed to insert the driver also.

Thanks,
XH
 

 

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Tue, 2020-03-24 04:44

Hi XH,

Thank you for sharing details.

We need to make sure if our card was enumerated. We should see a new mmc device in /sys/bus/mmc/devices after inserting QCA9377 to SDIO slot. Something like this, after inserting the card:

vtanuku@blrnapleshost01:~$ ls /sys/bus/mmc/devices/
 
mmc0:0001

 

Do you see this?

Thanks.

  • Up0
  • Down0
xhlaw
Join Date: 5 Mar 20
Posts: 5
Posted: Tue, 2020-03-24 08:49

Hi,

Yes, I can see the new mmc device (mmc0:0001) under /sys/bus/mmc/devices after inserting QCA9377 SDIO card and can detect the vendor ID as well. However, the driver still failed to insert although ID can be detected, this is the error log:

 

This is the log when I insert the QCA9377 SDIO to IPQ8065 board:

[  350.766795] mmc0: cannot verify signal voltage switch
[  350.794751] mmc0: queuing unknown CIS tuple 0x01 (3 bytes)
[  350.805214] mmc0: queuing unknown CIS tuple 0x1a (5 bytes)
[  350.809820] mmc0: queuing unknown CIS tuple 0x1b (8 bytes)
[  350.810539] mmc0: queuing unknown CIS tuple 0x14 (0 bytes)
[  350.826880] mmc0: tuning execution failed
[  350.826914] mmc0: error -11 whilst initialising SDIO card
[  350.926493] mmc0: cannot verify signal voltage switch
[  350.931723] mmc0: queuing unknown CIS tuple 0x01 (3 bytes)
[  350.941014] mmc0: queuing unknown CIS tuple 0x1a (5 bytes)
[  350.944500] mmc0: queuing unknown CIS tuple 0x1b (8 bytes)
[  350.946186] mmc0: queuing unknown CIS tuple 0x14 (0 bytes)
[  350.954330] mmc0: queuing unknown CIS tuple 0x80 (1 bytes)
[  350.956686] mmc0: queuing unknown CIS tuple 0x81 (1 bytes)
[  350.962027] mmc0: new high speed SDIO card at address 0001
 
While this is the error log when insmod wlan.ko without inserting QCA9377 SDIO:
[  473.034677] vmap allocation for size 4558848 failed: use vmalloc=<size> to increase size.
[  473.036642] vmap allocation for size 262144 failed: use vmalloc=<size> to increase size.
[  473.062791] wlan: loading driver v4.5.25.38
[  473.062962] ath_hif_sdio: HIF (Atheros/multi-bss)
[  613.056216] R0: wlan: [2695:E :HDD] hdd_hif_register_driver: 18307: hif registration timedout
[  613.056261] R0: wlan: [2695:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
[  613.063724] AR6000: Unregistering with the bus driver
[  613.071755] AR6000: Unregistered!failed to insert wlan.ko
 

Thanks,

XH

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Thu, 2020-03-26 01:23

Hi XH,

[  473.034677] vmap allocation for size 4558848 failed: use vmalloc=<size> to increase size.
[  473.036642] vmap allocation for size 262144 failed: use vmalloc=<size> to increase size.
 
Do you see this error while loading the driver? Or is it some generic print from your linux platform?
 
Thanks.
  • Up0
  • Down0
xhlaw
Join Date: 5 Mar 20
Posts: 5
Posted: Thu, 2020-03-26 02:05

Hi,

Thanks for looking out my issue.

Sorry, it is my mistake when copying the error log, the following I attached is the errror when I load the driver with inserting QCA9377 SDIO:

[  900.946034] vmap allocation for size 4558848 failed: use vmalloc=<size> to increase size.
[  900.964836] wlan: loading driver v4.5.25.38
[  900.965292] hifDeviceInserted: Dumping clocks (50000000,192000000)
[  900.971142] R0: wlan: [2576:E :HDD] hdd_apply_cfg_ini: Reg Parameter gRrmOperChanMax > allowed Maximum [8 > 7]. Enforcing Default= 4
[  900.974114] R0: wlan: [2576:E :HDD] hdd_apply_cfg_ini: Reg Parameter gRrmNonOperChanMax > allowed Maximum [8 > 7]. Enforcing Default= 4
[  900.989387] send_filled_buffers_to_user: Send Failed -3 drop_count = 1
[  901.116715] mmci-pl18x 12180000.sdcc: unsupported block size (12 bytes)
[  901.116743] AR6000: SDIO bus operation failed! MMC stack returned : -22 
[  901.122165] __HIFReadWrite, addr:0X0017F4, len:00000012, Write, Sync 
[  901.129246] Unable to send the BMI data to the device
[  901.135435] BMI : Unable to Send Message to device 
[  901.140543] Unable to read from the device
[  901.145158] BMIReadMemory for setting fwmode failed 
[  901.149391] R0: [insmod][07:41:45.009145]  wlan: [2576:F :VOS] vos_open: BMI failed to download target
[  901.154482] R0: [VosMCThread][07:41:45.014236]  wlan: [2582:E :VOS] VosMCThread: MC Thread exiting!!!!
[  901.163786] R0: [VosTlshimRxThre][07:41:45.023533]  wlan: [2583:E :VOS] VosTlshimRxThread: Shutting down tl shim Tlshim rx thread
[  901.172950] R0: [VosTlshimRxThre][07:41:45.032700]  wlan: [2583:E :VOS] VosTlshimRxThread: Exiting VOSS Tlshim rx thread
[  901.187165] R0: [insmod][07:41:45.046919]  wlan: [2576:F :HDD] hdd_wlan_startup: vos_open failed
[  901.196206] R0: wlan: [2576:F :HIF]  hdd_wlan_startup failed
[  901.204357] tx_completion_task: tx completion task stopping
[  901.211288] ar6k_wlan: probe of mmc0:0001:1 failed with error -1
[  901.215328] ath_hif_sdio: HIF (Atheros/multi-bss)
[  901.221659] R0: wlan: [2576:E :HDD] hdd_hif_register_driver: 18314: hdd_wlan_startup failed status:-11 jiffies_left:14000
[  901.226236] R0: wlan: [2576:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
[  901.237221] AR6000: Unregistering with the bus driver
[  901.244904] AR6000: Unregistered!failed to insert wlan.ko
 
Thanks,
XH
  • Up0
  • Down0
xhlaw
Join Date: 5 Mar 20
Posts: 5
Posted: Tue, 2020-03-31 21:32

Hi, 

Shall I modify the board device tree (dtsi) file? 

Thanks,

XH

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Wed, 2020-04-01 11:18

Hi XH,

What are you going to modify in your DTSI file?

From the logs that you have shared so far, it seems an incompatibility from your host controller. I'm trying to check internally about the errors you are seeing.

Thanks.

  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Mon, 2020-05-25 20:26

Hi,

I am using module QCA9377-3 and SDK "qca9377.lea_.3.0_qdn_r3000017.1" from Qualcomm's website to build and try install driver.

- Kernel: 4.11.0

- Wlan version: 4.0.11.213V

I use cmd: insmod wlan.ko to install the driver for module QCA9377, but it fail:

[13536.075602] INFO: task insmod:54119 blocked for more than 120 seconds.
[13536.075606]       Tainted: G           OE   4.11.0+ #11
[13536.075607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[13536.075608] insmod          D    0 54119  54118 0x00000000
[13536.075611] Call Trace:
[13536.075725]  __schedule+0x3b9/0x8f0
[13536.075727]  schedule+0x36/0x80
[13536.075729]  schedule_timeout+0x188/0x310
[13536.075750]  ? del_timer_sync+0x50/0x50
[13536.075754]  wait_for_completion_timeout+0xad/0x140
[13536.075755]  ? wait_for_completion_timeout+0xad/0x140
[13536.075773]  ? wake_up_q+0x70/0x70
[13536.075775]  ? 0xffffffffc0c95000
[13536.075840]  hdd_hif_register_driver+0x52/0x100 [wlan]
[13536.075859]  init_module+0x127/0x1000 [wlan]
[13536.075879]  do_one_initcall+0x53/0x1a0
[13536.075883]  ? __vunmap+0x81/0xd0
[13536.075899]  ? kmem_cache_alloc_trace+0x152/0x1c0
[13536.075915]  ? kfree+0x162/0x170
[13536.075916]  ? kfree+0x162/0x170
[13536.075959]  do_init_module+0x5f/0x1ff
[13536.075963]  load_module+0x2641/0x2b30
[13536.076007]  ? ima_post_read_file+0x7d/0xa0
[13536.076012]  ? security_kernel_post_read_file+0x6b/0x80
[13536.076014]  SYSC_finit_module+0xdf/0x110
[13536.076015]  ? SYSC_finit_module+0xdf/0x110
[13536.076016]  SyS_finit_module+0xe/0x10
[13536.076017]  entry_SYSCALL_64_fastpath+0x1e/0xad
[13536.076018] RIP: 0033:0x7f9d9566a4d9
[13536.076019] RSP: 002b:00007ffc33194b58 EFLAGS: 00000202 ORIG_RAX: 0000000000000139
[13536.076020] RAX: ffffffffffffffda RBX: 00007f9d9592db20 RCX: 00007f9d9566a4d9
[13536.076022] RDX: 0000000000000000 RSI: 000055fd32fba26b RDI: 0000000000000003
[13536.076023] RBP: 0000000000001011 R08: 0000000000000000 R09: 00007f9d9592fea0
[13536.076023] R10: 0000000000000003 R11: 0000000000000202 R12: 00007f9d9592db78
[13536.076024] R13: 00007f9d9592db78 R14: 000000000000270f R15: 00007f9d9592e1a8
[13538.124117] R0: wlan: [54119:E :HDD] hdd_hif_register_driver: 17762: hif registration timedout
[13538.124119] R0: wlan: [54119:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
[13538.124121] AR6000: Unregistering with the bus driver
====
insmod: ERROR: could not insert module AIO/rootfs-te-f30.build/lib/modules/wlan.ko: No such device
 
Can you give me any advice? Thank you so much.
 
Regards,
Lap
 
  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Mon, 2020-05-25 22:08

Hi Lap,

I see a timeout in the logs:

[13538.124117] R0: wlan: [54119:E :HDD] hdd_hif_register_driver: 17762: hif registration timedout

1. Have you checked if the card was detected?

Detection:

we have to see a new mmc device in /sys/bus/mmc/devices after inserting dut

ls /sys/bus/mmc/devices

 

Something like this, after inserting the card

vtanuku@blrnapleshost01:~$ ls /sys/bus/mmc/devices/

mmc0:0001

 

2. Which Laptop/Platform are you using for this test?
Following are the supported laptop models

Some Lenovo SL410
Some L412
HP EliteBook 8460p
HP EliteBook 8470w
Dell Latitude E6330
Dell E5430
Lenovo T430
Lenovo T420
Lenovo T410
Lenovo SL400
MSi U270DX
Toshiba R700
  •  
  • Thanks.
  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Tue, 2020-05-26 03:09

Hi,

Thank you for your reply.

1. After insert the card, I go to ls /sys/bus/mmc/devices/ and no device is showed. But in my laptop can detect the device on Player/Removable Device of my VMware Vitural Machine.

2. I using the Latitude 3490 and other is Dell Inspirion for tetst but it still faill when insmod the driver.

When try on Dell Inspirion, the dmesg as below:

[32773.031032] AR6000: Unregistered!

[32848.351879] usb 1-1: new high-speed USB device number 9 using ehci-pci
[32848.722572] usb 1-1: New USB device found, idVendor=0bda, idProduct=0177
[32848.722584] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32848.722593] usb 1-1: Product: USB2.0-CRW
[32848.722601] usb 1-1: Manufacturer: Generic
[32848.722609] usb 1-1: SerialNumber: 20121112761000000
[32848.741420] usb-storage 1-1:1.0: USB Mass Storage device detected
[32848.742203] scsi host33: usb-storage 1-1:1.0
[32849.771468] scsi 33:0:0:0: Direct-Access Generic- SD/MMC/MS PRO 1.00 PQ: 0 ANSI: 4
[32849.780704] sd 33:0:0:0: Attached scsi generic sg2 type 0
[32857.045148] sd 33:0:0:0: [sdb] Attached SCSI removable disk
[32861.420860] usb 1-1: USB disconnect, device number 9
[32889.179124] wlan: loading driver v4.0.11.213V
[32889.188357] ath_hif_sdio: HIF (Atheros/multi-bss)
[32916.195556] usb 1-1: new high-speed USB device number 10 using ehci-pci
[32916.572407] usb 1-1: New USB device found, idVendor=0bda, idProduct=0177
[32916.572418] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32916.572427] usb 1-1: Product: USB2.0-CRW
[32916.572433] usb 1-1: Manufacturer: Generic
[32916.572440] usb 1-1: SerialNumber: 20121112761000000
[32916.592218] usb-storage 1-1:1.0: USB Mass Storage device detected
[32916.592767] scsi host33: usb-storage 1-1:1.0
[32917.609416] scsi 33:0:0:0: Direct-Access Generic- SD/MMC/MS PRO 1.00 PQ: 0 ANSI: 4
[32917.615633] sd 33:0:0:0: Attached scsi generic sg2 type 0
[32924.877061] sd 33:0:0:0: [sdb] Attached SCSI removable disk
[32929.251532] usb 1-1: USB disconnect, device number 10
[33035.171769] R0: wlan: [74502:E :HDD] hdd_hif_register_driver: 17762: hif registration timedout
[33035.171778] R0: wlan: [74502:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
[33035.171784] AR6000: Unregistering with the bus driver
====
insmod: ERROR: could not insert module AIO/rootfs-te-f30.build/lib/modules/wlan.ko: No such device
 
Seem the USB is auto disconnected when the command insmod is working and the process is fail.
 
Do you have any idea for the problem? 
 
Regards.
Lap
  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Wed, 2020-05-27 06:57

Hi Lap,

Are you using QCA9377 USB or SDIO module?

The SDIO is only supported by the software.

Thanks.

  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Wed, 2020-05-27 20:04

Hi,

I am using the board with interface SDIO. I connect the board and my laptop by SD card slot on laptop.

I don't know why the log display that USB

I am still fail when try insmod driver to the board.

Regards,

Lap

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Wed, 2020-05-27 23:28

Hi Lap,

Not sure on the USB enumeration.

Since you are using a laptop that is not known to work for QCA9377 SDIO, we aren't sure what might be going wrong.

Please use one of the above laptops from the "Supported Laptops list". I already shared with you in previous response.
If still doesn't work, we can help to check.

Thanks.

  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Sun, 2020-06-14 23:52

Hi,

I tested with Lenovo T430 but it still can not detect the HW. In path /sys/bus/mmc/devices: no device here

And also can not insmod the driver for the HW

Have you any idea?

Regards,

Lap

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Mon, 2020-06-15 01:24

Hi Lap,

T430 is verified to be working. At least you should see some prints in dmesg when you insert the card. Can you check?

What happens when you insmod? HIF registration fails?

Thanks.

  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Mon, 2020-06-15 01:47

Hi,

I inserted the HW into SD card slot and no log from dmesg, nothing happen in linux or windown.

When run the insmod command, it's fail with notified: no such device.

Regards,

Lap

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Mon, 2020-06-15 07:08

Does your kernel have SD/MMC support enabled?

  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Mon, 2020-06-15 19:45

Hi,

Sure about that. I already enable all SD/MMC support in menu_makeconfig follow the document of Qualcomm.

Please confirm the version Ubuntu and version Kernel which you use for test?

Current I use Ubuntu 16.4 and Kernel 4.11, is it OK?

Regards,

Lap

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Mon, 2020-06-15 23:15

Hi Lap,

We verify on 4.9 generally and it works.

On 4.11, are you able to build the driver? If so, I believe you can use it as well.

I still doubt on the SDIO detection. If you have an SD/MMC memory card, you may check if that gets detected.

Unless the card gets detected, we may not be able to help much.

Thanks.

  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Mon, 2020-06-15 23:45

Hi,

I use kernel version 4.11 and can build the driver successfully.

I used the SD card to test and the laptop can detect the SD card, can read/ write file.

If not any other solution, I will try with Kernel version 4.9.

Regards,

Lap

  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Wed, 2020-07-22 12:23

Lap,

As suggested, please verify your slot supports SDIO too. You might already know SD and SDIO are 2 different things.

SD card detection is fine but you need to test if QCA9377 SDIO card gets detected or not.

Thanks.

  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Fri, 2020-07-31 02:51

Hi,

Thank you for your advice. Currenlly, my laptop can detect the HW via SDIO port.

I copied all the file from "Source" to "Target" follow the Qualcomm document and try insmod, but it fail.

Here my log:

[  149.854335] mmc0: new high speed SDIO card at address 0001
[  218.357008] wlan: loading out-of-tree module taints kernel.
[  218.361790] wlan: module verification failed: signature and/or required key missing - tainting kernel
[  218.377930] wlan: loading driver v4.0.11.213V
[  363.506037] INFO: task insmod:2213 blocked for more than 120 seconds.
[  363.506050]       Tainted: G           OE   4.9.11+ #2
[  363.506054] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  363.506059] insmod          D    0  2213   2212 0x00000000
[  363.506069]  ffff891c429926c0 0000000000000000 ffff891c545ac380 ffff891c3bd75a00
[  363.506077]  ffff891c5e399140 ffff9b974347fb48 ffffffff96cacd72 0000000000000000
[  363.506084]  0000000000000000 0000000000000246 0000000000000003 ffff891c3bd75a00
[  363.506091] Call Trace:
[  363.506107]  [<ffffffff96cacd72>] ? __schedule+0x232/0x6f0
[  363.506113]  [<ffffffff96cad266>] schedule+0x36/0x80
[  363.506119]  [<ffffffff96cb092a>] schedule_timeout+0x18a/0x310
[  363.506127]  [<ffffffff964f6030>] ? del_timer_sync+0x50/0x50
[  363.506138]  [<ffffffff96cae0ad>] wait_for_completion_timeout+0xad/0x140
[  363.506146]  [<ffffffff964b0400>] ? wake_up_q+0x70/0x70
[  363.506151]  [<ffffffffc0722000>] ? 0xffffffffc0722000
[  363.506293]  [<ffffffffc0c81be6>] hdd_hif_register_driver+0x56/0x110 [wlan]
[  363.506433]  [<ffffffffc0722127>] init_module+0x127/0x1f9 [wlan]
[  363.506444]  [<ffffffff96402190>] do_one_initcall+0x50/0x180
[  363.506451]  [<ffffffff965ead31>] ? __vunmap+0x81/0xd0
[  363.506457]  [<ffffffff9660a6a2>] ? kmem_cache_alloc_trace+0x152/0x1c0
[  363.506462]  [<ffffffff965eadee>] ? vfree+0x2e/0x70
[  363.506469]  [<ffffffff9659eafd>] do_init_module+0x5f/0x1dd
[  363.506476]  [<ffffffff96512742>] load_module+0x22b2/0x2880
[  363.506481]  [<ffffffff9650f4d0>] ? __symbol_put+0x60/0x60
[  363.506491]  [<ffffffff967bd0bd>] ? ima_post_read_file+0x7d/0xa0
[  363.506500]  [<ffffffff96776e8b>] ? security_kernel_post_read_file+0x6b/0x80
[  363.506507]  [<ffffffff96512f7f>] SYSC_finit_module+0xdf/0x110
[  363.506513]  [<ffffffff96512fce>] SyS_finit_module+0xe/0x10
[  363.506520]  [<ffffffff96cb1f3b>] entry_SYSCALL_64_fastpath+0x1e/0xad
[  365.554025] R0: wlan: [2213:E :HDD] hdd_hif_register_driver: 17762: hif registration timedout
[  365.554033] R0: wlan: [2213:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
lapdang@lapdang-ESPL:~/QCA9377.LEA.3.0_QDN_r3000017.1$ 
 
Do you have any idea? Thank you.
 
Regards,
Lap
  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Mon, 2020-08-03 05:57

Hi Lap,

It is a driver registration timeout issue when the driver tries to register itself to the SDIO Host Controller driver.

You can add some prints in the WLAN driver function hif_sdio_register_driver() and check the return of this call:

status = sdio_register_driver(&ar6k_driver);

You can further trace kernel code as to why the SDIO registration is failing. I don't see it as Qualcomm driver issue.

Thanks.

  • Up0
  • Down0
lap.dang
Join Date: 24 Oct 18
Posts: 14
Posted: Tue, 2020-08-25 21:21

Hi,

Thanks for your help. I had insmod Wlan successfully.

Now, I am trying to enable the Bluetooth:

I got to gap_menu -> enable but it fail.

=====

connecting to socket
hw_get_module_by_class: prop_name default path name bluetooth
hw_module_exists /usr/lib/libbluetoothdefault.so
loading the library /usr/lib/libbluetoothdefault.so
 
Wrong option selected
 
**************** Menu ******************
gap_menu
pan_menu
rsp_menu
test_menu
a2dp_sink_menu
hfp_client_menu
hid_menu
hfp_ag_menu
a2dp_source_menu
spp_server_menu
spp_client_menu
exit
******************************************
gap_menu
 
**************** Menu ******************
enable
disable
inquiry
cancel_inquiry
pair<space><bt_address> eg. pair 00:11:22:33:44:55
unpair<space><bt_address> eg. unpair 00:11:22:33:44:55
inquiry_list
bonded_list
get_state
get_bt_name
get_bt_address
set_bt_name<space><bt name> eg. set_bt_name MDM_Fluoride
main_menu
******************************************
enable
wcnssfilter: no process found
btsnoop: no process found
qcbtdaemon: no process found
current State = 0, new state = 1
Killing the proces due to timeout 1022
Killed
=====
Please help me some advice. Thanks
  • Up0
  • Down0
ddeepakk Moderator
Join Date: 27 Jun 17
Posts: 85
Posted: Tue, 2020-09-08 22:57

Hi Lap,

Thanks for creating new thread for the BT issue. Someone from BT Team will be supporting you soon.

Thanks.

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.