Create Account
Search
You are here: TDG Forum  >>  Board Support Packages (BSP)  >>  Linux  >>  Receiving corrupted packets from wifi.

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 03 Sep 2015 11:20 AM by  jduran.gm
Receiving corrupted packets from wifi.
 39 Replies
Sort:
You are not authorized to post a reply.
Page 1 of 212 > >>
Author Messages
jduran.gm
New Member
New Member
Posts:79


--
10 Jul 2015 06:10 AM

    Hello,

    On a Torpedo wireless module updated to BSP 2.4-3, we've discovered that packages are lost because they were corrupted:

    Jan  1 00:52:56 DM-37x user.warn kernel: [ 3179.250488] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:56 DM-37x user.warn kernel: [ 3179.252899] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:56 DM-37x user.warn kernel: [ 3179.253845] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3179.463684] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3178.89] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3179.555358] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3179.544525] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3179.556549] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3179.949981] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3179.54537in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3179.957336] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:57 DM-37x user.warn kernel: [ 3179.958557] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:58 DM-37x user.warn kernel: [ 3180.576568] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:52:59 DM-37x user.warn kernel: [ 3181.395233] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:53:00 DM-37x user.warn kernel: [ 3183.124176] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:53:01 DM-37x user.warn kernel: [ 3179.953430] wl1283: WARNING corrupted packet 50] wl1283: WARNING corrupted packet in RX with status: 0x1


    Jan  1 00:53:02 DM-37x user.warn kernel: [ 3184.672241] wl1283: WARNING corrupted packet in RX with status: 0x1


    [...]

    Jan  1 01:01:21 DM-37x user.debug kernel: [ 3683.730407] wlan0: Connection to AP 48:5b:39:e7:63:0f lost.
    Jan  1 01:01:21 DM-37x user.info kernel: [ 3683.870269] cfg80211: Calling CRDA to update world regulatory domain
    Jan  1 01:01:23 DM-37x user.debug kernel: [ 3685.792114] wlan0: authenticate with 48:5b:39:e7:63:0f (try 1)
    Jan  1 01:01:23 DM-37x user.debug kernel: [ 3685.986999] wlan0: authenticate with 48:5b:39:e7:63:0f (try 2)
    Jan  1 01:01:23 DM-37x user.warn kernel: [ 3183.8744<7>[ 3685.996948] wlan0: authenticated
    Jan  1 01:01:23 DM-37x user.debug kernel: [ 3686.042175] wlan0: associate with 48:5b:39:e7:63:0f (try 1)
    Jan  1 01:01:23 DM-37x user.debug kernel: [ 3686.048706] wlan0: RX AssocResp from 48:5b:39:e7:63:0f (capab=0x411 status=0 aid=3)
    Jan  1 01:01:23 DM-37x user.debug kernel: [ 3686.048767] wlan0: associated
    Jan  1 01:01:23 DM-37x user.info kernel: [ 3686.165924] wl1283: Association completed.


    To reproduce them on the Torpedo module, open a session on the console interface, and follow the steps:

    1 - Start syslogd

    /etc/rc.d/init.d/syslog start

    2 - Disable eth0, to 

    ifconfig eth0 down

    2 - Configure wpa_supplicant to connect to an AP based on WPA2 / tkip:

    network={
            ssid="SSID"
            psk="PASSKEY"
            key_mgmt=WPA-PSK
            pairwise=TKIP
    }


    3 - Indicate to wpa_supplicant to connect to AP

    4 - Start the dhcp client to wlan0.

    5 - Create the download.sh script with the contents:

     

    #!/bin/sh



    while [ "1" -eq "1" ];


    do


    tftp -r uImage -g


    sleep 1


    done


    6 - Set execution permissions to script

    7 - Run the previous script as a background process.

    ./download.sh&

    8 - Dump the warnings on the screen:

    tail -f /var/log/messages

    You should wait some minutes before the messages are shown.

    Joaquim Duran

     
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    10 Jul 2015 10:49 AM

    I did a little research on the message you are receiving. It looks like it is due to the age of the TI firmware being loaded. We are working on a BSP update (2.4-4) for release this fall. It will have an updated Wifi driver.


    For now, please contact your sales representative to request a patch that will update your wifi drivers, TI firmware, and the build environment until we release the updated BSP.


    These new drivers should be newer, unfortunately we don't have knowledge of what is inside the Ti firmware, because they have it closed source.

    adam

    Pedro Erencia
    New Member
    New Member
    Posts:17


    --
    13 Jul 2015 03:42 AM

    Hi Adam,

    Thanks for the quick response,

    What do that patches fix ? We ask that because the fact is that we are getting kernel Oops regarding wpa_supplicant and the wl12xx driver (I paste one below); that crashes are the "real" problem.

    So, we wonder wheter the "wl1283: WARNING corrupted packet in RX with status: 0x1" and the crash could be related or they seem completely different issues...

    Thanks.

    ---- Kernel crash -----

    Jul  9 20:26:40 DM-37x user.alert kernel: [ 7717.907409] Unable to handle kernel NULL pointer dereference at virtual address 00000009

    Jul  9 20:26:40 DM-37x user.alert kernel: [ 7717.915985] pgd = cb11c000

    Jul  9 20:26:40 DM-37x user.alert kernel: [ 7717.918823] [00000009] *pgd=8b124831, *pte=00000000, *ppte=00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7717.925476] Internal error: Oops: 817 [#1]

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.929748] Modules linked in: twl4030_usb wl12xx_sdio wl12xx omaplfb pvrsrvkm musb_hdrc omap2430 [last unloaded: twl4030_usb]

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.941680] CPU: 0    Not tainted  (3.0.0-BSP-dm37x-2.3-2 #131)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.947875] PC is at __ieee80211_key_replace+0x88/0x240

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.953338] LR is at ieee80211_key_link+0xa8/0x178

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.958343] pc : []    lr : []    psr: a0000013

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.958343] sp : cb117bf0  ip : 00000000  fp : 00000002

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.970336] r10: 00000000  r9 : 00000001  r8 : 00000000

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.975769] r7 : 00000000  r6 : cd1efc00  r5 : cb049580  r4 : cdbdd200

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.982604] r3 : 00200200  r2 : 00100100  r1 : cd1efe0c  r0 : 00000009

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.989410] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7717.996856] Control: 10c5387d  Table: 8b11c019  DAC: 00000015

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.002868] Process wpa_supplicant (pid: 246, stack limit = 0xcb1162f0)

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.009765] Stack: (0xcb117bf0 to 0xcb118000)

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.014312] 7be0:                                     cdbdd200 cdbdd200 c354d460 cd1efc00

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.022857] 7c00: 00000000 cb049580 00000002 00000000 cb081400 c0593180 cd1efc00 00000006

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.031402] 7c20: 00000006 cd1efc00 cb049000 00000000 cb049580 cd24ec10 cb117ca8 c058b688

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.039947] 7c40: 00000006 cd24ec44 00000000 00000000 cb10c000 cb049000 cb117c68 c056501c

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.048492] 7c60: 00000000 cb117c68 cd24ec18 cd24ec44 00000020 00000006 000fac02 00000002

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.057006] 7c80: 00000000 01000000 c0977100 00000000 cd24ec00 cd2652c0 c0977248 c04951d8

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.065551] 7ca0: c05fd220 00000000 559ebb1c 000000eb cd24ec00 cd24ec10 cd24ec14 cd912800

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.074096] 7cc0: cb10c000 cb049000 cd24ec00 cd2652c0 c0494fc8 cd91342c cd2652c0 cb117d0c

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.082641] 7ce0: c0f14494 c0493358 c0970cfc cd2652c0 00000064 c0494fbc cd913400 00000064

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.091186] 7d00: 00000064 c0493028 00000064 7fffffff 00000000 cd2652c0 00000000 cb117f74

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.099731] 7d20: cac2cb80 00000000 cb117e00 cb081400 00000064 c0493998 cd31c3c0 a0000013

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.108276] 7d40: cd2652c0 00000000 cd2a9e40 cd1e30c0 00000000 000000f6 00000000 00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.116821] 7d60: cd2652c0 00000000 00000000 cac2cb80 00000064 cb117d88 cb117ee0 cb117ee0

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.125366] 7d80: 00000000 c0468e00 00000002 60000013 00000000 00000001 ffffffff 00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.133880] 7da0: 00000000 00000000 00000000 00000000 cd2a4100 00000000 00000000 00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.142425] 7dc0: 00000000 00000000 cb117e00 00000000 00000002 00000000 00000000 00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.150970] 7de0: cd2a4100 cb117df8 cb116000 00000000 0000000b c0468e00 00000002 00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.159515] 7e00: cd2a4100 00000001 ffffffff 00000064 cac2cb80 00000000 cb117d48 cb117f74

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.168060] 7e20: cb117ee0 cb117f74 cb117ee0 cac2cb80 c00c2208 cb117ee0 00000008 00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.176605] 7e40: cb117f74 00000064 00000000 cac2cb80 cb117f20 c04689b0 cb117f20 00000008

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.185150] 7e60: 00000010 00000000 00000000 00000000 00000000 00000000 00000002 c07c6f8c

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.193695] 7e80: 00000001 60000013 00000000 c012f8ac 00000001 00000000 00000000 c05b435c

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.202239] 7ea0: 00000000 c012f8ac c07b1fe0 fffffffe c07c6f8c 00000000 00000001 ffffffff

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.210754] 7ec0: c07b1cd4 000005a0 00000002 c05b43d8 00000000 00000000 c05b435c c00f0d38

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.219299] 7ee0: 000b324c 00000000 00000000 cd3060c0 00000001 c00f2c9c cd18b040 c07b2614

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.227844] 7f00: cd3060c0 cd2a4100 cb117fac c05aec9c 00000002 00000080 00000000 c013e2a4

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.236389] 7f20: c093ce9c c07b2614 c0944a60 c07ac168 c00c20ac cb116000 f71e5fc1 00000704

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.244934] 7f40: c013e2a4 bec15d1c 00000000 cac2cb80 00000128 c00c2208 cb116000 00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.253479] 7f60: 00000002 c0469368 00000000 00000000 00000000 cb117e60 0000000c cb117ee0

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.262023] 7f80: 00000001 00000000 00000000 00000000 fffffff7 00000000 000a5c28 40033568

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.270568] 7fa0: 000a5c60 c00c2040 000a5c28 40033568 00000006 bec15d1c 00000000 00000000

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.279113] 7fc0: 000a5c28 40033568 000a5c60 00000128 000a5c60 00000003 00000000 00000002

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.287628] 7fe0: bec15d1c bec15d00 400255f4 403940ac 60000010 00000006 80c00202 0888002d

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.296203] [] (__ieee80211_key_replace+0x88/0x240) from [] (ieee80211_key_link+0xa8/0x178)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.306732] [] (ieee80211_key_link+0xa8/0x178) from [] (ieee80211_add_key+0xb8/0x12c)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.316741] [] (ieee80211_add_key+0xb8/0x12c) from [] (nl80211_new_key+0xf8/0x124)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.326477] [] (nl80211_new_key+0xf8/0x124) from [] (genl_rcv_msg+0x210/0x250)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.335845] [] (genl_rcv_msg+0x210/0x250) from [] (netlink_rcv_skb+0xa8/0xc0)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.345123] [] (netlink_rcv_skb+0xa8/0xc0) from [] (genl_rcv+0x2c/0x38)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.353820] [] (genl_rcv+0x2c/0x38) from [] (netlink_unicast+0x2e8/0x2f8)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.362731] [] (netlink_unicast+0x2e8/0x2f8) from [] (netlink_sendmsg+0x2b8/0x304)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.372467] [] (netlink_sendmsg+0x2b8/0x304) from [] (sock_sendmsg+0x98/0xb8)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.381744] [] (sock_sendmsg+0x98/0xb8) from [] (__sys_sendmsg+0xf0/0x230)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.390747] [] (__sys_sendmsg+0xf0/0x230) from [] (sys_sendmsg+0x3c/0x64)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.399658] [] (sys_sendmsg+0x3c/0x64) from [] (ret_fast_syscall+0x0/0x3c)

    Jul  9 20:26:40 DM-37x user.emerg kernel: [ 7718.408660] Code: e594100c e3402010 e3003200 e3403020 (e5801000)

    Jul  9 20:26:40 DM-37x user.warn kernel: [ 7718.415100] ---[ end trace b5493a05541ee956 ]---
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    13 Jul 2015 09:07 AM
    The patches from a newer Linux Kernel (3.17), and included in those patches are updated firmware from TI. Unfortunately, TI doesn't fully disclose their closed-source firmware information, but there are several TI forum postings with similar errors to what was originally posted. When I looked up the error message about the corruption packet on one of TI's forum pages, it was listed as a bug in the TI firmware and updating was their suggested solution.

    I also know that the backports are required for use in Europe to meet regulatory compliance which I believe you need.


    Are you getting the kernel panic from the original driver or the backport drivers?


    adam

    jduran.gm
    New Member
    New Member
    Posts:79


    --
    14 Jul 2015 02:49 AM
    Adam,

    I've applied the patch in a clean environment, I haven't modified any kernel option, but the wlan0 doesn't exists:

    DM-37x# lsmod
    Module Size Used by
    wlcore_sdio 5813 0
    compat 20309 1 wlcore_sdio
    g_ether 57800 0
    DM-37x# ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:50:C2:70:0A:61
    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:33

    lo Link encap:Local Loopback
    LOOPBACK MTU:16436 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    usb0 Link encap:Ethernet HWaddr 0E:F5:35:BC:00:2D
    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)

    DM-37x# /etc/rc.d/init.d/network-wifi-station start
    Importing configuration variables from /etc/rc.d/rc.conf
    loading wlcore_sdio
    Starting wpa_supplicant:
    Successfully initialized wpa_supplicant
    nl80211: 'nl80211' generic netlink not found
    Failed to initialize driver 'nl80211'
    wlan0: Unsupported driver 'nl80211'
    Bouncing WiFi interface (workaround).
    Timeout waiting for /var/run/wlan0 creation
    ifconfig: SIOCGIFFLAGS: No such device
    ifconfig: SIOCGIFFLAGS: No such device
    ip: SIOCGIFFLAGS: No such device
    DM-37x#

    Joaquim Duran
    jduran.gm
    New Member
    New Member
    Posts:79


    --
    14 Jul 2015 03:22 AM
    Based on the previous error, I've modified the configuration options of 'Networking support / Wireless' based on the configuration of an BSP 2.4-3 with no patch.

    --- Wireless
    <*> cfg80211 - wireless configuration API
    [*] nl80211 testmode command
    [ ] enable developer warnings (NEW)
    [ ] cfg80211 regulatory debugging (NEW)
    [*] enable powersave by default (NEW)
    [ ] cfg80211 DebugFS entries (NEW)
    [ ] use statically compiled regulatory rules database (NEW)
    [*] cfg80211 wireless extensions compatibility (NEW)
    [*] Wireless extensions sysfs files (NEW)
    < > Common routines for IEEE802.11 drivers
    <*> Generic IEEE 802.11 Networking Stack (mac80211)
    [ ] PID controller based rate control algorithm (NEW)
    [*] Minstrel (NEW)
    [*] Minstrel 802.11n support (NEW)
    Default rate control algorithm (Minstrel) --->
    [ ] Enable mac80211 mesh networking (pre-802.11s) support (NEW)
    [ ] Enable LED triggers (NEW)
    [ ] Export mac80211 internals in DebugFS (NEW)
    [ ] Select mac80211 debugging features (NEW) --->

    The interface wlan0 is not usable (error is different than in previous message):

    DM-37x# lsmod
    Module Size Used by
    wlcore_sdio 5813 0
    compat 20309 1 wlcore_sdio
    g_ether 57800 0
    DM-37x# ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:50:C2:70:0A:61
    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:33

    lo Link encap:Local Loopback
    LOOPBACK MTU:16436 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    usb0 Link encap:Ethernet HWaddr 9E:94:9D:EA:0F:67
    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)

    DM-37x# /etc/rc.d/init.d/wpa_supplicant start
    Importing configuration variables from /etc/rc.d/rc.conf
    loading wlcore_sdio
    Starting wpa_supplicant:
    Successfully initialized wpa_supplicant
    nl80211: Could not configure driver to use managed mode
    Could not read interface wlan0 flags: No such device
    wlan0: Failed to initialize driver interface
    Bouncing WiFi interface (workaround).

    DM-37x#

    Joaquim Duran
    Pedro Erencia
    New Member
    New Member
    Posts:17


    --
    14 Jul 2015 07:48 AM

    Ok, I see.

    The kernel panic was from the original driver.

    Thanks.

    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    14 Jul 2015 08:52 AM
    Joaquim,

    With the patch installed, the kernel module and the corresponding wireless packages like cfg80211 are disabled in the kernel, because they are built as a separate package.

    The patch modifies LTIB to build them as a separate package.

    The driver name also changes from the original BSP to the patched version. In our stock 2.4-3 BSP, the driver is called wl12xx_sdio and in the patched version, it is named wlcore_sdio. Performing a modprobe on wlcore_sdio should auto enable the wl12xx driver along with some of the cfg80211 and mac80211 modules.


    Looking at some of the logs above it looks some of the patches may not have applied or the BSP wasn't completely clean.

    Enabling PM off mode:


    Welcome to the LTIB Embedded Linux Environment

    !!!!! WARNING !!!!!!!

    The default password for the root account is: root
    please change this password using the 'passwd' command
    and then edit this message (/etc/issue) to remove this message.

    To enable DHCP on ethernet, type "ifup eth0"

    DM-37x login: [ 28.379760] smartreflex smartreflex.0: sr_v2_disable: Smartreflex disable timedout
    root
    Password:
    DM-37x# [ 31.074981] omap_device: omap_i2c.1: new worst case deactivate latency 0: 61035
    DM-37x# lsmod
    Module Size Used by
    g_ether 57800 0
    DM-37x# modprobe wlcore_sdio
    [ 40.634002] Loading modules backported from Linux version v3.17.1-0-g9db8a8b
    [ 40.641662] Backport generated by backports.git v3.17.1-1-0-g2ced168
    DM-37x# [ 41.356750] smartreflex smartreflex.0: sr_v2_disable: Smartreflex disable timedout
    [ 41.366546] cfg80211: Calling CRDA to update world regulatory domain
    [ 41.847412] Copying NVS calibration from product ID chip
    [ 41.982574] cfg80211: World regulatory domain updated:
    [ 41.988159] cfg80211: DFS Master region: unset
    [ 41.992736] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [ 42.003021] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 42.011566] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 42.020080] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    [ 42.028533] cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
    [ 42.037078] cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 42.045623] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 42.054199] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    [ 42.062652] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
    [ 42.348724] cfg80211: Updating information on frequency 2412 MHz with regulatory rule:
    [ 42.357269] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.365234] cfg80211: Updating information on frequency 2417 MHz with regulatory rule:
    [ 42.373657] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.381622] cfg80211: Updating information on frequency 2422 MHz with regulatory rule:
    [ 42.390014] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.398010] cfg80211: Updating information on frequency 2427 MHz with regulatory rule:
    [ 42.406433] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.414398] cfg80211: Updating information on frequency 2432 MHz with regulatory rule:
    [ 42.422790] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.430755] cfg80211: Updating information on frequency 2437 MHz with regulatory rule:
    [ 42.439147] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.447143] cfg80211: Updating information on frequency 2442 MHz with regulatory rule:
    [ 42.455566] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.463500] cfg80211: Updating information on frequency 2447 MHz with regulatory rule:
    [ 42.471954] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.479919] cfg80211: Updating information on frequency 2452 MHz with regulatory rule:
    [ 42.488311] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.496276] cfg80211: Updating information on frequency 2457 MHz with regulatory rule:
    [ 42.504699] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.512634] cfg80211: Updating information on frequency 2462 MHz with regulatory rule:
    [ 42.521057] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.528991] cfg80211: Updating information on frequency 2467 MHz with regulatory rule:
    [ 42.537414] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.545349] cfg80211: Updating information on frequency 2472 MHz with regulatory rule:
    [ 42.553771] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 42.561706] cfg80211: Updating information on frequency 2484 MHz with regulatory rule:
    [ 42.570129] cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A mBi, 2000 mBm)
    [ 42.578063] cfg80211: Disabling freq 5040 MHz
    [ 42.582733] cfg80211: Disabling freq 5060 MHz
    [ 42.587310] cfg80211: Disabling freq 5080 MHz
    [ 42.592010] cfg80211: Disabling freq 5170 MHz
    [ 42.596588] cfg80211: Updating information on frequency 5180 MHz with regulatory rule:
    [ 42.605010] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.613037] cfg80211: Updating information on frequency 5190 MHz with regulatory rule:
    [ 42.621459] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.629486] cfg80211: Updating information on frequency 5200 MHz with regulatory rule:
    [ 42.637939] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.645996] cfg80211: Updating information on frequency 5210 MHz with regulatory rule:
    [ 42.654418] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.662475] cfg80211: Updating information on frequency 5220 MHz with regulatory rule:
    [ 42.670898] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.678955] cfg80211: Updating information on frequency 5230 MHz with regulatory rule:
    [ 42.687347] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.695404] cfg80211: Updating information on frequency 5240 MHz with regulatory rule:
    [ 42.703796] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.711853] cfg80211: Updating information on frequency 5260 MHz with regulatory rule:
    [ 42.720275] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.728302] cfg80211: Updating information on frequency 5280 MHz with regulatory rule:
    [ 42.736724] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.744781] cfg80211: Updating information on frequency 5300 MHz with regulatory rule:
    [ 42.753173] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.761230] cfg80211: Updating information on frequency 5320 MHz with regulatory rule:
    [ 42.769622] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.777679] cfg80211: Updating information on frequency 5500 MHz with regulatory rule:
    [ 42.786071] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.794128] cfg80211: Updating information on frequency 5520 MHz with regulatory rule:
    [ 42.802520] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.810577] cfg80211: Updating information on frequency 5540 MHz with regulatory rule:
    [ 42.818969] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.827026] cfg80211: Updating information on frequency 5560 MHz with regulatory rule:
    [ 42.835449] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.843505] cfg80211: Updating information on frequency 5580 MHz with regulatory rule:
    [ 42.851898] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.859954] cfg80211: Updating information on frequency 5600 MHz with regulatory rule:
    [ 42.868347] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.876403] cfg80211: Updating information on frequency 5620 MHz with regulatory rule:
    [ 42.884796] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.892852] cfg80211: Updating information on frequency 5640 MHz with regulatory rule:
    [ 42.901245] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.909301] cfg80211: Updating information on frequency 5660 MHz with regulatory rule:
    [ 42.917724] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.925750] cfg80211: Updating information on frequency 5680 MHz with regulatory rule:
    [ 42.934143] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.942169] cfg80211: Updating information on frequency 5700 MHz with regulatory rule:
    [ 42.950592] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 42.958618] cfg80211: Updating information on frequency 5745 MHz with regulatory rule:
    [ 42.967041] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 42.974975] cfg80211: Updating information on frequency 5765 MHz with regulatory rule:
    [ 42.983398] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 42.991333] cfg80211: Updating information on frequency 5785 MHz with regulatory rule:
    [ 42.999755] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 43.007720] cfg80211: Updating information on frequency 5805 MHz with regulatory rule:
    [ 43.016143] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 43.024078] cfg80211: Updating information on frequency 5825 MHz with regulatory rule:
    [ 43.032501] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 43.058197] wlcore: loaded

    DM-37x# lsmod
    Module Size Used by
    wl12xx 61790 0
    wlcore 217423 1 wl12xx
    mac80211 549928 2 wl12xx,wlcore
    cfg80211 488046 2 wlcore,mac80211
    wlcore_sdio 5805 0
    compat 20293 5 wl12xx,wlcore,mac80211,cfg80211,wlcore_sdio
    g_ether 57800 0
    DM-37x#




    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    14 Jul 2015 09:39 AM
    You may want to delete the linux kernel directory all together and let LTIB rebuilt it. If the kernel drivers exist when the backport modules try to load it will cause a conflic.t

    adam
    jduran.gm
    New Member
    New Member
    Posts:79


    --
    15 Jul 2015 06:46 AM

    We repeated the process as stated in the README:

    1.  unpacking the BSP
    2. /ltib -b -m distclean
    3. copying wifi_patch.sh and wireless_updates.tar.xz to the BSP dir
    4. ./wifi_patch.sh

    Finally we did modprobe wlcore_sdio, but the result was the same that Joaquim told you before.

    It seems that wlcore_sdio does not loads wl12xx. We have loaded  it manually and now it seems to work.

     DM-37x# lsmod
    Module                  Size  Used by
    wl12xx                 61798  0
    wlcore                217431  1 wl12xx
    mac80211              549932  2 wl12xx,wlcore
    cfg80211              488050  2 wlcore,mac80211
    wlcore_sdio             5805  0
    compat                 20293  5 wl12xx,wlcore,mac80211,cfg80211,wlcore_sdio
    g_ether                57800  0

    Can you confirm that is really the new driver that is running ?


    [ 1659.085571] Loading modules backported from Linux version v3.17.1-0-g9db8a8b
    [ 1659.085632] Backport generated by backports.git v3.17.1-1-0-g2ced168
    [ 1863.147430] cfg80211: Calling CRDA to update world regulatory domain
    [ 1863.616577] Copying NVS calibration from product ID chip
    [ 1864.014434] cfg80211: World regulatory domain updated:
    [ 1864.014465] cfg80211:  DFS Master region: unset
    [ 1864.014465] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [ 1864.014495] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 1864.014495] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 1864.014526] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    [ 1864.014526] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
    [ 1864.014556] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 1864.014556] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 1864.014587] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    [ 1864.014587] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
    [ 1864.267822] cfg80211: Updating information on frequency 2412 MHz with regulatory rule:
    [ 1864.267852] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.267883] cfg80211: Updating information on frequency 2417 MHz with regulatory rule:
    [ 1864.267883] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.267913] cfg80211: Updating information on frequency 2422 MHz with regulatory rule:
    [ 1864.267913] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.267944] cfg80211: Updating information on frequency 2427 MHz with regulatory rule:
    [ 1864.267944] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.267944] cfg80211: Updating information on frequency 2432 MHz with regulatory rule:
    [ 1864.267974] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.267974] cfg80211: Updating information on frequency 2437 MHz with regulatory rule:
    [ 1864.268005] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268005] cfg80211: Updating information on frequency 2442 MHz with regulatory rule:
    [ 1864.268035] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268035] cfg80211: Updating information on frequency 2447 MHz with regulatory rule:
    [ 1864.268066] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268066] cfg80211: Updating information on frequency 2452 MHz with regulatory rule:
    [ 1864.268066] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268096] cfg80211: Updating information on frequency 2457 MHz with regulatory rule:
    [ 1864.268096] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268127] cfg80211: Updating information on frequency 2462 MHz with regulatory rule:
    [ 1864.268127] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268157] cfg80211: Updating information on frequency 2467 MHz with regulatory rule:
    [ 1864.268157] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268188] cfg80211: Updating information on frequency 2472 MHz with regulatory rule:
    [ 1864.268188] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268188] cfg80211: Updating information on frequency 2484 MHz with regulatory rule:
    [ 1864.268218] cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268218] cfg80211: Disabling freq 5040 MHz
    [ 1864.268249] cfg80211: Disabling freq 5060 MHz
    [ 1864.268249] cfg80211: Disabling freq 5080 MHz
    [ 1864.268249] cfg80211: Disabling freq 5170 MHz
    [ 1864.268280] cfg80211: Updating information on frequency 5180 MHz with regulatory rule:
    [ 1864.268280] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268310] cfg80211: Updating information on frequency 5190 MHz with regulatory rule:
    [ 1864.268310] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268310] cfg80211: Updating information on frequency 5200 MHz with regulatory rule:
    [ 1864.268341] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268341] cfg80211: Updating information on frequency 5210 MHz with regulatory rule:
    [ 1864.268371] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268371] cfg80211: Updating information on frequency 5220 MHz with regulatory rule:
    [ 1864.268402] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268402] cfg80211: Updating information on frequency 5230 MHz with regulatory rule:
    [ 1864.268432] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268432] cfg80211: Updating information on frequency 5240 MHz with regulatory rule:
    [ 1864.268463] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268463] cfg80211: Updating information on frequency 5260 MHz with regulatory rule:
    [ 1864.268463] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268493] cfg80211: Updating information on frequency 5280 MHz with regulatory rule:
    [ 1864.268493] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268524] cfg80211: Updating information on frequency 5300 MHz with regulatory rule:
    [ 1864.268524] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268554] cfg80211: Updating information on frequency 5320 MHz with regulatory rule:
    [ 1864.268554] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268585] cfg80211: Updating information on frequency 5500 MHz with regulatory rule:
    [ 1864.268585] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268585] cfg80211: Updating information on frequency 5520 MHz with regulatory rule:
    [ 1864.268615] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268615] cfg80211: Updating information on frequency 5540 MHz with regulatory rule:
    [ 1864.268646] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268646] cfg80211: Updating information on frequency 5560 MHz with regulatory rule:
    [ 1864.268676] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268676] cfg80211: Updating information on frequency 5580 MHz with regulatory rule:
    [ 1864.268707] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268707] cfg80211: Updating information on frequency 5600 MHz with regulatory rule:
    [ 1864.268707] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268737] cfg80211: Updating information on frequency 5620 MHz with regulatory rule:
    [ 1864.268737] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268768] cfg80211: Updating information on frequency 5640 MHz with regulatory rule:
    [ 1864.268768] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268798] cfg80211: Updating information on frequency 5660 MHz with regulatory rule:
    [ 1864.268798] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268829] cfg80211: Updating information on frequency 5680 MHz with regulatory rule:
    [ 1864.268829] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268859] cfg80211: Updating information on frequency 5700 MHz with regulatory rule:
    [ 1864.268859] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268859] cfg80211: Updating information on frequency 5745 MHz with regulatory rule:
    [ 1864.268890] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268890] cfg80211: Updating information on frequency 5765 MHz with regulatory rule:
    [ 1864.268920] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268920] cfg80211: Updating information on frequency 5785 MHz with regulatory rule:
    [ 1864.268951] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268951] cfg80211: Updating information on frequency 5805 MHz with regulatory rule:
    [ 1864.268981] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.268981] cfg80211: Updating information on frequency 5825 MHz with regulatory rule:
    [ 1864.268981] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 1864.283538] wlcore: loaded
    [ 1962.060211] omap_device: omap_i2c.1: new worst case activate latency 0: 213623
    [ 1962.831420] wlcore: firmware booted (Rev 7.3.10.0.139)
    [ 2092.242523] wlcore: down
    [ 2092.816192] wlcore: firmware booted (Rev 7.3.10.0.139)
    [ 2291.343231] wlan0: authenticate with 48:5b:39:e7:63:0f
    [ 2291.388946] wlan0: send auth to 48:5b:39:e7:63:0f (try 1/3)
    [ 2291.400299] wlan0: authenticated
    [ 2291.409393] wl12xx_driver wl12xx: wlan0: disabling HT/VHT due to WEP/TKIP use
    [ 2291.409576] wl12xx_driver wl12xx: wlan0: disabling HT as WMM/QoS is not supported by the AP
    [ 2291.409637] wl12xx_driver wl12xx: wlan0: disabling VHT as WMM/QoS is not supported by the AP
    [ 2291.420318] wlan0: associate with 48:5b:39:e7:63:0f (try 1/3)
    [ 2291.428466] wlan0: RX AssocResp from 48:5b:39:e7:63:0f (capab=0x411 status=0 aid=1)
    [ 2291.491851] wlan0: associated
    [ 2291.601867] wlcore: Association completed.
    [ 2325.221862] wlan0: deauthenticating from 48:5b:39:e7:63:0f by local choice (Reason: 3=DEAUTH_LEAVING)
    [ 2325.335693] wlcore: down
    [ 2325.348693] cfg80211: All devices are disconnected, going to restore regulatory settings
    [ 2325.348754] cfg80211: Restoring regulatory settings
    [ 2325.349060] cfg80211: Kicking the queue
    [ 2325.349151] cfg80211: Calling CRDA to update world regulatory domain
    [ 2325.586273] cfg80211: Updating information on frequency 2412 MHz with regulatory rule:
    [ 2325.586334] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.586364] cfg80211: Updating information on frequency 2417 MHz with regulatory rule:
    [ 2325.586425] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.586456] cfg80211: Updating information on frequency 2422 MHz with regulatory rule:
    [ 2325.586486] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.586547] cfg80211: Updating information on frequency 2427 MHz with regulatory rule:
    [ 2325.586578] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.586608] cfg80211: Updating information on frequency 2432 MHz with regulatory rule:
    [ 2325.586669] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.586700] cfg80211: Updating information on frequency 2437 MHz with regulatory rule:
    [ 2325.586730] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.586791] cfg80211: Updating information on frequency 2442 MHz with regulatory rule:
    [ 2325.586822] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.586853] cfg80211: Updating information on frequency 2447 MHz with regulatory rule:
    [ 2325.586883] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.586944] cfg80211: Updating information on frequency 2452 MHz with regulatory rule:
    [ 2325.586975] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587005] cfg80211: Updating information on frequency 2457 MHz with regulatory rule:
    [ 2325.587066] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587097] cfg80211: Updating information on frequency 2462 MHz with regulatory rule:
    [ 2325.587127] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587188] cfg80211: Updating information on frequency 2467 MHz with regulatory rule:
    [ 2325.587219] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587249] cfg80211: Updating information on frequency 2472 MHz with regulatory rule:
    [ 2325.587280] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587341] cfg80211: Updating information on frequency 2484 MHz with regulatory rule:
    [ 2325.587371] cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587402] cfg80211: Disabling freq 5040 MHz
    [ 2325.587432] cfg80211: Disabling freq 5060 MHz
    [ 2325.587463] cfg80211: Disabling freq 5080 MHz
    [ 2325.587493] cfg80211: Disabling freq 5170 MHz
    [ 2325.587524] cfg80211: Updating information on frequency 5180 MHz with regulatory rule:
    [ 2325.587554] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587615] cfg80211: Updating information on frequency 5190 MHz with regulatory rule:
    [ 2325.587646] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587677] cfg80211: Updating information on frequency 5200 MHz with regulatory rule:
    [ 2325.587738] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587768] cfg80211: Updating information on frequency 5210 MHz with regulatory rule:
    [ 2325.587799] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587860] cfg80211: Updating information on frequency 5220 MHz with regulatory rule:
    [ 2325.587890] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.587921] cfg80211: Updating information on frequency 5230 MHz with regulatory rule:
    [ 2325.587982] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588012] cfg80211: Updating information on frequency 5240 MHz with regulatory rule:
    [ 2325.588043] cfg80211: 5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588073] cfg80211: Updating information on frequency 5260 MHz with regulatory rule:
    [ 2325.588134] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588165] cfg80211: Updating information on frequency 5280 MHz with regulatory rule:
    [ 2325.588195] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588256] cfg80211: Updating information on frequency 5300 MHz with regulatory rule:
    [ 2325.588287] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588317] cfg80211: Updating information on frequency 5320 MHz with regulatory rule:
    [ 2325.588378] cfg80211: 5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588409] cfg80211: Updating information on frequency 5500 MHz with regulatory rule:
    [ 2325.588439] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588500] cfg80211: Updating information on frequency 5520 MHz with regulatory rule:
    [ 2325.588531] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588562] cfg80211: Updating information on frequency 5540 MHz with regulatory rule:
    [ 2325.588623] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588653] cfg80211: Updating information on frequency 5560 MHz with regulatory rule:
    [ 2325.588684] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588714] cfg80211: Updating information on frequency 5580 MHz with regulatory rule:
    [ 2325.588775] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588806] cfg80211: Updating information on frequency 5600 MHz with regulatory rule:
    [ 2325.588836] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588897] cfg80211: Updating information on frequency 5620 MHz with regulatory rule:
    [ 2325.588928] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.588958] cfg80211: Updating information on frequency 5640 MHz with regulatory rule:
    [ 2325.589019] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.589050] cfg80211: Updating information on frequency 5660 MHz with regulatory rule:
    [ 2325.589080] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.589141] cfg80211: Updating information on frequency 5680 MHz with regulatory rule:
    [ 2325.589172] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.589202] cfg80211: Updating information on frequency 5700 MHz with regulatory rule:
    [ 2325.589263] cfg80211: 5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.589294] cfg80211: Updating information on frequency 5745 MHz with regulatory rule:
    [ 2325.589324] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.589691] cfg80211: Updating information on frequency 5765 MHz with regulatory rule:
    [ 2325.589752] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.589782] cfg80211: Updating information on frequency 5785 MHz with regulatory rule:
    [ 2325.589813] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.589874] cfg80211: Updating information on frequency 5805 MHz with regulatory rule:
    [ 2325.589904] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.589935] cfg80211: Updating information on frequency 5825 MHz with regulatory rule:
    [ 2325.589996] cfg80211: 5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A mBi, 2000 mBm)
    [ 2325.590057] cfg80211: World regulatory domain updated:
    [ 2325.590087] cfg80211:  DFS Master region: unset
    [ 2325.590118] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [ 2325.590179] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 2325.590209] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 2325.590270] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    [ 2325.590301] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
    [ 2325.590362] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 2325.590393] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 2325.590454] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    [ 2325.590484] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
    [ 2326.536468] wlcore: firmware booted (Rev 7.3.10.0.139)
    [ 2326.776794] wlcore: down
    [ 2327.330718] wlcore: firmware booted (Rev 7.3.10.0.139)
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    15 Jul 2015 07:03 AM
    That is correct. 7.3 is the correct firmware for the newer driver.

    If you want to get rid of a bunch of that extra cgf80211 chatter, you can change the u-boot parameter 'otherbootargs' and eliminate the 'ignore_loglevel' parameter, and cfg80211 will stop being so verbose.

    adam
    Pedro Erencia
    New Member
    New Member
    Posts:17


    --
    22 Jul 2015 03:45 AM

    Hello Adam,

     

    We are experiencing some problems with the new 2.4.3 BSP and the wifi patch. First of all, we experience a great loss of performance in our application. With the 2.3.2 BSP it started in ~18 seconds, most of that time spent in compiling and creating javascript objects in memory. With the new 2.4.3 and wifi patches it takes 1 minute to start. It must be said that we also apply some patches to the BSP kernel from our manufacturer, but most of them apply smoothly and the few rejects that we are forced to do manually seem trivial, related with screen config (resolution, etc). They all applied well to the 2.3.2 because they were done with respect to that BSP.

    We are going to try to run our app without our manufacturer patches and be back here to show the results. In the meantime, is there any hint you could provide us of where to look or what changes since 2.3.2 to 2.4.3 may have such impact on the performance ?

    Aside from that, we experience the same problems with the wifi corruption packets with the 2.4.3 BSP with the wifi patch. We have tested with two different APs. Here (http://e2e.ti.com/support...07/p/346356/1212732) there's people that claims to have the same problem with the firmware version we have in the BSP. It seems that the solution also involves updating the wl12xx driver.

     We look forward to your comments.

     

    Cheers,

     

    Pedro.

     
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    22 Jul 2015 08:18 AM
    If you log into our support site, you should be able to download the release notes that cover the changes to the BSP located here: http://support.logicpd.co...talid=0&EntryId=1396

    Since I don't know what patches you are applying to the kernel, I cannot speak as to what is happening there. I would suggest that you consider a plain, stock BSP with our development board to see if you notice any speed changes there in the time it takes to boot. If you notice something there, I can look into it.

    If you can give me an idea of how you're patching the kernel or in what ways the performance is degraded, it might be able to help me identify ways to improve it.

    Having said that, we're in the final stages of development for our latest BSP which will be 2.4-4 and scheduled to be released this fall. This new BSP will have some additional performance improvements. Most notably will be the Kernel will be updated to 3.0.101 (from 3.0). We will also enable the L2 cache which is currently disabled by default in the 2.4-3 and older BSP since there was compatibility issues with larger displays and certain toolchain combinations. Enabling the L2 cache has shown a 3x improvement in certain floating point calculations and to a lesser extent, overall system performance. The kernel update to 3.0.101 has also shown some improvement in throughput on the ethernet driver. (70+ Mbps up from about 50-60). The SD card driver in the u-boot will also improve the throughput, so the time it takes to load uImage and rootfs from the SD card will be greatly improved. We will also be adding support to act as a Wifi access point in the 5GHz bands. Currently, we only can connect to an access point in the 5GHz band. For customers who use the DSP, we are also including a method to increase the DSP frequency for better performance.

    The upcoming BSP release will also include newer TI firmware for the wifi driver. wlcore: firmware booted (Rev 7.3.10.0.139). This is a backport from the Linux Kernel 4.0 and adapted to work for our 3.0 Kernel. However, when reading the forum post you sent, it looks as if that user is still having trouble despite the firmware image being the latest, so the issue may still be on TI's side since we don't have control over the TI firmware that is loaded into the. You might want to start with playing with Wifi Channels, beecause we've had some customers report improved performance when moving to better channels.

    We don't have any of these updates ready for distribution, but I wanted to let you know what is coming and we are targeting September for a release.


    adam


    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    22 Jul 2015 08:28 AM
    Joaquim,

    If you're still having issues with the driver loading on startup, check the contents of /etc/rc.d/rc.conf

    Look for WIFI_MODULE in this file.

    For the backported driver, it should read:

    export WIFI_MODULE="wlcore_sdio"

    adam

    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    22 Jul 2015 08:45 AM
    Pedro,

    If you have our latest Linux BSP User Guide, we have some recommendations for removing unwanted/unnecessary drivers. Check out section - 10.3.2 Remove Specific Interfaces

    The User Guide is found here: http://support.logicpd.co...talid=0&EntryId=1392

    adam
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    22 Jul 2015 08:50 AM
    Joaquim,

    If you want to remove some of the excessive text, you can change the u-boot parameter called otherbootargs to reduce this extra text.


    setenv otherbootargs 'early_printk no_console_suspend'

    By eliminating the ignore_loglevel, only outputs at specific log levels will be displayed.

    adam
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    22 Jul 2015 09:19 AM
    Pedro,

    I did a little more digging. If you are not operating the Wireless chipset in the US, you may want to change the country code. I believe the backports we sent you have more countries enabled, but we only certified the radio to US and Canada. However if you are operating in España, you could switch it.

    In order to operate at all these available channels and frequencies, you'll need to submit your system for regulatory approvals.

    iw reg set ES
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    22 Jul 2015 03:15 PM
    I did more investigating, and from the link given above it appears that it might be related to encryption. I would suggest the following as something to try:

    ./ltib -c
    [*] Configure Kernel

    (exit)
    (save)

    Cryptographic API --> <*> GCM/GMAC support

    (exit)
    (save)


    It will build in some additional encryption which is necessary for the latest edition of the drivers. Which encryption method are you using?

    adam

    jduran.gm
    New Member
    New Member
    Posts:79


    --
    23 Jul 2015 02:53 AM
     Posted By Adam Ford on 22 Jul 2015 08:28 AM 
    For the backported driver, it should read:

    export WIFI_MODULE="wlcore_sdio"

    adam

    We've replaced the previous line with:

    export WIFI_MODULE="wlcore_sdio wl12xx"

    The script executes two modprobe commands to the modules and then the wifi works fine.

    Joaquim Duran

     
    Pedro Erencia
    New Member
    New Member
    Posts:17


    --
    27 Jul 2015 06:57 AM

    Hello Adam,

     

    I'm trying to figure it out why the performance is so bad. I have compiled the 2.4.3 BSP without any patch from our manufacturers but the problem remains. Until now, I have only found that only 800Mhz can be reached by the CPU - not the 1000GHz available - as stated by cpufreq-info,

    I'd say that this by itself does not explains all the loss of performance, but I don't know if it can be some clue. Anyway, the 1000GHz should be achieved.

     
    You are not authorized to post a reply.
    Page 1 of 212 > >>
    Forums Board Support Packages (BSP) Linux