wl18xx R8.5 slow ping time on network ~120ms

user4195508

Other Parts Discussed in Thread: WL1801

Hello, I am working on a beaglebone black, TI kernel 3.14.19 with a wl1801. All modules were successfully built at R8.5 following the WL18xx_System_Build_Scripts and WL18xx Platform Integration Guide pages.

wlconf was used to generate the appropriate wl18xx-conf.bin and default wl1271-nvs.bin is used.

We seem to have performance issues since ping time within network is around 120ms. the modules were originally built from kernel source with wl18xx-fw-2.bin and ping time was around 5ms. Driver was updated because we had crashing issues:wlcore: ERROR SW watchdog interrupt received! starting recovery.

Please help.

over 10 years ago

0 Joseph Gigi over 10 years ago

TI__Guru* 85400 points

Hi,

Can you share the full boot logs including the ping command?

Regards,
Gigi Joseph.

0 user4195508 over 10 years ago in reply to Joseph Gigi

Prodigy 60 points

Here is the relevant boot log:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.14.19 (gcc version 4.9.1 (crosstool-NG git+52260cc) ) #7 PREEMPT Fri May 1 11:56:14 EDT 2015
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: TI AM335x

Initializing WiFi... [    6.486657] Loading modules backported from Linux version R8.5-0-gcb51164
Jan 1 00:00:01 custom-linux user.info kernel: [    6.486657] Loading modules backported from Linux version R[    6.499851] Backport generated by backports.git R8.4-0-g0d46f43
8.5-0-gcb51164
Jan 1 00:00:01 custom-linux user.info kernel: [    6.499851] Backport generated by backports.git R8.4-0-g0d46f43
[    6.607541] cfg80211: Calling CRDA to update world regulatory domain
Jan 1 00:00:01 custom-linux user.info kernel: [    6.607541] cfg80211: Calling CRDA to update world regulatory domain
[    6.987260] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
Jan 1 00:00:01 custom-linux user.info kernel: [    6.987260] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[    7.068766] wlcore: loaded
[    7.071665] wlcore: driver version: R8.5-dirty
[    7.076319] wlcore: compilation time: test
Jan 1 00:00:01 custom-linux user.info kernel: [    7.068766] wlcore: loaded
Jan 1 00:00:01 custom-linux user.info kernel: [    7.071665] wlcore: driver version: R8.5-dirty
Jan 1 00:00:01 custom-linux user.info kernel: [    7.076319] wlcore: compilation time: test
Successfully initialized wpa_supplicant
[    9.255463] wlcore: PHY firmware version: Rev 8.2.0.0.224
Jan 1 00:00:04 custom-linux user.info kernel: [    9.255463] wlcore: PHY firmware version: Rev 8.2.0.0.224
[    9.309412] wlcore: firmware booted (Rev 8.9.0.0.31)
Jan 1 00:00:04 custom-linux user.info kernel: [    9.309412] wlcore: firmware booted (Rev 8.9.0.0.31)
[    9.323121] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 1 00:00:04 custom-linux user.info kernel: [    9.323121] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Starting Dropbear SSH Server... udhcpc (v1.22.1) started
Jan 1 00:00:04 custom-linux daemon.info init: starting pid 178, tty '/dev/ttyO0': '/sbin/getty -L -n ttyO0 115200 vt100 '
Jan 1 00:00:04 custom-linux authpriv.info dropbear[177]: Running in background
[    9.458521] random: nonblocking pool is initialized
Jan 1 00:00:04 custom-linux user.notice kernel: [    9.458521] random: nonblocking pool is initialized

custom-linux login: Sending discover...
[    9.996361] wlan0: authenticate with 1c:df:0f:e4:fe:cc
Jan 1 00:00:04 custom-linux user.info kernel: [    9.996361][   10.004904] wlan0: send auth to 1c:df:0f:e4:fe:cc (try 1/3)
wlan0: authenticate with 1c:df:0f:e4:fe:cc
Jan 1 00:00:04 custom-linux user.info kernel: [   10.004904] wlan0: send auth to 1c:df:0f:e4:fe:cc (try 1/3)
[   10.027903] wlan0: authenticated
[   10.036895] wlan0: associate with 1c:df:0f:e4:fe:cc (try 1/3)
Jan 1 00:00:04 custom-linux user.info kernel: [   10.027903] wlan0: authenti[   10.047171] wlan0: RX AssocResp from 1c:df:0f:e4:fe:cc (capab=0x411 status=0 aid=26)
cated
Jan 1 00:00:04 custom-linux user.info kernel: [   10.036895] wlan0: associate with 1c:df:0f:e4:fe:cc [   10.063965] wlan0: associated
(try 1/3)
Jan 1 00:00:04 custom-linux user.[   10.071205] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
info kernel: [   10.047171] wlan0: RX AssocResp from 1c:df:0f:e4:fe:cc (capab=0x411 status=0 aid=26)
Jan 1 00:00:04 custom-linux user.info kernel: [   10.063965] wlan0: associated
Jan 1 00:00:04 custom-linux user.info kernel: [   10.071205] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   10.155065] wlcore: Association completed.
Jan 1 00:00:04 custom-linux user.info kernel: [   10.155065] wlcore: Association completed.
Sending discover...
Sending select for 192.168.10.66...
Lease of 192.168.10.66 obtained, lease time 86400
deleting routers
adding dns 192.168.10.1
adding dns 0.0.0.0

