• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 1487 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.

Linux: WL1831 - Beacon loss and reconnect every hour

mans.andersson
Intellectual 540 points
Other Parts Discussed in Thread: WL1831

Tool/software: Linux

So, I have a curious little problem which I'm not sure if it's related to WL1831 or not. It seems that every hour the wifi chip is experiencing beacon losses which disconnects the device from the current network and then reconnects it. We have not been able to relate it to any other device within the network (the minute changes between restarts). Has someone else experienced anything similar or have an idea of what could create such an issue?

See output from syslog below.

BR,

Måns

Jun 21 02:21:15 my-board user.info kernel: [38854.140602] wlcore: Beacon loss detected. roles:0x1
Jun 21 02:21:20 my-board user.info kernel: [38859.022103] wlcore: Connection loss work (role_id: 0).
Jun 21 02:21:20 my-board user.info kernel: [38859.033907] wlan0: Connection to AP c4:ea:1d:e4:9e:97 lost
Jun 21 02:21:20 my-board daemon.info connmand[653]: wlan0 {RX} 27664 packets 4957027 bytes
Jun 21 02:21:20 my-board daemon.info connmand[653]: wlan0 {TX} 3744 packets 654225 bytes
Jun 21 02:21:20 my-board daemon.info connmand[653]: wlan0 {update} flags 36867 <UP>
Jun 21 02:21:20 my-board daemon.info connmand[653]: wlan0 {newlink} index 4 address 88:C2:55:2C:C2:31 mtu 1500
Jun 21 02:21:20 my-board daemon.info connmand[653]: wlan0 {newlink} index 4 operstate 2 <DOWN>
Jun 21 02:21:20 my-board daemon.err connmand[653]: Time request for server 192.168.1.1 failed (101/Network is unreachable)
Jun 21 02:21:20 my-board daemon.err connmand[653]: Time request for server 192.168.1.1 failed (101/Network is unreachable)
Jun 21 02:21:20 my-board user.info kernel: [38859.143024] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 21 02:21:20 my-board daemon.info connmand[653]: wlan0 {del} address 192.168.1.102/24 label wlan0
Jun 21 02:21:20 my-board daemon.info connmand[653]: wlan0 {del} route 192.168.1.0 gw 0.0.0.0 scope 253 <LINK>
Jun 21 02:21:20 my-board daemon.info connmand[653]: wlan0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Jun 21 02:21:21 my-board daemon.warn connmand[653]: Skipping disconnect of 4672656a6131_managed_psk, network is connecting.
Jun 21 02:21:21 my-board user.info kernel: [38859.996002] wlan0: authenticate with c4:ea:1d:e4:9e:97
Jun 21 02:21:21 my-board user.info kernel: [38860.028192] wlan0: send auth to c4:ea:1d:e4:9e:97 (try 1/3)
Jun 21 02:21:21 my-board user.info kernel: [38860.051718] wlan0: authenticated
Jun 21 02:21:21 my-board user.info kernel: [38860.072153] wlan0: associate with c4:ea:1d:e4:9e:97 (try 1/3)
Jun 21 02:21:21 my-board user.info kernel: [38860.108663] wlan0: RX AssocResp from c4:ea:1d:e4:9e:97 (capab=0x1411 status=0 aid=2)
Jun 21 02:21:21 my-board user.info kernel: [38860.223725] wlan0: associated
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {RX} 27665 packets 4957140 bytes
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {TX} 3744 packets 654225 bytes
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {update} flags 102403 <UP,LOWER_UP>
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {newlink} index 4 address 88:C2:55:2C:C2:31 mtu 1500
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {newlink} index 4 operstate 5 <DORMANT>
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Jun 21 02:21:21 my-board user.info kernel: [38860.272287] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {RX} 27666 packets 4957309 bytes
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {TX} 3746 packets 654513 bytes
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {newlink} index 4 address 88:C2:55:2C:C2:31 mtu 1500
Jun 21 02:21:21 my-board daemon.info connmand[653]: wlan0 {newlink} index 4 operstate 6 <UP>
Jun 21 02:21:22 my-board user.info kernel: [38860.444087] wlcore: Association completed.
Jun 21 02:21:22 my-board daemon.info connmand[653]: Setting hostname to my-board
Jun 21 02:21:22 my-board daemon.info connmand[653]: Setting domainname to lan
Jun 21 02:21:22 my-board daemon.info connmand[653]: wlan0 {add} address 192.168.1.102/24 label wlan0 family 2
Jun 21 02:21:22 my-board daemon.info connmand[653]: wlan0 {add} route 192.168.1.0 gw 0.0.0.0 scope 253 <LINK>
Jun 21 02:21:22 my-board daemon.info connmand[653]: wlan0 {add} route 192.168.1.1 gw 0.0.0.0 scope 253 <LINK>
Jun 21 02:21:22 my-board daemon.info connmand[653]: wlan0 {add} route 0.0.0.0 gw 192.168.1.1 scope 0 <UNIVERSE>
Jun 21 02:21:22 my-board daemon.info connmand[653]: ntp: time slew +0.072574 s
Jun 21 02:21:22 my-board daemon.info connmand[653]: wlan0 {add} route 212.227.81.55 gw 192.168.1.1 scope 0 <UNIVERSE>
Jun 21 02:21:22 my-board daemon.info connmand[653]: wlan0 {del} route 212.227.81.55 gw 192.168.1.1 scope 0 <UNIVERSE>
Jun 21 02:21:22 my-board daemon.info connmand[653]: ntp: time slew -0.003862 s

  • 0
    TI__Mastermind 20285 points
    Hello,

    How have you configured your wl18xx-conf.bin file?
    Did you use wlconf with the configure-device.sh script and selected wl1831 as your device?
    www.ti.com/.../swra489.pdf
    See section 2.

    You might have wrong configuration of the number of connected antennas etc. which can lead to issues like this one.

    Best Regards,
    Eyal
  • 0 in reply to Eyal Reizer
    TI__Mastermind 20285 points
    Hi,

    Any update on this thread?
    Should we keep it open?

    Best Regards,
    Eyal
  • 0 in reply to Eyal Reizer
    Intellectual 540 points

    I've been investigating your latest suggestion with the configuration of the device. We have configured it using the wlconf utility and as an input we've used the ini file provided by our module manufacturer MuRata. We have verified with them that we're using the latest version of that ini file (WL8_INI_1ANT_muRata_20130618.ini).

    The configuration file is not the easiest to read so I can't tell if everythings correct within it but from what I can see it's configured with two antennas, one 2.4GHz and one 5GHz. The WL1831 only supports 2.4GHz though so I'm guessing that could be our issue. Would it work to just change the following two rows or do I need to make other adjustments in the configuration file as well?

    NumberOfAssembledAnt2_4     	= 01 # Indicates the active bands and the number of mounted antennas for 2.4GHz;  
