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.

WLAN0 interface not created on J6 Vayu EVM with DRA7xx GLSDK 6.04.00.02

Other Parts Discussed in Thread: WL1835

Hi,

I am not able to get the WLAN0 up on J6 EVM with DRA7xx GLSDK 6.04.00.02. The lsmod output is as follows:

root@dra7xx-evm:~# lsmod
Module Size Used by
wl18xx 93017 0
wlcore 187969 1 wl18xx
mac80211 632830 2 wl18xx,wlcore
cfg80211 509005 3 mac80211,wl18xx,wlcore
wlcore_sdio 4988 0
compat 7893 4 cfg80211,mac80211,wl18xx,wlcore_sdio
dwc3 43021 0
omap_usb3 4024 1
omap_usb2 4082 2
ahci_platform 4543 0
libahci 25786 1 ahci_platform
omapdrm_pvr 342237 0
dwc3_omap 4465 1 dwc3
extcon_gpio_usbvid 3647 0
 

Running ifup on the wlan0 interface gives an error:

root@dra7xx-evm:~# ifup wlan0
Successfully initialized wpa_supplicant
wlan0: Unsupported driver 'wext'
ifconfig: SIOCGIFFLAGS: No such device

Please let me know how to get the wlan0 interface up. 

Thanks,

Anurag Maheshwari

  • Hi,

    "ifup" would not be the right shell script to use. it seems like it is using wrong parameters for starting the supplicant. For example it uses -Dwext while it should use -Dnl80211

    Can you first just try:

    ifconfig wlan0 up

    iw wlan0 scan

    This would bring up the interface without the supplicant and perform a scan, just to see that the module is basically working.

    Next, you should use the following procedure for starting/connecting using the supplicant:

    http://processors.wiki.ti.com/index.php/Connect_to_Secure_AP_using_WPA_Supplicant

    Best Regards,

    Eyal Reizer

  • Hi Eyal,

    Since the wlan0 interface is not created, the ifconfig command fails:

    root@dra7xx-evm:~# ifconfig wlan0 up
    ifconfig: SIOCGIFFLAGS: No such device

    Here is the complete ifconfig output:

    root@dra7xx-evm:/etc/network# ifconfig
    eth0 Link encap:Ethernet HWaddr C4:ED:BA:C0:88:5A
    inet addr:192.168.39.20 Bcast:0.0.0.0 Mask:255.255.240.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:17577 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2209 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2454412 (2.3 MiB) TX bytes:301186 (294.1 KiB)
    Interrupt:82

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:32 errors:0 dropped:0 overruns:0 frame:0
    TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2240 (2.1 KiB) TX bytes:2240 (2.1 KiB)

    I have insmoded the wl18xx driver after bootup before executing the ifconfig command. Here is the lsmod output:

    root@dra7xx-evm:~# lsmod
    Module Size Used by
    wl18xx 93017 0
    wlcore 187969 1 wl18xx
    mac80211 632830 2 wl18xx,wlcore
    cfg80211 509005 3 mac80211,wl18xx,wlcore
    wlcore_sdio 4988 0
    compat 7893 4 cfg80211,mac80211,wl18xx,wlcore_sdio
    dwc3 43021 0
    omap_usb3 4024 1
    omap_usb2 4082 2
    ahci_platform 4543 0
    libahci 25786 1 ahci_platform
    omapdrm_pvr 342237 0
    dwc3_omap 4465 1 dwc3
    extcon_gpio_usbvid 3647 0

    Do I need to insmod any other module as well for the wlan0 interface to be created?

    Regards,

    Anurag Maheshwari

     

  • Hi Anurag,

    The module is probably not detected on the SDIO bus on boot as otherwise the modules would have been loaded automatically.

    Can you check on your J6-EVM the status of the userconfig switches (SW5)?. switch number 6 should be set to "On"  so it should look like "0010110000". If switch 6 is "off" then the COM8 module is not getting 32Khz clock and this may explain why it doesn't work for you.

    Best Regards,

    Eyal

  • Hi Eyal,

    The SW5 switch was set to "0001100000" on our EVM. I changed it to "0010110000"

     .

    But the wl18xx module still doesn't get loaded on its own. The rest of the behaviour remains the same and wlan0 is not created. 

    Regards,

    Anurag Maheshwari

  • Hi Anurag,

    Now the switch looks ok. Can you please paste the full kernel boot log followed by the output of "ifconfig -a"

    In addition, can you also paste a picture of the COM8 module mounted on the board and also make sure it is pushed in firmly.

    Best Regards,

    Eyal

  • Hi Eyal,

    The kernel boot logs are at: 1070.J6 kernel boot log.txt

    The ifconfig output is at: [View:http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/885/0167.ifconfig_2D00_a.txt]

    Here are the pictures of the COM module on the board. It does not seem detachable so I hope I am looking at the right one.

     

    Regards,

    Anurag Maheshwari

  • Hi Anurag,

     

    This explains it. It looks like you do not have the wilink8 com module. It is a small module that needs to plug into the connector you show in the picture. Where did you get the J6-EVM from? You would need to acquire a wilink8 module for it.

     

    Best Regards,

    Eyal

  • Hello,

    How would one bring up the wireless with insmod?  Would it be to first rmmod the wlcore_sdio and then insmod?

    rmmod wlcore_sdio

    insmod cfg80211.ko

    insmod mac80211.ko

    insmod wlcore.ko

    insmod wl18xx.ko

    insmod wlcore_sdio

    Thanks,

    David

  • Hi Eyal,

    We want to buy a Wifi Module for the J6 EVM which supports both 2.4GHz & 5GHz operation. We are also interested in testing the P2P/Wifi-Direct mode on this board. Can you recommend the right Wilink8 module and where to procure it from ? 

    Regards,

    Anurag Maheshwari

  • Hi Eyal,

    We now have the WL1835COM8Q module inserted into the COM8 connector. On booting up the board and insmoding the wl18xx driver we still do not see the wlan0 interface getting created. Bluetooth scan works by the way. 

    1. I am attaching the pictures of the board (and the dipswitch SW5 at "0010110000")  and the module. We see that there is a chip missing on the COM8Q PCB. Is this the right combo module which supports Wifi? 

    2. The following are the ifconfig and lsmod outputs:

    root@dra7xx-evm:~# ifconfig -a

    can0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  

              NOARP  MTU:16  Metric:1

              RX packets:0 errors:0 dropped:0 overruns:0 frame:0

              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:10 

              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

              Interrupt:113 

     

    can1      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  

              NOARP  MTU:16  Metric:1

              RX packets:0 errors:0 dropped:0 overruns:0 frame:0

              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:10 

              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

              Interrupt:114 

     

    eth0      Link encap:Ethernet  HWaddr C4:ED:BA:C0:88:5A  

              inet addr:192.168.39.61  Bcast:0.0.0.0  Mask:255.255.240.0

              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

              RX packets:1703 errors:0 dropped:0 overruns:0 frame:0

              TX packets:3 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:1000 

              RX bytes:265179 (258.9 KiB)  TX bytes:716 (716.0 B)

              Interrupt:82 

     

    eth1      Link encap:Ethernet  HWaddr C4:ED:BA:C0:88:5B  

              BROADCAST MULTICAST  MTU:1500  Metric:1

              RX packets:0 errors:0 dropped:0 overruns:0 frame:0

              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:1000 

              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

     

    lo        Link encap:Local Loopback  

              inet addr:127.0.0.1  Mask:255.0.0.0

              UP LOOPBACK RUNNING  MTU:65536  Metric:1

              RX packets:32 errors:0 dropped:0 overruns:0 frame:0

              TX packets:32 errors:0 dropped:0 overruns:0 carrier:0

              collisions:0 txqueuelen:0 

              RX bytes:2240 (2.1 KiB)  TX bytes:2240 (2.1 KiB)

    root@dra7xx-evm:~# lsmod

    Module                  Size  Used by

    wl18xx                 93017  0 

    wlcore                187969  1 wl18xx

    mac80211              632830  2 wl18xx,wlcore

    cfg80211              509005  3 mac80211,wl18xx,wlcore

    dwc3                   43021  0 

    omap_usb3               4024  1 

    omap_usb2               4082  2 

    ahci_platform           4543  0 

    libahci                25786  1 ahci_platform

    omapdrm_pvr           342237  0 

    wlcore_sdio             4988  0 

    compat                  7893  4 cfg80211,mac80211,wl18xx,wlcore_sdio

    dwc3_omap               4465  1 dwc3

    extcon_gpio_usbvid      3647  0 

    Regards,

    Anurag Maheshwari

  • Hi,

    We have a particular DRA7xx ES1.0 Rev-E1 board where the Wi-Fi interface (wlan0) does not get created (We have a WL8Q module). We are booting up using GLSDK 6.04 image. Please see the photo below: 

    With the same uSD card, Wi-Fi interface is created and works fine on another DRA7xx ES1.0 Rev-E1 board that we have so it seems like a board specific issue.

    Please let me know how to debug this board.

    Regards,

    Anurag Maheshwari

  • Can you please double check the SW5 switches as below?

    Especially pay attention to SW5-6 It has to be "ON" otherwise wilink8 is not getting a clock it needs.

     

    DIP Switch settings

    Required DIP switch settings: This configuration corresponds to the following device boot order: SD ⇒ QSPI_1

    SYSBOOT [0-15]

    OFF ON ON OFF OFF OFF OFF OFF    ON OFF OFF OFF OFF OFF OFF OFF ON

     

    USERCONFIG [SW5]

    OFF OFF ON OFF ON ON ON OFF OFF OFF

     

    Best Regards,

    Eyal

     

  • Hi Eyal,

    I have checked both SW5 and SYSBOOT settings.

    1. SW5-6 was already ON.

    2. SW5-7 was OFF and I made it ON. 

    3. SYSBOOT-0 was ON and I made it OFF 

    There is no change in behaviour after booting up with these changes 

    root@dra7xx-evm:~# lsmod
    Module Size Used by
    wlcore_sdio 4988 0
    wl18xx 93017 0
    wlcore 187969 1 wl18xx
    mac80211 632830 2 wl18xx,wlcore
    cfg80211 509005 3 mac80211,wl18xx,wlcore
    compat 7893 4 cfg80211,mac80211,wl18xx,wlcore_sdio

    root@dra7xx-evm:~# ifconfig wlan0
    ifconfig: wlan0: error fetching interface information: Device not found
    root@dra7xx-evm:~#

    What else can I check on this board ? 

    Regards,

    Anurag Maheshwari

  • Hello,

    What is the output of "ifconfig -a"?

    Perhaps the interface is named wlan1 and not wlan0?

    If there is no wlan interface at all, please send the output from kernel boot.

    You should see a message like"new SDIO .... at address 0001" if the module is detected.

    Best Regards,

    Eyal

  • root@dra7xx-evm:~# ifconfig -a
    can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:16 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:10
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:113

    can1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:16 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:10
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:114

    eth0 Link encap:Ethernet HWaddr 20:CD:39:2D:39:7E
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:82

    eth0:avahi Link encap:Ethernet HWaddr 20:CD:39:2D:39:7E
    inet addr:169.254.6.33 Bcast:169.254.255.255 Mask:255.255.0.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    Interrupt:82

    eth1 Link encap:Ethernet HWaddr 20:CD:39:2D:39:7F
    BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:32 errors:0 dropped:0 overruns:0 frame:0
    TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2240 (2.1 KiB) TX bytes:2240 (2.1 KiB)

    I have also attached the kernel boot logs. Doesn't look like the WL8Q is being detected.

    2860.kernel.log