WL1285Q on Android4.3 Miracast Low Throughput issue

Hi.

I recommend that you upgrade to the latest driver/firmware versions as the one you are using is pretty old.
The latest version is: ol_R5.SP7.01

Regards,
Gigi Joseph.

Hi Joseph, 

Thanks for your information, 

do you have link where can download ol_R5.SP7.01 FW  ?

BR

K.C.

Hi K.C,

All TI driver/firmware/utils releases are available at: https://github.com/TI-OpenLink

Regards,
Gigi Joseph.

Hi Joseph, 

Thanks for your information, however, After I updated it that it seems that this issue still existed.

do you have other idea ?

BR

K.C.

Hi Joseph, 

We've try to build the version of "ol_R5.SP7.01" as like the following

wl12xx: firmware booted (Rev 7.3.10.0.139) >> ol_R5.SP4.01 is 7.3.10.0.136

wl12xx: state: 2

wl12xx: adding p2p mgmt vif

wl12xx: Association completed.

wl12xx: removing interface 00:da:36:16:de:ec

wl12xx: removing interface 00:da:36:16:de:eb

ieee80211 phy0: Hardware restart was requested

wl12xx: state: 0

wl12xx: forcing mr firmware

wl12xx: firmware booted (Rev 7.5.7.0.47)  >>  ol_R5.SP4.01 is 7.5.7.0.46


It seems this issue still existed, do you have any other advise ?

BR
K.C

Hi TI member, 

any suggestion that I could solve this  “discoverPeers”  issue ?

BR

K.C

Hi K.C,

Can you please share the iPerf numbers?

Regards,
Gigi Joseph.

Hi Joseph, 

Was it relative at iPef version ?

our iPerf version is 2.0.5

BR.

K.C

Hi K.C,

I was looking for the iPerf report...
What throughput numbers does iPerf give?

Regards,
Gigi Joseph.

Hi Joseph, 

our setting as like below, 

On machine:
-s -w 1M
On PC:
iperf -c 192.168.11.101 -t 60 -i 10 -w 1M
 

It results to the RX throughput down to only 5~6Mbps(normal is about 24Mbps).

BR

KC

Hi,

iPerf of 5-6 Mbps is very low... Because its basic TCP data, and nothing to do with Miracast.
I would suggest the below

1. Check RF performance
2. Check the Android porting/configuration
3. Check the rate that you are using. Do you use 11n mode?

Regards,
Gigi Joseph.

Hi Joseph, 

Thanks for your suggestion, 

We don't think it was relative RF performance issue, because when in normal operation, out T-put could reach 24 Mbps, it happened such low T-put  only when system operated Miracast function and it seems be caused by “discoverPeers”. 

Is it possible that we could turn off “discoverPeers” ? it might could increase T-Put, 

what do you think ?

BR

K.C.

Hi K.C,

I don't fully understand your question. As per the Android documentation, discoveryPeers is used to discover available peer devices in the vicinity.
So if you remove the API, how can you connect?

Also, the case (2) that you mentioned above:

***
(2) If AP is connected, and “discoverPeers” is called to find source device,
the warning message will keep output to debug port. The throughput becomes bad.
***

If I understand the scenario well, you are connected to an AP, and then trying to connect to a P2P device for Miracast.

In this situation, where is the question of low TP as the connection itself is not made... and you would need the discoverPeers method, right?

Regards,
Gigi Joseph.

Hi Joseph, 

Thanks so much for your usually support, 

we've checked the UDP performance by iPerf, the station was LG Nexus4 and P2P directly transmitted the data to DUT,but it show some package loss issue as like in the attachment

0435.For TI reference.xlsx

The UDP downlink will show package loss and sometimes will be out of order, 
The UDP uplink was better, but it still existed some package loss issue.

We have already check their RF HW design, it should be no so much problem, even we tested by remove ID and use external antenna, the result was almost same.

does it need some fine tune for the driver ? please advise us.

BR

K.C

Hi K.C,

With this information, I can only suspect three things (1) the environment has some noise (2) the remote RF is not good and (3) The host is not able to handle high TP (high CPU).

To know more, we will need the Air Sniffer Log and the CPU usage numbers of bad runs.

Can you please provide them?

Regards,
Gigi Joseph.