• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 41 subscribers
  • Views 1116 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Wl18xx problem when enable Bluetooth and Wifi with R8.4 driver

Tuan_Nguyen
Intellectual 680 points

Hi,

It will be OK if I just enable only Wifi but when I enabled Bluetooth, I got that message:

root@OpenWrt:/# udhcpc -i wlan0
udhcpc (v1.22.1) started
Sending discover...
[   56.999291] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[   57.006711] ------------[ cut here ]------------
[   57.011652] WARNING: CPU: 0 PID: 901 at drivers/net/wireless/ti/wlcore/main.c:801 wl1271_op_add_interface+0x88c/0x8c0 [wlcore]()
[   57.023806] Modules linked in: btwilink bluetooth 6lowpan_iphc pppoe ppp_async iptable_nat wl18xx pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 krng ipt_MASQUERADE chainiv xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT wlcore_sdio wlcore slhc rng nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_irc nf_conntrack_ftp nf_conntrack mac80211 iptable_raw iptable_mangle iptable_filter ipt_REJECT ip_tables ctr crypto_wq crc_itu_t crc_ccitt cfg80211 ccm aead ip6t_REJECT ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ipv6 arc4 crypto_blkcipher usbcore usb_common
[   57.089247] CPU: 0 PID: 901 Comm: irq/171-wl18xx Not tainted 3.14.18 #1
[   57.096183] Backtrace: 
[   57.098794] [<c001bea0>] (dump_backtrace) from [<c001c184>] (show_stack+0x18/0x1c)
[   57.106732]  r6:bf196480 r5:00000000 r4:c053ad80 r3:00000000
[   57.112721] [<c001c16c>] (show_stack) from [<c01aab5c>] (dump_stack+0x88/0x98)
[   57.120319] [<c01aaad4>] (dump_stack) from [<c0040ad4>] (warn_slowpath_common+0x78/0x94)
[   57.128819]  r5:00000009 r4:00000000
[   57.132581] [<c0040a5c>] (warn_slowpath_common) from [<c0040b94>] (warn_slowpath_null+0x24/0x2c)
[   57.141809]  r8:df5496d8 r7:df549538 r6:df549550 r5:df549520 r4:df549500
[   57.148893] [<c0040b70>] (warn_slowpath_null) from [<bf196480>] (wl1271_op_add_interface+0x88c/0x8c0 [wlcore])
[   57.159421] [<bf196454>] (wl1271_op_add_interface [wlcore]) from [<bf1966d0>] (wlcore_irq+0xf8/0x540 [wlcore])
[   57.169926]  r4:df549500 r3:00000002
[   57.173705] [<bf1965d8>] (wlcore_irq [wlcore]) from [<c007cfdc>] (irq_thread_fn+0x24/0x48)
[   57.182387]  r9:df55df80 r8:df0e4540 r7:00000001 r6:00000000 r5:df0e4540 r4:df55df80
[   57.190556] [<c007cfb8>] (irq_thread_fn) from [<c007d2bc>] (irq_thread+0xd0/0x17c)
[   57.198515]  r6:00000000 r5:df430000 r4:df55dfa0 r3:00000004
[   57.204484] [<c007d1ec>] (irq_thread) from [<c005c3c0>] (kthread+0xf0/0xf4)
[   57.211798]  r10:00000000 r9:00000000 r8:00000000 r7:c007d1ec r6:df55df80 r5:00000000
[   57.220050]  r4:df55df40
[   57.222716] [<c005c2d0>] (kthread) from [<c0008e58>] (ret_from_fork+0x14/0x3c)
[   57.230303]  r7:00000000 r6:00000000 r5:c005c2d0 r4:df55df40
[   57.236257] ---[ end trace 47bca053c8fa5fa8 ]---
[   57.242237] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.17
[   57.249915] wlcore: pc: 0x12798, hint_sts: 0x00000000 count: 1
[   57.256272] wlcore: down
[   57.260201] ieee80211 phy0: Hardware restart was requested
[   57.683940] wlcore: PHY firmware version: Rev 8.2.0.0.212
[   57.780347] wlcore: firmware booted (Rev 8.9.0.0.17)
[   57.802928] wlcore: Association completed.
Sending discover...
Sending select for 192.168.168.117...
Lease of 192.168.168.117 obtained, lease time 604800
udhcpc: ifconfig wlan0 192.168.168.117 netmask 255.255.255.0 broadcast 192.168.168.255
udhcpc: setting default routers: 192.168.168.1

My kernel is 3.14.8, and I tried to patch the "compat-wireless" (R8.4 release) to my kernel, maybe I missed or wrong in somewhere.

Thanks

Tuan Nguyen

  • 0
    TI__Guru* 85400 points

    Hi Tuan,

    Can you please advise on the below?

    1. Which platform is being used
    2. Which BT Stack is used?
    3. Which BT Script file (.bts) are you downloading?

    Also, please share the complete boot logs which includes the exact commands that you are executing.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Intellectual 680 points

    Hi Joseph,

    I am using BT firmware version: TIInit_11.8.32.bts with Beaglebone black, control by bluez.

    Here is my log:

    4774.wl18xx-blue.log

    Thanks

    Tuan Nguyen

  • 0 in reply to Tuan_Nguyen
    TI__Guru* 85400 points

    Hi Tuan,

    Is it possible to get a WLAN FW log for this case? 
    To get fw logs:

    ***

    Device Configuration

    First time only:

    Wlconf configuration:

    Set SDIO as an output:
    wlconf -i /etc/firmware/ti-connectivity/wl18xx-conf.bin -o /etc/firmware/ti-connectivity/wl18xx-conf.bin –set       core.fwlog.output=0x02

    (Optional)Update num of FW‘s memblocks allocate for logger :
    wlconf -i /etc/firmware/ti-connectivity/wl18xx-conf.bin -o /etc/firmware/ti-connectivity/wl18xx-conf.bin –set core.fwlog.mem_blocks=0x03

    (Optional)Validate Configuration:
    wlconf -i /etc/firmware/ti-connectivity/wl18xx-conf.bin –g

    wl_logproxy daemon:


    Copy “wl_logproxy” to /system/bin and chmod it.

    Link to source code:
    https://github.com/TI-OpenLink/18xx-ti-utils/blob/mc_internal/wl_logproxy.c


    mkdir /data/misc/wifi/fwlogs

    Update the insmod of the wlcore module to:
    insmod /system/lib/modules/wlcore.ko fwlog=continuous

    reboot device.

    Every time after reboot:

    Activate the logger:


    Prior to WLAN-ON:

    /system/bin/wl_logproxy 1555 /sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc2/mmc2:0001/mmc2:0001:2/wl18xx/fwlog /data/misc/wifi/fwlogs/ 10000000 &
    If not a TI standard platform , you might need to look for fwlogs/ location

    ***


    Regards,
    Gigi Joseph.



  • 0
    Expert 1985 points
    Hi Tuan,

    I am also facing the same issue with wifi enabled randomly and in i.MX platform. Are you able to find out the cause for this issue?. I really appreciate if you could share any info.


    Thanks,
    Ijaz Fazily