Here is the ping:

ping -R 192.168.10.66
PING 192.168.10.66 (192.168.10.66) 56(124) bytes of data.
64 bytes from 192.168.10.66: icmp_req=1 ttl=64 time=51.1 ms
RR:     192.168.10.98
        192.168.10.66
        192.168.10.66
        192.168.10.98

64 bytes from 192.168.10.66: icmp_req=2 ttl=64 time=82.9 ms     (same route)
64 bytes from 192.168.10.66: icmp_req=3 ttl=64 time=302 ms      (same route)
64 bytes from 192.168.10.66: icmp_req=4 ttl=64 time=110 ms      (same route)
64 bytes from 192.168.10.66: icmp_req=5 ttl=64 time=136 ms      (same route)
64 bytes from 192.168.10.66: icmp_req=6 ttl=64 time=148 ms      (same route)
64 bytes from 192.168.10.66: icmp_req=7 ttl=64 time=186 ms      (same route)
64 bytes from 192.168.10.66: icmp_req=8 ttl=64 time=215 ms      (same route)
64 bytes from 192.168.10.66: icmp_req=9 ttl=64 time=231 ms      (same route)
^C
--- 192.168.10.66 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8009ms
rtt min/avg/max/mdev = 51.149/162.793/302.381/74.630 ms

Let me know if you need more logs

0 user4195508 over 10 years ago in reply to user4195508

Prodigy 60 points

Here is my .dts in case

&mmc3 {
/* these are on the crossbar and are outlined in the
xbar-event-map element */
dmas = <&edma 12 &edma 13>;
dma-names = "tx", "rx";
status = "okay";
vmmc-supply = <&vmmcwifi_fixed>;
bus-width = <4>;
pinctrl-names = "default";
pinctrl-0 = <&mmc3_pins_default &wlan_pins_default>;
ti,non-removable;
ti,needs-special-hs-handling;
cap-power-off-card;
keep-power-in-suspend;

#address-cells = <1>;
#size-cells = <0>;
wlcore: wlcore@0 {
compatible = "ti,wlcore";
reg = <2>;
interrupt-parent = <&gpio0>;
interrupts = <21 IRQ_TYPE_NONE>;
};
};

0 Shahar Patury over 10 years ago in reply to user4195508

TI__Expert 5840 points

Hi,

The high average Ping time looks like as the device is running in PS mode.
Can you please share WIFI Sniffer logs, and the wl18xx-conf.bin file?

Thanks
Shahar

0 user4195508 over 10 years ago in reply to Shahar Patury

Prodigy 60 points

Thanks for your help, it looks like you are right, if I type: iw wlan0 set power_save off

The ping time falls below 5ms, How do I fix this?

What tool should I use to give you the log you need? I attached my wl18xx-conf.bin file.

Fullscreen wl18xx-conf.bin.txt Download

��g
�
�
P
P## 22
K�2d ��<���


�1	��X

???�?�d,0	^


�%=*�' N
2����P��

L0u�aP����IP�L�W�^���I� @'?((-�������������} �

	��������������/���������������������������������������������������������������������������������������������������������������������������������������d�������d@p������

0 user4195508 over 10 years ago in reply to user4195508

Prodigy 60 points

Problem solved, CONFIG_CFG80211_DEFAULT_PS was enabled, thanks again.

0 Joseph Gigi over 10 years ago in reply to user4195508

TI__Guru* 85400 points

HI,

Thanks! I will mark this post as answered.

Regards,
Gigi Joseph.

Wi-Fi

Wi-Fi forum

wl18xx R8.5 slow ping time on network ~120ms