NumberOfAssembledAnt5       	= 01 # Indicates the active bands and the number of mounted antennas for 5GHz;

  • 0 in reply to mans.andersson
    TI__Mastermind 20285 points
    Hi,

    In case you are using a wl1831 device you should actually put "0" for the number of "NumberOfAssembledAnt5".
    Is suggest you use wlconf and get a dump of your actual wl18xx-conf.bin file that was created using the supplied .ini file and make sure the values are indeed correct.

    ./wlconf -i /lib/firmware/ti-connectivity/wl18xx-conf.bin --get >dump.txt

    Best Regards,
    Eyal
  • 0 in reply to Eyal Reizer
    Intellectual 540 points

    Thanks Eyal for your answer.

    We haven't tried your suggested change yet due to us waiting for a reply from our module manufacturer MuRata regarding their ini file. We're thinking we've got the wrong one from them and would like to clarify that first. If it's not the wrong one then it could possibly have other errors as well, thinking the number of antennans would be the easy thing to configure and they didn't get that right... We need to have that under control before continuing due to the possible problems it could cause us during our certification process.

    Please leave the conversation open for now and I'll get back with more details whenever I have some.

  • 0 in reply to mans.andersson
    TI__Mastermind 20285 points
    Hi,

    I will close this thread for now as it is pending for too long.
    Please open a new one if needed.

    Best Regards,
    Eyal