Omega2S - WiFi not working



  • Hi.
    I have a problem with wifi on my Omega2S board. I've successfully got 2 boards up and running, but the third one, when I connected it for the first time, I noticed I couldn't find Omega access point to connect to. Therefore I connected it to serial port to see what is going on.

    When I ran wifisetup and try to scan Wifi networks, I got an error: Scan Failed, try again. And then it seems the wifi driver just reset.

    root@Omega-80F3:/# wifisetup
    Onion Omega Wifi Setup
    
    Select from the following:
    1) Scan for Wifi networks
    2) Type network info
    q) Exit
    
    Selection: 1
    Scanning for wifi networks...
    > ERROR: Scan failed, try again
    
    > ERROR: specified ssid not in the database
    root@Omega-80F3:/# [  245.730908] br-wlan: port 1(ra0) entered disabled state
    [  246.398478] device ra0 left promiscuous mode
    [  246.402932] br-wlan: port 1(ra0) entered disabled state
    [  246.457492] IPv6: ADDRCONF(NETDEV_UP): br-wlan: link is not ready
    [  246.819311]
    [  246.819311] _      _____   ___  ___    _________  ___  ____
    [  246.819311] | | /| / / _ | / _ \/ _ \  / ___/ __ \/ _ \/ __/ V1.0
    [  246.819311] | |/ |/ / __ |/ , _/ ___/ / /__/ /_/ / , _/ _/
    [  246.819311] |__/|__/_/ |_/_/|_/_/     \___/\____/_/|_/___/
    [  246.819311]             Onion Enhanced MT7688 WiFi Driver
    [  246.819311]
    [  246.986960] DMA Scheduler Mode=0(LMAC)
    [  246.990795] efuse_probe: efuse = 10000012
    [  246.994920] 1. Phy Mode = 14
    [  247.181818] 2. Phy Mode = 14
    [  247.184794] 3. Phy Mode = 14
    [  247.188288]  WTBL Segment 1 info:
    [  247.191654]          MemBaseAddr/FID:0x28000/0
    [  247.195558]          EntrySize/Cnt:32/128
    [  247.199075]  WTBL Segment 2 info:
    [  247.202440]          MemBaseAddr/FID:0x40000/0
    [  247.206345]          EntrySize/Cnt:64/128
    [  247.209790]  WTBL Segment 3 info:
    [  247.213149]          MemBaseAddr/FID:0x42000/64
    [  247.217138]          EntrySize/Cnt:64/128
    [  247.220585]  WTBL Segment 4 info:
    [  247.223945]          MemBaseAddr/FID:0x44000/128
    [  247.228021]          EntrySize/Cnt:32/128
    [  255.048594] device ra0 entered promiscuous mode
    [  255.053340] br-wlan: port 1(ra0) entered forwarding state
    [  255.058926] br-wlan: port 1(ra0) entered forwarding state
    [  255.065977] IPv6: ADDRCONF(NETDEV_CHANGE): br-wlan: link becomes ready
    [  257.055693] br-wlan: port 1(ra0) entered forwarding state
    

    Then I read there could be problem with firmware, so I loaded lastest Omega image to usb and hook it to the board. I performed the update, but wifi still doesnt work.

    root@Omega-80F3:/# wifisetup
    Onion Omega Wifi Setup
    
    Select from the following:
    1) Scan for Wifi networks
    2) Type network info
    q) Exit
    
    Selection: 1
    Scanning for wifi networks...
    > ERROR: Scan failed, try again
    
    > ERROR: specified ssid not in the database
    root@Omega-80F3:/# [  114.002972] br-wlan: port 1(ra0) entered disabled state
    [  114.021346] device ra0 left promiscuous mode
    [  114.025856] br-wlan: port 1(ra0) entered disabled state
    [  114.065930] IPv6: ADDRCONF(NETDEV_UP): br-wlan: link is not ready
    [  114.878368] device ra0 entered promiscuous mode
    [  115.004451] br-wlan: port 1(ra0) entered forwarding state
    [  115.009977] br-wlan: port 1(ra0) entered forwarding state
    [  115.022620] IPv6: ADDRCONF(NETDEV_CHANGE): br-wlan: link becomes ready
    [  117.004291] br-wlan: port 1(ra0) entered forwarding state
    

    I don't know what could couse this behaviour.

    Here is some dmesg from startup:

    [   25.577922]
    [   25.577922] _      _____   ___  ___    _________  ___  ____
    [   25.577922] | | /| / / _ | / _ \/ _ \  / ___/ __ \/ _ \/ __/ V1.0
    [   25.577922] | |/ |/ / __ |/ , _/ ___/ / /__/ /_/ / , _/ _/
    [   25.577922] |__/|__/_/ |_/_/|_/_/     \___/\____/_/|_/___/
    [   25.577922]             Onion Enhanced MT7688 WiFi Driver
    [   25.577922]
    [   25.928211] DMA Scheduler Mode=0(LMAC)
    [   25.932046] efuse_probe: efuse = 10000012
    [   25.936219] 1. Phy Mode = 14
    [   26.131293] 2. Phy Mode = 14
    [   26.134344] 3. Phy Mode = 14
    [   26.145357]  WTBL Segment 1 info:
    [   26.148737]          MemBaseAddr/FID:0x28000/0
    [   26.152624]          EntrySize/Cnt:32/128
    [   26.156123]  WTBL Segment 2 info:
    [   26.159483]          MemBaseAddr/FID:0x40000/0
    [   26.163368]          EntrySize/Cnt:64/128
    [   26.166825]  WTBL Segment 3 info:
    [   26.170185]          MemBaseAddr/FID:0x42000/64
    [   26.174157]          EntrySize/Cnt:64/128
    [   26.177615]  WTBL Segment 4 info:
    [   26.180975]          MemBaseAddr/FID:0x44000/128
    [   26.185051]          EntrySize/Cnt:32/128
    [   33.467718] device ra0 entered promiscuous mode
    [   33.472458] br-wlan: port 1(ra0) entered forwarding state
    [   33.478048] br-wlan: port 1(ra0) entered forwarding state
    [   33.484852] IPv6: ADDRCONF(NETDEV_CHANGE): br-wlan: link becomes ready
    [   35.474303] br-wlan: port 1(ra0) entered forwarding state
    [   40.810360] device ra0 left promiscuous mode
    [   40.815004] br-wlan: port 1(ra0) entered disabled state
    [   41.329955] IPv6: ADDRCONF(NETDEV_UP): br-wlan: link is not ready
    [   42.754153] device ra0 entered promiscuous mode
    [   42.844328] br-wlan: port 1(ra0) entered forwarding state
    [   42.849886] br-wlan: port 1(ra0) entered forwarding state
    [   42.871965] IPv6: ADDRCONF(NETDEV_CHANGE): br-wlan: link becomes ready
    [   44.844284] br-wlan: port 1(ra0) entered forwarding state
    [   54.088901] random: nonblocking pool is initialized 
    

    After FW update, version is as following:

    Onion Omega2 UBoot Version: 4.3.0.3
    Image Name: MIPS LEDE Linux-4.4.74
    Board: Onion Omega2 APSoC DRAM: 64 MB
    ?-ware: 0.2.2 b201

    I have noticed also this:

    find flash: W25Q128BV
    *** Warning - bad CRC, using default environment
    

    How to solve this issue with wifi?



  • @opti-gregor

    Board: Onion Omega2 APSoC DRAM: 64 MB

    I don't have any Omega2S', so this may not be relevant at all, but that line looks like it belongs to an Omega2 (64MB).

    Did you perhaps flash with the O2 firmware by mistake?



  • Well after initial wifi failure I updated firmware from http://repo.onion.io/omega2/images/

    So it is O2 image. I don't know if there is any separate repository for O2S. If there is, please let me know.

    EDIT: I found this on this forum: "Actually, Omega2S's firmware is the same as for the Omega2 and Omega2S+ has the same firmware as Omega2S+."



  • @opti-gregor

    I found this on this forum: "Actually, Omega2S's firmware is the same as for the Omega2 and Omega2S+ has the same firmware as Omega2S+."

    Aah, ok.



  • @opti-gregor Yes, there isn't separate firmware repository for Omega2S(+).
    I wanted to suggest a Factory Reset and / or a firmware reflash but you have already done it.
    Unfortunately I don't have any Omega2S(+) - so I guess.
    One of earlier versions of the Warp Core WiFi driver has some wifisetup problem if there are two "identical" Omega2(+) APs (Omega-ABCD, 192.168.3.1, 12345678 and Omega-WXYZ, 192.168.3.1, 12345678) on the same network. Maybe???
    I don't know the current situation.


    About that U-Boot message:
    0_1545387532658_U-boot bad CRC warning.png
    This is not related to your WiFi issue.
    Does it bother you? It can be corrected quite easily.



  • Well have updated firmware with this procedure: https://docs.onion.io/omega2-docs/manual-firmware-installation.html
    So I copied last version of FW to usb and then connect usb with O2S and copy FW to /tmp/ and then I ran sysupgrade<FIRMWARE FILE NAME>

    I have also tried to install firmware by pressing Reset button and then selecting option 2, but I was unsucessfull, as once it showed

    ERROR: CTL:TIMEOUT X
    BBB_reset
    usb_control_msg: request: 0xFF, requesttype: 0x21
    value 0x0 index 0x0 length 0x0
    

    and other time it started to do an infinite loop with messages

    ------------[ cut here ]------------
    


  • @opti-gregor OK. Presumably there is one (1) Omega2S on your WiFi network - only the problematic one.
    If I were you I would try on the Serial Console:

    1. run these commands (ie. Factory Reset)
      firstboot -y
      reboot
      ...
      wifisetup

    2. the wget http://repo.onion.io.s3.amazonaws.com/omega2/images/omega2-v0.2.2-b201.bin command does not work so I copy the b201 firmware into the /tmp directory somehow and check it
      This is its MD5 hash: c3d57622dd176bd27ae7f6719eea5f1a
      cd /tmp
      ls -l omega2-v0.2.2-b201.bin
      -rw-r--r-- 1 root root 7864492 Dec 3 23:57 omega2-v0.2.2-b201.bin
      md5sum omega2-v0.2.2-b201.bin
      c3d57622dd176bd27ae7f6719eea5f1a omega2-v0.2.2-b201.bin
      sysupgrade omega2-v0.2.2-b201.bin
      ...
      wifisetup


    BTW
    Do you have a genuine Onion Omega2S Development Kit and try your devices one after another?

    Or do you have some custom solution for each device?
    Q: Is there any short circuit at the ANT pin? ;-)

    Sorry I have no more idea.
    Good luck!



  • I have tried firstboot -y procedure before but there was no difference. Only thing I didn't checked is md5 value. There are also other Omega2S running in the roorm, but I didn't managed even to put this fault one to connect to network and AP wasn't working anyway. Other omegas also have different host names and I have disabled AP on them so they are only connected to router.

    Anyhow I have now somehow managed to unsolder Omega2S and put new one there. The new one is now working perfectly.

    So to answer your questions, I use custom PCB where O2S had been soldered on, and as I have checked I haven't noticed any short.



  • @opti-gregor said in Omega2S - WiFi not working:

    There are also other Omega2S running in the room, but I didn't managed even to put this fault one to connect to network and AP wasn't working anyway.

    Each WiFi AP should has different hostname SSID and different IP - for example:
    Omega-ABCD, 192.168.3.1 and Omega-WXYZ, 192.168.5.1

    Other omegas also have different host names and I have disabled AP on them so they are only connected to router.

    I'm afraid it is not possible with disabled AP on Omega2:
    no WiFi AP = no WiFi Station (Client) = no WiFi connection to the router (I think ;-)



  • @György-Farkas said in Omega2S - WiFi not working:

    I'm afraid it is not possible with disabled AP on Omega2:

    It is possible, because I'm already sucessfuly doing it and it keeps WifiClient on.

    ifconfig ra0 down and ifconfig ra0 up to disable and enable AP.

    I guess there was something wrong internaly in my Omega2S.



  • @opti-gregor said in Omega2S - WiFi not working:

    @György-Farkas said in Omega2S - WiFi not working:

    I'm afraid it is not possible with disabled AP on Omega2:

    It is possible, because I'm already sucessfuly doing it and it keeps WifiClient on.

    ifconfig ra0 down and ifconfig ra0 up to disable and enable AP.

    Good catch! Congratulation on your success! :-)
    I reproduced / confirmed it also on an Omega2+ v0.2.2 b201 successfully.
    I think your hack puts Omega2's WiFi subsystem some kind of "in-between" "intermediate" state because this state - unfortunately - can not survive the usual /etc/init.d/network restart command.

    The main thing is that it's working fine now ... but one should check the details. As you know - the Devil is in the details. ;-)

    Good luck!



  • I now stumbled upon similar case, if not the same with another board. I was able to connect access point of Omega2S and open putty to run commands. After I have run command wifisetup and select option 1, link with omega broke, and I think it also rebooted. I'm not sure about all circumstances, as I didn't connect via serial port.

    Then I made conection with O2S again and check ifconfig.

    I noticed that there is suspecious eth0.1 interface. So I decided to run command ifconfig eth0.1 down to disable that interface.
    Then I tried to run wifisetup and this time it was succesful! I managed to finish instalation of all needed software and it works like a charm.

    I can't check if it's the same with one that I had problems with, as it is not on it's board anymore, but for this one it worked.


Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.